Transit Traffic Trunk Group Sample Clauses

Transit Traffic Trunk Group. 4.10.5.1 Transit Traffic trunks can either be two-way trunks or two (2) one-way trunks ordered by ComSouth to deliver and receive Transit Traffic. Establishing Transit Traffic trunks at BellSouth Access and Local Tandems provides Intratandem Access to the third parties also interconnected at those tandems. ComSouth shall be responsible for all recurring and nonrecurring charges associated with Transit Traffic trunks and facilities.
Sample 1
AutoNDA by SimpleDocs
Transit Traffic Trunk Group. Transit Traffic trunks can either be two-way trunks or two one-way trunks ordered by PBT to deliver and receive Transit Traffic. Establishing Transit Traffic trunks at BellSouth access and local tandems provides intratandem access to the third Version 3Q03: 11/12/2003 parties also interconnected at those tandems. In accordance with this Agreement, PBT shall be responsible for ordering any one-way or two-way trunks carrying Transit Traffic and PBT shall be responsible for paying for such ordered trunks carrying Transit Traffic.
Sample 1
Transit Traffic Trunk Group. Transit Traffic trunks can either be two-way trunks or two one-way trunks ordered by TWTC to deliver and receive Transit Traffic. Establishing Transit Traffic trunks at BellSouth access and local tandems provides intratandem access to the third parties also interconnected at those tandems. TWTC shall be responsible for all recurring and non-recurring charges associated with Transit Traffic trunks and facilities.
Sample 1
Transit Traffic Trunk Group. 2.19.1 Transit Traffic trunks can either be two-way trunks or two one-way trunks ordered by SouthEast to deliver and receive local and intraLATA toll Transit Traffic from third parties, such as Independent Companies and other CLECs, via AT&T access tandems (or AT&T local tandems for Local Traffic), and Switched Access traffic to and from Interexchange Carriers via AT&T access tandems pursuant to the Transit Traffic section of this Attachment. Establishing Transit Traffic trunks at AT&T access and local tandems provides intratandem access to the third parties also interconnected at those tandems. Attachment 3 – Network Interconnection SouthEast 07/25/08
Sample 1
Transit Traffic Trunk Group. 2.6.5.1 Transit Traffic trunks can either be two-way trunks or two one-way trunks ordered by Knology to deliver and receive local and intraLATA toll Transit Traffic from third parties, such as Independent Companies and other CLECs, via BellSouth access tandems (or BellSouth local tandems for local traffic), and Switched Access traffic to and from Interexchange Carriers via BellSouth access tandems pursuant to the Transit Traffic section of this Attachment. Establishing Transit Traffic trunks at BellSouth access and local tandems provides intratandem access to the third parties also interconnected at those tandems.
Sample 1

Related to Transit Traffic Trunk Group

  • Transit Traffic The following rates will apply:

  • 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.

  • 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.

  • 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):

  • Local Traffic Traffic that is originated by a Customer of one Party on that Party’s network and terminates to a Customer of the other Party on that other Party’s network within Verizon's then current local calling area (including non-optional local calling scope arrangements) as defined in Verizon’s effective Customer Tariffs. A non- optional local calling scope arrangement is an arrangement that provides Customers a local calling scope (Extended Area Service, “EAS”), beyond their basic exchange serving area. Local Traffic does not include optional local calling scope traffic (i.e., traffic that under an optional rate package chosen by the Customer terminates outside of the Customer’s basic exchange serving area). IntraLATA calls originated on a 1+ presubscription basis, or on a casual dialed (10XXX/101XXXX) basis are not considered Local Traffic. Local Traffic does not include any Internet Traffic.

  • Traffic Control The Surveyor shall control traffic in and near surveying operations adequately to comply with provisions of the latest edition of the Texas Manual on Uniform Traffic Control Devices – Part VI which can be found on the State’s internet site. In the event field crew personnel must divert traffic or close traveled lanes, a Traffic Control Plan based upon principles outlined in the latest edition of the Texas Manual on Uniform Traffic Control Devices – Part VI shall be prepared by the Surveyor and approved by the State prior to commencement of field work. A copy of the approved plan shall be in the possession of field crew personnel on the job site at all times and shall be made available to the State’s personnel for inspection upon request.

  • 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.

  • 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:

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

  • Trunk Group Connections and Ordering 5.2.1 For both One-Way and Two-Way Interconnection Trunks, if Onvoy wishes to use a technically feasible interface other than a DS1 or a DS3 facility at the POI, the Parties shall negotiate reasonable terms and conditions (including, without limitation, rates and implementation timeframes) for such arrangement; and, if the Parties cannot agree to such terms and conditions (including, without limitation, rates and implementation timeframes), either Party may utilize the Agreement’s dispute resolution procedures.

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