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/EAS Traffic (“Local Interconnection Trunks”) on the Direct Interconnection Facility. The Parties agree that all Local/EAS Traffic exchanged between them will be on trunks exclusively dedicated to such traffic. Neither Party will terminate InterLATA toll traffic or originate untranslated traffic to service codes (e.g., 800, 888) over Local Interconnection Trunks.

Appears in 3 contracts

Samples: Interconnection Agreement, Interconnection Agreement, Interconnection Agreement

AutoNDA by SimpleDocs

Local Interconnection Trunks. 3.4.2.1.1 2.4.1.1.1 The Parties will establish a local trunk group groups for the exchange of Local/Local and EAS Traffic and ISP Bound Traffic (“Local Interconnection Trunks”) on the Direct Interconnection Facility. The Parties agree that all Local/EAS Traffic and ISP Bound Traffic exchanged between them will be on trunks exclusively dedicated to such traffic. Neither Party will terminate InterLATA toll traffic or originate untranslated traffic to service codes (e.g., e.g. 800, 888) over Local Interconnection Trunks.

Appears in 1 contract

Samples: General Terms And

Local Interconnection Trunks. 3.4.2.1.1 The Parties will establish a local trunk group for the exchange of Local/Local Traffic, EAS Traffic, and ISP-Bound Traffic (“Local Interconnection Trunks”) on the Direct Interconnection Facility. The Parties agree that all Local/Local Traffic, EAS Traffic and ISP-Bound Traffic exchanged between them will be on trunks exclusively dedicated to such traffic. Neither Party will terminate InterLATA toll traffic or originate untranslated traffic to service codes (e.g., 800, 888) over Local Interconnection Trunks.

Appears in 1 contract

Samples: Essential Facilities Agreement

Local Interconnection Trunks. 3.4.2.1.1 The Parties will establish a local 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 Local Traffic exchanged between them will be on trunks exclusively dedicated to such traffic. Neither Party will terminate terminate, InterLATA toll traffic Toll Traffic or originate untranslated traffic to service codes (e.g., 800, 888) over Local Interconnection Trunks.

Appears in 1 contract

Samples: Interconnection Agreement

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/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 trafficTraffic. Neither Party will terminate InterLATA IntraLA TA or InterLA TA toll traffic or originate untranslated traffic to service codes (e.g., 800, 888) over Local Interconnection Trunks.

Appears in 1 contract

Samples: Interconnection Agreement

Local Interconnection Trunks. 3.4.2.1.1 2.4.1.1.1 The Parties will establish a local separate trunk group groups for the exchange exchanged 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 InterconnecAtitotanchment to service codes (e.g., 800, 888) over Local servicecodes(e.g. 800,888)over Interconnection Trunks.

Appears in 1 contract

Samples: Interconnection Agreement

Local Interconnection Trunks. 3.4.2.1.1 The Parties will establish a local trunk group for the exchange of Local/ELCS/EAS Traffic, ISP-Bound Traffic and Tandem Transit Service 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, InterLATA toll traffic or originate untranslated traffic to service codes (e.g., 800, 888) over Local Interconnection Trunks.

Appears in 1 contract

Samples: Interconnection Agreement

AutoNDA by SimpleDocs

Local Interconnection Trunks. 3.4.2.1.1 The Parties will establish a local trunk group for the exchange of Local/EAS Local Traffic (“Local Interconnection Trunks”) on the Direct Interconnection Facility. The Parties agree that all Local/EAS Local Traffic exchanged between them will be on trunks exclusively dedicated to such traffic. Neither Party will terminate InterLATA toll traffic or originate untranslated traffic to service codes (e.g., 800, 888) over Local Interconnection Trunks.

Appears in 1 contract

Samples: Interconnection Agreement

Local Interconnection Trunks. 3.4.2.1.1 3.3.1.1 The Parties will establish a local trunk group for the exchange of Local/EAS and ISP-Bound Traffic (“Local Interconnection Trunks”) on the Direct Interconnection Facility. The Parties agree that all Local/EAS 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.

Appears in 1 contract

Samples: Interconnection Agreement

Local Interconnection Trunks. 3.4.2.1.1 3.4.1 The Parties will establish a local trunk group for the exchange of Local/Local Traffic, EAS Traffic, and ISP-Bound Traffic (“Local Interconnection Trunks”) on the Direct Interconnection Facility. The Parties agree that all Local/Local Traffic, EAS Traffic and ISP-Bound Traffic exchanged between them will be on trunks exclusively dedicated to such traffic. Neither Party will terminate IntraLATA toll traffic or InterLATA toll traffic or originate untranslated traffic to service codes (e.g., 800, 888) over Local Interconnection Trunks.

Appears in 1 contract

Samples: Essential Facilities Agreement

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, InterLATA toll traffic or originate untranslated traffic to service codes (e.g., 800, 888) over Local Interconnection Trunks.

Appears in 1 contract

Samples: Interconnection Agreement

Time is Money Join Law Insider Premium to draft better contracts faster.