Common use of Tandem Transit Traffic Clause in Contracts

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, Tandem Transit Traffic is Telephone Exchange Service traffic that originates on PrincetonBCN'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 BCN 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 BCN 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 PrincetonSelectel'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 Selectel 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 Selectel 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 PrincetonWide Voice'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 Wide Voice 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 Wide Voice 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 PrincetonCBAD'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 CBAD 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 CBAD 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 PrincetonNHC'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 NHC 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 NHC 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 PrincetonTQCI'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 TQCI 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 TQCI 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.