Subject Traffic Sample Clauses

The 'Subject Traffic' clause defines the specific types of data, communications, or transactions that are covered under the agreement. It typically outlines what constitutes 'traffic' for the purposes of the contract, such as internet data packets, voice calls, or messaging services, and may set parameters like volume, origin, or destination. By clearly identifying the scope of traffic subject to the agreement, this clause ensures both parties understand their rights and obligations regarding the handling, processing, or exchange of such traffic, thereby reducing ambiguity and potential disputes.
Subject Traffic. Traffic (excluding Commercial Mobile Radio Services traffic, e.g., paging, cellular, PCS) that is originated by an End User of one Party on that Party’s network and terminates to an End User of the other Party on that Party’s network where both End Users are physically located within TTC’s local service exchange area or mandatory EAS service area as defined in TTC’s effective Local Exchange Tariff. Subject Traffic does not include optional local calling scope traffic, i.
View SourceView Similar (12)
Subject Traffic. 5.1.1 Reciprocal Compensation is applicable for Transport and Termination of Subject Traffic as defined in Section 1.41 and is related to the exchange of traffic described in Section 4, as applicable. For the purposes of billing compensation for Subject Traffic, billed minutes will be based upon actual usage recorded, with the exception of traffic described in Section 4.4, where records/reports provided by the transiting carrier shall be the basis for billing if actual usage records are not available. Measured usage begins when the terminating recording switch receives answer supervision from the called end user and ends when the terminating recording switch receives or sends disconnect (release message) supervision, whichever comes first. The measured usage is aggregated at the end of the measurement cycle and rounded to a whole minute. Billing for Subject Traffic shall be based on the aggregated measured usage less traffic that is not Subject Traffic. 5.1.2 Subject to the exceptions described in Sections 5.1.3 below, each Party shall pay the other Party for Transport and Termination of Subject Traffic that either Party delivers to the other Party’s network pursuant to the provisions of this Agreement. The charges and rates for Termination of Subject Traffic shall be at the rates set forth in Appendix B of this Agreement. These charges and rates do not apply to any other types of traffic or for traffic delivered in any other areas other than those set forth in this Agreement as described in Appendix B. 5.1.3 Neither Party will provide any compensation to the other Party for traffic associated with one way paging services, ISP traffic, or video services. 5.1.4 SPRINT does not currently provide fixed wireless services in CITIZENS exchange boundaries, SPRINT agrees that it will provide CITIZENS prior written notice of its intent to launch fixed wireless services in CITIZENS exchange boundaries. Upon CITIZENS receipt of such notice, the Parties agree to negotiate an appropriate agreement or an amendment to this Agreement, which will address the exchange of such traffic. In the event that the Parties cannot reach an agreement on the amendment, the dispute will be resolved pursuant to the provisions of Section 14.0.
View SourceView Similar (11)
Subject Traffic. Traffic (excluding Commercial Mobile Radio Services traffic, e.g., paging, cellular, PCS) that is originated by an End User of one Party on that Party’s network and terminates to an End User of the other Party on that Party’s network where both End Users are physically located within MTC’s Local Service Exchange Area or mandatory EAS service area as defined in MTC’s effective General Service Tariff. Subject Traffic does not include optional local calling scope traffic, i. e. optional rate packages that permit the End User to choose a local calling scope beyond their basic exchange serving area for an additional fee, referred to hereafter as “optional EAS”. All other traffic will be defined as non- Subject Traffic and subject to the terminating Party’s applicable access tariff rates regardless of the technology used to deliver the traffic. For the avoidance of doubt, Subject Traffic includes VoIP-originated or VoIP- terminated traffic exchanged by the Parties over local interconnection facilities.
View SourceView Similar (2)
Subject Traffic. 5.1 Subject to the provisions of Section each Party shall pay the other Party for Transport and Termination of Subject Traffic that either Party delivers to the other Party‘s network pursuant to the provisions of this Agreement. These charges and rates do not apply to any other types of traffic or for traffic delivered in any other areas other than those set forth in this Agreement and described in Appendix A. The Parties agree that WKRTC will not provide any compensation to NPCR for traffic associated with one-way CMRS, including paging services, provided by NPCR.
View SourceView Similar (2)
Subject Traffic. Traffic (excluding Commercial Mobile Radio Services traffic, e.g., paging, cellular, PCS) that is originated by an End User of one Party on that Party’s network and terminates to an End User of the other Party on that Party’s network where both End Users are physically located within NCTC’s local service exchange area or mandatory EAS service area as defined in NCTC’s effective Local Exchange Tariff. Subject Traffic does not include optional local calling scope traffic, i.e., optional rate packages that permit the End User to choose a local calling scope beyond their basic exchange serving area for an additional fee, referred to hereafter as “optional EAS,” or FX Traffic. Any traffic not defined as Subject Traffic is non-Subject Traffic and is subject to the terminating Party’s applicable access tariff rates regardless of the technology used to deliver the traffic.
View Source
Subject Traffic. Traffic (excluding Commercial Mobile Radio Services traffic, e.g., paging, cellular, PCS) that is originated by an End User via the service of one Party and terminates to an End User via the service of the other Party where both End Users are physically located within ▇▇▇▇▇’▇ local service exchange area or mandatory EAS service area as defined in ▇▇▇▇▇’▇ effective Local Exchange Tariff. Subject Traffic does not include optional local calling scope traffic, i.e., optional rate packages that permit the End User to choose a local calling scope beyond their basic exchange serving area for an additional fee, referred to hereafter as “optional EAS,” or FX Traffic. Any traffic not defined as Subject Traffic is non-Subject Traffic and is subject to the terminating Party’s applicable access tariff rates regardless of the technology used to deliver the traffic.
View Source

Related to Subject Traffic

  • Transit Traffic 7.2.2.3.1 CenturyLink will accept traffic originated by CLEC’s network and/or its end user(s) for termination to other Telecommunications Carrier’s network and/or its end users that is connected to CenturyLink's Switch. CenturyLink will also terminate traffic from these other Telecommunications Carriers’ network and/or its end users to CLEC’s network and/or its end users. For purposes of the Agreement, transit traffic does not include traffic carried by Interexchange Carriers. That traffic is defined as Jointly Provided Switched Access. 7.2.2.3.2 The Parties involved in transporting transit traffic will deliver calls to each involved network with CCS/SS7 protocol and the appropriate ISUP/TCAP messages to facilitate full Interoperability and Billing functions. 7.2.2.3.3 The originating company is responsible for payment of appropriate rates to the transit company and to the terminating company. The Parties agree to enter into traffic exchange agreements with third party Telecommunications Carriers prior to delivering traffic to be transited to third party Telecommunications Carriers. In the event one Party originates traffic that transits the second Party’s network to reach a third party Telecommunications Carrier with whom the originating Party does not have a traffic exchange agreement, then the originating Party will indemnify, defend and hold harmless the second Party against any and all charges levied by such third party Telecommunications Carrier, including any termination charges related to such traffic and any attorneys fees and expenses. In the case of IntraLATA LEC Toll traffic where CenturyLink is the designated IntraLATA Toll provider for existing LECs, CenturyLink will be responsible for payment of appropriate usage rates. 7.2.2.3.4 When CenturyLink receives an unqueried call from CLEC to a telephone number that has been ported to another local services provider, the transit rate will apply in addition to any query rates. 7.2.2.3.5 In the case of a transit call that terminates in the Local Calling Area but in a different state than the call originated, and the CLEC does not have an agreement with CenturyLink in the state where the transit call terminated, CLEC must execute an agreement for that state if it is a state served by CenturyLink. In the absence of a second agreement, the transit rate in Exhibit A of this Agreement will be billed to the CLEC.

  • Tandem Transit Traffic ‌ 12.1 As used in this Section, Tandem Transit Traffic is Telephone Exchange Service traffic that originates on Onvoy's network, and is transported through Frontier’s Tandem to the subtending End Office or its equivalent of another carrier (CLEC, ILEC other than Frontier, Commercial Mobile Radio Service (CMRS) carrier, or other LEC (“Other Carrier”). Neither the originating nor terminating customer is a Customer of Frontier. Subtending End Offices shall be determined in accordance with and as identified in the Local Exchange Routing Guide (LERG). For the avoidance of any doubt, under no circumstances shall Frontier be required to transit traffic through a Frontier Tandem to a Central Office that the LERG does not identify as subtending that particular Frontier Tandem. Switched Exchange Access Service traffic is not Tandem Transit Traffic. 12.2 Tandem Transit Traffic Service provides Onvoy with the transport of Tandem Transit Traffic as provided below. 12.3 Tandem Transit Traffic may be routed over the Interconnection Trunks described in Sections 2 through 6 of this Attachment. Onvoy shall deliver each Tandem Transit Traffic call to Frontier’s Tandem with CCS and the appropriate Transactional Capabilities Application Part (“TCAP”) message to facilitate full interoperability of CLASS Features and billing functions. 12.4 Onvoy may use Tandem Transit Traffic Service only for traffic that originates on Onvoy’s network and only to send traffic to an Other Carrier with whom Onvoy has a reciprocal traffic exchange arrangement (either via written agreement or mutual tariffs) that provides for the Other Carrier, to terminate or complete traffic originated by Onvoy and to bill Onvoy, and not to bill Frontier, for such traffic. Onvoy agrees not to use Frontier’s Tandem Transit Traffic Service to send traffic to an Other Carrier with whom Onvoy does not have such a reciprocal traffic exchange arrangement or to send traffic that does not originate on Onvoy’s network. 12.5 Onvoy shall pay Frontier for Tandem Transit Traffic Service at the rates specified in the Pricing Attachment. Frontier will not be liable for compensation to any Other Carrier for any traffic that is transported through Frontier’s Tandem and Frontier reserves the right to assess to Onvoy any additional charges or costs any Other Carrier imposes or levies on Frontier for the delivery or termination of such traffic, including any Switched Exchange Access Service charges. If Frontier is billed by any Other Carrier for any traffic originated by Onvoy, Frontier may provide notice to Onvoy of such billing. Upon receipt of such notice, Onvoy shall immediately stop using Frontier’s Tandem Transit Traffic Service to send any traffic to such Other Carrier until it has provided to Frontier certification that the Other Carrier has removed such billed charges from its bill to Frontier and that the Other Carrier will not bill Frontier for any traffic originated by Onvoy. Such certification must be signed by an authorized officer or agent of the Other Carrier and must be in a form acceptable to Frontier. 12.6 If Onvoy uses Tandem Transit Traffic Service for traffic volumes that exceed the Centum Call Seconds (Hundred Call Seconds) busy hour equivalent of 200,000 combined minutes of use per month (a DS1 equivalent) to the subtending End Office of a particular Other Carrier for any month (the “Threshold Level”). Onvoy shall use good faith efforts to establish direct interconnection with such Other Carrier and reduce such traffic volumes below the Threshold Level. If Frontier believes that ▇▇▇▇▇ has not exercised good faith efforts promptly to obtain such direct interconnection, either Party may use the Dispute Resolution processes of this Agreement. 12.7 If Onvoy fails to comply with Section 12 of this Attachment, such failure shall be a material breach of a material provision of this Agreement and Frontier may exercise any and all remedies under this Agreement and Applicable Law for such breach. 12.8 If or when a third party carrier plans to subtend an Onvoy switch, then Onvoy shall provide written notice to Frontier at least ninety (90) days before such subtending service arrangement becomes effective so that Frontier may negotiate and establish direct interconnection with such third party carrier. Upon written request from Frontier, Onvoy shall offer to Frontier a service arrangement equivalent to or the same as Tandem Transit Traffic Service provided by Frontier to Onvoy as defined in this Section such that Frontier may terminate calls to a Central Office or its equivalent of a CLEC, ILEC other than Frontier, CMRS carrier, or other LEC, that subtends an Onvoy Central Office or its equivalent (“Reciprocal Tandem Transit Service”). Onvoy shall offer such Reciprocal Transit Service arrangements under terms and conditions of an amendment to this Agreement or a separate agreement no less favorable than those provided in this Section. 12.9 Neither Party shall take any actions to prevent the other Party from entering into a direct and reciprocal traffic exchange arrangement with any carrier to which it originates, or from which it terminates, traffic.

  • Contract Transition Upon Contract expiration or termination, the Contractor shall ensure a seamless transfer of Contract responsibilities with any subsequent Contractor necessary to transition the Products and services of the Contract. The incumbent Contractor assumes all expenses related to the contract transition.

  • Compliance Audit LEA shall have the right but shall be under no obligation to conduct audit(s), from time to time, of Provider’s records concerning its compliance obligations as set forth in this Article V. Provider shall make such records and other documents available to LEA upon request.

  • Compliance Audits D. 4.1 Compliance Audit(s). Without limiting the generality of section A.7.4 (Records Review), if requested by the Province from time to time, which request shall be at the Province’s sole discretion, the Recipient, at its own expense, will forthwith retain an independent third party auditor to conduct one or more compliance audits of the Recipient or any Project. The audit will be conducted in accordance with Canadian Generally Accepted Auditing Standards, as adopted by the Canadian Institute of Chartered Accountants, applicable as of the date on which a record is kept or required to be kept under such standards. In addition, the audit will assess the Recipient’s compliance with the terms of the Agreement and will address, with respect to each Project, without limitation, the following: (a) whether the Funds were spent in accordance with the Agreement and with due regard to economy, efficiency, and effectiveness; (b) the Project’s progress or state of completion; (c) whether the financial information the Recipient provided is complete, accurate, and timely, and in accordance with the Agreement; (d) whether the Recipient’s information and monitoring processes and systems are adequate to identify, capture, validate, and monitor the achievement of intended benefits of the Project; (e) the overall management and administration of the Project; (f) recommendations for improvement or redress; and (g) whether prompt and timely corrective action is taken on prior audit findings.