Trunk Groups. 65.5.1 The Parties shall provide all SS7 signaling information pursuant to Signaling Parameters Section 65.2. Where required, network signaling information such as transit network selection (TNS) parameter, Originating Line Information Parameter (OLIP) and CIC/OZZ ANI information digits (II) (non-SS7 environment) will be provided by CLEC wherever such information is needed for call routing or billing. The Parties will follow all Network Operations Forum (NOF) adopted standards and all OBF adopted standards pertaining to TNS and CIC/OZZ codes.
65.5.2 CLEC and CenturyLink shall, where applicable, make reciprocally available, the required trunk groups to handle different traffic types.
a. Any Local Traffic routed over Switched Access Service trunks will be billed the intrastate terminating access rate. Neither Party shall route Switched Access Service traffic over Local Interconnection Trunks.
b. Each Party shall only deliver traffic over the Local Interconnection Trunk Groups to the other Party’s Tandem or End Office for those NXX Codes served by that Tandem or End Office as applicable in accordance with the LERG.
Trunk Groups. BellSouth and Supra Telecommunications and Information Systems, Inc. shall establish trunk groups between interconnecting facilities. Trunks may be either one-way or two-way. Two-way trunking may be provided by BellSouth consistent with BellSouth engineering specifications, with the costs of provisioning such trunking being shared equally by both parties. Local and intraLATA traffic only may be routed over the same one-way trunk group. Requests for alternative trunking arrangements may require submission of a bona fide request via the Bona Fide Request Process set forth in Attachment 9.
Trunk Groups. 5.1 The following trunk groups shall be used to exchange local traffic between TCAL and TDS TELECOM.
5.2 Local Interconnection Trunk Group(s) in Each Exchange
Trunk Groups. 4.5.1 The following trunk groups shall used to exchange various types of traffic between CLEC and SBC-AMERITECH.
4.5.1.1 Each Party shall deliver to the other Party over the Local Trunk Group(s) only such traffic that originates and terminates in the local exchange area.
4.5.2 Local and IntraLATA Interconnection Trunk Group(s) in Each LATA:
4.5.2.1 Tandem Trunking - Single Tandem LATAs
4.5.2.1.1 Where SBC-AMERITECH has a single Access Tandem in a LATA, IntraLATA Toll and Local traffic shall be combined on a single Local Interconnection Trunk group for calls destined to or from all End Offices that subtend the Tandem. This trunk group shall be one-way and will utilize Signaling System 7 (SS7) signaling.
4.5.2.2 Tandem Trunking – Multiple Tandem LATAs
4.5.2.2.1 Where SBC-AMERITECH has more than one Access Tandem in a LATA, IntraLATA Toll and Local traffic shall be combined on a single Local Interconnection Trunk Group at every SBC-AMERITECH Tandem for calls destined to or from all End Offices that subtend each Tandem. These trunk groups shall be one-way and will utilize Signaling System 7 (SS7) signaling.
Trunk Groups. 5.1 The following trunk groups shall be used to exchange local traffic between LEVEL 3 and TDS TELECOM.
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 Charter switch and a CenturyTel 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 Charter shall be the sole responsibility of Charter. For administrative consistency, Charter 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 the preceding paragraph 3.2.2 above, the Parties recognize that certain technical and billing issues may necessitate the use of one-way trunking. Either Party may provision its own one-way trunks. Regardless of whether one-way or two-way facilities are provisioned, each Party is individually responsible to provide facilities to the POI. If one- way trunking is used, CenturyTel shall only be financially responsible for deploying and maintaining one-way trunks between CenturyTel’s switch and the POI. 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 configuration shall be subject to the dispute resolution process in Section 20 of Article III.
3.2.4 Separate local trunk groups may be established based on billing, signaling, and network requirements. The following is the current list of traffic types that require separate trunk groups, unless specifically stated otherwise in this Agreement:
3.2.4.1 911/...
Trunk Groups. BellSouth and AXSYS shall establish interconnecting trunk groups betweennetworks. Trunks may be either one-way or two-way. Two-way trunking may be provided by BellSouth consistent with BellSouth engineering specifications. Local and intraLATA traffic only may be routed over the same one-way trunk group. Requests for alternative trunking arrangements may require submission of a Bona Fide Request/New Business Request via the Bona Fide Request/New Business Request Process set forth in Attachment 9.
Trunk Groups. BellSouth and ICS shall establish interconnecting trunk groups between networks. Trunks may be either one-way or two-way. Two-way trunking may be provided by BellSouth consistent with BellSouth engineering specifications. Local and intraLATA traffic only may be routed over the same one-way trunk group. Trunk installation charges, both non-recurring and recurring, assessed by either party, as well as all terms and conditions, associated with interconnecting trunk groups between BellSouth and ICS shall be as set forth in Section E.6 of the appropriate BellSouth intrastate access tariff. Requests for alternative trunking arrangements may require submission of a Bona Fide Request/New Business Request via the Bona Fide Request/New Business Request Process set forth in Attachment 9.
Trunk Groups. 4.5.1 The following trunk groups shall used to exchange various types of traffic between CLEC and SBC-AMERITECH.
4.5.1.1 Each Party shall deliver to the other Party over the Local Trunk Group(s) only such traffic that originates and terminates in the local exchange area.
4.5.2 Local and IntraLATA Interconnection Trunk Group(s) in Each LATA:
4.5.2.1 Tandem Trunking - Single Tandem LATAs
Trunk Groups. 5.1 The following trunk groups shall be used to exchange local and intraLATA toll traffic between CLEC and UNION.
5.2 The Trunk Groups identified below shall be provisioned over the facilities identified in Appendix NIM. Multiple types of Trunk Groups may be provisioned over the same facility(s). The ordering Party agrees to pay, as defined in Pricing Appendix Attachment A, the providing Party for multiplexing from DS3 to DS1 when a DS3 facility is used to aggregate between two or more POIs.
5.2.1 CLEC shall, if it desires, have different trunk groups utilize the same Interconnection and POI. For Illustrative purposes, the following architecture could exist between CLEC and UNION: Illustrative Architecture 1: • DS3 Interconnection from CLEC switch location to UNION’s Xxxxx Central Office. • DS3 to DS1 Multiplexing service at the Xxxxx Office. • Five T1’s of LOCAL Trunks over this DS3 Interconnection to the UNION Xxxxx End Office Switch (a POI) (for local calls routed between CLEC and the Union Xxxxx End Office) • Five T1’s of LOCAL Trunks over this DS3 Interconnection to the UNION End Office Switch in New Durham (a POI) (for local calls routed between CLEC and the Union Barnstead End Office) Illustrative Architecture 2: • DS1 Interconnection from CLEC switch location to UNION’s Xxxxx Host End Office via DS1 Leased Facility Interconnection and POI to deliver local traffic between the Parties. • DS1 Interconnection from CLEC switch location to UNION’s New Durham Host End Office via DS1 Leased Facility Interconnection and POI to deliver local traffic between the Parties.
5.3 Interconnection Trunk Group(s)
