Trunk Servicing. Orders between the Parties to establish, add, change or disconnect trunks shall be processed by use of an ASR, or another industry standard eventually adopted to replace the ASR for trunk ordering.
Trunk Servicing. 60.6.1 Orders between the Parties to establish, add, change or disconnect trunks shall be processed by using an ASR. CLEC will have administrative control for the purpose of issuing ASR’s on both two-way and one-way trunk groups. Parties will jointly manage the capacity of Local Interconnection Trunk Groups.
60.6.2 Should CLEC request trunking from CenturyLink in excess of the industry traffic engineering design blocking standard set forth in Section 59.2.3. CenturyLink is not obligated to provide such trunking unless XXXX agrees in writing to pay for the excess trunking on the CenturyLink side of the POI.
60.6.3 Utilization shall be defined as ‘trunks required’ as a percentage of trunks in service. Trunks required shall be determined using design utilization criteria stated in Section 60.6.4.
Trunk Servicing. 4.6.1 Both Parties will jointly manage the capacity of Local Only, Local Interconnection, Third Party and Meet Point Trunk Groups. Either Party may send a Trunk Group Service Request (TGSR) to the other Party to trigger changes to the Local Only, Local Interconnection, Third Party and Meet Point Trunk Groups based on capacity assessment. The TGSR is a standard industry support interface developed by the OBF of the Carrier Liaison Committee of the Alliance for Telecommunications Solutions (ATIS) organization. TELCORDIA TECHNOLOGIES Special Report STS000316 describes the format and use of the TGSR. Contact TELCORDIA TECHNOLOGIES at 0-000-000-0000 regarding the documentation availability and use of this form.
4.6.2 Orders greater than eight (8) DS1s shall be submitted as a project as described in Section 4.7 below.
Trunk Servicing.
7.1 Orders between the Parties to establish, add, change or disconnect trunks shall be processed by use of an Access Service Request ("ASR") or another industry standard method subsequently adopted by the Parties to replace the ASR for local trunk ordering.
7.2 The Parties shall jointly manage the capacity of local Interconnection Trunk Groups. Either Party may send the other Party an ASR to initiate changes to the Local Interconnection Trunk Groups that the ordering Party desires based on the ordering Party's capacity assessment.
7.3 Orders that comprise a major project (i.e., new switch deployment) shall be submitted in a timely fashion, and their implementation shall be jointly planned and coordinated.
7.4 Each Party shall be responsible for engineering its networks on its side of the IP.
7.5 Each Party will provide trained personnel with adequate and compatible test equipment to work with each other's technicians.
7.6 The Parties will coordinate and schedule testing activities of their own personnel, and others as applicable, to ensure its interconnection trunks/trunk groups are installed per the interconnection order, meet agreed-upon acceptance test requirements, and are placed in service by the due date.
7.7 Each Party will perform sectionalization to determine if a trouble is located in its facility or its portion of the interconnection trunks prior to referring the trouble to each other.
7.8 The Parties will advise each other's Control Office if there is an equipment failure, which may affect the interconnection trunks.
7.9 Each Party will provide to each other test-line numbers and access to test lines.
7.10 The Parties will cooperatively plan and implement coordinated repair procedures for the local interconnection trunks to ensure trouble reports are resolved in a timely and appropriate manner.
7.11 A blocking standard of one-half of one percent (.005) during the average busy hour for final trunk groups between an SPRINT end office and ALLTEL access tandem carrying meet point traffic shall be maintained. All other final trunk groups are to be engineered with a blocking standard of one percent (.01). ALLTEL will engineer all interconnection trunks between the Parties to a 6 db of digital pad configuration.
Trunk Servicing. Orders between the Parties to establish, add, change or disconnect trunks shall be processed by use of an ASR, RASR or other industry standard format as specified by CenturyLink for trunk ordering.
Trunk Servicing. 3.7.1 Orders between the Parties to establish, add, change or disconnect trunks shall be processed by using an Access Service Request (ASR). Charter will have administrative control for the purpose of issuing ASR’s on two-way trunk groups. Where one-way trunks are used (as discussed in Section 3.2 of this Article), CenturyTel will issue ASRs for trunk groups for traffic that originates from CenturyTel and terminates to Charter. The Parties agree that neither Party shall alter trunk sizing without first conferring with the other Party.
3.7.2 Both Parties will jointly manage the capacity of Local Interconnection Trunk Groups. Either Party may send an ASR to the other Party to trigger changes to the Local Interconnection Trunk Groups based on capacity assessment.
Trunk Servicing. 7.1 Orders between the Parties to establish, add, change or disconnect trunks shall be processed by use of an Access Service Request ("ASR") or another industry standard method subsequently adopted by the Parties to replace the ASR for local trunk ordering.
7.2 The Parties shall jointly manage the capacity of local Interconnection Trunk Groups. Either Party may send the other Party an ASR to initiate changes to the Local Interconnection Trunk Groups that the ordering Party desires based on the ordering Party's capacity assessment.
7.3 Orders that comprise a major project (i.e., new switch deployment, multiple office trunk group installation, or network reconfiguration) shall be submitted in a timely fashion, and their implementation shall be jointly planned and coordinated.
7.4 Each Party shall be responsible for engineering its networks on its side of the IP.
7.5 Each Party will provide trained personnel with adequate and compatible test equipment to work with each other's technicians.
7.6 The Parties will coordinate and schedule testing activities of their own personnel, and others as applicable, to ensure its interconnection trunks/trunk groups are installed per the interconnection order, meet agreed-upon acceptance test requirements, and are placed in service by the due date.
7.7 Each Party will perform sectionalization to determine if a trouble is located in its facility or its portion of the interconnection trunks prior to referring the trouble to each other.
7.8 The Parties will advise each other's Control Office if there is an equipment failure, which may affect the interconnection trunks.
7.9 Provided information is not available through the LERG, each Party will provide to each other test-line numbers and access to test lines.
7.10 The Parties will cooperatively plan and implement coordinated repair procedures for the local interconnection trunks to ensure trouble reports are resolved in a timely and appropriate manner.
7.11 A blocking standard of one-half of one percent (.005) during the average busy hour for final trunk groups between a Onvoy end office and Windstream access tandem carrying meet point traffic shall be maintained. All other final trunk groups are to be engineered with a blocking standard of one percent (.01). Windstream will engineer all interconnection trunks between the Parties to a 6 db of digital pad configuration. Attachment 5: INTENTIONALLY LEFT BLANK Attachment 11: INTENTIONALLY LEFT BLANK
Trunk Servicing. 3.5.5.1 The Parties will jointly manage the capacity of Interconnection Trunk Groups. A Trunk Group Service Request (“TGSR”) will be sent by AT&T-21STATE to notify WSP to establish or make modifications to existing Trunk Groups. WSP will issue an ASR or WSR, as applicable, to AT&T- 21STATE’s Wireless Access Service Center, to begin the provisioning process as required below:
3.5.5.1.1 Within ten (10) Business Days after receipt of the TGSR or other notification; or
3.5.5.1.2 At any time as a result of WSP’s own capacity management assessment.
3.5.5.2 Upon review of the TGSR, if a Party does not agree with the resizing, of the Interconnection Truck Groups the Parties will schedule a joint planning discussion to take place and conclude within twenty (20) Business Days of WSP’s receipt of the TGSR. At the joint planning discussion, the Parties will resolve and mutually agree to the disposition of the TGSR.
3.5.5.3 If the Parties cannot agree on the resizing of the Interconnection Trunk Groups at the joint planning discussion, then either Party may invoke the dispute resolution provisions of this Agreement. Further, if AT&T-21STATE does not receive an ASR or WSR, as applicable, from WSP, or if WSP does not respond to the TGSR by scheduling a discussion with the other Party within the twenty (20) Business Day period, AT&T-21STATE will attempt to contact WSP to schedule a joint planning discussion. If WSP will not agree to meet within an additional five (5) Business Days and present adequate reason for keeping Trunks operational, AT&T-21STATE will issue an ASR or WSR, as applicable, to resize the Interconnection Trunks and Facilities.
Trunk Servicing. 56.5.1 Orders between the Parties to establish, add, change or disconnect trunks shall be processed by using an Access Service Request (ASR). Carrier will have administrative control for the purpose of issuing ASR’s on both two-way and one-way trunk groups. Parties will jointly manage the capacity of Local Interconnection Trunk Groups.
Trunk Servicing. 8.1 Orders between the Parties to establish, add, change or disconnect trunks shall be processed by using an Access Service Request (ASR). TCAL will have administrative control for the purpose of issuing ASR’s on two-way trunk groups. Where one-way trunks are used (as discussed in section 3.3), TDS TELECOM will issue ASRs for trunk groups for traffic that originates from TDS TELECOM and terminates to TCAL. The Parties agree that neither Party shall alter trunk sizing without first conferring with the other Party.
8.2 Both Parties will jointly manage the capacity of Local Interconnection Trunk Groups. Either Party may send a Trunk Group Service Request (TGSR) to the other Party to trigger changes to the Local Interconnection Trunk Groups based on capacity assessment. The TGSR is a standard industry support interface developed by the Ordering and Billing Forum of the Carrier Liaison Committee of the Alliance for Telecommunications Solutions (ATIS) organization. TELECORDIA TECHNOLOGIES Special Report STS000316 describes the format and use of the TGSR. The forms can be obtained from xxx.xxxx.xxx/xxxx/xxx/xxx/xxxxxxxx.xxx.
8.3 In A Blocking Situation:
8.3.1 In a blocking final situation, a TGSR will be issued by TDS TELECOM when additional capacity is required to reduce measured blocking to objective design blocking levels based upon analysis of trunk group data. Either Party upon receipt of a TGSR in a blocking situation will issue an ASR to the other Party within three (3) business days after receipt of the TGSR, and upon review and in response to the TGSR received. TCAL will note “Service Affecting” on the ASR.
