Common use of Trunk Servicing Clause in Contracts

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. 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, (i.e., no less than 120 days), 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 Network Operations Control Office (NOC) if there is an equipment failure, which may affect the interconnection trunks. 7.9 Provided information is not available through the LERG, each 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 an TCG’s end office and Windstream ALLTEL’s 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 ALLTEL will engineer all interconnection trunks between the Parties to a 6 6.0 db of digital pad configuration. Attachment 5: INTENTIONALLY LEFT BLANK Attachment 11: INTENTIONALLY LEFT BLANK.

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-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 an Peerless 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. 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.. SouthEast Telephone, Inc. DATE 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 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 an SouthEast 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 BLANKSouthEast Telephone, Inc. DATE SouthEast Telephone, Inc. DATE Page 47

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, (i.e., no less than 120 days), 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 Network Operations Control Office (NOC) if there is an equipment failure, which may affect the interconnection trunks. 7.9 Provided information is not available through the LERG, each 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 an MCIW’s end office and Windstream ALLTEL’s 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 ALLTEL will engineer all interconnection trunks between the Parties to a 6 6.0 db of digital pad configuration. Attachment 5: INTENTIONALLY LEFT BLANK Attachment 11: INTENTIONALLY LEFT BLANK.

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, (i.e., no less than 120 days), 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 Network Operations Control Office (NOC) if there is an equipment failure, which may affect the interconnection trunks. 7.9 Provided information is not available through the LERG, each 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 an AT&T’s end office and Windstream ALLTEL’s 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 ALLTEL will engineer all interconnection trunks between the Parties to a 6 6.0 db of digital pad configuration. Attachment 5: INTENTIONALLY LEFT BLANK Attachment 11: INTENTIONALLY LEFT BLANK.

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-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 Comcast end office and Windstream access tandem carrying meet point traffic shall be maintained. All other final trunk groups are to be engineered with a minimum 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. 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, (i.e., no less than 120 days), 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 Network Operations Control Office (NOC) if there is an equipment failure, which may affect the interconnection trunks. 7.9 Provided information is not available through the LERG, each 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 an MCIm’s end office and Windstream ALLTEL’s 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 ALLTEL will engineer all interconnection trunks between the Parties to a 6 6.0 db of digital pad configuration. Attachment 5: INTENTIONALLY LEFT BLANK Attachment 11: INTENTIONALLY LEFT BLANK.

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 an Broadview 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.