Common use of Loop Testing/Trouble Reporting Clause in Contracts

Loop Testing/Trouble Reporting. 2.1.6.1 Ruddata will be responsible for testing and isolating troubles on the Loops. Ruddata must test and isolate trouble to the BellSouth portion of a designed/non- designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Ruddata will be required to provide the results of the Ruddata test which indicate a problem on the BellSouth provided Loop.

Loop Testing/Trouble Reporting. 2.1.6.1 Ruddata NOW will be responsible for testing and isolating troubles on the Loops. Ruddata NOW must test and isolate trouble to the BellSouth portion of a designed/non- non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Ruddata NOW will be required to provide the results of the Ruddata test NOW tests which indicate a problem on the BellSouth provided Loop.

Loop Testing/Trouble Reporting. 2.1.6.1 Ruddata ACN will be responsible for testing and isolating troubles on the Loops. Ruddata ACN must test and isolate trouble to the BellSouth portion of a designed/non- non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Ruddata ACN will be required to provide the results of the Ruddata ACN test which indicate a problem on the BellSouth provided Loop.

Loop Testing/Trouble Reporting. 2.1.6.1 Ruddata Knology will be responsible for testing and isolating troubles on the Loops. Ruddata Knology must test and isolate trouble to the BellSouth portion of a designed/non- non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Ruddata Knology will be required to provide the results of the Ruddata Knology test which indicate a problem on the BellSouth provided Loop.

Loop Testing/Trouble Reporting. 2.1.6.1 Ruddata Charter will be responsible for testing and isolating troubles on the Loops. Ruddata Charter must test and isolate trouble to the BellSouth portion of a designed/non- non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Ruddata Charter will be required to provide the results of the Ruddata Charter test which indicate a problem on the BellSouth provided Loop.

Loop Testing/Trouble Reporting. 2.1.6.1 Ruddata 2.1.8.1 NOW will be responsible for testing and isolating troubles on the Loops. Ruddata NOW must test and isolate trouble to the BellSouth portion of a designed/non- non-designed unbundled Loop loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at At the time of the trouble report, Ruddata NOW will be required to provide the results of the Ruddata NOW test which indicate a problem on the BellSouth provided Looploop.

Loop Testing/Trouble Reporting. 2.1.6.1 Ruddata 2.1.8.1 Knology will be responsible for testing and isolating troubles on the Loops. Ruddata Knology must test and isolate trouble to the BellSouth portion of a designed/non- designed unbundled Loop loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at At the time of the trouble report, Ruddata Knology will be required to provide the results of the Ruddata Knology test which indicate a problem on the BellSouth provided Looploop.

Loop Testing/Trouble Reporting. 2.1.6.1 Ruddata 2.1.8.1 eXpeTel will be responsible for testing and isolating troubles on the Loops. Ruddata eXpeTel must test and isolate trouble to the BellSouth portion of a designed/non- designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at At the time of the trouble report, Ruddata eXpeTel will be required to provide the results of the Ruddata eXpeTel test which indicate a problem on the BellSouth provided Loop.

Loop Testing/Trouble Reporting. 2.1.6.1 Ruddata ONS will be responsible for testing and isolating troubles on the Loops. Ruddata ONS must test and isolate trouble to the BellSouth portion of a designed/non- non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Ruddata ONS will be required to provide the results of the Ruddata test ONS tests which indicate a problem on the BellSouth provided Loop.

Loop Testing/Trouble Reporting. 2.1.6.1 Ruddata ONS will be responsible for testing and isolating troubles on the Loops. Ruddata ONS must test and isolate trouble to the BellSouth portion of a designed/non- non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Ruddata ONS will be required to provide the results of the Ruddata ONS test which indicate a problem on the BellSouth provided Loop.

Loop Testing/Trouble Reporting. 2.1.6.1 Ruddata Victory will be responsible for testing and isolating troubles on the Loops. Ruddata Victory must test and isolate trouble to the BellSouth portion of a designed/non- non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Ruddata Victory will be required to provide the results of the Ruddata test Victory tests which indicate a problem on the BellSouth provided Loop.

Loop Testing/Trouble Reporting. 2.1.6.1 Ruddata 2.1.8.1 Xxx.Xxx will be responsible for testing and isolating troubles on the Loops. Ruddata Xxx.Xxx must test and isolate trouble to the BellSouth portion of a designed/non- designed unbundled Loop loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at At the time of the trouble report, Ruddata Xxx.Xxx will be required to provide the results of the Ruddata Xxx.Xxx test which indicate a problem on the BellSouth provided Looploop.

Loop Testing/Trouble Reporting. 2.1.6.1 Ruddata 2.1.8.1 ALTICOMM will be responsible for testing and isolating troubles on the Loops. Ruddata ALTICOMM must test and isolate trouble to the BellSouth portion of a designed/non- non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at At the time of the trouble report, Ruddata ALTICOMM will be required to provide the results of the Ruddata ALTICOMM test which indicate a problem on the BellSouth provided Loop.

Loop Testing/Trouble Reporting. 2.1.6.1 Ruddata Conextel will be responsible for testing and isolating troubles on the Loops. Ruddata Conextel must test and isolate trouble to the BellSouth portion of a designed/non- designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Ruddata Conextel will be required to provide the results of the Ruddata Conextel test which indicate a problem on the BellSouth provided Loop.

Loop Testing/Trouble Reporting. 2.1.6.1 Ruddata Xxxx will be responsible for testing and isolating troubles on the Loops. Ruddata Xxxx must test and isolate trouble to the BellSouth portion of a designed/non- non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Ruddata Xxxx will be required to provide the results of the Ruddata Xxxx test which indicate a problem on the BellSouth provided Loop.

Loop Testing/Trouble Reporting. 2.1.6.1 Ruddata Think 12 will be responsible for testing and isolating troubles on the Loops. Ruddata Think 12 must test and isolate trouble to the BellSouth portion of a designed/non- designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Ruddata Think 12 will be required to provide the results of the Ruddata Think 12 test which indicate a problem on the BellSouth provided Loop.