Transmission and Routing of Exchange Access Traffic Sample Clauses

Transmission and Routing of Exchange Access Traffic. PURSUANT TO 251(c)(2) 13 5.1 Scope of Traffic 13 5.2 Trunk Group Architecture and Traffic Routing 13 5.3 Logical Trunk Groups 13 5.4 End Office Access 13 ARTICLE VI MEET-POINT BILLING ARRANGEMENTS 14 6.1 Meet-Point Billing Services 14 6.2 Data Format and Data Transfer 14 6.3 Errors or Loss of Access Usage Data 15 6.4 Payment 15 6.5 Additional Limitation of Liability Applicable to Meet-Point Billing Arrangements 16 ARTICLE VII BLV/BLVI TRAFFIC 16
Sample 1Sample 2See All (4)
Transmission and Routing of Exchange Access Traffic. 9.1 Scope of Traffic.
Sample 1Sample 2
Transmission and Routing of Exchange Access Traffic. 9.1 Scope of Traffic.‌‌‌‌‌‌‌‌‌‌‌ Section 9 prescribes parameters for certain trunks to be established over the Interconnections specified in Sections 2 through 5 of this Attachment for the transmission and routing of traffic between OneStar Telephone Exchange Service Customers and Interexchange Carriers (“Access Toll Connecting Trunks”), in any case where OneStar elects to have its End Office Switch subtend a Verizon Tandem. This includes casually-dialed (1010XXX and 101XXXX) traffic.
Sample 1
Transmission and Routing of Exchange Access Traffic. 39.1Scope of Traffic This Section prescribes parameters for certain trunk groups (“Access Toll Connecting Trunks”) to be established over the Interconnections specified in this Agreement for the transmission and routing of Exchange Access traffic and nontranslated 800 traffic between SBCT Telephone Exchange Service Customers and Interexchange Carriers.
Sample 1
Transmission and Routing of Exchange Access Traffic. The Parties shall jointly provide Tandem-transported Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic from/to ITC/\DeltaCom's End Users, and to originate and terminate traffic to/from BellSouth's End Users.
Sample 1
Transmission and Routing of Exchange Access Traffic. 7.1 Scope of Traffic.
Sample 1
Transmission and Routing of Exchange Access Traffic 
Sample 1Sample 2Sample 3See All (179)

Related to Transmission and Routing of Exchange Access Traffic

  • Transmission and Routing of Telephone Exchange Service Traffic 50.4.1 The Appendix Reciprocal Compensation, which is/are attached hereto and incorporated herein by reference, prescribe traffic routing parameters for Local Interconnection Trunk Group(s) the Parties shall establish over the Interconnections specified in the Appendix ITR, which is/are attached hereto and incorporated herein by reference.

  • Information Access Each Party (“Disclosing Party”) shall make available to another Party (“Requesting Party”) information that is in the possession of the Disclosing Party and is necessary in order for the Requesting Party to: (i) verify the costs incurred by the Disclosing Party for which the Requesting Party is responsible under this Agreement; and (ii) carry out its obligations and responsibilities under this Agreement. The Parties shall not use such information for purposes other than those set forth in this Article 25.1 of this Agreement and to enforce their rights under this Agreement.

  • Voice Information Service Traffic 5.1 For purposes of this Section 5, (a) Voice Information Service means a service that provides [i] recorded voice announcement information or [ii] a vocal discussion program open to the public, and (b) Voice Information Service Traffic means intraLATA switched voice traffic, delivered to a Voice Information Service. Voice Information Service Traffic does not include any form of Internet Traffic. Voice Information Service Traffic also does not include 555 traffic or similar traffic with AIN service interfaces, which traffic shall be subject to separate arrangements between the Parties. Voice Information Service Traffic is not subject to Reciprocal Compensation charges under Section 7 of the Interconnection Attachment.

  • Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit B.

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