Common use of Loop Testing/Trouble Reporting Clause in Contracts

Loop Testing/Trouble Reporting. 2.1.6.1 PLI will be responsible for testing and isolating troubles on the Loops. PLI 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, PLI will be required to provide the results of the PLI tests which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once PLI has isolated a trouble to the BellSouth provided Loop, and has issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If PLI reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge PLI for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the End User’s location more than once due to incorrect or incomplete information provided by PLI (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx PLI for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

Loop Testing/Trouble Reporting. 2.1.6.1 PLI Covista will be responsible for testing and isolating troubles on the Loops. PLI Covista 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, PLI Covista will be required to provide the results of the PLI tests Covista test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once PLI Covista has isolated a trouble to the BellSouth provided Loop, and has had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If PLI Covista reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge PLI Covista for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the End Userend-user’s location more than once due to incorrect or incomplete information provided by PLI Covista (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx PLI Covista for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

Loop Testing/Trouble Reporting. 2.1.6.1 PLI Hotline will be responsible for testing and isolating troubles on the Loops. PLI Hotline 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, PLI Hotline will be required to provide the results of the PLI tests Hotline test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once PLI Hotline has isolated a trouble to the BellSouth provided Loop, and has had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If PLI Hotline reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge PLI Hotline for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the End Userend-user’s location more than once due to incorrect or incomplete information provided by PLI Hotline (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx PLI Hotline for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

Loop Testing/Trouble Reporting. 2.1.6.1 PLI Xxxx will be responsible for testing and isolating troubles on the Loops. PLI Xxxx 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, PLI Xxxx will be required to provide the results of the PLI tests Xxxx test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once PLI Xxxx has isolated a trouble to the BellSouth provided Loop, and has had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If PLI Xxxx reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge PLI Xxxx for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the End Userend-user’s location more than once due to incorrect or incomplete information provided by PLI Xxxx (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx PLI Xxxx for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

Loop Testing/Trouble Reporting. 2.1.6.1 PLI ACN will be responsible for testing and isolating troubles on the Loops. PLI ACN 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, PLI ACN will be required to provide the results of the PLI tests ACN test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once PLI ACN has isolated a trouble to the BellSouth provided Loop, and has had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If PLI ACN reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge PLI ACN for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the End Userend-user’s location more than once due to incorrect or incomplete information provided by PLI ACN (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx PLI ACN for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

Loop Testing/Trouble Reporting. 2.1.6.1 PLI FPB will be responsible for testing and isolating troubles on the Loops. PLI FPB 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, PLI FPB will be required to provide the results of the PLI FPB tests which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once PLI FPB has isolated a trouble to the BellSouth provided Loop, and has issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If PLI FPB reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge PLI FPB for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the End User’s location more than once due to incorrect or incomplete information provided by PLI FPB (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx PLI FPB for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

Loop Testing/Trouble Reporting. 2.1.6.1 PLI BAK will be responsible for testing and isolating troubles on the Loops. PLI BAK 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 XxxxXxxxx at the time of the trouble report, PLI BAK will be required to provide the results of the PLI tests BAK test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once PLI BAK has isolated a trouble to the BellSouth provided Loop, and has had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If PLI BAK reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge PLI BAK for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the End Userend-user’s location more than once due to incorrect or incomplete information provided by PLI BAK (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx PLI XXX for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

Loop Testing/Trouble Reporting. 2.1.6.1 PLI Victory will be responsible for testing and isolating troubles on the Loops. PLI Victory 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, PLI Victory will be required to provide the results of the PLI Victory tests which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once PLI Victory has isolated a trouble to the BellSouth provided Loop, and has issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If PLI Victory reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge PLI Victory for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the End User’s location more than once due to incorrect or incomplete information provided by PLI Victory (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx PLI Victory for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

Loop Testing/Trouble Reporting. 2.1.6.1 PLI JCM will be responsible for testing and isolating troubles on the Loops. PLI JCM 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, PLI JCM will be required to provide the results of the PLI tests JCM test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once PLI JCM has isolated a trouble to the BellSouth provided Loop, and has had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If PLI JCM reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge PLI JCM for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the End Userend-user’s location more than once due to incorrect or incomplete information provided by PLI JCM (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx PLI JCM for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

Loop Testing/Trouble Reporting. 2.1.6.1 PLI COMTECH21 will be responsible for testing and isolating troubles on the Loops. PLI COMTECH21 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, PLI COMTECH21 will be required to provide the results of the PLI tests COMTECH21 test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once PLI COMTECH21 has isolated a trouble to the BellSouth provided Loop, and has had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If PLI COMTECH21 reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge PLI COMTECH21 for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the End Userend-user’s location more than once due to incorrect or incomplete information provided by PLI COMTECH21 (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx PLI COMTECH21 for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

Loop Testing/Trouble Reporting. 2.1.6.1 PLI 2.1.8.1 DTM will be responsible for testing and isolating troubles on the Loops. PLI DTM 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, PLI DTM will be required to provide the results of the PLI tests DTM test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 2.1.8.2 Once PLI DTM has isolated a trouble to the BellSouth provided Loop, and has had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Usersend users. 2.1.6.3 2.1.8.3 If PLI DTM reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge PLI DTM for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 2.1.8.4 In the event BellSouth must dispatch to the End Userend-user’s location more than once due to incorrect or incomplete information provided by PLI DTM (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx PLI bill DTM for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

Loop Testing/Trouble Reporting. 2.1.6.1 PLI ICG will be responsible for testing and isolating troubles on the Loops. PLI ICG 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, PLI ICG will be required to provide the results of the PLI tests ICG test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once PLI ICG has isolated a trouble to the BellSouth provided Loop, and has had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If PLI ICG reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge PLI ICG for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the End Userend-user’s location more than once due to incorrect or incomplete information provided by PLI ICG (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx PLI ICG for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

Loop Testing/Trouble Reporting. 2.1.6.1 PLI Think 12 will be responsible for testing and isolating troubles on the Loops. PLI Think 12 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, PLI Think 12 will be required to provide the results of the PLI tests Think 12 test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once PLI Think 12 has isolated a trouble to the BellSouth provided Loop, and has had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If PLI Think 12 reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge PLI Think 12 for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the End Userend-user’s location more than once due to incorrect or incomplete information provided by PLI Think 12 (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx PLI Think 12 for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

Loop Testing/Trouble Reporting. 2.1.6.1 PLI Vertex will be responsible for testing and isolating troubles on the Loops. PLI Vertex 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 XxxxXxxxx at the time of the trouble report, PLI Vertex will be required to provide the results of the PLI tests Vertex test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once PLI Vertex has isolated a trouble to the BellSouth provided Loop, and has had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If PLI Vertex reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge PLI Vertex for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the End Userend-user’s location more than once due to incorrect or incomplete information provided by PLI Vertex (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx PLI bill Vertex for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

Loop Testing/Trouble Reporting. 2.1.6.1 PLI Freedom will be responsible for testing and isolating troubles on the Loops. PLI Freedom 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 Attachment 2 Page 8 report, PLI Freedom will be required to provide the results of the PLI tests Freedom test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once PLI Freedom has isolated a trouble to the BellSouth provided Loop, and has had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If PLI Freedom reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge PLI Freedom for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the End Userend-user’s location more than once due to incorrect or incomplete information provided by PLI Freedom (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx PLI Freedom for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

Loop Testing/Trouble Reporting. 2.1.6.1 PLI ONS will be responsible for testing and isolating troubles on the Loops. PLI ONS 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, PLI ONS will be required to provide the results of the PLI ONS tests which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once PLI ONS has isolated a trouble to the BellSouth provided Loop, and has issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If PLI ONS reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge PLI ONS for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the End User’s location more than once due to incorrect or incomplete information provided by PLI ONS (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx PLI ONS for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

Loop Testing/Trouble Reporting. 2.1.6.1 PLI Charter will be responsible for testing and isolating troubles on the Loops. PLI Charter 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, PLI Charter will be required to provide the results of the PLI tests Charter test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once PLI Charter has isolated a trouble to the BellSouth provided Loop, and has had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If PLI Charter reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge PLI Charter for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the End User’s location more than once due to incorrect or incomplete information provided by PLI Charter (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx PLI bill Charter for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

Loop Testing/Trouble Reporting. 2.1.6.1 PLI EPICUS will be responsible for testing and isolating troubles on the Loops. PLI EPICUS 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, PLI EPICUS will be required to provide the results of the PLI tests EPICUS test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once PLI EPICUS has isolated a trouble to the BellSouth provided Loop, and has had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If PLI EPICUS reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge PLI EPICUS for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the End Userend-user’s location more than once due to incorrect or incomplete information provided by PLI EPICUS (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx PLI bill EPICUS for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

Loop Testing/Trouble Reporting. 2.1.6.1 PLI ONS will be responsible for testing and isolating troubles on the Loops. PLI ONS 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, PLI ONS will be required to provide the results of the PLI tests ONS test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once PLI ONS has isolated a trouble to the BellSouth provided Loop, and has had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If PLI ONS reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge PLI ONS for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the End User’s location more than once due to incorrect or incomplete information provided by PLI ONS (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx PLI ONS for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

Loop Testing/Trouble Reporting. 2.1.6.1 PLI OnePoint will be responsible for testing and isolating troubles on the Loops. PLI OnePoint 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, PLI OnePoint will be required to provide the results of the PLI tests OnePoint test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once PLI OnePoint has isolated a trouble to the BellSouth provided Loop, and has had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If PLI OnePoint reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge PLI OnePoint for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the End User’s location more than once due to incorrect or incomplete information provided by PLI OnePoint (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx PLI bill OnePoint for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

Loop Testing/Trouble Reporting. 2.1.6.1 PLI 2.1.8.1 CGI will be responsible for testing and isolating troubles on the Loops. PLI CGI 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, PLI CGI will be required to provide the results of the PLI tests CGI test or analysis which indicate a problem on the BellSouth provided Looploop. 2.1.6.2 2.1.8.2 Once PLI CGI has isolated a trouble to the BellSouth provided Loop, and has had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Usersend users. 2.1.6.3 2.1.8.3 If PLI CGI reports a trouble on a non-designed or designed Loop loop (e.g., UVL-SL1, UCL-ND, etc.) and no trouble actually existscan be found by BellSouth no, BellSouth will charge PLI CGI for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Looploop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the End User’s location more than once due to incorrect or incomplete information provided by PLI (e.g., incomplete address, incorrect contact name/number, etc.). If CGI reports trouble on a designed loop and no trouble is found, BellSouth will xxxx PLI charge CGI for each additional any dispatch required to repair and testing outside the circuit due to central office. If it is subsequently determined that a trouble did exist on the incorrect/incomplete information providedBellSouth network facilities at the time of the initial trouble report, CGI will not be billed for the NTF. BellSouth will assess Both Bell and CGI charges are disputable in the applicable Trouble Determination rates from BellSouth’s FCC or state tariffsnormal manner.

Loop Testing/Trouble Reporting. 2.1.6.1 PLI BSE will be responsible for testing and isolating troubles on the Loops. PLI BSE 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, PLI BSE will be required to provide the results of the PLI BSE tests which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once PLI BSE has isolated a trouble to the BellSouth provided Loop, and has issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If PLI BSE reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge PLI BSE for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the End User’s location more than once due to incorrect or incomplete information provided by PLI BSE (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx PLI BSE for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

Loop Testing/Trouble Reporting. 2.1.6.1 PLI Xxxx will be responsible for testing and isolating troubles on the Loops. PLI Xxxx 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, PLI Xxxx will be required to provide the results of the PLI tests Xxxx test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once PLI Xxxx has isolated a trouble to the BellSouth provided Loop, and has had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If PLI Xxxx reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge PLI Xxxx for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the End User’s location more than once due to incorrect or incomplete information provided by PLI Xxxx (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx PLI Xxxx for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

Loop Testing/Trouble Reporting. 2.1.6.1 PLI SPARDI will be responsible for testing and isolating troubles on the Loops. PLI SPARDI 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, PLI SPARDI will be required to provide the results of the PLI tests SPARDI test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once PLI SPARDI has isolated a trouble to the BellSouth provided Loop, and has had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If PLI SPARDI reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge PLI SPARDI for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the End Userend-user’s location more than once due to incorrect or incomplete information provided by PLI SPARDI (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx PLI bill SPARDI for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

Loop Testing/Trouble Reporting. 2.1.6.1 PLI Velocity will be responsible for testing and isolating troubles on the Loops. PLI Velocity 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, PLI Velocity will be required to provide the results of the PLI Velocity tests which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once PLI Velocity has isolated a trouble to the BellSouth provided Loop, and has issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If PLI Velocity reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge PLI Velocity for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the End User’s location more than once due to incorrect or incomplete information provided by PLI Velocity (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx PLI Velocity for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

Loop Testing/Trouble Reporting. 2.1.6.1 PLI INET will be responsible for testing and isolating troubles on the Loops. PLI INET 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, PLI INET will be required to provide the results of the PLI tests INET test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once PLI INET has isolated a trouble to the BellSouth provided Loop, and has had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If PLI INET reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge PLI INET for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the End User’s location more than once due to incorrect or incomplete information provided by PLI INET (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx PLI bill INET for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

Loop Testing/Trouble Reporting. 2.1.6.1 PLI ACI will be responsible for testing and isolating troubles on the Loops. PLI ACI 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, PLI ACI will be required to provide the results of the PLI tests ACI test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once PLI ACI has isolated a trouble to the BellSouth provided Loop, and has had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If PLI ACI reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge PLI ACI for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the End Userend-user’s location more than once due to incorrect or incomplete information provided by PLI ACI (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx PLI ACI for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

Loop Testing/Trouble Reporting. 2.1.6.1 PLI Ruddata will be responsible for testing and isolating troubles on the Loops. PLI Ruddata 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, PLI Ruddata will be required to provide the results of the PLI tests Ruddata test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once PLI Ruddata has isolated a trouble to the BellSouth provided Loop, and has had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If PLI Ruddata reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge PLI Ruddata for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the End Userend-user’s location more than once due to incorrect or incomplete information provided by PLI Ruddata (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx PLI Ruddata for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

Loop Testing/Trouble Reporting. 2.1.6.1 PLI CCI will be responsible for testing and isolating troubles on the Loops. PLI CCI 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, PLI CCI will be required to provide the results of the PLI tests CCI test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once PLI CCI has isolated a trouble to the BellSouth provided Loop, and has had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If PLI CCI reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge PLI CCI for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the End Userend-user’s location more than once due to incorrect or incomplete information provided by PLI CCI (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx PLI CCI for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

Loop Testing/Trouble Reporting. 2.1.6.1 PLI NTBS will be responsible for testing and isolating troubles on the Loops. PLI NTBS 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, PLI NTBS will be required to provide the results of the PLI NTBS tests which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once PLI NTBS has isolated a trouble to the BellSouth provided Loop, and has issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If PLI NTBS reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge PLI NTBS for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the End User’s location more than once due to incorrect or incomplete information provided by PLI NTBS (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx PLI NTBS for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.