Disconnection by Transmitter Clause Samples

Disconnection by Transmitter. 20.3.1. The Transmitter may disconnect the Customer’s facilities at any connection point and at any time throughout the term of this Agreement in any of the following circumstances: (a) in accordance with subsection 40 (5) of the ▇▇▇▇▇▇▇▇▇▇▇ ▇▇▇, ▇▇▇▇, other applicable law, the Transmitter’s licence or the Market Rules; (b) where required to comply with a decision or order of an arbitrator or court made or given under section 17; (c) during an emergency or where necessary to prevent or minimize the effects of an emergency; or (d) where required by an order or direction from the IESO given in accordance with the Market Rules. 20.3.2. Section 20.5 shall, to the extent applicable, apply in relation to the disconnection of the Customer’s facilities under section 20.3.1.

Related to Disconnection by Transmitter

  • Termination by ViaCord ViaCord may terminate enrollment in the DNA Guardian Program upon written notice to the Client if the Account Payor fails to pay any required fees within sixty (60) days of the payment due date. Before terminating enrollment in the DNA Guardian Program, ViaCord may, at its exclusive discretion, use commercially reasonable effort to contact other Clients, if applicable, and give them the opportunity to take over the Account Payor obligations by executing applicable documentation.

  • TERMINATION BY MPS MPS further reserves the right to terminate this Contract at any time for any reason by giving Contractor written notice by Registered or Certified Mail of such termination. MPS will attempt to give Contractor 20 days’ notice, but reserves the right to give immediate notice. In the event of said termination, Contractor shall reduce its activities hereunder, as mutually agreed to, upon receipt of said notice. Upon said termination, Contractor shall be paid for all services rendered through the date of termination, including any retainage. This section also applies should the Milwaukee Board of School Directors fail to appropriate additional monies required for the completion of the Contract.

  • Termination by ICANN (a) ICANN may, upon notice to Registry Operator, terminate this Agreement if: (i) Registry Operator fails to cure (A) any fundamental and material breach of Registry Operator’s representations and warranties set forth in Article 1 or covenants set forth in Article 2, or (B) any breach of Registry Operator’s payment obligations set forth in Article 6 of this Agreement, each within thirty (30) calendar days after ICANN gives Registry Operator notice of such breach, which notice will include with specificity the details of the alleged breach, (ii) an arbitrator or court of competent jurisdiction has finally determined that Registry Operator is in fundamental and material breach of such covenant(s) or in breach of its payment obligations, and (iii) Registry Operator fails to comply with such determination and cure such breach within ten (10) calendar days or such other time period as may be determined by the arbitrator or court of competent jurisdiction. (b) ICANN may, upon notice to Registry Operator, terminate this Agreement if Registry Operator fails to complete all testing and procedures (identified by ICANN in writing to Registry Operator prior to the date hereof) for delegation of the TLD into the root zone within twelve (12) months of the Effective Date. Registry Operator may request an extension for up to additional twelve (12) months for delegation if it can demonstrate, to ICANN’s reasonable satisfaction, that Registry Operator is working diligently and in good faith toward successfully completing the steps necessary for delegation of the TLD. Any fees paid by Registry Operator to ICANN prior to such termination date shall be retained by ICANN in full. (c) ICANN may, upon notice to Registry Operator, terminate this Agreement if (i) Registry Operator fails to cure a material breach of Registry Operator’s obligations set forth in Section 2.12 of this Agreement within thirty (30) calendar days of delivery of notice of such breach by ICANN, or if the Continued Operations Instrument is not in effect for greater than sixty (60) consecutive calendar days at any time following the Effective Date, (ii) an arbitrator or court of competent jurisdiction has finally determined that Registry Operator is in material breach of such covenant, and (iii) Registry Operator fails to cure such breach within ten (10) calendar days or such other time period as may be determined by the arbitrator or court of competent jurisdiction. (d) ICANN may, upon notice to Registry Operator, terminate this Agreement if (i) Registry Operator makes an assignment for the benefit of creditors or similar act, (ii) attachment, garnishment or similar proceedings are commenced against Registry Operator, which proceedings are a material threat to Registry Operator’s ability to operate the registry for the TLD, and are not dismissed within sixty (60) calendar days of their commencement, (iii) a trustee, receiver, liquidator or equivalent is appointed in place of Registry Operator or maintains control over any of Registry Operator’s property, (iv) execution is levied upon any material property of Registry Operator, (v) proceedings are instituted by or against Registry Operator under any bankruptcy, insolvency, reorganization or other laws relating to the relief of debtors and such proceedings are not dismissed within sixty (60) calendar days of their commencement, or (vi) Registry Operator files for protection under the United States Bankruptcy Code, 11 U.S.C. Section 101, et seq., or a foreign equivalent or liquidates, dissolves or otherwise discontinues its operations or the operation of the TLD. (e) ICANN may, upon thirty (30) calendar days’ notice to Registry Operator, terminate this Agreement pursuant to Section 2 of Specification 7 or Sections 2 and 3 of Specification 11, subject to Registry Operator’s right to challenge such termination as set forth in the applicable procedure described therein. (f) ICANN may, upon notice to Registry Operator, terminate this Agreement if (i) Registry Operator knowingly employs any officer who is convicted of a misdemeanor related to financial activities or of any felony, or is judged by a court of competent jurisdiction to have committed fraud or breach of fiduciary duty, or is the subject of a judicial determination that ICANN reasonably deems as the substantive equivalent of any of the foregoing and such officer is not terminated within thirty (30) calendar days of Registry Operator’s knowledge of the foregoing, or (ii) any member of Registry Operator’s board of directors or similar governing body is convicted of a misdemeanor related to financial activities or of any felony, or is judged by a court of competent jurisdiction to have committed fraud or breach of fiduciary duty, or is the subject of a judicial determination that ICANN reasonably deems as the substantive equivalent of any of the foregoing and such member is not removed from Registry Operator’s board of directors or similar governing body within thirty (30) calendar days of Registry Operator’s knowledge of the foregoing. (g) ICANN may, upon thirty (30) calendar days’ notice to Registry Operator, terminate this Agreement as specified in Section 7.5. (h) [Applicable to intergovernmental organizations or governmental entities only.] ICANN may terminate this Agreement pursuant to Section 7.16.

  • ODUF Message to be Transmitted 6.1.1 The following messages recorded by BellSouth will be transmitted to Quality Telephone: - Message recording for per use/per activation type services (examples: Three Way Calling, Verify, Interrupt, Call Return, etc.) - Measured billable Local - Directory Assistance messages - IntraLATA Toll - WATS and 800 Service - N11 - Information Service Provider Messages - Operator Services Messages - Credit/Cancel Records - Usage for Voice Mail Message Service 6.1.2 Rated Incollects (originated in BellSouth and from other companies) can also be on ODUF. Rated Incollects will be intermingled with BellSouth recorded rated and unrated usage. Rated Incollects will not be packed separately. 6.1.3 BellSouth will perform duplicate record checks on records processed to ODUF. Any duplicate messages detected will be deleted and not sent to Quality Telephone. 6.1.4 In the event that Quality Telephone detects a duplicate on ODUF they receive from BellSouth, Quality Telephone will drop the duplicate message and will not return the duplicate to BellSouth).

  • Termination by Customer You may cancel your acceptance of the Agreement with XOOM at any time within three (3) business days of your enrollment authorization and receipt of this Agreement without penalty or