Loop Testing/Trouble Reporting Sample Clauses
The Loop Testing/Trouble Reporting clause establishes procedures for identifying, reporting, and resolving issues or faults within a telecommunications or data transmission loop. In practice, this clause outlines the responsibilities of each party for conducting diagnostic tests, documenting any detected problems, and communicating these issues to the appropriate technical support teams for resolution. Its core function is to ensure prompt detection and correction of service disruptions, thereby maintaining system reliability and minimizing downtime.
Loop Testing/Trouble Reporting. 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks 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, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop.
2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and 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 Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks 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 Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will ▇▇▇▇ ▇▇▇▇▇▇▇ Networks 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 EPICUS will be responsible for testing and isolating troubles on the Loops. EPICUS 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, EPICUS will be required to provide the results of the EPICUS test which indicate a problem on the BellSouth provided Loop.
2.1.6.2 Once EPICUS has isolated a trouble to the BellSouth provided Loop, and 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 EPICUS reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge 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-user’s location more than once due to incorrect or incomplete information provided by EPICUS (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will 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.8.1 CCI will be responsible for testing and isolating troubles on the Loops. 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. At the time of the trouble report, CCI will be required to provide the results of the CCI test which indicate a problem on the BellSouth provided loop.
2.1.8.2 Once CCI has isolated a trouble to the BellSouth provided Loop, and 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.8.3 If CCI reports a trouble on a non-designed or designed loop and no trouble actually exists, BellSouth will charge CCI for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the loop’s working status.
Loop Testing/Trouble Reporting. 2.1.8.1 Comm South will be responsible for testing and isolating troubles on the Loops. Comm South 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 Center. At the time of the trouble report, Comm South will be required to provide the results of the Comm South test which indicate a problem on the BellSouth provided loop.
2.1.8.2 Once Comm South has isolated a trouble to the BellSouth provided Loop, and 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.8.3 If Comm South reports a trouble on a non-designed loop (e.g., UVL-SL1, UCL- ND, etc.) and no trouble actually exists, BellSouth will charge Comm South for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the loop’s working status. If Comm South reports trouble on a designed loop and no trouble is found, BellSouth will charge Comm South for any dispatch and testing outside the central office.
Loop Testing/Trouble Reporting. 2.1.8.1 ▇▇▇▇▇▇▇.▇▇▇ will be responsible for testing and isolating troubles on the Loops. ▇▇▇▇▇▇▇.▇▇▇ 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. At the time of the trouble report, ▇▇▇▇▇▇▇.▇▇▇ will be required to provide the results of the ▇▇▇▇▇▇▇.▇▇▇ test which indicate a problem on the BellSouth provided loop.
Loop Testing/Trouble Reporting. 2.1.4.1 Comcast Phone will be responsible for testing and isolating troubles on the Loops. Comcast Phone 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, Comcast Phone will be required to provide the results of the Comcast Phone test which indicate a problem on the BellSouth provided Loop.
Loop Testing/Trouble Reporting. 2.1.9.1 MCI shall use commercially reasonable efforts to test and isolate the trouble to the BellSouth Loop before reporting a trouble to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center.
2.1.9.2 Once MCI 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 customers.
2.1.9.3 If MCI reports a trouble on a Network Element or Other Service and no trouble actually exists on the BellSouth portion, BellSouth will charge MCI, at the rates set forth in Exhibit A of this Attachment, for any dispatching and testing (both inside and outside the central office (CO)) required by BellSouth in order to confirm the working status. MCI agrees to waive its right to a billing dispute for each No Trouble Found/Maintenance of Service charge for which no documentation is provided by MCI upon request from BellSouth. The documentation provided may consist of the notes or statements by MCI’s technicians and other personnel regarding the testing work performed.
2.1.9.4 In the event BellSouth must dispatch to the customer’s location more than once due to incorrect or incomplete information provided by MCI (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will bill MCI for each additional dispatch required to provision or Page 63 of 509 Attachment 2 Network Elements & Other Services Page 15 repair the circuit due to the incorrect/incomplete information provided, in accordance with Maintenance of Service rates set forth in Exhibit A to this Attachment. BellSouth will provide proof that the requirement for multiple dispatches was based on MCI errors in the trouble ticket. This information will be provided upon request by MCI.
2.1.9.5 For voice grade Loop orders (or Loops intended to provide voice grade services), for which MCI orders a migration of existing service, MCI shall have its dial-tone available forty-eight (48) hours prior to the Loop order completion due date. For voice grade Loop orders for which MCI does not order a migration of existing service, MCI’s failure to have such dial-tone available shall not affect BellSouth’s processing of the order, but BellSouth shall not be responsible for its inability to test such Loop if no dial-tone is present.
Loop Testing/Trouble Reporting. 2.1.8.1 Symtelco will be responsible for testing and isolating troubles on the Loops. Symtelco 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. At the time of the trouble report, Symtelco will be required to provide the results of the Symtelco test which indicate a problem on the BellSouth provided loop.
2.1.8.2 Once Symtelco has isolated a trouble to the BellSouth provided Loop, and 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.8.3 If Symtelco reports a trouble on a non-designed or designed loop and no trouble actually exists, BellSouth will charge Symtelco for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the loop’s working status.
Loop Testing/Trouble Reporting. 2.4.5.1 NuVox will be responsible for testing and isolating troubles on the loops. NuVox must test and isolate trouble to the AT&T portion of a designed/non-designed Page 77 of 321 Attachment 2 – Network Elements and Other Services/BELLSOUTH TELECOMMUNICATIONS, INC. AT&T SOUTH CAROLINA/NUVOX 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 AT&T at the time of the trouble report, NuVox will be required to provide the results of the NuVox test which indicate a problem on the AT&T provided loop.
2.4.5.2 Once NuVox has isolated a trouble to the AT&T provided loop, and has issued a trouble report to AT&T on the loop, AT&T will take the actions necessary to repair the loop if a trouble actually exists. AT&T will repair these loops in a reasonable and nondiscriminatory manner and in time frames that are as favorable as those in which AT&T repairs similarly situated loops to its customers.
2.4.5.3 If NuVox reports a trouble on a non-designed or designed loop and no trouble actually exists, AT&T will charge NuVox for any dispatching and testing (both inside and outside the CO) required by AT&T in order to confirm the loop’s working status. AT&T will assess the applicable Maintenance of Service Charge rates from AT&T’s FCC No. 1 Section 13.3.1 for designed circuits, Section A4.3.1 of the GSSTs for Alabama, Kentucky, Louisiana, Mississippi and Tennessee where trouble determination for non-designed circuits is covered under premises work charges, Section A15.
4.1 of the GSSTs for Florida and North Carolina where trouble determination for non-designed circuits is covered under trouble location charges, and Section N1.1.2 of the Non-Regulated Services Pricing tariff for Georgia and South Carolina where trouble determination for non-designed circuits is covered under trouble determination charges. If NuVox reports the same trouble on the same UNE loop within thirty (30) calendar days of AT&T’s notification to NuVox of its disposition of the prior trouble, and AT&T is able to determine that such trouble does exist on AT&T’s network, NuVox shall be credited on the next billing cycle for charges associated with the prior trouble.
2.4.5.4 In the event AT&T must dispatch to the customer’s location more than once due to incorrect or incomplete information provided by NuVox (e.g., incomplete address, incorrect contact name/number, etc.), AT&T will...
Loop Testing/Trouble Reporting. 2.1.6.1 Comm South will be responsible for testing and isolating troubles on the Loops. Comm South 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, Comm South will be required to provide the results of the Comm South test which indicate a problem on the BellSouth provided Loop.
2.1.6.2 Once Comm South has isolated a trouble to the BellSouth provided Loop, and 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 Comm South reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Comm South 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 Comm South (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will ▇▇▇▇ Comm South 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.