Common use of Local Interconnection Trunks Clause in Contracts

Local Interconnection Trunks. 2.5.1.1 The Parties will establish a separate trunk group for the exchange of Local/EAS Traffic and ISP-Bound Traffic ("Local Interconnection Trunks") on the Direct Interconnection Facility. The Parties agree that all Local/EAS and ISP-Bound Traffic exchanged between them will be on trunks exclusively dedicated to such Traffic. Neither Party will terminate IntraLATA or InterLATA toll traffic or originate untranslated traffic to service codes (e.g., 800, 888) over Local Interconnection Trunks. Traffic destined to RHTC End User Customers shall not be routed over the Local I_uterconnection Trunks. 2.5.1.2 If the Parties' originated Local/EAS Traffic and ISP-Botmd 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. 2.5.1.1 The Parties will establish a separate trunk mink group for the exchange of Local/EAS Traffic and ISP-Bound Traffic ("Local Interconnection Trunks") on the Direct Interconnection Facility. The Parties agree that all Local/EAS and ISP-Bound Traffic exchanged between them will be on trunks exclusively dedicated to such Traffic. Neither Party will terminate IntraLATA or InterLATA toll traffic or originate untranslated traffic to service codes (e.g., 800, 888) over Local Interconnection TrunksTrtmks. Traffic destined to RHTC End User Customers shall not be routed over the Local I_uterconnection Interconnection Trunks. 2.5.1.2 If the Parties' originated Local/EAS Traffic and ISP-Botmd 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.