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 Othe...
Tandem Transit Traffic. 11.1 As used in this Section 11, Tandem Transit Traffic is Telephone Exchange Service traffic that originates on Reconex’s network, and is transported through a Verizon Tandem to the Central Office of a CLEC, ILEC other than Verizon, Commercial Mobile Radio Service (CMRS) carrier, or other LEC, that subtends the relevant Verizon Tandem to which Reconex delivers such traffic. Neither the originating nor terminating customer is a Customer of Verizon. Subtending Central Offices shall be determined in accordance with and as identified in the Local Exchange Routing Guide (LERG). Switched Exchange Access Service traffic is not Tandem Transit Traffic.
11.2 Tandem Transit Traffic Service provides Reconex with the transport of Tandem Transit Traffic as provided below.
11.3 Tandem Transit Traffic may be routed over the Local Interconnection Trunks described in Sections 3 through 6. Reconex shall deliver each Tandem Transit Traffic call to Verizon with CCS and the appropriate Transactional Capabilities Application Part (“TCAP”) message to facilitate full interoperability of CLASS Features and billing functions. The Parties will mutually agree to the types of records to be exchanged until industry standards are established and implemented.
11.4 Reconex shall exercise its best efforts to enter into a reciprocal Telephone Exchange Service traffic arrangement (either via written agreement or mutual Tariffs) with any CLEC, ILEC, CMRS carrier, or other LEC, to which it delivers Telephone Exchange Service traffic that transits Verizon’s Tandem Office. If Reconex does not enter into and provide notice to Verizon of the above referenced arrangement within 180 days of the initial traffic exchange with relevant third party carriers, then Verizon may, at its sole discretion, terminate Tandem Transit Service at anytime upon thirty (30) days written notice to Reconex.
11.5 Reconex shall pay Verizon for Transit Service that Reconex originates at the rate specified in the Pricing Attachment, plus any additional charges or costs the receiving CLEC, ILEC, CMRS carrier, or other LEC, imposes or levies on Verizon for the delivery or termination of such traffic, including any Switched Exchange Access Service charges.
11.6 Verizon will not provide Tandem Transit Traffic Service for Tandem Transit Traffic to be delivered to a CLEC, ILEC, CMRS carrier, or other LEC, if the volume of Tandem Transit Traffic to be delivered to that carrier exceeds one (1) DS1 level volume of calls.
11.7 If or ...
Tandem Transit Traffic. 12.1 As used in this Section 12, Tandem Transit Traffic is Telephone Exchange Service traffic that originates on AT&T Mobility’s network, and is transported through a Frontier Tandem to the Central Office of a CMRS, ILEC other than Frontier, Commercial Mobile Radio Service (CMRS) carrier, or other LEC, that subtends the relevant Frontier Tandem to which AT&T Mobility delivers such traffic. Neither the originating nor terminating Customer is a Customer of Frontier. Subtending Central Offices shall be determined in accordance with and as identified in the Local Exchange Routing Guide (LERG). Switched Exchange Access Service traffic is not Tandem Transit Traffic.
Tandem Transit Traffic. Local Traffic may include IP-PSTN Traffic.
Tandem Transit Traffic. Notwithstanding any other terms of this Agreement, at the time of the Effective Date of this Agreement, Xxxxx does not offer Transit Service, as herein defined in the Glossary Attachment of this Agreement, to TCA or any other connecting carriers. In the event that Xxxxx subsequently offers Transit Service to any third party connecting carrier, Xxxxx will promptly notify TCA of the availability of Transit Service. Upon such notice, the Parties agree to negotiate in good faith terms for the completion and compensation of Transit Traffic and amend this Agreement accordingly. If, within thirty (30) days of the notice of availability of Transit Service, the Parties have been unable to negotiate terms for completion and compensation of Transit Traffic, the Parties shall resolve it pursuant to the Dispute Resolution terms of the Agreement. During the pendency of the dispute, if requested by TCA, Xxxxx shall provide Transit Service to TCA via the Local Trunk Group, subject to true-up of compensation upon resolution of the dispute.
Tandem Transit Traffic. 12.1 As used in this Section, Tandem Transit Traffic is Telephone Exchange Service traffic that originates on Princeton's network, and is transported through Verizon’s Tandem to the subtending End Office or its equivalent of another carrier (CLEC, ILEC other than Verizon, Commercial Mobile Radio Service (CMRS) carrier, or other LEC (“Other Carrier”). Neither the originating nor terminating customer is a Customer of Verizon. 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 Verizon be required to transit traffic through a Verizon Tandem to a Central Office that the LERG does not identify as subtending that particular Verizon Tandem. Switched Exchange Access Service traffic is not Tandem Transit Traffic.
12.2 Tandem Transit Traffic Service provides Princeton 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. Princeton shall deliver each Tandem Transit Traffic call to Verizon’s Tandem with CCS and the appropriate Transactional Capabilities Application Part (“TCAP”) message to facilitate full interoperability of CLASS Features and billing functions.
Tandem Transit Traffic. 12.1 As used in this Section 12, Tandem Transit Traffic is Telephone Exchange Service traffic that originates on NOW Communications, Inc.'s network, and is transported through a Verizon Tandem to the Central Office of a CLEC, ILEC other than Verizon, Commercial Mobile Radio Service (CMRS) carrier, or other LEC, that subtends the relevant Verizon Tandem to which NOW Communications, Inc. delivers such traffic. Neither the originating nor terminating customer is a Customer of Verizon. Subtending Central Offices shall be determined in accordance with and as identified in the Local Exchange Routing Guide (LERG). Switched Exchange Access Service traffic is not Tandem Transit Traffic.
12.2 Tandem Transit Traffic Service provides NOW Communications, Inc. 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. NOW Communications, Inc. shall deliver each Tandem Transit Traffic call to Verizon with CCS and the appropriate Transactional Capabilities Application Part (“TCAP”) message to facilitate full interoperability of CLASS Features and billing functions.
Tandem Transit Traffic. All voice calls exchanged between the Parties originating from or terminating to the PSTN shall be jurisdictionalized and compensated in the same manner (e.g., reciprocal compensation, interstate access, and intrastate access) regardless of the technology used to originate, terminate, or transport the call, including voice calls that are transmitted in part via the public Internet or a private IP network (VoIP) that originate from or terminate to the PSTN.
Tandem Transit Traffic. 12.1 As used in this Section, Tandem Transit Traffic is Telephone Exchange Service traffic that originates on Hypercube's network, and is transported through Verizon’s Tandem to the subtending End Office or its equivalent of another carrier (CLEC, ILEC other than Verizon, Commercial Mobile Radio Service (CMRS) carrier, or other LEC (“Other Carrier”), when neither the originating nor terminating customer is a Customer of Verizon. For the avoidance of any doubt, under no circumstances shall Verizon be required to transit traffic through a Verizon Tandem to an End Office that does not have local interconnection facilities and direct trunks to that particular Verizon Tandem. Switched Exchange Access Service traffic is not Tandem Transit Traffic.
12.2 Tandem Transit Traffic Service provides Hypercube 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. Hypercube shall deliver each Tandem Transit Traffic call to Verizon’s Tandem with CCS and the appropriate Transactional Capabilities Application Part (“TCAP”) message to facilitate full interoperability of CLASS Features and billing functions.
Tandem Transit Traffic. 12.1 As used in this Section, Tandem Transit Traffic is Telephone Exchange Service traffic that originates on ADSC'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”), when neither the originating nor terminating customer is a Customer of Frontier. For the avoidance of any doubt, under no circumstances shall Frontier be required to transit traffic through a Frontier Tandem to an End Office that does not have local interconnection facilities and direct trunks to that particular Frontier Tandem. Switched Exchange Access Service traffic is not Tandem Transit Traffic.
12.2 Tandem Transit Traffic Service provides ADSC 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. ADSC 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.