Trunking Arrangements Clause Samples
A Trunking Arrangements clause defines the terms under which telecommunications lines or channels are shared or interconnected between parties, typically service providers. It outlines the technical and operational requirements for connecting networks, such as capacity, maintenance responsibilities, and cost allocation. This clause ensures that both parties have a clear understanding of how traffic will be routed and managed, thereby facilitating efficient network interoperability and minimizing disputes over usage or service quality.
Trunking Arrangements. 10.1 Upon request, AT&T ILLINOIS will provide nondiscriminatory access to its 911/E911 facilities and databases, equal in quality to that provided to itself, facilitating the provision of service to MCIm. The Parties agree to provide access to 911/E911 in a manner that is transparent to the Customer. The Parties will work together to facilitate the prompt, reliable, and efficient Interconnection of MCIm’s systems to AT&T ILLINOIS’ 911/E911 platforms, with a level of performance that will provide at least the same grade of service as that which AT&T ILLINOIS provides to itself, its Customers, subsidiaries, Affiliates or any third-party.
10.2 Subject to section 10.2.1 below (Trunking Exception), MCIm, with AT&T ILLINOIS’ cooperation shall establish dedicated trunks from MCIm’s Central Office to each AT&T ILLINOIS 911/E911 Selective Router (i.e., 911 Tandem Office) for the provision of 911/E911 services and for access to all subtending PSAPs (“911 Interconnection Trunk Groups”). MCIm may establish such Interconnection by providing its own facilities/trunks, or by leasing such facilities/trunks from a third party.
10.2.1 TRUNKING EXCEPTION The Parties agree that MCIm shall not be required to establish 911 trunking or interconnection to AT&T ILLINOIS’ 911 Selective Routers in rate centers where MCIm does not originate local (dial tone) traffic for its end user customers (“Non-Dial Tone Rate Centers”). MCIm shall identify such Non-Dial Tone Rate Centers when completing the “MCIm to AT&T Network Information Sheet” (“NIS”) and AT&T ILLINOIS specifically agrees that no other notification shall be required of MCIm. AT&T ILLINOIS shall not be required to provide 911 services for those Non-Dial Tone Rate Centers designated by MCIm on a NIS. MCIm agrees that it will not originate dial tone service for its customers in such Non-Dial Tone Rate Centers until 911 connectivity has been established pursuant to the requirements of this Agreement and Applicable Law. MCIm acknowledges that, if MCIm wishes to begin offering originating dial tone service in a Non-Dial Tone Rate Center, the establishment of 911 connectivity for these existing rate centers shall be subject to the same intervals for establishing 911 connectivity that are applicable to new rate centers. When MCIm designates a rate center as a Non-Dial Tone Rate Center, MCIm agrees to indemnify AT&T ILLINOIS, in accordance with the requirements of the General terms, for any 911 claims made by MCIm’s customers in that ...
Trunking Arrangements. 2.2.1 The Parties will interconnect one or more trunk groups for the transmission and routing of Local Traffic as set forth in Appendix A.
2.2.2 For each trunk group with a utilization level of less than sixty percent (60%) for three consecutive months, unless the Parties agree otherwise, either Party may disconnect a sufficient number of the available trunks to attain a utilization level of approximately sixty percent (60%); provided, however, the trunks will be grouped in multiples of 24 trunks for the purpose of determining utilization levels. The minimum utilization level of sixty percent (60%) is not required until trunk groups have been in service for at least six (6) months.
2.2.3 All trunks shall utilize SIP Trunking or SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available in the event a physical connection is made between the Parties.
2.2.4 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on two-way trunks to determine the need for new trunk groups and to plan any necessary changes in the number of trunks.
2.2.5 The trunk group(s) established between the Parties pursuant to the terms of this Agreement for the exchange of Local Traffic and Local Internet Traffic shall be engineered to a P.01
Trunking Arrangements. 2.2.1 The Parties will interconnect one or more trunk groups for the transmission and routing of Local Traffic as set forth in Appendix A.
2.2.2 For each trunk group with a utilization level of less than sixty percent (60%) for three consecutive months, unless the Parties agree otherwise, either Party may disconnect a sufficient number of the available trunks to attain a utilization level of approximately sixty percent (60%); provided, however, the trunks will be grouped in multiples of 24 trunks for the purpose of determining utilization levels. The minimum utilization level of sixty percent (60%) is not required until trunk groups have been in service for at least six (6) months.
2.2.3 All trunks shall utilize SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DSl facilities, where available. ILEC will provide and implement all defined and industry supported SS7 mandatory parameters as well as procedures in accordance with ANSI standards to support SS7 signaling for call setup for the interconnection trunks. To the extent ILEC provides ANSI optional parameters for its own use, ILEC shall provide the same to CLEC for CLEC’s review. ILEC shall support 64 KBPS clear channel where it provides such capability to its end users.
2.2.4 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on two-way trunks to determine the need for new trunk groups and to plan any necessary changes in the number of trunks.
2.2.5 The trunk group(s) established between the Parties pursuant to the terms of this Agreement for the exchange of Local Traffic shall be engineered to a P.01
Trunking Arrangements. 2.2.1 The Parties will interconnect one or more trunk groups for the transmission and routing of Local Traffic and Local Internet Traffic as set forth in Appendix A.
2.2.2 For each trunk group with a utilization level of less than sixty percent (60%) for three consecutive months, unless the Parties agree otherwise, either Party may disconnect a sufficient number of the available trunks to attain a utilization level of approximately sixty percent (60%); provided, however, the trunks will be grouped in multiples of 24 trunks for the purpose of determining utilization levels. The minimum utilization level of sixty percent (60%) is not required until trunk groups have been in service for at least six (6) months.
2.2.3 All trunks shall utilize SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DSl facilities, where available.
2.2.4 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on two-way trunks to determine the need for new trunk groups and to plan any necessary changes in the number of trunks.
2.2.5 The trunk group(s) established between the Parties pursuant to the terms of this Agreement for the exchange of Local Traffic and Local Internet Traffic shall be engineered to a P.01 Grade of Service. The performance standard for two-way trunk groups shall be that no such trunk group will exceed its design blocking objective for three (3) consecutive calendar traffic study months.
2.2.6 The Parties shall collaboratively determine the number of two-way trunks that are required to meet the applicable design-blocking objective for all traffic carried on each two-way trunk group. CLEC shall order two-way trunks by submitting ASRs to ILEC and any applicable third party, setting forth the number of two-way trunks to be installed and the requested installation dates within ILEC's effective standard intervals or negotiated intervals, as appropriate. LEC shall populate all applicable fields in ASRs in accordance with OBF Guidelines as in effect from time to time, or use another mutually agreed upon format.
2.2.7 Both Parties shall monitor two-way trunk groups using service results for the applicable design blocking objective. If either Party ("Observing Party") observes blocking in excess of the applicable design objective on any two-way trunk group, the Observing Party may submit an ASR or Trunk Group Service Request ("TGSR") to the Other Party requesting that the trunk group be ...
Trunking Arrangements. 2.2.1 The Parties will interconnect one or more trunk groups for the transmission and routing of Local Traffic as set forth in Appendix A.
Trunking Arrangements. 2.2.1 Each Party will identify its Carrier Identification Code (“CIC”), a four-digit numeric obtained from Bellcore, to the other Party when ordering a trunk group.
2.2.2 Unless otherwise agreed to by both Parties, each Party will send a Carrier Identification Code and outpulse ten (10) digits to the other Party.
2.2.3 Each Party will use commercially reasonable efforts to monitor its trunk groups and to augment those groups using generally accepted trunk engineering standards so as to not exceed blocking objectives. Each Party agrees to use modular trunk engineering techniques where practical.
2.2.4 Each Party will maintain and provide the other Party signaling information necessary for the routing and delivery of traffic exchanged between them.