Indirect Traffic Sample Clauses

Indirect Traffic. To the extent that CENTENNIAL and a Transiting Carrier or XXXX and a Transiting Carrier have entered into or may enter into contractual arrangements for the delivery of traffic for termination to the other Party’s customers, both Parties will accept this traffic subject to the compensation arrangements as outlined in Attachment I, Section 2 below.
Indirect Traffic. In the absence of mutual agreement to directly interconnect CINGULAR and ALLENDALE agree to connect indirectly and to send traffic originated on their respective networks through a third party network. Each Party shall be responsible for all costs and arrangements associated with traffic originating on their network and sent through a third party network. Both Parties will accept this traffic subject to the compensation arrangements as outlined in Attachment I, Section 2 below.
Indirect Traffic. When the Parties interconnect their networks indirectly via a third party LEC’s tandem, compensation shall be in accordance with the terms of this Agreement as specified in section 4 and at the rates specified in Attachment 1. Neither Party shall deliver traffic destined to terminate at the other Party’s end office via another LEC’s end office or via another LEC's tandem to the other Party's tandem. When traffic to an end office that directly subtends a third party LEC’s tandem exceeds 500,000 mobile to land minutes of use, then Carrier will establish a direct connection to the ALLTEL end office. If the ALLTEL end office is a remote switch, the Carrier will establish a direct connection to the ALLTEL host switch serving the ALLTEL remote switch. 4.3.1 With respect to Carrier’s originated indirect traffic, the POI will be adjacent to and on the ALLTEL side of the third party LEC's tandem through which ALLTEL and Carrier are indirectly interconnected. With respect to ALLTEL originated indirect traffic, the POI will be adjacent to and on Carrier’s side of the third party LEC's tandem through which ALLTEL and Carrier are indirectly interconnected. 4.3.2 Each Party will assume responsibility for the costs of transport from its switch to the POI for the traffic it originates. 4.3.3 ALLTEL agrees to provide local dialing parity on calls to Carrier’s NPA-NXXs associated with ALLTEL’s local and EAS calling scope, regardless of what transport arrangements ALLTEL utilizes to deliver intraMTA traffic to Carrier, or whether the third party tandem provider imposes or attempts to impose transit fees for traffic in the land-to-mobile direction.
Indirect Traffic. To the extent that ALLTEL and a Transiting Carrier or Baraga and a Transiting Carrier have entered into or may enter into contractual arrangements for the delivery of traffic for termination to the other Party’s customers, both Parties will accept this traffic subject to the compensation arrangements as outlined in Attachment I, Section 2 below.
Indirect Traffic. To the extent that either Party and a third party tandem provider have entered into or may enter into contractual arrangements for the delivery of one Party's originated traffic for termination to the other Party's customers (i.e., traffic that is not covered elsewhere in this Agreement), both Parties will accept this traffic subject to the compensation arrangements as outlined in § 5 below. Both Parties will use best efforts to route Local Service Area calls to the other Party over the direct interconnection facilities except in the case of an emergency, temporary equipment failure, or blocking of existing direct interconnection facilities. Should either Party determine that the other Party is routing its originated traffÉc indirectly, the originating Party agrees to update its routing and translations tables to move such traffic to the direct interconnection facilities within five (5) business days. 8/13/2008 - Final Home Telephone Company, Inc. and Alltel Communications, LLC
Indirect Traffic 

Related to Indirect Traffic

  • Internet Traffic Any traffic that is transmitted to or returned from the Internet at any point during the duration of the transmission.

  • 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.

  • Measured Internet Traffic Dial-up, switched Internet Traffic originated by a Customer of one Party on that Party’s network at a point in a Verizon local calling area, and delivered to a Customer or an Internet Service Provider served by the other Party, on that other Party’s network at a point in the same Verizon local calling area. Verizon local calling areas shall be as defined by Verizon. For the purposes of this definition, a Verizon local calling area includes a Verizon non-optional Extended Local Calling Scope Arrangement, but does not include a Verizon optional Extended Local Calling Scope Arrangement. Calls originated on a 1+ presubscription basis, or on a casual dialed (10XXX/101XXXX) basis, are not considered Measured Internet Traffic. For the avoidance of any doubt, Virtual Foreign Exchange Traffic (i.e., V/FX Traffic) (as defined in the Interconnection Attachment) does not constitute Measured Internet Traffic.

  • 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 Xxxxx 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.

  • Traffic The provisions in this Section apply regardless how the ISP-bound traffic is determined.

  • Posting licensed content on any Website The following terms and conditions apply as follows: Licensing material from an Elsevier journal: All content posted to the web site must maintain the copyright information line on the bottom of each image; A hyper-text must be included to the Homepage of the journal from which you are licensing at xxxx://xxx.xxxxxxxxxxxxx.xxx/science/journal/xxxxx or the Elsevier homepage for books at xxxx://xxx.xxxxxxxx.xxx; Central Storage: This license does not include permission for a scanned version of the material to be stored in a central repository such as that provided by Heron/XanEdu. Licensing material from an Elsevier book: A hyper-text link must be included to the Elsevier homepage at xxxx://xxx.xxxxxxxx.xxx . All content posted to the web site must maintain the copyright information line on the bottom of each image.

  • TRAFFIC INFRACTIONS The State will not be liable for any expense incurred by the Contractor for any parking fees or as a consequence of any traffic infraction or parking violations attributable to employees of the Contractor.

  • Local Traffic Traffic that is originated by a Customer of one Party on that Party’s network and terminates to a Customer of the other Party on that other Party’s network within Verizon's then current local calling area (including non-optional local calling scope arrangements) as defined in Verizon’s effective Customer Tariffs. A non- optional local calling scope arrangement is an arrangement that provides Customers a local calling scope (Extended Area Service, “EAS”), beyond their basic exchange serving area. Local Traffic does not include optional local calling scope traffic (i.e., traffic that under an optional rate package chosen by the Customer terminates outside of the Customer’s basic exchange serving area). IntraLATA calls originated on a 1+ presubscription basis, or on a casual dialed (10XXX/101XXXX) basis are not considered Local Traffic. Local Traffic does not include any Internet Traffic.

  • Third Party Websites The Service may contain or reference links to websites operated by third parties ("Third Party Websites"). These links are provided as a convenience only. Such Third Party Websites are not under our control. We are not responsible for the content of any Third Party Website or any link contained in a Third Party Website. We do not review, approve, monitor, endorse, warrant, or make any representations with respect to Third Party Websites, and the inclusion of any link in the Service, Debit Rewards Offers or any other services provided in connection with them is not and does not imply an affiliation, sponsorship, endorsement, approval, investigation, verification or monitoring by us of any information contained in any Third Party Website. In no event will we be responsible for the information contained in such Third Party Website or for your use of or inability to use such website. Access to any Third Party Website is at your own risk, and you acknowledge and understand that linked Third Party Websites may contain terms and privacy policies that are different from ours. We are not responsible for such provisions, and expressly disclaim any liability for them.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.