IXC Traffic. 11.2.1 Carrier may send traffic to IXCs via Type 2A interface utilizing FGD protocol. 11.2.2 If traffic is handed from Telco directly to an IXC, from Carrier directly to an IXC, from Carrier to an IXC via Trunks with Type 2A interfaces, or from an IXC directly to Telco, access charges shall not apply to Carrier. 11.2.3 When used in the Carrier to Telco direction, Trunks employing a Type 2A interface may be provided to a Telco Tandem Switch to transport calls from Carrier's premises to an IXC's Switched Access Services Feature Group D service at the same Tandem Switch. 11.2.4 When the Parties jointly provide access service to an IXC, each Party will provide its own part of the access service to the IXC. Each Party will bill its own access services rates to the IXC. Pursuant to the procedures described in Multiple Exchange Carrier Access Billing (“MECAB”) document SR-BDS-000983, Issue 5, June 1994, the Parties shall provide to each other the Switched Access Detail Usage Data and Switched Access Summary Usage Data to bill for jointly provided service, such as Telco’s Switched Access Service or Carrier’s access service. The Parties shall provide this data to each other at no charge. If the procedures in the MECAB document are amended or modified, the Parties shall implement such amended or modified procedures within a reasonable period of time. Each Party shall provide the other Party the billing name, billing address, and carrier identification code (“CIC”) of the IXCs that may utilize any portion of that Party's network in order to comply with the Meet Point Billing (“MPB”) Notification process as outlined in the MECAB document. 11.2.5 THIS SECTION 11.2.5 APPLIES ONLY IN ILLINOIS, INDIANA, MICHIGAN, OHIO AND WISCONSIN. This arrangement requires a separate Trunk Group employing a Type 2 interface. When Telco is not able to record Carrier-originated traffic to an IXC, Carrier will also provide to Telco, using industry standard data record formats, recordings of all calls (both completed calls and attempts) to IXCs from Carrier's network using Trunks employing a Type 2A interface.
Appears in 5 contracts
Samples: Cellular/PCS Interconnection Agreement, Cellular/PCS Interconnection Agreement, Interconnection Agreement
IXC Traffic. 11.2.1 Carrier may send traffic to IXCs via Type 2A interface utilizing FGD protocol.
11.2.2 If traffic is handed from Telco directly to an IXC, from Carrier directly to an IXC, from Carrier to an IXC via Trunks with Type 2A interfaces, or from an IXC directly to Telco, access charges shall not apply to Carrier.
11.2.3 When used in the Carrier to Telco direction, Trunks employing a Type 2A interface may be provided to a Telco Tandem Switch to transport calls from Carrier's premises to an IXC's Switched Access Services Feature Group D service at the same Tandem Switch.
11.2.4 When the Parties jointly provide access service to an IXC, each Party will provide its own part of the access service to the IXC. Each Party will bill its own access services rates to the IXC. Pursuant to the procedures described in Multiple Exchange Carrier Access Billing (“MECAB”) document SR-BDS-000983BDS- 000983, Issue 5, June 1994, the Parties shall provide to each other the Switched Access Detail Usage Data and Switched Access Summary Usage Data to bill for jointly provided service, such as Telco’s Switched Access Service or Carrier’s access service. The Parties shall provide this data to each other at no charge. If the procedures in the MECAB document are amended or modified, the Parties shall implement such amended or modified procedures within a reasonable period of time. Each Party shall provide the other Party the billing name, billing address, and carrier identification code (“CIC”) of the IXCs that may utilize any portion of that Party's network in order to comply with the Meet Point Billing (“MPB”) Notification process as outlined in the MECAB document.
11.2.5 THIS SECTION 11.2.5 APPLIES ONLY IN ILLINOIS, INDIANA, MICHIGAN, OHIO AND WISCONSIN. This arrangement requires a separate Trunk Group employing a Type 2 interface. When Telco is not able to record Carrier-originated traffic to an IXC, Carrier will also provide to Telco, using industry standard data record formats, recordings of all calls (both completed calls and attempts) to IXCs from Carrier's network using Trunks employing a Type 2A interface.
Appears in 1 contract