Local Interconnection Trunks Clause Samples

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. Interconnection for Local Traffic and IntraLATA Toll Traffic shall be provided via one-way trunks, or by written notice (in the form of an ASR, as defined in Section 23.1) to Ameritech from TWC, two-way trunks. Once two-way trunks are employed, TWC shall provide to Ameritech a PLU or actual minutes of use. No Party shall construct facilities which require another Party to build unnecessary facilities.

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. Unless otherwise agreed (e.g., in the case of 911 trunks) the Parties shall configure two-way trunk groups as a direct transmission path through the Interconnection Point(s) specified in Schedule 3.0. TWTC shall specify the Digital Signal Level of the trunk facilities (e.g., DS0, DS1 or higher, where available) consistent with the forecasting requirements in Section 19.3. No Party shall terminate Exchange Access traffic or originate untranslated 800/888 traffic over Local Interconnection Trunks.

Local Interconnection Trunks. 3.4.1 The Parties will establish a local trunk group for the exchange of Local Traffic, EAS Traffic, and ISP-Bound Traffic (“Local Interconnection Trunks”) on the Direct Interconnection Facility. The Parties agree that all 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. 3.4.2 If the Parties’ originating Local Traffic, 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 according to standard practices as set forth in Section 8. 3.4.3 All traffic terminated over the Local Interconnection Trunks must terminate in the End Office or subtending Remote; i.e., no Tandem switching will be performed in the End Office, including transiting to other carriers connected to that End Office except as provided in Section 5.3 of this Attachment. 3.4.4 All non-local, non-EAS and non-ISP-Bound traffic shall be completed by a separate carrier(s) or on a separate trunk group(s).

Local Interconnection Trunks. 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. Neither Party will terminate IntraLATA or InterLATA toll traffic or originate untranslated traffic to service codes (e.g., 800, 888) over Local Interconnection Trunks. 3.3.1.2 If the Parties’ originated Local/EAS 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. 2.4.1.1.1 The Parties will establish separate trunk groups for the exchanged of Local/EAS Traffic and ISP-Bound Traffic ("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 servicecodes(e.g. 800,888)over Interconnection Trunks. 2.4.1.1.2 If the Parties'originatedLocal/EASTraffic andISP- BotmdTrafficis exchangeudtilizingthesametwo-way InterconnectionTrunk, both parties will mutually coordinatteheprovisioningandquantityof trunkstobe utilizedin thisarrangement. 2.4.1. 2AccessTrunks 2.4.1.2.1 Toll traffic shallnot be routedon the Interconnection Trunks.Separatterunkgroupsfor suchToll andAccess Traffic must be established on the Direct. InterconnectioFnacility. Standaradccescsompensation arrangementfsrom the ILECs respectivetariffs will applytothetoll trunks.

Local Interconnection Trunks. 2.4.1.1.1 The Parties will establish local trunk groups for the exchange of 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. 800, 888) over Local Interconnection Trunks. 2.4.1.1.2 If the Parties’ originated Local and 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