Interconnection Trunk Groups for Exchange of Local Traffic and Transit Traffic Sample Clauses

Interconnection Trunk Groups for Exchange of Local Traffic and Transit Traffic. Upon mutual agreement of the Parties in a joint planning meeting, the Parties’ shall exchange Local Traffic on two-way interconnection trunk group(s) with the quantity of trunks being mutually determined and the provisioning being jointly coordinated. Furthermore, the Parties shall agree upon the IP(s) for two-way interconnection trunk groups transporting both Parties’ Local Traffic, ISP-bound Traffic and IntraLATA Toll Traffic. PBT shall order such two-way trunks via the Access Service Request (ASR) process. BellSouth will use the Trunk Group Service Request (TGSR) to request changes in trunking. Furthermore, the Parties shall jointly review trunk performance and forecasts on a periodic basis. The Parties’ use of two-way interconnection trunk groups for the transport of Local Traffic, ISP-bound Traffic and IntraLATA Toll Traffic between the Parties does not preclude either Party from establishing additional one-way interconnection trunks for the delivery of its originated Local Traffic, ISP-bound Traffic and IntraLATA Toll Traffic to the other Party.
Sample 1
AutoNDA by SimpleDocs
Interconnection Trunk Groups for Exchange of Local Traffic and Transit Traffic. Upon mutual agreement of the Parties in a joint planning meeting, the Parties shall exchange Local Traffic on two-way interconnection trunk group(s) with the quantity of trunks being mutually determined and the provisioning being jointly coordinated. Furthermore, the Parties shall agree upon the IP(s) for two-way interconnection trunk groups transporting both Parties’ Local Traffic, ISP-Bound Traffic and IntraLATA Toll Traffic. TWTC shall order such two-way trunks via the Access Service Request (ASR) process. BellSouth will use the Trunk Group Service Request (TGSR) to request changes in trunking. Furthermore, the Parties shall jointly review trunk performance and forecasts in accordance with Section 6 Version: 4Q04 Standard ICA 06/15/05 of this Attachment. The Parties’ use of two-way interconnection trunk groups for the transport of Local Traffic, ISP-Bound Traffic and IntraLATA Toll Traffic between the Parties does not preclude either Party from establishing additional one-way interconnection trunks for the delivery of its originated Local Traffic, ISP-Bound Traffic and IntraLATA Toll Traffic to the other Party. Other trunk groups for operator services, directory assistance and intercept must be established pursuant to the applicable BellSouth tariff or other negotiated agreement, if applicable, if service is requested.
Sample 1

Related to Interconnection Trunk Groups for Exchange of Local Traffic and Transit Traffic

  • Traffic Measurement and Billing over Interconnection Trunks 6.1 For billing purposes, each Party shall pass Calling Party Number (CPN) information on at least ninety-five percent (95%) of calls carried over the Interconnection Trunks.

  • One-Way Interconnection Trunks 2.3.1 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from CBB to Verizon, CBB, at CBB’s own expense, shall:

  • Transit Traffic The following rates will apply:

  • Two-Way Interconnection Trunks 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and ICG, ICG shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks, and the Entrance Facility on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.

  • Scope of Interconnection Service 1.3.1 The NYISO will provide Energy Resource Interconnection Service to Interconnection Customer at the Point of Interconnection.

  • Tandem Transit Traffic 12.1 As used in this Section, Tandem Transit Traffic is Telephone Exchange Service traffic that originates on CBB'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). Switched Exchange Access Service traffic is not Tandem Transit Traffic.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where EveryCall has requested an Unbundled Loop and BellSouth uses Integrated Digital Loop Carrier (IDLC) systems to provide the local service to the end user and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to EveryCall. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for EveryCall (e.g. hairpinning):

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Interconnection Service Interconnection Service allows the Interconnection Customer to connect the Large Generating Facility to the Participating TO’s Transmission System and be eligible to deliver the Large Generating Facility’s output using the available capacity of the CAISO Controlled Grid. To the extent the Interconnection Customer wants to receive Interconnection Service, the Participating TO shall construct facilities identified in Appendices A and C that the Participating TO is responsible to construct. Interconnection Service does not necessarily provide the Interconnection Customer with the capability to physically deliver the output of its Large Generating Facility to any particular load on the CAISO Controlled Grid without incurring congestion costs. In the event of transmission constraints on the CAISO Controlled Grid, the Interconnection Customer's Large Generating Facility shall be subject to the applicable congestion management procedures in the CAISO Tariff in the same manner as all other resources.

  • Interconnection Customer’s Interconnection Facilities The Interconnection Customer shall design, procure, construct, install, own and/or control the Interconnection Customer’s Interconnection Facilities described in Appendix A at its sole expense.

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