INTERCONNECTION TRUNKING REQUIREMENTS Sample Clauses
INTERCONNECTION TRUNKING REQUIREMENTS. 3.1 Introduction
3.1.1 This Section 3 of Article V sets forth terms and conditions for Interconnection provided by CenturyLink and BendTel.
3.1.2 This Section 3 of Article V provides descriptions of the trunking requirements between BendTel and CenturyLink. All references to incoming and outgoing trunk groups are from the perspective of BendTel. The paragraphs below describe the required and optional trunk groups for local and mass calling.
3.1.3 Local trunk groups may only be used to transport traffic between the Parties’ End Users pursuant to the terms of this Article.
3.2 One Way and Two Way Trunk Groups
3.2.1 One-way trunk groups for ancillary services (e.g. mass calling) can be established between the Parties. Ancillary trunk groups will utilize Signaling System 7 (SS7) or multi-frequency (MF) signaling protocol, with SS7 signaling preferred whenever possible. The originating Party will have administrative control of one-way trunk groups.
3.2.2 The Parties agree that two-way trunk groups for local, IntraLATA and InterLATA traffic shall be established between a BendTel switch and a CenturyLink End Office switch pursuant to the terms of this Article. Trunks will utilize Signaling System 7 (SS7) or multi-frequency (MF) signaling protocol, with SS7 signaling being used whenever possible. Two-way trunking for Local Traffic will be jointly provisioned and maintained, with each Party being responsible for costs on its side of the POI. The costs associated with transporting Information Access Traffic and/or ISP-Bound Traffic to BendTel shall be the sole responsibility of BendTel. For administrative consistency BendTel will have control for the purpose of issuing Access Service Requests (ASRs) on two-way groups. Either Party will also use ASRs to request changes in trunking. Both Parties reserve the right to issue ASRs, if so required, in the normal course of business.
3.2.3 Notwithstanding 3.2 above, the Parties recognize that certain technical and billing issues may necessitate the use of one-way trunking for an interim period. If either Party wants to provision its own one-way trunks, this must be agreed to by both Parties. The Parties will negotiate the appropriate trunk configuration, whether one-way or two-way giving consideration to relevant factors, including but not limited to, existing network configuration, administrative ease, any billing system and/or technical limitations and network efficiency. Any disagreement regarding appropriate trunk config...
INTERCONNECTION TRUNKING REQUIREMENTS. AMERITECH-ILLINOIS shall provide to CLEC Interconnection of the Parties’ facilities and equipment for the transmission and routing of Telephone Exchange Service traffic and Exchange Access traffic pursuant to the applicable Appendix ITR, which is/are attached hereto and incorporated herein by reference. Methods for Interconnection and Physical Architecture shall be as defined in the applicable Appendix NIM, which is/are attached hereto and incorporated herein by reference. AMERITECH-ILLINOIS shall provide to CLEC certain trunk groups (Meet Point Trunks) under certain parameters pursuant to the applicable Appendix ITR, which is/are attached hereto and incorporated herein by reference. The applicable Appendix 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 applicable Appendix ITR, which is/are attached hereto and incorporated herein by reference. One or more of the ILECs making up SBC have deployed a set of AIN features and functionalities unique to the particular ILEC(s). As such, the AIN network architecture, methods of access and manner of provisioning are specific to that ILEC or those ILECs. Accordingly, any request for AIN access pursuant to this Agreement must be reviewed for technical feasibility, with all rates, terms and conditions related to such request to be determined on an individual case basis and to be negotiated between the Parties. Upon request by CLEC, and where technically feasible, AMERITECH-ILLINOIS will provide CLEC with access to Ameritech-Illinois’ Advanced Intelligent Network (AIN) platform, AIN Service Creation Environment (SCE) and AIN Service Management System (SMS) based upon ILEC-specific rates, terms, conditions and means of access to be negotiated by the Parties pursuant to Section 252 of the Act, and incorporated into this Agreement by Appendix or amendment, as applicable, subject to approval by the appropriate state Commission.
INTERCONNECTION TRUNKING REQUIREMENTS. 74.1. This Section sets forth terms and conditions for Interconnection provided by CenturyLink and **CLEC, and provides descriptions of the trunking requirements between **CLEC and CenturyLink. All references to incoming and outgoing trunk groups are from the perspective of **CLEC. The paragraphs below describe the required and optional trunk groups for local and mass calling.
74.2. Local trunk groups may only be used to transport traffic between the Parties’ End Users pursuant to the terms of this Article. A Party will not originate any Local Traffic to the other Party except via the trunk group established for the exchange of Local Traffic.
74.3. One Way and Two Way Trunk Groups 74.3.1. One-way trunk groups for ancillary services (e.g. mass calling) can be established between the Parties. Ancillary trunk groups will utilize Signaling System 7 (SS7) signaling protocol. Multi-frequency (MF) signaling protocol may only be used where **CLEC can demonstrate that it is not technically feasible to use SS7 or where CenturyLink otherwise agrees to use MF. The originating Party will have administrative control of one-way trunk groups.
INTERCONNECTION TRUNKING REQUIREMENTS. Each Party is financially responsible for transport on its side of each POI. If CLEC chooses to lease the facility from each POI to CLEC's network from CenturyLink and the facility is within CenturyLink's serving territory, CLEC will lease the facility from CenturyLink as defined in Section 2 of this Amendment. Nothing herein shall be read to require CLEC to immediately obtain additional POIs. However, CLEC agrees that it will continue to comply with the terms of the Agreement, including but not limited to the requirements to establish additional POIs based on volume thresholds in existing Interconnection Agreements. Network Interconnection Methods for Direct Interconnection
INTERCONNECTION TRUNKING REQUIREMENTS. 1.3.1. The Parties agree to initially use two-way trunks when appropriate and available for a given trunk group.
1.3.2. The Parties shall initially reciprocally terminate Local Traffic and IntraLATA/InterLATA toll calls originating on the other Party’s network as follows:
1.3.2.1. The Parties shall make available to each other two-way trunks for the reciprocal exchange of combined Local Traffic, and non-equal access IntraLATA toll traffic. Neither Party is obligated under this Agreement to order reciprocal trunks or build facilities in the establishment of interconnection arrangements for the delivery of Internet traffic. The Party serving the Internet service provider shall order trunks or facilities from the appropriate tariff of the other Party for such purposes and will be obligated to pay the full cost of such facility.
1.3.2.2. SBCT is solely responsible for the facilities that carry OS/DA, 911, mass calling and Meet-Point trunk groups.
1.3.2.3. Separate two-way trunks will be made available for the exchange of equal-access InterLATA or IntraLATA interexchange traffic that transits Sprint’s network.
1.3.2.4. Separate trunks will be utilized for connecting SBCT’s switch to each 911/E911 tandem or equivalent.
1.3.2.5. Separate trunks will be utilized for connecting SBCT’s switch to Sprint’s Choke tandem and Operator Services/Directory Assistance tandem, where available.
1.3.2.6. SBCT may choose to use the same physical facilities to provision all categories of traffic. Such use will not be for the purpose of avoiding access charges associated with InterLATA and IntraLATA traffic originated by or terminated to an End User who is not a SBCT local exchange service End User.
1.3.2.7. Separate trunk groups will be utilized for connecting SBCT’s switch to Sprint’s Operator Service center for operator-assisted busy line interrupt/verify.
1.3.2.8. Inward operator-assisted busy line interrupt/verify traffic may be routed between the two Parties via a separate dedicated trunk group.
1.3.2.9. Telcordia nomenclature convention(s) will be employed.
1.3.2.10. When end office functionality is provided in a remote end office of a host/remote configuration, the interconnection for that remote end office will be provided at the host switch.
INTERCONNECTION TRUNKING REQUIREMENTS. 58.1. This Section sets forth terms and conditions for Interconnection provided by CenturyLink and QCC.
58.2. This Section provides descriptions of the trunking requirements between QCC and CenturyLink. The paragraphs below describe the required and optional trunk groups for local and mass calling.
58.3. Local trunk groups may only be used to transport traffic between the Parties’ End Users pursuant to the terms of this Article. A Party will not originate any Local Traffic to the other Party except via the trunk group established for the exchange of Local Traffic.
58.4. One Way and Two Way Trunk Groups a. One-way trunk groups for ancillary services (e.g., mass calling) can be established between the Parties. Ancillary trunk groups will utilize Signaling System 7 (SS7) signaling protocol. Multi-frequency (MF) signaling protocol may only be used where QCC can demonstrate that it is not technically feasible to use SS7 or where CenturyLink otherwise agrees to use MF. The originating Party will have administrative control of one-way trunk groups.
INTERCONNECTION TRUNKING REQUIREMENTS. 3.1 Introduction
3.1.1 This Section 3 of Article IV sets forth terms and conditions for Interconnection provided by CenturyLink and ELTOPIA.
3.1.2 This Section 3 of Article IV provides descriptions of the trunking requirements between ELTOPIA and CenturyLink. All references to incoming and outgoing trunk groups are from the perspective of
INTERCONNECTION TRUNKING REQUIREMENTS. 58.1. Introduction
58.1.1. This Section of Article IV sets forth terms and conditions for Interconnection provided by CenturyLink and US Xchange.
58.1.2. This Section of Article IV provides descriptions of the trunking requirements between US Xchange and CenturyLink. All references to incoming and outgoing trunk groups are from the perspective of US Xchange. The paragraphs below describe the required and optional trunk groups for local and mass calling.
58.1.3. Local trunk groups may only be used to transport traffic between the Parties’ End Users pursuant to the terms of this Article. A Party will not originate any Local Traffic to the other Party except via the trunk group established for the exchange of Local Traffic.
INTERCONNECTION TRUNKING REQUIREMENTS