Common use of Local Interconnection Trunks Clause in Contracts

Local Interconnection Trunks. 3.4.2.1.1 The Parties will establish a local trunk group for the exchange of Local/ELCS/EAS Traffic and ISP-Bound Traffic (“Local Interconnection Trunks”) on the Direct Interconnection Facility. The Parties agree that all Local/ELCS/EAS Traffic and ISP-Bound Traffic exchanged between them will be on trunks exclusively dedicated to such traffic. Neither Party will terminate CMRS traffic and/or InterLATA toll traffic or originate untranslated traffic to service codes (e.g., 800, 888) over Local Interconnection Trunks. 3.4.2.1.2 If the Parties’ originating Local/ELCS/EAS Traffic and ISP-Bound Traffic is exchanged utilizing the same two-way Local Interconnection Trunk, both Parties will mutually coordinate the provisioning and quantity of trunks to be utilized in this arrangement.

Local Interconnection Trunks. 3.4.2.1.1 3.6.1.1 The Parties will establish a local trunk group for the exchange of Local/ELCS/EAS Traffic and ISP-Bound Traffic (“Local Interconnection Trunks”) on the Direct Interconnection Facility. The Parties agree that all Local/ELCS/EAS Traffic and ISP-Bound Traffic exchanged between them will be on trunks exclusively dedicated to such traffic. Neither Party will terminate CMRS traffic and/or traffic, InterLATA toll traffic or originate untranslated traffic to service codes (e.g., 800, 888) over Local Interconnection Trunks. 3.4.2.1.2 3.6.1.2 If the Parties’ originating Local/ELCS/EAS Traffic and ISP-Bound Traffic is exchanged utilizing the same two-way Local Interconnection Trunk, both Parties will mutually coordinate the provisioning and quantity of trunks to be utilized in this arrangement.

Local Interconnection Trunks. 3.4.2.1.1 2.5.1.1 The Parties will establish a local separate trunk group for the exchange of Local/ELCS/EAS Traffic and ISP-Bound Traffic (“"Local Interconnection Trunks”") on the Direct Interconnection Facility. The Parties agree that all Local/ELCS/EAS Traffic and ISP-Bound Traffic exchanged between them will be on trunks exclusively dedicated to such trafficTraffic. Neither Party will terminate CMRS traffic and/or InterLATA IntraLA TA or InterLA TA toll traffic or originate untranslated traffic to service codes (e.g., 800, 888) over Local Interconnection Trunks. 3.4.2.1.2 2.5.1.2 If the Parties’ originating ' originated Local/ELCS/EAS Traffic and ISP-Bound Traffic is exchanged utilizing the same two-way Local Interconnection Trunk, both Parties will mutually coordinate the provisioning and quantity of trunks to be utilized in this arrangement.

Local Interconnection Trunks. 3.4.2.1.1 The Parties will establish a local trunk group for the exchange of Local/ELCS/Local Traffic, EAS Traffic Traffic, and ISP-Bound Traffic (“Local Interconnection Trunks”) on the Direct Interconnection Facility. The Parties agree that all Local/ELCS/Local Traffic, EAS Traffic and ISP-Bound Traffic exchanged between them will be on trunks exclusively dedicated to such traffic. Neither Party will terminate CMRS traffic and/or InterLATA toll traffic or originate untranslated traffic to service codes (e.g., 800, 888) over Local Interconnection Trunks. 3.4.2.1.2 If the Parties’ originating Local/ELCS/Local Traffic, EAS Traffic and ISP-ISP- Bound Traffic is exchanged utilizing the same two-way Local Interconnection Trunk, both Parties will mutually coordinate the provisioning and quantity of trunks to be utilized in this arrangementarrangement according to the UBET Procedures.