Test Results User Guide Toolgrade PDF

Consumer Access Solutions
LoopCare Test OSS

Test Results User Guide
Revision Q
Release 2.15
December, 2006
040-0357
ELECTRONIC EMISSION NOTICE

Federal Communications Commission (FCC) Statement
Warning: The hardware provided with the LoopCare Testing System generates, uses, and can radiate radio
frequency energy and if not installed and used in accordance with the instruction manual, may cause interference to
radio communications. The hardware has been tested and found to comply with the limits for a Class A computing
device pursuant to Subpart J of Part 15 of FCC Rules. These rules are designed to provide reasonable protection
against such interference when the hardware is operated in a commercial environment. Operation of this equipment
in a residential area is likely to cause interference, in which case the users, at their own expense, will be required to
take whatever measures necessary to eliminate the interference.
NOTICE: Every effort has been made to ensure that the information in this manual is complete and accurate at the
time of printing. However, information is subject to change without notice.
LoopCare is a trademark of Tollgrade Communications, Inc.
DigiTest is a registered trademark of Tollgrade Communications, Inc.
EDGE is a trademark of Tollgrade Communications, Inc.
All other trademarks and copyrights are property of their respective owners.
All figures, screen images, results and diagrams contained in this manual are examples for reference purposes only.
Operational results may vary depending on the configuration of and conditions existing on your telecommunications
system.
This document contains proprietary information that shall be distributed or routed only within Tollgrade
Communications, Inc. and to its authorized clients, except with written permission of Tollgrade.
2006, Tollgrade Communications, Inc., All Rights Reserved

PROPRIETARY TOLLGRADE AND AUTHORIZED CLIENTS ONLY
Tollgrade Communications, Inc.

493 Nixon Road
Cheswick, PA 15024
Revision Q (p/n 040-0357)
Phone: 412-820-1400 0
Fax: 412-820-1530 3
Technical Support: 800-777-5405 o
412-820-1498 9
Orders: 412-820-13053
Web Site: www.tollgrade.com
Release 2.15, December, 2006 ii
About this Guide
xvii
Overview
xvii
Organization of This Guide
xviii
Conventions Used
xx
Related Documentation
xxi
Ordering Documentation
xxii
Introduction
1-1
Test Results
1-2
LoopCare Measurements
1-9
Individual LoopCare Tests
1-13
Specialized Tests
1-22
LoopCare VER Code Enhancement Features - DCTU and non-DCTU1-31
LoopCare Verification Codes (0-99)
2-1
VER 0: TEST OK
2-4
VER 0A: TEST OK
2-5
VER 0B: CPE or HIGH RESISTANCE OPEN
2-6
VER 0C: CPE or HIGH RESISTANCE OPEN
2-7
VER 0D: OPEN IN OR DSL TERM
2-8
VER 0E: OPEN OUT BALANCED OR DSL TERM
2-9
VER 0H: ROH DETECTED DURING TEST
2-10
VER 0L: NO FAULTS TO BENCHMARKED LENGTH
2-11
VER 0M: TEST OK MTU
2-12
VER 0P: PROBABLY TEST OK
2-13
VER 0R: TEST OK
2-14
VER 0T: OUT OF TOLERANCE CONDITION
2-15
VER 05: TEST OK - CHANNEL NOT TESTED
2-16
VER 6: BUSY-SPEECH
2-17
VER 11: CROSS TO WORKING PAIR- FAULT
2-18
VER 12: AC FEMF FAULT
2-20
VER 13: HAZARDOUS POTENTIAL
2-21
Release 2.15, December, 2006 -iii
-iv
VER 14: CROSS TO WORKING PAIR: MARGINAL
2-22
VER 15: DC FEMF MARGINAL
2-24
VER 16: AC FEMF MARGINAL
2-26
VER 17: RESISTIVE FAULT AND DC FEMF
2-27
VER 18: OPEN OUT AND CROSS
2-28
VER 21: GROUND FAULT
2-29
VER 22: SHORT FAULT
2-31
VER 23: SWINGING RESISTANCE: FAULT
2-32
VER 24: SWINGING RESISTANCE: MARGINAL
2-33
VER 25: SHORT AND GROUND
2-34
VER 26: MDF TEST RECOMMENDED- LOW RESISTANCE
2-35
VER 27: DC RESISTANCE- MARGINAL
2-37
VER 28: SHORT OR GROUND
2-38
VER 3: OPEN IN
2-39
VER 30: SWITCH COMMON EQUIP BAD
2-40
VER 31: INVALID LINE CIRCUIT
2-41
VER 32: CANNOT DRAW DIAL TONE
2-42
VER 33: CANT BREAK DIAL TONE
2-43
VER 34: POSSIBLE INVALID ACCESS
2-44
VER 35: OPEN IN AND CROSS
2-45
VER 36: LINE CIRCUIT AND DIAL TONE PROBLEM
2-46
VER 37: DIAL TONE BURST DETECTED
2-47
VER 38: POSSIBLE CO WIRING ERROR
2-48
VER 39: CO EQUIP BAD - ISTF BAD - LINE CARD BAD - PROTOCOL HANDLER
BAD
2-50
VER 40: CO EQUIP SUSPECT
2-52
VER 41: OPEN OUT BALANCED
2-53
VER 42: OPEN OUT IN CABLE
2-55
VER 43: HIGH RESISTANCE OPEN
2-57
VER 44: OPEN OUT 2-PARTY OR BRIDGE LIFTERS
2-58
VER 45: OPEN OUT - NEAR DROP
2-59
VER 46: OPEN ON PREMISES
2-61
VER 47: OPEN IN REMOTE TERMINAL
2-62
VER 48: T1 FACILITY BAD
2-64
VER 50: COT CHANNEL UNIT SUSPECT
2-66
VER 51: CO BATTERY ON PAIR GAIN SYSTEM
2-67
Release 2.15, December, 2006
2-68
VER 52: INVALID PAIR GAIN CO SIGNATURE
VER 53: PAIR GAIN TEST ACCESS FAILURE -POSSIBLE BUSY CONDITION269
VER 54: PAIR GAIN SYSTEM FAILURE
2-70
VER 55: PAIR GAIN CHANNEL FAILURE
2-71
VER 56: BAD PAIR GAIN COT CHANNEL UNIT
2-72
VER 57: BAD RT CHANNEL UNIT
2-73
VER 58: BAD COT AND RT CHANNEL UNITS
2-74
VER 59: RT CHANNEL UNIT SUSPECT
2-75
VER 60: BUSY PACKET
2-76
VER 61: LINE IN USE
2-77
VER 63: CRAFT ACTION
2-78
VER 71: RECEIVER OFF HOOK (ROH)
2-79
VER 72: MDF TEST RECOMMENDED- PERMANENT SIGNAL
2-80
VER 73: LINE IN USE OR PERMANENT SIGNAL
2-81
VER 74: PERMANENT SIGNAL
2-83
VER 75: SHORT - PROBABLY ROH
2-84
VER 80: DIAL OK
2-85
VER 81: DIAL NOT OK
2-86
VER 90: C-MESSAGE NOISE
2-87
VER 91: INVALID PBX SIGNATURE
2-88
VER 92: INVALID AC SIGNATURE
2-89
VER 93: POOR BALANCE
2-90
VER 95: RESISTIVE FAULT AND OPEN
2-91
VER 96: MARGINAL BALANCE
2-92
VER 97: DERIVED PR NOT TESTED-PHYSICAL PR NOT SERVED2-93
VER 98: ANALYSIS OF FULL RESULTS NEEDED
2-94
VER 99: MULTIPLE FAULTS DETECTED
2-95
Verification Codes (AC-DT)
3-1
VER AA: STATIC ADDRESSING VERIFICATION FAILED
3-4
VER AB: LOOK OUT ATM LOOPBACK FAILURE
3-5
VER AC: TRANSACTION STOPPED
3-6
VER AD: DHCP ADDRESS RESOLUTION FAILURE
3-7
Release 2.15, December, 2006 -v
-vi
VER AH: HTTP ADDRESS TEST FAILURE
3-8
VER AI: IP PING FAILURE
3-9
VER AJ: SEARCH STRING NOT IN HTML SOURCE
3-10
VER AK: METALLIC TESTS NOT ALLOWED
3-11
VER AL: ATM LOOPBACK FAILURE
3-12
VER AM: SYNC FAILURE - MODEM NOT DETECTED
3-13
VER AN: SYNCOUT FAILURE - MODEM NOT DETECTED
3-14
VER AO: SYNCOUT FAILURE - MODEM DETECTED
3-15
VER AP: PPP AUTHENTICATION FAILURE
3-16
VER AQ:VLAN PARAMETER MISMATCH
3-17
VER AR: IP TRACE ROUTE FAILURE
3-18
VER AS: SYNC FAILURE - MODEM DETECTED
3-19
VER AT: THROUGHPUT TEST FAILURE
3-20
VER AU:HOSTNAME (DNS) TRANSLATION FAILURE
3-21
VER AV:ATM FAILURE - CHECK VPI/VCI
3-22
VER AZ: TEST COMPLETE - EXAMINE RESULTS
3-23
VER B0: TEST EQUIPMENT BUSY - TIME OUT IN ACCESS
3-24
VER B1: TEST NOT MADE
3-25
VER B2: TEST EQUIPMENT BUSY - SANITY OR DIAG IN PROGRESS3-26
VER B3: TEST EQUIPMENT BUSY - SIMULTANEOUS TEST REQUEST MADE327
VER B4: TEST EQUIPMENT OUT OF SERVICE
VER B5: TEST EQUIPMENT BUSY - PAIR GAIN ACCESS EQUIPMENT BUSY329
VER B6: DOWNLOAD IN PROGRESS
3-30
VER B7: TEST EQUIP BUSY
3-31
VER B8: ALL TRUNKS ARE BUSY BY OTHER USERS
3-32
VER BA: NO DCTU PORT AVAILABLE
3-33
VER BB: DCTU NOT AVAILABLE
3-34
VER BC: NO GDXC AVAILABLE
3-35
VER BD: NO MTB AVAILABLE
3-36
VER BE: NO MTIB AVAILABLE
3-37
VER BF: NO MA PACK AVAILABLE
3-38
VER BG: NO MAB AVAILABLE
3-39
VER BH: NO PRTC AVAILABLE
3-40
VER BI: NO MTB TO PGTC AVAILABLE
3-41
3-28
VER BJ: NO MTB TO PGTC PORT AVAILABLE
3-42
VER BK: PGTC PATH SETUP BLOCKAGE (other)
3-43
VER BL: NO PORT AVAILABLE
3-44
VER BM: NO TRUNK AVAILABLE
3-45
VER BN: NO TEST PACKAGE AVAILABLE
3-46
VER BP: NO PMU AVAILABLE
3-47
VER BQ: NO DIALER AVAILABLE
3-48
VER BR: NO BUSY DETECTOR AVAILABLE
3-49
VER BS: SWITCH TEST ACCESS BLOCKAGE
3-50
VER BT: RMU IN USE
3-51
VER BU: CAN'T CONNECT TO RMU
3-52
VER BV: NO MODEM PORT AVAILABLE
3-53
VER BW: CAN'T CONNECT TO CMU
3-54
VER BY: LTE BUSY
3-55
VER BZ:HDT INITIALIZING
3-56
VER C1: TOTALIZER OPERATION PROBLEMS
3-57
VER C2: TOTALIZER DEFECT
3-58
VER C3: POLARITY GUARD PROBLEMS
3-59
VER C4: COIN RELAY PROBLEMS
3-60
VER C5: COIN SUPERVISORY CKT PROBLEMS
3-61
VER C6: INITIAL RATE OR FRAUD CONTACT PROBLEMS
3-63
VER C7: OSCILLATOR PROBLEMS
3-64
VER D1: DENIED SERVICE - TERMINATING
3-65
VER D2: DENIED SERVICE - ORIGINATING
3-66
VER D3: DENIED SERVICE
3-67
VER D4: DENIED CPE
3-68
VER D5: DENIED SERVICE MIXED
3-69
VER DG: GATEWAY FAILURE
3-70
VER DI: DENIED/INTERCEPT - MIXED
3-71
VER DL: CONTROLLER-LTF OR FRONT END-LTS DATA LINK FAILURE3-72
VER DP: DEFECTIVE DC TEST PAIR - (OPEN, SHORT, GROUND or BATTERY)

3-73
VER DT:BAD DLC OR DC TEST PAIR
3-74
Release 2.15, December, 2006 -vii
-viii
Verification Codes (E0-IZ)
4-1
VER E0: TEST SYSTEM ERROR
4-4
4-5
4-6
4-7
4-8
4-9
4-10
VER E8: CAN'T SEND REQUEST TO APPROPRIATE FE
4-12
VER E9: ISDN DIGITAL LINK NOT AVAILABLE
4-13
VER EA: LTE LOGIN ERROR
4-14
VER EB: BSU MODULE EQUIPAGE ERROR
4-15
VER EC: COMMUNICATION OR MML ERROR
4-16
VER ED: DLC CONCENTRATOR COMM FAILURE
4-17
VER EL: SWITCH LOGIN FAILURE
4-18
VER EP: LTE SLOT NOT EQUIPPED
4-19
VER ER: LTE COMMUNICATION FAILURE
4-20
VER ES: LTE CHANNEL OOS
4-21
VER ET: POTS DETECTED ON DRY DSL LINE
4-22
VER EU: POTS ONLY OR NON-COMBO CIRCUIT
4-23
VER EV:VOIP EQUIPAGE ERROR
4-24
VER F0: TEST EQUIPMENT FAILURE
4-25
4-26
4-27
4-28
VER F4: TEST EQUIP BUSY
4-29
VER F5: LTE INTERNAL ERROR
4-30
VER F6: DLC CONCENTRATOR INTERNAL ERROR
4-31
VER FA: BUSY DETECTOR FAILURE
4-32
VER FB: DIALER FAILURE
4-33
VER FC: MEASUREMENT UNIT FAILURE
4-34
VER FD: SLEEVE CONTROL FAILURE
4-35
VER FE: CONTROL FAILURE - ISLC/DCTU
4-36
VER FF: CONTROL FAILURE - USLC/DCTU
4-37
VER FG: TBCU PROTOCOL TEST FAILURE - (OPEN)
4-38
VER FH: EQUIPMENT ACCESS FAILURE
4-39
VER FJ: SWITCH TEST ACCESS FAILURE
4-40
VER FK: GDXC FAILURE
4-41
VER FL: MODEM CONNECTION FAILURE
4-42
VER FM: RMU/CMU CONNECT FAILURE
4-43
VER FN: LOGIN FAILURE
4-44
VER FP: AS COMMUNICATION FAILURE
4-45
VER FQ: STUCK RELAY - MA CP
4-46
VER FR: AS PORT OR DMU CONFIG ERROR
4-47
VER FS: MSU OUT OF SERVICE
4-48
VER FT: CONNECT FAIL - PROTOCOL FAILURE
4-49
VER FV: DEFECTIVE DIST OR SCAN CP
4-50
VER FW: RT COMM FAIL
4-51
VER FX: TEST EQUIPMENT FAILURE
4-52
VER FZ: TEST HEAD COMM FAILURE
4-53
VER G0: VALID RINGER COUNT AND TERMINATION
4-54
VER G1: INVALID RINGER TERMINATION
4-55
VER G2: INVALID 2 PARTY RINGER TERMINATION
4-56
VER G4: RINGER TEST WITH NO RECORDS
4-57
VER G5: VALID 2 PARTY TERMINATION
4-58
VER G6: RINGER TEST- UNCATALOGED EQUIPMENT
4-59
VER G8: NO RINGERS FOUND
4-60
VER HA: ONT IS INACTIVE
4-61
VER HB: NON SERVICE AFFECTING ALARM PRESENT
4-62
VER HJ: SYSTEM AND BACKUP MEMORY RESET
4-63
VER HK: NON SERVICE AFFECTING ALARM PRESENT
4-64
VER H0:SWITCH TO VG COMMUNICATION DOWN
4-65
VER HP: FOLLOWING CONFIG NOT PROV IN VG
4-66
VER I0: TEST OK NOW
4-67
VER IA: WIRING ERROR - NT1 REVERSED
4-68
VER IB: UNEXPECTED ISDN TERMINATION
4-69
VER IC: POSSIBLE AMI BRITE DETECTED
4-70
VER ID: ISDN TERMINATION MISMATCH
4-71
VER IF: INVALID TERM FOR ISDN LINE
4-72
VER IG: FURTHER TEST REQUIRED
4-73
Release 2.15, December, 2006 -ix
-x
VER IH: OE MISMATCH
4-74
VER IJ: DENIED SERVICE - ADD ANALYSIS
4-75
VER IK: NOT AN ISDN LINE
4-76
VER IL: TERMINATION MISMATCH SUSPECTED
4-77
VER IM: DIGITAL TEST MARGINAL
4-78
VER IN: CPE (NT1) POWER SUSPECTED
4-79
VER IP: TEST OK PARTIAL TEST DONE
4-80
VER IR: CPE (NT1) ON SECONDARY POWER
4-82
VER IS: SECTIONALIZE WITH LONGER LPBK
4-83
VER IT: TERMINATION MISMATCH
4-84
VER IU: LINE RECORD SHOWS TERM MISMATCH
4-85
VER IV: CHANNEL MISMATCH
4-86
VER IW: INVALID WIRE CENTER IN LINE RECORD
4-87
VER IZ: DIGITAL ANALYSIS REQUIRED
4-88
Verification Codes (L0-XU)
5-1
VER L0: LOADING REQUIRED ON LOOP
5-5
VER L1: INCORRECT COIL DETECTED
5-6
VER L2: INCORRECT SECTION DETECTED
5-7
VER L3: END SECTION TOO LONG
5-8
VER L4: INCORRECT NUMBER OF LOADS
5-9
VER L5: DOUBLE LOAD DETECTED
5-10
VER L6: MISSING LOAD DETECTED
5-11
VER LB: LOOP BAD
5-12
VER LD: LOOP DETECT
5-13
VER LE: LOOP DETECT
5-14
VER LF: TEST TRANSFERRED - EXPECT DELAY
5-15
VER LM: REMOTE TEST-EXPECT DELAYED RESULTS
5-16
VER LS: LOOP SUSPECT
5-17
VER LT: LONG TEST-EXPECT DELAYED RESULTS
5-18
VER LU: LINE IN USE
5-19
VER MC: TEST OK WITH CPE AND MTU CONDITION
5-20
VER MD: MDF TEST RECOMMENDED
5-21
VER MH: MEMBER OF MLHG
5-22
VER MT: MDF TESTABLE ONLY
5-23
VER NA: UDLC SIGNATURE FOUND - LTS TEST
5-24
VER ND: TEST NOT MADE FROM THIS FE
5-25
VER NE: CU NOT EQUIPPED FOR TEST ACCESS
5-26
VER NF: NOT SUPPORTED BY TEST HEAD
5-27
VER NG: INVALID TDSL REQUEST
5-28
VER NK: LINE RECORD ERROR
5-29
VER NL: NO LINE RECORD IN SYSTEM
5-30
VER NM: NETWORK MANAGER FAILURE
5-31
VER NP: NOT VALID IDENTIFIER
5-32
VER NS: LINE NOT SERVED BY MLT
5-33
VER NT: LINE NOT MLT TESTABLE
5-34
VER NV: LINE NOT VERIFIED
5-36
VER P1: DC RESISTIVE FAULT: PREMISES
5-37
VER P2: DC RESIST MARGINAL: PREMISES
5-39
VER P3: DC RESISTANCE-MARGINAL
5-41
VER P4: CUSTOMER PREMISE EQUIPMENT BAD
5-42
VER P5): CUST PREM EQUIP SUSPECT
5-43
VER P6: CUST PREM EQUIP IN TEST MODE
5-44
VER P7: CPE (STATION SET) BAD OR INVALID
5-45
VER P8: CPE (T-INTERFACE) BAD
5-46
VER P9: NT1 PRIMARY POWER FAIL
5-47
VER PA: LAYER 2 PROBLEM
5-48
VER PB: POSSIBLE PROTOCOL PROBLEM
5-49
VER PC: LAYER 3 PROBLEM
5-50
VER PD: SIGNAL LOSS FROM REMOTE END
5-51
VER PF: XDSL POWER PROBLEM
5-52
VER PI: REMOTE SIG LOSS: UNKNOWN CAUSE
5-53
VER PR: XDSL CPE EQUIP PROBLEM
5-54
VER S0: LINE IN SERVICE - ADD ANALYSIS
5-55
VER SP: PROTECTED SERVICE
5-56
VER SS: SPECIAL SERVICES REQUIRED
5-57
VER ST: INTERCEPT - ADD ANALYSIS
5-59
VER SU: INTERCEPT
5-60
VER SX: PBX ROUTE ADVANCED TELEPHONE NUMBERS
5-61
VER T1: SYSTEM TIMEOUT
5-62
Release 2.15, December, 2006 -xi
-xii
VER T2: SWITCH PROCESS TIMEOUT
5-63
VER TB: DIGITAL TEST BUSY
5-64
VER TR: ANOTHER USER IS ACCESSING THIS REMOTE TEST EQUIPMENT565
VER TS: SSA ACCESS REQUIRED BEFORE REQUEST IS PERFORMED5-66
VER U1: UNEXPECTED THERMISTORS
5-67
VER U2: UNEXPECTED PBX SIGNATURE
5-68
VER U3: UNEXPECTED RINGER TERMINATION
5-69
VER U4: UNEXPECTED INWARD SERVICE
5-70
VER U5: UNEXPECTED CHANNEL TEST RESULTS
5-71
VER U6: UNEXPECTED INTEGRATED PGS/UNEXPECTED UNIVERSAL PGS572
VER V0:VOIP TEST FAILURE
5-73
VER VA:CALL NOT ANSWERED
5-74
VER VB:VOIP SERVER BUSY
5-75
VER VC:CALL FAILED
5-76
VER VP:DROP ACCESS TO CHANGE TEST PORT
5-77
VER VQ:VOICE QUALITY BELOW THRESHOLD
5-78
VER VR:REGISTRATION FAILED
5-79
VER VT:TESTING ON DEDICATED PORT / *DROP ACCESS FIRST5-80
VER W1: WIDEBAND NOISE PROBLEM
5-81
VER W2: LOAD COIL DETECTED
5-82
VER W4: POTS Line Circuit Found On ADSL Line
5-83
VER WC: XDSL LTE EQUIP PROBLEM
5-84
VER WT: XDSL MODEM IN TRANSITION PHASE
5-85
VER WU: XDSL MODEM IN UNKNOWN STATE
5-86
VER WX: XDSL CARD IS NOT IN SERVICE
5-87
VER X7: TEST SYSTEM ERROR
5-88
VER XA: OVRD-EXK/NNX COMBO NOT IN DATABASE
5-89
VER XF: INVALID/INCOMPLETE CIRCUIT INFO
5-90
VER XG:LDS NAME UNKNOWN TO SDV-EM
5-91
VER XH: LINE RECORD ERROR
5-92
VER XI: INVALID TN
5-93
VER XN: REQUEST NOT ALLOWED IN THIS MODE
5-94
VER XO: TESTABLE VIA STV OPTION
5-95
VER XR: INVALID TEST REQUEST
5-96
VER XS: TESTABLE VIA THE STV MASK ONLY
5-98
VER XT: TRAINING SCRIPT UNAVAILABLE
5-99
VER XU: ONT TEST HEAD NOT AVAILABLE
5-100
RSA Line 24 Messages
6-1
RSA Line 24 Messages vs. VER Codes
6-2
Summary Messages
7-1
Overview
7-4
Testing Non-Locally Switched Services on DLCS
7-5
DLCS Testing From LoopCare
7-8
AC FEMF Summary Messages
7-10
AC Signature Summary Messages
7-15
ADSL Splitter Signature Summary Messages
7-16
ADTRAN 3000 Summary Messages
7-17
APMAC Summary Messages
7-18
Balance Summary Messages
7-19
Benchmark Database (BMDB) Summary Messages
7-20
bPON Summary Messages
7-24
BSU Summary Messages
7-27
CALL Summary Messages
7-32
Central Office Summary Messages
7-33
C-Message Noise Summary Messages
7-38
Coin Summary Messages
7-39
DC FEMF Summary Messages
7-42
Denied Service Summary Messages
7-44
Digital Loop Carrier Summary Messages
7-45
Digital Service Summary Messages
7-46
Distance to Short Summary Messages
7-52
EMU Summary Messages
7-53
FTTPDIG Summary Messages
7-54
In Use Summary Messages
7-66
Release 2.15, December, 2006 -xiii
ISDN Summary Messages
Load Coil Summary Messages
7-102
Local Number Portability (LNP) Summary Messages
7-105
Long Loop Summary Messages
7-107
LTE Summary Messages
7-108
Miscellaneous Summary Messages
7-111
MTU Summary Messages
7-114
National ISDN (NT1) Summary Messages
7-115
NSDB Summary Messages
7-116
Open Summary Messages
7-118
Permanent Signal Release Summary Messages
7-123
REF0 Summary Messages
7-124
Remote Measurement Unit (RMU) Summary Messages
7-125
Resistive Fault Summary Messages
7-126
Ringer Summary Messages
7-130
Rotary Dial & Touch-Tone Summary Messages
7-133
Special & Protected Service Summary Messages
7-135
Special Signature Summary Messages
7-136
System Status Summary Messages
7-147
TONE Summary Messages
7-160
Training Messages
7-161
Unexpected Signature Summary Messages
7-162
Wideband Summary Messages
7-164
xTU-R Detect Summary Messages
7-172
FDR (Frequency Domain Reflectometry
7-173
Introduction to the Appendices
Introduction To The Appendices
Central Office Equipment
-xiv
7-72
Central Office Equipment Effects on Testing
8-1
8-2
A-1
A-2
Outside Plant Equipment Effects

Outside Plant Equipment
B-2
Termination Equipment Effects
C-1
C-2
Other Special Effects on Testing
D-1
AC Signatures
Valid Thermistor Signatures
Valid DC Signatures
Valid AC Signatures
Valid DC Signatures
B-1
Protocol Error Codes (PEC)
D-2
E-1
E-2
F-1
F-2
G-1
G-2
H-1
H-2
Release 2.15, December, 2006 -xv
IX
-xvi
Index
IX-1
About this Guide
Overview
Overview
This section describes the purpose and organization of this guide, the intended
audience, conventions used, and related documents.
The LoopCareTM Test Operations Support System (LoopCare) Test Results User
Guide provides an overview of LoopCare testing features and instructions for
analyzing the results returned from the test equipment.
LoopCare is an automated test system that tests and analyzes POTS, DLC, and
ISDN telephone lines and equipment in support of loop maintenance operations.
Intended Audience
This guide is intended for the following LoopCare audience:
Maintenance administrators
Facility managers
Repair technicians
(Continued on next page)
Release 2.15, December, 2006 -xvii
Organization of This Guide

Organization of
This Guide
This guide is organized into five chapters and eight appendices:
About This Guide

Describes the purpose, intended audience, and organization of this guide.
Chapter 1 - Introduction
Provides an overview of LoopCare testing features and discusses how the
test results and measurements can be analyzed to isolate problems on the
line under test.
Chapter 2 - LoopCare Verification (VER) Codes (0-99)

Describes the numeric VER codes (0-99) along with sample displays,
summary messages, and trouble analysis.
Chapter 3 - LoopCare Verification (VER) Codes (B0-DP)

Describes the alphanumeric VER codes (B0-DP) along with sample
displays, summary messages, and trouble analysis.
Chapter 4 - LoopCare Verification (VER) Codes (EO-IZ)

Describes the alphanumeric VER codes (EO-IZ) along with sample
Chapter 5 - LoopCare Verification (VER) Codes (LB-XU)

Describes the alphanumeric VER codes (LB-XU) along with sample
Chapter 6 - RSA Line 24 Messages

Describes the messages that the Repair Service Attendant sees on line 24
that accompany the VER code in the test results.
Chapter 7 - Summary Messages

Describes additional messages that may be displayed with a VER code.
Organization of
This Guide
(continued)
Chapter 8 - Introduction to the Appendices

Describes an explanation of the Appendices.
Appendix A - CO Equipment Effects

Describes Central Office Equipment effects on LoopCare testing.
Appendix B - OSP Equipment Effects

Describes Outside Plant Equipment effects on LoopCare testing.
-xviii Release 2.15, December, 2006
Appendix C - Test Equipment Effects

Describes LoopCare Test Equipment features and their effects on
LoopCare testing.
Appendix D - Other Special Effects on Equipment

Describes LoopCare features and line record items and their effect on
LoopCare testing.
Appendix E - Valid DC Signatures

Lists the valid DC signatures and configurations.
Appendix F - Valid AC Signatures

Lists the valid AC signatures and configurations.
Appendix G - Valid Thermister Signatures

Lists the valid thermister signatures and configurations.
Appendix H - Protocol Error Codes

Describes the Protocol Error Codes that may be received during LoopCare
testing.
Release 2.15, December, 2006 -xix
Conventions Used
Conventions Used
The Following special typeface conventions are used in this guide:
Italic type is used to show emphasis and to reference chapters within this
guide or to related documents.
Mono-spaced type is used to indicate information that appears on the

screen and to denote keyboard function keys.
Bold type is used to show emphasis.
A note is used to indicate additional information, a reminder, or a

clarification.
NOTE:
This symbol indicates a note.
-xx
Related Documentation
Overview
The complete LoopCare Testing System documentation set is listed and

described in the Documentation Installation Guide.
Release 2.15, December, 2006 -xxi
Ordering Documentation
Overview
-xxii
For copies of the LoopCare documents, contact your LoopCare Customer

Support Representative.
Introduction
Contents
Test Results
1-2
1-9
1-13
Specialized Tests
1-22
LoopCare VER Code Enhancement Features - DCTU and

non-DCTU
1-31
Release 2.15, December, 2006 1-1
Introduction
Test Results
Overview
The LoopCare test results are displayed in the lower portion of the TV mask in a
summary section and in a detailed results section. An example of the LoopCare
test results format is shown below:
LoopCare test results are affected by the various types of line equipment and
services involved. These effects on the test results are provided in The Effects On
Testing tables in Appendices A through D. The DC, AC, and Thermistor Signature
tables in Appendices E, F, and G show the electrical signals associated with the
various types of line equipment.
NOTE:
The sample screens in this document display loop length in feet. Your
system may be configured to display the length in meters.
1-2
Introduction
Test Results (Continued)

The Results
Summary
The summary has up to six lines of information consisting of analytical statements

that, in some cases, contain the actual LoopCare values.
Also appearing in this summary section is an LoopCare Verification (VER) code.
The VER code is a two character code that categorizes the line condition based
on LoopCare tests. For a list of all the LoopCare VER codes and their meanings,
see the VER Codes section of this Guide. Each VER code is usually associated
with a specific summary message or set of messages. Sometimes, however, you
will see summary messages that do not relate directly to the VER code. These
messages typically describe secondary information about the line condition and
generally follow the more important information. Each of these messages is
described in the Summary Message section of this Guide.
An example of the summary part of the results section is shown below:
VER 0: TEST OK
TESTED WITH PARTIAL RECORDS
The VER code "0" shows a Test OK situation. This is verified by the first summary
message "TEST OK". The second message is not directly related to the VER
code, and shows that the line was tested with incomplete line records.
Introduction

The Detailed
Results
The detailed results contain categories of information that provide the actual
measured values obtained during LoopCare testing. These categories contain
data that support the information in the summary statements. Often, the
information in the categories is helpful when making an in depth analysis of the
line condition. You can read more about these measures and the tests that
produce them in the LoopCare Measurements section of this guide.
Each type of result (for example, DC resistance, AC resistance) has its own spot
in the results section. This is to help you quickly locate the information that you
need. You should know where to look because whatever you are looking for is
always in the same place in the results section. An example of the detailed part of
the results section is given below. Because almost all of the LoopCare test
categories are shown, you should realize that these results followed a FULL
request. That's because only FULL performs virtually all of the LoopCare tests.
1-4
Introduction

The Detailed
Results (continued)
Information on each detailed test results category is discussed below.
CRAFT: DC
SIGNATURE
The Craft DC signature provides the two terminal DC

resistances and voltage values on the line. These
values are displayed for the benefit of the repair person
that you are working with. Craft people are more familiar
with these two terminal values than with the three
terminal values that LoopCare also measures. This is
because the meters they carry in the field give them two
terminal values.
LoopCare: DC
SIGNATURE
The LoopCare DC signature provides the three terminal

DC resistances and voltages on the line. LoopCare
uses these values to identify DC resistive faults (shorts,
grounds) and DC battery faults (cross to working pair).
LoopCare also uses them to identify different types of
terminations and equipment on the line (PBXs, for
example). See Appendix E for a list of valid DC
signatures.
AC SIGNATURE
The AC signature refers to the AC resistance and AC

voltage on a line. LoopCare uses AC resistance to
identify terminations and detect open faults. See
Appendix F for a list of valid AC signatures.
The AC voltage values tell you if there is any foreign AC
voltage on the line (for example, a cross to an AC power
line). LoopCare gives you this information only if there is
foreign voltage present on the line. Otherwise, you won't
even see the VOLTS heading. Here's what this section
of the mask will look like when there is AC voltage:
AC SIGNATURE
KOHMS VOLTS
9
450
14
460
15
Continued on next page
RNGRS
The RNGRS category tells you about the number and

location of standard ringers on the line: tip to ring (T-R),
tip to ground (T-G), and ring to ground (R-G).
Introduction
THRMS
The THRMS category tells you if there are any

thermistors on the line. And it tells you where those
thermistors are located: T-R, T-G, and/or R-G. Because
thermistors are never present when there are standard
ringers, this category appears in the same spot on the
TV mask as the RNGRS category. So, if LoopCare sees
standard ringers, it tells you about them and you won't
see the THRMS category. The example above is like
that. If LoopCare doesn't see standard ringers or
doesn't see a valid signature for a PBX or Key system, it
runs a thermistor test and tells you about it. In this case,
the RNGRS spot on the mask is replaced with the
THRMS category. If LoopCare sees a thermistor, the
message "YES" is given next to its location. Here's an
example:
THRMS
T-R
YES T-G
YES R-G
Appendix G gives the expected locations of thermistors
for various termination equipment.
1-6
Introduction

CENTRAL OFFICE
The central office category gives brief messages about

the central office tests. Specifically, the tests are the line
circuit test and the draw and break dial tone (DT) test. A
list of the messages that may appear in this spot on the
TV mask is given below:
CAN'T DO CO TEST
DT GROUND SUPPLIED
XBAR NO TEST
CAN'T DRAW DT
INWARD SERVICE
SLOW DIAL TONE
LINE CKT OK
CAN'T BREAK DT
CAN'T DO DT TEST
BALANCE
DIAL TONE OK
The balance category gives the results of the

longitudinal and capacitive balance tests. The
longitudinal balance is shown in decibels (DB); and the
capacitive balance is shown as a percentage (%). The
capacitive balance is shown in the following cases:
a.
when the line is open
b.
when longitudinal balance is printed.
Here's how this area on the TV mask might look when

both the longitudinal and capacitive balance are shown:
BALANCE
CAP
LONG
LOOP LENGTH
100 %
65 DB
The length category tells you about how long the loop
is. When there are no problems on a line (in other
words, the line is TEST OK), LoopCare tells you how far
the telephone is from the central office. When there is
an open fault on the line, LoopCare tells you how far the
open is from the central office and, sometimes, how far
the open is from the telephone. Of course, there are
exceptions to these rules. For example, you won't get
the open measurements if it is a two party line or if the
line has a bridge lifter. Here's what this length section
looks like when there is an open fault:
OPEN DISTANCE
FROM CO
= 2300 FT
FROM STATION = 1100 FT
Introduction

General Rules for
the Results Section
1-8
1.
When there is no information for a certain category, LoopCare leaves that

category's section of the mask blank. It doesn't even give you the heading.
So if there is no ringer information, there will be no RNGRS heading.
2.
The results format discussed in this section is for the FULL request. The
formats for the LOOP, LIN, CO, MDFIN, MDFOUT, and RINGER requests
are subsets of the FULL request. In other words, these other requests don't
do all of the tests that the FULL request does, so some of the results
categories are not used. See the descriptions of these requests to find out
what results they do or do not show.
3.
All DC voltage values appearing in the summary are the CRAFT (2

terminal) (craft) values.
4.
LoopCare DC resistance values that are less than 100 KOHMS will be
shown out to two decimal places. For example, 37.89 KOHMS. All other
resistance values (CRAFT and AC) will be rounded off to whole numbers.
For example, 224.33 KOHMS (AC) will become 224 KOHMS (AC) on your
TV mask.
Introduction
Overview
LoopCare takes a number of electrical measurements of a telephone line.

Interpreting LoopCare results requires an understanding of these measurements
and why they are made.
The following section describes the measurements that LoopCare makes and why
they are important. It will deal primarily with the most frequent type of telephone
service - sometimes called Plain Old Telephone Service or POTS - rather than
lines with special equipment (bridge lifters, for example) or terminations (PBXs).
Remember that telephone lines consist of two wires--tip (T) and ring (R). At one
end of these wires (in the central office) is a line circuit; at the other end (in the
subscriber's home) is a telephone. The line circuit has a battery on the ring wire
and ground on the tip wire. The telephone, which is usually connected between
the tip and ring, acts as a switch.
When the receiver is on-hook, the switch is off and the path from the battery to the
telephone back to the ground is not complete-- current doesn't flow because it
can't get past the telephone (since the switch is open). When the receiver is offhook, the switch is on and the current flows from the battery, out the ring wire,
through the telephone, and back along the tip wire to the central office ground--the
loop is complete. The flow of electrical current is fundamental to the proper
working of the telephone.
Dialing information and the subscriber's voice are carried by changing the
characteristics of that current--so it is important that the path it follows is in
working order. LoopCare checks the condition of that loop primarily by measuring
DC resistance and voltage and AC resistance and voltages. These terms are
defined below (see the glossary at the end of this guide for the definitions of other
important LoopCare terms):
DC - direct current: continuous current in one direction on a circuit; the

central office battery provides direct current.
AC - alternating current: current that reverses direction at certain intervals;

the power company provides alternating current for lighting and other uses.
And, the telephone company uses it to ring telephones.
resistance - a measure of how much current is "held back" or resisted.
voltage - a measure of how much current a circuit can produce.
Introduction
LoopCare Measurements (Continued)

DC Resistance
LoopCare measures three DC resistances on a telephone line:

1.
between tip and ring (T-R): how hard it is for current to flow from the tip side
through the phone to the ring side. Because the phone is on-hook and the
loop is open during LoopCare testing, the T-R resistance should be high--it
should hold back the current very well.
2.
between ring and ground (R-G): how hard it is for current to flow the ring
wire to the outside--out of the wire. The ground in this case is not the
central office ground in the line circuit, but a ground outside of the loop.
Basically, LoopCare is checking to see if current is getting out of the loop. A
high R-G resistance means that it is hard for the current to get out of the
telephone line, which is exactly what we want.
3.
between tip and ground (T-G): how hard it is for current to flow from the tip
wire to the outside. Again, the ground is outside of the loop, not the central
office ground. The T-G resistance should also be high.
Resistance is usually displayed in Kilo-ohms (thousands of ohms). (NOTE: An

easy way to translate Kohms into ohms is to make the decimal point into a comma
and add a 0. For example, 1.00 KOHMS is 1,000 OHMS and .30 KOHMS is 300
OHMS). For a completely good POTS line that is on-hook, the resistances should
look like this:
3500 Kohms T-R
3500 Kohms R-G
3500 Kohms T-G
If any of these values are lower than 1000 ohms, there is either a short or ground
fault on the line. See the description of the DC Tests for more information about
DC resistances for shorts and grounds.
These DC Resistance values may also be displayed as >3500 or >5000 only for
tests performed by Stinger CLT/CLT-EXs, if the DC Signature Raw Data field on
the custenv screen is set to ON. See Appendix F of the System Administration
Guide.
1-10
Introduction

DC Voltage
LoopCare makes two DC voltage measurements--tip to ground (T-G) and ring to

ground (R-G), where the ground is again outside of the loop and not in the central
office. Basically, LoopCare is checking to see whether any voltage is entering
either side of the loop from the outside world. LoopCare removes the central office
line circuit as soon as it begins its tests. So there should be no voltage on the line
due to the central office battery. Any voltage seen by LoopCare must come from
an outside source. For a good telephone line, DC voltages should be:
0 volts T-G
0 volts R-G
If the values are not zero, there is probably a cross to a working pair or a wet
cable. See the description of DC tests for information about DC voltages for a
cross fault.
AC Voltage
LoopCare also makes T-G and R-G AC voltage measurements. LoopCare is

checking to see if there is AC voltage entering the loop from the outside.
Obviously, we don't want the telephone line to be carrying AC voltage, so a good
pair should have no AC voltage. LoopCare won't even display the AC voltage if it
is zero. If the values are not zero, the telephone line may be touching a power
line, which could mean lots of trouble. See the description of Foreign
Electromotive Force (FEMF) tests for information about excess AC voltage.
Introduction

AC Resistance
LoopCare uses AC resistance to see if there is a telephone or other termination

on the line. It makes three AC resistance measurements: T-R, T-G, and R-G.
These measurements are called the "signature" of a telephone termination. A
telephone causes a low AC resistance value. So, if the telephone is connected
between the tip and ring, as on a POTS line, the T-R AC resistance value should
be low--usually between 2 - 20 K Ohms. Since there is usually no phone on the tip
side or ring side of the line, the AC resistance T-G and R-G should be higher,
above 25 Kohms. A good line gives AC resistances like this:
8 Kohms T-R
927 Kohms T-G
929 Kohms R-G
If either of the T-G or R-G values is low and the T-R value is high, the telephone
may be connected improperly. If none of the values is low, then there is probably
an open fault. See the descriptions of the AC tests and Opens test for more
information about open faults.
The above set of AC resistances is a typical AC signature of a standard POTS
line--one or more telephones connected tip to ring. Different types of terminations
(2-party lines, PBXs) have different signatures. Both AC and DC resistance values
are used to identify these different signatures. See the descriptions of DC Tests
and AC signature Tests for information about signatures.
LoopCare Analysis
1-12
As you will see below, LoopCare makes a lot of other measurements of a line.
And based on the results of each test, LoopCare decides which of the other tests
to run. This brings up an important point about LoopCare testing - LoopCare
"thinks for itself." It makes decisions about what to do next by comparing the
results that it has to results that it expects to see. LoopCare has a list of DC and
AC values that correspond to certain line conditions. This list specifies what a
short looks like in terms of DC resistance and what a Key Set looks like in terms of
AC resistance. And it compares the measurements it gets to the ones on this list.
For example, LoopCare expects a standard POTS line to have a certain AC
resistance. After it runs the AC Signature Test on a line, it checks to see if the
results match the standard values. If they do, LoopCare decides that there are no
AC problems and moves on to the next test in the sequence. If they do not match,
LoopCare decides that there is a problem and does a special test for an open
circuit. The point is that LoopCare makes decisions by comparing the present
values to ones that it already knows about.
Introduction

Overview
Individual LoopCare tests are described below. The first set below is run when
you request a full series of tests on a line. They are initiated by the FULL request
from an LoopCare test mask. The other LoopCare requests run a subset of these
tests. In each description, the decisions made based on the results of the test are
discussed.
Access Tests
These are the tests that LoopCare runs when it first connects a test trunk to the
subscriber's line. First it checks for hazardous potential, which is defined as
extremely high voltage on the line. That much voltage is dangerous, so LoopCare
quickly drops access to the line, putting a halt to any further testing. If there's no
hazardous potential, LoopCare connects a busy detector to the line. The busy
detector, as you might expect, checks to see if there is speech on the line. If there
is, LoopCare drops access immediately so that the customer is not disturbed.
Otherwise, LoopCare remains connected to the line over the test trunk and moves
on to the next test in the sequence.
Foreign
Electromotive Force
(FEMF) Tests
These tests do a second check for excess AC or DC voltage. If there is a lot of

excess voltage, LoopCare drops access to the line during the Access Tests
discussed above. The FEMF tests look for high (but not necessarily hazardous)
voltage. Because high voltage would adversely affect the results of later
LoopCare tests, LoopCare stops testing if the FEMF tests reveal voltage
exceeding a certain level. It does not drop access to the line in this case, however.
So you can still monitor or talk on the line.
Introduction
Individual LoopCare Tests (Continued)

Line in Use Tests
LoopCare expects that the line it is about to test is NOT being used at the time of
the test. It expects that the telephone is on-hook. To make sure of this, it does a
few checks to make sure that this is the case.
1.
Is the Receiver Off-Hook?

This is the first question that LoopCare asks. Each type of central office
switch indicates an off-hook condition in a different way. Each has its own
off-hook "signature." LoopCare figures out which type of switch is
connected to the subscriber's line and then looks for this signature. If it
finds what looks like an off-hook condition, it checks for conversation.
Otherwise, LoopCare moves to the next test in the sequence - the Intercept
Test.
2.
Is the Receiver Off-Hook Because the Subscriber Is Talking On the Line?

This is LoopCare's second question if it thinks that the receiver is off-hook.
Conversation for all switch types is usually indicated by a T-R short,
grounds on both sides of the line and battery on the ring side. If it looks like
conversation, LoopCare stops testing immediately to avoid disturbing the
customer. Basically, LoopCare is double-checking to make sure that the
busy detector in the Access Tests didn't make a mistake. If there is no
conversation, LoopCare tries to figure out whether the receiver is really offhook or if there is a fault that makes it look like that's the case. It does that
by running a Receiver-Off-Hook (ROH) test.
3.
Is the Receiver Really Off-Hook?

The ROH test distinguishes between a T-R short and an actual off-hook
condition. It does this by placing current on the line and waiting for a signal
that the current passed through the telephone. If there is a short fault, this
signal will never come and LoopCare decides there is a T-R short. If the
signal comes, LoopCare decides that the receiver is indeed off-hook.
1-14
Introduction

Intercept Test
This test identifies lines that are out-of-service. Out-of-service lines are often
called "lines on intercept" Such lines also have characteristic signatures. In ESS
offices, for example, an intercept tone is placed on the line. So, LoopCare
compares what it sees in the intercept test to the standard intercept signature and
makes a decision. If it sees an intercept, it stops testing. If not, it moves on to the
next test in the sequence.
Direct Current
(*DC) Tests
By now, LoopCare is satisfied that the line is not in use or on intercept. So, it starts
the DC and AC tests. An important thing to remember is that LoopCare removes
the line circuit from the line at this point. The customer is out-of-service - THE
LINE IS DEAD.
The DC tests measure DC resistance and voltage.
1.
Resistance
The resistance values are used to identify shorts and/or grounds. A normal
line with a standard ringer should show DC resistances of approximately
3500 Kohms. Recall that a short fault means that current is taking an
alternate route between the tip and ring. So the DC resistance T-R will be
low (less than 150 Kohms):
10 Kohms T-R
3500 Kohms T-G
3500 Kohms R-G
Note the low resistance value T-R.
Recall that a ground fault means that current is escaping from the loop on either
the tip or the ring side. So the DC resistance would be low either T-G or R-G.
3500 Kohms T-R
15 Kohms T-G
3500 Kohms R-G
Note the low T-G resistance value.
LoopCare moves on to the next test in the sequence if it identifies a short or
ground, unless the fault is a major one. Major is defined as less than 3 Kohms DC
resistance on any one of the three sides (T-R, T-G, or R-G). LoopCare stops
testing if it discovers a major fault.
Introduction

Direct Current
(*DC) Tests
(continued)
2.
Voltage
The DC voltage values are used to identify a cross to a working pair,
among other things. On a good POTS line, there should be no voltage T-G
and R-G. That's because LoopCare removed the line circuit, which is where
DC voltage comes from on a telephone line. A cross to a working pair
means that the line is touching another telephone line and drawing battery
from that pair--so there should be voltage on whichever side is crossed
with the working pair:
-47 volts T-G
0 volts R-G
These results indicate that the tip of this pair is touching the ring side of
another pair. The 47 volts T-G are being drawn from that other pair. The
voltage should be about 48 volts since that is the voltage produced by a
normal central office line circuit, but it can be much less if the cross isn't a
severe one.
3.
PBX Identification
DC resistances are also used to validate non-POTS telephone signatures.
Usually, AC resistances are used to identify telephones on the line, but
some terminations (for example, a 756 PBX system) are recognized by
their DC resistances. LoopCare compares the DC values it measures to
those it expects for that particular telephone. A 756 PBX, for example,
would normally have values like this:
100 Kohms T-R
12 Kohms T-G
400 Kohms R-G
If LoopCare measured these values and the line record indicated the
presence of a 756 PBX, then LoopCare would report a valid PBX signature.
And, because it validated a PBX, it would skip the AC Signature,
Longitudinal Balance, Thermistor, and Opens tests since the presence of a
PBX on the line leads to inaccurate results from these tests. See the
description of AC Signature Tests for more information about termination
signatures. Also see Appendices C and E in the LoopCare Results User
Guide for a list of valid DC signatures for non-POTS terminations.
1-16
Introduction

Alternating Current
(AC) Signature Test
This test uses AC resistance measurements to identify POTS and other

termination equipment.
1.
POTS Terminations
The T-R value for a standard ringer should normally be between 8-18
Kohms; the T-G and R-G values should be greater than 25 Kohms and
about equal.
2.
Other Terminations
Other terminations (2 party, Key Systems) will have different AC
signatures. On a two-party line, one ringer is connected tip-to-ground and
the other is connected ring-to-ground. Because a telephone lowers the AC
resistance, LoopCare expects to see low values T-G and R-G (less than 20
Kohms) and a higher value (greater than 25 K ohms) T-R. Here's an
example of a two-party line.
500 Kohms T-R
10 Kohms T-G
8 Kohms R-G
These values indicate one or more ringers on the tip side and one or more
ringers on the ring side.
A Key Telephone System would look something like this:
12 Kohms T-R
100 Kohms T-G
104 Kohms R-G
See Appendices C and F in the LoopCare Results User Guide for other
valid AC signatures.
If LoopCare sees high AC resistance values (doesn't see a valid signature),
it suspects that there is an open fault and it initiates an Opens Test. See the
description of the Opens Test for more information.
Introduction
Individual LoopCare Tests (Continued)\

Longitudinal
Balance Test
This test measures how likely it is that the line is noisy. The results are expressed
in decibels (dB). If the balance is less than 40 dB, the line is probably very noisy. If
the balance is between 40 and 65 dB, the condition is marginal--the line may or
may not be noisy. If the balance is above 65 dB, the line is good--there should be
no noise problem.
Thermistor Test
This test checks for the presence of a thermistor on the line. A thermistor is a part
in some PBX and Key System telephones. It causes the telephone line's
resistance to decrease as its temperature increases. By applying voltage to the
line, LoopCare heats the thermistor and measures changes in resistance. The
resistances are compared to expected values for the termination (for example,
PBX) listed in the line record. For example, a tip-to-ring thermistor would be
expected if the line record lists 701 PBX as the termination. See Appendix G in
the LoopCare Results User Guide for valid thermistor signatures.
The Thermistor Test is done if:
Opens Test
the line record indicates that there should be a thermistor on the line;
the AC resistance on the part of the loop that is supposed to have a ringer
(T-G, for example) is between 30 and 100 Kohms. This leads LoopCare to
suspect that a thermistor is part of that ringer.
This test uses AC capacitance measurements to analyze the location and type of
open on a line. If LoopCare decides that a line is open, it then determines whether
the open is in or out of the central office. AC capacitance is a measure of how long
a wire is. So, if the length of either the tip or ring wire (for example, the distance
from the CO to the open) is short, LoopCare decides that the open is in the central
office and reports OPEN IN; if those lengths are long, LoopCare decides that it is
outside of the central office. In the latter case, it also reports the distance (in feet)
from the central office to the open.
The opens test is done whenever an open is suspected based on results from the
DC Tests, AC Signature Test, or Thermistor Test.
1-18
Introduction

Capacitive Balance
Measurement
LoopCare also uses AC capacitance to compute a percentage called capacitive

balance. Basically, it compares the capacitance of the tip wire to the capacitance
of the ring wire. Because capacitance is used to measure the length of a wire, the
balance measurement is the same as comparing the lengths of the tip and ring
wires. For a good pair with a single termination, these lengths are equal and the
balance percentage is about 100% (for example, if tip=152 feet and ring=152 feet,
then 152/152 = 1.0 or 100%).
Capacitive balance is very important when there is an open fault. If the lengths
from the central office to the open on both sides of the loop are equal, the balance
will again be about 100% and LoopCare will report a balanced open. This means
that both sides of the loop are open at the same place. If the lengths are not
equal, and the balance is less than 95% (for example, 150 feet/167 feet =.90 =
90%), LoopCare will not report a balanced open. This means that the open is
probably only on one side--the shorter one. LoopCare determines which side is
shorter and reports either OPEN TIP or OPEN RING.
Line Circuit Test
This test checks for the proper arrangement of the battery and ground in the
central office line circuit. The line circuit is the equipment that 1) detects that the
phone has been taken off-hook, 2) connects the loop to the switching equipment
and battery, 3) accepts dialed digits, and 4) provides dial tone. All of the tests
described so far are conducted without the line circuit present. Remember that
LoopCare removes the line circuit at the start of the DC Tests. Now, LoopCare has
to re-connect the line circuit to the subscriber's line. On a good line, LoopCare
expects to see a battery of approximately -48 volts on the ring side and a central
office ground on the tip side.
Introduction

Draw and Break
Dial Tone Test
With the line circuit still present, this test attempts to draw and break dial tone.
LoopCare electrically simulates a telephone going off-hook and checks for the
presence or absence of dial tone. Then, it removes the simulated off-hook
condition and checks to see if the dial tone breaks or stops. (Remember that the
Central Office tests are not run if the CO is a crossbar.)
Soak Test
This test measures DC resistance over time to determine if a ground is "swinging"

and if it may be "dried out." It will be attempted only if the ground is between 10
and 1000 Kohms. Voltage is applied to the line and a series of six resistance
measurements are made over a short period of time. The highest resistance value
of these six is compared to resistance value seen in the initial DC test. If the
highest value is at least 20% greater than the initial value, LoopCare calls the fault
"swinging." If the highest value is greater than 2,000 Kohms, LoopCare decides
that the fault has "dried out," in which case a Repair Technician should not be
dispatched to clear the trouble.
Ringer Test
This test, which uses a similar type of measurement to the AC Signature Test,
determines the number and location of standard ringers on a particular line. It
counts the number of ringers T-R, T-G, and R-G. It then determines whether the
results are consistent with what was expected from the line record information. If
the line record says that it is a two-party line with only one party assigned,
LoopCare expects to see one ringer on either the tip or ring side (remember that 2
party ringers are hooked up T-G and R-G, not T-R like POTS lines). So, it looks for
low AC resistance on either the tip or ring side.
1-20
Introduction

Length of Loop
Measurement
This calculation, which is the last performed in the series, uses AC capacitance to
measure the length of a good pair. It functions similarly to the Opens Test and
reports the distance from the central office to the telephone.
This test is run only on single party POTS and coin lines that have already been
deemed TEST OK.
Introduction
Specialized Tests
Overview
Most LoopCare test requests run through all or some of the above tests. Other
LoopCare requests are more specialized, sometimes requiring interaction with a
subscriber or repair technician. These are described below.
Dial Test
This test checks the subscriber's rotary dial. It requires the assistance of someone
at the telephone in question. When that person dials a "0," LoopCare measures
the dial speed and percent break of the rotary dial.
This test is run when a problem with the dial is suspected (for example, the
subscriber can't call out).
Touch-Tone Test
This test checks the condition of the subscriber's Touch-Tone pad by analyzing
the tones that are produced when the subscriber presses a certain sequence of
buttons on the pad. LoopCare does this by connecting a Touch-Tone Applique
Circuit to the line. This circuit checks the tones and returns a signal to indicate
whether the pad is good or not.
This test is run whenever you suspect a problem with the Touch-Tone pad (for
example, the subscriber gets a lot of wrong numbers).
1-22
Introduction
Specialized Tests (Continued)

Resistive Fault
Sectionalization
Tests
These tests measure the distance between a fault on a line and the repair
technician's location along that line. To do this, the repair technician has to tell
LoopCare where he or she is located. This is done by putting an intentional short
on the telephone line. Then, LoopCare measures the distance from the fault to the
repair technician's short. This distance helps the repair technician find the exact
location of the fault.
Coin Tests
These tests check for potential problems in a coin telephone set. Basically, it
checks the two primary mechanisms in the coin set - the totalizer and the coin
relay. The totalizer counts the coins that a customer puts in. It must be in a certain
starting position when the coins are dropped in. When it is in this position, the
totalizer is "homed." Each coin deposited causes the totalizer to send tones to the
central office. When the central office hears enough tones, the customer is
allowed to make a call. When a coin test is run, LoopCare first looks for a T-R
short. If it finds one, it suspects that the totalizer is not homed. So, it (a) tries to
home the totalizer, (b) listens for tones put out when the totalizer is homed, and (c)
measures how much current it took to home the totalizer. If LoopCare doesn't find
a T-R short, it checks the coin relay.
The coin relay is the mechanism that returns or collects the coins deposited by the
customer. It sends the coin to either the coin box or the return slot. If LoopCare
sees a T-G fault, it suspects a problem with the relay. So, it (a) tries to operate the
relay, (b) measures the relay's timing, and (c) measures how much current was
needed to operate the relay.
Introduction

ISDN Tests
If the line being tested is an ISDN line, then LoopCare must run additional test.
These test are described below.
Digitest Test
This function performs a digital loopback test on an ISDN terminal's DSL using the
test equipment (ISTF for circuit-switched channels) or using messages from the
Protocol Handler (for packet-switched channels).
Performing Digital Test (digtest) will indicate if the test was interrupted by a
customer for service thereby causing an early termination of the test. If not, the
first array on the results screen will contain the identification number for the
switching module that contains the protocol handler that tested the "D" channel for
the specified PDN. Following that array will be several more array's that contain
information such as:
the identification number for the switching module that contains the test
equipment (either a Protocol Handler or an ISTF)
the ISTF numbers tested
the port number used for testing the "B1" and "B2" channels respectively
for the specified PDN
was a digital test run on the "D" channel, and what type of test was run on
the "B1" and "B2" channels
what was the status results of the "D", "B1" and "B2" channels tested for
the specified PDN
what was the percentage of good frames received on each the channels
("D", "B1", and "B2")
what was the BER and BE, in exponential form, calculated as a result of an
ISTF test run on the "B1" and "B2" channels
1-24
Introduction

Linespecs Test
This function retrieves all available information about an ISDN line from a switch
database. The data will include items that range from physical data about the
Digital Subscriber Line (DSL) to provisioned services for each channel and for
each terminal connected to the DSL.
The information retrieved from the databases contain data associated with the
specified terminal identifier such as:
line unit type
switching module type
line card type
Additional data related to the line card is also retrieved, such as:
whether the line card serving the specified PDN has a provisioned spare in
use
if the line card is spared, then the equipment number for the spared line
card is obtained
LoopCare/ISDN needs to know the type of provisioned service that is on the "D",
"B1", and "B2" channels. Also from the data retrieved from the database
LoopCare/ISDN gets the primary directory number, the terminal type, and
Automatic Customer Station Rearrangement (ACSR) provisioning information for
each terminal connected to this DSL.
LoopCare users can perform a linespecs request to obtain information about the
provisioned service on the B channels. However, it should be noted that if both B
channels are provisioned to be PKT SW, the subscriber will not get dial tone.
Introduction

Per Test
This function returns a formatted set of protocol error records to LoopCare/ISDN.

If the function specifies a primary directory number, then only those protocol error
records for that primary directory number will be returned. If the function specifies
a line card equipment number, then all the protocol error records for the DSL will
be returned.
The "selection criteria" input parameter will specify further what protocol error
records to return. For example, if the selection criteria is a period of time, then all
the protocol error records generated by the given terminal(s) for that period of
time would be returned. Similarly, if the selection criteria is a type of channel (e.g.,
all, D, B1, B2, any B, or both Bs), then all the protocol error records generated by
the given terminal(s) for that channel(s) would be returned.
1-26
Introduction

PML1 Test
ISDN defines standard protocols for digital transmission in layers. These layers
are important for maintenance of ISDN lines because the switch keeps track of
errors in transmission according to the layer in which the error occurred.
LoopCare/ISDN defines these layers as, layer 1, layer 2, and layer 3. Layer 1 is
related to the physical transmission of raw data. Layer 2 and 3 refer to the ways in
which the raw digital data is grouped into "frames" and "packets" to transmit
information.
The PML1 function gets the layer 1 error counts from a line card and intermediate
elements (e.g., D channel banks and SLC systems). It then formats the error
counts and returns them to LoopCare/ISDN. Switches that meet the ANSI U
interface standard will provide registers for the different error counts. LoopCare/
ISDN may request any combination of the above counts.
Separate error counts are kept for each of the following:
current hour
previous hour
current interval
previous interval
recent interval number 2

current interval register 1st
previous interval register 1st

current interval register 2nd
previous interval register 2nd
current interval register 3rd
previous interval register 3rd
current interval register 4th
previous interval register 4th
Introduction

PML2 Test
Level two is called the data link level. This level groups the bits into "frames".
Included in the frame are certain "framing bits" to designate frame boundaries,
identify the type and destination of the frame, and detect transmission errors. The
rules for putting together the frame and the framing bits are called the level two
protocols. The level two protocol for packet-switched "B" channels is called LAPB
and for the "D" channel is LAPD. Circuit-switched "B" channels, which are used
for voice calls, do not use a level two protocol.
The level two frames are processed in the switch by the Packet Handler and at
the other end by the customer's premise equipment. The 5ESS switch keeps track
of errors having to do with the framing, which are called level two errors. If a line
has level two errors, but does not have level one errors, then the problem on that
line is not caused by a faulty transmission path.
Separate tallies are kept for each of the following:
current day, hour, minute, and second as determined by the 5ESS switch's
internal clock
day, hour, minute, and second when the 5ESS switch last reset the layer 2
counters
The following tallies are kept for each "D", "B1", and "B2" channels:
the number of frames received which failed the Cyclic Redundancy Check
(CRC)
the total number of frames received during the measurement period
the number of unexpected frames (e.g., out of sequence, unexpected

SABM, etc.)
the number of protocol timeouts
the number of primary directory numbers for which information is being

returned
1-28
Introduction

PML3 Test
Level three is called the Network level. Within each level two frame, between the
framing bits, is a "packet" of data which contains the real information being
transmitted. The "packet" is formed according to a set of rules called the level
three protocol. For both "B" channel and "D" channel data packets, the protocol is
X.25 Packet Layer. For the "D" channel signaling packets, referred to as
messages, the level three protocol is called Q.931. Circuit-switched "B" channels
do not use a level three protocol.
Separate tallies are kept for each of the following:
the current day, hour, minute, and second as determined by the 5ESS
switch's internal clock
the number of primary directory numbers for which information is being

returned
the primary directory number for which the following information pertains
the number of X.25 protocol error records collected for the "D" channel
? the number of Q.931 protocol error records collected for the "D" channel
the number of protocol error records collected for the "B1" channel and for
the "B2" channel
Introduction

Restore Test
When a status inquiry is made via the switch to LoopCare/ISDN interface, an

ISDN terminal or digital subscriber line may be found to have been automatically
removed from service. The ability to promptly restore service will be required to
confirm a problem or to test a repair when the repair service bureau is working
interactively with a customer or with the field craft. The "restore" function restores
an ISDN terminal or DSL that has been removed from service by automatic
maintenance action, but not when it has been removed from service by any
manual action. A digital subscriber line may be restored by either a primary
directory number or line card equipment number. An ISDN terminal can only be
restored through a primary directory number.
Status Test
This function returns all available status information for one or more ISDN
terminals. This information includes the status of the DSL, its channels, and the
terminal. It may also, optionally, include the status of the other terminals on the
DSL.
1-30
Introduction
LoopCare VER Code Enhancement

Features - DCTU and non-DCTU
Overview
The VER Code Enhancement Features provide new, unique VER codes to
identify the specific cause of blockages and failures, when testing subscriber
loops. The new codes identify the source of the problem in the test head, the
facilities, or the switch.
The non-DCTU feature, available in the G4I5/G5I3 and later releases, is
applicable to the LTS, LTF, CMU and RMU test heads. The 5ESS DCTU feature,
available in the G6I2/G7I2 and later releases, is applicable to the 5ESS (DCTU)
test head.
VER Code
Enhancement
Features Benefits
The new VER Codes provided in the VER Code Enhancement Features are more
specific in nature and are designed to provide the following benefits:
More direct analysis of the problem
Rapid correction of the problem
Better engineering of the test equipment
Increased flowthrough.
MTAS/TREAT can then identify persistent blockage and failure problems, such as
inadequate engineering of test head or switch resources.
The Testability Expert System can be used to provide:
Daily analysis of MTAS/TREAT data
Identification of "untestable" VER Codes
Indication of probable cause of problems
Weekly/Monthly management reports summarizing all identified testability

problems.
Introduction

(Continued)
Non-DCTU VER
Code Enhancement
Feature
The Non-DCTU VER Code Enhancement Feature became available in the G4I5/
G5I3 LoopCare/ISDN release. This feature is designed for use with LTSs, LTFs,
RMUs and CMUs.
TE/TR results will indicate the new VER codes. Most summary messages remain
the same (TEST EQUIP BUSY and TEST EQUIP FAIL).
TV and TEST masks will indicate the new VER code and summary message.
1-32
Introduction

(Continued)
New VER Codes
The following is a list of VER Codes that have been added or updated for the nonDCTU VER Code Enhancement Feature:
CATEGORY
VER
CODE
DESCRIPTION
CO FAULT
05
CHANNEL STATUS NOT IDENTIFIED
EQUIPMENT BUSY
BL
BM
BN
BP
BQ
BR
BS
BT
BU
BV
BW
NO PORT AVAILABLE
NO TRUNK PACKAGE AVAILABLE
NO TEST PACKAGE AVAILABLE
NO PMU AVAILABLE
NO DIALER AVAILABLE
NO BUSY DETECTOR AVAILABLE
SWITCH BLOCKAGE
RMU IN USE
CANT CONNECT TO RMU
NO MODEM PORT AVAILABLE
CANT CONNECT TO CMU
EQUIPMENT FAIL
FA
FB
FC
FD
FH
FL
FM
FN
FZ
BUSY DETECTOR FAILURE

DIALER FAILURE
PMU FAILURE
SLEEVE CONTROL FAILURE
EQUIPMENT ACCESS FAILURE
MODEM CONNECTION FAILURE
RMU/CMU CONNECT FAILURE
LOGIN FAILURE
TEST HEAD COMMUNICATIONS FAILURE
Introduction

5ESS DCTU VER
Code Enhancement
Feature
The 5ESS DCTU VER Code Enhancement Feature became available in the G6I2/
G7I2 LoopCare/ISDN release. This feature is designed for use with the 5ESS
DCTU.
This feature requires a compatible 5ESS generic but either the LoopCare generic
or the 5ESS generic can be operational before the other. The compatible 5ESS
generics are:
5E8.1 SU 93-0045
5E9.1 SU 93-0013
5E9.2 Base
TE/TR results will indicate the new VER codes. Most summary messages remain
the same (TEST EQUIP BUSY and TEST EQUIP FAIL). VER Code DP is added
and the RSA will be given a TEST EQUIP FAIL message. VER DP means that the
DC test pair used for IDLC in 5ESS is defective (either open, short, ground or
battery). A screening rule can be used to direct this VER Code directly to a MA
who handles DLC troubles for correction of the problem.
TV and TEST masks will indicate the new VER code and summary messages.
PST results will indicate the specific cause of the blockage or failure condition
instead of the current TEST EQUIP BUSY or TEST EQUIP FAIL messages.
1-34
Introduction

(Continued)
New VER Codes
The following is a list of VER Codes that have been added or updated for the
5ESS DCTU VER Code Enhancement Feature:
CATEGORY
VER CODE
DESCRIPTION
BA
NO DCTU PORT AVAILABLE
BB
DCTU NOT AVAILABLE
BC
NO GDXC AVAILABLE
BD
NO MTB AVAILABLE
BE
NO MTIB AVAILABLE
BF
NO MA PACK AVAILABLE
BG
NO MAB AVAILABLE
BH
NO PRTC AVAILABLE
BI
NO MTB TO PGTC AVAILABLE
BJ
NO MTB TO PGTC PORT EQUIPPED
BK
PGTC PATH SETUP BLOCKAGE (Other)
BL
NO PORT AVAILABLE
BP
NO PMU AVAILABLE
BS
SWITCH BLOCKAGE
BU
CANT CONNECT TO RMU
BV
NO MODEM PORT AVAILABLE
BW
CANT CONNECT TO CMU
DENIED SERVICE
DP
DEFECTIVE DC TEST PAIR - (OPEN, SHOT,

GROUND OR BATTERY)
EQUIPMENT FAIL
FE
CONTROL FAILURE - ISDL/DCTU
FF
CONTROL FAILURE - USLC/DCTU
FG
TBUC PROTOCOL TEST FAILURE - (OPEN)
FH
EQUIPMENT ACCESS FAILURE
FJ
SWITCH FAILURE
FK
GDXC FAILURE
FL
MODEM CONNECTION FAILURE
FM
RMU/CMU CONNECT FAILURE
FZ
TEST HEAD COMMUNICATIONS FAILURE
EQUIPMENT BUSY
1-36
Introduction
Contents
VER 0: TEST OK
2-4
VER 0A: TEST OK
2-5
VER 0B: CPE or HIGH RESISTANCE OPEN
2-6
VER 0C: CPE or HIGH RESISTANCE OPEN
2-7
2-8
2-9
2-10
VER 0L: NO FAULTS TO BENCHMARKED LENGTH
2-11
VER 0M: TEST OK MTU
2-12
2-13
VER 0R: TEST OK
2-14
VER 0T: OUT OF TOLERANCE CONDITION
2-15
VER 05: TEST OK - CHANNEL NOT TESTED
2-16
VER 6: BUSY-SPEECH
2-17
VER 11: CROSS TO WORKING PAIR- FAULT
2-18
2-20
2-21
Contents (Continued)
VER 14: CROSS TO WORKING PAIR: MARGINAL
2-22
2-24
2-26
2-27
2-28
2-29
VER 22: SHORT FAULT
2-31
2-32
2-33
2-34
VER 26: MDF TEST RECOMMENDED- LOW RESISTANCE 2-35

2-37
2-38
VER 3: OPEN IN
2-39
2-40
2-41
2-42
2-43
2-44
2-45
VER 36: LINE CIRCUIT AND DIAL TONE PROBLEM
2-46
2-47
VER 38: POSSIBLE CO WIRING ERROR
2-48
VER 39: CO EQUIP BAD - ISTF BAD - LINE CARD BAD - PROTOCOL
HANDLER BAD2-50
2-2
2-52
2-53
2-55
2-57
VER 44: OPEN OUT 2-PARTY OR BRIDGE LIFTERS
2-58
2-59
2-61
2-62
2-64
2-66
2-67
VER 52: INVALID PAIR GAIN CO SIGNATURE
2-68
VER 53: PAIR GAIN TEST ACCESS FAILURE -POSSIBLE BUSY

CONDITION
2-69
2-70
2-71
2-72
2-73
2-74
VER 59: RT CHANNEL UNIT SUSPECT
2-75
VER 60: BUSY PACKET
2-76
VER 61: LINE IN USE
2-77
2-78
VER 71: RECEIVER OFF HOOK (ROH)
2-79
VER 72: MDF TEST RECOMMENDED- PERMANENT SIGNAL2-80

2-81
2-83
2-84
VER 80: DIAL OK
2-85
VER 81: DIAL NOT OK
2-86
2-87
2-88
2-89
2-90
2-91
2-92
VER 97: DERIVED PR NOT TESTED-PHYSICAL PR NOT SERVED2-93
2-94
VER 99: MULTIPLE FAULTS DETECTED
2-95
VER 0: TEST OK
Overview
No obvious trouble was detected on the line. However, there may still be a
problem with parts of the loop that were not tested. In general, when the system
tests OK, there is no problem indicated by any of the detailed results. For metallic
testing, the DC resistances and voltage are within the acceptable range, the AC
signature is valid, and a loop length is reported. For higher-layer testing, such as
BSU and VoIP, the reported statistics and/or graphics indicate that each of the
tested layers and network elements is functioning normally. For more information,
see the section of the Test Request Guide that corresponds to the particular test
that was run,
Example
VER 0: TEST OK
CRAFT: DC SIGNATURE MLT: DC SIGNATURE AC SIGNATURE
KOHMS VOLTS
KOHMS VOLTS
KOHMS
RNGRS
3500
T-R
3500
T-R
9 1
T-R
3500
0 T-G
3500
0 T-G
4500
T-G
3500
0 R-G
3500
0 R-G
4600
R-G
Additional
Information
This example is a TEST OK for a single party line. Note the CRAFT and LoopCare
DC signatures show high resistances (3500 K ohms) and low voltage (0 Volts).
The AC signature indicates the presence of a ringer tip to ring. The central office
check indicates that the line circuit arrangement of battery and ground was valid
and LoopCare was able to draw and break dial tone properly. In addition, the
capacitive balance (100%) and the longitudinal balance (65 DB) were both good.
Finally, the length of the loop is given as the last piece of information about the
line.
Also take note that you may occasionally get a TEST OK message if there is a
keyset on the customer's line.
bPON Feature
VER 0: DROP TEST OK
A bPON test on a customer drop detected no obvious problems.
2-4
VER 0A: TEST OK

Overview
VER 0A indicates that either a FULL(X) or LOOP(X) test request was run and the
signatures returned show an ADSL served line.Testing indicates that the line is
OK. One of the following summary messages appears.
ADSL C.O. SPLITTER SIGNATURE FOUND
NON SIGNATURED SPLITTER DETECTED
Example
VER 0A: TEST OK

ADSL C.O. SPLITTER SIGNATURE FOUND
CRAFT: DC SIGNATURE
KOHMS VOLTS
MLT: DC SIGNATURE
KOHMS VOLTS
AC SIGNATURE
KOHMS
3500
T-R
3500
T-R
15
3500
0 T-G
3500
0 T-G
3500
0 R-G
3500
0 R-G
RNGRS
YES T-R
2000
2000
T-G
R-G
BALANCE
CAP 100 %
LOOP LENGTH = 9100 FT
LONG 65 DB
VER 0B: CPE or HIGH RESISTANCE

OPEN
Overview
LoopCare did not detect any obvious trouble on the line, however, it did find either
a CPE termination or a high resistance open on the line. In most cases this will
indicate that it is a CPE termination. The remote possibility exists however, that it
could be a high resistance open problem.
LoopCare sets VER 0B when it finds the termination through the Breakthrough
CPE Detection tests. See the System Description for more information on this
feature.
2-6
VER 0C: CPE or HIGH RESISTANCE

OPEN
Overview
LoopCare did not detect any obvious trouble on the line, however, it did find either
a CPE termination or a high resistance open on the line. In most cases this will
indicate that it is a CPE termination. The remote possibility exists however, that it
could be a high resistance open problem.
Additional
Information
This example is a TEST OK for a single party line, Centrex lines, Key Systems,
and loop-start PBX lines with CPE termination. These lines may or may not have
line records. Note the CRAFT and LoopCare DC signatures show high
resistances (3500 Kohms) and low voltage (0 Volts). The message "CPE or HIGH
RESISTANCE OPEN" is shown because of the remote possibility that there is a
high resistance open condition on the line. It should be noted that a ringer
configuration test is not performed here.
The central office check indicates that the line circuit arrangement of battery and
ground was valid and LoopCare was able to draw and break dial tone properly. In
addition, the capacitive balance (100%) and the longitudinal balance (65 DB)
were both good. Finally, the length of the loop is given as the last piece of
information about the line.

Overview
LoopCare has detected either an open condition or an xDSL termination with an

AC signature similar to that of an open condition on the loop. It has been
determined that the open is in or very close to the Central Office. There is an
offset value (in feet) stored in the computer for each test unit. If the open is
detected within this offset limit, it is considered an open in. An open is a physical
break in the line.
Example

KOHMS VOLTS
KOHMS VOLTS
KOHMS
3500
T-R
3500
T-R
2000
T-R
3500
0 T-G
3500
0 T-G
1267
T-G
3500
0 R-G
3500
0 R-G
1038
R-G
2-8
VER 0E: OPEN OUT BALANCED OR

DSL TERM
Overview
LoopCare has detected either an open condition or an xDSL termination with an

AC signature similar to that of an open condition on the loop. It has been
determined that the open is out of the Central Office. The capacitive balance,
which indicates the difference between the capacitance in each side of the line, is
99% or better.
Example

KOHMS VOLTS
KOHMS VOLTS
KOHMS
3500
T-R
3500
T-R
2000
T-R
3500
0 T-G
3500
0 T-G
1267
T-G
3500
0 R-G
3500
0 R-G
1038
R-G
VER 0H: ROH DETECTED DURING

TEST
Overview
VER 0H denotes that an open loop condition was found during testing and that an
ROH condition occurred during the test. This is an indication that there is a
undetectable CPE on the loop and that it went off-hook during testing. This
condition could be caused by a FAX or Answering machine or a human.
When this condition occurs, the data from the Central Office portion of the test is
discarded because of the unexpected short on the loop. Run a CO test to
determine the validity of the line circuit and dial tone. If the CO test passes, treat
the VER 0H same as a VER 0. Running a LOOP test by itself results in a VER 41
or other open VER code. This is normal. The loop should be considered
terminated with an undetectable CPE.
Example

USE CO REQ FOR LINE CKT & DIALTONE
2-10
VER 0L: NO FAULTS TO

BENCHMARKED LENGTH
Overview
When a test returns a VER41 (OPEN OUT BALANCED) for a POTS test
(narrowband only) and the loop length is within tolerance of the BENCH result in
the BMDB, the VER code is changed to 0L.
For information on loop length tolerance, see the BMDB section of the OA&M
Guide.
Example
VER 0L: TEST OK

NO FAULTS TO BENCHMARKED LENGTH
VER 0M: TEST OK MTU

Overview
VER 0M (zero M) is used by LMOS on the TR and DMLT masks and by ADSL
Pre-qualification tests to indicate a TEST OK condition on a line that has a
Maintenance Termination Unit (MTU). In LMOS, this VER code is used for
flowthrough.
EXAMPLE
VER 0M: TEST OK MTU
2-12

Overview
LoopCare has analyzed a marginal DC fault on the line under test and determined
that there is a high probability that it does not affect service. This VER code
should be treated as a TEST OK and an attempt should be made to close out any
trouble report.
EXAMPLE

VER CODE MAPPED FROM VER <CODE>
VER 0R: TEST OK

Overview
This is an otherwise Test OK result where the results are sufficiently different from
the BENCH result in the Benchmark Database to remove existing data about the
circuit. Candidate VER CODES for rebenching are all "0" VER codes and 41 and
46. The conditions under which a circuit is rebenched can be found in the BMDB
Re-Bench section of the System Description and the BMDB section of the OA&M
Guide.
Example
VER 0R : TEST OK
BENCHMARK DATA STORED
KOHMS VOLTS KOHMS VOLTSKOHMS RNGRS
3500
T-R
3500
T-R
9
Y T-R
3500 0 T-G
3500 0 T-G
2000
T-G
3500 0 R-G
3500 0 R-G
2000
R-G
2-14
VER 0T: OUT OF TOLERANCE

CONDITION
Overview
This VER code is displayed on the TV mask when the FULL/LOOP test result for
a TN differs from the Benchmark by a user-configured pre-set threshold.
Measured parameters include Loop Length, Capacitive Balance, and any of the
three AC Impedances.
One of the following summary messages may also appear with VER 0T:
Additional
Information
AC IMPEDANCE IS OUT OF TOLERANCE
CAPACITIVE BALANCE IS OUT OF TOLERANCE
Refer to the LoopCare Test Requests User Guide for detailed information and
procedures.
VER 05: TEST OK - CHANNEL NOT

TESTED
Alternative
With the Reclassify VER Code 5x feature turned on, the message is as follows:
TEST OK - CHANNEL TESTS IGNORED
Label
VER_05 (zero five) is applicable to all switches and applies to both integrated and
universal DLC loops. It indicates that all metallic tests passed, but that the
channel test was either not made, didn't complete in time or the returned results
did not match the acceptable signatures. It does not mean that the channel is bad.
For IDLC in 5ESS switches, it may be an indication that there may be a shortage
of transmission test facility (TTF) responders (The TTF performs the ISLC
channel tests). If the VER 55-58 reclassification feature is enabled, VER 55-58
codes will be changed to VER 05 with a summary message of TEST OK CHANNEL TESTS IGNORED. Use the V55 override to disable this feature.
Exclusions
This VER Code applies to the LTF, LTS, DCTU and CMU test heads. With this
VER Code, the RSA may be able to arrange a front end close out as no trouble
affecting the loop has been identified.
Example
VER 05 : TEST OK - CHANNEL TESTS IGNORED

3500
T-R
3500
T-R
11 YES T-R
3500 0 T-G
3500 0 T-G
1959
T-G
3500 0 R-G
3500 0 R-G
1962
R-G
BALANCE
CAP 100 %
LONG 65 DB
2-16
VER 6: BUSY-SPEECH
Overview
The system found the line busy with what it identifies as conversation on
the line. Testing is stopped at this point.
Additional
Information
Hold the trouble until the customer is finished talking on the line, then retest the
line with the LoopCare.
See Also
VER codes related to VER 6 (BUSY- SPEECH) are listed below:

VER 61
LINE IN USE
VER 11: CROSS TO WORKING PAIRFAULT

Overview
DC foreign voltage (battery) was detected on the line. This can be caused by DC
current flowing from one line to another, as can happen if exposed wires from the
lines touch or come close. The side of the line that is crossed usually has a low
resistance to ground. A cross is usually a cable trouble, that is where lines are
most likely to come in contact.
Example
VER 11 :CROSS TO WORKING PAIR: RING SIDE

MODERATE BATTERY R-G - 9 V
3500
T-R
3500
T-R
9
1 T-R
3500 0 T-G
3500 0 T-G
4500
T-G
3500 0 R-G
3500 0 R-G
4600
R-G
VER 11: CROSS TO WORKING PAIR: RING SIDE
MODERATE BATTERY R-G - 9 V
CRAFT: DC SIGNATURE
Additional
Information
MLT: DC SIGNATURE
KOHMS VOLTS
KOHMS VOLTS
1676
T-R
3500
T-R
1633
T-G
2801
0 T-G
117
389
-9 R-G
415
-46 R-G
AC SIGNATURE
KOHMS
98
RNGRS
Y T-R
T-G
R-G
LoopCare identifies a cross in the following manner:
First the LoopCare DC SIGNATURE must fit the thresholds given below:
RESISTANCE
VOLTAGE
> 10 K T-R
2-18
> 1 K T-G
> 20 V T-G and/or
> 1 K R-G
> 20 V R-G
If the LoopCare DC SIGNATURE indicates a CROSS, then the CRAFT DC

VOLTAGE is calculated. If the CRAFT voltage is greater than the locally
determined fault threshold, then this condition is a CROSS FAULT (VER
11).
If the CRAFT VOLTAGE is below the locally established fault value, then
the condition is a CROSS MARGINAL (VER 14).
The locally settable CRAFT voltage threshold is adjusted from the SAM mask via
the CT request. The default value is -6 volts.
Note the relationships between the LoopCare DC VOLTAGE, the LoopCare DC
RESISTANCE, and the CRAFT DC VOLTAGE. The CRAFT DC VOLTAGE is less
than the LoopCare DC VOLTAGE (-9 to -46 respectively R-G). This difference is
due to the way the measurements are made to calculate each voltage. Simply
stated the LoopCare DC VOLTAGE gives you the actual amount of voltage
present on the line. The CRAFT DC VOLTAGE gives you the amount of voltage
on the line that is measured across the DC resistance. It is actually what a craft
meter would see if the measurement was made next to the Loop Test System of
LoopCare. The lower the resistance the more CRAFT DC VOLTAGE will be found.
The higher the resistance the less CRAFT DC VOLTAGE will be found. Therefore,
as the DC resistance approaches 0, the CRAFT and LoopCare DC VOLTAGE
values will be closer.
A cross is usually a cable problem. This makes sense when you realize the most
likely place for two telephone pairs to come in contact is in the cable where they
are bundled together.
See Also
VER codes related to VER 11 (CROSS FAULT) are listed below:

VER 14 (CROSS MARGINAL)
VER 15 (DC FEMF MARGINAL)
VER 17 (RESISTIVE FAULT AND DC FEMF)
VER 18 (OPEN OUT AND CROSS)

Overview
An AC foreign voltage greater than the locally determined fault value (default
value is 25 volts) was detected on the line. The locally settable AC foreign voltage
(FEMF) value is changed from the SAM transaction via the CT request.
This condition could be caused by a cross with a power line, or AC induction due
to telephone lines being close to power lines.
Additional
Information
If this trouble is dispatched to a repair person, that person should be advised to

use caution when working on the line. Anytime there is AC voltage on the line
there is a potential danger.
See Also
VER codes related to VER 12 (AC FEMF FAULT) are listed below
2-20
VER 13
HAZARDOUS POTENTIAL
VER 16
AC FEMF MARGINAL

Overview
The preliminary LoopCare tests on the line indicate that there is a potentially
dangerous amount of voltage on the line ( > 150 Volts DC or 53 Volts rms AC).
When LoopCare identifies this condition, it will stop testing.
Additional
Information
Hazardous potential could be caused by a high voltage surge on a line due to a

number of conditions, including a cross with a power line or lightning striking the
line. The LoopCare equipment will remain attached to the line, but all further test
requests will only check to see if the Hazardous Potential is still present.
This condition could be potentially dangerous. It is important that you warn any
craft person working with the line of the possible hazard.
Example

DANGER- ADVISE SUPERVISOR
USE EXTREME CAUTION
See Also
VER codes related to VER 13 (HAZARDOUS POTENTIAL) are listed below:

VER 12 AC FEMF FAULT
VER 16 AC FEMF MARGINAL
VER 14: CROSS TO WORKING PAIR:

MARGINAL
Overview
LoopCare detected the presence of DC foreign voltage (also called foreign

battery) below the fault level (marginal) on the line. This is caused by DC current
flowing on the line from another telephone line. The source of the voltage is the
CO battery of the other line. The battery can be present tip to ground, ring to
ground or both. The side of the line that has the battery will usually have low
resistance (a ground).
Additional
Information
LoopCare identifies a cross in the following manner:

First the LoopCare DC SIGNATURE must fit the thresholds given below:
RESISTANCE
VOLTAGE
> 10 K T-R
> 1 K T-G
> 20 V T-G and/or
> 1 K R-G
> 20 V R-G
If the LoopCare DC SIGNATURE indicates a CROSS, then the CRAFT DC

VOLTAGE is calculated. If the CRAFT voltage is greater than the locally
determined fault threshold, then this condition is a CROSS FAULT (VER
11).
If the CRAFT VOLTAGE is below the locally established fault value, then
the condition is a CROSS MARGINAL (VER 14).
The locally settable CRAFT voltage threshold is adjusted from the CRSB
mask. The default value is -6 volts.
Note the relationships between the LoopCare DC VOLTAGE, the LoopCare DC

RESISTANCE, and the CRAFT DC VOLTAGE. The CRAFT DC VOLTAGE is less
than the LoopCare DC VOLTAGE (-3 to -46 respectively R-G). This difference is
due to the way the measurements are made to calculate each voltage. Simply
stated the LoopCare DC VOLTAGE gives you the actual amount of voltage
present on the line. The CRAFT DC VOLTAGE gives you the amount of voltage
on the line that is measured across the DC resistance. Actually, this measurement
is what the craft meter would see if the measurement was made next to the Loop
Test System of LoopCare. The lower the resistance the more CRAFT DC
VOLTAGE will be found. The higher the resistance the less CRAFT DC VOLTAGE
will be found. Therefore, as the DC resistance approaches 0, the CRAFT and
LoopCare DC VOLTAGE values will be closer.
2-22
A cross is usually a cable problem. This makes sense when you realize the most
likely place for two telephone pairs to come in contact is in the cable where they
are bundled together.
See Also
VER codes related to VER 14 (CROSS MARGINAL) are listed below:

VER 11 (CROSS FAULT)
VER 15 (DC FEMF MARGINAL)
VER 17 (RESISTIVE FAULT AND DC FEMF)
VER 18 (OPEN OUT AND CROSS)

Overview
The LoopCare DC VOLTAGE detected on the line was between -8 and -20 volts.
In addition, no other problems are found on the line. Note that while the CRAFT
DC VOLTAGE values will be displayed in the summary, it is the LoopCare DC
VOLTAGE values that identify this condition.
Additional
Information
A VER 15 (DC FEMF MARGINAL) is probably a cable trouble. This condition is

very similar to both CROSS TO WORKING PAIR conditions (VER 14 and 15)
since it indicates that foreign DC battery is on the line. The distinction of this
condition is that the LoopCare DC VOLTAGE does not match the expected
voltage of the LoopCare DC SIGNATURE for a cross. LoopCare expects to see
an LoopCare DC VOLTAGE greater than 20 volts in order to call the trouble a
cross. In this case the LoopCare DC VOLTAGE will never be greater than 20 volts.
Basically, VER 15 (DC FEMF MARGINAL) is usually a cross-like condition with a
small amount of voltage on the line. The LoopCare DC RESISTANCE on the side
of the line with the voltage, while below 3500 K ohms, is usually close to or above
1000 K ohms. DC resistances in this range will result in some voltage on the line,
but not much.
Because of the particular DC resistance range and the low amount of battery on
the line, this condition might be difficult for a craft person to locate in the field.
Follow local procedures when handling this type of trouble.
Example
VER15: DC FEMF MARGINAL

LONGITUDINAL NOISE 93 DB
KOHMS VOLTS KOHMS VOLTS
KOHMS RNGRS
2095
T-R
3500
T-R
9
Y T-R
2095
0 T-G
3500
0 T-G
2000
T-G
1378
-1 R-G
1716
-19 R-G
2000
R-G
See Also
VER codes related to VER 15 (DC FEMF MARGINAL) are listed below:
VER 11
2-24
CROSS FAULT
VER 14
CROSS MARGINAL
VER 17
RESISTIVE FAULT AND DC FEMF

VER 18

OPEN OUT AND CROSS

Overview
An AC foreign voltage less than the locally determined fault value (default value is
25 volts) but greater than the display threshold (15 volts). The locally settable AC
foreign voltage (FEMF) value is changed from the SAM transaction via the CT
request.
This condition could be caused by a cross with a power line, or AC induction due
to telephone lines being close to power lines.
Additional
Information
While there is not a great deal of AC voltage on the line, it may be appropriate to
inform the repair person that there is some foreign AC voltage on the line and to
use caution.
See Also
VER codes that are related to VER 16 (AC FEMF MARGINAL) are listed below:
2-26
VER 12
AC FEMF FAULT
VER 13
HAZARDOUS POTENTIAL
VER 17: RESISTIVE FAULT AND DC

FEMF
Overview
LoopCare has detected a stable resistive trouble (short or ground) that is below
the locally established fault threshold. In addition, the LoopCare DC VOLTAGE on
the line is greater than 8 volts.
Additional
Information
Many of the troubles that are grouped under this VER code are CROSS-like
conditions that did not match the LoopCare DC SIGNATURE of a cross for one of
the following reasons:
The T-R LoopCare resistance was > 10 K
The T-G and R-G LoopCare resistance was < 1 K
The LoopCare voltage on the line was > -20 V
Another case may be that the VER condition may be a LINE IN USE condition or
a PERMANENT SIGNAL condition that did not match the LoopCare DC
SIGNATURE for those conditions. To check for this possibility, match the
LoopCare DC SIGNATURE against what is expected for a LINE IN USE or a
PERMANENT SIGNAL condition. If the values are very close, you might suspect
that you have such a condition.
See Also
VER codes that are related to VER 17 (RESISTIVE FAULT AND DC FEMF) are
listed below:
VER 11 CROSS FAULT
VER 14 CROSS MARGINAL
VER 15 DC FEMF MARGINAL
VER 21 GROUND FAULT
VER 22 SHORT FAULT
VER 25 SHORT AND GROUND
VER 61 LINE IN USE
VER 73 LINE IN USE OR PERMANENT SIGNAL
VER 74 PERMANENT SIGNAL

Overview
LoopCare has detected an open on the line and has determined that the open is
out of the CO. In addition, a cross to a working pair has been detected.
If the line is served by a digital loop carrier system (DLCS) and is tested by a
Remote Measurement Unit (RMU), LoopCare has determined that the open is out
of the Remote Terminal (RT) of the carrier system.
Additional
Information
Usually, when there is more than one trouble on the line, they are related in some
way. One likely situation is that there is an open in the cable and the open wires in
the cable are crossed. Here, the open is causing the cross to working pair
condition.
This VER code is likely to reflect cable trouble. One likely possibility is that the line
is open and one or both of the open sides are crossed with another pair. This
could happen if the cable were cut and the open ends were contacting each other.
If the line is served by a DLCS and tested by an RMU, the distance provided by
LoopCare is measured from the RT of the DLCS. Since the "cable" of a carriersystem-served line is part of the carrier system, the fault would necessarily be
between the RT and the station for such lines.
See Also
The following VER codes are related to VER 18 (OPEN OUT AND CROSS):
VER 11 CROSS FAULT
VER 41 OPEN OUT BALANCED
VER 42 OPEN OUT CABLE
VER 45 OPEN OUT NEAR DROP
2-28

Overview
This condition indicates that the LoopCare DC RESISTANCE to ground (ringground and/or tip-ground) is below the locally settable fault threshold. The default
threshold for a ground fault is 150 K ohms. On a normal line the LoopCare DC
RESISTANCE to ground is high (usually > 3500 K ohms).
LoopCare will not display the AC SIGNATURE with DC resistance to ground less
than 50 Kohms. With this fault condition, VER code 21 will be displayed with either
an open or a termination.
Additional
Information
A ground condition can be caused when the insulation between wires of a pair is
worn down and the wires either come in contact with or establish an electrical path
to a grounded object. Most grounds occur outside of the central office. You can
assume that the ground is out of the central office on an LoopCare VER 21. When
the resistances are very low the trouble may be in or out of central office.
LoopCare, however, realizes this and in such cases recommends that you run an
MDF test to sectionalize the trouble.
On a regular plain old telephone line (POTS) the only valid path to ground is in the
central office line circuit on the tip and ring sides of the line. Any other path to
ground, unless specifically identified as being caused by CO, Outside Plant, or
Termination equipment, is a trouble.
When the customer goes off-hook the central office line circuit puts battery on the
line. This battery goes out from the CO on the ring side of the line and flows
between tip and ring at the receiver (ROH). It then completes the loop by returning
to the ground in the central office on the tip side of the line. If there is a path to
ground at any other point in the circuit then some or all of the current will leak out
of the loop. How much current leaks out of the loop depends on the severity of the
ground. The harder the ground the more current will leak out and the more severe
the trouble.
Sometimes the pair is grounded to another working telephone line. When this
happens we can identify this if the battery from the other pair is detected. This will
happen if we are crossed to the ring-side of the other pair. Remember the battery
is found on the ring side of the line. When this happens it is called a cross to
working pair. For more information see the module on VER 11 (CROSS TO
WORKING PAIR FAULT) or VER 14 (CROSS TO WORKING PAIR MARGINAL).
For an ISDN line with an NT1, when there is a hard fault on one side, a ghost fault
can appear on the other side. We will mask the light ghost fault and only display
the hard fault. If there is a double sided fault, only the hard fault will be displayed
and the other fault masked. Therefore, in this case, when the fault which was

displayed has been fixed and a retest is run, a fault could appear on the other
side. This is because there was initially a double sided fault.
See Also
VER codes related to VER 21 (GROUND FAULT) are listed below:

VER 17 RESISTIVE FAULT AND DC FEMF
VER 22 SHORT FAULT
VER 23 SWINGING RESISTANCE FAULT
VER 24 SWINGING RESISTANCE MARGINAL
VER 27 DC RESISTANCE MARGINAL
VER 95 RESISTIVE FAULT AND OPEN
2-30
VER 22: SHORT FAULT

Overview
This condition indicates that the LoopCare DC resistance tip to ring is below the
locally settable fault threshold. The default threshold for a short fault is 150
kohms. On a normal line the LoopCare DC resistance tip to ring is high (usually >
3500 kohms).
LoopCare will not display the AC SIGNATURE with short less than 50 Kohms.
With this DC fault condition, VER code 22 will be displayed with either an open or
a termination.
Additional
Information
A short condition can be caused when the insulation between wires of a pair is
worn down and the wires either come in contact with or establish an electrical path
with each other. Most shorts occur outside of the central office. You can assume
that the short is out of the central office on an LoopCare VER 22. When the
resistances are very low the trouble may be in or out of central office. LoopCare,
however, realizes this and in such cases recommends that you run an MDF test to
sectionalize the trouble.
A short allows a path for the central office current to go between tip and ring. The
only valid path between tip and ring is at the customer's phone when it is off-hook.
Any other short, unless specifically identified as being caused by CO, outside
plant, or termination equipment, is a trouble. When the customer goes off-hook
(ROH), the central office line circuit puts battery on the line. This battery goes out
from the central office on the ring side of the line and flows between tip and ring at
the receiver. It then completes the loop by returning to the ground in the central
office on the tip side of the line. If there is a short at any other point in the circuit,
some or all of the current will not reach the receiver but will take the shorter path
to the central office ground. How much current takes this shorter path depends on
the severity of the short. The harder the short the more current will take this path
between tip and ring instead of the short at the receiver.
See Also

VER 21 GROUND FAULT
VER 26 MDF TEST RECOMMENDED- LOW RESISTANCE
VER 71 ROH
VER 75 SHORT - PROBABLY ROH
VER 23: SWINGING RESISTANCE:

FAULT
Overview
LoopCare detects a ground below the locally established fault value but greater
than 10 K ohms. A SOAK test is then run on the line to determine the stability of
the ground (determines whether the DC resistances of the ground vary with time).
If the ground is not stable (a swinging condition), then LoopCare will display VER
23.
LoopCare will not display the AC SIGNATURE with DC faults less than 50 Kohms.
With this fault condition, VER code 23 will be displayed with either an open or a
termination.
Additional
Information
The SOAK test is used to determine the stability of resistive troubles to ground.
The SOAK test is run when the LoopCare DC RESISTANCE to ground (T-G or RG) is between 10 and 1000 K ohms. The SOAK test is not run if there is a short or
cross condition identified. Sometimes the ground problem may be due to some
temporary condition like a wet cable. As the cable dries, the trouble becomes less
severe.
The SOAK test puts voltage on the line and then takes six measurements of the
DC resistance. If the last of the six measurements is 20% greater than the DC
resistance measured before the SOAK test, LoopCare determines that the ground
is not stable (SWINGING). If the largest of the six measurements is greater than
2000 K ohms LoopCare indicates that the trouble has come clear (DRIED OUT).
See Also
VER codes related to VER 23 (SWINGING RESISTANCE- FAULT) are listed

below:
VER 21 GROUND
VER 24 SWINGING RESISTANCE- MARGINAL
2-32
VER 24: SWINGING RESISTANCE:

MARGINAL
Overview
LoopCare detects a ground above the locally established fault value but less than
1000 K ohms. A SOAK test is then run on the line to determine the stability of the
ground (determines whether the DC resistances of the ground vary with time). If
the ground is not stable (a swinging condition), then LoopCare will display VER
24.
Additional
Information
The SOAK test is used to determine the stability of resistive troubles to ground.
The SOAK test is run when the LoopCare DC RESISTANCE to ground (T-G or RG) is between 10 and 1000 K ohms. The SOAK test is not run if a short or a cross
condition is identified. Sometimes the ground problem may be due to some
temporary condition like a wet cable. As the cable dries, the trouble becomes less
severe.
The SOAK test puts voltage on the line and then takes six measurements of the
DC resistance. If the last of the six measurements is 20% greater than the DC
resistance measured before the SOAK test, LoopCare determines that the ground
is not stable (SWINGING). If the largest of the six measurements is greater than
2000 K ohms LoopCare indicates that the trouble has come clear (DRIED OUT).
See Also
VER codes related to VER 24 (SWINGING RESISTANCE- MARGINAL) are listed

below:
VER 21 GROUND FAULT
VER 23 SWINGING RESITANCE- FAULT

Overview
This VER code indicates that LoopCare has detected a short fault (DC resistance
tip to ring below the local fault threshold). In addition, one or both of the ground
DC resistances was below the local fault threshold. On a normal line all the
LoopCare DC resistances should be high (usually > 3500 K ohms).
With this fault condition, VER code 25 will be displayed with either an open or a
termination.
Additional
Information
A short or ground condition can be caused when the insulation on the telephone
wires is worn or becomes wet, exposing the wires. Most grounds and shorts occur
outside of the central office. You can assume that such a condition is out of the
central office on an LoopCare VER 25. When the resistances are very low the
trouble may be in or out of central office. LoopCare, however, realizes this and in
such cases recommends that you run an MDF test to sectionalize the trouble.
A short allows a path for the central office current to go between tip and ring. A
ground is a source that absorbs the central office current. The only valid path
between tip and ring is at the customer's phone when it is off-hook. The only valid
grounds are the tip and ring grounds in the central office line circuit. Unless the
line records indicate that there is CO, Outside Plant, or Termination equipment
that also cause low DC resistance, any other short or ground is a trouble.
When the customer goes off-hook the central office line circuit puts battery on the
line. This battery goes out from the CO on the ring side of the line and flows
between tip and ring at the receiver (ROH). It then completes the loop by returning
to the ground in the central office on the tip side of the line. If there is a short at
any other point in the circuit then some or all of the current will not reach the
receiver but will take the shorter path to the CO ground. Likewise, if there are any
other path to ground other than the ground in the CO, the current will leak off the
line before it can complete the circuit. How much current leaks from the circuit at
the ground or short fault depends on the severity of the resistive fault. The harder
the problem the more current will leave the circuit.
See Also
VER codes related to VER 25 (SHORT AND GROUND) are listed below:
VER 21 GROUND FAULT
VER 22 SHORT FAULT
2-34
VER 26: MDF TEST RECOMMENDEDLOW RESISTANCE

Overview
This VER code indicates that LoopCare has detected a short and/or ground(s) on
the line below the locally settable fault threshold. The default threshold for a
resistive fault is 150 kohms. In addition, the LoopCare DC resistance of one or
more of the troubles was low enough that LoopCare could not determine if the
trouble was in or out of the central office. Therefore, LoopCare recommends an
MDF test to sectionalize the problem in or out of the C.O.
The thresholds that determine whether or not the MDF test is recommended are
listed below. These thresholds represent the LoopCare DC resistance after the
test trunk resistances are subtracted. This subtraction is done by LoopCare and is
not displayed for the user. It is possible that this VER code could be set even if the
values in the LoopCare DC resistances are greater than those given below.
THRESHOLD FOR RECOMMENDING MDF TEST
Any one of these values could set VER 26.
T-R < 0.1 kohm
T-G < 0.07 kohm
R-G < 0.07 kohm
On a normal line all the LoopCare DC resistances should be high (usually > 3500
kohms).
Additional
Information
The LoopCare DC resistance values may be recorded for each central office
where an MDF test could be used. This would supplement the decision LoopCare
makes when it sets VER 26.
If the displayed LoopCare DC resistance value is between 0 and 100 ohms,
LoopCare recognizes the trouble as a short that may be within or outside the
central office (VER 26) and recommends an MDF test to sectionalize the trouble.
If the resistance value is between 100 ohms and 3.4 kohms, LoopCare may
determine that the trouble stems from an ROH condition (VER 71) or requires
manual confirmation of this (VER 75). If the resistance value is above 3.4 kohms,
LoopCare classifies the problem as a short between the central office and the
subscriber (VER 22).
See Also

VER 21 GROUND FAULT
VER 22 SHORT FAULT
VER 71 ROH
2-36
VER 27: DC RESISTANCEMARGINAL

Overview
This VER code indicates that LoopCare has detected a short or a ground
condition and the LoopCare DC RESISTANCE was above the locally settable fault
threshold, but below 1000 K ohms. This is a marginal condition, not a fault. On a
normal line the LoopCare DC resistances should be high (usually > 3500 K
ohms).
Additional
Information
wires is worn or becomes wet, exposing the wires. This exposure can provide a
path for current to escape from the loop.
paths to ground are the tip and ring grounds in the central office line circuit. Unless
the line records specifically indicate that there is CO, Outside Plant, or
Termination equipment on the line that can cause low DC resistance, any other
short or ground is a trouble. When the customer goes off-hook the current from
the central office line circuit battery flows on the line. This current goes out from
the CO on the ring side of the line and flows between tip and ring at the receiver
(ROH). It then completes the loop by returning to the ground in the central office
on the tip side of the line. If there is a short at any other point in the circuit then
some or all of the current will not reach the receiver but will take the shorter path
to the CO ground. Likewise, if there are any other path to ground other than the
ground in the CO, the current will leak off the line before it can complete the
circuit. How much current leaks from the circuit at the ground or short fault
depends on the severity of the resistive fault. The harder the problem the more
current will leak from the circuit.
In this case the ground is not a very severe problem, it is marginal (note the
summary message LIGHT SHORT). Repair people may have a more difficult time
locating the trouble since it is only a marginal one.
See Also
VER codes that are related to VER 27 (DC RESISTANCE MARGINAL) are listed
below:
VER 21 GROUND FAULT
VER 22 SHORT FAULT

Overview
A drop test was run on an POTS/ISDN-SDV or bPON line. The test failed due to
a possible short across the line circuit or a leakage to ground.
Example
2-38
VER 3: OPEN IN
Overview
LoopCare has detected an open condition and has determined that the open is in
or very close to the central office. An open is simply a physical break in the line.
There is an offset value (in feet) stored in the computer for each NNX. As a result
of this offset, an open that is outside the CO but very close to it will be identified as
an open in.
Note that LoopCare does not give a distance to the open when the open is in the
CO.
Example
VER 3: OPEN IN
KOHMS VOLTS
KOHMS VOLTS
KOHMS
3500
T-R
3500
T-R
2000
T-R
3500
0 T-G
3500
0 T-G
1267
T-G
3500
0 R-G
3500
0 R-G
1038
R-G
Additional
Information
The offset footage is designed to bias opens in favor of the CO when LoopCare
detects an open. This is because an open in the central office is handled by a
dispatch in. A dispatch in is less expensive than a dispatch out.8
See Also
VER codes related to VER 3 (OPEN IN) are listed below:

VER 35 OPEN IN AND CROSS
VER 38 POSSIBLE CO WIRING ERROR
VER 41 OPEN OUT BALANCED
VER 30: SWITCH COMMON EQUIP

BAD
Overview
When the status indicates that an ISDN line is taken out of service because either
the Integrated Services Line Unit (ISLU) or Packet Switching Unit (PSU) is not
functioning properly, VER 30 is returned with the appropriate summary message.
Additional
Information
VER_30 was added with the implementation of LoopCare/ISDN. The first

summary message that appears for this VER code is:
Additional summary messages that may appear with the VER code are as follows:
ISLU BAD
PSU BAD
SWITCH INDICATES ISDN SERVICE
Refer to LoopCare/ISDN Summary Messages for a brief description of each
Summary Message. The DSL Port Status messages associated with VER 30
depend on the actual summary message received. See the following chart:
Applicable Summary
Messages
ISLU BAD
DSL Status
D-OOS-FE-ISLU
B-OOS-FE-ISLU
PSU BAD
D-OOS-FE-PSU
B- OOS-FE-PSU
2-40

Overview
LoopCare checked the central office line circuit and the arrangement of battery
and ground was not what was expected based on the line record information.
Normally, the proper line circuit arrangement would be battery (with a ground) on
the ring side and ground on the tip side.
Another case that could cause this VER condition is if the line circuit was open on
both tip and ring sides.
r
Additional
Information
This condition is usually a central office problem.
See Also
VER codes related to VER 31 (INVALID LINE CKT ARRANGEMENT) are listed
below:
VER 36
LINE CKT AND DIAL TONE PROBLEM

Overview
LoopCare attempts to draw and break dial tone after it checks the central office
line circuit. In this VER condition, LoopCare was not able to draw dial tone within
the allotted 6 second interval.
Additional
Information
This VER condition is usually a central office problem. However, sometimes in

busy office situations (emergencies, etc.) the load on the office might cause a
delay in drawing or breaking dial tone. This delay may cause a VER 32 condition.
Example
VER 32: CAN'T DRAW DIAL TONE

CRAFT: DC SIGNATURE
MLT: DC SIGNATURE
KOHMS VOLTS
KOHMS VOLTS
3500
3500
T-R
T-R
3500
0 T-G
3500
0 T-G
3500
0 R-G
3500
0 R-G
CENTRAL OFFICE
LINE CKT OK
CAN'T DRAW DT
See Also
2-42
AC SIGNATURE
KOHMS
RNGRS
Y T-R
2000
T-G
2000
R-G
BALANCE
CAP 100 %
LONG 65 DB
VER codes related to VER 32 (CAN'T DRAW DIAL TONE) are listed below:
VER 33
CAN'T BREAK DIAL TONE
VER 36
LINE CKT AND DIAL TONE PROBLEMS
VER 37
DIAL TONE BURST DETECTED

Overview
LoopCare attempts to draw and break dial tone after it checks the central office
line circuit. In this VER condition, LoopCare was able to draw dial tone within the
allotted 6 second interval but it was not able to break dial tone within the 1 second
interval.
Example

CRAFT: DC SIGNATURE
MLT: DC SIGNATURE
KOHMS VOLTS
KOHMS VOLTS
3500
T-R
3500
T-R
3500
0 T-G
3500
0 T-G
3500
0 R-G
3500
0 R-G
CENTRAL OFFICE
BALANCE
LINE CKT OK
CAP 100 %
CAN'T BREAK DT
LONG 65 DB
AC SIGNATURE
KOHMS
RNGRS
Y T-R
2000
T-G
2000
R-G
Additional
Information
This VER condition is usually a central office problem. However, during busy
office conditions (emergencies, etc.) the load on the central office may cause
delays in attempts to break dial tone. Such delays could cause VER 33
conditions.
See Also
VER codes related to VER 33 (CAN'T BREAK DIAL TONE) are listed below:
VER 31
CAN"T DRAW DIAL TONE
VER 36
LINE CKT AND DIAL TONE PROBLEM
VER 37

Overview
This VER condition indicates that LoopCare could have made an improper access
to the line. LoopCare identifies this condition in the following manner. When
LoopCare identifies an OPEN IN condition, it checks for the central office line
circuit. If LoopCare "sees" the line circuit then it assumes the open in is valid. If
LoopCare does not "see" the line circuit, then the condition may be an open
between the test trunk and the line circuit or an invalid access to the line.
Example

KOHMS VOLTS
KOHMS VOLTS
KOHMS
3500
T-R
3500
T-R
35
T-R
3500
0 T-G
3500
0 T-G
2000
T-G
3500
0 R-G
3500
0 R-G
2000
R-G
Additional
Information
If LoopCare can't see the line circuit it is because either the open was between the
test trunk and the switch, or LoopCare hasn't accessed the line. If LoopCare
hasn't accessed the line, that means it is testing out over a test trunk with no
termination. When LoopCare tests this it looks like an open in. Since the test trunk
is not connected to the line or the switch there is no way that LoopCare can
access or see the central office line circuit (line identification in Crossbar offices).
Note that this condition is more common in Crossbar offices.
True invalid accesses are not frequent. If this VER code appears, you should drop
access (if you kept access from the TV mask) and retest it. If the access was bad,
then the next request should give you proper access to the line. If the VER 34 still
appears, then the access is good but the line is open between the test trunk and
the line circuit.
See Also
2-44
VER codes related to VER 34 (POSSIBLE INVALID ACCESS) are listed below:
VER 3
OPEN IN
VER 38
POSSIBLE C.O. WIRING ERROR

Overview
LoopCare has detected an open and has determined that the open is in or very
close to the central office. In addition, LoopCare has detected an LoopCare DC
SIGNATURE that matches the requirements for a cross to working pair.
> 10 K
T-R
> 1 K > 20 V T-G or

> 1 K > 20 V R-G
Additional
Information
This situation is usually a central office problem. What might happen is that the
pair is open at the frame and one of the open leads is grounded against
something in the central office. This ground can then cause battery from the
central office line circuit to be drawn out on the line. The combination of the
ground and battery causes a cross type signature.
See Also
VER codes that are related to VER 35 (OPEN IN AND CROSS) are listed below:
VER 11 CROSS FAULT
VER 3 OPEN IN
VER 36: LINE CIRCUIT AND DIAL

TONE PROBLEM
Overview
LoopCare has detected an invalid line circuit arrangement in the central office. In
addition, LoopCare can neither draw nor break dial tone from the central office.
Unless the records specify differently, the usual line circuit arrangement is battery
(with a ground) on the ring side and a ground on the tip side. Also LoopCare
should be able to draw dial tone within six seconds and break dial tone within one
second.
Additional
Information
This VER condition, which is not very common, indicates a central office problem.
See Also
VER codes related to VER 36 (LINE CKT AND DIAL TONE PROBLEMS) are
listed below:
2-46
VER 31
INVALID LINE CKT ARRANGEMENT
VER 32
CAN'T DRAW DIAL TONE
VER 33
CAN'T BREAK DIAL TONE
VER 37: DIAL TONE BURST

DETECTED
Overview
This VER code will appear on lines served by 1ESS, 2ESS, 5ESS, or DMS100 *
switches. If LoopCare can't draw dial tone, it checks for a one-second burst of
tone. This burst can be caused by one of the following conditions:
1.
Denied service
2.
Unigauge loop
3.
Remote make-busy key feature
4.
Voice Dialing Line.
The detection of the one-second tone prevents misleading draw- and break-dialtone results.
* As of the G3I1.0 Release of LoopCare, a new feature is available that identifies
switch types S-EWSD, FET150, AXE-10, SC-DCO, GTD-5 and NEAX. VER 37
will also appear on lines served by these switch types. Switch identification for
these switch types will default to DMS100 at locations that do not purchase this
feature.
Additional
Information
To prevent false dispatches from misleading line circuit tests, a check is made for
a one-second tone burst if it isn't possible to draw dial tone. The one-second burst
can be caused by a number of different things listed above. Check the line record
information to determine which condition exists. For example, if it turns out that
service is denied or there is a remote busy key feature, follow local procedures. If
the loop is Unigauge, a dispatch to the central office is probably the best action.
See Also
VER codes related to VER 37 (DIAL TONE BURST DETECTED) are listed below:
VER 32 CAN'T DRAW DIAL TONE
VER D1 DENIED SERVICE - TERMINATING
VER D2 DENIED SERVICE - ORIGINATING
VER D3 DENIED SERVICE
VER 38: POSSIBLE CO WIRING

ERROR
Overview
This VER code may have different meanings depending on the type of line being
tested (POTS or ISDN). If its a POTS line, then the line is served by a crossbar
switch. When LoopCare detects an open in on a crossbar line it attempts to
determine if the open in is valid. LoopCare monitors the line for a 480 HZ tone. If
the tone is detected, LoopCare decides that the OPEN IN is due to a wiring
problem in the office. It reports a VER 38. If the tone is not heard, LoopCare
reports a VER 3 - OPEN IN.
If the line being tested is an ISDN line, and a digital loopback test finds that the
problem is between the switch and the COT and not in the COT channel unit nor
in the line card, VER 38 with the appropriate summary message is returned.
Additional
Information
This VER code was created to reduce the number of false OPEN IN detections.
This condition occurs when the line is busy and the no-test connector is used to
cut through the busy line. However, the line is not properly accessed and an
invalid open in detection results. This problem is due to a CO wiring problem with
the no-test connectors. When this VER code appears, retest the line since the
chance of a second invalid access is remote. If the next test comes up with the
same VER code, then run a test with an MDF access. On a long term basis, the
bureau should keep track of the occurrence of VER 38 in crossbar offices to pick
up a wiring problem that occurs over time.
If this happens to be an ISDN line, then the testing has narrowed the problem
down to be somewhere between the switch and the COT.
VER_38 existed with LoopCare, but was enhanced with LoopCare/ISDN. The first
summary message that appears for the VER code is:
VER 38 POSSIBLE CO-WIRING ERROR
COULD BE COT CU
COULD BE CUSTOMER LOOP
COULD BE LINE CARD
COULD BE NT1
COULD BE RT CU
COULD NOT COMPLETE METALLIC TEST LINE RECORD
CONFIGURATION MISMATCH NO PDN AVAILABLE FOR METALLIC
ACCESS
2-48

Summary Message.
See Also
VER codes related to VER 38 (POSSIBLE CO WIRING ERROR) are listed below:
VER 3 OPEN IN
VER 39: CO EQUIP BAD - ISTF BAD LINE CARD BAD - PROTOCOL
HANDLER BAD
Overview
When the digital loopback test indicates that either the line card or the Integrated
Services Test facility (ISTF) or Protocol Handler (PH) is not functioning properly,
VER 39 with the appropriate summary message is returned.
Additional
Information
VER_39 was added with the implementation of LoopCare/ISDN.

The first summary message that appears for this VER code is one of the following:
VER 39: CO EQUIP BAD
VER 39: ISTF BAD
VER 39: LINE CARD BAD
VER 39: PROTOCOL HANDLER BAD
COULD BE CO-WIRING
COULD BE COT CU
COULD BE CUST PREM EQUIP
COULD BE LINE CARD
COULD BE NT1
COULD BE RT CU
COULD BE TDSL LOOP
COULD NOT COMPLETE METALLIC TEST
CO EQUIP BAD - ISTF BAD - LINE CARD BAD - PROTOCOL HANDLER
BAD
COULD NOT GAIN METALLIC ACCESS
DIGITAL TEST BUSY
ISTF BAD
LAYER 1 COUNT BAD
LAYER 1 PM COUNT CORRUPT
LAYER 1 PM GOOD
LINE RECORD CONFIGURATION MISMATCH
METALLIC TEST NOT RUN
METALLIC TEST OK
2-50
NO PDN AVAILABLE FOR METALLIC ACCESS

ONLY CIRCUIT SWITCHED TEST FAIL
PROTOCOL HANDLER BAD
Summary Message.

Overview
When a digital loopback test can not conclusively indicate that the switch
equipment has a problem but points toward the switch, VER 40 with a summary
message is returned. The summary message also indicates what other equipment
besides the CO equipment is suspect.
Additional
Information

VER 40: LINE CARD SUSPECT
VER 40: PROTOCOL HANDLER SUSPECT
CO-WIRING SPAN L1 PM BAD
COULD BE CO-WIRING
COULD BE COT CU
COULD BE NT1
COULD BE RT CU
COULD NOT COMPLETE METALLIC TESTING
DIGITAL TEST BUSY
Summary Message.
2-52

Overview
LoopCare has detected an open on the line and has determined that the open is
outside the central office. An open is simply a physical break in the telephone line.
In a balanced open, LoopCare estimates that the lengths of both sides of the line
are roughly the same. The capacitive balance, which indicates the difference in
capacitance between both sides of the line, is 99% or greater. The higher the
balance, the closer the lengths of each side match each other.
LoopCare also provides an estimate of the distance of the open from the central
office.
Remote Measurement Unit (RMU), then LoopCare provides an estimate of the
distance of the open from the Remote Terminal (RT) of the DLCS.
Example

KOHMS VOLTS
KOHMS VOLTS
KOHMS
3500
T-R
3500
T-R
2000
T-R
3500
0 T-G
3500
0 T-G
1267
T-G
3500
0 R-G
3500
0 R-G
1038
R-G
Additional
Information
In a balanced open, both sides of the line are roughly the same length. This
means either both sides of the line are open at the same place (the line is cut in
one place), or the open is on one side of the line but is very close to the
customer's termination. In this latter case, because one side of the line is open
very near the end, it is still very close to being as long as the other side which
continues to the customer's premises.
Balanced opens are usually open on both sides in the same place. There is no
direct way to tell whether the open is close to the station or back in the cable. The
distance of the open from the central office, however, can be helpful in pinpointing
the open more specifically.
See Also
VER codes related to VER 41 (OPEN OUT- BALANCED) are listed below:
VER 18 OPEN OUT AND CROSS
VER 3 OPEN IN

VER 42 OPEN OUT- CABLE
VER 44 OPEN OUT- 2 PTY OR BRIDGE LIFTER
VER 45 OPEN OUT- NEAR DROP
2-54

Overview
LoopCare has detected an unbalanced open on the line. When an open is

unbalanced, one side of the line is significantly shorter than the other one - and
that's usually because only one side is really open, the shorter one. LoopCare
uses capacitive balance to decide if the open is balanced or not. If the CAP BAL is
less than 99%, it calls the condition an unbalanced open. This can be an open in
the drop wire (Open Out Near Drop - VER 45) or an open in the cable (Open Out
in Cable - VER 42). (The drop is, by definition, the last thousand feet or so of the
metallic path. The cable is, by definition, the rest of the metallic path.)
When LoopCare sees an unbalanced open, it computes another measurement to
determine the location of the open - to see if it is open in the cable or in the drop.
LoopCare decides that the open is in the drop if one of the following is true:
1.
The CAP BAL is greater than 97% but less than 99%.
2.
The CAP BAL is greater than 95% but less than or equal to 97% and the
distance to the station is less than 500 feet.
If the CAP BAL is less than 99% and the above two conditions are not applicable,
the open is in the cable (VER 42).
The general idea is that the distance from the station to the open must be larger
than the distance from the CO to the open for the trouble to be in the cable.
LoopCare reports the side that is open and the distances from the open to the
station and CO, as well as the CAP BAL.
If the line is served by a digital loop carrier system and is tested by a Remote
Measurement Unit (RMU), then LoopCare makes its measurements from the
Remote Terminal (RT) of the digital loop carrier system. LoopCare uses the same
procedures, but now reports distances from the RT instead of from the CO.
Additional
Information
As mentioned above, the estimates of the open's distance from both the CO and
the station are displayed to the user. These should be helpful in coordinating a
repair person's search for the trouble.
See Also
VER codes related to VER 42 (OPEN OUT- CABLE) are listed below:
VER 18
OPEN OUT AND CROSS
VER 41
OPEN OUT- BALANCED
VER 44
OPEN OUT- 2 PT OR BRIDGE LIFTERS
2-56

VER 45
OPEN OUT- NEAR DROP
VER 95
RESISTIVE FAULT AND OPEN

Overview
LoopCare makes two AC tests to determine if there is an open on the line. The
first AC test is run with 10 volts, if an open is suspected from this test, the results
are stored and a second AC test is run. The second AC test is run with 60 volts. If
the AC resistance T-R for this 60 volt test is less than 20 k ohms or if there is no
value returned for the T-R AC resistance, a check is made for the DC resistance. If
the DC resistances are all greater than 1000 k ohms, then the VER code 43 is
displayed (high resistance open out).
An open is simply a physical break in the telephone line. in some cases, the break
in the line is not a clean one. This could happen if the problem is caused by
corrosion on the customer's line. Corrosion of the telephone pair may cause the
low voltage test to see an open condition but permits the high voltage test to see
the terminations. Such corrosion can cause intermittent problems with telephone
service.
In addition to the case of corrosion, a high resistance open message can indicate
one of the following:
1.
The customer has a single telephone with a high resistance ringer (for
example, a princess or trimline set).
2.
The customer has an illegal device which permits free long distance calls.
Additional
Information
One recommendation for handling a high resistance open is to be sure that the
line is really open. Try to call the customer. If you get through to the customer and
there are popping or cracking sounds on the line, the line could be going open. If
everything sounds fine there could be no problem. In either case, you might want
to retest again to be sure.
See Also
Because a high resistance open is a "marginal" or "intermittent" type of problem

that may come and go depending on the exact state of the line, a repair person
may have difficulty locating and clearing the open. VER codes related to VER 43
(OPEN OUT: HIGH RESISTANCE) are listed below:
VER 41 OPEN OUT- BALANCED
VER 44 OPEN OUT- 2 PTY OR BRIDGE LIFTERS
VER 44: OPEN OUT 2-PARTY OR

BRIDGE LIFTERS
Overview
LoopCare has detected an open and has determined that the open is outside the
central office (CO). An open is simply a physical break in the line. The line records
for this line indicate that it is a two-party service or has bridge lifters on it.
Because of the two-party service or the bridge lifters, no open measurements are
available for this condition. The capacitive balance and the distances calculated
from the capacitances can be distorted by the bridge lifters or equipment on a twoparty line. This distortion can produce wrong or misleading values. In order to
avoid this, no measurements are displayed. The open is outside of the CO, but
LoopCare cannot decide if the open is balanced or located in the cable or drop.
Remote Measurement Unit (RMU), then all measurements are made from the
Remote Terminal (RT) of the DLCS. Bridge lifters are not used with pair gain
systems. However, a two-party, RMU-tested line would give LoopCare
uncertainties that are similar to those with a two-party, LTS-tested line. Thus, no
length measurements are displayed in this case either.
See Also
VER codes related to VER 44 (OPEN OUT- 2 PTY OR BRIDGE LIFTER) are
listed below:
2-58

Overview
An open has been detected and it has been determined that the open is outsi the
Central Office, probably in or very near the drop wire, and that the difference in
length between the two sides of the line is marginal. The capacitive balance value
will be between 95% and 99%. This range indicates that the open is likely to be
back from the station in the drop wire or the cable just beyond the drop.
When LoopCare sees an unbalanced open, it computes another measurement to
determine the location of the open - to see if it is open in the cable or in the drop.
LoopCare decides that the open is in the drop if one of the following is true:
1.
The CAP BAL is greater than 97% but less than 99%.
2.
The CAP BAL is greater than 95% but less than or equal to 97% and the
distance to the station is less than 500 feet.
The general idea is that the distance from the station to the open must be smaller
than the distance from the CO to the open for the trouble to be in the drop.
LoopCare reports the side that is open and the distances from the open to the
station and CO, as well as the CAP BAL.
If the line is served by a digital loop carrier system and is tested by a Remote
Measuring Unit (RMU), then LoopCare makes its measurements from the Remote
Terminal (RT) of the digital loop carrier system. LoopCare uses the same
procedures, but now reports distances from the RT instead of from the CO.
The following summary messages may appear with this VER code:
OPEN - NO RINGER SEEN
This message may appear when a test request is performed on a
bPON line, among others, and VER 45 is the result.
OPEN - NO NT1 SEEN
Example
VER 45: OPEN OUT NEAR DROP- CAP BAL 98 %

DISTANCE FROM STATION 170 FT
DISTANCE FROM C.O. 14800 FT
CRAFT: DC SIGNATURE
KOHMS VOLTS
3500
T-R
MLT: DC SIGNATURE
KOHMS VOLTS
3500
T-R
AC SIGNATURE
KOHMS
1583
T-R

3500
3500
0 T-G
0 R-G
3500
3500
0 T-G
1146
0 R-G
876
T-G
R-G
Additional
Information
As mentioned above the estimates of the open's distance from both the CO and
the station are displayed. These should be helpful in coordinating a repair
person's search for the trouble. On display masks, the capacitive balance is
rounded to the nearest whole number.
See Also
VER codes related to VER 45 (OPEN OUT- NEAR DROP) are listed below:
2-60

Overview
LoopCare has tested a line with a Maintenance Termination Unit (MTU) on it. An
MTU is a device that may be installed near the customer's premises to help
LoopCare determine whether a trouble is located in the network or on the
customer's premises. In this case LoopCare has tested the line and recognizes
the electrical signature of the MTU. However, the termination on the line (ringer) is
not seen due to an open. Because LoopCare can "see" as far as the MTU it
assumes that the line has continuity to at least that point. Therefore, the open
must be beyond the protector on the customer's premises.
Additional
Information
Because the open is reliably located on the customer's premises no estimate of

the distance to the open from the CO or the station is made, however, if the Loop
Length Reporting Enhancement feature is on, a loop length will be reported for
this VER Code.
See Also
VER codes related to VER 46 (OPEN ON PREMISES) are listed below:

VER 45 OPEN OUT: NEAR DROP
VER 47: OPEN IN REMOTE

TERMINAL
Overview
LoopCare has detected an open condition when testing with a Remote

Measurement Unit (RMU), which is located in a SLC(TM)-96 remote terminal. The
remote terminal is located several miles outside the central office. LoopCare has
determined that the open is in or very close to the remote terminal. An open is
simply a physical break in the line.
There is an offset value (in feet) stored in the computer for each NNX. As a result
of this offset, an open that is outside the remote terminal but very close to it will be
identified as an open in remote terminal.
Note that LoopCare does not give a distance to the open when the open is in the
remote terminal.
This VER Code may also appear when the distance measured is 0-10% less than
the DLC calibration value configured in the OAM->RT WIRE CENTER->TG
Distance.
Example

KOHMS VOLTS
KOHMS VOLTS
KOHMS
3500
T-R
3500
T-R
2000
T-R
3500
0 T-G
3500
0 T-G
1267
T-G
3500
0 R-G
3500
0 R-G
1038
R-G
Additional
Information
The offset footage is designed to bias opens in favor of the remote terminal when
LoopCare detects an open.
See Also
VER codes related to VER 47 (OPEN IN REMOTE TERMINAL) are listed below:
VER 43 OPEN OUT: HIGH RESISTANCE
VER 45 OPEN OUT: NEAR DROP
2-62
VER 46 MAINTENANCE UNIT FOUND ON LINE

OPEN IN REMOTE TERMINAL
OPEN ON PREMISES
OPEN IN LTE

Overview
A T1 facility can exist between the Central Office Terminal (COT) and Remote
Terminal (RT), or between two D4 channel banks. When either the status returned
from the switch or the digital loopback indicates that the T1 facility is bad, VER 48
is returned.
Also, if the loopback test indicates that either the facility is provisioned for 64K
restricted or 56K restricted services and not for 64K clear services, LoopCare/
ISDN sees it as a problem, and VER 48 is returned with the proper summary
message. The ISDN BRI service should be provisioned for 64kbs clear channels.
Three types of data rates are tested by LoopCare/ISDN: 64K restricted (64R), 64K
clear (64C), and 56K restricted (56R). 64K clear is used to test the circuit
provisioned to support 64K-bps clear channel.
Additional
Information

The first summary message that appears for this VER code is:
CHANNEL PROVISIONED FOR 56R
CHANNEL PROVISIONED FOR 64R
COULD NOT COMPLETE METALLIC TEST LINE RECORD
CONFIGURATION MISMATCH NO PDN AVAILABLE FOR METALLIC
ACCESS STATUS SHOW LINK AFTER COT BAD
Summary Message.
CHANNEL UNIT X UNDER TEST (VER 48)
VER 48 is returned when the status of the line indicates that the DSL is taken out
of service because there is a test in progress somewhere on the line. If the DSL is
served by a digital carrier system, VER_48 is set to indicate where in the carrier
system maintenance activity is occurring.
Additional
Information

2-64
VER 48: CHANNEL UNIT X UNDER TEST

An additional summary message that may appear with the VER code follows:
LINE IS OUT OF SERVICE
Summary Message.
VER 50: COT CHANNEL UNIT

SUSPECT
Overview
When either the status, digital tests or metallic tests indicate that the trouble may
be in the COT channel unit, but can not conclusively say that the problem is the
channel unit, VER 50 with the appropriate summary message is returned.
Additional
Information

COULD BE RT CU
COULD BE T1 FACILITY
DIGITAL TEST BUSY
STATUS SHOWS CU HAS PROBLEM
Summary Message.
2-66
VER 51: CO BATTERY ON PAIR GAIN

SYSTEM
Overview
A busy (with no speech) condition is detected on a line on a DLC system off a

PGTC. Testing determines that there is voltage on the line not due to a line in use
or a permanent signal condition. LoopCare assumes that there is CO battery on
the pair gain access system. Testing is stopped and no metallic access is
attempted.
Additional
Information
This condition is a central office problem. It should be routed to the CO to clear.
See Also
VER codes related to VER 51 (C.O. BATTERY ON PAIR GAIN SYSTEM) are
listed below:
VER 52 INVALID PAIR GAIN CO SIGNATURE
VER 53 PAIR GAIN TEST ACCESS FAILURE - POSSIBLE BUSY
CONDITION
VER 54 PAIR GAIN SYSTEM FAILURE
VER 55 PAIR GAIN CHANNEL FAILURE
VER 52: INVALID PAIR GAIN CO

SIGNATURE
Overview
Prior to metallic access LoopCare attempts to identify the CO signature for the
UDLC or IDLC equipment. If the CO signature that is identified is not one that is
expected, LoopCare will call the signature invalid and this summary will be set.
Testing is stopped and no metallic access is attempted.
Additional
Information
This condition could exist due to a record error. The UDLC or IDLC equipment
may not be on the line as the records indicate or the service may not be the one
indicated in the records. Determine whether or not the records are correct. If they
are not, follow local procedures for correcting them. If they are correct and there is
an invalid CO signature, the problem is most likely in the central office.
When the DLC Testing Feature (DLC testing independent of line records) is used,
you may notice a significant decrease in the number of VER codes 52 and U6
(UNEXPECTED UNIVERSAL (INTEGRATED) PAIR GAIN SYSTEM being
displayed because, with the feature turned on, line records will be used less in
testing.
See Also
VER codes related to VER 52 (INVALID PAIR GAIN CO SIGNATURE) are listed
below:
VER 51 CO BATTERY ON PAIR GAIN SYSTEM
CONDITION
2-68
VER 53: PAIR GAIN TEST ACCESS

FAILURE -POSSIBLE BUSY
CONDITION
Overview
LoopCare cannot establish metallic access on the pair gain line to be tested. This
is either because someone else is using the metallic access path, or the access
path is defective at some point. Testing is stopped and no further test access is
attempted. LoopCare automatically drops access to the line.
Additional
Information
Since there is a possible busy condition, retest the line to check if access is
available. However, if the VER 53 result re-occurs, it is likely that the metallic
access path is defective at some point. Possible causes are:
See Also
Defective, wrong type, unplugged or missing CTU
Translations needed for integrated testing
Inhibit/SCSD leads not/improperly wired or translated
Defective or missing channel unit
Defective, unplugged or missing 28-lead PGTC cable
DLC common unit defective
Power unit missing in DLC system
VER codes related to VER 53 (PAIR GAIN TEST ACCESS FAILURE POSSIBLE BUSY CONDITION) are listed below:
VER 51 C.O. BATTERY ON PAIR GAIN SYSTEM
VER 52 INVALID PAIR GAIN C.O. SIGNATURE
VER 54: PAIR GAIN SYSTEM

FAILURE
Overview
LoopCare cannot make metallic access on the pair gain system because of either
a major alarm or some other failure in the system. Testing is stopped.
When a VER Code 54 is generated, LoopCare will automatically drop access to
the line.
Additional
Information
There are four possible modifying messages with this VER code:
1.
*DUE TO TEST SYSTEM FAILURE

This means LoopCare has seen some unidentified system failure. For
example, this could be a problem with the COT channel unit, or with the
wiring in the CO.
2.
*DUE TO MAJOR ALARM

LoopCare has seen that the DLC system is in Major Alarm. This means
that this is a facility failure and a number of customers are affected.
3.
*DUE TO MAJOR ALARM OR BUSY ACCESS SYSTEM

LoopCare determined that the system is either in major alarm or is busy.
You should probably try to run this test again in a few minutes to see if it
was indeed just busy. If you get this message repeatedly, it probably
means that the DLC is in major alarm, and you should act accordingly.
See Also
VER codes related to VER 54 (PAIR GAIN SYSTEM FAILURE) are listed below:
CONDITION
VER 56 BAD COT CHANNEL UNIT
VER 57 BAD RT CHANNEL UNIT
VER 58 BAD COT AND RT CHANNEL UNIT
2-70
VER 55: PAIR GAIN CHANNEL

FAILURE
Overview
If metallic access is made, LoopCare conducts its regular testing. Meanwhile, the
Digital Loop Carrier (DLC) conducts a self test to determine the condition of the
digital carrier channel. If this self check indicates a failure, this VER code is set.
Additional
Information
This problem is most likely a central office problem and should be dispatched to
them.
See Also
VER codes related to VER 55 (PAIR GAIN CHANNEL FAILURE) are listed below:
CONDITION
VER 58 BAD COT AND RT CHANNEL UNIT
VER 56: BAD PAIR GAIN COT

CHANNEL UNIT
Overview
If the condition of the digital carrier channel indicates a failure at the Central Office
Terminal (COT), VER 56 is returned. The condition of the digital carrier channel is
determined by a Digital Loop Carrier (DLC) self-check. This VER Code is only
returned for SLC lines which use the Extended Test Controller (XTC) on either
POTS or ISDN lines.
Additional
Information
VER COT CU BAD
COULD BE NT1
COULD BE RT CU
DIGITAL TEST BUSY
Summary Message.
See Also
VER codes related to VER 56 (BAD COT CHANNEL UNIT) are listed below:
CONDITION
VER 58 BAD COT/RT CHANNEL UNIT
2-72

Overview
If the condition of the digital carrier channel indicates a problem in the RT channel
unit, VER 57 is returned. The condition of the digital carrier channel is determined
by a Digital Loop Carrier (DLC) self-check. VER 57 can be returned for either
POTS or ISDN lines.
Additional
Information
CHAN TEST FAIL - RINGING
CHAN TEST FAIL - OFF HOOK
CHAN TEST FAIL - RETURN LOSS
CHAN TEST FAIL - NOISE
CHAN TEST FAIL - CHAN LOSS
Summary Message.
VER 58: BAD COT AND RT CHANNEL

UNITS
Overview
If metallic access is made, LoopCare conducts its regular testing. Meanwhile, the
Digital Loop Carrier (DLC) conducts a self test to determine the condition of the
digital carrier channel. If this self check indicates a failure at the COT and RT, this
VER code is set.
Additional
Information
This VER code is the result of enhanced channel diagnostics which will only be
run on certain DLC systems, e.g., SLC Series 5.
See Also
VER codes related to VER 58 (BAD COT AND RT CHANNEL UNITS) are listed
below:
VER 52 INVALID PAIR GAIN CO SIGNATURE
CONDITION
2-74
VER 59: RT CHANNEL UNIT

SUSPECT
Overview
When digital or metallic tests indicate that a problem may exist at the RT channel
unit but cannot confirm it, VER 59 with the appropriate summary message is
returned. In such cases, other equipment and not the RT CU could be bad. The
summary message indicates what else could be suspect.
Additional
Information
VER_59 was added with the implementation of /ISDN. The first summary
message that appears for this VER code is:
VER 59: RT CU SUSPECT
COULD BE NT1
DIGITAL TEST BUSY
T1 FACILITY L1 PM BAD
ONU EQUIPMENT FAILURE
Summary Message.
VER 60: BUSY PACKET

Overview
The switch denies access to the system's ISDN software for a test, because
the requested test channel is busy with packet traffic.
Example
VER 60 : BUSY PACKET

BENCHMARK DATA STORED
3500
T-R
3500
T-R
11 YES T-R
3500 0 T-G
3500 0 T-G
1469
T-G
3500 0 R-G
3500 0 R-G
1336
R-G
2-76
VER 61: LINE IN USE

Overview
LoopCare has determined that the line was being used at the time of testing, but
no speech was detected. Further analysis showed the Line In Use signature for
the switch in question. This condition can occur for all switch types (see below for
the different LIU signatures).
Additional
Information
In step-by-step offices, a VER 61 indicates a "called party" line in use. This

condition is defined as the case where LoopCare tests the called party and a talk
path is established but no speech is detected.
The following signatures define this VER Code:
SWITCH
1,2 & 3 ESS
LoopCare
RESISTANCE
LoopCare VOLTAGE
0 to 3500 K T-R
-36 to -75 Volts one side to ground
07 to 1.2 K T-G
+15 to -15 Volts other side to ground
07 to 1.2 K R_G
SXS
> 200 K T-R
1 & 5 XBAR
0 to 2.5 K T-G
< 3V T-G
> 200 K R-G
< 3V R-G
< 10 K T-R
0 to 1 K T-G
0 to 1 K R-G
On a Crossbar switch an additional check is made for a 500 Hz permanent signal.

If this signal is not detected, a line in use condition exists. If it is detected,
permanent signal is identified and an ROH test is attempted.
See Also
VER codes related to VER 61 (LINE IN USE) are listed below:

VER 72 MDF TEST RECOMMENDED- PERM SIGNAL

Overview
When status of the Digital Subscriber Line (DSL) indicates that it has been taken
out of service because a person is doing maintenance work on it, VER_63 is
returned. The status returned by the switch can be:
D-OOS-MAIN DIS (D-channel is out of service, disabled for maintenance)
B-OOS-MAIN DIS (B-channel is out of service, disabled for maintenance)
D-OOS-MANUAL REMOVE (D-channel is out of service, manually
removed)
Additional
Information

DSL OUT OF SERVICE
USER MANUALLY OUT OF SERVICE
Summary Message.
2-78
VER 71: RECEIVER OFF HOOK

(ROH)
Overview
When LoopCare sees an initial busy condition, it also see a short. LoopCare
thinks that the line is being used, but no speech was detected. It then checked for
a Line In Use or Permanent Signal condition, but didn't find one. Next it runs the
receiver-off-hook (ROH) test and an ROH condition was detected. (This condition
will exist only if the DC resistance value falls between 100 ohms and 3.4 kohms.)
No further tests are performed.
Additional
Information

Example
VER 71: BUSY- NO SPEECH

ROH
See Also
VER codes related to VER 71 (ROH) are listed below:

VER 22 SHORT
VER 6 SPEECH
VER 61 LINE IN USE
VER 72 MDF TEST RECOMMENDED- PERM SIGNAL
VER 73 LINE IN USE OR PERM SIGNAL
VER 72: MDF TEST RECOMMENDEDPERMANENT SIGNAL

Overview
This VER code will appear on crossbar numbers that are equipped with 7AREGs.
First, LoopCare decides that the line is busy, but hears no speech. Then,
LoopCare detects permanent signal on the line, but cannot release the CO
battery. So, it recommends an MDF test.
Additional
Information
The MDF test is recommended so that the CO battery can be removed from the
line. When the line is accessed and tested from an MDF trunk (with a LOOP test
for example) the CO part of the line is physically removed from the circuit. This
allows the test to be made on the outside part of the line without interference from
the CO battery. The trouble can then be sectionalized. The following LoopCare
DC SIGNATURE will identify this condition:
SWITCH
1,5 XBAR
See Also
LoopCare
RESISTANCE
LoopCare VOLTAGE
< 10 K T-R
0 to 1 K T-G
0 to 1 K R-G
VER codes related to VER 72 (MDF TEST RECOMMENDED- PERMANENT

SIGNAL) are listed below:
VER 61 LINE IN USE
VER 71 ROH
2-80
VER 73: LINE IN USE OR

PERMANENT SIGNAL
Overview
LoopCare decided that the line was busy, but didn't see any speech. Next it
checks for permanent signal or line in use conditions. This VER Code will occur in
two conditions:
1.
Additional
Information
In a step-by-step office only -- either a line in use condition exists on the

line or a permanent signal is present. In the step-by-step, these two
conditions cannot be distinguished. If it is permanent signal, it is caused by
one of the following:
n
ROH (not detectable because line is not ROH-testable)
Resistive fault drawing in the line circuit.
2.
In either an SXS or ESS switching office -- if a busy signature is detected

and the T-R LoopCare DC RESISTANCE is between 0 and 3500 K ohms
3.
In a 5ESS office -- with a hard short of 0.1 to 3.4 K ohms, the ROH test
cannot always be run. When LoopCare detects this condition, this VER
code will be set. To investigate the problem further, run an MDF test.
This condition rarely occurs on a line served by an ESS office but occurs more
frequently on step-by-step. The signatures under which these messages will be
displayed are given below:
ESS, SXS
A busy signature was detected and the LoopCare

resistance is 0 to 3500 K T-R. This condition rarely
occurs in an ESS office.
The following LoopCare resistances and voltages are identified:
ESS only
LoopCare
RESISTANCE
0 to 3500 K T-R
.07 to 1.2 K T-R
LoopCare VOLTAGE
and +15 to -15 Volts other side to
ground.
.07 to 1.2 K R-G
SXS only
LoopCare
RESISTANCE
0 to 3500 K T-R
.07 to 1 K T-R
LoopCare VOLTAGE
and +22 to -22 Volts other side to
ground.
.07 to 1 K R-G
To determine if the permanent signal is caused by an ROH, you could attempt to
call the customer or monitor the line (with TV). If the ROH cannot be confirmed,
assume that the trouble is a resistive fault.
See Also
VER codes related to VER 73 (LINE IN USE OR PERMANENT SIGNAL) are

listed below:
VER 61 LINE IN USE
VER 72 MDF TEST RECOMMENDED- PERMANENT SIGNAL
2-82

Overview
In ESS and crossbar offices, LoopCare decides that the line is busy, but there is
no speech. Next, it checks for permanent signal and finds it. The permanent
signal is on the line because of a resistive fault or an ROH condition that
LoopCare cannot detect because the line is not ROH testable.
Additional
Information
The LoopCare DC SIGNATURES that identify a permanent signal condition are

listed below:
SWITCH
1,2,& 3 ESS
1,5 XBAR
LoopCare
RESISTANCE
LoopCare VOLTAGE
.15 to 3.4 T-R

> 150 K T-G
< 3 Volts T-G
> 150 K R-G
< 3 Volts R-G
< 10 K T-R

+10 to -10 Volts on the other side
0 to 1 K T-G
0 to 1 K R-G
To determine if the permanent signal is caused by an ROH try to call the customer
or monitor the line with the TV mask. If the ROH cannot be confirmed, assume
that the trouble is a resistive fault.
See Also
VER codes related to VER 74 (PERMANENT SIGNAL) are listed below:

VER 61 LINE IN USE
VER 71 ROH
VER 72 MDF TEST RECOMMENDED- PERMANENT SIGNAL

Overview
In all central offices except those with crossbar switches, LoopCare determines
that a tip-to-ring short exists if the resistance value on the displayed LoopCare DC
signature is below the locally settable fault threshold. (Default value for the
threshold is 150 kohms.)
If the resistance value is between 100 ohms and 3.4 kohms, LoopCare will run a
receiver-off-hook (ROH) test. If this test doesn't verify an ROH condition, it may
not be possible for LoopCare to determine directly whether the trouble is the result
of an off-hook receiver or a short. LoopCare then will display the VER 75
message, which asks that you verify the presence of an ROH condition either by
monitoring the line, checking with the subscriber, or following local procedures. If
an ROH condition apparently does not exist, you should then dispatch craft to
locate the trouble.
Additional
Information

See Also
VER codes related to VER 75 (SHORT - PROBABLY ROH) are listed below:
2-84
VER 22
SHORT FAULT
VER 26
MDF TEST RECOMMENDED- LOW RESISTANCE
VER 71
ROH
VER 80: DIAL OK

Overview
The LoopCare rotary dial test (DIAL) was run and the results indicate that the dial
was working properly. This means that the dial speed was correct (8 to 11 pulses
per second), and the percent break was within acceptable ranges (57 to 64
percent).
Additional
Information
The LoopCare rotary dial test is only available from the TV and TEST masks. As a
result this VER code will not appear on a basic or mini output report.
See Also
VER codes related to VER 80 (DIAL OK) are listed below:

VER 81
DIAL NOT OK
VER 81: DIAL NOT OK

Overview
The LoopCare rotary dial (DIAL) test has been run and a problem with the dial has
been detected. The problem could be with the dial speed (correct dial speed is 8
to 11 pulses per second), or the percent break (the correct range for the break is
57 to 64%). Remember, however, that the percent break may occasionally fall
within this range and the summary message will still say DIAL NOT OK. This is
because the break that is reported in the test results is an average for all 10
pulses. If even one fails, LoopCare will report that the dial was not ok, but the
average break may still fall within the acceptable range.
Additional
Information
The LoopCare rotary dial test is only available from the TV and TEST mask.
Therefore this VER code will never appear on a basic or mini output report.
See Also
VER codes related to VER 81 (DIAL NOT OK) are listed below:
VER 80 DIAL OK
2-86

Overview
C-message noise metallic and/or C-message noise longitudinal faults have been
found on the pair. C-message noise on the pair is measured in the units of
decibels reference nice (dBrnC) (decibels above reference noise, C-message
weighted) and subjected to the standard C-message filtering (~300 to 3,000 Hz).
C-message filtering is used because it is the normal voice frequency range of a
POTS line. Two measurements are made: longitudinal (noise to ground) and
metallic, and noise balance is calculated from them.
Example

LONGITUDINAL NOISE 93 DB
KOHMS VOLTS KOHMS VOLTS
KOHMS RNGRS
3500
T-R
3500
T-R
1583
Y T-R
3500
0 T-G
3500
0 T-G
1146
T-G
3500
0 R-G
3500
0 R-G
876
R-G

Overview
The LoopCare DC SIGNATURE was not what was expected for the type of PBX
termination indicated in the line record. A list of the valid LoopCare DC
SIGNATURES for PBXs is found in Appendix E - Valid DC Signatures.
Additional
Information
Check the LoopCare DC SIGNATURE that is displayed against the DC signature

expected for a 756 PBX. A 756 PBX should have the following LoopCare DC
SIGNATURES:
756 A option S
KOHMS
VOLTS
18-25
T-R
> 200
<3
T-G
> 200
<3
R-G
756 A option R
KOHMS
VOLTS
> 54
7-13
> 200
T-R
40-55
<3
T-G
R-G
The LoopCare DC SIGNATURE in the above example does not match a valid DC
signatures. The line record may be incorrect and the condition on the line might be
a fault.
See Also
VER codes related to VER 91 (INVALID PBX SIGNATURE) are listed below:
VER 92
INVALID AC SIGNATURE
VER U2
UNEXPECTED PBX SIGNATURE
Also refer to Appendix C (TERM EQUIPMENT EFFECTS), and APPENDIX E

(VALID DC SIGNATURES).
2-88

Overview
LoopCare has found that the AC SIGNATURE was not what was expected for the
type of equipment and services indicated in the line records. A list of the valid AC
SIGNATURES is provided in Appendix F (VALID AC SIGNATURES).
Additional
Information
Check the LoopCare AC SIGNATURE against the AC signature expected for a

Key System. A Key system should have the following AC signature:
KOHMS
2-18 T-R
> 25 T-G
> 25 R-G
In the example above, the AC resistance T-R is not within the 2-18 Kohm range,
thus causing the invalid AC signature.
If the AC signature displayed does not match the one expected, determine if the
AC signature matches any of the valid ones listed in Appendix F. It could be that
the line records are wrong but the termination is a recognizable one.
If the AC signature does not match any in Appendix F, then the condition might
indicate trouble on the line.
See Also
VER codes related to VER 92 (INVALID AC SIGNATURE) are listed below:

VER 91
INVALID PBX SIGNATURE
VER G1
POSSIBLE LONG LOOP
VER U3
UNEXPECTED RINGER TERMINATION
Also refer to Appendix C (TERM EQUIPMENT EFFECTS) and Appendix F

(VALID AC SIGNATURES).

Overview
LoopCare detects no major faults on the line except poor longitudinal balance
(below the locally settable fault threshold), and poor capacitive balance (less than
95%). This condition could be caused by one of the following:
ringer improperly connected to ground
cable imbalance due to bridge tap
incomplete line records (for example, if a line has a range extender (REG)
and the associated line record byte is missing, the line will look
unbalanced).
NOTE:
There is no longitudinal balance test for RMUs, CMUs, and REG units;
therefore this VER code refers to poor capacitance balance in the case of
RMUs, CMUs, and REG units. If the RMU is used, however, as a DMU-C or
DMU-R, then the longitudinal balance and soak tests will be performed.
Additional
Information
On a single party service this problem most likely could be handled by dispatching
someone to station.
On a two party line, the condition may be caused by one party having more
phones than the other. If this is the case some of the recommendations include:
See Also
Reassign parties
add C.O. bridge
add dummy ringers to the line to balance the ringers on each side.
VER codes related to VER 93 (POOR BALANCE) are listed below:

VER 96
2-90
MARGINAL BALANCE
VER 95: RESISTIVE FAULT AND

OPEN
Overview
LoopCare has detected one or more DC resistances below the locally settable
fault value (short or grounds). In addition, LoopCare has detected an open on the
line. Because of the effect of the resistive fault on the line, LoopCare may not be
able to tell if the open is in or out of the central office.
An open is simply a physical break in a telephone line. This can be the result of
corrosion on the customer's line, or other causes. Sometimes, the wires are
shorted together or have DC leakages to ground, as well. When these resistive
faults are present, the normal measurements that LoopCare makes of distance to
an open circuit can not be made reliably. In this case, LoopCare gives you a VER
95, with resistive faults between 50 Kohms and the level determined below
(usually 150 Kohms).
The level at which LoopCare decides not to measure the distance is set by a local
Facilities Manager in the telephone company. If the value is not set, then
LoopCare will use 150 Kohms.
If the line is served by a Digital Loop Carrier System (DLCS) and is tested by a
Remote Measurement Unit (RMU), then LoopCare makes its measurements from
the Remote Terminal (RT) of the DLCS. Thus, since LoopCare can only measure
"out" from the RT, LoopCare knows that the fault is at or beyond the RT.
Additional
Information
It is likely that both troubles are related. If the values of the resistive fault are large
enough to indicate that the fault is outside of the CO (approximately > 2 Kohms)
you can assume that the open is also out of the CO. If clearing one problem does
not lead to clearing the other, a subsequent test (post dispatch) will detect it.
See Also
VER codes related to VER 95 (RESISTIVE FAULT AND OPEN) are listed below:
VER 21 GROUND FAULT
VER 22 SHORT FAULT

Overview
LoopCare has detected no major faults on the line, but the longitudinal balance
was marginal (less than 65 DB but greater than the locally settable fault value,
which by default is 40 DB).
Additional
Information
The marginal balance is generally not a severe problem. However, depending on

the customer report, work load, and local policy, you can choose whether or not to
dispatch someone on this trouble.
See Also
VER codes related to VER 96 (MARGINAL BALANCE) are listed below:

VER 93
2-92
POOR BALANCE
VER 97: DERIVED PR NOT TESTEDPHYSICAL PR NOT SERVED

Overview
LoopCare is requested to test a derived pair. However, the derived pair cannot be
tested because the physical pair is on a line not served by LoopCare.
Additional
Information
If the derived pair cannot be tested because the physical pair is not served by
LoopCare, you should probably send the trouble to a bureau where the physical
pair can be test.
See Also
VER codes related to VER 97 (DERIVED PR NOT TESTED-PHYSICAL PR NOT

SERVED) are listed below:
VER NT TEST NOT MADE (NOT TESTED)
VER NV NOT VERIFIED (NOT TESTED)
VER 98: ANALYSIS OF FULL

RESULTS NEEDED
Overview
This VER code condition is a "catch-all" condition set when LoopCare does not
identify or set any VER code conditions in testing. As a default, VER 98 is
displayed to the user with the messages explaining that the detailed results
should be examined. One condition that might commonly set this VER code is the
case where the line is an uncataloged AC termination or a multiparty (4 or 8) line.
In these cases LoopCare does not know what the AC signature should look like
and does not attempt to classify the condition on the line. Instead it leaves the
analysis up to the user.
The summary messages and the detailed results should provide the necessary
information about the trouble.
Additional
Information
2-94
VER 98 is set because no VER condition is detected. There will be summary

messages to indicate what you should look at in the detailed test results to identify
the condition on the line. This means that you should examine the DC and AC
signatures and compare them against known valid signatures. Also look at other
information such as balance and central office information to identify any
particular pattern. Sometimes there are no test results or only incomplete test
results. This situation could be due to premature termination of testing. A good
suggestion in this case would be to retest the line in an attempt to get more
complete results. If, however, the same thing occurs and no test results are
available, follow local procedures.
VER 99: MULTIPLE FAULTS

DETECTED
Overview
This VER code condition is a "catch-all" for cases where LoopCare wants to return
more than one VER code. The summary messages and the detailed results will
provide the necessary information about the trouble.
Additional
Information
When VER 99 is set the summary messages should provide enough information
to identify the problems. There is such a wide range of conditions that could cause
VER 99 that it is not really practical to list the known ones here. In addition, there
are conditions that we really don't know about right now. As you work with
LoopCare you will find certain patterns of test results resulting in VER 99. It would
be a good idea to keep track of these cases, especially if the actions required to
handle them are similar.
2-96
Contents
3-4
3-5
3-6
3-7
3-8
3-9
3-10
VER AK: METALLIC TESTS NOT ALLOWED
3-11
3-12
3-13
3-14
3-15
3-16
VER AQ:VLAN PARAMETER MISMATCH
3-17
3-18
3-19
3-20
VER AU:HOSTNAME (DNS) TRANSLATION FAILURE
3-21
VER AV:ATM FAILURE - CHECK VPI/VCI
3-22
3-23
VER B0: TEST EQUIPMENT BUSY - TIME OUT IN ACCESS 3-24

3-25
VER B2: TEST EQUIPMENT BUSY - SANITY OR DIAG IN PROGRESS326

VER B3: TEST EQUIPMENT BUSY - SIMULTANEOUS TEST REQUEST
MADE3-27
3-28
VER B5: TEST EQUIPMENT BUSY - PAIR GAIN ACCESS EQUIPMENT

BUSY3-29
3-2
3-30
3-31
VER B8: ALL TRUNKS ARE BUSY BY OTHER USERS
3-32
3-33
3-34
3-35
3-36
3-37
3-38
3-39
3-40
VER BI: NO MTB TO PGTC AVAILABLE
3-41
VER BJ: NO MTB TO PGTC PORT AVAILABLE
3-42
VER BK: PGTC PATH SETUP BLOCKAGE (other)
3-43
3-44
3-45
VER BN: NO TEST PACKAGE AVAILABLE
3-46
3-47
3-48
VER BR: NO BUSY DETECTOR AVAILABLE
3-49
VER BS: SWITCH TEST ACCESS BLOCKAGE
3-50
VER BT: RMU IN USE
3-51
3-52
VER BV: NO MODEM PORT AVAILABLE
3-53
3-54
VER BY: LTE BUSY
3-55
3-56
3-57
3-58
3-59
3-60
3-61
VER C6: INITIAL RATE OR FRAUD CONTACT PROBLEMS 3-63

3-64
3-65
3-66
3-67
VER D4: DENIED CPE
3-68
3-69
3-70
3-71
VER DL: CONTROLLER-LTF OR FRONT END-LTS DATA LINK FAILURE

3-72
VER DP: DEFECTIVE DC TEST PAIR - (OPEN, SHORT, GROUND or
BATTERY)3-73
3-74
VER AA: STATIC ADDRESSING

VERIFICATION FAILED
Overview
A PING, HTTP, TRACE, TPUT, or HTPUT test request has resulted in a static
addressing verification failure. Anytime one of these test requests is submitted for
an IPoA Routed line, the testhead attempts to ping the user specified IP gateway
after DSL synchronization completes. If the ping fails, it is likely that there is an
error in the IP input parameters. VER AA also occurs when the IP Gateway does
not support pings.Provided that the test request was not entered with a trailing "X"
for example, TPUT instead ofTPUTX, the test system maintains the DSL sync
after the VER AA result.
Example
3-4
VER AB: LOOK OUT ATM

LOOPBACK FAILURE
Overview
The test system attempted to establish an ATM loopback as part of an

ATMLBOUT test request. This VER code indicates that the broadband test head
was able to establish DSL synchronization with the ATU-R, but the percentage of
lost loopback responses was greater than or equal to the look-out loopback failure
threshold.
If no loopback responses were received, it is possible that the particular model of
ATU-R (CPE modem) does not support ATM loopbacks.
Example

DSL SYNC SUCCEEDED

Overview
A stoppable test request (SYNC, SYNCOUT, ATMRSP, ATMLB, ATMLBOUT,

PING, HTTP, TRACE, TPUT, HTPUT. VOIP, or VOIPRING), in the "Processing"
state, was cancelled when the GUI's STOP button was clicked by the user. Additional summary message(s) and statistics will indicate the progress of the test
request at the point when it was stopped.
Example

DSL SYNC SUCCEEDED
DHCP ADDRESS RESOLUTION SUCCEEDED
3-6
VER AD: DHCP ADDRESS

RESOLUTION FAILURE
Overview
The test system attempted to perform DHCP address resolution, after establishing
DSL synchronization as part of a PING, HTTP, TRACE, TPUT or HTPUT test
request. This VER code indicates that the DHCP address resolution failed, as the
result of any or all of the following -- DHCP server failure, unresolvable IP
address, invalid IP parameters, improper protocol.
The following message can appear with this VER Code:
* POSSIBLE VLAN PROBLEM
Example

DSL SYNC SUCCEEDED
VER AH: HTTP ADDRESS TEST

FAILURE
Overview
The test system attempted to retrieve a web page via HTTP addressing, as part of
an HTTP test request. This VER code indicates that the HTTP address test failure
took place after DSL synchronization had been established, and after any
required authentication and/or IP address resolution had been completed.
The implications of this VER code are dependent upon the specified HTTP output
mode and, in most cases, will be clarified by an additional summary message.
Example
Display Mode: No web page was retrieved from the specified HTTP
address
Title Mode: No web page was retrieved or no title was found in the HTML
source
Source Mode: No web page was retrieved from the specified HTTP
address
Search Mode: No web page was retrieved, the search string was not found
in the HTML source, or an invalid search string was specified.

WEB SITE NOT FOUND
DSL SYNC SUCCEEDED
PPP AUTHENTICATION SUCCEEDED
3-8

Overview
The test system attempted to perform an IP ping as part of a PING test request
This VER code indicates that the ping failure took place after DSL synchronization
had been established, and after any required authentication and/or IP address
resolution had been completed. The ping failure indicates that the number of ping
responses received was less than or equal to the ping failure threshold.
In addition to a summary message indicating the success of the DSL
synchronization, additional summary messages will be displayed if PPP
authentication and/or DHCP address resolution was invoked as part of the PING
request.
Example

DSL SYNC SUCCEEDED
VER AJ: SEARCH STRING NOT IN

HTML SOURCE
Overview
This VER code indicates that an HTTP test request has completed successfully,
but the user-requested HTTP Search String was not found in the first 7000 bytes
of the HTML web page source that was retrieved.
Example

DSL SYNC SUCCEEDED
3-10
VER AK: METALLIC TESTS NOT

ALLOWED
Overview
An attempt was made to run a metallic test request (i.e. FULL, LOOP) on a line
where a broadband testhead is holding a DSL sync in keep-alive mode. In this
scenario, the broadband testhead has split the line to allow DSL testing while
maintaining voice service. In order to run a metallic test, the broadband access
must be dropped first.
Example
VER AK: METALLIC TEST REQ. NOT ALLOWED

MUST DROP ACCESS FIRST
POTS CALL MAINTAINED

Overview
The test system attempted to establish an ATM loopback as part of an ATMLB test
request. This VER code indicates that the broadband testhead was able to
establish DSL synchronization with the ATU-C, but the percentage of lost
loopback responses was greater than or equal to the look-in loopback failure
threshold.
Example

DSL SYNC SUCCEEDED
3-12
VER AM: SYNC FAILURE - MODEM

NOT DETECTED
Overview
The test system attempted to perform an inward-looking DSL modem

synchronization as part of a SYNC, ATMRSP, ATMLB, PING, HTTP, TRACE,
TPUT, or HTPUT request. This VER code indicates that the broadband testhead,
acting as an ATU-R, did not detect the LTE modem (ATU-C), and, as such, was
unable to establish sync.
Example
VER AN: SYNCOUT FAILURE MODEM NOT DETECTED

Overview
The test system attempted to perform an outward-looking DSL modem

synchronization as part of a SYNCOUT or ATMLBOUT request. This VER code
indicates that the broadband testhead, acting as an ATU-C, did not detect the
CPE modem (ATU-R), and, as such, was unable to establish sync.
Example
3-14
VER AO: SYNCOUT FAILURE MODEM DETECTED

Overview
The test system attempted to perform an outward-looking DSL modem

synchronization as part of a SYNCOUT or ATMLBOUT request. This VER code
indicates that the broadband testhead, acting as an ATU-C, detected the CPE
modem (ATU-R), but was unable to establish sync using the specified protocol /
parameters.
Example
VER AP: PPP AUTHENTICATION

FAILURE
Overview
The test system attempted to perform PPP authentication, after establishing DSL
synchronization as part of a PING, HTTP, TRACE, TPUT or HTPUT test request.
This VER code indicates that the PPP authentication failed, as the result of any or
all of the following - incorrect login, incorrect password, and/or improper protocol.
* POSSIBLE VLAN PROBLEM
Example

DSL SYNC SUCCEEDED
3-16
VER AQ:VLAN PARAMETER

MISMATCH
Overview
As part of a DSL/IP test request, the test system detected a VLAN parameter
mismatch. This indicates that either a VLAN was detected on the network side
when none was expected or that VLANs were enabled on both the BSU and the
network, but the VLAN ID values did not match.
Check the VLAN ID input parameter in the IP section of the BSU profile.
Example
VER AQ: VLAN PARAMETER MISMATCH

* NO VLAN DETECTED

Overview
The test system attempted to perform an IP trace route as part of a TRACE test
request. This VER code indicates that the trace route failure took place after DSL
synchronization had been established, and after any required authentication and/
or IP address resolution had been completed. The trace route failure indicates
that the specified IP address was not reached, due to any one or more of the
following -- failure of device at specified IP address, failure of intermediate
network node, or the number of required hops exceeded the specified maximum.
synchronization, additional summary messages will be displayed if PPP
authentication and/or DHCP address resolution was invoked as part of the
TRACE request.
Example

DSL SYNC SUCCEEDED
DHCP ADDRESS RESOLUTION SUCCEEDED
3-18
VER AS: SYNC FAILURE - MODEM

DETECTED
Overview
The test system attempted to perform an inward-looking DSL modem

synchronization as part of a SYNC, ATMRSP, ATMLB, PING, HTTP, TRACE,
TPUT, or HTPUT request. This VER code indicates that the broadband testhead,
acting as an ATU-R, detected the LTE modem (ATU-C), but was unable to
establish sync using the specified protocol / parameters.
Example
VER AT: THROUGHPUT TEST

FAILURE
Overview
The test system attempted to perform a throughput test as part of a TPUT or

HTPUT test request. This VER code indicates that the throughput failure took
place after DSL synchronization had been established, and any required authentication and/or IP address resolution had been completed. For TPUT, the failure
was most likely caused by one or more of the following conditions -- incorrect
login, incorrect password, incorrect server address, and/or file not found on the
server. For HTPUT, the failure may have been caused by an incorrect/invalid
HTTP address, a web server error, or a redirected HTTP request. In addition, for
HTPUT only, an additional summary message categorizes the type of failure
(server side error, client side error, etc.).
The following messages can appear with this VER Code:
* PPPOE LINK NOT ESTABLISHED
* LOSS OF SYNC
* FTP SERVER UNREACHABLE
* UNABLE TO RETRIEVE FILE
* NO DATA FROM SERVER
"* CANNOT CHANGE TO VDSL"
Example

DSL SYNC SUCCEEDED
3-20
VER AU:HOSTNAME (DNS)

TRANSLATION FAILURE
Overview
This VER code indicates that a PING, HTTP, TRACE, TPUT, or HTPUT test
request has failed as the result of a host name translation failure. When one of
these test requests is entered with a URL as the target address, the test system
relies on the network's Domain Name Server (DNS) to translate the specified host
name to an IP address. If the DNS is unreachable or out-of-service, or the specified host name can not be translated, the system is unable to successfully complete the test request.
Example
VER AU: HOSTNAME (DNS) TRANSLATION FAILURE
VER AV:ATM FAILURE - CHECK VPI/

VCI
The test system attempted to perform PPP authentication, after establishing DSL
synchronization as part of a PING, HTTP, TRACE, TPUT or HTPUT test request.
This VER code indicates that the PPP authentication failed and that no ATM traffic
was detected.
Verify that the customers VPI and VCI are configured correctly.
Example
3-22
VER AV: ATM FAILURE - CHECK VPI/VCI
VER AZ: TEST COMPLETE EXAMINE RESULTS

Overview
This VER code indicates that a PING, TRACE, ATMLB, ATMLBOUT, TPUT or
HTPUT test request completed with inconclusive results. For the PING
transaction, this VER code indicates that the number of pings received was
greater than the failure threshold, but less than the success threshold. For the
TRACE transaction, this VER code indicates that the time to reach one or more of
the intermediate hops was not determined or that the specified maximum number
of hops was traversed without reaching the target destination. For the ATMLB and
ATMLBOUT transactions, this VER code indicates that the number of successful
loopbacks was greater than the failure threshold, but less than the success
threshold.For the TPUT or HTPUT test requests, this VER code indicates that the
resulting throughput rate was greater than the failure threshold, but less than the
success threshold.
Example

DSL SYNC SUCCEEDED
VER B0: TEST EQUIPMENT BUSY TIME OUT IN ACCESS

Overview
Additional
Information
LoopCare has attempted to test a line but was not successful due to busy system
equipment. VER B0 occurs in the following cases:
Office overflow (busy Central Office switching machine)
Timeout in testing
Timeout in access
Couldn't access the line because one of the following pieces of equipment
were not available:
dialers
busy detectors
trunks (ntt or unigauge)
test ports
When an ISDN line is tested by LTS and the DSL is busy this summary
message will appear: POSSIBLE BUSY DSL
If this condition occurs, the most appropriate action would be to retest the line and
get complete test results.
Hopefully, this is a temporary condition. If, however, this VER code continues to
appear over and over, it could indicate a more widespread problem. In this case,
notify someone responsible for system maintenance.
See Also
VER codes related to VER B0 (TEST EQUIPMENT BUSY) are listed below:
VER B1 TEST NOT MADE
VER B2 TEST EQUIPMENT BUSY - SANITY OR DIAG IN PROGRESS
VER B3 TEST EQUIPMENT BUSY - SIMULTANEOUS TEST REQUEST
MADE
VER B4 TEST EQUIPMENT OUT OF SERVICE
VER B5 TEST EQUIPMENT BUSY - PAIR GAIN ACCESS EQUIPMENT
BUSY
VER B6 DOWNLOAD IN PROGRESS
3-24

Overview
+ No test packages available
Additional
Information
If this condition occurs, the most appropriate action would be to retest the line and
get complete test results.
See Also
VER B0 TEST EQUIPMENT BUSY - TIME OUT IN ACCESS
MADE
BUSY
VER B6 DOWLOAD IN PROGRESS
VER B2: TEST EQUIPMENT BUSY SANITY OR DIAG IN PROGRESS

Overview
Sanity in progress
Diagnostics in progress
Additional
Information
If this condition occurs, the most appropriate action would be to retest the line at a
later time. Hopefully, this is a temporary condition. However, if you get this VER
code over and over again, bring it to the system administrator's attention.
See Also
MADE
BUSY
3-26
VER B3: TEST EQUIPMENT BUSY SIMULTANEOUS TEST REQUEST

MADE
Overview
equipment. VER B3 occurs when another test request was made simultaneously
for the same number.
Additional
Information
later time and get complete test results.
See Also
BUSY
VER B4: TEST EQUIPMENT OUT OF

SERVICE
Overview
LoopCare has attempted to test a line but was not successful due to system
equipment failure. VER B4 occurs when the LTS or DMU is out of service and
cannot accept test requests.
Additional
Information
See Also
VER B3 TEST EQUIPMENT BUSY - SIMULTANEOUS TEST REQUEST MADE
VER B5 TEST EQUIPMENT BUSY - PAIR GAIN ACCESS EQUIPMENT BUSY
3-28
VER B5: TEST EQUIPMENT BUSY PAIR GAIN ACCESS EQUIPMENT

BUSY
Overview
equipment. VER B5 occurs specifically on loops equipped with SLC-96. In this
case the pair gain access is not available.
Additional
Information
See Also
VER B0TEST EQUIPMENT BUSY - TIME OUT IN ACCESS
VER B1TEST NOT MADE
VER B2TEST EQUIPMENT BUSY - SANITY OR DIAG IN PROGRESS
VER B3TEST EQUIPMENT BUSY - SIMULTANEOUS TEST REQUEST
MADE
VER B4TEST EQUIPMENT OUT OF SERVICE
VER B6DOWNLOAD IN PROGRESS

Overview
equipment. VER B6 occurs if a test request is made while downloading is in
progress.
Additional
Information
See Also
VER B0TEST EQUIPMENT BUSY - TIME OUT IN ACCESS
VER B1TEST NOT MADE
VER B2TEST EQUIPMENT BUSY - SANITY OR DIAG IN PROGRESS
VER B3TEST EQUIPMENT BUSY - SIMULTANEOUS TEST REQUEST
MADE
VER B4TEST EQUIPMENT OUT OF SERVICE
VER B5TEST EQUIPMENT BUSY - PAIR GAIN ACCESS EQUIPMENT
BUSY
Summary messages related to VER B6 (TEST EQUIPMENT BUSY) are listed
below:
* DATABASE DOWNLOAD IN PROGRESS
* SOFTWARE DOWNLOAD IN PROGRESS
3-30

Overview
VER B7 is returned, when the switch cannot complete a request because

resources are unavailable from a Switch Module (SM), Protocol Handler (PH),
Integrated Service Line Unit (ISLU), Integrated Services Test Function (ISTF),
Loop Testing System (LTS), or Directly Connected Test Unit (DCTU).
Additional
Information
VER_B7 was added with the implementation of LoopCare/ISDN.

One of the following summary messages will appear for this VER code.
VER B7: ISTF UNAVAILABLE
VER B7: SWITCH EQUIP NOT AVAILABLE
Summary Message.
NO DCTU PORT AVAILABLE (VER BA)
This VER Code indicates that all DCTU ports are in use or that there is a port
allocation problem. Additional DCTU ports may be required.
VER B8: ALL TRUNKS ARE BUSY BY

OTHER USERS
Overview
3-32
This VER Code is only displayed when the Loop Detect feature is active. VER B8
occurs when a user requests a test from the TV Mask or GUI and one of the
following conditions exist:
other users are already using all EMU trunks
the tested waited more than two minutes for an EMU trunk to become
available.

Overview
This VER Code indicates that all DCTU ports are in use or that there is a port
allocation problem. Additional DCTU ports may be required.
Example

Overview
3-34
This VER Code indicates that the DCTU is out-of-service because either the
DCTU, EAN, PORTs or PMUs have been place out-of-service either automatically
or manually.

Overview
This VER Code indicates that a line unit could not be accessed because there are
no GDX Compensator circuit packs (TN880) available because all are either busy
or out-of-service. Additional GDX Compensator pack(s) on the MMSU may be
required.

Overview
3-36
This VER Code indicates that the MTB (Metallic Test Bus) is either busy or out-ofservice. MMSU assignments should be reviewed and compared to DOPS
(SD5D005-01) engineering guidelines. Particular attention should be given to
DCTU appearances in service groups where line units reside.

Overview
This VER Code indicates that the MMSU switching matrix cannot interconnect the
desired devices because the MTIB (Metallic Test Interconnect Bus) paths are all
busy. This can indicate a MTIBAX (TN138) circuit pack problem in the MMSU, or
improperly assigned testing devices (DCTU, PGTC, TBCU). MMSU assignments
should be reviewed and compared to DOPS (SD5D005-01) engineering
guidelines.

Overview
3-38
desired devices because a MA (Metallic Access) pack (TN138) is out-of-service.
This VER Code is applicable only to the DCTU.

Overview
desired devices because the MAB (Metallic Access Bus) interconnect paths
(junctors) are all busy. MMSU assignments should be reviewed and compared to
DOPS (SD5D005-01) engineering guidelines. Particular attention should be given
to the assignment of testing devices (DCTU, PGTC, TBCU, GDXC).

Overview
3-40
This VER Code indicates that the MTIB (Metallic Test Interconnect Bus) path to
the Protocol Circuit (PRTC) is unavailable or all of the Protocol Circuit hardware
units are busy or out-of-service. Common contributors to this VER Code are (1)
Protocol Bus, (2) MTIBAX CP (TN 138) and (3) Common CP (TN 879) being
either busy or out-of-service. Use of the faster TN 879B Common CP is
recommended.
VER BI: NO MTB TO PGTC

AVAILABLE
Overview
This VER Code indicates that the PGTC port and the MTB (Metallic Test Bus)
serving it are busy or out-of-service. This could mean that the PGTC ports are not
properly assigned to the MMSU. MMSU assignments should be reviewed and
compared to DOPS (SD5D005-01) engineering guidelines.
VER BJ: NO MTB TO PGTC PORT

AVAILABLE
Overview
3-42
This VER Code indicates that there is no PGTC accessible to this DCTU. This can
mean that there is no PGTC port assigned to the MMSU.
VER BK: PGTC PATH SETUP

BLOCKAGE (other)
Overview
This VER Code indicates that the setup of the metallic test path to the PGTC was
blocked for reasons other than those stated under VER BI and VER BJ.

Overview
3-44
This VER code indicates that there is no port available because they are all either
busy or out-of-service. For the CMU, there is an exception: if all CMU ports are
out-of-service, VER Code FH will appear. This VER Code is applicable to the LTF,
LTS, CMU and DMU. However, for the LTS and CMU the term port and trunk are
synonymous.

Overview
This VER Code indicates that there is no test trunk available because all are
either busy or out-of-service.
VER BN: NO TEST PACKAGE

AVAILABLE
Overview
3-46
This VER Code indicates that there is no test package available because all are
either busy or out-of-service.

Overview
This VER Code indicates that there are no PMUs available because all are either
busy or out-of-service. Excluded is the DCTU case where all PMUs are out-ofservice (see VER BB). This VER Code is applicable to the LTS, DCTU and CMU
(called a Measuring Unit).

Overview
3-48
This VER Code indicates that there is no dialer available because they are either
busy or out-of-service. This VER Code is applicable to the LTF and LTS.
VER BR: NO BUSY DETECTOR

AVAILABLE
Overview
This VER Code indicates that there are no busy detector available because all are
either busy or out-of-service. This VER Code is applicable to the LTF and LTS.
VER BS: SWITCH TEST ACCESS

BLOCKAGE
Overview
3-50
This VER Code indicates that the switch could not set up the access to the
subscriber loop because of a switch resource shortage or a switch failure
condition. This would normally not be a LoopCare equipment problem unless
there was a dialing error (such as incorrect number of digits or incorrect steering
digits).
VER BT: RMU IN USE

Overview
This VER Code indicates that a request has been made to access a remote test
head that is already in use or that is currently performing a periodic selfcalibration. Excessive occurrences of this VER Code may be indicative of
excessive loading of pair gain systems on a single Remote Test Unit.

Overview
This VER Code indicates that a local modem was used and that a busy Remote
Test Unit was found.
This VER Code can also occur if the local modem cannot connect to the Remote
Test Unit due to a dial-out failure, such as no dial-tone to the local modem.
3-52
VER BV: NO MODEM PORT

AVAILABLE
Overview
This VER Code indicates that there is no modem port available when requesting
access to a Remote Test Unit. This applies to calls from all modem pools or
internal test unit modems. This may indicate a shortage of modems.

Overview
3-54
This VER Code indicates that a local modem was used and that a busy CMU was
found.
VER BY: LTE BUSY

Overview
Resources within the Loop Terminating Equipment (LTE) needed to complete the
request were busy. Conditions which could cause this result are:
Example
All TCP/IP ports into the LTE were in use.
The Test Access Path (TAP) was being used by another application or local
craft personnel.
Another user was logged into the LTE using the login/password assigned to
the system.
VER BY: LTE BUSY

Overview
Example
3-56
The system received an invalid status indication from the SDV system. The SDV
system may be experiencing initialization problems at the Host Digital Terminal
(HDT). If the error remains after a period of time, contact the SDV system
administrator. For more information, see the section on VER BZ in the Test
Results Guide.
VER BZ: HDT INITIALIZING
VER C1: TOTALIZER OPERATION

PROBLEMS
Overview
A VER of C1 would be set if more than one attempt were needed to home the
totalizer, and more than 18 ma of current were needed to home and in addition, no
loop, C.O., or other coin problems were found.
Additional
Information
This problem is probably at the station set. The best action would be to check the
totalizer.
See Also
VER codes related to VER C1 (TOTALIZER OPERATION PROBLEMS) are listed

below:
VER C2TOTALIZER DEFECT
VER C3POLARITY GUARD PROBLEMS
VER C4COIN RELAY PROBLEMS
VER C5COIN SUPERVISORY CKT PROBLEMS
VER C6INITIAL RATE OR FRAUD CONTACT PROBLEMS
VER C7OSCILLATOR PROBLEMS

Overview
Additional
Information
This VER code could occur under a number of conditions listed below:
1.
The totalizer could not be homed, or was homed with more than 18 ma of
current.
2.
The totalizer was a runaway (> 36 tone bursts detected).
3.
The totalizer is stalled (continuous tone detected).
Once a definite coin problem is detected no further testing is done on the line.
If a stalled totalizer case exists, it might be more economical to dispatch a coin
collector than a repair person since the trouble might be a stuck coin or a full coin
box.
If a runaway totalizer case exists, check the T-2 contacts. Otherwise, examine the
entire totalizer, and possibly replace it.
See Also
VER codes related to VER C2 (TOTALIZER DEFECT) are listed below:

VER C1TOTALIZER OPERATION PROBLEMS
3-58
VER C3: POLARITY GUARD

PROBLEMS
Overview
A problem is detected in the A-relay polarity guard or the polarity guard in a C set.
In addition, this VER code could be set if there is a lead reversal on an A set.
Additional
Information
For an A set, the leads might be reversed in the central office. It would be less
costly to change the leads in the C.O. than to dispatch someone to the station.
For a C set, dial tone first (DTF) station, one of the totalizer polarity guard diodes
may have failed. In this case replacing the totalizer is recommended.
If the problem is a CR4 diode failure, replacing the entire chassis is
recommended.
For a C set, coin first (CF) station if the problem is the A-relay, the chassis might
be replaced.
See Also
VER codes related to VER C3 (POLARITY GUARD PROBLEMS) are listed

below:

Overview
This VER code can be caused by a number of conditions which are listed below:
1.
The coin relay did not operate.
2.
The coin relay did not operate at the correct speed.
3.
More than one attempt was needed to operate the relay. In addition, more
than 41 ma of current was needed to operate it.
Additional
Information
This condition is probably a station problem. If the relay is slow or fast, an easy
adjustment could be made. If the problem is in the coin relay, examine it, and if
necessary replace it.
See Also
VER codes related to VER C4 (COIN RELAY PROBLEMS) are listed below:
3-60
VER C5: COIN SUPERVISORY CKT

PROBLEMS
Overview
If the totalizer is homed on the first attempt and with the proper current, or the coin
relay is operated on the first attempt and with the proper current, and there are no
other loop or C.O. problems, then this VER code will be set.
Additional
Information
If everything was as it should be on a coin line, the totalizer would be homed

already and LoopCare would test through the station and look at the loop and
central office.
The fact that LoopCare homes a totalizer indicates that something was off normal
to begin with.
This condition could be due to some temporary situation or could be due to a
more serious condition described below.
There are several coin supervisory circuits (CSC) in the central office. Each time a
call is made on a coin station, a CSC is selected at random in the C.O. to serve
that call. If you notice a lot of VER C5 codes appearing randomly across NNXs
and coin stations, you might suspect that you have a central office problem with
the CSCs.
If, however, the problem appears to be with one coin station, then the problem is
an isolated one and a dispatch to the station to fix the problem is appropriate.
What you can do when you see a VER C5 is hold the trouble and retest later. If the
trouble is in the station, it is likely that you will see the same VER C5 when you
retest.
If you monitor the VER C5 over a period of time, you will be able to detect whether
there is a central office problem.
See Also
VER codes related to VER C5 (COIN SUPERVISORY CKT PROBLEM) are listed
below:

3-62
VER C6: INITIAL RATE OR FRAUD

CONTACT PROBLEMS
Overview
LoopCare has detected an initial rate or fraud contact open on a dial tone first coin
phone.
Additional
Information
This VER code is probably due to a station fault.
See Also
VER codes related to VER C6 (INITIAL RATE OR FRAUD CONTACTS

PROBLEM) are listed below:

Overview
LoopCare detected a possible coin oscillator problem. Basically this occurs when
the totalizer is homed but no tones ((1537 or 1700 Hz) and 2200 Hz) are detected.
Additional
Information
This VER code indicates a possible coin oscillator problem. The chassis should
be replaced if there is a problem.
See Also
VER codes related to VER C7 (OSCILLATOR PROBLEMS) are listed below:

3-64
VER D1: DENIED SERVICE TERMINATING

Overview
LoopCare has detected that this customer's service was denied by action from the
Switching Control Center. This action is normally taken for nonpayment of bills or
at the customers request (e.g., vacation home, etc.). A terminating denial means
that the customer can make calls, but cannot receive them.
Denied service does not indicate that anything is wrong with the customer's loop
or central office equipment. Even on lines with denied service, LoopCare will still
test the customer's telephone line and tell you if there is anything else wrong. In
that case, you will get a VER code 99 (MULTIPLE FAULTS DETECTED) and the
denied service summary message will still appear, along with messages indicating
what else is wrong with the customer's telephone line.
Additional
Information
VER code D1 will only appear on lines that are tested by the ESS5-D switch. This
is because LoopCare talks directly to this switch and can receive status
information about individual lines from it. Denied service on other types of
electronic switches will give a result of VER 37 (DIAL TONE BURST
DETECTED).
You can still contact customers on denied lines by setting up a callback with the
RING transaction. This can be done whether the access is on a No-test trunk or
MDF trunk.
Another example of denied service terminating lines are the charge-a-call
telephone lines. These phones are not designed to receive calls.
See Also
VER codes related to VER D1 (DENIED SERVICE - TERMINATING) are listed

below:
VER 37
VER D2
DENIED SERVICE - ORIGINATING
VER D3
DENIED SERVICE
VER D2: DENIED SERVICE ORIGINATING

Overview
Switching Control Center. This action is normally taken for nonpayment of bills. An
originating denial means that the customer can receive calls, but not place them.
that case, you will get a VER 99 (MULTIPLE FAULTS DETECTED) and the
Additional
Information
VER code D2 will only appear on lines that are tested by the ESS5-D switch. This
is because LoopCare talks directly to this switch and can receive status
information about individual lines from it. Denied service on other types of
electronic switches will give a result of VER 37 (DIAL TONE BURST
DETECTED).
MDF trunk.
See Also
VER codes related to VER D2 (DENIED SERVICE - ORIGINATING) are listed

below:
VER 37DIAL TONE BURST DETECTED
VER D1DENIED SERVICE - TERMINATING
VER D3DENIED SERVICE
3-66

Overview
Switching Control Center. This action is normally taken for nonpayment of bills.
Denied service means that the customer cannot make or receive calls.
Additional
Information
VER Code D3 will appear on lines that are tested by the ESS5-D switch. This is
because LoopCare talks directly to this switch and can receive status information
about individual lines from it. Denied service on other types of electronic switches
will give a result of VER 37 (DIAL TONE BURST DETECTED).
VER Code D3 may also occur with Harris test units and some types of switches
where the test units have a direct data interface to the switch.
MDF trunk.
See Also
VER codes related to VER D3 (DENIED SERVICE) are listed below:
VER 37
VER D1
DENIED SERVICE - TERMINATING
VER D2
VER D4: DENIED CPE

Overview
LoopCare has denied service to this CPE because the customer has installed
more CPEs than they subscribed for. For example, customer subscribes for an
ISDN line for four PDNs and tries to hook up five. The fifth CPE would be
"Denied". This status applies to ISDN lines only.
Additional
Information
VER code D4 will only appear on lines that are served by the 5ESS switch. This is
about individual lines from it.
VER_D4 was added with the implementation of LoopCare/ISDN. The first
summary message that appears for the VER code is:
VER D4: DENIED CPE
DENIED SERVICE
POSSIBLE INTERFACE-TERMINAL MISMATCH
See Also
3-68
VER codes related to VER D4 (DENIED CPE) are listed below:

VER D1
VER D2
VER D3
DENIED SERVICE

Overview
This VER code is necessary for those cases where there are different types of
restricted services on the PDN or DN. For example, some services could be
denied while others are on intercept. If a service is on INTERCEPT, then that
service can not be used. If the service is DENIED ORIGINATING then only
incoming calls can be received. If the service is DENIED TERMINATING then only
outgoing calls can be made. If the service is completely DENIED then the line is
temporally out of service.
Additional
Information
VER code D5 will only appear on lines that are served by the 5ESS switch. This is
about individual lines from it. VER_D5 was added with the implementation of
LoopCare/ISDN.
The summary message that appears for this VER code is: VER D5:
DENIED/RESTRICTED SERVICE - MIXED

Overview
LoopCare/ISDN was not able to send a request to TL1ISDN because of a

probable Gateway failure.
Additional
Information
VER code DG will only appear for requests involving the TL1 Feature which
permits LoopCare/ISDN digital testing through some DMS-100 switches.
3-70
VER DI: DENIED/INTERCEPT MIXED

Overview
This VER code appears only on the TE/TR mask as a result of a STATUS-L
request. LMOS has determined via LoopCare/ISDN that some of the services on
the DSL are on intercept while others are denied. LoopCare/ISDN testing will not
occur.
Additional
Information
VER_DI was added with the implementation of LoopCare/ISDN.

The summary message that appears for this VER code is:
Refer to LoopCare/ISDN Summary Messages for a brief description of this
summary message.
VER DL: CONTROLLER-LTF OR

FRONT END-LTS DATA LINK
FAILURE
Overview
LoopCare tests could not run or be completed because the data link between the
LoopCare- controller and the LTF or between the LoopCare Front End and the
LTS has failed.
Additional
Information
The person responsible for system maintenance should be notified of this

condition.
3-72
VER DP: DEFECTIVE DC TEST PAIR (OPEN, SHORT, GROUND or

BATTERY)
Overview
This VER Code indicates that the 5ESS Diode Protocol Test (DPT) performed on
the DC test pair failed between the TBCU and the RT site. The type of failure
(open, short, ground, battery) found will be part of the summary message. The
measurements obtained from the DCTU will also be provided.
This VER Code can also occur if DLC Loop Calibration is enabled in the following
situation: the open distance is 10% less than the calibration distance for the
Remote Terminal (RT). If an open on a DLC line is 10% less than the calibrated
RT distance, it is likely that the bypass pair is open and not the customer loop.
NOTE:
After an initial FULL or LOOP request returns a VER DP, any additional
tests will not report a VER DP but a VER code dependent on the test
results. The reason for the VER DP not being repeated is that the Diode
Protocol Test is only run on the initial access to the DC test pair (or MCU
equivalent). In addition, with a FULLX or LOOPX request, a VER DP will be
reported if the DPT test fails and the reason for the failure will also be
reported (Short, Ground, Open, FEMF). Even with a VER DP reported, the
subscriber loop is attached (except for the Open condition) and the AC and
DC results are provided, including any found on the DC test pair.

Overview
This VER code indicates that there is a service affecting problem with the Digital
Loop Carrier (DLC) or DC test pair attached to this line There was not enough
information in the test result to sectionalize the problem to the DLC or DC test
pair.
Direct repair activities to the affected DLC system and DC test pair, not to the line.
The VER CODE MAPPED FROM VER <code> message identifies the VER
code that would have appeared if the bad DLC had not been identified.
Example
VER DT: BAD DLC OR DC TEST PAIR

VER CODE MAPPED FROM VER <code>
3-74
Contents
4-4
4-5
4-6
4-7
4-8
4-9
4-10
4-12
VER E9: ISDN DIGITAL LINK NOT AVAILABLE
4-13
4-14
4-15
VER EC: COMMUNICATION OR MML ERROR
4-16
4-17
4-18
4-19
VER ER: LTE COMMUNICATION FAILURE
4-20
4-21
4-2
VER ET: POTS DETECTED ON DRY DSL LINE
4-22
VER EU: POTS ONLY OR NON-COMBO CIRCUIT
4-23
4-24
4-25
4-26
4-27
4-28
4-29
4-30
4-31
4-32
4-33
VER FC: MEASUREMENT UNIT FAILURE
4-34
VER FD: SLEEVE CONTROL FAILURE
4-35
VER FE: CONTROL FAILURE - ISLC/DCTU
4-36
VER FF: CONTROL FAILURE - USLC/DCTU
4-37
VER FG: TBCU PROTOCOL TEST FAILURE - (OPEN)
4-38
4-39
VER FJ: SWITCH TEST ACCESS FAILURE
4-40
4-41
VER FL: MODEM CONNECTION FAILURE
4-42
VER FM: RMU/CMU CONNECT FAILURE
4-43
4-44
4-45
4-46
4-47
4-48
4-49
4-50
4-51
4-52
VER FZ: TEST HEAD COMM FAILURE
4-53
VER G0: VALID RINGER COUNT AND TERMINATION
4-54
VER G1: INVALID RINGER TERMINATION
4-55
VER G2: INVALID 2 PARTY RINGER TERMINATION
4-56
4-57
VER G5: VALID 2 PARTY TERMINATION
4-58
4-59
4-60
4-61
4-62
4-63
4-64
VER H0:SWITCH TO VG COMMUNICATION DOWN
4-65
4-66
VER I0: TEST OK NOW
4-67
VER IA: WIRING ERROR - NT1 REVERSED
4-68
VER IB: UNEXPECTED ISDN TERMINATION
4-69
VER IC: POSSIBLE AMI BRITE DETECTED
4-70
VER ID: ISDN TERMINATION MISMATCH
4-71
VER IF: INVALID TERM FOR ISDN LINE
4-72
4-73
VER IH: OE MISMATCH
4-74
4-75
4-76
4-77
4-78
4-79
4-80
4-82
4-83
4-84
4-85
4-86
VER IW: INVALID WIRE CENTER IN LINE RECORD
4-87
4-88

Overview
LoopCare could not test a line due to a system error.
Additional
Information
Hopefully, this condition is only temporary. In this case wait a short while and then
retest the line with LoopCare. If the same results (TEST SYSTEM ERROR)
appear over and over this is probably a widespread system problem; notify
someone responsible for maintaining the system.
Example
See Also
VER codes related to VER E0 (TEST SYSTEM ERROR) are listed below:
4-4
VER E1
TEST SYSTEM ERROR
VER E2
TEST SYSTEM ERROR

Overview
LoopCare could not test a line due to a system error. VER E1 is set specifically
when there is a power clear and reset of the system equipment during testing.
Additional
Information
Hopefully, this condition is only temporary. In this case wait a short while and then
retest the line with LoopCare. If the same results (TEST SYSTEM ERROR)
appear over and over this is probably a widespread system problem; notify
someone responsible for maintaining the system.
See Also
VER E0
TEST SYSTEM ERROR
VER E2
TEST SYSTEM ERROR

Overview
LoopCare could not test a line due to a system error. VER E2 is set specifically
when the particular LTF involved in the test was not calibrated.
Additional
Information
Hopefully, this condition is only temporary. Contact the system administrator and
notify that person of the situation. Request calibration for the LTF.
See Also
4-6
VER E0
TEST SYSTEM ERROR
VER E1
TEST SYSTEM ERROR

Overview
Additional
Information
VER E3 is returned under one of the following circumstances:
when the switch cannot complete a request because of an internal error
when the switch version number is not compatible with LoopCare/ISDN
when the requested command is not yet implemented.
when LoopCare performs a version check on Stinger and CLT versions and
determines that they are incompatible. The summary that appears with the
VER code is INCOMPATIBLE VERSIONS
when LoopCare performs a version check on the RTUs version and

determines that it is incompatible with the entry of extra digits for a
Telephone Number (TN) or of a Hunt Group. The summary that appears
with the VER code is INCOMPATIBLE VERSIONS.
VER E3 was added with the implementation of LoopCare/ISDN.

One of the following summary messages will appear for this VER code.
VER E3: INCOMPATIBLE VERSIONS
VER E3: INVALID COMMAND
VER E3: SWITCH INTERNAL ERROR
VER E3: SWITCH OVERFLOW
VER E3: TEST SESSION FAILURE
VER E3: UNEQUIPPED COMMAND
Summary Message.

Overview
LoopCare could not test a line due to system error. When you make an request,
LoopCare checks to see if the NPA-NNX that you entered maps to an Exchange
Key by checking the Default Exchange Key table. Situations where VER E5 may
be set include:
The exchange key is missing from the Line Record
The tip module of LoopCare could not access the Default Exchange Key
Table
A Packet arrives containing LRDATA=Y and LREXK=
In non-North American telephone numbering plans, this VER Code may indicate
an inability to match the Exchange.
Additional
Information
This VER code may reflect an error in the data base or simply an invalid entry in
the TN field. Do not try to retest because it will not work. If you know that the TN
you are entering is valid contact the system administrator to check for a data base
error.
See Also
4-8
VER E0
TEST SYSTEM ERROR
VER E1
TEST SYSTEM ERROR
VER E2
TEST SYSTEM ERROR
VER NS
NNX NOT SERVED

Overview
Additional
Information
LoopCare could not test a line due to system error. VER E6 is set specifically
when one of the following cases are met:
1.
You are testing a derived pair but the TN of the physical pair is not a valid 7
digit TN. or---
2.
You are testing over an MDF dedicated number and the MDF DED NBR is
not a valid 7 digit TN.
If the problem is due to an invalid physical pair TN then this is a data base
problem. Physical pair numbers used to be only 4 digits and were updated to be
seven. It is possible that the data base was not updated properly.

Overview
LoopCare could not test a line due to a system error. When you make a request,
LoopCare checks the Default Exchange Key table to see if the NPA-NNX maps to
an Exchange Key. Then it checks the LoopCare Access Table to see if the NPANNX is testable by LoopCare. In this case, the NPA-NNX was in the Default
Exchange Key table, but not in the Access Table. So, LoopCare returns VER E7.
The following summary message is returned with VER E7 when the Local Number
Portability (LNP) R1 feature is not enabled and the NXX-EXK is not unique in the
LoopCare database. Refer to the Local Number Portability (LNP) Summaries in
Chapter 4.
DUPLICATE NNX-EXK IN DATA BASE
The following summary message is returned with VER E7 when the line record
indicates a ported-in number and the switch identified has ported number testing
inactive. Refer to the Local Number Portability (LNP) Summaries in Chapter 4.
PORTED NUMBER TESTING INACTIVE
In non-North American telephone numbering plans, this VER Code may indicate
an inability to find the City Code/Exchange combination corresponding to the
Telephone Number existing in the LoopCare database.
The following summary message is returned with VER E7 when an RTU table
setup error is encountered:
MISSING DATA IN TEST UNIT
LRN Error
If the SPID is ILEC owned and testable (SPID Type = L) LoopCare uses the
retrieved LRN to identify the serving switch and associated test equipment
following the rules developed in the LoopCare LNP Release 2 feature. If the LRN
provided by the LRN Server does not match any LRN entries in the LoopCare
Switch ADEF tables, LoopCare stops testing, returns VER E7 and updates the
LRN Missing Log File.
Additional
Information
This VER code may reflect an error in the data base. Do not try to retest because
it will not work. If you know that the TN you are entering is valid, contact the
system administrator to check for a data base error.
4-10
See Also
VER E0
TEST SYSTEM ERROR
VER E1
TEST SYSTEM ERROR
VER E2
TEST SYSTEM ERROR
VER NS
NNX NOT SERVED
VER X7
TEST SYSTEM ERROR
VER E8: CAN'T SEND REQUEST TO

APPROPRIATE FE
Overview
4-12
When you make a request, LoopCare tries to retrieve a line record. If that line
record belongs to a database that corresponds to another Front End (FE),
LoopCare will try to reach that FE. If it fails to establish a connection, it will attempt
to continue on the current FE with the default exchange key for that NPANNX. If a
matching entry for this default exchange key can't be found in the LoopCare
Access Table, LoopCare will send you this error message.
VER E9: ISDN DIGITAL LINK NOT

AVAILABLE
Overview
The ISDN Digital communications link required to perform the requested ISDN
test has not been configured in the LoopCare Database.
Example
VER ER: ISDN DIGITAL LINK NOT AVAILABLE

Overview
4-14
LoopCare failed to login to the LTE with SNMP v3 support. Conditions which could
cause this result are:
1.
Invalid Login/Password information in the LoopCare database for the given

LTE Id.
2.
A communications failure occurred during the login procedure.
VER EB: BSU MODULE EQUIPAGE

ERROR
Overview
The test system attempted to perform a DSL synchronization as part of a SYNC.

SYNOUT, ATMRSP, ATMLB, ATMLBOUT, PING, HTTP, TRACE, TPUT, HTPUT,
VOIP, or VOIPRING test request. This VER Code indicates that the test head is
not equipped for specified type of broadband testing. Either the test head has no
BSU or the BSU does not have the type of modem card required for specified DSL
protocol. For example, if the BSU has only an ADSL modem card and the user
selects G.SHDSL as the DSL type, the test system returns this VER Code.
Example
VER EC: COMMUNICATION OR

MML ERROR
Overview
4-16
If the OE retrieval feature is on LoopCare will send a request to the 5ESS Switch
for OE information on the line under test. VER EC will be returned if that request
did not reach the switch. The reasons for this communication failure could be
anyone of the following:
The LoopCare process responsible for communicating with the switch is

not running. Verify that the resmgr process is running on the LoopCare
machine.
The command was not interpreted correctly by the Switch due to a switch
error or load condition. Try to resend a request for OE information (INFO
request would do) to verify whether or not the condition is temporary.
The switch does not recognize the command sent by LoopCare because
the request format is not correct for the generic of software running on the
switch. Verify versions of 5ESS generic running and check with switch
people to determine if the formation of the OP:STATUS command has
changed.
VER ED: DLC CONCENTRATOR

COMM FAILURE
Overview
The DLC Concentrator failed to respond to a SNMP request by the system. This
result could indicate either a general communications network problem or a failure
of SNMP Authentication.
Example

Overview
If the system logging into a switch failed, this VER Code will be displayed. The
connection manager performs a two-part connection, the first part LoopCare
opens the socket and connects to the modem. The second part LoopCare logs
into the switch. If the second part fails, this VER Code is displayed.
See Also
VER codes related to VER EL (SWITCH LOGIN FAILURE) are listed below:
VER EC: COMMUNICATIONS OR MML ERROR
VER T2: SWITCH PROCESSOR TIMEOUT
4-18

Overview
The slot in the LTE (as derived from either the OE if testing by TN or Slot entry if
testing by shelf-slot-line circuit information) is not equipped or has yet to be
assigned.
VER ER: LTE COMMUNICATION

FAILURE
Overview
The Loop Terminating Equipment (LTE) failed to respond to a request by

LoopCare or the Remote Test Unit. This result could indicate either a general
communications network problem or a problem with the specific LTE itself.
LTE is the generic LoopCare term for all DLCs (Digital Loop Carriers) or DSLAMs
(Digital Subscriber Line Access Multiplexers).
4-20

Overview
The circuit associated with the number or circuit ID under test is not in service.
This condition could be caused by the following events:
1.
A switch provisioning problem.
2.
A problem between the switch and the LTE
3.
The Test Access Unit (TAU) within the AMAS may be out of service.
LTE is the generic LoopCare term for all DLCs (Digital Loop Carriers) or DSLAMs
(Digital Subscriber Line Access Multiplexers).
VER ET: POTS DETECTED ON DRY

DSL LINE
Overview
4-22
The circuit tested has an existing POTS assignment, i.e., it is not a Dry Line ADSL
circuit.
VER EU: POTS ONLY OR NONCOMBO CIRCUIT

The circuit tested is not serviced by a combo POTS/ADSL circuit, required for
testing Dry Line ADSL circuits on the Alcatel Litespan.

Overview
Request is not allowed. The testhead is not VoIP enabled.

The user attempted to run a Voice over IP test request, but the test head servicing
the specified line was not enabled for VoIP testing.
4-24

Overview
The system could not test the line due to failure of the testing equipment. This
condition indicates a serious problem and generally means that the system is
down. Whenever this VER code occurs, notify the facilities manager.
Example
See Also
VER codes related to VER F0 (TEST EQUIPMENT FAILURE) are listed below:
VER F1
TEST EQUIPMENT FAILURE

Overview
LoopCare could not test a line because of failure in the LoopCare testing
equipment. Specifically VER F1 occurs on lines equipped with SLC-96. This
condition indicates a failure in the SLC-96 testing equipment.
When a VER Code F1 is generated, LoopCare will automatically drop access to
the line.
Additional
Information
This condition indicates a serious problem with the system. Generally it means
that the system is down. When this VER code occurs, notify the system
administrator of the situation.
See Also
VER F0
4-26

Overview
LoopCare could not test a line because of failure of the LoopCare testing
equipment. This condition indicates that the failure could be due to unplugging of
circuit packs during diagnostics.
Additional
Information
This condition indicates that the system administrator is running diagnostics to fix
a problem in the system. Wait for a while and try your request again.
See Also
VER F0

Overview
VER F3 is returned, when the switch cannot complete a request because of an

internal error, or the switch version number is not compatible with LoopCare/
ISDN, or the requested command is not yet implemented.
Additional
Information
VER_F3 was added with the implementation of LoopCare/ISDN. One of the

following summary messages will appear for this VER code.
VER F3: INCOMPATIBLE VERSIONS
VER F3: INVALID COMMAND
VER F3: SWITCH INTERNAL ERROR
VER F3: SWITCH OVERFLOW
VER F3: TEST SESSION FAILURE
VER F3: UNEQUIPPED COMMAND
Summary Message.
4-28

Overview
VER F4 is returned, when the switch cannot complete a request because

resources are unavailable from a Switch Module (SM), Protocol Handler (PH),
Integrated Service Line Unit (ISLU), Integrated Services Test Function (ISTF),
Loop Testing System (LTS), or Directly Connected Test Unit (DCTU).
Additional
Information
VER_F4 was added with the implementation of LoopCare/ISDN. One of the

following summary messages will appear for this VER code.
VER F4: ISTF UNAVAILABLE
VER F4: SWITCH EQUIP NOT AVAILABLE
Summary Message.

Overview
4-30
LoopCare received a response from the LTE which indicates that an internal error
condition exists within the LTE. Conditions which could cause this result are:
1.
A Software installation is being performed in the LTE
2.
The LTE is initializing.
3.
There is an unspecified internal error within the LTE.
VER F6: DLC CONCENTRATOR

INTERNAL ERROR
Overview
The DLC Concentrator failed to respond to a SNMP request by the system. This
result could indicate that DLC Concentrator could not perform the specific SNMP
operations on the Management Information Base (MIB).
Example

Overview
4-32
This VER Code indicates that the busy detector failed when it was in use. This
VER Code is applicable only to the LTS.

Overview
This VER Code indicates that the dialer failed when it was in use. This VER Code
can also indicate the absence of dial-tone on the callback line.
VER FC: MEASUREMENT UNIT

FAILURE
Overview
4-34
This VER Code indicates that the measurement unit failed when it was in use.
This VER Code is applicable to the LTS, DCTU (called a PMU), CMU (called a
MU), and DMU.
VER FD: SLEEVE CONTROL

FAILURE
Overview
This VER Code indicates that there was a sleeve control failure associated with
the no-test trunk connected to the LTS and CMU.
VER FE: CONTROL FAILURE - ISLC/

DCTU
Overview
4-36
This VER Code indicates that there was a control failure with the DCTU during an
ISLC access or, possibly, during a non-SLC access. The failure may occur before
or after bypass.
VER FF: CONTROL FAILURE - USLC/

DCTU
Overview
This VER Code indicates that there was a control failure after bypass of a
universal DLC line when tested with a DCTU.
VER FG: TBCU PROTOCOL TEST

FAILURE - (OPEN)
Overview
4-38
This VER Code indicates that the 5ESS Diode Protocol Test failed between the
MMSU and the TBCU. This may indicate that the SM500 pack is defective. If the
continuity part of the diode protocol test fails, OPEN will appear in the
summary message (as indicated above). If the test failed because of either a
ground, short or battery fault, the OPEN field in the summary message will be
blank. This VER Code is applicable only to the DCTU.
VER FH: EQUIPMENT ACCESS

FAILURE
Overview
This VER Code indicates that there was a failure in the test equipment that
prevented access or that all test equipment ports are out-of-service, or there was
a trunk access failure.
Example
VER FJ: SWITCH TEST ACCESS

FAILURE
Overview
This VER Code indicates that there was a failure in the switch (which includes the
metallic access network) that prevented test access to the line (other than those
failures already represented by other VER Codes).
If the telephone number is served by a 5ESS-integrated DLC, this VER Code may
indicate that the TBCU SM500 CP is missing.
4-40

Overview
This VER Code indicates that a GDXC circuit pack was obtained and that a
problem occurred when it was operating. This VER Code is an indication that the
GDXC CP (TN 880 or TN 140) may be defective or that the line unit is faulty. This
VER Code is applicable only to the DCTU.
VER FL: MODEM CONNECTION

FAILURE
Overview
4-42
This VER Code indicates that a local modem was obtained but failed in
connecting to the Remote Test Unit. The type of failures that can cause this VER
Code are no dial- tone or no answer. This VER Code is applicable only for the
types of modems that are designed to provide a failure indication.
VER FM: RMU/CMU CONNECT

FAILURE
Overview
The most likely cause of this VER Code is that the RMU/CMU is busy when tested
from another Front End or that the RMU/CMU is disconnected. This VER Code
can also indicate that there is a Datakit connection failure. That failure would most
likely be a DKTRAM (Network Manager) problem.

Overview
This VER Code may indicate that a TCP/IP network socket was opened or a
modem was connected to the test unit. However, the login process into the test
unit was not completed because of problems such as the following.
TCP/IP network congestion or delays
noisy modem connection
test head hardware problem
password error
This case is applicable to the DMU, CMU and RMU.
It may also indicate a Foreign Operation System (FOS) EMS (Element
Management System) login failure. This case is applicable to the Siemens EWSD
switch with testing capabilities.
4-44
VER FP: AS COMMUNICATION

FAILURE
Overview
This VER Code indicates that an access server used for communicating with test
units was unreachable. The type of failures that can cause this VER Code are an
invalid or unknown IP address or an unpowered access server device.
Example

Overview
This VER Code indicates a stuck Junctor Relay detected with the MA CP.
Contact the Switch Administrator. Perform Phase II and Phase III diagnostic with
the 5ESS.
4-46
VER FR: AS PORT OR DMU CONFIG

ERROR
Overview
This VER Code indicates that either the access server's port or the test unit (DMU
or RMU) has a configuration error or the unit is hung. The type of failures that can
cause this VER Code are an incorrect access server port configuration like parity,
stop bits, port number range(i.e.6001-6014), etc. It can also be caused by the test
unit being misconfigured or in a hung state. Also try resetting the unit and if that
does not work it may need to be replaced.
Example

Overview
This VER Code indicates that the MSUCOM pack is out of service.
the 5ESS.
4-48
VER FT: CONNECT FAIL PROTOCOL FAILURE

Overview
This VER Code indicates that there was no continuity detected on the MTB to test
equipment or Line Unit.
the 5ESS.
VER FV: DEFECTIVE DIST OR SCAN

CP
Overview
This VER Code indicates that the DIST or SCAN pack in the MSU is out of
service.
the 5ESS.
4-50

Overview
This VER Code indicates that a failure occurred while attempting to connect the
metallic testing bus to the line under test at the RT. This could be due to the RT
not responding to 5ESS switch-initiated events necessary to connect the metallic
test bus.
TR008
Check the A shelf to verify that no alarm condition exists. If an alarm exists, find
the cause and retire the alarm. Check the channel unit pack for the line on which
the test is failing.
TR303
Verify the that the EOC channel for the IDCU RT which terminates the line under
test is in service. Check the channel unit pack for the failing line.
TR008 or TR303
At the switch maintenance terminal, execute the ALW:METALLIC,DEBUG
command. Record any PTRACEs, assets, and/or audits that may occur during the
failing test request.
VER FX: TEST EQUIPMENT

FAILURE
Overview
4-52
This VER Code indicates that there was an unrecoverable failure in the Remote
Test Equipment. This can be a hardware failure, a software failure, or an error in
the test unit setup.
VER FZ: TEST HEAD COMM

FAILURE
Overview
This VER Code indicates that communication to the test head dropped during the
test and could not be re-established. Repeated failures of this type on a single test
head would indicate that a problem exists with the test head.
VER G0: VALID RINGER COUNT AND

TERMINATION
Overview
This VER code will only appear for the RINGER series test of LoopCare. It
indicates that both the number of ringers and the arrangement of those ringers (TR,T-G,R-G) were what we expected to see according to the line records.
Additional
Information
On a single party line you would expect the ringer to be connected T-R. On a two
party-one assigned line you would expect the ringer to be connected one side to
ground (most likely R-G). On a two party-two assigned line you would expect the
ringers to be connected on both sides to ground (T-G and R-G).
See Also
VER codes related to VER G0 (VALID RINGER COUNT AND TERMINATION)

are listed below:
VER G1INVALID RINGER TERMINATION
VER G2INVALID 2 PARTY RINGER TERMINATION
VER G4RINGER TEST WITH NO RECORDS
VER G5VALID 2 PARTY RINGER TERMINATION
VER G6RINGER TEST- UNCATALOGUED TERMINATION
VER G8NO RINGERS FOUND
4-54
VER G1: INVALID RINGER

TERMINATION
Overview
This summary can appear in the FULL or LOOP series test as well as the
RINGER series test.
VER G1 indicates that the ringer termination was invalid for the type of termination
expected by the line records. This will only appear for single party lines.
For a RINGER request, LoopCare displays the number of ringers counted by
LoopCare rather than the word YES as shown in the example below.
Additional
Information
The summary messages not only indicate that the termination is wrong, but as the
example above shows, it will also provide information about the type of
termination LoopCare thinks is present
When this VER code appears following the RINGER request it indicates that the
ringer count matched the records. Following a FULL or LOOP request this may
not be the case.
See Also
VER codes related to VER G1 (INVALID RINGER TERMINATION) are listed

below:
VER 92
POSSIBLE LONG LOOP
VER G0
VALID RINGER COUNT AND TERMINATION
VER G2
INVALID 2 PTY RINGER TERMINATION
VER G4
RINGER TEST WITH NO RECORDS
VER G5
VALID 2 PTY RINGER TERMINATION
VER G6
RINGER TEST- UNCATALOGED EQUIPMENT
VER G8
NO RINGERS FOUND
VER G2: INVALID 2 PARTY RINGER

TERMINATION
Overview
This summary can appear in the FULL or LOOP series test as well as the
RINGER series test.
VER G2 indicates that the ringer termination was invalid for the type of termination
expected by the line records. This will only appear for two party lines.
For a RINGER request, LoopCare displays the number of ringers counted by
LoopCare rather than the word YES as shown in the example below.
Additional
Information
The summary messages not only indicate that the termination is wrong, but as the
example above shows, they also indicate the type of termination that LoopCare
thinks is present.
When this VER code appears following the RINGER request it indicates that the
ringer count matched the records. Following a FULL or LOOP request this may
not be the case.
See Also
VER codes related to VER G2 (INVALID 2 PARTY RINGER TERMINATION) are

listed below:
VER G0VALID RINGER COUNT AND TERMINATION
VER G5VALID 2 PTY RINGER TERMINATION
VER G6RINGER TEST- UNCATALOGED EQUIPMENT
4-56
VER G4: RINGER TEST WITH NO

RECORDS
Overview
This VER code will only appear following the RINGER request. It indicates that
the RINGER test was run on a line that did not have any line records. Because of
this LoopCare cannot determine whether or not the ringer termination or the count
is valid.
The detailed information must be examined in order to identify the condition on
the line.
Additional
Information
The messages will indicate what the type ringer termination looks like (i.e., single
party, two party, etc.). This should help you figure out the condition on the line. If
more information is required, run a FULL test.
See Also
VER codes related to VER G4 (RINGER TEST WITH NO RECORDS) are listed
below:
VER G0
VALID RINGER COUNT AND TERMINATION
VER G1
INVALID RINGER TERMINATION
VER G2
INVALID 2 PTY RINGER TERMINATION
VER G5
VALID 2 PTY RINGER TERMINATION
VER G6
RINGER TEST- UNCATALOGED EQUIPMENT
VER G8
NO RINGERS FOUND
VER G5: VALID 2 PARTY

TERMINATION
Overview
This VER will only appear following the RINGER request. It indicates that the
ringer termination was valid for a two party line.
See Also
VER codes related to VER G5 (VALID 2 PARTY RINGER TERMINATION) are

listed below:
VER G2INVALID 2 PTY RINGER TERMINATION
4-58
VER G6: RINGER TESTUNCATALOGED EQUIPMENT

Overview
This VER code will only appear following the RINGER request. It indicates that
LoopCare ran the RINGER test on a line that had uncataloged equipment for the
termination.
LoopCare cannot determine whether or not the ringer termination is valid for an
uncataloged termination simply because there is no information to indicate what a
valid termination should be for this line. If more information is required run a FULL
test.
See Also
VER codes related to VER G6 (RINGER TEST- UNCATALOGED EQUIPMENT)

are listed below:

Overview
This VER code will only appear for the LoopCare Ringer series. It indicates that
no ringers were found when LoopCare was expecting ringers as per the line
record. This VER code will not appear for the line that had uncataloged equipment
for the termination. See valid ringer count and termination module.
See Also
VER codes related to VER G8 (NO RINGERS FOUND) are listed below:
4-60

Overview
VER HA indicates that the FTTPDIG test request retrieved one or more service
affecting alarms associated with the ONT and none for the P-OLT. The body of the
GUI report for this test request displays the specific alarm conditions. The highest
priority alarm condition is displayed as the summary message.
For more information, see the section on FTTPDIG Summary Messages in
Chapter 7, and the description of the FTTPDIG request in the Test Request User
Guide.
Example
VER HB: NON SERVICE AFFECTING

ALARM PRESENT
Overview
VER HB indicates that the FTTPDIG test request retrieved one or more nonservice affecting alarms for the ONT, none for the P-OLT, and no service affecting
alarms. The body of the GUI report for this test request displays the specific alarm
conditions.
Guide.
Example
4-62
VER HJ: SYSTEM AND BACKUP

MEMORY RESET
Overview
VER HJ indicates that the FTTPDIG test request retrieved one or more service
affecting alarms associated with the P-OLT. The body of the GUI report for this
test request displays the specific alarm conditions. The highest priority alarm
condition is displayed as the summary message.
Guide.
Example
VER HK: NON SERVICE AFFECTING

ALARM PRESENT
Overview
VER HK indicates that the FTTPDIG test request retrieved one or more nonservice affecting alarms for the P-OLT and no service affecting alarms. The body
of the GUI report for this test request displays the specific alarm conditions.
Guide.
Example
4-64
VER H0:SWITCH TO VG
COMMUNICATION DOWN
Overview
VER H0 indicates that the bPON test executed the GR 909 test successfully but
the GR303 link from the switch to the Voice Gateway is down.
VER HP: FOLLOWING CONFIG NOT

PROV IN VG
Overview
VER HP indicates a provisioning error. A parameter identified in the summary

message may be missing or LoopCare may have found a mismatch between a
parameter value configured in a reference database and the value that was actually provisioned for the network element.
Example

CRV = ****
VIG = ****
4-66
VER I0: TEST OK NOW

Overview
This VER code is returned when the status obtained from the switch indicates that
the DSL has been out of service (OOS) because of physical layer problems, but
all the digital tests and the metallic tests are OK. There is a possibility that a
transient problem like high frequency loss or impulse noise has caused a large
number of errors and caused the DSL to go out of service.
Additional
Information
VER_I0 was added with the implementation of LoopCare/ISDN. The first

VER I0: TEST OK NOW
DIGITAL AND METALLIC TEST OK
DSL OOS LAYER 1
DSL OOS LAYER 1 ALL TEST OK
DSL OOS LAYER 2
DSL OOS LAYER 2 ALL TEST OK
POSSIBLE TRANSIENT PROBLEM
Summary Message.
VER IA: WIRING ERROR - NT1

REVERSED
Overview
VER Code IA occurs on ISDN digital lines. These lines are ordinary two-wire
twisted pairs, but the information they carry is in digital form instead of analog
form, as with a POTS line. ISDN lines are terminated with a device known as an
NT1. Certain kinds of NT1s are polarity-sensitive, that is, they must be wired
correctly between the tip and the ring conductors. If the are wired backwards, you
will get the message WIRING ERROR - NT1 REVERSED, and this VER Code.
There are cases when an unexpected ISDN termination (an NT1) is found, and
that NT1's wiring is reversed. VER Code IA will also be returned in these
instances, (i.e., Unexpected ISDN Termination AND Wiring Error - NT1
Reversed).
Wiring an NT1 in reverse does not interfere with the operation of an ISDN line,
and the customer will normally be experiencing no obvious problems. It is
important, however, that this problem be corrected, since the reversed NT1 will
prevent corrosion control circuitry in the loop from working properly. If an NT1 is
left reversed for too long, the loop will eventually become open.
See Also
VER codes related to VER IA are listed below:

VER IB(Unexpected ISDN Termination)
VER IC(Possible AMI Brite Detected)
VER ID(ISDN Termination Mismatch)
VER IF(Invalid Term for ISDN Line)
4-68
VER IB: UNEXPECTED ISDN

TERMINATION
Overview
VER Code IB occurs only on ISDN digital lines. These lines are ordinary two--wire
NT1.
This VER Code occurs when the line records do not indicate ISDN service, but an
NT1 has been found, which should occur only on ISDN lines. Most likely, the
records are wrong and need correction.
There are cases when an unexpected ISDN termination (an NT1) is found, and
that NT1's wiring is reversed. In these cases, the VER Code IA will be returned,
(i.e. Unexpected ISDN Termination AND Wiring Error- NT1 Reversed).
Sometimes VER Code IB will be accompanied by the message SWITCH
INDICATES ISDN SERVICE. This means that LoopCare asked the switch if it was
wired for ISDN on this loop and got a yes answer. In this case, the most likely
problem is a line record error.
See Also
VER codes related to VER_IB are listed below:

VER IA(Wiring Error - NT1 Reversed)
VER IC: POSSIBLE AMI BRITE

DETECTED
Overview
VER Code IC occurs only on ISDN digital lines. These lines are ordinary two--wire
NT1.
Some ISDN lines are wired through pair-gain systems, such as a SLC-96. When
this is done, most of the line consists of a channel on the pair-gain system. There
is a short loop going from the switch in the central office to the pair-gain system,
and a short loop in the field from the remote end of the pair-gain system to the
subscriber's premises. Usually, LoopCare tests the part of the loop inside the
central office first and then uses a metallic bypass pair to test the outside part of
the loop going to the customer. On certain ISDN lines, especially older ones, this
is not possible. Only the testing inside the office can be done. When this is the
case, LoopCare will set VER Code IC.
See Also
VER codes related to VER IC are listed below:

VER IF(Invalid Term For ISDN Line)
4-70
VER ID: ISDN TERMINATION

MISMATCH
Overview
VER Code ID occurs only on ISDN digital lines. These lines are ordinary two--wire
NT1.
VER Code ID indicates that inconsistent information has been found during
testing. Specifically, the line record indicates that the line has ISDN service, but
LoopCare has checked with the switch serving the subscriber and it is not wired
for ISDN service. This may be a line record error, or it may be a switch wiring
error. If the message VALID NT1 SIGNATURE occurs, it is probably an ISDN line
that has been wired incorrectly.
See Also
VER codes related to VER ID are listed below:

VER IF: INVALID TERM FOR ISDN

LINE
Overview
When testing an ISDN line, LoopCare will sometimes find a termination that
would be valid on other lines, but is incorrect for an ISDN line. For example,
LoopCare might find a PBX or a POTS ringer. When this happens, LoopCare sets
VER Code IF. This means that the termination, while a valid one for some lines, is
not valid for ISDN lines.
VER Code IF is set whenever the loop is good and a valid termination exists, but
the line records or the switch (or both) indicate ISDN. the termination found is one
other than an NT1. If the switch indicates ISDN, it is definitely a wiring error,
probably at the termination. If only the line record indicates ISDN, it could be a
wiring error or a line record error.
See Also
VER codes related to VER IF are listed below:

4-72

Overview
request. VER IG is returned when results indicate a problem with the DSL status,
NT1 power or layers 1, 2, or 3 and further testing is necessary. This VER Code
causes the LMOS/WM to send a FULL request to LoopCare/ISDN via the retest
queue.
Additional
Information
VER_IG was added with the implementation of LoopCare/ISDN. The first

DSL IS IN SERVICE
DSL OUT OF SERVICE
LAYER 1 PROBLEM
LAYER 2 PROBLEM
LAYER 3 PROBLEM
NT1 PRIMARY PWR FAIL
NT1 SECONDARY PWR FAIL
Summary Message.
VER IH: OE MISMATCH

Overview
When an Automatic Customer Station Rearrangement (ACSR) takes place, the

Originating Equipment (OE) associated with the requested Primary Directory
Number (PDN) in the LMOS/WM line record may differ from the OE in the switch
data base. The switch OE is the most current OE. LoopCare/ISDN may find this
discrepancy when it compares the OE from the line record with that from the
switch obtained by a LINESP transaction. This comparison is made every time a
user session starts. When a mismatch is found, VER IH is returned.
Additional
Information
VER_IH was added with the implementation of LoopCare/ISDN. The first

VER IH: OE MISMATCH
SW OE DOES NOT MATCH LR OE
USE S OR R OVERRIDE
Summary Message.
4-74
VER IJ: DENIED SERVICE - ADD

ANALYSIS
Overview
request. It indicates that service is denied by the 5ESS Switch. Although there are
three classes of denied services, (Originating, Terminating and 2-way), the 5ESS
code does not distinguish between the three. Denied service may also be the
results of a CPE terminal being connected to the line.
Additional
Information
VER_IJ was added with the implementation of LoopCare/ISDN. The summary

Summary Message.

Overview
This VER Code is returned when an ISDN request is entered for a line that cannot
be verified as an ISDN line. The line records for these cases are either missing or
indicate ISDN. Other summary messages are shown to indicate the case.
Additional
Information
VER_IK was added with the implementation of LoopCare/ISDN. The first

ERROR IN LINE RECORDS
TESTED WITHOUT LINE RECORDS
Summary Message.
4-76
VER IL: TERMINATION MISMATCH

SUSPECTED
Overview
This VER Code appears only on the TE/TR mask as a result of a Status-L
request. Information from the switch indicates that there appears to be a
termination mismatch, but this condition must be verified by a test. This VER code
causes the LMOS/WM to send a FULL test request to LoopCare/ISDN via the
retest queue.
Additional
Information
VER_IL was added with the implementation of LoopCare/ISDN. This VER Code
and summary message will only appear on the TE/TR mask.

Overview
When the loopback test indicates the DSL is marginal, VER IM is returned.
Because of the time constraints imposed on LoopCare/ISDN, the normal loopback
test time is 16 seconds. In some cases a longer test of 100 seconds may be
performed. In either case, the loopback test may find that the line is marginal and
a longer loopback time of five minutes is needed to determine whether the DSL is
good or bad. See the req.LPBK module in the Request Guide for detailed
performance requirements. When the test finds the DSL marginal, VER IM is
returned.
Additional
Information
VER_IM was added with the implementation of LoopCare/ISDN. The first

COT CU SUSPECT
COULD BE CO-WIRING
COULD BE COT CU
COULD BE RT CU
LAYER 1 PM GOOD
LINE CARD SUSPECT
LONGER TEST IS NEEDED
METALLIC TEST OK
Summary Message.
4-78
VER IN: CPE (NT1) POWER

SUSPECTED
Overview
This VER code appears only on the TE/TR mask as a result of a Status-L request.
Information from the switch indicates that there appears to be an NT1 power
problem, but this condition must be verified by a test. This VER code causes the
LMOS/WM to send a FULL test to LoopCare/ISDN via the retest queue.
Additional
Information
VER_IN was added with the implementation of LoopCare/ISDN. This VER Code
and summary message only appears on the TE/TR mask.
Summary Message.
VER IP: TEST OK PARTIAL TEST

DONE
Overview
When the test performed is OK but is not exhaustive this ver code is returned. To
determine why metallic tests may not have been run, execute the MET or NFULL
request. To determine why complete digital tests were not executed, a STATUS
request may be used to determine if the channels are busy. If any of the BChannels are busy, only logical loopbacks (LPBK) will be performed. For more
information, see the section on VER IP in the Test Results Guide.
This VER code is also applicable to testing of xDSL lines. It is set when the
metallic tests on a line are OK, but wideband tests have not been done due to
equipment problems.
*EXAMPLE*
VER IP: TEST OK PARTIAL TEST DONE LPBK PASS AT NT1
DSL IN SERVICE
ONLY LOGICAL LOOPBACKS DONE
MLT: DIGITAL TEST RESULTS

LPBK L/P RATE TIME CH RESULT
NT1 L 64C 100S B2 PASS
Additional
Information
VER_IP was added with the implementation of LoopCare/ISDN. The first

COULD NOT COMPLETE METALLIC ACCESS
CPE LOOPBACK NOT DONE - NON FIT
CUSTOMER LOOP SPAN L1 PM BAD
DSL IN SERVICE
4-80

LAYER 1 PM COUNT BAD
LAYER 1 PM COUNT GOOD
LAYER 2 PM COUNT BAD
LOOPBACK PASS AT CO LINE CARD
LPBK PASS AT CO LINE CARD
LPBK PASS AT NT1
METALLIC TEST NOT AVAILABLE - TDSL
METALLIC TEST NOT RUN
METALLIC TEST OK
ONLY LOGICAL LOOPBACKS DONE
PARTIAL DIGITAL TEST OK
POSSIBLE LAYER 2 PROTOCOL PROBLEM
POSSIBLE LAYER 3 PROTOCOL PROBLEM
SWITCH INDICATES T-DSL LINE CARD
TEST OK - PARTIAL TEST DONE

Summary Message.
VER IR: CPE (NT1) ON SECONDARY

POWER
Overview
This VER Code appears only on the TE/TR mask as a result of a STATUS-L
request. This VER code indicates that the NT1 is running on secondary power
instead of primary power. Such information can be communicated to the
customers since they may not be aware of it. A FULL request is automatically put
on the retest queue.
Display Example
For a description of the TE/TR mask refer to the document named The Trouble
Report Initial Mask. This document can be found in the LMOS/WM Guide For
Work Item Entry, Col. 462.
Additional
Information
VER_IR was added with the implementation of LoopCare/ISDN. The summary

Summary Message.
4-82
VER IS: SECTIONALIZE WITH

LONGER LPBK
Overview
This VER code is generated from running a FULL or DIG request. Because of
time constraints on LoopCare/ISDN to sectionalize and return results to the user,
it runs only 16 second loopback tests. Occasionally LoopCare/ISDN finds that
longer loopback tests are required to sectionalize a problem. When this is
necessary the software will run a 100 second loopback test. If the 16 second
loopback test passes and the 100 second loopback test fails, the user should run
a 60 second loopback test from Predictor, or the Trunk and Line Work Station
(TLWS) to isolate the location of the problem. The TLWS is located in the Central
Office.
Additional
Information
VER_IS was added with the implementation of LoopCare/ISDN. The first

COT CU SUSPECT
COULD BE RT CU
RUN LPBK WITH 60 SEC
Summary Message.

Overview
VER IT is returned when the switch found a mismatch between the Line Card and
NT1 of a pair gain system. For example, the line card is ANSI standard while the
NT1 is AMI. Other summary messages clarify the type of mismatch that exists.
Additional
Information
VER_IT was added with the implementation of LoopCare/ISDN. The first

AMI LC - ANSI NT1
ANSI LC - AMI NT1
Summary Message.
4-84
VER IU: LINE RECORD SHOWS

TERM MISMATCH
Overview
Additional
Information
VER IU is used to indicate a mismatch between the type of NT1 specified in line
record and the type of NT1 actually detected. The conditions under which VER IU
is returned are:
1.
With FP1 on, Feature 10 set, the Line Record Terminal Equipment (LRTE)
field indicates ANSI (91), and AMI NT1 detected.
2.
With FP2 on, Feature 10 set, the LRTE field indicates AMI (90), and ANSI
NT1 detected.
VER_IU was added with the implementation of LoopCare/ISDN. The first

LINE RECORD INDICATES ISDN
LINE RECORD SHOWS TERM MISMATCH
TESTED WITH PARTIAL LINE RECORDS
WIRING ERROR - AMI NT1 REVERSED
Summary Message.

Overview
VER IV is returned when the switch found a mismatch between the Line Card and
the COT (Central Office Terminal) of a pair gain system. For example, the line
card is ANSI U card while the CU is AMI. Other summary messages clarify the
type of mismatch that exists.
Additional
Information
VER_IV was added with the implementation of LoopCare/ISDN. The first

AMI LC - POSSIBLE ANSI COT CU
ANSI LC - POSSIBLE AMI COT CU
Summary Message.
4-86
VER IW: INVALID WIRE CENTER IN

LINE RECORD
Overview
This message will appear if you are trying to test a Special Services line on a DLC
and there is no wire center in the line record.
VER IZ: DIGITAL ANALYSIS

REQUIRED
Overview
This VER code indicates that LoopCare has tested a T-DSL line and found it to be
in service. Since metallic testing was not available, it is recommended that further
testing be done to isolate the problem.
Additional
Information
VER_IZ was added with the implementation of LoopCare/ISDN. The summary

Summary Message.
4-88
Contents
5-5
VER L1: INCORRECT COIL DETECTED
5-6
VER L2: INCORRECT SECTION DETECTED
5-7
5-8
VER L4: INCORRECT NUMBER OF LOADS
5-9
5-10
5-11
VER LB: LOOP BAD
5-12
VER LD: LOOP DETECT
5-13
VER LE: LOOP DETECT
5-14
VER LF: TEST TRANSFERRED - EXPECT DELAY
5-15
5-16
5-17
5-18
VER LU: LINE IN USE
5-19
VER MC: TEST OK WITH CPE AND MTU CONDITION
5-20
5-21
5-2
5-22
5-23
VER NA: UDLC SIGNATURE FOUND - LTS TEST
5-24
VER ND: TEST NOT MADE FROM THIS FE
5-25
VER NE: CU NOT EQUIPPED FOR TEST ACCESS
5-26
VER NF: NOT SUPPORTED BY TEST HEAD
5-27
5-28
5-29
VER NL: NO LINE RECORD IN SYSTEM
5-30
VER NM: NETWORK MANAGER FAILURE
5-31
5-32
5-33
5-34
5-36
5-37
5-39
VER P3: DC RESISTANCE-MARGINAL
5-41
VER P4: CUSTOMER PREMISE EQUIPMENT BAD
5-42
VER P5): CUST PREM EQUIP SUSPECT
5-43
5-44
5-45
5-46
5-47
5-48
5-49
5-50
5-51
5-52
VER PI: REMOTE SIG LOSS: UNKNOWN CAUSE
5-53
5-54
5-55
5-56
5-57
5-59
VER SU: INTERCEPT
5-60
VER SX: PBX ROUTE ADVANCED TELEPHONE NUMBERS 5-61

5-62
VER T2: SWITCH PROCESS TIMEOUT
5-63
5-64
VER TR: ANOTHER USER IS ACCESSING THIS REMOTE TEST

EQUIPMENT5-65
VER TS: SSA ACCESS REQUIRED BEFORE REQUEST IS
PERFORMED5-66
VER U1: UNEXPECTED THERMISTORS
5-67
VER U2: UNEXPECTED PBX SIGNATURE
5-68
VER U3: UNEXPECTED RINGER TERMINATION
5-69
VER U4: UNEXPECTED INWARD SERVICE
5-70
VER U5: UNEXPECTED CHANNEL TEST RESULTS
5-71
VER U6: UNEXPECTED INTEGRATED PGS/UNEXPECTED UNIVERSAL

PGS5-72
5-73
5-74
5-75
VER VC:CALL FAILED
5-76
VER VP:DROP ACCESS TO CHANGE TEST PORT
5-77
VER VQ:VOICE QUALITY BELOW THRESHOLD
5-78
5-79
VER VT:TESTING ON DEDICATED PORT / *DROP ACCESS FIRST5-80
5-81
5-82
VER W4: POTS Line Circuit Found On ADSL Line
5-83
5-84
5-85
5-86
5-4
5-87
5-88
VER XA: OVRD-EXK/NNX COMBO NOT IN DATABASE
5-89
VER XF: INVALID/INCOMPLETE CIRCUIT INFO
5-90
VER XG:LDS NAME UNKNOWN TO SDV-EM
5-91
5-92
VER XI: INVALID TN
5-93
VER XN: REQUEST NOT ALLOWED IN THIS MODE
5-94
VER XO: TESTABLE VIA STV OPTION
5-95
5-96
5-98
5-99
5-100
VER L0: LOADING REQUIRED ON

LOOP
Overview
LoopCare performed load coil detection via a Harris RTU as part of a DCOILX or
LCOILX request on a loop and detected no load coil with a loop length greater
than the limit for an unloaded pair.
Example

KOHMS VOLTS
KOHMS VOLTS
KOHMS
3500
T-R
3500
T-R
2000
T-R
3500
0 T-G
3500
0 T-G
2000
T-G
3500
0 R-G
3500
0 R-G
2000
R-G
VER L1: INCORRECT COIL

DETECTED
Overview
LoopCare performed load coil detection as part of a DCOILX or LCOILX request

on a loop and detected a load coil with an incorrect value. The proper value of a
load coil should be 88 MH.
Example
VER L1: INCORRECT COIL DETECTED = 44 MH

COIL 2 IN QUESTION
KOHMS VOLTS
KOHMS VOLTS
KOHMS
3500
T-R
3500
T-R
2000
T-R
3500
0 T-G
3500
0 T-G
2000
T-G
3500
0 R-G
3500
0 R-G
2000
R-G
5-6
VER L2: INCORRECT SECTION

DETECTED
Overview

on a loop and detected a load coil section with an incorrect length. The proper
length of a load coil section is 6000 FT, except for the first section, which should
be 3000 FT.
Example
VER L2: INCORRECT SECTION DETECTED = 8000 FT

SECTION 3 IN QUESTION
KOHMS VOLTS
KOHMS VOLTS
KOHMS
3500
T-R
3500
T-R
2000
T-R
3500
0 T-G
3500
0 T-G
2000
T-G
3500
0 R-G
3500
0 R-G
2000
R-G

Overview

on a loop and detected that the end load coil section was too long. The proper
be 3000 FT.
Example
VER L3: END SECTION TOO LONG = 8000 FT

KOHMS VOLTS
KOHMS VOLTS
KOHMS
3500
T-R
3500
T-R
2000
T-R
3500
0 T-G
3500
0 T-G
2000
T-G
3500
0 R-G
3500
0 R-G
2000
R-G
5-8
VER L4: INCORRECT NUMBER OF

LOADS
Overview

on a loop and detected an incorrect number of load coils for cable acceptance.
When used, load coils should be spaced 6000 FT apart, except for the first load
coil, which should be 3000 FT from the switch.
Example
VER L4: INCORRECT NUMBER OF LOADS DETECTED

KOHMS VOLTS
KOHMS VOLTS
KOHMS
3500
T-R
3500
T-R
2000
T-R
3500
0 T-G
3500
0 T-G
2000
T-G
3500
0 R-G
3500
0 R-G
2000
R-G

Overview

on a loop and detected a double load coil. The proper value of a load coil should
be 88 MH. A double load coil will have a value of approximately 176 MH.
Example
VER L5: DOUBLE LOAD DETECTED = 174 MH

COIL 2 IN QUESTION
KOHMS VOLTS
KOHMS VOLTS
KOHMS
3500
T-R
3500
T-R
2000
T-R
3500
0 T-G
3500
0 T-G
2000
T-G
3500
0 R-G
3500
0 R-G
2000
R-G
5-10

Overview

on a loop and detected a load coil section with a missing load coil. The proper
be 3000 FT. Each load section should have one load coil, with a value of 88 MH.
Example
VER L6: MISSING LOAD DETECTED = 12000 FT

KOHMS VOLTS
KOHMS VOLTS
KOHMS
3500
T-R
3500
T-R
2000
T-R
3500
0 T-G
3500
0 T-G
2000
T-G
3500
0 R-G
3500
0 R-G
2000
R-G
VER LB: LOOP BAD

Overview
VER LB indicates that the fault is between the line card and NT1 (for a simple UInterface Digital Subscriber Line - U-DSL) or between the RT channel unit and
NT1 (for a SLC line). Another possible cause is a mismatch between the line card
and the NT1, and therefore metallic access could not be achieved (usually
because of an office overflow condition). In this last case, without metallic access,
the type of NT1 cannot be identified.
Additional
Information
VER LB: LOOP BAD
COULD NOT COMPLETE METALLIC ACCESS
DSL OOS LAYER 1
DSL OOS LAYER 2
Refer to ISDN Summary Messages for a brief description of each Summary
Message.
5-12
VER LD: LOOP DETECT

Overview
A TN has changed from an initial state where no outside loop is connected to the
TNs Central Office (CO), to a loop state where the customers actual outside plant
(i.e. cable, termination, etc.) is connected to the CO equipment.
VER LE: LOOP DETECT

Overview
5-14
A termination is seen, but the average TG and RG capacitance is less than

MIN_LOOP_CAPACITANCE (set in M2.env). This condition indicates that the
loop is too close to the Central Office (a very short loop) or that it is a UDLC or
Splitter.
VER LF: TEST TRANSFERRED EXPECT DELAY

Overview
This VER Code appears when the test has been transferred from LoopCare.
VER LM: REMOTE TEST-EXPECT

DELAYED RESULTS
Overview
LoopCare testing through certain kinds of equipment may take longer than you
normally would expect. When this happens, you will see this temporary message
at the bottom of your screen to warn you of the extended testing time.
Additional
Information
The new message will appear temporarily, when it applies, on line 24 of the TV,
STV, TE/TR, DISP, and MSCR masks. It is printed after the initial line 24 message
but before LoopCare results are returned. On the TV and STV masks, the
message is printed for both initial and subsequent test requests on a line. When
results are returned, the final VER codes and test results overwrite the message.
5-16

Overview
VER LS is returned when the loop is suspect. The ISDN line that is out of service
is a T-Interface Digital Subscriber Line (T-DSL) and a digital test to the line card
passed. The CPE type is unknown, therefore a digital test could not be run to the
CPE.
Additional
Information
SWITCH INDICATES ISDN SERVICE
Message.
VER LT: LONG TEST-EXPECT

DELAYED RESULTS
Overview
At present results are generally returned within one minute. With ISDN FP3 any
user can request a long loopback test, or to sectionalize digital loopback tests may
take more than one minute.
In such circumstances the user should be informed that the test is going to take
more than one minute. VER LT should be returned before the complete results are
available. See the section on VER LT in the test results guide.
Example

CRAFT: DC SIGNATURE MLT: DC SIGNATURE
5-18
AC SIGNATURE
KOHMS VOLTS
KOHMS VOLTS
3500
T-R
3500
T-R
11
3500
0 T-G
3500
0 T-G
1469
3500
0 R-G
3500
0 R-G
KOHMS
1336
RNGRS
YES T-R
T-G
R-G
VER LU: LINE IN USE

Overview
This VER code will appear when a subscriber is calling on the line to be tested via
the TE mask. It indicates that the line is in use and cannot be tested immediately
by LoopCare.
After a default waiting period of 60 seconds, VER LU will initiate a retest on the
line if the RETEST feature is on.
Additional
Information
If a line in use times out of RETEST, the VER code remains LU.
(The line-in-use condition is known to the RSA as either LIU or LU.)
VER MC: TEST OK WITH CPE AND

MTU CONDITION
Overview
This VER code is used by LMOS to indicate a TEST OK condition on a line that
has a Maintenance Termination Unit (MTU), and a CPE termination. The remote
possibility exists however, that it could be a high resistance open problem. This
VER code is displayed on the TR, TV, TEST, DMLT, or MSCR mask, and will be
used for flowthrough.
Additional
Information
This VER Code and summary message is sent to either the TR, TV, TEST, DMLT,
or MSCR mask.
VER MC: TEST OK CPE/MTU
Refer to MTU Summaries for a brief description of this summary message.
See Also
VER codes related to VER MC (TEST OK CPE/MTU) are listed below:

VER_0C
5-20
CPE OR HIGH RESISTANCE OPEN
VER MD: MDF TEST

RECOMMENDED
Overview
This VER code can be caused by two conditions unrelated except for the fact that
an MDF access is necessary to get further information about the condition on the
line.
The first condition is AC FEMF CURRENT is detected on the line and LoopCare
testing is stopped. No DC tests have been run. An MDF access is necessary to
determine if the AC condition is in or out of the CO.
The second condition is when a CO test is run from the TV mask on a line that has
a Crossbar office over a no test access. LoopCare cannot run the CO tests (line
circuit configuration and draw and break dial tone test) over a no test trunk on a
crossbar line. To get the CO test to run the test must be made from an MDF trunk.
Additional
Information
The MDF test is recommended for this VER condition because by using an MDF
access it is possible to sectionalize the AC FEMF and enable you to determine its
source.
This condition could be caused by excess voltage at the frame, although excess
AC FEMF from the outside part of the line could cause the problem as well.
See Also
VER codes related to VER MD (MDF TEST RECOMMENDED) are listed below:
VER 12AC FEMF FAULT
VER 13HAZARDOUS POTENTIAL
VER 16AC FEMF MARGINAL
VER 26MDF TEST RECOMMENDED- LOW RESISTANCE
VER 72MDF TEST RECOMMENDED- PERMANENT SIGNAL
VER MTMDF TESTABLE ONLY

Overview
LoopCare could not test this line because it is either the primary number for a hunt
group or is part of a multi-line hunt group.
Check the Switch office records to identify hunt group and member number
information needed to test the line.
The following summary message could appear with VER MH instead: MEMBER
OF MADN. This message indicates that LoopCare could not test this telephone
number because it is a Multiple Appearance Directory Number associated with
multiple lines.
5-22

Overview
The loop can only be tested via an MDF access. This may be due to equipment in
the central office (i.e., Dial Long Lines) that prohibits LoopCare testing. This
equipment is bypassed when testing is done on an MDF trunk.
Additional
Information
Although LoopCare cannot test through the C.O. equipment, the line circuit and
draw and break dial tone tests are run. The results are presented in the CENTRAL
OFFICE category of the detailed results in this example. If there is a problem the
appropriate messages will be in the summary.
Example

MLT CAN'T TEST THROUGH C.O. EQPT
See Also
VER codes related to VER MT (MDF TESTABLE ONLY) are listed below:
VER 26
MDF TEST RECOMMENDED- LOW RESISTANCE
VER 72
MDF TEST RECOMMENDED- PERMANENT SIGNAL
VER MD
MDF TEST RECOMMENDED
VER NA: UDLC SIGNATURE FOUND LTS TEST

Overview
5-24
This VER Code is applicable only when the UDLC Overlay feature is enabled.
This VER Code indicates that the DCTU detected a USLC signature and the test
was routed to the UDLC overlay testhead, either an EMU or LTS. The overlay test
head which is connected to the PGTC will run the transaction.
VER ND: TEST NOT MADE FROM

THIS FE
Overview
The telephone number was not tested because the FE that initiated the request is
connected to a DCN that is different from the DCN that is associated with this
telephone number. Remember that when a request is initiated from a FE that does
not contain the telephone number's line record, that FE requests the line record
from the FE that does have it. Once it has the line record, it tests the line. This
usually works fine because both FEs are usually connected to the same DCN so
that either one can access the telephone number. When there is more than one
DCN, however, the FEs may be connected to different DCNs. In this case the
initiating FE requests the line record but then can't test because it cannot
physically access the line through the DCN to which it is connected.
Additional
Information
If this VER code is returned, try to access a FE that is connected to the DCN that
can test this line.
VER NE: CU NOT EQUIPPED FOR

TEST ACCESS
Overview
5-26
The equipment in the slot in the Loop Terminating Equipment (LTE) (as derived
from either the OE if testing by TN or Slot entry if testing by shelf-slot-line circuit
information) does not support metallic test access.
VER NF: NOT SUPPORTED BY TEST

HEAD
Overview
A CO test was requested for an EDGE with a firmware release less than 4.0.
The test head as currently configured does not support the requested function.
This can probably be corrected by downloading the most current firmware version
to the test head. In some cases a new hardware option or a new test head may
be needed.

Overview
VER NG is returned when the test request made is invalid for a T-Interface Digital
Subscriber Line (TDSL). An example is the PML1 request.
Additional
Information
VER NG: INVALID REQUEST FOR TDSL
Refer to ISDN Summary Messages for a brief description of this Summary
Message.
5-28

Overview
The line record did not contain an OE code. Notify the LoopCare system
administrator.
Additional
Information
The following summary messages may be returned with VER NK when the LNP
R2 feature is enabled. Refer to the LNP Summaries in Chapter 7. EXK/LRN
REQUIRED FOR PORTED NUMBER VALID OE NEEDED TO TEST PORTED
NUMBER
VER NL: NO LINE RECORD IN

SYSTEM
Overview
This is a Special Services TN and to do No-test trunk testing on this line, there
must be a line record on the system. This error message means either:
There is no line record for this TN
+ LoopCare could not find the line record.
5-30
VER NM: NETWORK MANAGER

FAILURE
Overview
Additional
Information
A failure occurred while sending a message from a LoopCare process to another

LoopCare or external application process. This failure could occur because:
The group containing the destination application process is down.
The destination application process' message queue is full due to high

load.
The destination process is on another front end (FE) and either the front
end or the network manager (NM) software is not operating.
VER NM CANNOT SEND TO APPLICATION PROCESS

Overview
When the switch denies access because the requested Directory Number (DN) or
Originating Equipment (OE) (line card equipment number in 5ESS) is not in the
switch data base, VER NP with the appropriate summary message is returned.
Currently the 5ESS switch denies a test request if the requested DN is not a
Primary Directory Number (PDN) and returns VER NP with the summary
message "NOT PRIMARY DN". In the future, when a shared or non shared DN
becomes a legal parameter for entering a test request, this summary message will
not be displayed.
Additional
Information
VER NP: DN NOT IN SWITCH DATABASE
VER NP: INVALID DN - EXTRA DIGITS REQUIRED
VER NP: LCEN NOT IN SW DATABASE
VER NP: NO 5ESS LINE CARD
VER NP: NOT PRIMARY DN
Message.
5-32

Overview
The NNX of the telephone number that LoopCare has been requested to test is an
NNX that is not served by the LoopCare system. LoopCare knows this by
checking the LoopCare Access table which specifies which NPA-NNXs are or are
not testable.
See Also
VER codes related to VER NS (LINE NOT SERVED BY MLT) are listed below:
VER NT
LINE NOT MLT TESTABLE
VER NV
LINE NOT VERIFIED

Overview
VER NT is returned when the line being requested is not testable by LoopCare.
Some causes are the following:
If the line being tested has a Subscriber Loop Multiplexer (SLM) system,
LoopCare recognizes this and stops testing.
CMU/RMU testing has been requested and is not permissible, or a 14-digit

line has been tested, but the 14-digit feature has not been activated.
If a Bridged Tap test (BT) was requested, and the condition of the loop
under test prohibits the test from being performed.
If an LRN and an SPID are successfully retrieved from the LRN Server,
LoopCare checks the SPID table. If the SPID is CLEC owned or ILEC
owned but not LoopCare testable, LoopCare stops testing and returns the
VER NT code and summary message depending on the origin of the test
request and value of the SPID Type:
FOR TE/TR (SPID Type = C or N)
VER NT: NO TESTING AVAILABLE
FOR PST (SPID Type = C or N)
VER NT: TEST WAS NOT MADE
FOR TV, EUGUI, API (SPID Type = C)
VER NT: LINE NOT SERVED BY <COMPANY NAME>
MESSAGE 1 (from OAM SPID table)
FOR TV, EUGUI, API (SPID Type = N)
VER NT: TN NOT TESTED BY <COMPANY NAME> LOOPCARE
NOTE:
Messages 1 and 2 are displayed only if the Display Message field is
checked on the OAM SPID form.
Additional
Information
5-34
If you received this VER code and the line record indicates that it is a POTS line,
you might want to run a LINESP request. This request may tell you to use F10
override to force an ISDN test. Run either a FULL or LINESP request with the F10
override. A summary message may come back indicating that it is an ISDN T-DSL
line. If that is the case, the line record information is incorrectly indicating that this
is a POTS line. If the test comes back with a VER code IK, then the line record is
correct.
VER NT is also returned when the Local Number Portability (LNP) feature is
enabled and the line under test is POTS MLHG or PBX on an LTS.
The following summary messages may be returned with VER NT when the: LNP
R2 feature is enabled.
LINE RECORD INDICATES NOT-IN-SERVICE
LINE RECORD INDICATES PORTED-OUT
USE EXK or LRN OVERRIDE TO TEST
The following summary message may be returned with VER NT when a test
request is submitted for a LIM that is not supported:
* UNSUPPORTED LTE CARD TYPE
The following summary message may be returned with VER NT when a line to be
tested is in galvanic isolation mode:
* LINE IN GALVANIC ISOLATION MODE
When a test is performed via a DigiTest EDGE without an MTM, the following
message may be displayed.
NO METALLIC TEST FACILITY
A DigiTest EDGE without an MTM cannot perform metallic tests.
One of the following summary messages may appear if the switch is a DMS100
switch:
* REMOTE CALL FORWARDING
* VIRTUAL DIRECTORY NUMBER
* SPECIAL TRANSLATION
* CONFERENCE DN
* UNASSIGNED
* DIRECT INWARD SYSTEM ACCESS DN
See Also
VER codes related to VER NT (LINE NOT MLT TESTABLE) are listed below:
VER NS
LINE NOT SERVED BY MLT
VER NV
LINE NOT VERIFIED

Overview
This VER code will only appear on BORs or MORs. An LoopCare test was
requested for the line but the test could not be made because the trouble was a
subsequent report, or through TE/TR when the NPA-NNX is defined in the NNXF
as NDA (see LMOS/WM documentation number 413.NNX).
Additional
Information
When processing this trouble follow local procedures for handling subsequent
reports. In other cases, the trouble description and other relevant data on the
report should provide information to make a decision.
See Also
VER codes related to VER NV (LINE NOT VERIFIED) are listed below:
5-36
VER NS
LINE NOT SERVED BY MLT
VER NT
LINE NOT MT TESTABLE
VER P1: DC RESISTIVE FAULT:

PREMISES
Overview
This VER code indicates that LoopCare has tested a line with a Maintenance
Termination Unit (MTU) on it. The MTU is a device that may be installed near the
customer's protector. It is recognized by LoopCare from its electrical signature
and helps the system determine whether faults are in the network or on the
customer's premises.
In this case, LoopCare identifies a resistive fault (below the local fault thresholddefault of 150 K ohms) and determines that the fault is on the customer's
premises.
With this fault condition, VER code P1 will be displayed with either an open or a
termination.
Additional
Information
short or ground is a trouble.
When the customer goes off-hook the current from the central office line circuit
battery flows on the line. This current goes out from the CO on the ring side of the
line and flows between tip and ring at the receiver (ROH). It then completes the
loop by returning to the ground in the central office on the tip side of the line. If
there is a short at any other point in the circuit then some or all of the current will
not reach the receiver but will take the shorter path to the CO ground. Likewise, if
there are any other paths to ground other than the ground in the CO, the current
will leak off the line before it can complete the circuit. How much current leaks
from the circuit at the ground or short fault depends on the severity of the resistive
fault. The harder the problem the more current will leak from the circuit.
See Also
5-38

VER codes that are related to VER P1 (DC RESISTIVE FAULT: PREMISES) are
listed below:
VER 21
GROUND FAULT
VER 22
SHORT FAULT
VER P2
DC RESIST FAULT: PREMISES
VER P2: DC RESIST MARGINAL:

PREMISES
Overview
This VER code indicates that LoopCare has tested a line with a Maintenance
Termination Unit (MTU) on it. The MTU is a device usually located near the
customer's protector. It is recognized by LoopCare from its electrical signature
and helps the system determine whether faults are in the network or on the
customer's premises.
In this case, LoopCare identifies a resistive trouble above the local fault threshold
but below 300 K ohms and determines that the fault is on the customer's
premises.
Additional
Information
short or ground is a trouble.
When the customer goes off-hook the current from the central office line circuit
battery flows on the line. This current goes out from the CO on the ring side of the
line and flows between tip and ring at the receiver (ROH). It then completes the
loop by returning to the ground in the central office on the tip side of the line. If
there is a short at any other point in the circuit then some or all of the current will
not reach the receiver but will take the shorter path to the CO ground. Likewise, if
there are any other paths to ground other than the ground in the CO, the current
will leak off the line before it can complete the circuit. How much current leaks
from the circuit at the ground or short fault depends on the severity of the resistive
fault. The harder the problem the more current will leak from the circuit.
In this case the short is not a very severe problem, it is marginal (note the
summary message LIGHT SHORT). Repair people may have a more difficult time
locating the trouble since it is only a marginal one.
See Also
5-40

VER codes that are related to VER P2 (DC RESIST MARGINAL: PREMISES) are
listed below:
VER 21
GROUND FAULT
VER 22
SHORT FAULT
VER P1
DC RESIST FAULT: PREMISES
VER P3: DC RESISTANCEMARGINAL

Overview
This VER code indicates that LoopCare has tested a line that may have a faulty
telephone set connected to it. LoopCare recognizes this condition from the line's
electrical signature.
VER P4: CUSTOMER PREMISE

EQUIPMENT BAD
Overview
When the status obtained from the switch, the digital loopback test results, or the
performance monitoring data indicates that the NT1 or T-interface on the
customer side of the NT1 has a problem, VER P4 is returned.
Additional
Information
VER P4: CUST PREM EQUIP BAD
VER P4: NT1 BAD
VER P4: NT1 POWER SUPPLY BAD
VER P4: T-INTERFACE HAS PROBLEM
COULD BE T-INTERFACE
DIGITAL TEST OK
DSL IN SERVICE
CUSTOMER PREMISE EQUIPMENT BAD
DSL OOS LAYER 1
DSL OOS LAYER 2
LAYER 1 PM GOOD
LAYER 2 PM SHOW HIGH CRC ERRORS
LAYER 2 PM SHOW UNEXPECTED MESSAGES
METALLIC TEST OK
POSSIBLE INTERFACE-TERMINAL MISMATCH
STATUS SHOWS CUST T-INT PROBLEM
T-DSL LOOP OR CPE PROBLEM
Message.
5-42
VER P5): CUST PREM EQUIP

SUSPECT
Overview
When either the status or the tests indicate, but cannot conclusively determine,
that the problem is in the customer premises equipment (either in the NT1 or in
the T-interface), VER P5 with an appropriate summary message is returned. If the
status indicates that the DSL is in service but the switch is receiving too many
user errors, or the digital test fails at the NT1 and passes at the line card but the
metallic test does not find any loop faults, a long loopback test at the NT1 should
be done before telling the customer that the problem is on their side of the NT1.
Additional
Information
VER P5: CUST PREM EQUIP SUSPECT
VER P5: NT1 SENT A DYING GASP
VER P5: NT1 SUSPECT
VER P5: PROBABLE NT1 COULD BE LOOP
CUST PREM EQUIP SUSPECT
COULD BE TDSL LOOP
LAYER 1 COUNT BAD
LAYER 1 PM COUNT CORRUPT
LAYER 1 PM GOOD
LPBK PASS AT CO LINE CARD
METALLIC TEST OK
NT1 SENDING TOO MANY ERRORS
REMAINS IN TRANSITION STATE
Message.
VER P6: CUST PREM EQUIP IN TEST

MODE
Overview
When the status indicates that the switch has taken the DSL out of service
because the customer is performing a test on the NT1, this VER code is returned.
Additional
Information
Additional summary messages that may appear with this VER code are:
DSL OUT OF SERVICE
Message.
5-44
VER P7: CPE (STATION SET) BAD OR

INVALID
Overview
request. It indicates that the station set has been taken out of service either
because it is invalid or defective.
Additional
Information
Message.

Overview
This VER code appears on the TE/TR mask as a result of a STATUS-L request. It
indicates that the channel is out of service because the T-interface (customer
premises) of a U configuration is down.
Display Example
For a description of the TE/TR mask refer to the document named "The Trouble
Report Initial Mask". This document can be found in the LMOS/WM Guide For
Additional
Information
Message.
5-46

Overview
This VER code indicates that LoopCare has tested a U-DSL line and found it to be
in service. The results of the metallic test was OK. However, the NT1 primary
power has failed indicating that the line is on secondary power.
Additional
Information
Message.

Overview
This VER code is returned when the status of the D or B channels indicate an
excessive number of Layer 2 problems. Either one CPE is responsible for
generating the maximum number of PERs or the problem is found uniformly
among all the users. With this condition the line may or may not be in service.
Additional
Information
DIGITAL TEST OK
DSL IN SERVICE
DSL OOS LAYER 2
FURTHER PER ANALYSIS REQUIRED
LAYER 2 PROBLEM
LAYER 1 PM GOOD
LAYER 2 PM SHOWS UNEXPECTED MESSAGES
METALLIC TEST OK
PERS INDICATE SEVERAL PROBLEMS
PERS SHOW UNIQUE PROBLEM
Message.
5-48
VER PB: POSSIBLE PROTOCOL

PROBLEM
Overview
When the status indicates that the link layer remains in a transitional state
suggesting there is a possible layer 2 protocol problem, this VER code is returned.
Either there is an internal (switch) software or hardware error which prevents a
link from being used, or the response and acknowledgment between the switch
and the CPE is not correct. When the LMOS/WM asks for the status of the DSL
via the STATUS-L request, status messages which indicate protocol problems
generate VER PB with specific summary messages. The user may or may not
want to put these cases into the retest queue. When the lines are retested and
remain in a transitional state, VER PB is returned with a specific summary
message.
VER PB is also a possible xDSL protocol error that prevents xDSL modems from
synchronizing. This may be caused by invalid digital service parameters in
modem configuration on the xTU-C or xTU-R or difference in protocol versions
used.
Additional
Information
DSL IN SERVICE
LAYER 1 PM GOOD
LAYER 2 PM SHOWS PERS EXIST
LAYER 3 PM SHOWS PERS EXIST
LINE OUT OF SERVICE
LINK REMAINS IN DSL INIT STATE
LINK TRANSITIONING BETWEEN STATES
Message.

Overview
When a high rate of layer 3 protocol problems in the Q.931 signaling process or
X.25 protocol problems occur, this VER code is returned. Either one CPE is
responsible for generating the maximum number of PERs or the problem is found
uniformly among all the users. The line may or may not be in service with this
condition.
Additional
Information
CPE GENERATING ERRORS
CPE IS OUT OF SERVICE
DIGITAL TEST OK
DSL IN SERVICE
DSL OOS LAYER 3
FURTHER PER ANALYSIS REQUIRED
LAYER 1 PM GOOD
METALLIC TEST OK
PERS INDICATE SEVERAL PROBLEMS
PERS INDICATE UNIQUE PROBLEMS
Message.
5-50
VER PD: SIGNAL LOSS FROM

REMOTE END
Overview
When the status is obtained from the Loop Terminating Equipment (LTE), the
service parameters retrieved from the LTE indicate that the Central Office LTE
modem has detected a loss-of-signal from the customer premises end, and the
customer powering off their xTU-R modem most likely causes this, VER PD is
returned. It could also have been caused by a sudden break in the loop between
the LTE and the Customer Premises. If VER PD has been returned after a
DSLDIG, it is recommended that a FULLX be run to verify the condition of the
loop.
If VER PD has been returned after a FULLX request was made, it indicates that
LoopCare verified that the loop between the customer premises and the LTE in
the Central Office was tested and found not to have any problems. Also, unless
indicated by additional summary messages, no additional problems have been
detected with the Customer Premises Equipment.
If VER PD has been returned after a DSLDIG request was made, it indicates that
only the status of the LTE port and the Customer Premises Equipment was tested.
No tests on the condition of the loop in between them were made.
Additional
Information
VER_PD was added with the implementation of LoopCare G10I14.7, Digital

Testing for the Stinger DSLAM.
Refer to Digital Service Summary Messages for a brief description of each
Summary Message.

Overview
When the status is obtained from the DSLAM, the service parameters retrieved
indicate a power problem in the ATU-R or ATU-C.The cause of the problem could
be power failure or power status unavailable.
Additional
Information
The person in charge of system maintenance should be notified of this condition.
5-52
VER PI: REMOTE SIG LOSS:

UNKNOWN CAUSE
Overview
service parameters retrieved from the LTE indicate that the Central Office LTE
modem has detected a loss-of-signal from the customer premises end and the
cause of the loss-of-signal is not known, VER PI is returned. This situation can be
caused by a sudden break in the loop between the LTE and the Customer
Premises. If VER PD has been returned after a DSLDIG, it is recommended that a
FULLX be run to verify the condition of the loop.
If VER PI has been returned after a FULLX request was made, it indicates that
If VER PI has been returned after a DSLDIG request was made, it indicates that
Additional
Information
VER_PI was added with the implementation of LoopCare G10I14.7, Digital

VER PI: REMOTE SIGNAL LOSS: UNKNOWN CAUSE
Summary Message.

Overview
from the DSLAM indicate that the customer xDSL equipment has encountered a
problem, VER PR is returned. It is recommended that the customer be asked to
reset the CPE by powering it on or off, and retest the line to see if the condition is
permanent. If the condition can be reproduced, the CPE may need to be replaced.
If VER PR has been returned after a FULLX request, it indicates that the loop
between the customer premises and the DSLAM in the Central Office was tested
and found not to have any problems. Also, unless indicated by additional
summary messages, no additional problems have been detected with the
Customer Premises Equipment.
Example
Additional
Information
VER PR: XDSL CPE EQUP PROBLEM
XTUR NOT RESPONDING
XTUR LOSS OF SIGNAL DETECTED
XDSL LINE OUT OF SERVICE
Summary Message.
5-54
VER S0: LINE IN SERVICE - ADD

ANALYSIS
Overview
request. VER S0 is returned when results indicate that there is no problem with
the DSL status, NT1 power or layers 1, 2, or 3, however, further testing may be
required depending on the customer trouble report. This VER Code causes the
LMOS/WM to send a FULL request to LoopCare/ISDN via the retest queue.
Display Example
For a description of the TE/TR mask refer to the document named "The Trouble
Report Initial Mask". This document can be found in the LMOS/WM Guide For
Additional
Information

Overview
The line records indicate that the line LoopCare has been requested to test is a
protected service (i.e., alarm, etc.). LoopCare will not test the line unless you
override the line record information.
Additional
Information
Before you test the line by overriding the line records, you should first obtain the
customer's permission to do so. If you receive permission to test, you can override
the line records in the following ways:
TEST Enter Y in OVERRIDE LINE RECORDS? field
TV
5-56
Enter Y or P in OVER field
VER SS: SPECIAL SERVICES

REQUIRED
Overview
LoopCare has detected the electrical signature of one of the following special
services equipment:
MFT LOOP SIGNAL EXTENDER
DIGITAL CHANNEL CARRIER
Additional
Information
Special services is required to maintain LoopCare loop signal extenders and

digital channel carriers. It is appropriate then to route this case to the people
responsible for special services.
The DC SIGNATURE that identifies the two special services that are included in
VER SS are given below:
SPECIAL SERVICES REQUIRED
DC SIGNATURE
EQUIP
KOHMS
LOOP SIGNAL EXTENDER
>1000
DIGITAL CHANNEL CARRIER
VOLTS
T-R
75-90
-9 to -14
R-G
75 to 90
-9 to -14
R-G
>1000
T-R
50 to 800
-55 to -65
R-G
50 to 800
-55 to -65
R-G
OR
>1000
T-R
30 to 40
-36 to -40
T-G
30 to 40
-36 to -40
R-G
OR
>1000
T-R
140 to 150 -40 to -48
T-G
140 to 150 -40 to -48
R-G

When these signatures are identified, LoopCare will set the VER SS and specify
the particular piece of equipment it saw.
5-58
VER ST: INTERCEPT - ADD

ANALYSIS
Overview
request. LMOS has determined via the ISDN feature that some of the services on
the DSL are on intercept. Unless every service on the requested PDN or DN is on
intercept, testing is possible. This VER code is necessary in order for LMOS/WM
to send these cases to LoopCare/ISDN via the retest queue for a FULL test.
Additional
Information
Refer to ISDN Summary Messages for a brief description of this summary
message.
VER SU: INTERCEPT

Overview
LoopCare has tested a line and found it to be on intercept. The VER SU stands for
"SUspended service". No further LoopCare tests are made once an intercept
condition is identified.
Additional
Information
LoopCare detects an intercept condition when it tests from the LoopCare DC

SIGNATURE. The following signatures identify an intercept condition:
1.
Crossbar or Step by Step office- LoopCare DC RESISTANCE of 35 Kohms

on at least two of the three sides of the line.
2.
ESS office- Detects a 480 Hz tone in addition to the LoopCare DC

RESISTANCE specified below:
> 1000 K T-G
0.3 to 0.8 K R-G
When an intercept is detected, it is recommended that you determine whether or

not the line is supposed to be on intercept by calling the business office. If the line
is supposed to be on intercept, you can close out the report. If the line is not
supposed to be on intercept, follow local procedures to correct the situation.
5-60
VER SX: PBX ROUTE ADVANCED

TELEPHONE NUMBERS
Overview
LoopCare has tested a PBX line and found that it was possibly a route advanced
line. A PBX route advanced line is a PBX extension that is dialed direct, bypassing
the regular PBX trunks.
Additional
Information
LoopCare will only set this VER code when it finds a ground start PBX indicated in
the line records, an intercept signature, and one of the following switch types:
1ESS, 2ESS, 3ESS, 5ESS using a no-test trunk, DMS-10, and DMS-100AC.

Overview
Your LoopCare request has timed out while testing was in progress. This problem
can be caused by data link problems between the various parts of the system.
The best thing to do is try again.
Additional
Information
The person responsible for system maintenance should be notified if this happens
repeatedly.
5-62
VER T2: SWITCH PROCESS

TIMEOUT
Overview
The request has timed out while testing was in progress. This VER Code can be
caused by the following factors:
The 5E login failed, MML commands response not received in time the
process timed out, or the switch is busy.
Verify whether or not the communication link to the 5ESS is running by attempting
to have someone log into the 5E IOP port using LoopCares login and password. If
the link is down or login fails due to incorrect login/password contact the 5ESS
Switch Administrator for help.

Overview
VER TB is returned from the switch if a digital test was requested and not run
because the line was busy. A busy line condition will cause a logical loopback test
to be run instead of the physical loopback. Do to AMI channel hardware limitations
this VER code will be generated if a logical loopback test is run on a line which
contains an AMI channel unit.
Additional
Information
DSL IN SERVICE
LAYER 2 COUNT BAD
POSSIBLE LAYER 2 PROTOCOL PROBLEM POSSIBLE LAYER 3
PROTOCOL PROBLEM
Message.
5-64
VER TR: ANOTHER USER IS

ACCESSING THIS REMOTE TEST
EQUIPMENT
Overview
This VER Code is displayed when a user requests a test from the End User GUI
or TV Mask and one of the following conditions exists:
another user previously requested a test that uses the same remote test
equipment.
the test waited more than two minutes for the remote test equipment to
become available.
This VER Code is applicable under the following conditions.
The Loop Detect feature is turned on.
An RMU-S is being used to test Stinger Loop Terminating Equipment

(LTE).
A FULLX test request is made for a line served by an LTE when a test is
already in progress for another DSL line on the same LTE.
VER TS: SSA ACCESS REQUIRED

BEFORE REQUEST IS PERFORMED
Overview
5-66
The line record says that this is a Special Services telephone number on a DLCS
that is accessible via the SSA request. To do any testing, first establish access on
the line by doing an SSA request.
VER U1: UNEXPECTED

THERMISTORS
Overview
LoopCare is testing a line with a cataloged termination and it suspects an open.

When a thermistor check is run on the line, LoopCare identifies a thermistor.
However, according to the line records, the line should not have a thermistor.
Additional
Information
It is possible that the line records are incorrect for this line and thermistors should
be expected. However, you must verify this. If the records are wrong, take the
appropriate measures to correct them. If the records are correct, handle the
condition based on the customer report.
See Also
VER codes related to VER U1 (UNEXPECTED THERMISTORS) are listed below:

VER U2 UNEXPECTED PBX SIGNATURE
VER U3 UNEXPECTED RINGER TERMINATION
VER U4 UNEXPECTED INWARD SERVICE
VER U6 POSSIBLE RECORD ERROR UNEXPECTED INTEGRATED/
UNIVERSAL PGS
VER U2: UNEXPECTED PBX

SIGNATURE
Overview
LoopCare test results indicate that the LoopCare DC SIGNATURE matches one
of the valid LoopCare DC SIGNATURES for a PBX. However, the line records
indicate that the termination is not a PBX termination.
Additional
Information
It is possible that the line records are not correct and that the PBX signature
identified is valid. You must attempt to verify whether or not the line records are
correct. Appendix E has a list of valid DC signatures which could be helpful if you
want to identify the specific signature. If they are wrong, take the appropriate
steps to correct them. If they are correct, then the DC results most likely indicate
some sort of DC fault (short, ground, cross, etc.).
See Also
VER codes related to VER U2 (UNEXPECTED PBX SIGNATURE) are listed

below:
VER U1 UNEXPECTED THERMISTOR
UNIVERSAL PGS
5-68
VER U3: UNEXPECTED RINGER

TERMINATION
Overview
LoopCare tests a line whose records indicate that it is a ground start PBX.
However, an AC signature is present and the T-R values are in the 2 to 14 Kohm
range.
An AC signature (especially one that indicates the presence of a ringer T-R) is not
expected for a PBX termination.
Additional
Information
It is possible that the line records are wrong. You must determine whether or not
the line is a single party line (as you might expect with a possible ringer T-R). If the
records are wrong, take the appropriate action to correct them. If the records are
correct, handle the trouble based on the customer's report.
See Also
VER codes related to VER U3 (UNEXPECTED RINGER TERMINATION) are

listed below:
VER U1 UNEXPECTED THERMISTORS
UNIVERSAL PGS
VER U4: UNEXPECTED INWARD

SERVICE
Overview
LoopCare detects a ground start PBX DC signature with no line circuit and no way
to draw dial tone. It is possible that what LoopCare is accessed to is an inward
only trunk that cannot make outgoing calls.
Additional
Information
It is possible that the line records are wrong. You must determine whether or not
the records are wrong. If they are wrong, take the appropriate action to correct
them. If they are correct, handle the trouble based on the customer's trouble
report.
See Also
VER codes related to VER U4 (UNEXPECTED INWARD SERVICE) are listed

below:
VER U6 POSSIBLE RECORD ERROR
UNEXPECTED INTEGRATED/UNIVERSAL PGS
5-70
VER U5: UNEXPECTED CHANNEL

TEST RESULTS
Overview
The results of the DLC's self sanity check indicate that although the line records
show that the line is either a coin or multi-party line, the channel unit is only
capable of handling single-party service. This could mean a bad channel unit at
the DLC Central Office Terminal (COT) or Remote Terminal (RT), or the wrong
type of channel unit installed.
See Also
VER codes related to VER U5 (UNEXPECTED CHANNEL TEST RESULTS) are

listed below:
VER U3 POSSIBLE RECORD ERROR UNEXPECTED RINGER TERM
IDENTIFIED
VER U6 UNEXPECTED INTEGRATED/UNIVERSAL PGS
VER U6: UNEXPECTED

INTEGRATED PGS/UNEXPECTED
UNIVERSAL PGS
Overview
The results of an LoopCare test indicate a discrepancy in the Line Record

information and testing results, (i.e., LoopCare expects an Integrated PGS from
Line Record information, and testing indicates a Universal PGS). The opposite
scenario could also occur and cause VER_U6 to be returned.
The following is an example of the Line Record indicating a Universal PGS, but
line tests indicate an Integrated PGS.
Additional
Information
It is probable that the line records are wrong. If this is the case, take the
appropriate action to correct them. If the records are correct, then handle the
trouble based on the customer's report.
When the DLC Testing Feature (DLC testing independent of line records) is used,
you may notice a significant decrease in the number of VER codes U6 and 52
(INVALID PAIR GAIN C.O. SIGNATURE) being displayed because, with the
feature turned on, line records will be used less in testing.
See Also
VER codes related to VER U6 (UNEXPECTED INTEGRATED PGS) are listed

below:
VER U3 POSSIBLE RECORD ERROR UNEXPECTED INTEGRATED
PGS/ UNEXPECTED UNIVERSAL PGSUNEXPECTED RINGER TERM
IDENTIFIED
5-72

Overview
The system attempted to test a line with a VOIP or VOIPRING test request but
wasn't successful due to an internal error within the test system or test equipment.
This VER code indicates that the VoIP failure took place after DSL
synchronization and after the completion of required authentication and/or IP
address resolution. In addition to a summary message indicating the success of
the DSL synchronization, additional summary messages are displayed if PPP
authentication and/or DHCP address resolution were invoked as part of the VOIP
or VOIPRING request.
This error occurs if a call is already active on the line, VoIP parameters were not
configured correctly, or the analysis process is already in progress.
Example
VER V0: VOIP TEST FAILURE

DSL SYNC SUCCEEDED

Overview
The system attempted to place a VoIP call using a VOIP or VOIPRING test
request and the called party did not answer. This VER code indicates that the test
equipment, acting as a VoIP call origination point, was successfully able to
synchronize with the DSLAM and was configured as a VoIP client. In addition to a
summary message indicating the success of the DSL synchronization, additional
summary messages are displayed if PPP authentication and/or DHCP address
resolution were invoked as part of the PING request.
Example
VER VA: CALL NOT ANSWERED

DSL SYNC SUCCEEDED
5-74

Overview
The system attempted to register itself as a VoIP client as part of a VOIP or

VOIPRING test request. This VER code indicates that the registration failed
because the VoIP call server was busy. In addition to a summary message
indicating the success of the DSL synchronization, additional summary messages
are displayed if PPP authentication and/or DHCP address resolution were
invoked as part of the VOIP or VOIPRING request.
Example
VER VB: VOIP SERVER BUSY

DSL SYNC SUCCEEDED
VER VC:CALL FAILED

Overview
The system attempted to place a VoIP call as part of a VOIP or VOIPRING test
request and the call failed, most likely because of an unexpected, premature
termination of the call. This VER code indicates that the test equipment, acting as
a VoIP call origination point, synchronized with the DSLAM and was configured as
a VoIP client.
synchronization, additional summary messages are be displayed if PPP
authentication and/or DHCP address resolution was invoked as part of the VOIP
Example
VER VC: CALL FAILED

DSL SYNC SUCCEEDED
5-76
VER VP:DROP ACCESS TO CHANGE

TEST PORT
Overview
The tester submitted a VOIPRING test request following a VOIP request or DSL/
IP request (e.g. SYNC, PING) while holding access to the customer's port.
You must first drop access with an X request before running the test request.
Example
VER VP: DROP ACCESS TO CHANGE TEST PORT

DSL SYNC SUCCEEDED
VER VQ:VOICE QUALITY BELOW

THRESHOLD
Overview
The system successfully placed a VoIP call as part of a VOIP or VOIPRING test
request and one or more of the call quality measurements was below the
corresponding quality threshold. This VER code indicates that the test equipment,
acting as a VoIP call origination point, synchronized with the DSLAM and was
configured as a VoIP client.
synchronization, additional summary messages are displayed if PPP
The following supplemental messages may appear:
*EXCESSIVE BURST DETECTED

Excessive burst was detected on a VoIP connection.
*EXCESSIVE DELAY DETECTED

Excessive delay was detected on a VoIP connection.
The absence of these supplemental messages indicates a low quality alert. The
LoopCare Administrator can modify the thresholds for the excessive burst and
excessive delay alerts via OAM->FEATURES->VoIP->Quality Thresholds.
Example
VER VQ: VOICE QUALITY BELOW THRESHOLD

DSL SYNC SUCCEEDED
5-78

Overview
The system attempted to register itself as a VoIP client as part of a VOIP or

VOIPRING test request. This VER code indicates that the registration failed for
one or more reasons, such as:
The registration server was unreachable at the specified IP address.
The specified registration parameters were not accepted by the registration

server.

synchronization, additional summary messages are displayed if PPP
Example
VER VR: REGISTRATION FAILED

DSL SYNC SUCCEEDED
VER VT:TESTING ON DEDICATED

PORT / *DROP ACCESS FIRST
Overview
The user submitted a DSL/IP look-out test request (e.g. SYNCOUT, ATMLBOUT)
while holding access to a dedicated test port. With the line in this condition,
You must first drop ccess with an X request.
Example
VER VT: TESTING ON DEDICATED PORT

*DROP ACCESS FIRST
5-80
VER W1: WIDEBAND NOISE

PROBLEM
Overview
LoopCare performed the Wideband Noise and Bridge Tap tests as part of a FULL
or LOOP request and determined that the predicted data rate for the line was less
than the high data rate threshold for the associated DSL service type
(ADSL,G.SHDSL, etc.) The accompanying summary messages associated with
this VER Code vary depending upon the wideband analysis feature set(s) activated on the LoopCare server. Please see the Results User Guide for further
details.
Example

PREDICTED 24GA DATA RATE: 102 KBPS
NOISE-LOSS TOO HIGH FOR DSL ON 26GA
KOHMS
See Also
VOLTS
KOHMS VOLTS KOHMS RNGRS
3500
T-R
3500
T-R
Y T-R
3500
0 T-G
3500
0 T-G
2000
T-G
3500
0 R-G
3500
0 R-G
2000
R-G
System Administration Guide, Appendix A for information on configuring

wideband testing and analysis

Overview
The LoopCare performed load coil detection as part of a FULL or LOOP request
and detected a load coil on a loop with xDSL service. The LCOILX request can be
performed to determine the number and location of load coils.
NOTE:
Load coil detection for wideband FULL or LOOP test requests requires that
the -L option be set in the tserc module of the M2.gdf file.
5-82
VER W4: POTS Line Circuit Found On

ADSL Line
Overview
A CO line circuit that cannot be removed was found on the line. This line circuit
makes the results of all LoopCare tests invalid.
The line circuit may be removed by gaining and holding test access from test
facilities on the POTS switch or Digital Loop Carrier facility (if available). The line
circuit may also be manually removed by disconnecting it at the Main Distribution
Frame.
The line may also be successfully accessed and tested through the POTS CO
switch or Digital Carrier facility (if such facilities are available).
VER WC: XDSL LTE EQUIP

PROBLEM
Overview
from the DSLAM indicate that the XDSL port in the DSLAM (that is, the xTU-C)
assigned to the customer has a problem, VER WC is returned. If VER WC has
been returned after a FULLX request was made, it indicates that the system
verified that the loop between the customer premises and the DSLAM in the
Central Office was tested and found not to have any problems. Also, unless
If VER WC has been returned after a DSLDIG request was made, it indicates that
only the status of the DSLAM port and the Customer Premises Equipment was
tested. No test on the condition of the loop between them was made.
Example
5-84
VER WT: XDSL MODEM IN

TRANSITION PHASE
Overview
service parameters retrieved from the LTE indicate that the LTE port assigned to
the customer is in a transition phase either from being down to the steady-state
(normal) condition or from the steady-state to a being down, VER WT is returned.
Some possible causes for these transient conditions may be the presence of
impulse noise on the loop, the customer premises equipment being turned on or
off, etc. If this message is encountered, it is recommended that the test be re-run
after waiting a few minutes.
If VER WT has been returned after a FULLX request was made, it indicates that
If VER WT has been returned after a DSLDIG request was made, it indicates that
Additional
Information
VER_WT was added with the implementation of LoopCare G10I14.7, Digital

Summary Message.
VER WU: XDSL MODEM IN

UNKNOWN STATE
Overview
service parameters retrieved from the LTE indicate that the LTE port assigned to
the customer is in an unknown state, VER WU is returned. This is a highly
unlikely situation and may be transient. If this message is encountered, it is
recommended that the test be re-run after waiting a few minutes.
If VER WU has been returned after a FULLX request was made, it indicates that
If VER WU has been returned after a DSLDIG request was made, it indicates that
Additional
Information
VER_WU was added with the implementation of LoopCare G10I14.7, Digital

Summary Message.
5-86
VER WX: XDSL CARD IS NOT IN

SERVICE
Overview
service parameters retrieved from the LTE indicate that the card in the slot
provided for testing is not in service, VER WX is returned. It is possible that an
error was made when the slot or line number was entered on the LoopCare User
Interface. If so, check the slot number and test again. Alternatively, there may be
craft activity causing this situation and the card may have been removed.
If VER WX has been returned after a FULLX request was made, it indicates that
If VER WX has been returned after a DSLDIG request was made, it indicates that
Additional
Information
VER_WX was added with the implementation of LoopCare G10I14.7, Digital

Summary Message.

Overview
LoopCare could not test a line due to a system error. When you make a request,
LoopCare checks the Default Exchange Key table to see if the NPA-NNX maps to
an Exchange Key.
In this case, an override exchange key was entered on the test request but
LoopCare determined that the NPA-NNX was duplicated in the database, and the
Local Number Portability feature was not enabled. So, LoopCare returns VER X7.
Additional
Information
See Also
5-88
This VER code may reflect an error in the data base. Do not try to retest because
it will not work. If you know that the TN you are entering is valid, contact the
system administrator to check for a data base error. Verify that the LNP R1 feature
file has been installed. Refer to the LoopCare Installation Guide, Appendix F, LNP
Installation.
VER E7 TEST SYSTEM ERROR
VER XA: OVRD-EXK/NNX COMBO

NOT IN DATABASE
Overview
This message appears when the combination of override exchange key and NNX
of the telephone number you are planning to test is unknown to LoopCare. That is,
LoopCare does not know of any switch identified by that override exchange key
that also serves the NNX you entered.
Additional
Information
The override exchange key and NNX combination is used to gain test access from
the TV or STV mask under certain conditions -- typically when the NNX of the testline telephone number is split over two or more switches, or when the DEFEXK
table entry produces an EXK result that does not relate to the switch serving the
desired line, or when the line record itself does not exist or does not yet include an
EXK entry for the desired line. Check the records to determine which switch
serves the telephone number of the line you want to test.
VER XF: INVALID/INCOMPLETE

CIRCUIT INFO
Overview
5-90
This VER code is displayed on the TV mask or End User GUI screen, under a
number of circumstances.
The circuit data (shelf, slot, line) entered is either invalid or incomplete.
Invalid implies that either the shelf, slot or line entry is not within the
acceptable range for the Loop Terminating Equipment (LTE).
VER XF is also displayed when override entries for the EDAF feature are
invalid for that NXX/EXK.
VER XG:LDS NAME UNKNOWN TO

SDV-EM
Overview
The Local Digital Switch (LDS) Name of the switch host is invalid. The systems
may be out of sync and they do not recognize the same LSDids known to each
EM.
Restart the SDV Group to get the databases back in sync. This can be done using
the UIP System Administration menu Start option for the SDV Group. Contact the
system administrator.
Example
VER XG: LDS_NAME UNKNOWN TO SDV-EM INFORM MLT ADMINISTRATOR

The VER XG code also appears if the system detected a missing OE on line
records or invalid OE format on the TV mask.
VER XG: INVALID OR MISSING OE
Verify that the OE code on the service order or on similar company-supplied form.

Overview
LoopCare has received a line record error indicating an invalid Call Reference
Value (CRV) for the line under test.
Notify the LoopCare system administrator.
See Also
5-92
System Administration Guide, Appendix A for information on configuring

wideband testing and analysis
VER XI: INVALID TN

Overview
This message appears if you try to test a telephone number that is not one of the
following:
1.
A ten-digit TN
2.
A ten-digit TN plus an extra series field starting with either TER, XN, S,
OGO, or OD
3.
A special services TN served by a DLC such that you can do an SSA

request. The line record does not indicate that you can do an SSA request
on the line.
VER XN: REQUEST NOT ALLOWED

IN THIS MODE
Overview
This VER Code occurs when a request is made that is invalid for the current mode
of test access on the line.
" REQ NOT SUPPORTED BY CHIPSET"
Examples
Attempting to set up callback functions without getting the line in monitor

mode.
Attempting a request that is valid for TNs only by submitting a Circuit ID or

Circuit Information.
Attempting to run a test request through an RMU to EAIU-supported lines

when the request requires an initial FULL or LOOP request. In this event,
the following message accompanies the Ver XN message.
USE FULL OR LOOP TO GET MET ACCESS
5-94
VER XO: TESTABLE VIA STV

OPTION
Overview
This message will appear if you are on a TV mask, and the line record of the TN
you are trying to test shows that this is a Special Services TN on a DLC system
with special test equipment available in the CO. If you see this message, you
should use an STV mask and run an SSA request to access the line.

Overview
This VER code is displayed on the TV mask or End User GUI screen, under a
number of different circumstances.
following a BENCH or DISP request when one of the following conditions

has been detected:
The line is an ISDN line.
The Benchmark Database (BMDB) feature is not enabled.
following a BT or WNOISE request when one of the following conditions

has been detected:
Line record data (or override) does not provide wideband access
information.
The switch serving the loop is not a TelAccord/DAU 1000 (Type 34).
following a CO request when the line being tested has no associated TN or

T1/T2 override. The following summary messages are displayed.
INVALID TEST REQUEST
NOT POTS SERVICE
following a DSLDIG request when:

The DSLDIG feature is not enabled.
The DSLDIG request is invoked on an XDSL line where an invalid
DSLAM is used.
The following table lists the LTEs valid for xDSL services when the
DSLDIG request is invoked.
LTE
Supported DSL Service Types
AFC AccessMAX
ADSL
Alcatel LiteSpan
ADSL
Alcatel ASAM 7300
ADSL, G.Lite
Lucent Stinger
ADSL, G.Lite, SDSL, HDSL2,

G.SHDSL
The following summary messages are displayed:

THIS TYPE OF LTE IS NOT SUPPORTED
The DSLDIG request is invoked on the TV or TEST mask. The
following summary messages are displayed:
5-96

INVALID REQUEST: USER GUI REQUIRED FOR DISPLAY OF
DIGITAL SVC PARAMETERS
if line record data does not provide wideband access information, and/or
the switch serving the loop is not a TelAccord/DAU 1000. The following
summary message will be displayed along with the VER Code:
NO WIDEBAND ACCESS AVAILABLE.
if the testhead serving the loop is not wideband capable. The following
summary message will be displayed along with the VER Code:
NO WIDEBAND TEST EQUIP AVAILABLE.
if the wideband feature is turned off.
if the switch serving the loop is a TelAccord/DAU 1000 and the TL1TelAccord feature is not enabled. The following summary message will be
displayed along with the VER Code:
* FEATURE NOT ENABLED
If a test request other than FULLX, INFO, LOOPX, or METX is attempted

on a bPON-supported line.
if a test request is not supported by RMU testing of EAIU-supported lines.
following an OPEN request that uses circuit information. The OPEN

request is not valid for direct access architectures. The following message
is also displayed.
REQUEST NOT ALLOWED IN THIS MODE
The following message can also appear with this VER Code;
* CANNOT CHANGE TO ADSL2 SYMMETRIC
Additional
Information
Refer to the LoopCare Installation Guide or System Administration Guide for

procedures to install or activate the Benchmark Database feature.
VER XS: TESTABLE VIA THE STV

MASK ONLY
Overview
This message will appear if you try to test a line from any mask other than TV or
STV, and if the line record of the TN you are trying to test shows that this is a
Special Services TN on a DLC system with special test equipment available in the
CO. If you see this message, you should use an STV mask and run an SSA
request to access the line. There are two ways to bring up an STV mask:
1.
Clear the screen and enter: /FOR STV

or
2.
5-98
On the TV mask, enter 'STV' in the REQ field.
VER XT: TRAINING SCRIPT

UNAVAILABLE
Overview
This VER code appears only on the DISP, MSCR, or TE masks as a result of
LMOS running a test using a training TN number. When this VER code appears
either the ISDN training feature is turned off, or LMOS is sending a request which
contains an invalid TN or OE number.
Display Example
For a description of the DISP, MSCR, or TE masks refer to the following

documents:
Additional
Information
Introduction To The DISP Mask (disp.disp_mask)
Introduction To The MSCR Mask (mscr.mscr_mask)
The Trouble Entry Mask (txn.te)
VER_XT was added with the implementation of the LMOS/WM training scripts.
The summary message that appears for this VER code will is:
Refer to LoopCare Training Messages for a brief description of this Summary
Message.
VER XU: ONT TEST HEAD NOT

AVAILABLE
Overview
Special test equipment in the ONT(bPON) is necessary to test this line. Either
there is no such equipment available in this ONT, or the test equipment is not
functional. Check with the facilities manager to confirm the status.
Example
5-100
Contents
6-2

This chapter correlates the messages that the Repair Service Attendant (RSA)
sees at the bottom (line 24) of the terminal screen with the corresponding
LoopCare VER Codes. RSA Line 24 messages are less specific than VER Code
messages, so one RSA Line 24 message usually corresponds to more than one
VER Code.
Overview
RSA Line 24
VER CODE
TEST OK
VER 0: B TEST OK
CPE OR HIGH RESISTANCE

OPEN
VER 0C: CPE OR HIGH RESISTANCE OPEN
TEST OK MTU
VER 0M: TEST OK MTU
TEST OK (PARTIAL TEST DONE)
VER IP: TEST OK (PARTIAL TEST DONE)
TEST OK NOW
VER I0: TEST OK NOW
TEST OK CPE/MTU
VER MC: TEST OK CPE/MTU
TEST OK ADSL
VER 0A: TEST OK ADSL

6-2
RSA Line 24
FAULT
VER CODE
VER14: CROSS TO WORKING PAIR: MARGINAL
VER 22: SHORT FAULT
VER 26: MDF TEST RECOMMENDED LOW RESISTANCE
VER 28: SHORT or GROUND
VER 44: OPEN OUT 2 PARTY OR BRIDGE LIFTERS
VER 45: OPEN OUT NEAR DROP
VER 49: CHANNEL UNIT UNDER TEST
VER 57: BAD PAIR GAIN RT CHANNEL UNIT
VER 59: RT CU SUSPECT
VER LB: LOOP BAD
VER LS: LOOP SUSPECT ADD ANALYSIS
RSA Line 24
FAULT (contd)
VER CODE
VER 72: MDF TEST RECOMMENDEDPERMANENT SIGNAL
VER C6: INITIAL RATE OR FRAUD CONTACT
PROBLEMS
VER FP: OPERATION FAILED IN HDT
VER G0: VALID RINGER COUNT AND
CONFIGURATION
VER G1: INVALID RINGER CONFIGURATION
VER G2: INVALID 2 PARTY RINGER
CONFIGURATION
VER G3: RINGER COUNT DISAGREES WITH
RECORDS
6-4
RSA Line 24
FAULT (contd)
VER CODE
VER G7: INVALID RINGER COUNT AND
CONFIGURATION
VER IG: FULL TEST NEEDED
VER IH: OE MISMATCH
VER IS: FURTHER TEST REQUIRED
VER NE: CHAN UNIT NOT EQUIPPED
VER SX: PBX ROUTE ADVANCED OR INTERCEPT
VER U1: RECORD ERR-UNEXPECTED THERMISTORS
VER U2: RECORD ERR-UNEXPECTED PBX
SIGNATURE
VER U3: RECORD ERR-UNEXPECTED RINGER
TERMINATION
VER U4: RECORD ERR-UNEXPECTED INWARD
SERVICE
VER U5: RECORD ERR-UNEXPECTED PGS CHANGE
TYPE
VER U6: RECORD ERR-UNEXPECTED INTEGRATED
PGS
RSA Line 24
CO FAULT
VER CODE
VER 3: OPEN IN
VER 30: SWITCH COMMON EQUIPMENT BAD
VER 31: INVALID LINE CIRCUIT ARRANGEMENT
VER 32: CAN'T DRAW DIAL TONE
VER 33: CAN'T BREAK DIAL TONE
VER 36: LINE CIRCUIT AND DIAL TONE PROBLEMS
VER 38: POSSIBLE C.O. WIRING ERROR
VER 39: SWITCH EQUIPMENT BAD
VER 40: SWITCH EQUIPMENT SUSPECT
VER 50: COT CU SUSPECT
VER 52: INVALID PAIR GAIN C.O. SIGNATURE
CA FAULT
BUSY EQUIPMENT
VER 53: PAIR GAIN TEST ACCESS FAILURE POSSIBLE BUSY CONDITION
CANNOT SEND TO APPLICATION

PROCESS
VER NM: CANNOT SEND TO APPLICATION PROCESS
LINE IN USE
VER 6: BUSY- SPEECH

VER 61: LINE IN USE
VER 71: ROH
VER LU: LINE IN USE
LINE IN SERVICE - ADD

ANALYSIS
VER S0: LINE IN SERVICE - RUN FULL TEST
LINE UNDER TEST
VER 63: CRAFT ACTION - LINE UNDER TEST
POSSIBLE ROH
VER 75: SHORT - POSSIBLE ROH
CPE (NT1) BAD
VER P4: CPE (NT1) BAD
CPE (NT1) SUSPECT
VER P5: CPE/NT1 OR BRITE CU PROBLEM
CPE (NT1) IN TEST MODE
VER P6: CPE (NT1) IN TEST MODE

6-6
RSA Line 24
VER CODE
CPE (STATION SET) BAD OR

INVALID
VER P7: STATION SET BAD OR INVALID
CPE (T-INTERFACE) BAD
CPE (NT1) POWER SUSPECTED
VER IN: NT1 POWER SUSPECTED - RUN FULL TEST
CPE (NT1) ON SECONDARY

POWER
VER IR: NT1 ON SECONDARY POWER - RUN FULL

TEST
DIAL OK
VER 80: DIAL OK
DIAL NOT OK
VER 81: DIAL NOT OK
INVALID OR MISSING SPLITTER

OR CUT THROUGH CARD
VER E0 TEST SYSTEM ERROR
TEST NOT MADE
VER 97: DERIVED PR NOT TESTED-PHYSICAL PR

NOT SERVED
VER ND: TN FROM FE ON DIFFERENT DCN
TEST EQUIP BUSY
VER B0: TEST EQUIPMENT BUSY TIME OUT IN

ACCESS)
VER B2: TEST EQUIPMENT BUSY (SANITY OR DIAG IN
PROGRESS)
VER B3: TEST EQUIPMENT BUSY (SIMULTANEOUS
TEST REQUEST MADE)
VER B5: TEST EQUIPMENT BUSY PAIR GAIN ACCESS
EQUIPMENT BUSY)
VER BX: TEST EQUIPMENT BUSY
VER BY: NO HDT OR ONU EQUIP AVAIL
VER BZ: HDT INITIALIZING
VER TB: TEST EQUIPMENT BUSY
RSA Line 24
TEST SYSTEM ERROR
VER CODE
VER E1: TEST SYSTEM ERROR (LTF Power Clear)
(No System Calibration for LTF)
VER E1: TEST SYSTEM ERROR (LTF Power Clear)
VER E5: TEST SYSTEM ERROR (Invalid NPANNX)
VER E6: TEST SYSTEM ERROR (Invalid Physical Pair
TN or Invalid MDF Dedicated Number)
VER E7: TEST SYSTEM ERROR (NPANNX Not in
Database)
VER EX: TEST SYSTEM ERROR
VER NM: CANNOT SEND TO APPLICATION PROCESS
TEST EQUIP FAIL

VER F1: TEST EQUIPMENT FAILURE (Pair Gain
Equipment Failure)
VER F2: TEST EQUIPMENT FAILURE (Diagnostics
Running)
VER FP: OPERATION FAILED IN HDT
NO TESTING AVAILABLE
VER NS: NNX NOT SERVED BY TEST SYSTEM

TEST NOT MADE - PROTECTED

SERVICE
TEST NOT MADE - SWITCH

ERROR
VER B7: NO TEST - SWITCH EQUIP UNAVAILABLE

VER E3: NO TEST - SWITCH INTERNAL ERROR
VER F3: NO TEST - SWITCH INTERNAL ERROR
VER F4: NO TEST - SWITCH EQUIP UNAVAILABLE
NOT TESTABLE
VER IC: AMI PR GAIN SYSTEM - NOT TESTABLE
NOT AN ISDN LINE

NOT PRIMARY TN
6-8
VER NP: NOT PRIMARY TELEPONE NUMBER
RSA Line 24
VER CODE
INTERCEPT
VER SU: INTERCEPT
INVALID REQUEST FOR T-DSL
VER NG: INVALID REQUEST FOR T-DSL
ISDN TEST-EXPECT DELAYED

RESULTS
VER LT: ISDN TEST - EXPECT DELAYED RESULTS
SYSTEM TIMEOUT

VER TX: SYSTEM TIMEOUT
SYSTEM FAIL
VER DL: FE-LTS OR CTLR-LTF DATA LINK FAIL

VER PF: LTF POWER FAILURE
NETWORK FAULT
(No applicable VER Codes.)
PREMISES FAULT

VER P3: POSSIBLE FAULTY TELEPHONE SET
PREMISES WIRING ERROR ON

ISDN LINE
VER IA: ISDN - NT1 TERM REVERSED
INVALID TN
VER XI: INVALID TN
INVALID TERMINATION FOR ISDN
VER IF: INVALID TERMINATION FOR ISDN
DENIED SERVICE

DENIED SERVICE - ADD

ANALYSIS
VER IJ: DENIED SERVICE - RUN FULL TEST
DENIED/RESTRICTED SVC MIXED
VER D5: DENIED/RESTRICTED SVC - MIXED
DENIED/INTERCEPT - MIXED
DIGITAL TEST MARGINAL
PROTOCOL PROBLEM
VER PA: LAYER 2 PROTOCOL PROBLEM

VER PC: LAYER 3 PROTOCOL PROBLEM
PROTOCOL PROBLEM
SUSPECTED
VER PB: PROTOCOL PROBLEM SUSPECTED

REMOTE TEST-EXPECT
DELAYED RESULTS
RSA Line 24
VER CODE
SIMULATOR FAILURE
VER ZX: SIMULATOR FAILURE
LINE REC SHOWS TERM

MISMATCH
VER IU: LINE RECORD SHOWS TERMINATION

MISMATCH
TERMINATION MISMATCH
TERMINATION MISMATCH
SUSPECTED
VER IL: TERM MISMATCH SUSPECTED
TRAINING SCRIPT UNAVAILABLE
UNEXPECTED ISDN
TERMINATION
VER IB: UNEXPECTED ISDN LINE (NON-ISDN LR)
NOT EQUIPPED
VER NE: CHAN UNIT NOT EQUIPPED
LINE RECORD ERROR
INVALID ID
VER XF: HDT DID NOT RECOGNIZE CKT ID
INVALID DATA
VER XG: MLT: INVALID DATA
INVALID DATA
VER XH: MLT: INVALID DATA
INVALID EQUIP
VER XP: INVALID CJAN UNIT TYPE
TOK-BMDB LIMIT EXCEEDED
VER OT: OUT OF TOLERANCE CONDITION
INVALID TEST REQUEST
REQUEST NOT SUPPORTED

FOR THIS DSL SERVICE TYPE
WIDEBAND NOISE PROBLEM
VER W1: NOISE LIMITS 26 GA RATE TO ****KB/S
VER ID: TERM MISMATCH - NON-ISDN CO EQ
VER W1: DATA RATE MEDIUM = XXXX KBPS

VER W1: DATA RATE LOW = XXXX KBPS
VER W1: PREDICTED DR=XXXX KBPS<SUBSCRIBED
VER W2: POOR 26 GA NOISE MARGIN > **** KHZ
LOAD COIL DETECTED
6-10
Summary Messages
Contents
Overview
7-4
Testing Non-Locally Switched Services on DLCS
7-5
7-8
7-10
7-15
ADSL Splitter Signature Summary Messages
7-16
7-17
7-18
7-19
Benchmark Database (BMDB) Summary Messages
7-20
7-24
7-27
7-32
Summary Messages
7-2
7-33
7-38
7-39
7-42
7-44
7-45
7-46
7-52
7-53
7-54
7-66
7-72
7-102
Local Number Portability (LNP) Summary Messages
7-105
7-107
7-108
7-111
7-114
7-115
7-116
7-118
Permanent Signal Release Summary Messages
7-123
7-124
Remote Measurement Unit (RMU) Summary Messages
7-125
7-126
7-130
Rotary Dial & Touch-Tone Summary Messages
7-133
Special & Protected Service Summary Messages
7-135
7-136
7-147
7-160
Summary Messages
Training Messages
7-161
Unexpected Signature Summary Messages
7-162
7-164
7-172
Summary Messages
Overview
Summary Messages
Overview
7-4
The following pages contain all Summary Messages. These messages are used
in conjunction with the VER Codes that are returned when LoopCare has
completed a test transaction on a line. These messages may or may not be used
in your environment depending on the version of LoopCare that has been
purchased. Some of these messages may or may not be displayed on the GUI.
Summary Messages
Testing Non-Locally Switched Services on

DLCS
Overview
Testing non-locally switched services on Digital Loop Carrier Systems (DLCSs)

requires the interaction of LoopCare with special equipment in the central office
(CO). This equipment has enhanced features for testing lines served by SLC
Series 5. On SLC Series 5, a No-test trunk (NTT) can be connected to a nonlocally switched line, such as a private line or a foreign exchange. This is a special
case of a No-test trunk access, called a No-test trunk Special Services access.
This special access can only be done from a Special Services Trouble Verification
(STV) mask.
Upon access to most types of SLC Series 5 lines, LoopCare can get a separate
pass/fail test report for the Central Office Terminal (COT) and Remote Terminal
(RT) channel units. So, in addition to accessing non-locally switched lines for
testing, LoopCare can get enhanced channel unit testing for both POTS and
Special Services circuits. This is done automatically on locally switched lines as
part of the FULL or LOOP requests, or explicitly on either locally or non-locally
switched lines via the CHANNEL request.
LoopCare can access SLC Series 5 lines at three different access points:
1.
Access to the customer loop (access to both loops for 4-wire circuits)
beyond the RT
2.
Access to the network, or to the customer loops at the COT for non-locally
switched 2- and 4-wire circuits.
3.
Access into the channel, or Line Terminal (LT) at the COT for 2-wire nonlocally switched circuits.
Once access has been established, regular test requests (e.g., FULL, LOOP,
DTOUT, etc.) can be run. In most cases, it will be appropriate to interpret the test
results by referring to the Special Services Testing Guide.
LoopCare Access
Sequence
Because of the special features of special services circuits on DLCS, LoopCare

must use special procedures to access the lines. LoopCare knows a line is a
special services circuit on a DLCS from the line record information. It also knows
whether the special equipment in the CO needed to test these lines is available
from a table in the LoopCare Front End (FE). The line record information and the
table in the FE must correctly indicate that there is a DLCS on the line, and that it
is testable, or LoopCare will never know. Without knowing this information,
LoopCare will not allow you to run the Special Services access (SSA) request,
and therefore you won't be able to test these circuits. The access sequence is as
follows:
Summary Messages
1.
First, LoopCare checks for a valid access telephone number signature. If a

valid signature is not found, testing stops; otherwise, testing continues.
2.
The No-test trunk is connected to the desired circuit by commands sent

over the NTT by LoopCare.
3.
LoopCare then monitors the circuit for hazardous or busy conditions to

determine if testing can be done.
If conditions are okay, LoopCare prints:

SPECIAL SERVICES ACCESS UP
If conditions are not okay, error messages or status summaries are returned. If a
busy condition is found, testing can continue, but any calls in progress will be
dropped.
STV Mask Entries
The STV mask was developed for testing non-locally switched circuits on DLCSs.
To test one of these circuits, enter 'STV' in the request (REQ) field of the TV mask,
or bring up STV initially by typing /FOR STV on a blank screen. You will then need
to get Special Services access with the SSA request.
In the STV mask, Special Services accesses require certain entries in addition to
the regular TV/STV mask entries. These entries are: ID, LT, APT, and XMT.
1.
ID - DLC system identifier
2.
LT - DLC Line Terminal (LT) - This describes which channel unit on a DLC
system the line is connected to.
3.
APT - Access point. The following diagram shows a 2-wire private line, and
what the different access points on the circuit are.
The entries are:
7-6
R - Remote Terminal (RT) access via the metallic bypass pair. This
is used to test Loop B.
Summary Messages
4.
C - Central Office Terminal (COT) access. This is used to test Loop

A.
L - Line Terminal (LT) access. This is used only if you want to run
tests through the DLC (no metallic access). An example of the use
of this access point would be to run a rotary dial analysis (RDA) on a
telephone at the end of Loop B.
XMT - Transmit or receive pair for 4-wire circuits. The entries are 'Y for the
transmit pair, and 'N' for the receive pair. The following diagram shows an
example of a 4-wire circuit, and a PBX tie trunk.
NOTE:
The odd numbered LT is, by convention, assumed to be the transmit pair.
Additional
Information
For more information about DLCS testing, see the Test Requests User Guide for
information on STV Entries. Also, see the DLCS summary messages and the
following VER codes:
CONDITION
VER 58 BAD COT/RT CHANNEL UNIT
Summary Messages

Overview
Digital Loop Carrier Systems (DLCS) are subscriber loop carrier systems capable
of carrying multiple speech channels over several digital pairs. Such a system is
also called a pair gain system because it allows you to gain many speech
channels (the equivalent of a pair) over a small number of digital pairs. An
example of a DLCS is SLC-96, which is a DLCS that carries 96 separate speech
channels over four digital pairs.
A DLCS consists of the following parts:
1.
Central Office Terminal (COT)
2.
Several digital pairs connecting the COT with the Remote Terminal
3.
Remote Terminal (RT)
From the central office (CO) the customer equipment comes into the DLCS COT.
Many customers can come into the COT. The connection between the COT and
the RT is made through the digital pairs. All conversation is carried over these
pairs for the DLCS customers. The digital pairs terminate at the RT. The
connections to the various DLCS customers come out of the RT.
Different conversations are carried over the digital pairs. Each conversation is put
on a separate speech channel on the digital pair. This is similar to the way that
different programs can come over different channels on your television.
A special case of Digital Loop Carrier Systems is an Integrated DLCS, or
Integrated Pair Gain System. This case only occurs if the customer is served by a
digital switch, like a 5ESS or a DMS-100. In this case there is no COT; the digital
pairs go directly from the switch to the RT.
LoopCare Testing
Sequence
Because of the special features of DLCS, LoopCare must use special procedures
to test it.
LoopCare knows a line is served by DLCS from the line record information. The
line record information must correctly indicate that there is a DLCS on the line or
else LoopCare will never know. Without knowing that there is a DLCS on the line,
LoopCare will never run the special DLCS tests.
1.
7-8
The first thing that LoopCare does when it tests a DLCS line is test the CO
line circuit and dial tone. Basically, this is the same CO test done on regular
lines, however, it is usually performed last instead of first.
Summary Messages

LoopCare looks for the proper arrangement of battery and ground in the
CO line circuit. It also attempts to draw and break dial tone. If the line
records say that the DLCS is an integrated pair gain system, then the CO
test is not done at all, because the customer doesn't have a regular line
circuit.
2.
After the central office test, LoopCare checks for a valid COT signature.
There are five valid COT signatures.
If a valid COT signature is not found, testing stops. Otherwise, testing continues.
Additional
Information
1.
If a valid COT is found, the next thing LoopCare attempts is to get metallic
access to a special pair of wires connecting the COT with the RT. If metallic
access fails, LoopCare testing stops. If metallic access succeeds, testing
continues.
2.
If metallic access succeeds then a test of the channels of the digital pairs is
made by the DLCS itself. This self check is not part of LoopCare, but is
initiated by a successful LoopCare metallic access.
3.
The self check determines the status of the channels that carry the
conversation, and this status is relayed to LoopCare and displayed to the
user.
4.
If metallic access succeeds, LoopCare runs its standard series of tests on

the customer's line. Any problems on the loop will be detected by these
tests.
For more information about DLCS tests from LoopCare see the following:
DLCS Summary Messages:
CO BATTERY ON PAIR GAIN SYSTEM (VER 51)
INVALID PAIR GAIN CO SIGNATURE (VER 52) PAIR GAIN TEST
ACCESS FAILURE - POSSIBLE BUSY CONDITION (VER 53)
PAIR GAIN SYSTEM FAILURE (VER 54) PAIR GAIN CHANNEL FAILURE
(VER 55) BAD COT CHANNEL UNIT (VER 56) BAD RT CHANNEL UNIT
(VER 57)
BAD COT/RT CHANNEL UNIT (VER 58)
For information about testing special services lines on DLCS, see usr.dlcmod,
Non-locally Switched Services on DLCS from LoopCare."
Summary Messages

Summary Messages
1.
Msg: AC FEMF FAULGCAN'T MEASURE VOLT

AC foreign voltage greater than the fault value (locally determined) was
detected on the line. The test was terminated, however, because of the
excessive voltage. No values are available.
Such a condition could be caused by a cross to a power line or by AC
induction due to telephone wires being very close to AC power lines.
2.
Msg: AC FEMF FAULT T-G ***** V

AC foreign voltage greater than the locally determined fault value was
detected on the tip side of the line. Testing, however, was not terminated.
The voltage value associated with the problem will be displayed in the body
of the message.
This condition could be caused by a cross with a power line or AC induction
due to telephone lines being close to power lines.
3.
Msg: HAZARDOUS POTENTIAL

The preliminary tests on the line indicate that there is a dangerous amount
of voltage (greater than about 150 volts DC or 53 volts rms AC) on the loop.
Such a condition could be caused by a cross with a power line or by some
temporary condition such as lightning. This message will always be
followed by messages 4 and 11, respectively.
4.
Msg: HAZARDOUS POTENTIAL

The preliminary tests on the line indicate that there is a dangerous amount
of voltage (greater than about 150 volts DC or 53 volts rms AC) on the loop.
Such a condition could be caused by a cross with a power line or by some
temporary condition such as lightning. This message will always be
followed by messages 4 and 11, respectively.
5.
"HAZARDOUS POTENTIAL = *** Vexed Y-Z" "

where sax = "peak-peak", "dc" or "rms"
7-10
Summary Messages

where Y-Z = "T-R", "T-G" or "R-G"
This message returns the actual value of the dangerous amount of voltage.
If the HAZ_POT_STAT returns as OVERRANGE, then the message is:
"HAZARDOUS POTENTIAL = OVERRANGE
6.
Msg: DANGER- ADVISE SUPERVISOR

If hazardous potential is detected, it may be appropriate, because of the
danger on the loop, to advise both your supervisor and the supervisor of
the repair craft. Of course, you should follow local procedures in these
situations.
7.
Msg: TEST STOPPED-EXCESS AC CURRENT

Testing was terminated because of an excess amount of AC current
present on the loop (>12.5 ma).
8.
Msg: TEST STOPPED-EXCESS AC VOLTAGE

Testing was terminated because of an excess amount of AC FEMF
voltage. LoopCare defines an excess amount of voltage as a peak
combination of both AC and DC voltage so that the voltage is greater than
100 volts but less than 150 volts. Voltage above 150 volts is considered
hazardous potential.
NOTE:
Message 6 also is used in conjunction with messages 13 through 17. See
the explanations of those messages for details.
9.
Msg: AC FEMF MARGINALT-G ***** V

AC foreign voltage less than the locally established fault value but greater
than 15 volts was detected on the tip side of the line. Testing, however, was
not terminated. The voltage value associated with the problem will be
displayed in the body of the message.
A cross with a power line or AC induction with a power line could cause this
condition.
Summary Messages
10.
Msg: AC FEMF FAULT R-G ***** V

AC foreign voltage greater than the locally determined fault value was
detected on the ring side of the line. Testing, however, was not terminated.
The voltage value associated with the problem will be displayed in the body
of the message.
This condition could be caused by a cross with a power line or AC induction
due to telephone lines being close to power lines.
11.
Msg: AC FEMF MARGINAL R-G ***** V

AC foreign voltage less than the locally established fault value but greater
than 15 volts was detected on the ring side of the line. Testing, however,
was not terminated. The voltage value associated with the problem will be
A cross with a power line or AC induction with a power line could cause this
condition.
12.
Msg: CAN'T DO HAZARDOUS POTENTIAL CHECK

When access is established on a line where hazardous potential was
detected each request made on that line will cause the hazardous potential
check to be run. If for some reason the hazardous potential check can't be
made at this time, this message will be displayed.
13.
Msg: USE EXTREME CAUTION

If hazardous potential or AC FEMF above the fault level is detected, it is
advisable to tell the repair person working on the line to use extreme
caution.
14.
Msg: AC FEMF CURRENT

AC short-circuit current above 3 ma has been detected on the line.
15.
7-12
Msg: EXCESS AC FEMF T-G ***** V
Summary Messages

This message will appear with message 6 if the AC foreign voltage tip to
ground exceeds 70.71 volts.
NOTE:
Messages 6, 13, and 15 will appear together if both the AC and DC foreign
voltages T-G exceed the stated limits.
16.
Msg: EXCESS AC FEMF R-G ***** V

This message will appear with message 6 if the AC foreign voltage ring to
ground exceeds 70.71 volts.
NOTE: Messages 6, 14, and 16 will appear together if both the AC and DC
foreign voltages R-G exceed the stated limits.
17.
Msg: EXCESS DC FEMF T-G ***** V

This message will appear with message 6 if the DC foreign voltage tip to
ground exceeds 100 volts.
NOTE:
voltages T-G exceed the stated limits.
18.
Msg: EXCESS DC FEMF R-G ***** V

This message will appear with message 6 if the DC foreign voltage ring to
ground exceeds 100 volts.
NOTE:
voltages R-G exceed the stated limits.
19.
Msg: EXCESS FOREIGN VOLTAGE

This message will appear with message 6 if the total foreign voltage
exceeds 100 volts but the AC foreign voltage is less than 70.71 volts.
7-14
Summary Messages
Summary Messages

Summary Messages
1.
Msg: AC SIGNATURE NOT DEFINED

The AC signature tests were made, but LoopCare does not have any
information on whether or not the termination should have an AC signature.
In addition, the AC signature does not match the standard single party AC
signature. known to LoopCare. Therefore, LoopCare cannot determine
whether or not the AC signature is valid.
Check the AC resistances which will be displayed in the AC SIGNATURE
category of the test results. Perhaps, with experience, you will be able to
recognize a valid AC signature for the specific equipment being tested.
This message can be displayed in the following cases:
2.
1.
A line with uncataloged termination.
2.
A PBX with no known AC or DC signature.
3.
A line with unusual loop equipment, (in this case the next message
listed will appear).
Msg: * DUE TO LOOP ELECTRONICS

The AC signature tests were made but because there was unusual loop
equipment on the line, the AC signature was undefined. Some of the
equipment that could cause this condition include ringer isolators or DLLs
in the field.
3.
Msg: INVALID AC SIGNATURE

The AC signature tests were made and the results indicate an invalid
termination. That is, the LoopCare AC resistances were not what were
expected for the type of equipment and services indicated. For example, if
the line records indicate a KEY SYSTEM the following AC signature would
be invalid because the T-R resistance was below the 2 K to 18 K T-R range
for Key systems.
1K
T-R
44 K
T-G
46 K
R-G
Summary Messages
ADSL Splitter Signature Summary

Messages
Summary Messages
1.
Msg:ADSL C.O. SPLITTER SIGNATURE FOUND

The test system has detected a signatured ADSL splitter.
1.
Msg:NON SIGNATURED SPLITTER DETECTED

The test system has detected a non-signatured ADSL splitter.
7-16
Summary Messages

Summary Messages
1.
Msg: TA 3050 SHELF OR MTC NOT PRESENT

A message sent to an ADTRAN 3000 that requires a TA 3050 splitter
detected the absence of the TA 3050 splitter or the Metallic Test Controller
(MTC) card, that controls access to the TA3050.
Summary Messages

Summary Messages
1.
Msg:DEFAULT BSU PROFILE USED

The default BSU profile was used for the test request for one of the
following reasons:
2.
A DSL/IP test request was made via the Test Requester API without
a service class parameter value and LoopCare did not query
APMAC for a line record.
The service class parameter value returned from APMAC for the
specified TN did not match any values configured on LoopCare.
Msg:LINE RECORD DATA NOT AVAILABLE

Both the APMAC query and the cache query for a line record failed.
3.
Msg:LINE RECORD RETRIEVED FROM CACHE DB

The system used a line record cached in LoopCare instead of one retrieved
from APMAC.
4.
Msg:SERVICE CLASS MISMATCH

The service class parameter value returned from APMAC for the specified
TN did not match any values configured on LoopCare.
7-18
Summary Messages

Summary Messages
1.
Msg: LONGITUDINAL BAL MARGINAL ** DB

The longitudinal balance test was made and the balance was above the
locally determined fault value (default 40 DB), but was below 60 DB. The
DB value will be displayed in the body of the message.
2.
Msg: LONGITUDINAL BAL POOR
** DB
The longitudinal balance test was made and the balance was below the
locally determined fault value (default 40 DB). The DB value will be
3.
Msg: CAPACITIVE BALANCE POOR *** %

The capacitive balance test was made and the balance was less than 95
percent. The capacitive balance value will be displayed in the body of the
message.
4.
Msg: CAPACITIVE BALANCE
*** %
The capacitive balance test was made and the percent balance is greater
than 95 percent. The capacitive balance value will be displayed in the body
of the message.
5.
Msg: LONG BAL TEST NOT DONE

A longitudinal balance test was not run. Either the DC fault was found to be
less than 65 K ohms, or the line had too much noise on it. This message
will appear as part of other messages.
Summary Messages
Benchmark Database (BMDB) Summary

Messages
Summary Messages
1.
Msg: INVALID TEST REQUEST

This message appears when the user attempts to run the BENCH or DISP
test request on an ISDN line or when the Benchmark Database feature is
disabled.
2.
Msg: NO BENCHMARK DATA AVAILABLE

This message appears as the last summary message when all of the
following conditions occur:
a FULL/LOOP test has been run and the test result is a VER 0 or
VER 0C
in OA&M, the Comparison feature in On
no Bench result exists for the TN.
3.
Msg: NO VALID BENCHMARK DATA AVAILABLE

This message appears when the comparison feature in On and the current
test result is VER 0/0C, but the bench test result is non-VER 0/0C.
4.
Msg: LOOP LENGTH IS OUT OF TOLERANCE

This message appears when the measured Loop Length for the TN differs
from the benchmark by a user-configured pre-set threshold.
5.
Msg: AC IMPEDANCE IS OUT OF TOLERANCE

This message appears when one or more of the measured AC
Impedances for the TN differs from the benchmark by a user-configured
pre-set threshold.
6.
7-20
Msg: CAPACITIVE BALANCE IS OUT OF TOLERANCE
Summary Messages

This message appears when the measured Capacitive Balance for the TN
differs from the benchmark by a user-configured pre-set threshold.
7.
Msg: BMDB DATABASE NOT AVAIL. - NOTIFY ADMIN.

This message appears when the Benchmark Database is down due to
maintenance or malfunction. Benchmark data will not be stored during the
period when the BMDB is unavailable.
8.
Msg: TN NOT IN BENCHMARK DATABASE

This message appears when the telephone number used to run the DISP
request does not exist in the database.
9.
Msg: CKTID NOT IN BENCHMARK DATABASE

This message appears when the circuit id used to run the DISP request
does not exist in the database.
10.
Msg: CKT INFO NOT in BENCHMARK DATABASE

This message appears when additional circuit information used to run the
DISP request does not exist in the database.
11.
Msg: CONFLICTING CIRCUIT INFO ENTERED

Information to run the DISP request was entered in TN/Circuit ID and the
additional circuit information fields. (These two entries do not represent the
same circuit in the Benchmark database.)
12.
Msg: NO FAULTS to BENCHMARKED LENGTH

When the following conditions are met, this message appears and the VER
code is changed to 0L:
1.
A LOOP/FULL test has returned a VER41.
2.
The test was run on a narrowband circuit.
Summary Messages
13.
3.
A test OK result for this circuits stored as the Benchmark.
4.
The loop length is within the tolerances set forth in the OAM/
FEATURES/BMDB/OPTIONS screen.
Msg: INFO MISMATCH - RESULTS NOT STORED

This message appears when all of the following conditions are met:
14.
1.
The request originated from an interface other than an Application

Programmers Interface (API).
2.
The request provided both TN/Circuit ID and additional circuit

information.
3.
Data already exists for this circuit that differs from this information.
Msg: BENCHMARK DATA STORED

The test results have been stored in the BMDB database for later
comparison with other test results.
This message also is displayed for the BENCH(X), DCOILX, FULL(X),
LCOILX, LOOP(X), and QUALX test requests when a re-bench occurs.
15.
Msg: BENCHMARK DATA NOT STORED

The test results have not been stored in the BMDB database. This is
determined by the inclusion of the VER Code in the list of VER codes for
which test results are not stored. Refer to Chapter 9 of the ADEF Guide.
16.
Msg: TEST RESULTS RE-BENCHED

*SWITCH ID DIFFERENT
*OE DIFFERENT
*CABLE/PAIR DIFFERENT
*DLC INDICATOR DIFFERENT
*LENGTH REFERENCE DIFFERENT
*LOAD COILS DIFFERENT
These messages are displayed when a BENCH(X), DCOILX, FULL(X),
LCOILX, LOOP(X), or QUALX test request returns results that meet the
criteria for re-benching. The previous BMDB record for the TN or Circuit ID
7-22
Summary Messages

is deleted, and new circuit information and the current test results are
stored in the BMDB. Only one of the secondary messages is displayed,
explaining the first criteria detected for the re-bench:
For more information about the re-bench feature, see the System
Description.
17.
Msg: PROBABLY TEST OK

Using configured rules and benchmarked data, LoopCare has analyzed a
marginal DC fault on the line under test and determined that there is a high
probability that it does not affect service.
18.
Msg:VER CODE MAPPED FROM VER xx

The VER code in the current test results was converted from another VER
code, represented by xx. The displayed VER code more accurately reflects
the condition of the circuit.
Summary Messages

Summary Messages
1.
Msg: ATM LOOPBACK:VG-ONT:ABORTED.

An ATM loopback on a bPON line from the G6 to ONT has been aborted.
2.
Msg: ATM LOOPBACK:VG-ONT:FAILED.

An ATM loopback on a bPON line from the G6 to ONT has failed.
3.
Msg: ATM LOOPBACK:VG-ONT:PASSED.

An ATM loopback on a bPON line was performed successfully from the G6
to ONT.
4.
Msg: ATM LOOPBACK:VG-ONT:UNABLE TO RUN.

An ATM loopback on a bPON line from the G6 to ONT could not be run.
5.
Msg: bPON Line

The subscriber line on which the test request was performed is a bPON
line.
6.
Msg: Drop Test OK

The test from the main trunk to the Customer Premises showed no defects.
7.
Msg: ONT Self Test Failed

The ONT self test failed.
8.
7-24
Msg: ONT Self Test in Progress
Summary Messages

The ONT self test is in progress.
9.
Msg: ONT Self Test - No test results available

No test results were retrieved for the ONT self test.
10.
Msg: ONT Self Test Passed

The ONT self test showed no defects.
11.
Msg: OPEN - NO RINGER SEEN

This message is displayed when a VER Code 45 is returned.
12.
Msg: SHORT OR GROUND

This message is displayed when a VER Code 28 is returned.
13.
Msg: VOICE GATEWAY TO ONT CONN DOWN

The connection between the Voice Gateway and the ONT is down.
14.
Msg: VOICE GATEWAY TO ONT CONN UNKNOWN

No information has been returned about the status of the connection
between the Voice Gateway and the ONT.
15.
Msg: VOICE GATEWAY TO ONT CONN UP

The connection between the Voice Gateway and the ONT is up.
16.
Msg: VOICE GATEWAY TO SWITCH CONN DOWN
Summary Messages
The connection between the Voice Gateway and the switch is down.
17.
Msg: VOICE GATEWAY TO SWITCH CONN FAILURE

The connection between the Voice Gateway and the switch is down.
18.
Msg: VOICE GATEWAY TO SWITCH CONN UNKNOWN

No information has been returned about the status of the connection
between the Voice Gateway and the switch.
19.
Msg: VOICE GATEWAY TO SWITCH CONN UP

The connection between the Voice Gateway and the switch is up.
7-26
Summary Messages

Summary Messages
1.
Msg:ATM LOOPBACK FAILURE

The number of successful F5 OAM loopbacks is less than or equal to the
ATM loopback command failure threshold.
2.
Msg:ATM LOOPBACK SUCCEEDED

The number of successful F5 OAM loopbacks is greater than or equal to
the ATM loopback command success threshold.
3.
Msg:ATM PVC TRAFFIC PRESENT ON LINE

The number of ATM PVC packets in each direction is greater than zero.
This condition indicates that there is traffic at the ATM level and there is an
ATM PVC associated with the VPI and VCI parameters specified in the test
request. This message typically indicates that authentication was
attempted after DSL sync was established.
4.
Msg:*ATTEMPTING TO SYNC
The BSU, acting as an ATU-C, is attempting to establish synchronization
with the customers modem.
5.
Msg:CALL ANALYSIS IN PROGRESS

The VoIP call analysis process is in progress.
6.
Msg:CALL IN PROGRESS
A VoIP call is in progress.
7.
Msg:CALL TERMINATED PREMATURELY

There was a hangup during a VoIP test.
8.
Msg:CALL TIMED OUT

The VoIP call timed out.
9.
Msg:CALLED PARTY DISCONNECTED

The VoIP called party was disconnected.
10.
Msg:CLIENT SIDE ERROR

The HTTP error code listed in the HTTP THROUGHPUT STATISTICS
indicates an error on the client side.
11.
Msg:CONFIGURATION SUCCEEDED
The configuration process in VoIP call setup succeeded.
12.
Msg:CONNECTION ESTABLISHED
The connection was established in VoIP call setup.
Summary Messages
13.
Msg:DHCP ADDRESS RESOLUTION FAILURE

An attempt to resolve a dynamic IP address via DHCP failed.
14.
Msg: DHCP ADDRESS RESOLUTION SUCCEEDED

Dynamic IP address resolution via DHCP succeeded.
15.
Msg:DSL SYNC FAILURE

A DSL modem synchronization failure occurred.
16.
Msg:DSL SYNC LOST

The BSU has lost synchronization with the customers modem.
17.
Msg:DSL SYNC SUCCEEDED

DSL modem synchronization succeeded.
18.
Msg:FAR-END RINGING
The far end in a VoIP call is ringing.
19.
Msg: HAVE USER ACCESS HIGHLIGHTED IP ADDRESS

This message appears after a successful PPP authentication when the
ISPSYNC DSL/IP command is run. Instruct the customer to use the IP
address highlighted in yellow (the IP address of the BSU) to run ping,
traceroute, etc.
20.
Msg:HTTP ADDRESS TEST FAILURE

A web page was not returned for the HTTP test.
21.
Msg:HTTP ADDRESS TEST SUCCEEDED

A web page was returned for the HTTP test.
22.
Msg:IP PING FAILURE

The number of pings that were returned is equal to or less than the
configured Ping Connectivity Failure threshold.
23.
Msg:IP PING SUCCEEDED

The number of pings that were returned is equal to or greater than the
configured Ping Connectivity Success threshold.
24.
Msg:IP TRACE ROUTE FAILURE

The specified trace route IP address was not reached.
25.
Msg:IP TRACE ROUTE SUCCEEDED

For the trace route test, the targeted IP address was reached, and the time
to reach all of the intermediate addresses did not exceed the maximum
time allowed.
26.
7-28
Msg:METALLIC TEST REQUEST NOT ALLOWED
Summary Messages

* MUST DROP ACCESS FIRST
* POTS CALL MAINTAINED
When DSL synchronization has been established with POTS Keep-Alive,
metallic tests are blocked.
27.
Msg:* MUST DROP ACCESS FIRST

In order to run a metallic test after DSL synchronization has been
established with POTS Keep-Alive, you must first drop the access on the
line.
28.
Msg:NO ATM PVC TRAFFIC DETECTED

The count of ATM PVC packets is zero. This condition may indicate that the
ATM parameters used in the test request are wrong or that no
authentication was attempted.
29.
Msg:*POTS CALL MAINTAINED

Any voice call that was on the line prior to the attempted metallic test
request has been maintained.
30.
Msg:PPP AUTHENTICATION FAILURE

The test system was unable to authenticate to the PPP server. This might
indicate that the PPP Login or Password was not entered correctly.
31.
Msg:PPP AUTHENTICATION SUCCEEDED

The test system was able to successfully authenticate to the PPP server.
32.
Msg:READY TO AUTHENTICATE
The BSU has established synchronization with the customer ATU-R
modem and is ready to receive a DHCP or PPP authentication request
from the customers modem or computer.
33.
Msg:READY TO RESOLVE ADDRESS

The BSU modem has synchronized with the DSLAM modem using the
IPOA protocol and is in the process of resolving an IP address through
DHCP.
34.
Msg:READY TO VERIFY ADDRESS

The BSU modem has synchronized with the DSLAM modem using the
IPOA routed protocol and is in the process of verifying its IP address.
35.
Msg: READY TO ESTABLISH SYNC WITH CPE

The internal modem in the BSU has been configured as an ATU-C and is
waiting for the customers modem to synchronize.
36.
Msg:REGISTRATION SUCCEEDED.
The registration process in VoIP call setup succeeded.
Summary Messages
37.
Msg:REMOTE DSL MODEM DETECTED

*ATTEMPTING TO SYNC
The BSU has detected the customers modem.
38.
Msg: REQUEST REDIRECTED

The targeted web site was not reached. The web server redirected the
request.
39.
Msg:SEARCH STRING NOT IN HTML SOURCE

A web page was returned for the HTTP test, but the specified search string
was not found on the web page.
40.
Msg:SERVER SIDE ERROR

The HTTP error code listed in the HTTP THROUGHPUT STATISTICS
indicates an error on the server side.
41.
Msg: SYNC FAILURE - DSLAM DETECTED

The SYNC failed, but the BSU internal modem, configured as an ATU-R,
did detect a modem signal from the ATU-C located in the DSLAM.
42.
Msg:SYNC FAILURE - DSLAM NOT DETECTED

The SYNC failed because the BSU internal modem, configured as an ATUR, did not detect a modem signal from the ATU-C located in the DSLAM.
43.
Msg: SYNCOUT FAILURE - CPE DETECTED

The SYNC failed, but the BSU internal modem, configured as an ATU-C,
did detect a modem signal from the customers ATU-R.
44.
Msg: SYNCOUT FAILURE - CPE NOT DETECTED

The SYNCOUT failed because the BSU internal modem, configured as an
ATU-C, did not detect a modem signal from the customers ATU-R.
45.
Msg:TEST COMPLETE - EXAMINE RESULTS

For the PING test, the number of successful pings is greater than the PING
command failure threshold but less than the PING command success
threshold.
For the Trace route test, the targeted IP address was reached, but the time
to reach one or more of the intermediate addresses exceeded the
maximum time allowed.
For the ATM Loopback test, the number of successful F5 OAM loopbacks
is greater than the ATM Loopback command failure threshold but less than
the ATM Loopback command success threshold.
46.
7-30
Msg:THROUGHPUT TEST FAILURE
Summary Messages

The test system was able to log onto the server specified for the FTP or
HTTP throughput test, and the file to be transferred was found, but the test
timed out before the entire file was transferred.
47.
Msg:THROUGHPUT TEST SUCCEEDED

The test system was able to log onto the server specified for the FTP or
HTTP Throughput test, the file to be transferred was found, and the entire
file was transferred to the test system.
48.
Msg:TRANSACTION STOPPED
The user clicked the STOP button to cancel a BSU test request.
49.
Msg:WEB SITE NOT FOUND

The user specified URL for the HTTP test was not found.
Summary Messages

Summary Messages
1.
Msg: TIMEOUT IN CALL TEST

When you establish a callback path on certain types of lines, LoopCare will
deliver two audible beeps over the callback line. You can then monitor the
subscriber's dial tone by entering the pound (#) sign on your Touch-Tone
pad. If LoopCare fails to detect a pound sign, it will return this message.
7-32
Summary Messages

Summary Messages
1.
Msg: CO TESTS NOT DONE

A FULL request was submitted for a Harris RTU, which does not support
CO tests.
2.
Msg: OPEN LINE CKT TIP AND RING

The line circuit test was made and the arrangement indicated an open on
both sides of the line circuit.
3.
Msg: INVALID LINE CKT ARRANGEMENT

The line circuit test was made and the arrangement of battery and ground
was not what was expected based on the line record information. This
message may be followed by a message describing the specific line circuit
arrangement detected. Usually, the valid line circuit arrangement would
have about -48 volts of battery on the ring side and a ground on the tip
side.
4.
Msg: * TIP **** V, RING-GROUND

LoopCare detects battery on the tip side and a ground on the ring side of
the line circuit. The voltage value for the tip side will be displayed in the
body of the message. This message will usually modify INVALID LINE CKT
ARRANGEMENT.
5.
Msg: * TIP **** V, RING-OPEN

LoopCare detects battery on the tip side and an open on the ring side of
the line circuit. The voltage value for the tip side will be displayed in the
ARRANGEMENT.
6.
Msg: * TIP-OPEN, RING **** V

LoopCare detects an open on the tip side and battery on the ring side of
the line circuit. The voltage value for the ring side will be displayed in the
ARRANGEMENT.
7.
Msg: * TIP-GROUND, RING-OPEN

LoopCare detects a ground on the tip side and an open on the ring side of
the line circuit. This message will usually modify INVALID LINE CKT
ARRANGEMENT.
8.
Msg: * TIP-OPEN, RING-GROUND
Summary Messages
LoopCare detects an open on the tip side and a ground on the ring side of
the line circuit. This message will usually modify INVALID LINE CKT
ARRANGEMENT.
9.
Msg: * BATTERY BOTH SIDES

LoopCare detects battery on both the tip and ring sides of the line circuit.
This message will usually modify INVALID LINE CKT ARRANGEMENT.
10.
Msg: * T-R SHORT

LoopCare detects a tip-to-ring short (< 50 kilohms) across the line circuit.
This message usually modifies INVALID LINE CKT ARRANGEMENT.
11.
Msg: * BATTERY OUT OF LIMITS

The measured battery voltage was not within the acceptable range of
values (normally -42 to -54 volts).
12.
Msg: * LINE CKT RESISTANCE TOO HIGH

The measured resistance to ground of the line circuit was higher than
expected. Normally you would usually expect less than 500 ohms T-G,
although exceptions exist.
13.
Msg: POSSIBLE INVALID ACCESS

An invalid access looks like an open-in to LoopCare. Whenever LoopCare
detects an open-in it tries to determine if the condition is a true open or an
invalid access. This message is seen most frequently on crossbar lines.
First, LoopCare will request that the line circuit (line identification in a
crossbar office) be placed on the loop. If LoopCare "sees" the line circuit, it
assumes that the condition is a true open. If LoopCare does not "see" the
line circuit, the condition may be an open between the test trunk and the
line circuit, or it may be an invalid access of the line. This message will be
displayed in the latter case. It will be modified by message 13.
14.
Msg: MLT CAN'T SEE LINE CKT

If a possible invalid condition is identified, this message will modify
message 12. It indicates that the line circuit was not seen.
15.
Msg: CAN'T DRAW DIAL TONE
16.
The dial-tone test was not able to draw dial tone within six seconds.
17.
Msg: CAN'T DRAW DIAL TONE DUE TO NOISE

The noise measurement on a line circuit indicates that the noise level is too
high to allow the accurate detection of dial tone.
This message applies to both the LTS and DMU.
18.
Msg: SLOW DIAL TONE

The dial-tone test was able to draw dial tone, but it was slow in doing so
(between three and six seconds).
7-34
Summary Messages

19.
Msg: CAN'T BREAK DIAL TONE

The dial-tone test was not able to break dial tone within one second.
20.
Msg: DIAL TONE BURST DETECTED

To prevent misleading draw and break dial-tone test results, a check is
made for a one-second burst of dial tone in ESS offices. This one-second
burst can be caused by one of the following:
21.
Denied service
Unigauge loop
Remote make busy key feature
Msg: POSSIBLE CO WIRING ERROR

In a crossbar office an invalid access can be caused by faulty wiring in the
No-Test connectors appearing in the central office. If an open-in is detected
in a crossbar office, LoopCare will check for a ground or -48 volts of battery
and a 480-Hz tone. If these are seen, LoopCare assumes that there is a
possible central office wiring error and will return this message.
22.
Msg: CAN'T DO CO TEST- LOOP FAULT

This message will appear on a CO test run over a No-Test trunk access
only. It indicates that the CO test was not run because of a loop fault. The
loop fault must be < 25 kilohms to prevent the CO test from being run. It will
be followed by message 20.
23.
Msg: DO FULL TEST FOR COMPLETE ANALYSIS

This message is a recommendation for the FULL test in order to get the full
series of tests run. This will allow you to identify the condition of the entire
line. This message will modify message 19.
24.
Msg: POSSIBLE LINE CKT DETECTED

This message may appear on the LIN and QIN tests. A LIN test will not run
the central office portion of the FULL series, although it is looking into the
central office. If a line circuit signature is identified, this message will be
displayed.
25.
Msg: CAN'T DO CO TEST- XBAR OFFICE

This summary message will be displayed when the CO test is made on a
crossbar office. LoopCare cannot run the line circuit and draw and break
dial tone tests in a crossbar office unless you have an MDF access.
26.
Msg: * MDF NEEDED TO TEST CO

In a crossbar office, LoopCare can only do the CO test if you have an MDF
access.
27.
Msg: NO POTS SERVICE
Summary Messages
This message is displayed when a CO request is run on a line that does
not provide POTS service, for example on a line that provides only xDSL
service.
28.
Msg: CAN'T DO CO TEST - INWARD SVC

Inward service means that a subscriber can receive telephone calls but
cannot make them. There is no line circuit and no source of dial tone on the
subscriber's line. Therefore, when LoopCare encounters a line record that
specifies inward service, it skips the CO tests.
29.
Msg: CAN'T DO CO TEST ON

When a line served by a Digital Loop Carrier System (DLCS) is being
tested, the central office must be tested before the loop portion. This is
because the pair gain system only allows access to the central office
before LoopCare requests connection to the loop. If you run a CO request
after a FULL or LOOP, you will receive this message (followed by message
27 and DLCS summary message 65). To test the central office at this point,
you must first drop access ("X" request) and then run a CO request.
30.
Msg: DLCS AFTER METALLIC ACCESS

See message 25. The full three-line message that appears is
CAN'T DO CO TEST ON
DLCS AFTER METALLIC ACCESS
DROP ACCESS, THEN REPEAT REQUEST
31.
Msg: DIAL TONE GROUND SUPPLIED

The line circuit is open on one side and battery is being applied on the
other side. LoopCare supplies a ground to draw dial tone.
32.
Msg: CO TESTS NOT DONE - NO POTS SERVICE

A FULL test was requested on a xDSL line which does not have underlying
POTS service. Central Office testing is not possible.
33.
Msg:EMS Login Failure

The login to the NetManager Element Management System was not
successful. This error could be due to a communication problem with the
EMS or an incorrect login ID or password.
34.
Msg:CHANGED DIRECTORY NUMBER

The line to be tested is on intercept because its directory number has been
changed or deleted.
35.
Msg:CHANGED DIRECTORY NUMBER INDIV

changed or deleted.
36.
7-36
Msg:PORTED DIRECTORY NUMBER
Summary Messages

ported out.
37.
Msg:LOCATION PORTABILITY
The line to be tested is on intercept because it has been ported out to
another switch.
38.
Msg:UNOBTAINABLE DIRECTORY NUMBER

The directory number supplied in the request is not valid in the switch at
this time.
Summary Messages

Summary Messages
1.
Msg: C-MESSAGE NOISE DETECTED

A test run by a Harris 107A/F test unit has detected C-message noise
faults.
2.
Msg: * LONGITUDINAL NOISE = ***DB RNC

The detected C-message noise fault is longitudinal.
3.
Msg: * METALLIC NOISE = ***DB RNC

The detected C-message noise fault is metallic.
4.
Msg. * NOISE BALANCE MARGINAL = ***DB

faults with marginal capacitance balance.
5.
Msg. * NOISE BALANCE POOR = ***DB

faults with poor capacitance balance.
7-38
Summary Messages

Summary Messages
The following coin messages will appear only on lines that have coin terminations.
(See FULL and COIN test requests.)
1.
Msg: TOTALIZER HOMED: ATTEMPT **

The totalizer was originally off home, but was successfully returned to
home by the test. The number of attempts needed to home the totalizer will
be displayed in the body of the message.
Normally, if the totalizer is off home it should take one attempt to home it. If
more attempts are required to home the totalizer this could mean that there
is some problem in the totalizer or loop.
2.
Msg: TOTALIZER NOT HOMED

A totalizer was detected, but the test failed to home it. This message may
be followed by other messages indicating whether or not tones were
detected.
3.
Msg: RUNAWAY TOTALIZER **** MA

An attempt has been made to home the totalizer, but the totalizer won't
stop stepping. This condition is identified by the detection of more than 36
tone bursts. The current at which the bursts were detected will be displayed
in the body of the message.
A runaway totalizer can be caused by faulty T2 contacts in the coin station.
LoopCare testing will stop after a runaway totalizer is detected.
4.
Msg: STALLED TOTALIZER **** MA

An attempt has been made to home the totalizer, but the totalizer won't
step. The condition is identified by the detection of a continuous tone. The
current at which the tone is detected will be displayed in the body of the
message.
The system makes three attempts to "unstall" the totalizer and home it. If it
fails after the third try, this message is displayed. Testing will stop at this
point. A stalled totalizer can occur with a stuck coin or a full coin box.
5.
Msg: TOTALIZER WAS STALLED **** MA

An attempt was made to home the totalizer, but the totalizer was stalled.
Subsequent attempts to "unstall" the totalizer were successful, however.
The current at which the totalizer was stalled will be displayed in the body
of the message.
6.
Msg: NO TONES DETECTED **** MA

LoopCare did not detect any of the expected coin tones during the totalizer
homing sequence. The current used while attempting to detect tones will
be displayed in the body of the message.
Summary Messages
7.
Msg: TONES DETECTED

LoopCare has detected either the low-frequency tone (1537 or 1700 Hz),
the high-frequency tone (2200 Hz), or both.
8.
Msg: RELAY OPERATED: ATTEMPT **

The coin relay has been operated successfully. The number of attempts
needed to operate the relay will be displayed in the body of the message.
Normally, it takes one attempt to operate the relay. If more attempts are
required to operate the relay, there may be a problem in the relay or the
loop.
9.
Msg: RELAY NOT OPERATED **** MA

LoopCare did not successfully operate the coin relay. The current used to
attempt relay operation will be displayed. A relay would not operate if the
tip-ground circuit resistance was too high or the current that was used to
operate the relay was too low (< 30 ma). A normal relay should operate
with a current of no more than 41 ma.
10.
Msg: RELAY IS FAST **** MSEC

The coin relay was operated, but the operation speed was too fast (<425
msec time span). The relay speed will be displayed in the body of the
message.
11.
Msg: RELAY IS SLOW **** MSEC

The coin relay was operated, but the operation speed was too slow (>475
msec time span). The relay speed will be displayed in the body of the
message.
12.
Msg: RELAY CURRENT **** MA

The current at which the coin relay was operated. Normally, a coin relay
should operate with a current under 41 ma.
13.
Msg: LEAD REV OR POLARITY GUARD PROBLEM

If the coin station is an "A" set, this message indicates that there is a lead
reversal problem. If the coin station is not an "A" type (if it were a "C" type
instead), the message would indicate a polarity guard problem.
14.
Msg: INITIAL RATE OR FRAUD CONTACT OPEN

On a dial-tone-first coin station, LoopCare detects the initial rate (IR) and/or
the fraud contacts open. This message will only appear for dial tone-first
coin sets.
15.
Msg: A RELAY POLARITY GUARD-POSS FAULT

On a coin-first station, LoopCare detects an A-relay polarity guard problem
(possibly a shorted diode). This message will only appear for coin-first sets.
16.
7-40
Msg: TOTALIZER STALLED AND/OR ROH
Summary Messages

This message will be set if a totalizer was detected on the line (T-R short
indicates presence of totalizer on coin line), no coin tones were detected
when homing was attempted, and the T-R DC resistance was between 500
ohms and 3.4 kohms.
17.
Msg: TOTALIZER: HOMED OR SHORT

This message may appear when running either a CSET or CHOME
request. The message appears when either a ROH or HARD SHORT
condition appears. The number of attempts that it took to home the totalizer
is displayed, along with whether or not it detected both the high- and lowfrequency tones.
18.
Msg: NO TONES DETECTED

This message will be set if, during the attempts to home the totalizer,
LoopCare does not detect either the high- or low-frequency coin tones.
19.
Msg: COIN SUPERVISORY CKT PROBLEMS

This message (along with the VER C5) will be displayed if the totalizer is
home on the first attempt with the proper current or if the coin relay is
operated on the first attempt with the proper current and if there are no
other loop or central office problems.
20.
Msg: TOT NOT HOME AND/OR ROH

This message will be displayed if LoopCare saw a hard tip-ring (T-R) short
(<3.4 kilohms) and was unable to classify the cause as either a jammed
totalizer or a receiver-off-hook (ROH) condition.
21.
Msg: DT NOT DONE

The dial tone (DT) test could not be done for this phone as it is a coin-first
phone. You need to separate the coin-first and dial-tone first phones to
unique NNXs and use the "C" and "D" options respectively. These options
are used in the m2 coin field in the LoopCare Access Table (mltacc.src).
Summary Messages

Summary Messages
1.
Msg: CROSS TO WORKING PAIR: TIP-SIDE

LoopCare detects a cross on the tip side of the pair. A cross is identified by
the following LoopCare DC SIGNATURE:
Resistance
Voltage
10 K
1K
T-R
20 V
1K
T-G
R-G
In addition, the LoopCare CRAFT battery must be greater than the locally
determined CRAFT threshold (default = 6 volts).
This message will be followed by another message that indicates the
relative severity of the battery on the line. This battery voltage will be given
in LoopCare CRAFT values.
2.
Msg: CROSS TO WORKING PAIR: RING-SIDE

LoopCare detects a cross on the ring side of the pair. A cross is identified
by the following DC SIGNATURE:
Resistance
Voltage
10 K
1K
1K
T-R
20 V
T-G
R-G
In addition, the CRAFT battery must be greater than the locally determined
CRAFT threshold (default = 6 volts).
This message will be followed by another message that indicates the
relative severity of the battery on the line. This battery voltage will be given
in CRAFT values.
The following messages indicate the relative severity of the battery on the
line. The battery voltage will be given in CRAFT values. These messages
will usually follow the messages that indicate LoopCare has detected a
cross, but they can also appear independently.
There are five general severity levels, they are determined by the CRAFT
voltage value. These severity levels and the CRAFT voltage values that are
used to set them are given below.
In addition to the voltage value, the side (tip-ground or ring-ground) that the
voltage is on is important in determining the exact text of the message.
7-42
Summary Messages

VERY LIGHT BATTERY
>
-1 V
and
<=
3V
LIGHT BATTERY
>
3V
and
<=
10 V
MODERATE BATTERY
>
6V
and
<=
10 V
HARD BATTERY
>
10 V
and
<
20 V
VERY HARD BATTERY
>=
20 V
If there is voltage on the tip-ground side of the line, one of the following
messages will be displayed.
(The CRAFT voltage will be displayed in the body of the message.)
3.
Msg: VERY LIGHT BATTERY T-G ***** V
4.
Msg: LIGHT BATTERY T-G ***** V
5.
Msg: MODERATE BATTERY T-G ***** V
6.
Msg: HARD BATTERY T-G ***** V
7.
Msg: VERY HARD BATTERY T-G ***** V

If there is voltage on the ring-ground side of the line one of the following
messages will be displayed. (The CRAFT voltage will be displayed in the
body of the message.)
8.
Msg: VERY LIGHT BATTERY R-G ***** V
9.
Msg: LIGHT BATTERY R-G ***** V
10.
Msg: MODERATE BATTERY R-G ***** V
11.
Msg: HARD BATTERY R-G ***** V
12.
Msg: VERY HARD BATTERY R-G ***** V
13.
Msg: S X S SPLIT C.O. BATTERY

When LoopCare recognizes the following DC three-terminal signature on a
Step-by-Step office, the message above will be displayed.
<1 Kohms T-G
- 28 < Volts
<-22 T-G
< 1 Kohms R-G
- 28 < Volts
<-22 R-G
In cases with hard shorts or hard ring grounds on a Step-by-Step line, the
three-terminal DC voltage will appear on both the tip and ring sides of the
line.
When this happens, the message indicating split C.O. battery should be
displayed and the VER Code should be VER 26 (MDF TEST
RECOMMENDED-LOW RESISTANCE) to inform the user that the trouble
may have to be sectionalized.
Summary Messages

Summary Messages
1.
Msg: DENIED CPE

This CPE is being denied service because it is over and above the number
subscribed. For example, the customer has subscribed for an ISDN line for
four PDNs and tries to hook up five. The fifth CPE would be DENIED. This
status applies to ISDN lines only.
2.
Msg: DENIED/INTERCEPT - MIXED

LoopCare/ISDN has determined that some of the services on this DSL are
on INTERCEPT while others are DENIED.
3.
Msg: DENIED/RESTRICTED SERVICE - MIXED

This message indicates that there are different types of restricted services
on the OE, PDN, or DN. The services may either be DENIED or on
INTERCEPT. For example, if the service is on INTERCEPT then the
incoming calls can be received. If the service is DENIED TERMINATING
then only outgoing calls can be made. Other services may be completely
DENIED, then the line is temporally out of service.
4.
Msg: DENIED SERVICE

This message indicates that LoopCare is testing on a line on which both
inward and outward calls have been denied by the Switching Control
Center. The subscriber cannot make or receive any calls. Typically this
situation occurs as a response to nonpayment of bills.
5.
Msg: DENIED SERVICE - ADD ANALYSIS

Service has been denied for this DSL, however, additional analysis or
further testing is required.
6.
Msg: DENIED SERVICE - TERMINATING

This message indicates that LoopCare is testing a line on which calls to the
subscriber's telephone have been denied by the Switching Control Center.
The subscriber can make calls but not receive any. Typically this situation
occurs as a response to nonpayment of bills; it also occurs on charge-a-call
telephone lines, where telephones are not designed to receive calls.
7.
Msg: DENIED SERVICE - ORIGINATING

This message indicates that LoopCare is testing a line on which calls from
the subscriber's telephone have been denied by the Switching Control
Center. The subscriber can receive calls but not make any. Typically this
situation occurs as a response to nonpayment of bills.
7-44
Summary Messages

Summary Messages
1.
Msg: BAD DLC OR DC TEST PAIR

There is a service affecting problem with the Digital Loop Carrier or DC
Test Pair attached to the line that was tested.
2.
Msg: C.O. BATTERY ON PAIR GAIN SYSTEM

LoopCare has detected central office (CO) battery on a pair gain system
and cannot make further tests since it cannot make loop access. This
message will be modified by the following message.
3.
Msg: * LOOP ACCESS NOT ATTEMPTED

This message modifies the messages above or message 3 below. It
indicates that loop access was not attempted for one of the reasons
described.
4.
Msg: INVALID PAIR GAIN C.O. SIGNATURE

LoopCare has detected a signature that does not match one of the
acceptable CO terminations. Loop access is not made. (Message 2 follows
to indicate this.) A description of the valid CO signatures is provided below:
Service
All but Coin
Resistance
T-R 17 to 44 kilohms
T-G 100 to 210 kilohms
R-G > 100 kilohms
Voltage
-3 to 3 volts
-3 to 3 volts
or
T-R > 162 kilohms
R-G 40 to 132 kilohms
-60 to -27 volts

-60 to -27 volts
or
Coin
Integrated DLCS
T-R > 122 kilohms

R-G > 122 kilohms
-3 to 3 volts
-3 to 3 volts
R-G > 40 kilohms
-3 to 3 volts
-3 to 3 volts
-3 to 3 volts
-3 to 3 volts
Summary Messages

Summary Messages
1.
Msg: CO TESTS NOT DONE

* NOT SUPPORTED BY TEST UNIT
This message indicates that a FULL test request was entered for a POTS
line tested by a CLT.
2.
Msg: DATA RATE BELOW BIT-RATE THRESHOLD

DSL service parameters retrieval has determined that the available data
rate on the tested line is below the permissible threshold.
3.
Msg: DIGITAL DATA NOT AVAILABLE

This message indicates that a DSLDIG or FULLX test request was entered
for a LTE for which digital data is not available.
4.
Msg: DSP DATA NOT RETRIEVED

* UNSUPPORTED LTE CARD TYPE
This message indicates that a FULL or DSLDIG test request was entered
for a LIM type that is not supported for testing by LoopCare. This summary
message appears only with VER NT.
5.
Msg: HDSL2 RATE ESTIMATED USING SDSL ALGORITHM

This message indicates that the SDSL Data Rate Prediction algorithm was
used for the line under test. There is no separate data prediction algorithm
for HDSL2 service.
6.
Msg: IDSL RATE ESTIMATED USING SDSL ALGORITHM

This message indicates that the SDSL Data Rate Prediction algorithm was
used for the line under test. There is no separate data prediction algorithm
for IDSL service.
7-46
Summary Messages

7.

REQUEST NOT SUPPORTED FOR THIS LTE TYPE
This message indicates that a CO or SOAK test request was entered for a
POTS line tested by a CLT.
8.

THIS TYPE OF LTE IS NOT SUPPORTED
This message indicates that a DSLDIG test request was entered for an
XDSL line where an LTE is used that is not supported for the DSLDIG
request.
9.
Msg: * LINE IN GALVANIC ISOLATION MODE

This message indicates that the line to be tested is in galvanic isolation
mode.
10.
Msg: LOSS OF CELL DELINEATION (FE)

Loss of Cell Delineation at the far end in the SONET layer.
11.
Msg: LOSS OF CELL DELINEATION (NE)

Loss of Cell Delineation at the near end in the SONET layer.
12.
Msg: METALLIC TEST NOT RUN

This message indicates a FULLX test request has been submitted for a
DSL line served by a LTE that is supported by the Digital Service
Parameters feature but for which there is no associated metallic test head.
13.
Msg: REMOTE MODEM NOT DETECTED

DSL service parameters retrieval has not detected a remote modem.
Summary Messages
14.
Msg: REMOTE SIG LOSS: UNKNOWN CAUSE

This message indicates that the Central Office Loop Terminating
Equipment (LTE) modem has detected a loss-of-signal from the customer
premises end. The cause of the loss-of-signal is not known.
15.
Msg: REQUEST REJECTED: MISSING LTE INFO OR TN

This message indicates the DSLDIG request has been submitted, but not
all LTE information has been provided.
16.
Msg: SIGNAL LOSS FROM REMOTE END

premises end. The customer powering off their xTU-R modem most likely
causes this.
17.
Msg: TESTED USING OVERRIDE DSL TYPE

* LTE INDICATES DIFFERENT DSL TYPE
This message indicates that the tester entered an override value in the CO
field, other than the current service available on the line. This may be done,
for example, to qualify a line for a specific service not currently offered on
the line.
18.
Msg: TEST EQUIPMENT BUSY

This message indicates that the tester submitted a DSLDIG test request for
a line served by a LTE when a test is already in progress for another DSL
line on the same LTE.
19.
Msg: XDSL CARD IS NOT IN SERVICE

This message indicates that the card in the slot provided for testing is not in
service. This may be have been done by the provisioning system, by the
LTE Element Management System, by a field technician using the craft
port, or the card could have been removed. This message could indicate
conditions such as entry of the incorrect slot number on the GUI, the
7-48
Summary Messages

customer may have been taken out of service due to non-payment, work is
being done on the LTE, etc. It is also possible that an error was made when
the slot or line number was entered.
20.
Msg: XDSL CPE EQUIP PROBLEM

This message indicates that the customer xDSL equipment (i.e., the
remote modem) has encountered a problem. Additional summary
messages that appear with this message will provide more detail on the
type of problem.
21.
Msg: XDSL EQUIPMENT NOT INSTALLED

DSL service parameters retrieval has determined that no XDSL equipment
has been installed.
22.
Msg: XDSL LTE EQUIP PROBLEM

This message indicates that the LTE port assigned to the customer has
encountered a problem. Additional summary messages that appear with
this message will provide more detail on the type of problem.
23.
Msg: XDSL LINE OUT OF SERVICE

This message indicates that the LTE port assigned to the customer has
been taken out of service. This may be have been done by the provisioning
system, by the LTE Element Management System, or by a field technician
using the craft port. This message could indicate conditions such as the
customer may have been taken out of service due to non-payment, work is
being done on the LTE, etc.
24.
Msg: XDSL LINE SELF TEST FAILURE

This message indicates that the Loop Terminating Equipment (LTE) port
assigned to the customer has failed its self-diagnostics testing. This
situation usually indicates a hardware failure.
Summary Messages
25.
Msg: XDSL LOSS OF SIGNAL DETECTED

premises end. The customer powering off their xTU-R modem did most
likely not cause this. It may have been caused by the loop between the
Central Office and the customer premises equipment being opened.
26.
Msg: XDSL MODEM IN TRANSITION PHASE

assigned to the customer is in a transition phase either from being down to
the steady-state (normal) condition or from the steady-state to a being
down. Some possible causes for these transient conditions may be the
presence of impulse noise on the loop, the customer premises equipment
being turned on or off, etc. If this message is encountered, it is
recommended that the test be re-run after waiting a few minutes.
27.
Msg: XDSL MODEM IN UNKNOWN STATE

assigned to the customer responded to the Loop Terminating Equipment
(LTE) operating system with an unknown state problem. This situation is
highly unlikely and usually indicates the port has reached a state outside of
its design parameters. If this message is encountered, it is recommended
that the xTU-C hardware be replaces and sent back to the factory for
diagnostics.
28.
Msg: XDSL POWER PROBLEM

When the status is obtained from the LTE, the service parameters retrieved
indicate a power problem in the ATU-R or ATU-C.The cause of the problem
could be power failure or power status unavailable.
29.
Msg: XDSL PROFILE IS NOT ACTIVE

The profile on the ASAM is not active. See the Alcatel instructions for how
to reactivate the profile on the ASAM.
7-50
Summary Messages

30.
Msg: XTUC CONFIGURATION PROBLEM

DSL service parameters retrieval has detected a problem with the XTUC
configuration.
31.
Msg: XTUC NOT DETECTED

DSL service parameters retrieval has not detected an XTUC.
32.
Msg: XTUC NOT RESPONDING

assigned to the customer is not responding to the LTE operating system.
This situation usually happens due to an internal communication problem.
33.
Msg: XTUR NOT RESPONDING

Equipment (LTE) modem is not getting a response from the customer
premises equipment (i.e., the xTU-R modem). This may have been caused
by the customer powering off their xTU-R modem or by the loop between
the Central Office and the customer premises equipment being in an open
state.
Summary Messages

Summary Messages
1.
Msg: DISTANCE FROM LTE nnnn FT

LoopCare has determined that the there is a hard Tip-to-Ring short at nnnn
feet.
NOTE:
The distance may be reported in feet (FT) or meters (M), depending on your
environment.
The Distance to Short test is available only for lines tested by a Stinger with
a CLT when wideband access is available. For this test to be performed,
the CLT must have firmware Version 23 or later running, and the Stinger
must have firmware Version 9.0-139 or later running. The test is performed
only when the Tip-Ring loop resistance is equal to or less than 700 Ohms.
Results are reported only if a short is found.
7-52
Summary Messages

Summary Messages
1.
Msg: CANNOT EXECUTE - LMOS/MLT group must be up.

EMUadmin requires the presence of an MLT group. If no group is running,
the above error message will be displayed
2.
Msg: ILLEGAL TRANSACTION FOR EMU

When the LOC2 test request is executed, and the testhead is the Digital
Measurement Unit - Central Office (DMU-C), the above error message will
be displayed. The LOC2 test request requires multiple test trunk access
and measurements and the DMU-C only has one test trunk access.
Summary Messages

NOTE:
Each message that is identified as non-service-affecting appears only in the
body of the FTTPDIG output and not with the VER code.
Messages
1.
Msg:ALL TIMING REFERENCES FAILED

Synchronization service affecting condition.
2.
Msg:BATTERY CHARGE IS LOW

Battery non service affecting condition.
3.
Msg:BATTERY IS PROVISIONED, BUT MISSING

4.
Msg:BATTERY PRESENT, BUT WILL NOT RECHARGE

5.
Msg:BOARD INSTALLATION ALARM

Equipment service affecting condition.
6.
Msg:BOARD INSTALLATION ALARM (SB CARD)

Equipment non service affecting condition for standby.
7.
Msg:BOARD INSTALLATION MISSING ALARM

Equipment non service affecting condition.
7-54
Summary Messages
8.
Msg:BOARD INSTALLATION MISSING ALARM (SB CARD)

9.
Msg:BOARD MISSING ALARM

10.
Msg:BOARD MISSING ALARM (SB CARD)

11.
Msg:BOARD RESET PROTECTION

12.
Msg:BOARD RESET PROTECTION (SB CARD)

13.
Msg:BOARD TYPE MISMATCH

14.
Msg:CELL PHASE ERROR

ONT service affecting condition
15.
Msg:DEFENSE ALARM, PLUG-IN UNIT DISCONNECTED

Summary Messages
16.
Msg:DEFENSE ALARM, PLUG-IN UNIT DISCONN (SB CARD)

17.
Msg:DOWNSTREAM CELL DISCARD

ATM non service affecting condition.
18.
Msg:END-TO-END VC-AIS RECEIVING INDICATION

ONT service affecting condition.
19.
Msg:END-TO-END VC-RDI GENERATING INDICATION

20.
Msg:END-TO-END VC-RDI RECEIVING INDICATION

21.
Msg:EQUIPMENT SHUTDOWN DUE TO HIGH TEMPERATURE

22.
Msg:EQPMT SHUTDOWN DUE TO HIGH TEMP (SB CARD)

23.
Msg:EQUIPMENT VERSION MISMATCH

24.
7-56
Msg:EXCESSIVE FAR-END BLOCK ERRORS
Summary Messages

OC3 non service affecting condition.
25.
Msg:EXCESSIVE LINE BIT ERRORS

OC3 service affecting condition.
26.
Msg:EXCESSIVE SECTION BIP-8 ERRORS

27.
Msg:FAN ALARM FOR FAN-1

28.
Msg:FAN ALARM FOR FAN-2

29.
Msg:FUSE ALARM. POWER FUSE BLOWN

30.
Msg:LINE ALARM INDICATION SIGNAL

31.
Msg:LOSS OF ACKNOWLEDGEMENT
32.
Msg:LOSS OF ATM CELL DELINEATION

Summary Messages
33.
Msg:LOSS OF CELL DELINEATION

34.
Msg:LOSS OF EXTERNAL POWER

ONT non service affecting condition.
35.
Msg:LOSS OF FRAME AT THE DS1 INTERFACE

36.
Msg:LOSS OF PROTECTION SWITCHING CAPABILITY

37.
Msg:LOSS OF SIGNAL
38.
Msg:LOSS OF SIGNAL AT THE DS1 INTERFACE

39.
Msg:MESSAGE ERROR
40.
Msg:MODULE INSERTED
7-58
Summary Messages

41.
Msg:MODULE REMOVED
42.
Msg:MODULE TEMPERATURE EXCEEDED LIMIT

43.
Msg: NETWORK ELEMENT (OR PART) NOT PROVISIONED

The PON port, ONT, ONT POTS, ONT Video, and/or ONT LAN entity has
not been provisioned. Check the provisioning data in the GUI output.
44.
Msg: NETWORK ELEMENT (OR PART) OOS

The PON port, ONT, ONT POTS, ONT Video, and/or ONT LAN entity is not
in service. Check the status data in the GUI output.
45.
Msg:NEWLY DISCOVERED BUT NOT ENTERED/PROVISIONED

PON non service affecting condition.
46.
Msg:NO ALARMS PRESENT

There are no service affecting or non service affecting alarms.
47.
Msg: NON SERVICE AFFECTING ALARMS PRESENT

There are no service-affecting alarms and one or more non-serviceaffecting alarms is listed in the body of the FTTPDIG output.
48.
Msg:OMCI COMMUNICATION DOWN

Summary Messages
49.
Msg:ONT AUTONOMOUSLY DISABLED(MISBEHAVING

TRANSMISSION)
50.
Msg:ONT FAILED TO RETURN EXPECTED PASSWORD

51.
Msg:ONT IS INACTIVE
52.
Msg:PARITY BIT ERROR ON UTOPIA BUS

PON service affecting condition.
53.
Msg:PEER BOARD LOSS OF COMMUNICATION ERROR

54.
Msg: PERFORMANCE MONITORING NOT ENABLED

No performance monitoring counts are available for the the specified ONT
and its related network elements, because performance monitoring is
disabled for the ONT.
55.
Msg:PHYSICAL EQUIPMENT ERROR OF ONT

56.
Msg:PLUG-IN MODULE AND CONFIGURATION MISMATCH

7-60
Summary Messages

57.
Msg:PON COMMUNICATION FAILURE ON OLT PORT

58.
Msg:PREFERRED TIMING REFERENCES FAILED

Synchronization service affecting condition.
59.
Msg:RECEIVED ALARM INHIBIT FROM ONT

60.
Msg:RECEIVING AIS AT THE DS1 INTERFACE

61.
Msg:RECEIVING RAI AT THE DS1 INTERFACE

62.
Msg:REMOTE FAILURE/DEFECT INDICATION

63.
Msg:SBOARD TEMPERATURE EXCEEDED

64.
Msg:SECTION LOSS OF CLOCK

65.
Msg:SECTION LOSS-OF-FRAME
Summary Messages
66.
Msg:SECTION LOSS-OF-SIGNAL
67.
Msg:SELF TEST FAILURE

68.
Msg:SIGNAL DEGRADATION
69.
Msg:SOFTWARE ACTIVATION FAILURE

70.
Msg:SOFTWARE DOWNLOAD FAILED

71.
Msg:SOFTWARE DOWNLOAD IN PROGRESS

72.
Msg:STANDBY EXCESSIVE FAR-END BLOCK ERRORS

OC3 non service affecting condition for standby.
73.
Msg:STANDBY EXCESSIVE LINE BIT ERRORS

7-62
Summary Messages
74.
Msg:STANDBY EXCESSIVE SECTION BIP-8 ERRORS

75.
Msg:STANDBY LINE ALARM INDICATION SIGNAL

76.
Msg:STANDBY LOSS OF ATM CELL DELINEATION

77.
Msg:STANDBY REMOTE FAILURE/DEFECT INDICATION

78.
Msg:STANDBY SECTION LOSS-OF-CLOCK

79.
Msg:STANDBY SECTION LOSS-OF-FRAME

80.
Msg:STANDBY SECTION LOSS-OF-SIGNAL

81.
Msg:STARTUP FAILURE IN RANGING OF ONT

Summary Messages
82.
Msg:SYSTEM AND BACKUP MEMORY RESET

Common equipment service affecting condition.
83.
Msg:TRANSMITTER FAILURE ON OLT PORT

84.
Msg:UNABLE TO ACTIVATE OSWP/LK-DB

Common equipment service affecting condition.
85.
Msg:UNABLE TO COMMUNICATE WITH SNTP SERVER

Common equipment non service affecting condition.
86.
Msg:UPSTREAM CELL DISCARD

ATM non service affecting condition.
87.
Msg:USED SHELF BANDWIDTH ABOVE 75% CAPACITY

88.
Msg:VIDEO LOSS OF SIGNAL

89.
Msg:WAITING FOR SOFTWARE

90.
7-64
Msg:WAITING FOR SOFTWARE (SB CARD)
Summary Messages

Summary Messages

Summary Messages
1.
Msg: LINE IN USE

LoopCare has determined that the line was being used at the time of
testing, but no speech was detected. This condition can occur for all switch
types.
Switch
Resistance
1, 2, & 3ESS
0 to 3.5 kilohms T-R

0.07 to 1.2 kilohoms T-G
0.07 to 1.2 kilohms R-G
RSSS (ESS1R,
ESS2R)
<7 kilohoms T-R

80 to 125 kilohms T-G
80 to 125 kilohms R-G
SXS
>200 kilohoms T-R

0 to 2.5 kilohoms T-R
>200 kilohoms R-G
1 & 5 XBAR
< 10 kilohoms T-R

0 to 1 kilohm T-G
0 to 1 kilohm R-G
Voltage
-36 to -75 volts one side to ground
+ 10 to - 10 volts other side to
ground.
< 3 volts T-G

< 3 volts R-G
+ 10 to -10 volts other side to
ground
In a Crossbar switch an additional check is made for a 500-Hz permanent

signal. If this signal is not detected, a line-in-use condition exists. If it is
detected, permanent signal is displayed and an ROH test is run.
2.
Msg: ROH: HIGH AND DRY

The receiver-off-hook (ROH) test has been run and an ROH has been
detected. In addition, if the office is a Step-by-Step office, the battery has
been removed from the line. No further tests are performed.
3.
Msg: ROH
The receiver-off-hook test has been run and an ROH has been detected.
No further tests are performed.
4.
Msg: NOT ROH: T-R RESISTANCE HIGH

The receiver-off-hook test has not been run because the T-R resistance is
higher than what is expected for an ROH (T-R resistance > 3.4 kilohms).
Because of this, LoopCare determines that the condition cannot be due to
an ROH.
5.
7-66
Msg: NOT ROH
Summary Messages

The receiver-off-hook test has been run and the condition is not an ROH.
Most likely, there is a T-R short on the line.
6.
Msg: COULD NOT DO ROH TEST

The ROH test could not be made. The reason will be given by one of the
following messages.
7.
Msg: * UNIGAUGE LOOP

The ROH test could not be made because the loop is a Unigauge type
design. The switched gain repeater in the test trunk for Unigauge loops
would result in invalid results.
8.
Msg: * BRIDGE LIFTERS

The ROH test could not be made because a bridge lifter is on the line. This
piece of equipment causes invalid ROH results.
9.
Msg: * NOT HIGH AND DRY

In an ESS office, LoopCare expects an ROH condition to be "High and
Dry." "High" means high resistances to ground, and "Dry" means no
central office battery. If a ground or battery is detected, the ROH test is not
done, because the condition cannot be due to an ROH.
10.
Msg: * DUE TO TYPE TERMINATION

The ROH test could not be made because the termination did not have a
single-party-like termination, or the termination was either 4- or 8-party
service.
11.
Msg: * DC FEMF
The ROH test could not be made because DC foreign voltage was
detected on the line.
12.
Msg: * CAN'T OPEN SLEEVE LEAD

Before LoopCare runs the ROH test in a Step-by Step office, it attempts to
release the permanent signal. If the line circuit could not be accessed
because the sleeve lead could not be operated, the ROH test will not be
made. This problem could be due to a condition in the central office trunk
equipment, the No-Test trunk, or LoopCare.
13.
Msg: * MEASURING CKT FAILURE

Before LoopCare runs the ROH test, it attempts to perform the line circuit
test. If the line circuit test could not be completed because of a problem
with the LoopCare measuring equipment, the ROH test will not be made.
14.
Msg: * CAN'T RELEASE PERMANENT SIGNAL
Summary Messages
To run the ROH test on a loop served by a Step-by-Step office, it is
necessary to remove the central office line circuit (permanent signal). If the
equipment used to release the permanent signal is not available or failed to
remove it, the ROH test will not be run.
15.
Msg: * MEASUREMENT ERROR

LoopCare will stop the ROH test if it receives test result data that is out of
range.
16.
Msg: * LOOP ELECTRONICS

The ROH test could not be made because of certain equipment (CO, OSP,
or TERM) on the line that would prevent valid results. For example, an E6
Repeater (OSP) will prevent an ROH test from being made.
17.
Msg: * CO BATTERY AND EQUIPMENT

If a line has a 7A Range Extender with Gain (REG) or Concentrated REG
(CREG) on it, the ROH test will not be made. These REGs, when active,
will cause inaccurate ROH test results.
18.
Msg: * REG
The ROH test could not be made because a REG is on the line. This
device causes inaccurate ROH results.
19.
Msg: PERMANENT SIGNAL

This message will appear on lines served by ESS and Crossbar offices. It
indicates that LoopCare detected permanent signal on the line. This may
be caused by either a resistive fault that draws in the line circuit or an ROH
that LoopCare was not able to detect because the line was not ROH
testable. The conditions for permanent signal detection are given below:
Switch
Resistance
1, 2, & 3ESS
0.15 to 3.4 kilohms T-R

>150 kilohoms T-G
>150 kilohms R-G
1 & 5 XBAR
< 10 kilohoms T-R

0 to 1 kilohm T-G
0 to 1 kilohm R-G
20.
Voltage
< 3 volts T-G
< 3 volts R-G
ground
Msg: LINE HIGH AND DRY

A permanent signal condition was detected on an ESS line. In this case,
however, there is no battery detected at all on the line.
21.
7-68
Msg: * PERMANENT SIG
Summary Messages

A permanent signal was detected on a line equipped with a 7A REG and
served by a Crossbar office. To release the permanent signal and
determine whether or not the trouble is in or out of the central office, an
MDF test should be performed on the line. The condition is identified by the
following LoopCare electrical signature:
Switch
Resistance
1 & 5 XBAR
< 10 kilohoms T-R

0 to 1 kilohm T-G
0 to 1 kilohm R-G
22.
Voltage
ground
Msg: POSSIBLE LINE IN USE OR

This message will always appear with Summary Messages 23 and 26. The
condition occurs for lines served by ESS or Step-by-Step offices. The
conditions under which these messages will be displayed are shown
below:
ESS, SXS
A busy signature was detected and LoopCare resistance is < 10

kilohms T-R. This condition rarely occurs in an ESS office.
ESS only
Switch
Resistance
Voltage
ESS only

0.07 to 1.2 kilohoms T-G -36 to -75 volts one side to ground
0.07 to 1.2 kilohms R-G + 10 to - 10 volts other side to
ground.
SXS only

0.07 to 1.2 kilohoms T-G -30 to -75 volts one side to ground
0.07 to 1.2 kilohms R-G + 10 to - 10 volts other side to
ground.
23.
Msg: POSSIBLE PERMANENT SIGNAL ON LINE

See Summary 22.
24.
Msg: BUSY - NO SPEECH

During the loop access sequence the line was determined to be busy, but
there was no speech detected at that time. An ROH test may be run.
25.
Msg: BUSY - SPEECH

During the loop access sequence the line was determined to be busy, and
speech was detected on the line. No further tests are run on the line.
Summary Messages
26.
Msg: * COULD BE FROM ROH OR FAULT

See Summary 22.
27.
Msg: DC BUSY
During the loop access sequence the line was determined to be busy. No
speech test was made.
28.
Msg: * 5ESS TRAFFIC BUSY - ACCESS DROPPED

When testing a 5ESS switch with a DCTU, the switch detects whether the
line is busy. A line with a call in progress through the switch is called a
"traffic busy" line. When LoopCare asks the 5ESS switch for an access to a
line, the switch will only allow it if a callback is present; that is, if you
entered a RING, TALK, or MONITOR request and answered your callback
telephone. If you entered a request that does not get a callback (i.e., FULL
or QUICK), the switch will deny access.
29.
Msg: USE MONITOR OR TALK REQUEST FOR ACCESS

When testing a 5ESS switch with a DCTU and the line is traffic busy, the
only way to gain access is with a callback established.
30.
Msg: 5ESS TRAFFIC BUSY - VERIFIABLE

If you entered a request that successfully establishes callback and the line
is traffic busy and the DCTU recognizes the line as NOT being a computer
data line, it is considered a verifiable busy detection. You should be able to
hear the conversation in progress over the callback telephone.
31.
Msg: 5ESS TRAFFIC BUSY - ONLY TALK,

It is not possible to run test requests on traffic busy lines. If you already
have interactive access to such a line, and try to enter any request besides
TALK, MONITOR, or X, you will receive this message.
32.
Msg: MONITOR AND X REQUESTS ALLOWED

See Summary 31.
33.
Msg: 5ESS TRAFFIC BUSY - NON-VERIFIABLE

If you entered a request that successfully establishes callback and the line
is traffic busy but the DCTU suspects that this is a computer data line, it is
considered non-verifiable. A non-verifiable call should not be disturbed
without prior customer permission. If you enter a TALK request on such a
line, you risk causing the call to be interrupted and terminated.
34.
Msg: TALK REQUEST MAY INTERRUPT CALL

Entering a TALK request on a traffic busy - non-verifiable line that may be a
computer data line may cause the call to be interrupted and terminated.
35.
7-70
Msg: SHORT - PROBABLY ROH
Summary Messages

If the resistance value measured by LoopCare is between 100 ohms and
3.4 kilohms, LoopCare will run an ROH test. If the test does not verify an
ROH condition, this message will be displayed, showing that the fault may
be a short or an ROH condition.
36.
Msg: ATTEMPT TO VERIFY BEFORE DISPATCH

This message, displayed with Summary 35, asks the craft to verify the
ROH condition before dispatch by monitoring the line, checking with the
subscriber, or following local procedures.
Summary Messages

Summary Messages
Listed below in alphabetical sequence are the summary messages that appear as
the first message for a Ver Code, followed by a description of what that message
means.
1.
Msg: BUSY PACKET

The packet handler is busy. Testing cannot be done.
2.
Msg: CHANNEL MISMATCH

This message is used to indicate a mismatch between the COT Channel
Unit and the Line Card on an ISDN line served by a Digital Loop Carrier
System (DLCS).
3.
Msg: CHANNEL UNIT ** UNDER TEST

The status of the line indicates that the DSL is taken out of service because
there is a test in progress some where on the line.
4.
Msg: CO EQUIP BAD

Defective equipment in the CO has prevented testing.
5.
Msg: COT CU BAD

The Channel Unit in the Central Office terminal of a universal digital loop
carrier system is bad.
6.
Msg: COT CU SUSPECT

The Channel Unit in the Central Office terminal of a universal digital loop
carrier system could be defective but test data is inconclusive.
7.
Msg: CPE REQUESTED OUT OF SERVICE

The customer has removed his or her terminal from being in service.
8.
Msg: CPE (NT1) ON SECONDARY POWER

This message indicates that the customer's NT1 is running on the
secondary power supply. Primary power supply is marginal or down. This is
not the cause of the trouble, but is additional information which can be
relayed to the customer. The VER Code associated with this message (IR)
causes LMOS/WM to send a FULL request to LoopCare/ISDN via the
retest queue.
9.
Msg: CPE (NT1) POWER SUSPECTED

This message indicates that the channel is out of service probably because
the NT1's primary power is marginal or down. This status is only returned
for an ANSI line. The VER Code associated with this message (IN) causes
LMOS/WM to send a FULL request to LoopCare/ISDN via the retest
queue.
7-72
Summary Messages
10.
Msg: CPE (STATION SET) BAD OR INVALID

This message indicates that the CPE (station set) has been taken out of
service because it is defective or invalid for an ISDN line.
11.
Msg: CPE (T-INTERFACE) BAD

This message indicates that the channel is out of service because the Tinterface (line between the NT1 and CPE) is down. If this is a multipoint
line, all CPEs are inactive. This message is a result of information obtained
from the NT1. All U-interfaces (between line card and NT1) are up.
12.
Msg: CRAFT ACTION

Maintenance craft have removed the line from service for testing or repair.
13.
Msg: CUST PREM EQUIP BAD

Either the customer's terminal, wiring or NT1 is defective.
14.
Msg: CUST PREM EQUIP IN TEST MODE

The customer is doing a test on their NT1.
15.
Msg: CUST PREM EQUIP SUSPECT

The customer's terminal, wiring or NT1 could be defective but test data is
inconclusive.
16.
Msg: DENIED CPE

This CPE is being denied service because it is over and above the number
subscribed. For example, the customer has subscribed for an ISDN line for
four PDNs and tries to hook up five. The fifth CPE would be DENIED. This
status applies to ISDN lines only.
Summary Messages
17.
Msg: DENIED/RESTRICTED SERVICE - MIXED

This message indicates that there are different types of restricted services
on the OE, PDN, or DN. The services may either be DENIED or ON
INTERCEPT. For example, if the service is on INTERCEPT then the
incoming calls can be received. If the service is DENIED TERMINATING
then only outgoing calls can be made. Other services may be completely
DENIED, then the line is temporally out of service.
18.
Msg: DIGITAL ANALYSIS REQUIRED

This message indicates that additional testing is required to reach a
conclusion.
19.
Msg: DIGITAL TEST BUSY

This message indicates that the digital test requested was not run because
the line is busy. Wait and retry.
20.
Msg: DIGITAL TEST MARGINAL

The loopback test may find that the line is marginal, therefore, a test longer
than 16 seconds is necessary.
21.
Msg: DN NOT IN SWITCH DATABASE

The switch has no record of this directory number in its database.
22.
Msg: FURTHER TEST REQUIRED

Digital loopback tests have been inconclusive. More testing is necessary to
isolate the problem.
7-74
Summary Messages

23.
Msg: INCOMPATIBLE VERSIONS

The software generics running on the switch and on the LoopCare
processor are not compatible. Contact your data center.
24.
Msg: INVALID COMMAND

The command that was entered is not valid in this environment. Make
certain that you entered it on the correct mask. Also, certain LoopCare/
ISDN commands are not valid on POTS lines and some POTS commands
are not valid on ISDN lines.
25.
Msg: INVALID DN - EXTRA DIGITS REQUIRED

The telephone number that was entered didn't contain enough digits.
26.
Msg: INVALID REQUEST FOR TDSL

This message indicates that the test requested cannot be run on a TDSL.
Examples are metallic tests and PML1.
27.
Msg: ISTF UNAVAILABLE

No Integrated Services Test Facilities (ISTFs) were available to do
loopback testing. ISTFs were either busy or out of service.
28.
Msg: LAYER 1 PROBLEM

A problem has been found in the physical layer of the digital subscriber
line. Suspect a problem in the wiring or the hardware at either end of the
line.
29.
Msg: OEN NOT IN SW DATABASE

The switch has no record of this office equipment number in its database.
Summary Messages
30.
Msg: LAYER 3 PROBLEM

The line is out of service because of a high rate of level 3 protocol
problems in the Q.931 signaling process. Either one CPE is responsible for
generating the maximum number of PERs or the problem is found
uniformly among all the users.
31.
Msg: LCEN NOT IN SW DATABASE

The switch has no record of this Line Card Equipment Number in its
database.
32.
Msg: LINE CARD BAD

The Switch Line Card for this line is defective.
33.
Msg: LINE CARD SUSPECT

The Switch Line Card for this line could be defective but test data is
inconclusive.
34.
Msg: LINE IN SERVICE

This message appears when LoopCare/ISDN detects that the line is in
service, however, further testing may be required depending on the
customers trouble report.
35.
Msg: LINE RECORD SHOWS TERM MISMATCH

This message appears when LoopCare/ISDN detects a mismatch between
the type of NT1 indicated in the line record (ANSI or AMI) and the type of
NT1 detected via LoopCare/ISDN testing. This message can only be
returned for a 5ESS with LTS, MDF, and ISLU_U. If a 5ESS with a DCTU is
used, the DCTU information will override the line record information.
36.
7-76
Msg: LOOP BAD
Summary Messages

This indicates that a digital loopback to the NT1 failed but a digital loopback
passed at either the line card or RT channel unit. The fault is therefore
between the two.
37.
Msg: LOOP SUSPECT

This message is returned for an out of service TDSL where a digital test
was not run to the CPE due to unknown CPE type and a digital test to the
line card passed. A metallic test is not possible on a TDSL.
38.
Msg: NO 5ESS LINE CARD

Testing cannot be done because the Line Card for this line is not installed.
39.
Msg: NO CPE STATUS AVAILABLE

The switch cannot identify this PDN because the CPE did not successfully
initialize. This will occur when the CPE is not able to identify itself to the
switch, such as a terminal mismatch (STANDARD interface, CUSTOM
CPE).
40.
Msg: NO PERS FOUND

This message will appear when no protocol error records were received
from the PDN, or if a terminal mismatch occurs (STANDARD interface,
CUSTOM CPE).
41.
Msg: NOT AN ISDN LINE

The request entered is an ISDN only type request. However, the switch
cannot verify that the line is ISDN or has determined that the line is POTs.
42.
Msg: NOT PRIMARY DN

The DN (TN) that was entered was not a primary DN. Testing can only be
done on primary DNs.
Summary Messages
43.
Msg: NT1 BAD

The customer's NT1 is either defective or un-powered. Make certain that
the customer's NT1 is powered.
44.
Msg: NT1 FOUND

If the digital loopback passes to the NT1, this message will be shown along
with the signature found by the metallic test. The user must be made aware
that although the digital test passed to the NT1 which proved that there is
an NT1 out there, there could also be a short out there within the NT1
range.
45.
Msg: NT1 POWER SUPPLY BAD

The NT1 has returned a message indicating that either its primary or
secondary power has failed. Have the customer check their NT1 power
supply. It may have lost AC power and is now working from its secondary
(battery) power supply.
46.
Msg: NT1 PRIMARY POWER FAIL

The NT1 has returned a message indicating that its primary power has
failed. It is working now on its secondary power supply which is usually a
battery. Have the customer check the AC power to his NT1 power supply. If
the problem is not fixed soon, the battery will discharge and service will be
lost.
47.
Msg: NT1 SENT DYING GASP

The NT1 has lost both primary and secondary power and can no longer
operate. Before it completely lost power, it sent a message that it was
going down due to loss of power.
48.
Msg: NT1 SUSPECT

The NT1 could be defective but test data is inconclusive.
7-78
Summary Messages
49.
Msg: OE MISMATCH
The Office Equipment Number (OE) in the LoopCare database does not
match the OE in the switch's database for the given PDN. The customer
may have moved his terminal to another DSL.
50.
Msg: POSSIBLE CO-WIRING ERROR

Wiring problems in the Central Office are suspected. Trouble could also be
in the Line Card or in the CO Channel Unit in a universal digital loop carrier
system.
51.
Msg: POSSIBLE PROTOCOL PROBLEM

Layer 2 or Layer 3 Performance Monitoring counters indicate problems
with protocols.
52.
Msg: PROBABLE NT1 COULD BE LOOP

The NT1 is probably defective but test data is not conclusive. The problem
could be in the loop.
53.
Msg: PROTOCOL HANDLER SUSPECT

Digital loopback testing was not successful probably because of a problem
in a protocol handler. Have switch diagnostics run on all protocol handlers
associated with the line under test.
54.
Msg: RT CU BAD
Digital loopback testing has isolated a defective Channel Unit in the
Remote Terminal of a digital loop carrier system.
55.
Msg: RT CU SUSPECT
Summary Messages
Digital loopback testing has partially isolated a defective Channel Unit in
the Remote Terminal of a digital loop carrier system but test results were
inconclusive.
56.
Msg: SECTIONALIZE WITH LONGER LPBK

The longest time that LoopCare/ISDN runs an automatic loopback test on a
DSL is 100 seconds. Test results show that this time is insufficient to prove
that the line is working properly. The loopback should be repeated for a
longer time (e.g. 5 minutes).
57.
Msg: SWITCH COMMON EQUIP BAD

There is a problem with the switching equipment common to a number
lines. Have switch diagnostics run to isolate the problem.
58.
Msg: SWITCH EQUIP NOT AVAILABLE

Some resource in the switch was not available to complete the requested
action. The request was canceled.
59.
Msg: SWITCH INTERNAL ERROR

The switch was unable to perform the requested function because of some
internal problem. If this message appears often, report it to your LoopCare
facilities manager or to the Switching Control Center.
60.
Msg: SWITCH OVERFLOW

Access to a switch resource was blocked because all paths to that
resource were either busy or out of service. Try again later.
61.
7-80
Msg: T-INTERFACE HAS PROBLEM
Summary Messages

The portion of the customer's ISDN loop between their NT1 and terminals
has a problem. The trouble could also be in one of the terminals or in the
NT1. For systems having NT1s integrated in the terminal, the problem is
surely in the terminal.
62.
Msg: T1 FACILITY BAD

For ISDN lines having digital carrier facilities, the digital carrier portion of
the link is bad or improperly provisioned. This message applies to all carrier
facilities (T1, Optical, Radio etc.).
63.
Msg: TERMINATION MISMATCH

Termination mismatch occurs when an AMI line card is connected to a DSL
that is terminated by an ANSI NT1 or vice versa. In the SLC case, a
mismatch can occur between the line card and the channel unit and the
NT1, or any combination of the two.
64.
Msg: TEST OK NOW

Switch data (service status and/or performance monitoring data) indicate
that the line under test has had problems in the past but all digital and
metallic test results are now OK. Suspect a transient problem. You may
want to test the line again during the busy hour when interference from
other lines may be greater. This line may also be a candidate for long term
protocol monitoring.
65.
Msg: TEST OK PARTIAL TEST DONE

All tests that were done indicated that the ISDN line was OK. Some tests
(either metallic or digital) could not be done for some reason. For example,
digital tests could be done on an idle B channel but metallic tests could not
be done because the customer was using their other B and D channels.
Full results may be obtained by testing the line later.
66.
Msg: TEST SESSION FAILURE

A problem has occurred from which the test system could not recover and
testing was stopped. Report this problem to your LoopCare Administrator.
Summary Messages
67.
Msg: UNEQUIPPED COMMAND

The requested command is not available on this system. Verify that you
have entered the request correctly. If the command has worked before, call
your LoopCare Administrator.
68.
Msg: AMI LC - ANSI NT1

This message appears when both Feature Package One and Feature
Package Two are turned on and LoopCare detects an ANSI NT1 on a line
which has an AMI line card. This message is valid only on 5ESS Switches
with a Directly Connected Test Unit (DCTU), at this time.
69.
Msg: AMI LC - POSSIBLE ANSI COT CU

Package Two are turned on and LoopCare detects an ANSI BRITE
channel unit on a line that has an AMI line card. In this case, the ANSI
channel unit does not provide metallic bypass to the NT1, so NT1
classification is not possible. The inability to gain metallic access would
normally trigger a VER IC as well. If a mismatch is detected, VER IC will
not be displayed and VER IV will predominate. Typically, the combination
of two or more VER codes causes VER 99 to occur.
70.
Msg: ANSI LC - AMI NT1

Package Two are turned on and LoopCare detects an AMI NT1 on a line
which has an ANSI line card. This message is valid only on 5ESS Switches
with a DCTU, at this time.
71.
Msg: ANSI LC - POSSIBLE AMI COT CU

Package Two are turned on and LoopCare detects an AMI BRITE channel
unit on a line that has an ANSI line card. In this case, the AMI channel unit
does not provide metallic bypass to the NT1, so NT1 classification is not
possible. The inability to gain metallic access would normally trigger a VER
7-82
Summary Messages

IC as well. If a mismatch is detected, VER IC will not be displayed and VER
IV will predominate. Typically, the combination of two or more VER codes
causes VER 99 to occur.
72.
Msg: AT&T AMI NT1 DETECTED

This message will be displayed when an AMI NT1 is detected on a line
served by a non 5ESS ISDN switch.
73.
Msg: CANNOT VERIFY SWITCH ATTRIBUTES

This will be used for the non 5ESS cases. LoopCare will not be able to
confirm line card type, or if the line is truly an ISDN line since no digital
interface to the non 5ESS switch exists.
74.
Msg: CHANNEL PROVISIONED FOR 56R

A digital carrier system channel used for ISDN service is provisioned for 56
Kbit Restricted service. Channels used for ISDN service must be
provisioned for 64 Kbit Clear service. Have carrier maintenance personnel
provision the carrier system correctly.
75.
Msg: CHANNEL PROVISIONED FOR 64R

A digital carrier system channel used for ISDN service is provisioned for 64
Kbit Restricted service. Channels used for ISDN service must be
provisioned for 64 Kbit Clear service. Have carrier maintenance personnel
provision the carrier system correctly.
76.
Msg: CO-WIRING SPAN L1 PM BAD

Layer 1 Performance Monitoring Data indicates that there are problems in
the portion of the ISDN line between the switch Line Card and the CO
Channel Unit of a universal carrier system. The CO wiring, Line Card or
Channel Unit could be defective.
Summary Messages
77.
Msg: COULD BE CO-WIRING

Problem could be in the wiring in the CO.
78.
Msg: COULD BE COT CU

Problem could be in the CO Channel Unit of a universal digital carrier
system.
79.
Msg: COULD BE CUST PREM EQUIP

Problem could be in the customer's terminal(s), inside wiring or NT1.
80.
Msg: COULD BE CUSTOMER LOOP

Problem could be in the wiring between the customer's terminal and NT1 or
between the customer's terminal an a T-interface Line Card.
81.
Msg: COULD BE LINE CARD

Problem could be in the switch Line Card.
82.
Msg: COULD BE NT1

Problem could be in the customer's NT1.
83.
Msg: COULD BE RT CU
Problem could be in the Channel Unit at the Remote Terminal of a digital
loop carrier system.
84.
Msg: COULD BE T-INTERFACE

Problem could be in the wiring between the customer's terminal and NT1 or
in the terminal or the NT1.
7-84
Summary Messages
85.
Msg: COULD BE T1 FACILITY

In ISDN lines having digital carrier facilities, the digital carrier portion of the
link is suspect. This message applies to all carrier facilities (T1, Optical,
Radio etc.).
86.
Msg: COULD BE TDSL LOOP

Problem could be in the 4-wire loop between a T-interface Line Card and
the customer's terminal.
87.
Msg: COULD NOT COMPLETE METALLIC TEST

The metallic testing algorithm could not be completed for some reason.
88.
Msg: COULD NOT GAIN METALLIC ACCESS

Metallic access could not be obtained because the loop was busy.
89.
Msg: CPE GENERATING ERRORS

Performance Monitoring counters show that the Customer's equipment is
generating Layer 2 or Layer 3 protocol errors.
90.
Msg: CPE IS OUT OF SERVICE

The customer's equipment has been removed from service by the CO
switch.
91.
Msg: CPE LOOPBACK NOT DONE - NON FIT

LoopCare/ISDN will loopback to a CPE only when it can be determined that
the CPE is a Fully Initializing Terminal. If line spec information indicates
that a CPE is non-fit, CPE loopbacks will not be done.
Summary Messages
92.
Msg: CPE REQUESTED OUT OF SERVICE

The CPE is out of service, this condition was requested by the user rather
than by the switch.
93.
Msg: CUSTOMER LOOP SPAN L1 PM BAD

Layer 1 Performance Monitoring counters indicate problems in the portion
of the ISDN loop between the Remote Terminal of a digital carrier system
and the customer's NT1.
94.
Msg: DIGITAL AND METALLIC TEST OK

All tests done on the ISDN line (both metallic and digital) showed the line to
be good.
95.
Msg: DIGITAL TEST BUSY

This message indicates that the digital test requested was not run because
the line is busy. Wait and retry.
96.
Msg: DIGITAL TEST OK

All digital tests showed the ISDN line to be good.
97.
Msg: DLCS CONFIGURATION MISMATCH

Either the line record indicated that there was no digital carrier channel unit
on the DSL under test, but one was found; or the line record indicated that
a channel unit was attached to the line, but none was found.
98.
Msg: DSL IN SERVICE

The switch data shows that the DSL is in service.
7-86
Summary Messages
99.
Msg: DSL OOS LAYER 1

The switch has removed the DSL from service because of a Layer 1
(physical layer) problem.
100.
Msg: DSL OOS LAYER 1 ALL TEST OK

(physical layer) problem, however, testing has found no problems.
101.

The switch has removed the DSL from service because of a Layer 2 (data
link layer) problem.
102.
Msg: DSL OOS LAYER 2 ALL TEST OK

The switch has removed the DSL from service because of a Layer 2 (data
link layer) problem, however, testing has found no problems.
103.

(network layer) problem.
104.
Msg: DSL OUT OF SERVICE

The switch has removed the DSL from service.
105.
Msg: ERROR IN LINE RECORD

This message appears when there is a discrepancy between the line
record and the switch. In this case, the switch indicates POTS and the line
record indicates ISDN.
Summary Messages
106.
Msg: FURTHER DIGITAL ANALYSIS REQUIRED

This message indicates that additional testing is required to reach a
conclusion.
107.
Msg: FURTHER PER ANALYSIS REQUIRED

The analysis of Protocol Error Records for the ISDN line could not isolate a
unique problem. A Protocol Expert must examine the PER data.
108.
Msg: INVALID OVERRIDE FOR SWITCH TYPE

This message will be used to indicate that the overrides entered for a non
5ESS switch type are not supported by the switch either due to the non
existing digital interface or the switch capability.
109.
Msg: INVALID REQUEST FOR SWITCH TYPE

This message is used to indicate that the request entered is not supported
by the switch. In particular, any digital type requests such as DIG, PML2,
STATUS, LINESP, will be considered an invalid request for a non 5ESS
ISDN switch. The FULL or LOOP requests are the only valid requests for
non 5ESS ISDN switches. The full array of POTS requests will work for non
5ESS switches if the line is not an ISDN line and is indicated as such in the
line record.
110.
Msg: ISLU BAD

The Integrated Services Line Unit common equipment in the switch is bad.
Have switch diagnostics run to isolate the problem.
111.
Msg: ISTF BAD

The Integrated Services Test Facility is bad. Have switch diagnostics run to
isolate the problem.
7-88
Summary Messages

112.
Msg: LAYER 1 PM COUNT BAD

Layer 1 Performance Monitoring counters have exceeded their threshold
for bad ISDN line performance.
113.
Msg: LAYER 1 PM COUNT CORRUPT

The Layer 1 Performance Monitoring Counters have been corrupted. They
may contain additional counts due to testing activities or they may contain
fewer counts because they were either cleared or suspended for some
time.
114.
Msg: LAYER 1 PM COUNT GOOD

The Layer 1 Performance Monitoring Counters show no problems.
115.
Msg: LAYER 2 PM COUNT BAD

The Layer 2 Performance Monitoring Counters have exceeded their
threshold for bad ISDN line performance.
116.
Msg: LAYER 2 PM GOOD

The Layer 2 Performance Monitoring Counters indicate no problems.
117.
Msg: LAYER 2 PM SHOWS HIGH CRC ERRORS

The Layer 2 Performance Monitoring Counters indicate an unusually high
number of CRC violations.
118.
Msg: LAYER 2 PM SHOWS PERS EXIST

The Layer 2 Performance Monitoring Counters indicate that some Protocol
Error Records have been received.
Summary Messages
119.
Msg: LAYER 2 PM SHOWS UNEXPECTED MESSAGES

The Layer 2 Performance Monitoring Counters indicate that some
unexpected messages were received on this line.
120.
Msg: LAYER 3 COUNT BAD

The Layer 3 Performance Monitoring Counters have exceeded their
threshold for bad ISDN line performance.
121.
Msg: LAYER 3 PM GOOD

The Layer 3 Performance Monitoring Counters indicate no problems.
122.
Msg: LAYER 3 PM SHOWS PERS EXIST

The Layer 3 Performance Monitoring Counters indicate that some Protocol
Error Records have been received.
123.
Msg: LINE CARD AND COT MISMATCH

The termination signature of the CO Channel Unit of a universal digital
carrier system that is seen by LoopCare or the switch equipment does not
match the type of switch Line Card in use. AT&T offers both pre-standard
ISDN equipment (called AMI) and standard equipment (called ANSI). AMI
and ANSI equipment will not work together. When this problem occurs,
either the Channel Unit or the switch Line Card must be changed so that
both are either AMI or ANSI.
124.
Msg: LINE CARD AND NEAREST TERM MISMATCH

The termination signature seen by LoopCare or the switch equipment does
not match the type of switch Line Card in use. AT&T offers both prestandard ISDN equipment (called AMI) and standard equipment (called
ANSI). AMI and ANSI equipment will not work together. When this problem
occurs, either the nearest terminal equipment or the switch Line Card must
be changed so that both are either AMI or ANSI.
7-90
Summary Messages

125.
Msg: LINE CARD AND NT1 MISMATCH

The NT1 termination signature seen by LoopCare or the switch equipment
does not match the type of switch Line Card in use. AT&T offers both prestandard ISDN equipment (called AMI) and standard equipment (called
occurs, either the customer's NT1 or the switch Line Card must be
changed so that both are either AMI or ANSI.
126.
Msg: LINE IS OUT OF SERVICE

The switch has removed the line from service.
127.
Msg: LINE OUT OF SERVICE

The switch has removed the line from service.
128.
Msg: LINE RECORD INDICATES TERM MISMATCH

This message appears when the line record (or override) indicates one
type of NT1 and the signature is of a different type. Quite possibly the line
record is wrong, but for LTS testing pre-FP3, this is the only information we
have to indicate a mismatch. This message appears for the following
cases:
FP1 on; T91 in line record or override; AMI NT1 detected.
FP2 on; T90 in line record or override; ANSI NT1 detected.
In either case, there would also be another summary message indicating

the NT1 signature. If a DCTU is used for testing and the information from
the DCTU disagrees with the line record or override, ignore the line record
or override information and use the DCTU information.
129.
Msg: LINK REMAINS IN DSL INIT STATE

The ISDN line cannot be brought up to normal operation. All attempts to
start the line have ended with the link returning to the "DSL INIT" state.
130.
Msg: LINK TRANSITIONING BETWEEN STATES
Summary Messages
The ISDN line cannot be brought up to normal operation.
131.
Msg: LONGER TEST IS NEEDED

The longest time that LoopCare/ISDN runs an automatic loopback test on a
DSL is 100 seconds. Test results show that this time is insufficient to verify
that the line is working properly. The loopback should be repeated for a
longer time (e.g. 5 minutes).
132.
Msg: LOOPBACK PASS AT CO LINE CARD

This message will accompany the message "CPE LOOPBACK NOT
DONE - NON FIT" to indicate that loopbacks were run and passed at the
line card.
133.
Msg: LOOPBACK PASS AT NT1

This message will accompany the message "CPE LOOPBACK NOT
DONE - NON FIT" to indicate that loopbacks were run and passed at the
NT1.
134.
Msg: LPBK PASS AT CO LINE CARD

The loopback test passed at the switch line card. Loopbacks could not be
placed at points closer to the customer's terminal probably because the
loop is a T-DSL.
135.
Msg: LPBK PASS AT NT1

The loopback test passed at the customer's NT1. Loopbacks could not be
placed closer to the customer's terminal probably because a terminal
loopback function is not available.
136.
7-92
Msg: METALLIC TEST INDICATES LC AND NT1 MISMATCH
Summary Messages

The NT1 termination signature seen by LoopCare metallic tests does not
match the type of switch Line Card in use. AT&T offers both pre-standard
ISDN equipment (called AMI) and standard equipment (called ANSI). AMI
and ANSI equipment will not work together. When this problem occurs,
either the customer's NT1 or the switch Line Card must be changed so that
both are either AMI or ANSI.
137.
Msg: METALLIC TEST NOT AVAILABLE - T-DSL

This message signifies that metallic testing is not available for T-DSL. This
is due to the nature of T-DSL and not due to LoopCare.
138.
Msg: METALLIC TEST NOT RUN

Metallic tests were not run on the ISDN line because it was busy or it had a
"protected service" class that prohibited metallic access.
139.
Msg: METALLIC TEST OK

The results of metallic tests show no problems. Digital tests were probably
not done.
140.
Msg: NO PDN AVAILABLE FOR METALLIC ACCESS

The metallic interface needs a PDN to gain metallic access. However,
LoopCare/ISDN allows a transaction to be run by a PDN or OE. If the test
is initiated by an OE and there are no PDNs on that OE we can't use a PDN
to gain metallic access.
141.
Msg: NT1 PRIMARY PWR FAIL

The NT1 has returned a message indicating that its primary power has
failed. It is working now on its secondary power supply which is usually a
battery. Have the customer check the AC power to his NT1 power supply. If
the problem is not fixed soon, the battery will discharge and service will be
lost.
Summary Messages
142.
Msg: NT1 SECONDARY PWR FAIL

The NT1 has returned a message indicating that its secondary power has
failed. It is working OK on its normal AC supply but if AC power is
interrupted, service will be lost. Have the customer check the secondary
power supply (usually a battery) in their NT1 power supply.
143.
Msg: NT1 SENDING TOO MANY ERRORS

The NT1 is not operating normally. The switch has received too many
errors from it and has changed its status to "NTOFN" (NT1 OFF Normal).
144.
Msg: NTT ACCESS MUST BE DROPPED

If there is already an NTT access with a 10 digit number, and MDF access
is requested with the same 10 digit number, then the request should be
blocked.
145.
Msg: ONLY LOGICAL LOOPBACKS DONE

Physical loopbacks could not be performed because LoopCare/ISDN
received a busy indication when a physical loopback was attempted.
146.
Msg: PARTIAL DIGITAL TEST OK

Digital loopback tests did not complete fully probably because the
customer requested service before the test finished. The tests completed
indicate that the loop is OK.
147.
Msg: PERS INDICATE SEVERAL PROBLEMS

The analysis of Protocol Error Records failed to find a correlation between
errors which implies that there is more than one problem on this loop. An
expert analysis of the PERs will probably be necessary.
148.
7-94
Msg: PERS SHOW SEVERAL PROBLEMS
Summary Messages

The analysis of Protocol Error Records was not able to find a correlation
among all the errors indicating a specific problem. This indicates that more
than one problem is occurring for this PDN. Further testing may be
necessary.
149.
Msg: PERS SHOW UNIQUE PROBLEM

The analysis of Protocol Error Records found a correlation among all errors
indicating a specific problem. The data displayed with this message should
be sufficient to permit repair of the problem.
150.
Msg: POSSIBLE BUSY DSL

The switch does not give access to the No Test Trunk (NTT) for the Loop
Testing System (LTS) to test an ISDN line if the DSL or Test Equipment is
busy. When LoopCare does not know the difference, then, this message
will appear on ISDN lines that were tested by LTS.
151.
Msg: POSSIBLE LAYER 2 PROTOCOL PROBLEM

A problem has been found in the Data Link Layer of the Digital Subscriber
Line. If there are no layer 1 PM counts, suspect a Layer 2 protocol problem.
152.
Msg: POSSIBLE LAYER 3 PROTOCOL PROBLEM

The line is out of service because of a high rate of level 3 protocol
problems in the Q.931 signaling process. Either one CPE is responsible for
generating the maximum number of PERs or the problem is found
uniformly among all the users.
153.
Msg: POSSIBLE NON-ANSI NT1

This message is shown only when testing an ISDN line on another vendors
switch and there is no valid ANSI NT1 signature, but:
1.
the signature could be that of another vendors' nonstandard NT1.
2.
the line record or override has T90 or T92.
Summary Messages
This message would most likely accompany a VER Code and message
indicating a fault that might be the result of a non-ANSI NT1.
154.
Msg: POSSIBLE TRANSIENT PROBLEM

Evidence exists (via PM counts or PERs) that there has been a problem on
this line. Tests made during this session (if any) did not indicate a problem.
Test this line again during the busy hour when there is more interference
from other lines.
155.
Msg: PROTOCOL HANDLER BAD

The switch's protocol handler associated with the line under test is
defective. Have switch diagnostics run.
156.
Msg: PSU BAD

Packet Switch Unit is bad.
157.
Msg: RESTORAL FAILED

The RESTORE request was run to attempt to put back in service the lines
being worked on. This message is displayed when the request is
unsuccessful in putting the lines back in service.
158.
Msg: REMAINS IN TRANSITION STATE

The DSL cannot be brought to a normal operating state. It remains in a
transitional state.
159.
Msg: STATUS SHOWS CU HAS PROBLEM

Switch status information indicates that the Channel Unit listed in another
summary message has a problem.
7-96
Summary Messages

160.
Msg: STATUS SHOWS CUST T-INT PROBLEM

Switch status information indicates that there is a problem on the
customer's side of the NT1.
161.
Msg: STATUS SHOWS LINK AFTER COT BAD

For ISDN lines having digital carrier facilities, the digital carrier portion of
the link is bad or improperly provisioned. This message applies to all carrier
facilities (T1, Optical, Radio etc.).
162.
Msg: SW OE DOES NOT MATCH LR OE

The Office Equipment Number (OE) in the LoopCare line record database
does not match the OE in the switch's database for the given PDN. The
customer may have moved his terminal to another DSL.
163.
Msg: SWITCH INDICATES T-DSL LINE CARD

This message is always shown for a T-DSL.
164.
Msg: T-DSL LOOP OR CPE PROBLEM

The problem is either in the customer's terminal equipment or in the Tinterface loop connected directly to it.
165.
Msg: T1 FACILITY L1 PM BAD

Layer 1 Performance Monitoring Data indicates that there are problems in
the portion of the ISDN line that passes over a digital carrier facility.
Suspect common carrier facility problems.
166.
Msg: USE S OR R OVERRIDE

When there is an OE mismatch, the tester can choose whether they want
to test the Switch OE (S Override) or the LoopCare Line Record OE (R
Override).
167.
Msg: USER MANUALLY OUT OF SERVICE
Summary Messages
The customer has manually taken their line out of service for local
maintenance operations. Additional summary messages that don't seem to
be associated with either a B flag or a VER code.
168.
Msg: * LINE RECORD INDICATES ISDN

The line under test is an ISDN line as indicated in the LoopCare line record.
169.
Msg: * LINE RECORD INDICATES NON-ISDN

The line under test is NOT an ISDN line.
170.
Msg: * METALLIC BYPASS NOT ALLOWED

The digital carrier channel unit under test is not capable of establishing a
metallic bypass to the remote end of the link.
171.
Msg: * ON CIRCUIT SWITCHED SERVICE

This message defines the service that the VER code and summary
message applies to.
172.
Msg: * ON DEMAND PACKET B SERVICE

message applies to.
173.
Msg: * PACKET D SERVICE

message applies to.
174.
7-98
Msg: * PERMANENT PACKET B SERVICE
Summary Messages

message applies to.
175.
Msg: * SWITCH INDICATES NON-ISDN

The switch's database indicates that the line under test is NOT an ISDN
line.
176.
Msg: BUSY ISDN LOOP - CANNOT TEST

It was determined that the loop to be tested is busy. Metallic access to busy
ISDN lines is NOT allowed.
177.
Msg: INVALID REQUEST FOR ISDN LINE

The test requested is intended for POTS lines only and cannot be done on
an ISDN line.
178.
Msg: INVALID TERM FOR ISDN LINE

The termination seen by metallic testing does not match any known ISDN
signature.
179.
Msg: ISDN TERMINATION ERROR

A valid ISDN termination was seen by metallic tests but there is something
wrong with it.
180.
Msg: ISDN TERMINATION MISMATCH

The NT1 termination signature seen by LoopCare or the switch equipment
does not match the type of switch Line Card in use. AT&T offers both prestandard ISDN equipment (called AMI) and standard equipment (called
occurs, either the customer's NT1 or the switch Line Card must be
changed so that both are either AMI or ANSI.
Summary Messages
181.
Msg: LINE RECORD INDICATES ISDN

The line under test is an ISDN line as indicated in the LoopCare line record.
182.
Msg: LOOPCARE TEST ON ISDN - RESULTS SUSPECT

LoopCare test equipment was used to test an ISDN line even though it is
not capable of recognizing ISDN terminations. The results can be used but
could be misleading.
183.
Msg: POSSIBLE AMI BRITE DETECTED

An ISDN AMI (BRITE) CO Channel Unit was detected by metallic tests.
Since the BRITE unit looks like a 4 K Ohm Tip-Ring (T-R) short to
LoopCare, the resistance seen could be a real short and not a BRITE unit.
184.
Msg: RINGER COUNT NOT DONE - ISDN LINE

ISDN lines do not have ringers so this test is not done.
185.
Msg: SWITCH INDICATES ISDN SERVICE

Data from the switch indicates that the line under test is an ISDN line.
186.
Msg: SWITCH INDICATES NON-ISDN SERVICE

Data from the switch indicates that the line under test is NOT an ISDN line.
187.
Msg: UNEXPECTED ISDN TERMINATION

The line under test was thought to be a POTS line but the loop termination
signature looks like an ISDN NT1.
7-100
Summary Messages

188.
Msg: VALID AMI NT1 SIGNATURE

This message is used any time FP1 is on and LoopCare recognizes an
AMI NT1 on 5ESS Switch.
189.
Msg: VALID ANSI NT1 SIGNATURE

This message is used any time FP2 is on and LoopCare recognizes an
ANSI NT1 on a line on a 5ESS or other vendor's digital switch.
190.
Msg: VALID NT1 SIGNATURE

The NT1 termination signature measured by LoopCare is valid.
191.
Msg: WIRING ERROR - NT1 REVERSED

An AMI NT1 was installed with its input leads reversed.
192.
Msg: SWITCH INDICATES IDLC

The switch has identified the line as IDLC, but it is not indicated as such in
the line records, or line records do not exist.
Summary Messages

Summary Messages
1.
Msg. DO LCOILX TEST TO LOCATE COILS

A load coil was detected during a LOOP or FULL request on a XDSL line. It
is suggested that the LCOILX request be performed to locate the coils(s).
2.
Msg. DOUBLE LOAD DETECTED = ***MH

The measured section length was greater or less than 12%.of twice the
section length threshold.
3.
Msg. END SECTION TOO LONG = ***FT

A measured section length value was 12% above or below the loaded
4.
Msg. * IMPLIES ZERO COILS ON LINE

The load coil test was not performed, because a condition was detected,
such as the presence of an ATU-R, that implies there are no load coils.
5.
Msg. INCORRECT LOAD COIL SECTION DETECTED = ***FT

A measured section length value was 12% above or below the loaded
6.
Msg. INCORRECT LOAD COIL DETECTED = ***MH

A measured load coil value was 25% above or below the load coil
threshold.
7.
Msg. INCORRECT NUMBER OF LOADS

The number of loads detected did not equal the #LOADS threshold for an
acceptance scan.
7-102
Summary Messages
8.
Msg. LOAD COIL DETECTED

A load coil was detected during a LOOP or FULL request on a XDSL line.
9.
Msg.LOAD COIL DETECTION INDETERMINATE

It was not possible to determine whether or not a load coil was present.
10.
Msg. LOAD COIL is XXXXX ft FROM RT

When a load coil is detected by an LCOILX request using a DWN, the
distance of the first load coil from the Remote Terminal is given in feet.
11.
Msg. LOAD COIL TESTS NOT DONE

The load coil detection test was not run as part of a wideband LOOP or
FULL request due to faults found on the line.
12.
Msg: LOAD COILS DETECTED - ?

When a DCOILX or a LCOILX test request is made and load coil(s) were
detected on the line. Where the ? is, if there were no load coils detected
after the DCOILX test, the number before the message will be zero. If there
were load coils detected, this area will be populated with the number of
load coils on the line.
13.
Msg. LOAD COILS DETECTED - NOT COUNTED

Load coils were detected in the loop under test but the number of load coils
present in the loop could not be determined.
14.
Msg. * LOAD COIL VALUE *** IN QUESTION

The indicated load coil value has been determined to be a problem.
Summary Messages
15.
Msg. LOCATION OF COILS NOT DETERMINED

This message is displayed when an LCOILX test request is made and the
test head is not able to determine the location of load coils it has detected.
LoopCare returns the count of load coils detected on a separate line but
does not return the locations. The location fields are left blank on the TV
Mask.
16.
Msg. MCU FOUND BY LOAD COIL DETECT

A metallic channel unit was detected to be present in the test path of the
loop under test. Load coil detection is possible when an EMU test head and
a metallic channel unit is present in the test path.
17.
Msg. MISSING LOAD DETECTED = ***FT

The number of loads detected did not equal the #LOADS threshold for an
acceptance scan.
18.
Msg. * SECTION *** IN QUESTION

The indicated section is where a load coil problem was detected.
19.
Msg. TEST EQUIPMENT CANT TEST LOAD COILS

The test equipment that has been assigned to the loop under test does not
have the capability of detecting load coils.
7-104
Summary Messages
Local Number Portability (LNP)

Summary Messages
Summary Messages
1.
Msg: DUPLICATE NNX-EXK IN DATABASE

This message accompanies VER E7 - TEST SYSTEM ERROR and
indicates that LoopCare could not test the line because the LNP R1 feature
is not enabled and the NNX-EXK is not unique in the database. Verify that
the LNP R1 feature file has been installed. Refer to the LoopCare
Installation Guide, LNP Installation.
2.
Msg: EXK/LRN REQUIRED FOR PORTED NUMBER

This message accompanies VER NK - LINE RECORD ERROR and
indicates that LoopCare could not test the line because a valid LRN or EXK
has not been received in the line record. Enter the LRN/EXK on the
LoopCare GUI to test the line.
3.
Msg: LINE NOT SERVED BY <COMPANY NAME>

An LRN and an SPID were successfully retrieved from the LRN Server, and
LoopCare checked the SPID table. The value of the SPID ID was C (=
CLEC). LoopCare stopped testing and returned the VER NT code and
summary message.
NOTE:
If the Display Message field is checked in the OAM SPID form, Messages 1
and 2 specified on that form are displayed.
4.
Msg: LINE RECORD INDICATES NOT-IN-SERVICE

This message accompanies VER NT - LINE IS NOT MLT TESTABLE. The
line could not be tested by LoopCare because the line record indicates a
number not in service. Enter the OE/LRN/EXK on the LoopCare GUI to test
the line.
5.
Msg: LINE RECORD INDICATES PORTED-OUT

This message accompanies VER NT - LINE IS NOT MLT TESTABLE. The
line could not be tested by LoopCare because the line record indicates a
ported-out number. Enter the OE/LRN/EXK on the LoopCare GUI to test
the line.
6.
Msg: NO TESTING AVAILABLE

CLEC owned) or N (= ILEC owned and not LoopCare tested). LoopCare
stopped testing and returned the VER NT code and summary message.
Summary Messages
7.
Msg: OVRD-EXK/NNX COMBO DUPLICATED IN DATABASE

An override exchange key was entered on the test request but LoopCare
determined that the NPA-NNX was duplicated in the database, and the
Local Number Portability feature was not enabled. Verify that the LNP R1
feature file has been installed.
8.
Msg: PORTED NUMBER TESTING INACTIVE

This message accompanies VER E7 - TEST SYSTEM ERROR and
indicates that LoopCare could not test the line because the line record
indicates a ported-in number and the switch identified has ported number
testing inactive. Use ADEF to turn ported number testing on for this switch.
9.
Msg: TEST WAS NOT MADE

CLEC owned) or N (= ILEC owned and not LoopCare tested). LoopCare
stopped testing and returned the VER NT code and summary message.
10.
Msg: TN NOT TESTED BY <COMPANY NAME> LOOPCARE

LoopCare checked the SPID table. The value of the SPID ID was N (=
ILEC owned and not LoopCare tested). LoopCare stopped testing and
returned the VER NT code and summary message.
NOTE:
If the Display Message field is checked on the OAM SPID form, Messages
1 and 2 specified on that form are displayed.
11.
Msg: USE EXK or LRN OVERRIDE TO TEST

This message accompanies VER NT - LINE IS NOT MLT TESTABLE. This
message is displayed along either summary message 3 or 4 when the line
record indicates a ported-out number or number not in service. Enter the
OE, LRN, or EXK override on the LoopCare GUI to test the line.
12.
Msg: VALID OE NEEDED TO TEST PORTED NUMBER

This message accompanies VER NK - LINE RECORD ERROR and
indicates that LoopCare could not test the line because a valid OE has not
been received in the line record. Enter the OE on the LoopCare GUI to test
the line.
7-106
13.
Msg: EXK NOT IN DATABASE
14.
Msg: SWITCHID NOT IN DATABASE
15.
Msg: LRN NOT IN DATABASE
Summary Messages

Message Summary
1.
Msg: RECEIVER-OFF-HOOK OR SHORT
2.
Msg: USE MON AND TALK TRANSACTIONS TO
3.
Msg: LISTEN FOR SPEECH

This message indicates that the telephone receiver is off hook or that there
is an T-R short. (Both possibilities exist because a long loop is involved.)
Use the MON transaction to listen for someone talking on the line; this will
eliminate the possibility of a T-R short.
4.
Msg: CAN'T DO LONG LOOP ANALYSIS
5.
Msg: * DUE TO DC FAULTS ON LINE

This message indicates that the line has a fault of less than 250 kohms on
T-R, T-G, or R-G. A complete long loop analysis cannot be performed until
this fault is repaired.
6.
Msg: ONE SIDE OF LINE IS OPEN OR
7.
Msg: ONE RINGER WIRED TO GROUND OR
8.
Msg: CROSS TO WORKING PAIR

This message indicates that the number of ringers do not match T-G and
R-G; they should, since the line records indicate that this is a single-party
line. The mismatch can be caused by an open on one side or by the ringers
having been wired incorrectly. Also, if a line under test is shorted to a
working pair, LoopCare may be seeing the AC signature of the ringer on
the line to which it is shorted.
9.
Msg: PROBABLE MISWIRED RINGERS OR
10.
Msg: LINE RECORD ERROR
11.
Msg: CHECK SERVICE TYPE

The AC signature does not look like a multiparty line. Either the line records
are incorrect or the ringer is miswired.
12.
Msg: POSSIBLE LONG LOOP

The system suspects that the line being tested is a long loop. This
message suggest that the user runs a long loop transaction.
Summary Messages

Summary Messages
1.
Msg: AMAS CHANNEL OOS

The circuit associated with the number or circuit ID under test is not in
service. This condition could be a caused by the following events:
2.
a.
A switch provisioning problem.
b.
A problem between the switch and the AnyMedia FAST shelf
c.
The Test Access Unit (TAU) within the AMAS may be out of service.
Msg: CU NOT EQUIPPED FOR TEST ACCESS

The equipment in the slot in the LTE (as derived from either the OE if
testing by TN or Slot entry if testing by shelf-slot-line circuit information)
does not support metallic test access.
3.
Msg: DLSAM/RT INTERNAL ERROR

LoopCare received a response from the LTE0 which indicates that an
internal error condition exists within the LTE. Conditions which could cause
this result are:
4.
a.
A Software installation is being performed in the LTE
b.
The LTE is initializing.
c.
There is an unspecified internal error within the LTE.
Msg: LOOK-IN ACCESS ON TAP2

Message displayed when LoopCare has successfully established access
from the DAU 1000. This access is supported only on the Tollgrade
DAU1000 LTE with Version 2 of the TL1 Control Card, which supports
Look-In and TAP 2.
5.
Msg: LTE COMMUNICATION FAILURE

The A TAP2 request has successfully created access from the TAP2 port of
a DAU 1000 to the switch. Access is retained for 30 minutes.
7-108
Summary Messages
6.
Msg: LTE EQUIPMENT BUSY

Resources within the LTE needed to complete the request were busy.
Conditions which could cause this result are:
7.
a.
All TCP/IP ports into the LTE were in use.
b.
The Test Access Path (TAP) was being used by another application
or local craft personnel.
c.
Another user was logged into the LTE using the login/password
assigned to LoopCare.
Msg: LTE LOGIN ERROR

LoopCare failed to login to the LTE. Conditions which could cause this
result are:
8.
a.
Invalid Login/Password information in the LoopCare database for

the given LTE Id.
b.
A communications failure occurred during the login procedure.
Msg: LTE NOT AVAILABLE

No ports are available on the AMS, ASAM or Litespan unit.
9.
Msg: LTE SLOT NOT EQUIPPED

The slot in the LTE (as derived from either the OE if testing by TN or Slot
entry if testing by shelf-slot-line circuit information) is not equipped or has
yet to be assigned.
10.
Msg: NO LOOK-IN ACCESS AVAILABLE

A FULL test was requested, but LoopCare could not perform the Central
Office (CO) portion of the test for one of two reasons:
a.
Test was requested by circuit information and only split, LOOK-OUT

access is allowed.
Summary Messages
b.
7-110
The Channel Unit of the TN under test supports only split, LOOKOUT access.
Summary Messages

Summary Messages
1.
Msg: INTERCEPT
LoopCare found the line to be on intercept. For Crossbar and Step-by-Step
offices this means that LoopCare recognized an LoopCare DC resistance
value of about 35 kilohms on at least two of the sides of the line. For ESS
(POTs line) offices LoopCare recognized intercept by identifying a 480-Hz
intercept tone along with the following DC signature:
> 1000 K T-G
300-800 K R-G
No further tests are made once intercept has been detected. For ESS
ISDN lines the switch informs LoopCare of intercept.
2.
Msg: INTERCEPT - ADD ANALYSIS

Service has been denied for this DSL, however, additional analysis or
further testing is required.
3.
Msg: MDF TESTABLE ONLY

The loop can only be tested by getting an MDF access and running tests
over it. This could happen if there were some equipment on the line that
caused inaccurate test results (Dial Long Lines). Normally, LoopCare will
run the line circuit test and display the results with this message. This
message will be followed by message 3.
4.
Msg: MLT CAN'T TEST THROUGH CO EQPT

This message indicates that some equipment in the central office prevents
LoopCare from testing the loop (Dial Long Lines). It will modify message 2.
5.
Msg: NO METALLIC TEST FACILITY

A test has been performed via a DigiTest EDGE without an MTM.
A DigiTest EDGE without an MTM cannot perform metallic tests.
6.
Msg: NPANXX OVERLAYED OPTION EWUIEWS

The user attempted to enter a SAM command without an option for an
overlaid number.
The omission of an option for the Request is not allowed in this case.
7.
Msg: OFFICE OVERFLOW

The central office switching machine was determined to be busy. No further
tests are made.
8.
Msg: TEST OK
The LoopCare tests do not indicate any faults on the parts of the line that
LoopCare can test (loop, line circuit, dial tone). Trouble still may exist on
parts of the line that LoopCare could not test; for example:
Summary Messages
9.
Problem in the station set
Problem in crossbar line circuit
Noise or transmission problem affecting service
Msg: INVALID THERMISTOR ARRANGEMENT

The thermistor test was made but the arrangement of thermistors was not
what was expected according to the line record information. This could be
the result of a fault or an invalid termination. The thermistor arrangement
will be displayed in the category section of the test results.
10.
Msg: THERMISTOR FOUND- NOT EXPECTED

The thermistor test was run and a thermistor was found. However,
thermistors were not expected for the type of termination indicated by the
line records.
11.
Msg: PBX INWARD SERVICE IDENTIFIED

LoopCare detected a PBX inward service from testing. However, line
records do not indicate an inward service for this line.
12.
Msg: TEST OK - CHANNEL TEST IGNORED

The VER 55-58 Reclassification feature is enabled and a VER 55 58
code has been changed to VER 05. The channel test results are ignored.
Use the V55 override to disable this feature on a per test basis and get the
channel test results.
13.
Msg: TESTED WITHOUT LINE RECORDS

LoopCare has tested the line but did not have line record information.
Therefore, the system could not compare results with the line record
information.
14.
Msg: EXAMINE DETAILED TEST RESULTS
15.
Msg: AND DETERMINE FURTHER ACTION

These messages will appear if there are no other summary messages set
and the VER code is 98. They indicate that one should use the detailed test
results (found in the categories), as well as other information available, to
determine the condition on the line and take action.
16.
Msg: TESTED WITH PARTIAL LINE RECORDS

This message will only appear on the GUI. It indicates that the test was run
but only part of the line record information was available. This can happen
if part of the records were overridden.
17.
Msg: PHYSICAL PAIR TN ON INTERCEPT

This message occurs whenever a physical pair's telephone number is on
intercept. The important thing to remember is that it will occur even when
the trouble report is on the derived telephone number.
7-112
Summary Messages

18.
Msg: SPECIAL SERVICE ACCESS UP

This message appears on the STV mask when you have accessed a "nonlocally switched" line -- a telephone line that does not originate at the local
central office switch -- via the Special Services Access (SSA) transaction.
(If you are trying to access a subscriber line that cannot be accessed via
the SSA transaction, you will receive an error message instead.)
19.
Msg: CPE or HIGH RESISTANCE OPEN

LoopCare did not detect any obvious trouble on the line, however, it did find
either a CPE termination or a high resistance open on the line. In most
cases this will indicate that it is a CPE termination. The remote possibility
exists however, that it could be a high resistance open problem.
20.
Msg:ROH DETECTED DURING TEST

LoopCare detected an off hook condition on a line that tested open.
21.
Msg:USE CO REQ FOR LINE CKT & DIALTONE

LoopCare detected an off hook condition on a line that tested open. Run
the CO test request. If the test fails, dispatch to the CO.
Summary Messages

Maintenance
Termination
Summary Messages
1.
Msg: MAINTENANCE UNIT FOUND ON LINE

LoopCare detects the presence of a Maintenance Termination Unit (MTU)
on the line. The MTU is a piece of equipment placed near the customer's
premises that helps determine the continuity of the line from the CO to the
MTU. For LoopCare-measured faults up to 300 kohms, the MTU will
sectionalize resistive faults to either the customer's premises or the
network. For faults over 300 kohms, the MTU will be detected but
sectionalization will not be done.
2.
Msg: TEST OK MTU

If the results of the test indicated a TEST OK condition, and there is an
MTU detected on the line, and the results are being sent to either the TR,
DMLT, or MSCR mask, then VER code 0M will be set with this summary
message.
3.
Msg: TEST OK CPE/MTU

This message is similar to "TEST OK MTU" except it has been determined
that in addition to the above conditions, the customer is using their own
equipment. Therefore, besides MTU being detected on the line, CPE has
also been detected. This message will appear with VER_MC.
4.
Msg: CANNOT SECTIONALIZE FAULT

LoopCare has detected a fault on a line which contains an MTU. The
location of this fault is not known. This message will follow a message that
says MAINTENANCE UNIT FOUND ON LINE.
7-114
Summary Messages

Summary Messages
1.
Msg: POSSIBLE INTERFACE-TERMINAL MISMATCH

National ISDN has a new interface called STANDARD. When this interface
is being used the CPE TYPE must be SIT. This message will appear when
the BRI CLASS is STANDARD and the CPE TYPE is other than SIT, or
when the BRI CLAS is CUSTOM and the CPE TYPE is SIT.
2.
Msg: STANDARD INTERFACE-CPE NOT TESTED

This message will appear when the interface type is STANDARD
(indicating National ISDN). Loopback test to the CPE can not be performed
for this type of interface.
Summary Messages

Summary Messages
1.
Msg: CIRCUIT IDENTIFIER EXCEEDS MAXIMUM FIELD LENGTH

This message indicates that a test request was submitted containing a
Circuit ID longer than 30 characters.
2.
Msg: DSL CIRCUIT DATA FOR REQUESTED LINE NOT AVAILABLE

FROM NSDB
This message indicates that no line record data is available in NSDB in
response to a test request for a Circuit ID.
3.
Msg: DSL CIRCUIT DATA QUERY TO NSDB FAILED

This message indicates that a circuit data query to NSDB timed out or the
query failed for some other reason.
4.
Msg: INVALID CIRCUIT ID - COMPANY MUST BE UP TO 4

ALPHANUMERICS OR EMPTY
This message indicates that a test request was submitted with a Company
component over the permitted 4 alphanumeric characters.
5.
Msg: INVALID CIRCUIT ID - PREFIX MUST BE UP TO 2 NUMERICS OR

EMPTY
This message indicates that a test request was submitted with a Circuit ID
with a Prefix component over the permitted 2 numeric characters.
6.
Msg: INVALID CIRCUIT ID - SEGMENT MUST BE UP TO 3

with a Segment component over the permitted 3 alphanumeric characters.
7-116
Summary Messages

7.
Msg: INVALID CIRCUIT ID - SERIAL NO MUST BE UP TO 6 NUMERICS

with a Serial Number over the permitted 6 numeric characters.
8.
Msg: INVALID CIRCUIT ID - SUFFIX MUST BE UP TO 3

with the Suffix component over the permitted 3 alphanumeric characters.
9.
Msg: INVALID CIRCUIT ID - SVC CODE/MODIFIER MUST BE UP TO 4

ALPHANUMERICS
with a Service Code and Modifier over the permitted 4 alphanumeric
characters.
10.
Msg: INVALID REQUEST: SPECIFY TN OR CIRCUIT ID BUT NOT BOTH

This message indicates that a test request was submitted with a data in the
TN and Circuit ID fields.
11.
Msg: TESTED WITHOUT LINE RECORD

This message indicates that a test request failed to obtain line record data
from NSDB and LMOS.
Summary Messages

Summary Messages
1.
Msg: OPEN IN
LoopCare has detected an open and determines that it is inside or very
close to the central office. LoopCare stores an offset value for each NNX.
An open condition that occurs within this offset distance is recognized as
an "open in" by LoopCare.
2.
Msg: OPEN OUT NEAR DROP- CAP BAL *** %

LoopCare has detected an open and determines that it is outside the
central office. The open is estimated to be near the drop wire if the
capacitive balance is greater than 97% but less than 99% or if the
capacitive balance is greater than 95% but less than or equal to 97% and
the distance to the telephone is determined to be less than 500 feet. The
capacitive balance value will be displayed with the message.
3.
Msg: OPEN OUT CABLE RING- CAP BAL *** %

central office on the ring side of the line. In addition, the capacitive balance
is such that LoopCare determines the open to be in the cable. The
capacitive balance will be displayed with the message.
4.
Msg: OPEN OUT CABLE TIP- CAP BAL *** %

central office on the tip side of the line. In addition, the capacitive balance is
such that LoopCare determines the open to be in the cable. The capacitive
balance will be displayed with the message.
5.
Msg: OPEN OUT- 2 PTY OR BRIDGE LIFTER

LoopCare has detected an "open out" on a line that has either two-party
service or bridge lifters. This message will be followed by the next
message.
7-118
Summary Messages

6.
Msg: OPEN MEASUREMENTS NOT PERFORMED

Because this line has two-party service or bridge lifters, no distance or
capacitive balance measurements can be made.
7.
Msg: OPEN-CANNOT MEASURE DISTANCE

LoopCare has detected an open but cannot measure the distance because
of a hard-to-moderate short on the line.
8.
Msg: OPEN OUT BALANCED- CAP BAL *** %

LoopCare has detected an "open out" on the line. The capacitive balance is
greater than 99%, which means that the open is balanced. This indicates
that the distances to the open on both sides of the line are fairly equal in
length.
9.
Msg: DISTANCE FROM STATION
****** FT
On opens near the drop and opens in the cable, LoopCare can estimate
the distance of the open from the station. This distance is given in feet.
10.
Msg: DISTANCE FROM C.O. ****** FT

On all open conditions that can display a measurement (drop, cable,
balanced), LoopCare will estimate the distance to the open from the central
office. The estimate is given in feet.
11.
Msg: OPEN OUT: HIGH RESISTANCE

LoopCare has run two AC tests to check for opens. The first is run at 10
volts and the second is run at 60 volts. LoopCare will display this message
if the first test indicates an open, but the second test shows less than 20
kohms T-R (or a missing T-R AC value) and all the DC resistances are
greater than 1000 kohms.
Summary Messages
Basically, a high-resistance open is one where the open may not be a clean
break in the line but only deterioration caused by corrosion. This can cause
intermittent problems to the telephone service. This message also may
appear in cases where LoopCare sees high-resistance ringers or certain
fraud devices on the line.
12.
Msg: OPEN ON PREMISES

LoopCare has identified the presence of a Maintenance Termination Unit
(MTU) on the line and can see that the loop to the MTU is unbroken.
However, it cannot see a telephone on the far side of the MTU. This can be
caused by one of several things: (1) the customer has unplugged the
telephone; (2) the wiring inside the customer's house is bad; or (3) the
phone is connected properly but it is of a type that cannot be seen by
LoopCare (an unusually high-impedance ringer, for example). In all of
these cases, LoopCare is indicating that the wiring from the central office to
the customer is not open; if there is a problem, it is on the customer's
premises.
13.
Msg: * NONSTANDARD TERMINATION

See message 12.
14.
Msg: DISTANCE FROM RT ****** FT

LoopCare has estimated the distance from the remote terminal of a Digital
Loop Carrier System (DLCS) to the open. The estimate is given in feet.
15.
Msg: OPEN IN REMOTE TERMINAL

LoopCare has detected an open and determined that it is inside or very
close to the remote terminal of a DLCS. LoopCare stores a "between-RTcable-length" value and recognizes an open as being in the RT if this value
exceeds the measured loop length.
16.
7-120
Msg: OPEN IN LTE
Summary Messages

LoopCare has detected an open and determined that it is inside or very
close to the LTE under test. LoopCare stores a "between-LTE-cablelength" value and recognizes an open as being in the LTE if this value
exceeds the measured loop length.The default value for the between-LTEcable-length is 880 feet.
17.
Msg: DIST FROM STATION ****** FT

When LoopCare sees an open, it computes the distance from the open to
the central office and the distance from the open to the subscriber (station).
This message shows the latter result (in feet).
18.
Msg: ACCESS DROPPED

LoopCare has detected an "open in" and determined that it is inside or very
close to the central office. If there is test equipment failure during the
calibration process, the access will be dropped. In this case, this summary
message will be displayed, along with numeric results.
19.
Msg: 500 FT. MAX. ERROR IN DISTANCE

LoopCare has detected an "open out" CABLE RING, CABLE TIP, or NEAR
DROP. For tests made by the 5ESS/DCTU, LoopCare dynamically
calibrates the capacitance values of the line units so the "Distance to
Open" measurements are always accurate. Should the dynamic calibration
fail, LoopCare still displays the results to the user and this summary
message is displayed.
20.
Msg: OR OPEN OUT NEAR CO

This message may be displayed as a qualifier for the "OPEN IN" summary.
For tests made by the 5ESS/DCTU, LoopCare dynamically calibrates the
capacitance values of the line units so the "Distance to Open"
measurements are always accurate. This helps avoid false dispatches.
Should the dynamic calibration fail, LoopCare still displays the results to
the user and this summary message is displayed.
21.
Msg:POSSIBLE RT CALIBRATION ERROR
Summary Messages
This message occurs if the DLC calibration feature (#110) is on and
7-122
There is no calibration length in the database.
The distance to station is less than the DLC calibration length.
The distance to open is less than 90% of the DLC calibration length.
Summary Messages
Permanent Signal Release Summary

Messages
Summary Messages
1.
Msg: PERMANENT SIGNAL RELEASED

The LoopCare Permanent Signal Release (PSR) test was successful in
releasing permanent signal in a Step-by-Step office.
2.
Msg: PERMANENT SIGNAL NOT RELEASED

The LoopCare PSR test was not successful in releasing permanent signal
in a Step-by-Step office.
3.
Msg: CAN'T RUN PSR REQUEST

The PSR request was not accepted for one of the reasons listed in the
messages below.
4.
Msg: * NO PERMANENT SIGNAL

The PSR request was not accepted because there was no permanent
signal on the line.
5.
Msg: * MEASUREMENT ERROR

The PSR request was not accepted because of an LoopCare
measurement error. This could be an error in the hardware or possibly a
change in state in the switch.
6.
Msg: CAN'T OBTAIN DC SIGNATURE

The PSR request was not accepted because LoopCare was unable to
make the necessary LoopCare DC resistance and voltage tests for PSR.
7.
Msg: NOT A STEP BY STEP SWITCH

The PSR request was not accepted because the line tested is not served
by a Step-by-Step switch according to the line records.
8.
Msg: EXCESS AC FEMF

The PSR request was not accepted because of excess AC foreign voltage.
Summary Messages

Summary Messages
1.
Msg: CALIBRATION DATA LOADED IN DATABASE

A REF0 request has successfully performed a trunk insertion loss
calibration, which has been loaded into a database record.
2.
Msg: CALIBRATION FAILED

A REF0 request attempting a trunk calibration has been aborted.
3.

* DC RESISTANCE TOO HIGH
A REF0 test request was aborted because the DC resistance of the test
path was too high.
4.

* EXCESS FOREIGN VOLTAGE
A REF0 test request was aborted because a foreign voltage was detected
by the request.
5.

* FAULT FOUND ON LINE
A REF0 test request was aborted because a fault was detected on the line.
6.

* NO LIL CALIBRATION MODULE DETECTED
A REF0 test request was aborted because the LIL-CM was not detected.
7-124
Summary Messages
Remote Measurement Unit (RMU)

Summary Messages
Summary Messages
1.
Msg: ILLEGAL TRANSACTION FOR RMU

The transaction requested is one that the RMU currently does not support.
The RMU is either not capable of doing this transaction or it makes no
sense to do it at the Remote Terminal end of a Digital Loop Carrier System
after the bypass path is set up. An example of this is requesting a FULL
transaction followed by a CO request. This is illegal, since you can't look
back into the CO after a bypass is set up.
2.
Msg: METALLIC ACCESS NOT ALLOWED WITH CALLBACK PRESENT

When the Remote Terminal end of a Digital Loop Carrier System is tested
by an RMU, there are two possible ways to set up a callback path. If a
RING, TALK, or MONITOR request is entered before a FULL or LOOP
request, a callback path will be set up from the Loop Testing System (LTS).
If the request is made after the FULL or LOOP request, the callback path
will be established from the RMU.
The above message is displayed when you have a callback path set up to
an LTS and then you request a FULL or LOOP transaction. You have to
drop the LTS callback (XCB), do the FULL or LOOP transaction to get
metallic bypass, and then reestablish the callback through the RMU with
the RING, TALK, or MONITOR request.
3.
Msg: REMOTE EAIU - RUN FULL OR LOOP FIRST

This message is displayed when an initial MON test is attempted on an
RMU to test an idle EAIU-supported line.
4.
Msg: RUN XCB REQUEST TO DROP CALLBACK BEFORE FULL OR

LOOP
This message usually appears with message 2 above.
5.
Msg: USE FULL OR LOOP TO GET MET ACCESS

This message occurs with Ver Code XN - REQUEST NOT ALLOWED IN
THIS MODE, when an invalid initial request is attempted for an RMU
testing EAIU-supported lines. Run a FULL or LOOP request first; then run
the blocked request.
Summary Messages

Summary Messages
1.
Msg: MDF TEST RECOMMENDED

A very low LoopCare DC resistance was detected and LoopCare cannot
determine whether the fault is in or out of the central office. An MDF test is
recommended to sectionalize the trouble in or out.
The following messages indicate the relative severity of the low resistance
condition on the line. There are five general severity levels which are
determined by the LoopCare DC resistance value. These categories and
the LoopCare DC resistance values that set them are shown below.
Category
DC Resistance
Very Light
<1000 & 500 K
Light
>300 & <= 500 K
Moderate
> 150 <= 300 K
Hard
>5 & <= 150 K
Very Hard
<= 5 K
If the low resistance is between tip and ring, one of the following messages
will be displayed:
2.
Msg: VERY LIGHT SHORT T-R
3.
Msg: LIGHT SHORT T-R
4.
Msg: MODERATE SHORT T-R
5.
Msg: HARD SHORT T-R
6.
Msg: VERY HARD SHORT T-R

If the low resistance is tip-to-ground, one of the following messages will be
displayed:
7.
Msg: VERY LIGHT GROUND T-G
8.
Msg: LIGHT GROUND T-G
9.
Msg: MODERATE GROUND T-G
10.
Msg: HARD GROUND T-G
11.
Msg: VERY HARD GROUND T-G

If the low resistance is ring-to-ground, one of the following messages will
be displayed:
(last mod 12/6/90)
12.
7-126
Msg: VERY LIGHT GROUND R-G
Summary Messages

13.
Msg: LIGHT GROUND R-G
14.
Msg: MODERATE GROUND R-G
15.
Msg: HARD GROUND R-G
16.
Msg: VERY HARD GROUND R-G
17.
Msg: SWINGING TROUBLE

If the DC resistance tip-to-ground or ring-to-ground is between 10 K and
1000 K, LoopCare will run a test to determine the stability of the ground.
There is also a specific request that can be used to run this same test by
itself. This request is the SOAK request.
The test for the stability of a ground in the regular LoopCare tests is the
same as the test run with the specific SOAK transaction. Basically,
LoopCare applies voltage to the line and then makes a series of six
measurements at half second intervals. The largest of these six values is
compared to the resistance value before the SOAK test. If the largest of the
six values is 20% greater than the value before the SOAK test then the
trouble is considered to be unstable (swinging) and this message is
displayed.
18.
Msg: SWINGING TROUBLE- DRIED OUT

The SOAK test was made and the largest resistance value found after the
voltage was put on the line was greater than 2000 K. This indicates that the
trouble on the line was not stable but may have been corrected (dried out)
by the voltage used in the SOAK test.
19.
Msg: DC RESISTANCE IS NOT SWINGING

A SOAK test is run on the line and the DC resistance is found to be stable
(not swinging). This message will only appear on the SOAK transaction.
20.
Msg: SOAK TEST NOT ATTEMPTED

The SOAK transaction was requested but could not be performed. One of
the following messages will be provided to explain. This message will only
appear on the SOAK transaction.
21.
Msg: * DC RESISTANCE OUT OF RANGE

The SOAK test was not performed because the DC resistances to ground
were not in the 10 K to 1000 K range.
22.
Msg: * EXCESS AC FEMF VOLTAGE

The SOAK test was not performed because AC FEMF voltage was
detected on the line (100 volt peak). Also excessive AC noise (12.5
milliamperes) will stop the SOAK test. [How much voltage?]
23.
Msg: * MEASURING CKT FAILURE

The SOAK test could not be run because of a problem in the LoopCare
measuring equipment.
Summary Messages
The following messages indicate that LoopCare has found a line with low
resistance and has determined that the trouble is in the customer
premises. The presence of a Maintenance Termination Unit on the line
enabled LoopCare to sectionalize the trouble.
The categories identifying the severity of the resistive fault are the same as
those identified above (Very Light to Very Hard). The possible list of
messages that can be displayed are given below:
24.
Msg: VERY LIGHT SHORT T-R ON PREMISES
25.
Msg: LIGHT SHORT T-R ON PREMISES
26.
Msg: MODERATE SHORT T-R ON PREMISES
27.
Msg: HARD SHORT T-R ON PREMISES
28.
Msg: VERY HARD SHORT T-R ON PREMISES
29.
Msg: VERY LIGHT GROUND T-G ON PREMISES
30.
Msg: LIGHT GROUND T-G ON PREMISES
31.
Msg: MODERATE GROUND T-G ON PREMISES
32.
Msg: HARD GROUND T-G ON PREMISES
33.
Msg: VERY HARD GROUND T-G ON PREMISES
34.
Msg: VERY LIGHT GROUND R-G ON PREMISES
35.
Msg: LIGHT GROUND R-G ON PREMISES
36.
Msg: MODERATE GROUND R-G ON PREMISES
37.
Msg: HARD GROUND R-G ON PREMISES
38.
Msg: VERY HARD GROUND R-G ON PREMISES

The following messages indicate that LoopCare has found a line with low
resistance and has determined that the trouble is in the network. The
presence of a Maintenance Termination Unit on the line enabled LoopCare
to sectionalize the trouble.
The categories identifying the severity of the resistive fault are the same as
those identified above (Very Light to Very Hard). The possible list of
messages that can be displayed are given below:
7-128
39.
Msg: VERY LIGHT SHORT T-R IN NETWORK
40.
Msg: LIGHT SHORT T-R IN NETWORK
41.
Msg: MODERATE SHORT T-R IN NETWORK
42.
Msg: HARD SHORT T-R IN NETWORK
43.
Msg: VERY HARD SHORT T-R IN NETWORK
44.
Msg: VERY LIGHT GROUND T-R IN NETWORK
Summary Messages

45.
Msg: LIGHT GROUND T-G IN NETWORK
46.
Msg: MODERATE GROUND T-G IN NETWORK
47.
Msg: HARD GROUND T-G IN NETWORK
48.
Msg: VERY HARD GROUND T-G IN NETWORK
49.
Msg: VERY LIGHT GROUND R-G IN NETWORK
50.
Msg: LIGHT GROUND R-G IN NETWORK
51.
Msg: MODERATE GROUND R-G IN NETWORK
52.
Msg: HARD GROUND R-G IN NETWORK
53.
Msg: VERY HARD GROUND R-G IN NETWORK # stopped here 170
54.
Msg: POSSIBLE RECEIVER-OFF-HOOK

LoopCare has tested a line with an MTU on it and has found an T-R short
less than 3.4 K ohms on the customer's premises. This message will only
appear on lines with MTUs.
Summary Messages

Summary Messages
1.
Msg: RINGER COUNT MAY BE WRONG- BL

The ringer count was made but the ringer count may be inaccurate
because of bridge lifters on the line. The ringer count will be displayed in
the RINGER category of the test results.
2.
Msg: WRONG RINGER TERM:LIKE 2 PTY-1 ASN

An LoopCare test was run on the line and the arrangement of ringers at the
termination was not what was expected according to the line records. In
this case, the ringer termination that was found looks like a two-party line
with one assigned pair.
3.
Msg: WRONG RINGER TERM:LIKE 2 PTY-2 ASN

this case, the ringer termination that was found looks like a two-party line
with two assigned pairs.
4.
Msg: WRONG RINGER TERM:LIKE SINGLE PTY

this case, the ringer termination that was found looks like a single-party
line.
5.
Msg: RINGER TERM LIKE 2 PTY-1 ASN

An LoopCare test was run on a line either with no line records or with
uncataloged termination. Because of this LoopCare cannot determine
whether the ringer termination is valid. Instead, LoopCare describes the
ringer termination it identifies. In this case the ringer termination looks like a
two-party line with one assigned pair.
6.
Msg: RINGER TERM LIKE 2 PTY-2 ASN

two-party line with two assigned pairs.
7.
Msg: RINGER TERM LIKE SINGLE PARTY

single-party line.
7-130
Summary Messages

8.
Msg: DIFFERENCE: RECORDS SAY ** RINGERS

The number of ringers counted by LoopCare differs from the number of
ringers indicated in the line records. The number of ringers noted in the line
records will be displayed in this message. This message will be followed by
the next message.
9.
Msg: * MLT RINGER COUNT SAYS ** RINGERS

The number of ringers counted by LoopCare differs from the number of
ringers indicated by the line records. This message indicates the number of
ringers that LoopCare detected.
10.
Msg: NO RINGERS FOUND

The LoopCare ringer count was made but no ringers were found. This
usually indicates a trouble condition, since LoopCare will make the ringer
check only if it expects ringers based on the line record information.
11.
Msg: CAN'T DO RINGER TEST

The LoopCare RINGER test was not performed. The reason for this may
be represented by any of the next four messages.
12.
Msg: * MEASURING CKT OVERLOAD

The RINGER test could not be run because of an overload on the
LoopCare measuring equipment.
13.
Msg: * NO RINGERS EXPECTED

The RINGER test was not run because no ringers were expected
according to the line record information.
14.
Msg: * LOW RESISTANCE

The RINGER test was not run because the LoopCare DC resistances were
low (less than 150 kilohms).
15.
Msg: * NOISE
The RINGER test was not run because of excess noise on the line (greater
than 12.5 milliamps AC current).
16.
Msg: RINGER TERMINATION OK

The RINGER test was run and the arrangement of ringers at the
termination was consistent with the type of arrangement indicated by the
line records.
17.
Msg: CANT VERIFY RNGR TERM- UNCATALOGED

The RINGER test was run on a line with an uncataloged termination.
Therefore, LoopCare cannot determine whether the ringer termination is
valid or not.
18.
Msg: WRONG RINGER TERMINATION
Summary Messages
The LoopCare ringer test was run and it was determined that the ringer
termination was incorrect for the type of termination indicated by the line
records. However, LoopCare did not indicate what type of termination the
ringer arrangement resembled.
19.
Msg: TONE RINGER DETECTED

An RC tone ringer is a high-impedance ringer found in some customerprovided equipment (CPE) as well as in standard sets. The RC tone ringer
causes the AC resistance to be higher than the usual values associated
with standard ringers. (Tone ringer: 20-50 kilohms AC; standard ringer: 1018 kilohms AC.) In fact, the AC values will almost look like those for an
open except for the case where a tone ringer was detected.
20.
Msg: POSSIBLE KEY SET

A Key telephone set is any set that permits the user to operate buttons to
access more than one central office line. If LoopCare detects more than
one ringer T-R and exactly one ringer T-G and R-G, a Key set probably is
causing the inconsistent ringer counts. LoopCare will remove the grounded
ringers and one of the T-R ringers and will display the adjusted ringer
count.
21.
Msg: POSSIBLE FAULTY TELEPHONE SET

The DC signature measured by LoopCare indicates the possible existence
of a faulty telephone set. A faulty telephone set presents a relatively low
resistance to current flow in one direction and a relatively high resistance in
the other.
22.
Msg: HARD SHORT

This message appears in tandem with Summary 22. It indicates that
LoopCare has measured a T-R short of less than 3.4 kilohms for current
flow in one direction.
7-132
Summary Messages
Rotary Dial & Touch-Tone Summary

Messages
Summary Messages
1.
Msg: DIAL SPEED OK
**** PPS
The rotary dial test has determined that the dial speed was correct [8 to 11
pulses per second (PPS)]. The PPS value will be displayed in the
message.
2.
Msg: SLOW DIAL SPEED
**** PPS
The rotary dial test has determined that the dial speed was too slow. A
problem with the dial is likely. The PPS value will be displayed in the
message.
3.
Msg: DIAL SPEED INCORRECT **** PPS

The rotary dial test indicates that the speed of the dial is incorrect. The PPS
value will be displayed in the message.
4.
Msg: INCORRECT NUMBER OF PULSES

The rotary dial test counted an incorrect number of pulses (other than ten).
This could happen if the customer did not dial zero.
5.
Msg: BREAK OK
**** %
The rotary dial test determines that the percent break of the dial tested is
within the acceptable range (57 to 64%). The percent break will be
displayed in the message.
6.
Msg: BREAK INCORRECT
**** %
The rotary dial test has determined that the percent break of the dial
measured is not within the acceptable range (57 to 64%). The measured
percent break will be displayed in the message. In some cases this
message will be followed by message 7.
7.
Msg: * DUE TO DLL ON LINE

The incorrect break could be due to a Dial Long Lines (DLL) on the loop.
8.
Msg: TIME OUT IN DIAL TEST

This message could occur if the person at the station waited too long
before dialing zero and LoopCare timed out before the test was made.
LoopCare waits 30 seconds for the dial before it times out. This message
could also occur if the dial cannot put out any pulses. This message will be
followed by message 9.
9.
Msg: RETEST IF DESIRED

This message follows message 8 and indicates that the rotary dial test can
be run again.
Summary Messages
10.
Msg: ROTARY DIAL ANALYZER NOT AVAILABLE

The rotary dial test could not be made because the LoopCare equipment
required to perform the test was not available.
11.
Msg: DIAL OK
If the results of the rotary dial test indicate that the dial speed and the
percent break both are okay, the dial is considered satisfactory.
12.
Msg: DIAL NOT OK

If there are any problems with the dial speed or the percent break,
LoopCare will indicate a problem with the rotary dial.
13.
Msg: CANT DO DIAL TEST

The rotary dial test could not be performed. This could happen for a
number of reasons, including timeout or a loop resistance that is too high
(see message 14).
14.
Msg: * LOOP RESIST TOO HIGH

The rotary dial test could not be performed because the combined
resistance of the loop and the test trunk exceeded 6 kohms in an off-hook
state. Resistance in this range may affect the reliability of the dial test.
15.
Msg: TIMEOUT IN TT TEST

This message could occur if the person at the station set waited too long
before entering the digits on the Touch-Tone pad. During the TT test,
LoopCare waits about 10 seconds for the tones before it times out. The
message also could occur if the subscriber's Touch-Tone pad fails to put
out any tones.
16.
Msg: TT PAD OK
The LoopCare TT test indicates that the tones put out by the subscriber's
Touch-Tone pad are within the acceptable limits.
17.
Msg: TT PAD NOT OK

The LoopCare TT test indicates that the tones put out by the subscriber's
Touch-Tone pad are not within acceptable limits. This message also could
occur if the customer entered the digits in the wrong order during the TT
test.
7-134
Summary Messages
Special & Protected Service Summary

Messages
Summary Messages
1.
Msg: PROTECTED SERVICE

The line records for this line indicate that the subscriber's line is protected
(police or fire department lines, for example). This message will be
modified by message 2.
2.
Msg: CUSTOMER PERMISSION NEEDED TO TEST

This message modifies message 1. It indicates that customer permission
should be obtained before testing the line. This is important because
testing the line will interfere with the circuit alarm.
3.
Msg: SPECIAL SERVICES IDENTIFIED

LoopCare has identified central office equipment which is special service.
The particular equipment that was found will be described in one of the
following messages.
4.
Msg: * MFT LOOP SIGNAL EXTENDER

LoopCare has detected an MFT (Metallic Facility Terminal) Loop Signal
Extender on the line. This equipment requires special services.
The MFT has the following LoopCare signature:
Resistance
Voltage
>1000 K T-R
5.
75 to 90 K T-G
- 9 to -14 V T-G
75 to 90 K R-G
-9 to -14 V R-G
Msg: * DIGITAL CHANNEL CARRIER

LoopCare has detected a Digital Channel Carrier unit on the line. This
equipment also requires special services. This carrier unit has the following
LoopCare signature:
Resistance
Voltage
>1000 K T-R
50 to 800 K T-G
-55 to -65 V T-G
50 to 800 K R-G
-55 to -65 V R-G
Summary Messages

Summary Messages
1.
Msg: GOOD PBX SIGNATURE- COUPLER

The LoopCare DC resistances and voltages were valid for the type of PBX
(equipped with a coupler) indicated in the line records.
2.
Msg: GOOD PBX SIGNATURE

The LoopCare DC resistances and voltages were valid for the type of PBX
indicated by the line records.
3.
Msg: GOOD DC VALUES- SPECIAL EQUIPMENT

The LoopCare DC resistance and voltages were valid for a line served with
equipment indicated in the line records. It is likely that the equipment
affects the LoopCare DC resistance or voltage in such a way as to make it
look like a trouble condition. This message indicates that any unusual
values in the LoopCare signature were due to the special equipment.
4.
Msg: INVALID PBX SIGNATURE FOR PBX TERM

The LoopCare DC resistances and voltages were not what were expected
for the type of PBX termination indicated by the line records.
5.
Msg: DC SIGNATURE LOOKS LIKE PBX

The LoopCare DC resistances and voltages match the electrical signature
that would be expected from a PBX. However, the line records do not
indicate a PBX termination. If the line records are correct and there is no
PBX, then the LoopCare signature is probably due to some sort of trouble.
6.
Msg: AC SIGNATURE NOT EXPECTED FOR PBX

An AC signature that resembles a ringer-like termination was identified on
a line that is identified as a PBX in the line records. Since PBXs do not
have ringer-like terminations, this AC signature is unexpected.
7.
Msg: DIMENSION TRUNK REVERSAL

This message indicates that LoopCare found an invalid PBX signature,
specifically for a DIMENSION PBX that has been installed in reverse. The
LoopCare DC signature for a DIMENSION reversal is shown below:
Resistance
Volts
> 54 kilohms T-R
7-136
27 - 35 kilohms
-40 V to -55 V T-G
7 - 20 kilohms
-40 V to -55 V R-G
Summary Messages

A reversal of this sort could result in a subscriber complaint of trouble
making outgoing calls. The problem may go unnoticed or seem intermittent
because the system will allow the user to get access to the next available
outgoing trunk if trouble is experienced.
8.
Msg: PBX LINE WITH POSSIBLE ROUTE ADVANCING
9.
Msg: OR ON INTERCEPT
This message indicates that LoopCare has tested a PBX line and found
that it may be a route-advanced line -- a PBX extension that is dialed direct,
bypassing the regular PBX trunks. The electrical signature that LoopCare
sees matches an intercept signature.
10.
Msg: COULD NOT MAKE METALLIC ACCESS

LoopCare could not access the metallic testing path of the DLCS. Message
5, 6, 7, 8, 9, 41, or 42 provides the specific reason.
11.
Msg: * DUE TO BUSY ACCESS SYSTEM

Metallic access was not made because the metallic access path was being
used (busy).
12.
Msg: * DUE TO MAJOR ALARM

Metallic access was not made because a major internal DLCS alarm was
set.
13.
Msg: * DUE TO TEST SYSTEM FAILURE

Metallic access was not made because a failure in the DLCS access
system was detected.
14.
Msg: * PAIR GAIN ACCESS EQUIPMENT BUSY

Metallic access was not attempted because the DLCS access equipment
was not available.
15.
Msg: * PAIR GAIN EQUIPMENT FAILURE

Metallic access was not made because of a failure in the DLCS pair gain
equipment.
16.
Msg: CHANNEL FAILURE

The results of the DLCS self sanity check indicated a channel failure.
17.
Msg: CHANNEL STATUS NOT IDENTIFIED

The DLCS self sanity check returned results that do not match any of the
recognizable channel signatures.
18.
Msg: CAN'T DO CHANNEL TEST

Although LoopCare has access to the line, the DLCS self sanity check
could not be made. This could occur if the sleeve lead could not be
opened.
Summary Messages
19.
Msg:CANT DO CHANNEL TEST

DLC channel test results are obtained by manipulating the No Test Trunks
sleeve lead. This summary message is displayed if the analog signaling
fails.
If the Reclassify VER 5X feature (#244) is enabled and no other faults were
found, this summary message is replaced with TEST OK CHANNEL
TESTS IGNORED.
20.
Msg: CHANNEL-SINGLE PARTY SERVICE

The results of the DLCS self sanity check indicate that the channel is
capable of handling single-party service.
21.
Msg: CHANNEL-MULTIPLE PARTY SERVICE

capable of handling multiple-party service.
22.
Msg: CHANNEL-COIN SERVICE

capable of handling coin service.
23.
Msg: PAIR GAIN SYSTEM BUSY

LoopCare cannot make metallic access on the pair gain system because
someone else is using the metallic access path to test the line. Testing is
stopped and no metallic access is attempted.
24.
Msg: PAIR GAIN SYSTEM FAILURE

LoopCare cannot make metallic access on the pair gain system because of
either a major or minor alarm in the system. Testing is stopped.
25.
Msg: CO TESTING NOT POSSIBLE

When followed with message 20, SPECIAL DLCS EQUIPMENT, this
message will appear if you run a CO transaction on a line served by an
integrated DLCS and Ground Start SPOTS channel. You should not do this
transaction, because the customer doesn't have regular CO equipment, so
LoopCare cannot do the normal CO tests.
26.
Msg: MDF TESTING NOT POSSIBLE

When followed with message 20, SPECIAL DLCS EQUIPMENT, this
message will appear if you run any type of MDF transaction on a line
served by an integrated DLCS. You should not do MDF testing if a
customer is served by an integrated DLCS, because the customer doesn't
have a dedicated pair coming from the MDF frame; the pairs coming out of
the switch for an integrated DLCS are shared by many customers.
27.
Msg: SPECIAL DLCS EQUIPMENT

This message is always used with message 18 or 19.
7-138
Summary Messages

28.
Msg: AGREE WITH TERMINATION CODE

The results of the DLCS self sanity check indicate that, although the line
records show that the line is either a coin or multiparty line, the channel unit
in the DLCS is only capable of handling single-party service.
29.
Msg: CHANNEL ISOLATION TEST RESULTS NOT READY

This message will appear if you have run a CHANNEL request and the test
equipment is too busy to have finished the test in time. If you get this
message, try to run the test again later.
30.
Msg: BAD COT CHANNEL UNIT

LoopCare has run channel unit diagnostics (also called channel isolation
tests), and has found something wrong with the COT channel unit.
31.
Msg: BAD RT CHANNEL UNIT

LoopCare has run channel unit diagnostics (also called channel isolation
tests) and has found something wrong with both the COT channel unit and
the RT channel unit.
32.
Msg: GOOD COT CHANNEL UNIT

This message will appear if you have run a CHANNEL request and the
channel unit diagnostics have shown that the COT channel unit is good.
This message will always appear with message 29. If the COT channel unit
is good but the RT unit is bad, only the BAD RT CHANNEL UNIT message
will be printed.
33.
Msg: GOOD RT CHANNEL UNIT

This message will appear if you have run a CHANNEL request and the
channel unit diagnostics have shown that the RT channel unit is good. This
message will always appear with message 28. If the RT channel is good
but the COT unit is bad, only the BAD COT CHANNEL UNIT message will
be printed.
34.
Msg: NEED ACCESS POINT INFORMATION
35.
Msg: TO ACCESS THIS LINE.
36.
Msg: ENTER R, C OR L IN APT FIELD

These messages will appear together if you have run a Special Services
Access (SSA) request but have left the APT field on the STV mask blank.
You must fill in this field to access a special services line with the SSA
request.
37.
Msg: LINE RECORD INDICATES 4 WIRE CIRCUIT
38.
Msg: ENTER Y OR N IN XMT FIELD TO SPECIFY
39.
Msg: TRANSMIT OR RECEIVE PAIR
Summary Messages
These messages will appear together if you have run an SSA request on a
4-wire special services circuit but have left the XMT field on the STV mask
blank. You must fill in this field to access a 4-wire circuit with the SSA
request.
40.
Msg: INVALID REQUEST FOR SPECIAL SERVICE ACCESS

This message will appear if you already have obtained a special services
access on a line by means of the SSA request and you attempt to run
certain requests that LoopCare cannot handle on these lines (for example,
a TAKE request).
41.
Msg: INVALID REQUEST FOR 4 WIRE CIRCUIT

This message will appear if you already have obtained a special services
access on a 4-wire circuit by means of the SSA request and you attempt to
run certain requests that LoopCare cannot handle on these circuits (for
example, a RING request).
42.
Msg: FEMF ON PAIR GAIN ACCESS TN

This message will appear if you are attempting to do a Special Services
Access (SSA) request on an STV mask and the access telephone number
(TN) in the central office has FEMF on it. You should probably notify the
Facilities Manager if you get this message.
43.
Msg: PAIR GAIN ACCESS TN ON INTERCEPT

This message will appear if you are attempting to do an SSA request on an
STV mask and the access TN in the central office is on intercept. You
should probably notify the Facilities Manager if you get this message.
44.
Msg: INVALID PAIR GAIN ACCESS TN SIGNATURE

This message will appear if you are attempting to do an SSA request on an
STV mask and the signature of the access TN in the central office is
incorrect. You should probably notify the Facilities Manager if you get this
message.
45.
Msg: * OR INVALID ID OR LT
This message will appear only with messages 4 and 5. This combination
means that you could not make metallic access because of a busy access
system or because of invalid DLC system ID or Line Terminal (LT) entries
during an SSA request from the STV mask.
46.
Msg: * OR INVALID ACCESS POINT

This message will appear only with messages 4 and 5. This combination
means that you could not make metallic access because of a busy access
system or because of invalid access point information on an SSA request
from the STV mask.
47.
7-140
Msg: BUSY -SPEECH
Summary Messages

48.
Msg: VALID REQUESTS ARE 'MON', 'SSA', OR 'X'

You will see this combination of messages if
1.
You have run an SSA request
2.
LoopCare has determined that the circuit you're testing is busy
3.
There is speech on the line.
At this point, you can do a 'MON' request without disturbing the customer; if
you do an SSA request, you will disconnect the customer's conversation if
it is still in progress.
49.
Msg: CAUTION: LINE RECORD WC USED. IF
50.
Msg: INCORRECT, CHANGE WC VIA RTE MASK

This message appears if you are testing a multi-point Special Services
circuit served by a DLC (that is, one that has more than one DPA line
record) and there is special equipment available in the central office. It only
appears if there is no trouble entered in LMOS for the line you are testing.
This means you should make sure that the wire center in the line record is
the wire center for the loop you are testing; if not, you will not be able to test
the line without entering a trouble and changing the wire center to the
correct one via the RTE mask.
51.
Msg: COULD NOT ACCESS
52.
Msg: * NO USABLE DIALER

These messages will appear together if you have run an SSA request but
the LoopCare hardware was not available to handle the request.
53.
Msg: COULD NOT DO CHANNEL ISOLATION TESTS
54.

These messages will appear together if you have run a CHANNEL request
but the LoopCare hardware was not available to handle the request.
55.
Msg: ID FIELD BLANK, ENTER DIGITS

This message will appear if you have run an SSA request but have left the
ID field on the STV mask blank. You must fill in this field to access a special
services line with the SSA request.
56.
Msg: LT FIELD BLANK, ENTER DIGITS

This message will appear if you have run an SSA request but have left the
LT field on the STV mask blank. You must fill in this field to access a special
services line with the SSA request.
57.
Msg: INVALID ACCESS PT FOR 4 WIRE CIRCUIT
Summary Messages
This message will appear if you have run an SSA request on a 4-wire
special services circuit and entered L in the APT field. LoopCare cannot
access a 4-wire circuit at one L access point.
58.
Msg: * OR BUSY ACCESS SYSTEM

This message will always appear with messages 4 and 6. Metallic access
was not made, either because a major interval DLCS alarm was set or
because the metallic access path was being used (busy).
59.
Msg: MDF ACCESS REQUIRED FOR THIS REQUEST

This message will appear if you do not have an MDF access established
and you have entered a request that requires an MDF access.
60.
Msg: INVALID REQUEST FOR THIS DLCS LINE

This request may appear alone or in conjunction with messages 62 and 63.
When it appears alone, it indicates that the hardware configuration is such
that LoopCare cannot run the request. TAKE requests will not be allowed
on SLC lines, as indicated in the line record; if you attempt one, this
message will appear alone.
It also appears with messages 62 and 63 when you have run a COIN
request on a DLCS line: For COIN tests on DLCS lines you should first run
FULL or LOOP, then the CSET request.
61.
Msg: USE FULL OR LOOP TO GET MET ACCESS

See messages 61, 64, 66, and 67.
62.
Msg: USE CSET REQUEST FOR COIN TESTS

See message 61.
63.
Msg: CAN'T DO TT TEST ON

This message is used with central office message 27 and DLCS message
65 or DLCS messages 68 and 62 to form the following three-line
messages:
7-142
CAN'T DO TT TEST ON
CAN'T DO TT TEST ON
DLCS BEFORE METALLIC ACCESS
Summary Messages

The TT test is not possible through certain hardware configurations. If you
get the first three-line message, you should drop the access by using the X
request, then do a TT request before you run another FULL or LOOP
request. If you get the second three-line message, you should get an
access by using a FULL or LOOP request and then run the TT request.
64.
Msg: DROP ACCESS, THEN REPEAT REQUEST

See messages 64, 66, and 67.
65.
Msg: CAN'T DO RING REQUEST ON THIS

messages:
CAN'T DO RING REQUEST ON
CAN'T DO RING REQUEST ON
The RING request is not possible through certain hardware configurations.

If you get the first three-line message, you should drop the access by using
the X request, then do a RING request before you run another FULL or
LOOP request. If you get the second three-line message, you should get
an access by using a FULL or LOOP request and then run the RING
request.
66.
Msg: CAN'T DO TALK REQUEST ON THIS

messages:
CAN'T DO TALK REQUEST ON
CAN'T DO TALK REQUEST ON
The TALK request is not possible through certain hardware configurations.

If you get the first three-line message, you should drop the access by using
the X request, then do a TALK request before you run another FULL or
Summary Messages
LOOP request. If you get the second three-line message, you should get
an access by using a FULL or LOOP request and then run the TALK
request.
67.
Msg: DLCS BEFORE METALLIC ACCESS

See messages 64, 66, and 67.
68.
Msg: CANNOT APPLY TONE ON THIS

This message is used with DLCS messages 68 and 62 to form the
following three-line message:
CANNOT APPLY TONE ON THIS
It isn't possible to put TONE on a DLCS line through certain hardware

configurations unless you already have metallic access. You should first
run a FULL or LOOP request and then run TONE.
69.
Msg: INVALID REQUEST FOR THIS

This message is used with messages 68 and 62 to form the following
three-line message:
INVALID REQUEST FOR THIS
The message indicates that LoopCare cannot run the request through the
existing hardware configuration. You should establish metallic access by
first running a FULL or LOOP request.
70.
Msg: VALID REQUESTS ARE SSA OR X

You can only make an SSA request or drop access altogether. (This
message appears as the third line of a three-line message described under
message 18 in System Status Summary Messages.)
71.
Msg: TT NOT AVAILABLE FOR
72.
Msg: THIS ACCESS POINT

This message will appear if you run a TT request and enter either a "C" or
an "L" in the APT field on the STV mask. You must enter an "R" in the APT
field for this to work.
7-144
73.
Msg: USE XCB REQUEST TO DROP CALLBACK
74.
Msg: THEN RUN SSA
Summary Messages

This message will appear if you have a callback established while testing a
Special Services circuit and are attempting to switch access points. In
certain situations you can't do this directly. You must first drop your
established callback via the XCB request before you can switch access
points and rerun your SSA request.
75.
Msg: USE XTONE REQUEST TO DROP TONE

This message is used with message 75 to form the following two-line
message:
USE XTONE REQUEST TO DROP TONE
THEN RUN SSA
This message will appear if you have applied tone while testing a Special
Services circuit and are attempting to switch access points. In certain
situations you can't do this directly. You must first drop your established
tone via the XTONE request before you can switch access points and rerun
your SSA request.
76.
Msg: LINE RECORD ID AND LT OVERRIDDEN

This message appears if you are running an SSA request and your entries
in the ID and LT fields on the STV mask do not match the values in the line
records. LoopCare assumes that your entered values are to take
precedence and sends you this message to confirm the discrepancy with
the line record values.
77.
Msg: C.O. TEST NOT DONE- SPECIAL DLCS

This message will appear if you run a FULL transaction on a line served by
an integrated DLCS and Ground Start SPOTS channel.
78.
Msg: INTEGRATED PGS DETECTED

This message may appear if you are using the DLC Testing Feature
(testing independent of line records). There are two cases in which this
message might be returned, they are:
79.
1.
An IDLC signature match was found and the line records available
did not indicate IDLC. The message will be displayed along with the
test results.
2.
An IDLC signature match was found and no line records were

available. This message will be displayed along with the test results.
Msg: NO PGS DETECTED

Summary Messages
80.
1.
No signature match was found and the line was tested as non-DLC
but the line records indicate UDLC. This message will be displayed
along with the test results.
2.
No signature match was found and the line was tested as non-DLC
but the line records indicate IDLC. This message will be displayed
along with the test results.
Msg: NO LIL CALIBRATION DETECTED

A REF0 test failed because no calibration module (LIL-CM) is detected on
the specified line.
81.
Msg: UNIVERSAL PGS DETECTED

1.
A UDLC signature match was found and the line records available
did not indicate UDLC. The message will be displayed along with
the test results.
A UDLC signature match was found and no line records were available.
This message will be displayed along with the test results.
See Also
A number of messages that originally appeared in this section now appear
in System Status Summary Messages -- specifically those previously
identified as ST42, ST43, ST44, ST45, ST46, ST47, ST48, ST49, and
ST51.
7-146
Summary Messages

Summary Messages
1.
Msg: CANNOT SEND TO APPLICATION PROCESS

There are several reasons why LoopCare could not send a request to the
application process, including Network Manager failure, incorrect machine
IDs stored in the mltacc table, or an error in the database.
2.
Msg: CAN'T GET MEMORY TO COMPLETE REQUEST

The system currently is very busy. Try again to enter the transaction later; if
the message continues to appear, call System Support.
3.
Msg: CANT SEND REQUEST TO APPROPRIATE FE

When a request can't be sent to another FE on which the line record exists,
LoopCare attempts to continue testing on the current FE with the default
exchange key for the NPANNX. This message appears when a matching
entry for the default exchange key can't be found in the MLTACC table.
4.
Msg: CAN'T TEST- POSS TRUNK CALIB PROB

LoopCare cannot test the line at the moment because the system is
experiencing problems in calibrating the trunk.
5.
Msg: COULD NOT ACCESS

LoopCare attempted to access the line but was unable to do so for some
reason. Some of these are listed in messages 35 to 40.
6.
Msg: * DATABASE DOWNLOAD IN PROGRESS

A test request was submitted for a testhead to which database information
is being downloaded. This summary message appears with VER B6, TEST
EQUIP BUSY.
Summary Messages
7.
Msg: DATA LINK FAILURE

The data link between the LoopCare Front End (FE) and the LTS has
failed. No testing can be done while this condition exists.
8.
Msg: DERIVED PAIR NOT TESTED
9.
Msg: PHYSICAL PAIR NOT SERVED BY MLT

The derived pair of a line was not tested because the physical pair was not
served by LoopCare. LoopCare must be able to access the physical pair in
order to test the derived pair.
This summary message was for LTF(BOS) simulator failures. It is not used
in LTF(UNIX)/LoopCare environments.
10.
Msg: DIAGNOSTICS REQUESTED

LoopCare testing was stopped because a request was made to run a
diagnostic program for system maintenance. Such a request stops all
testing in progress and suspends testing until the diagnostic tests are
complete.
11.
Msg: DIAGNOSTICS RUNNING

The test equipment failed because diagnostic tests were in progress at the
time the request was made.
12.
Msg: DOWNLOAD IN PROGRESS

Tests could not be run because the equipment was busy handling a
download of information from the FE. (This message will be followed by
message 75.)
13.
Msg: DPA REC NOT FOUND

This message will appear when the Different Premises Address (DPA) line
record is not found.
7-148
Summary Messages

14.
Msg: * INCOMPATIBLE VERSIONS

A test request containing a Telephone Number with Extra Type and Extra
Digits has been submitted to an RTU that does not provide Hunt Groups.
15.
Msg: INVALID CALLBACK TELEPHONE NUMBER

This message will appear if you have attempted a TV-interactive
transaction with an invalid callback number. Check your records, and, if
your callback number appears to be correct, notify the Facilities Manager
to resolve the problem.
16.
Msg: INVALID DCTU/PORT FOR NXX/EXK

This message appears if you have entered an invalid DCTU ID for a
specific NXX/EXK or selected a DCTU port that is not equipped. Each
NXX/EXK combination is assigned the test hardware using ADEF. Enter a
valid DCTU ID to correct the error.
The number of ports available for each DCTU depends on the number of
PMUs. Four ports are available with each PMU, but each PMU has access
to all ports.
Number of PMUs
Valid Port IDs
1-4
1-8
1-12
If, for example, the DCTU is equipped with one (1) PMU and you request
Port 5, the request would be invalid.
17.
Msg: INVALID NPA-NNX

The NPANNX that was entered in the TN (telephone number) field did not
match any exchange key in the database. Testing couldn't be done, since
the system couldn't map the number to an exchange key.
18.
Msg: INVALID OVERRIDE FOR ISDN

This message appears if you attempted to enter one of the following
requests with the E, K, or L override option:
Summary Messages
DIG, HELPI, LINESP, LPBK, NFULL, PER, PML1, PML2, PML3,
RESTORE, STATUS
19.
Msg: INVALID OVERRIDE FOR MDF

MDF, MDFNUM, MDFGRP
20.
Msg: INVALID OVERRIDE FOR REQUEST TYPE

LOCATE, LOC1, LOC2, LOCGP
21.
Msg: INVALID OVERRIDE FOR TEST HEAD TYPE

This message appears if you attempted an E override entry for a line where
the testhead (primary or secondary) is not an EMU or an L override entry
for a line where the testhead (primary or secondary) is not an LTS, or a K
override if the testhead is not a DCTU.
22.
Msg: INVALID PHYSICAL PAIR TN OR-
23.
Msg: INVALID MDF DEDICATED NUMBER

The system can't test a line because of one of two reasons:
24.
7-150
The line may be a derived pair and the telephone number of the
physical pair is not a valid seven-digit number. Previously the
telephone number of the physical pair was only four digits, but the
records should have been updated to show seven. This is a
database record problem.
The line could not be tested because the MDF dedicated number is
not a valid seven-digit TN.
Msg: INVALID TN
Summary Messages

This message appears if you try to test a telephone number that is not one
of the following:
25.
A ten-digit TN
A ten-digit TN plus an extra series field starting with either TER, XN,
S, OGO, or OD
A Special Services TN served by a DLCS so that you can do an

SSA request.
The line record does not indicate that you can do an SSA request on
the line.
Msg: INVALID WIRE-CENTER IN LINE RECORD

This message will appear if you are trying to test a Special Services line on
a DLCS and there is no wire center in the line record.
26.
Msg: LINE NOT MLT TESTABLE

The line for which the test request is made cannot be tested by LoopCare
because of the type of service or equipment. An example would be a line
with a Subscriber Loop Multiplexer (SLM).
27.
Msg: LINE NOT SERVED BY MLT

The line for which the test request is made is not served by the LoopCare
system. Therefore, no test is made.
28.
Msg: LOOP TESTING FRAME POWER FAILURE

The LTF has lost power. No testing can be done while this condition exists.
29.
Msg: LTF POWER CLEAR

Testing was not done because of a power clear condition that existed on
the LTF.
Summary Messages
30.
Msg: LTF POWER CLEAR REQUESTED

A power clear or reset was performed on an LTF. Send the request again. If
the message continues to appear, call System Support.
31.
Msg: MISSING DATA IN TEST UNIT

A setup error has been detected in an RTU table.
32.
Msg: NNX NOT IN DATA BASE

The test was not made because the NNX of the number requested was not
in the database.
33.
Msg: NO LINE RECORD IN SYSTEM-
34.
Msg: TN NOT TESTABLE WITHOUT LINE RECORD

This is a Special Services TN. To do No-Test trunk testing on this line, there
must be a line record on the system. This error message means one of the
following:
35.
There is no line record for this TN
LoopCare could not find the line record.
Msg: * NO TEST PACKAGE AVAILABLE

The line could not be accessed because there was no working test
package available at the time of access.
36.
Msg: * NO UNIGAUGE TRUNK AVAILABLE

The line could not be accessed because it is a Unigauge-type line; a
specific type of test trunk is required for access. This trunk was not
available.
37.
7-152
Msg: * NO USABLE BUSY DETECTOR
Summary Messages

The line could not be accessed because there was no working busy
detector available at the time of access.
38.

The line could not be accessed because there was no working dialer
available at the time of access.
39.
Msg: * NO USABLE PORT

The line could not be accessed because a good test port (circuits that allow
the testing system equipment to connect to any trunk) was not available at
the time of access.
40.
Msg: * NO USABLE TRUNK

The line could not be accessed because there was no working test trunk
(No-Test type) available at the time access was attempted.
41.
Msg: NPA-NNX NOT IN DATA BASE

The line could not be tested because the NPANNX of the telephone
number entered did not match any listings in the LoopCare Access
(MLTACC) table. The NPANNX is valid and has an exchange key, but there
is no match for the NNX in the table, so no testing is performed.
42.
Msg: NTT/PORT OUT-OF-SERVICE

This message appears if you enter the ID for an EMU NTT or DCTU port
that is out-of-service. If the DCTU is out-of-service, the message VER BB:
NO DCTU AVAILABLE is displayed.
43.
Msg: NTT/PORT SELECTION PROHIBITED

DROP ACCESS AND RETEST
Summary Messages
This message appears if you made a successful request for access, but
during that session attempted to select another NTT or DCTU port without
first dropping the initial access. To select another NTT or DCTU, you must
first drop the initial access.
44.
Msg: * OR DATA SET LOCKUP

This line follows LOOP TESTING FRAME POWER FAILURE (message
26). It is saying that sometimes what appears to be an LTF power failure
really indicates that the 202T data sets are locking up in the PDP 11/84
controller or the LTF. To correct this, reseat the 202T channel interface unit.
45.
Msg: OVRD-EXK/NNX COMBO NOT IN DATABASE

The override exchange key entry did not map to the entered telephone
number; i.e., the user attempted to obtain access from a switch that does
not serve the entered telephone number.
46.
Msg: PAIR GAIN ACCESS EQUIPMENT BUSY

This message appears in transactions attempted on Loops equipped with
SLC-96. This message indicates the pair gain access was not available.
Retest at a later time to get complete test results.
47.
Msg: *REMOTE FACILITY DETECTED

A REF0 request detected either a Universal Digital Loop Carrier (UDLC)
Integrated Digital Loop Carrier (IDLC), or EAIU, and was aborted.
This message may follow a CALIBRATION FAILED message.
48.
Msg: SANITY OR DIAG IN PROGRESS

The test equipment was busy because sanity or diagnostic testing was in
progress at the time the test request was made.
49.
7-154
Msg: SIMULTANEOUS TEST REQUEST MADE
Summary Messages

Two or more test requests were made on the same number simultaneously.
The system will accept only one request and indicate a TEST EQUIPMENT
BUSY condition for the other requests.
50.
Msg: * SOFTWARE DOWNLOAD IN PROGRESS

A test request was submitted for a testhead to which software is being
downloaded. This summary message appears with VER B6, TEST EQUIP
BUSY.
51.
Msg: SSA ACCESS REQUIRED BEFORE REQUEST IS PERFORMED
52.
Msg: ENTER 'SSA' IN THE REQUEST FIELD

The line record says that this is a Special Services TN on a Digital Loop
Carrier System (DLCS), which is accessible via the SSA request. To do any
testing, first establish access on the line by doing an SSA request.
53.
Msg: SWITCH INTERFACE UPDATE REQUIRED

This message appears if LoopCare is on the new interface and 5ESS is on
the old and a test request is entered with a K override or a CS request
entered on the SAM ES mask.
54.
Msg: SYSTEM TIMEOUT

The testing system has timed out. This could be a temporary condition, but,
until it is resolved, no testing can be done.
55.
Msg: TAKE NOT ALLOWED ON CMUs

This message will appear if you try to do a TAKE request on a line served
by a Compact Measurement Unit (CMU). Because of differences in how
LoopCare communicates with CMUs as opposed to LTSs, you can't
transfer accesses on CMU-served lines from someone else's terminal to
your own.
Summary Messages
56.
Msg: TAKE NOT ALLOWED ON SPECIAL SERVICES ACCESSES

This message will appear if you try to do a TAKE request on a line that was
obtained with an SSA request. LoopCare doesn't allow you to transfer
SSAs from someone else's terminal to your own.
57.
Msg: TESTABLE VIA GUI ONLY

This message will appear if you attempt to run a DIAL test through a 5ESS
switch from the LTF TEST mask. You must use LoopCare, and, therefore,
the GUI (or an STV mask), for DIAL tests through 5ESS switches.
(Remember that any test you can run from a GUI you also can run from an
STV mask -- but not vice versa.)
58.
Msg: TESTABLE VIA STV OPTION - ENTER STV IN THE REQ FIELD
This message will appear if you are on a GUI, and the line record of the TN
you are trying to test shows that this is a Special Services TN on a DLCS
with special test equipment available in the central office (CO). If you see
this message, you should use an STV mask and run an SSA request to
access the line.
59.
Msg: TESTABLE VIA THE STV MASK ONLY

This message will appear if you try to test a line from any mask other than
STV, and if the line record of the TN you are trying to test shows that this is
a Special Services TN on a DLCS with special test equipment available in
the CO. If you see this message, you should use an STV mask and run an
SSA request to access the line. There are two ways to bring up an STV
mask:
1.
Clear the screen and enter /FOR STV

or
2.
60.
On the GUI, enter "STV" in the REQ field.
Msg: TEST EQUIPMENT BUSY

This indicates that LoopCare testing was not done because the equipment
needed to test was not available. The specific reasons for this will be
provided by a modifying message.
7-156
Summary Messages

This message also appears if an LTS NTT is out-of-service but usable. If
that specific NTT is selected with the L override, however, access will be
granted and the test performed.
61.
Msg: TEST EQUIPMENT BUSY - COULD NOT ACCESS

This message appears if you enter the ID for an NTT or port (for the E, K,
or L option) that is in use.
62.
Msg: TEST EQUIPMENT FAILURE

Testing could not be made or completed because of a failure in the test
system. Such a condition could be caused by a computer or
communication link failure or by the unplugging of the circuit packs during
diagnostic testing.
This message appears as the first line of a three-line message. The second
and third lines are DLCS messages 9 and 71, respectively. The full
message reads as follows:
* PAIR GAIN EQUIPMENT FAILURE
VALID REQUESTS ARE SSA OR X
This message appears if you are testing a Special Services circuit and
could not make metallic access because of a failure in the DLCS pair gain
equipment. Try running your SSA request again, or, if you repeatedly fail to
establish metallic access, use the X request to drop access altogether.
63.
Msg: TEST EQUIPMENT NOT AVAILABLE FOR WC

Special equipment in the CO is necessary to test this line. Either there is no
such equipment available in this CO, or the table that identifies this
equipment has an invalid entry. If you think this is the case, check with the
Facilities Manager.
64.
Msg: TEST EQUIPMENT NOT CALIBRATED

The test could not be made because there was no system calibration
information for the LTF or LTS.
Summary Messages
65.
Msg: TEST EQUIPMENT OUT OF SERVICE

The Loop Testing Frame (LTF) or Loop Testing System (LTS) is out of
service. Any testing that is directed to that equipment will return this
message.
66.
Msg: TEST NOT MADE

The LoopCare test was not made on the line. This could be due to a test
made on a PBX extension or the reason indicated by message 50.
67.
Msg: TEST SYSTEM ERROR

The LoopCare test could not be made because of some error condition in
the test system. Such a problem could be caused by a software or a
hardware malfunction.
68.
Msg: TIME OUT IN ACCESS

LoopCare could not access the subscriber's line within the allotted period
of time.
69.
Msg: TIME OUT IN TESTING

LoopCare could not test the subscriber's line within the allotted period of
time.
70.
Msg: TIMEOUT-POSSIBLE LINE ON INTERCEPT

This message will appear whenever there is a timeout on an access for a
3ESS switch. The problem is that the access times out before the intercept
condition is detected.
71.
7-158
Msg: * TN FROM FE IN DIFFERENT FE GROUP
Summary Messages

This line follows message 9 (TEST NOT MADE). The test was requested
from an FE that cannot test the telephone number because it is associated
with a different Data Communication Network (DCN). It cannot physically
access the telephone number through the DCN to which it is connected.
This can only happen when there are multiple DCNs.
72.
Msg: TN NOT IN 5ESS DATABASE

The telephone number for which the test request was made is a nonworking number on intercept. Therefore, no test is made.
73.
*Msg: VALID ENTRIES ARE 1-12 for port and 1-192 for DCTU
This message appears if you entered invalid entries for the DCTU ID with
the K override option. Valid entries for this feature are 1-2 digits between 1
- 12 for the port ID, and 1-3 digits between 1 - 192 for the DCTU ID. The
message would appear if, for example, you entered K15-3 or K9.
K15-3 is invalid because the port ID range is 1-12. K9 is invalid because a
DCTU Id is required. The 5ESS numbering scheme for the port is 0-11
while LoopCares is 1-12.
74.
Msg: VALID ENTRIES ARE 1-16 FOR LTS/EMU

This message appears if you entered an invalid NTT ID, for example, NTT
0 or NTT 17. Enter an NTT ID from 1 to 16.
75.
Msg: WAIT ONE MINUTE THEN TRY AGAIN

This gives the user an option to make another test request entry, allowing
the system time to complete the download. (This message appears after
message 12.)
Summary Messages

Summary Messages
1.
Msg: CANNOT APPLY TONE WITH CALLBACK PRESENT ON 5ESS/

DCTU
2.
Msg: USE XCB TO DROP CALLBACK AND THEN RUN TONE REQUEST
When LoopCare tests through the Directly Controlled Test Unit (DCTU) of a
5ESS switch, the TONE transaction cannot be run with a callback path
established. This is because the talking path to the subscriber's line is
handled by the switch, but the tone is applied by the DCTU, and both
cannot be connected to the line at the same time. This message tells you to
drop the established callback via the XCB request and then request tone
again.
3.
Msg: CANNOT OBTAIN CALLBACK WITH TONE PRESENT ON 5ESS/

DCTU
4.
Msg: USE XTONE TO DROP TONE AND THEN ADD CALLBACK

When LoopCare tests through the DCTU of a 5ESS switch and a TONE
transaction is in progress, the architecture of the 5ESS/DCTU equipment
prevents the establishment of a callback path until tone is dropped. This
message tells you to drop tone via the XTONE request, after which you can
establish a callback.
7-160
Summary Messages
Training Messages
Summary Messages
1.
Msg: UNACCEPTABLE REQUEST IN THIS CASE - TRY AGAIN

This message will appear on the GUI results screen when the MTRAIN
scenario's are being run. In this case a request was entered against a TN
number which does not apply to this training script.
2.
Msg: ISDN TRAINING UNAVAILABLE - NOTIFY INSTRUCTOR

This message will appear on GUI results screen when a user is attempting
to run the MTRAIN training guide, however, the training feature is not
turned on.
3.
Msg: TRAINING SCRIPT UNAVAILABLE

This message will appear with VER XT on either the DISP, MSCR, or TE
screens when LMOS training is being done. This message means that
either the LoopCare training feature is turned off, or that LMOS is sending
a request which contains an invalid TN or OE number.
Summary Messages
Unexpected Signature Summary

Messages
Summary Messages
1.
Msg: POSSIBLE RECORD ERROR

LoopCare has detected an electrical signature that is not consistent with
the line record information. This message indicates that the line record
information may be incorrect and should be checked.
2.
Msg: DC VALUES LOOK LIKE PBX

The LoopCare DC resistances and voltages match the acceptable
signature for some type of PBX.
3.
Msg: UNEXPECTED RINGER TERM IDENTIFIED

The records indicate a ground-start PBX but the LoopCare tests detect a
ringer-like AC signature between tip and ring (2 to 18 kilohms).
4.
Msg: UNEXPECTED THERMISTOR FOUND

LoopCare suspects an open on a line that has a cataloged termination.
This termination should not have Thermistor on it according to the records,
but, when LoopCare runs a thermistor test to check this possibility, it
detects the presence of Thermistor.
5.
Msg: UNEXPECTED PBX INWARD SERVICE

LoopCare detects a ground-start PBX line with no line circuit and no way to
draw dial tone. It is possible that this line is an inward-only trunk, which
would have no line circuit.
6.
7-162
Msg: UNEXPECTED INTEGRATED PGS/UNEXPECTED UNIVERSAL

PGS
Summary Messages

The results of an LoopCare test indicate a discrepancy between Line
Record information and LoopCare test results. Line Record information
indicates the presence of an Integrated PGS and LoopCare detects a
Universal PGS, or vice versa.
Summary Messages

Summary Messages
1.
Msg: ADSL C.O. SPLITTER SIGNATURE FOUND

A FULL(X) or LOOP(X) was run on a POTS twisted pair and the ADSL
central office maintenance signature was detected which indicates that the
line has ADSL equipment installed on the line.
2.
Msg: AM RADIO DISTURBER AT **** KHZ

The identified disturber is AM radio. The frequency (in KHZ) identifies the
most prominent AM radio disturber. Frequencies conform to standards for
North American AM radio stations.
3.
Msg: BRIDGE TAP TEST NOT DONE
4.
Msg: DATA RATE HIGH= **** KBPS

For the Data Rate Prediction feature, the predicted data rate is greater than
or equal to the Data Rate High Threshold set through the OA&M interface.
5.
Msg: DATA RATE HIGH > **** KBPS

For the Data Rate Prediction feature, the predicted data rate is greater than
or equal to the Data Rate High Threshold set through the OA&M interface.
In addition, this predicted data rate identified at **** KBPS is the lower
bound of the data rate. A specific disturber has not been identified, so an
assumption is made that the noise measured at the near end is actually
dissipated far end noise. Because this is a worst case assumption, it is
presumed that the predicted data rate is at least **** KBPS.
6.
Msg: DATA RATE LOW= **** KBPS

For the Data Rate Prediction feature, the predicted data rate is less than or
equal to the Data Rate Low Threshold set through the OA&M interface.I
7-164
Summary Messages

7.
Msg: DATA RATE LOW > **** KBPS

For the Data Rate Prediction feature, the predicted data rate is less than or
equal to the Data Rate Low Threshold set through the OA&M interface. In
addition, this predicted data rate identified at **** KBPS is the lower bound
of the data rate. An assumption is made (because a specific disturber has
not been identified) that the noise measured at the near end is actually far
end noise. Because this is a worst case assumption, it is presumed that the
predicted data rate is at least **** KBPS.
8.
Msg: DATA RATE MEDIUM= **** KBPS

For the Data Rate Prediction feature, the predicted data rate is less than
the Data Rate High Threshold and greater than the Data Rate Low
Threshold set through the OA&M interface.
9.
Msg: DATA RATE MEDIUM > **** KBPS

For the Data Rate Prediction feature, the predicted data rate is less than
the Data Rate High Threshold and greater than the Data Rate Low
Threshold set through the OA&M interface. In addition, this predicted data
rate identified at **** KBPS is the lower bound of the data rate. An
assumption is made (because a specific disturber has not been identified)
that the noise measured at the near end is actually far end noise. Because
this is a worst case assumption, it is presumed that the predicted data rate
is at least **** KBPS.
10.
Msg: DN RATE CAN BE IMPROVED TO **** K

* BY REMOVING BRIDGED TAP [#]
The Data Rate Optimization algorithm has calculated that the downstream
data rate can be improved by **** Kbps by removing Bridged Tap [#] from
the loop. The Bridged Tap # matches a bridged tap identified in the Bridged
Tap Test Results section of the Test Results page (see Chapter 2 of the
End User GUI Guide - Data Rate Prediction Feature).
11.
Msg: DN RATE CAN BE IMPROVED TO **** K

* BY REMOVING DISTURBER [#]
Summary Messages
The Data Rate Optimization algorithm has calculated that the downstream
data rate can be improved by **** Kbps by removing Disturber [#] from the
loop. The Disturber # matches a disturber identified in the Rate
Improvement section of the test results page for Data Rate Optimization
(see Chapter 2 of the End User GUI Guide - Data Rate Prediction Feature).
12.
Msg: EST. MIXED GA DATARATE ***** KBPS

This message displays the estimated mixed gauge data rate based on loop
length speed bin tables or on loop insertion loss measurements, where
***** is the estimated data rate.
13.
Msg: EST. MIXED GA DATARATE HIGH

The estimated mixed gauge data rate is high based on OAM QUAL
threshold settings.
14.
Msg: EST. MIXED GA DATARATE MEDIUM

The estimated mixed gauge data rate is medium based on OAM QUAL
threshold settings.
15.
Msg: EST. MIXED GA DATARATE LOW

The estimated mixed gauge data rate is low based on OAM QUAL
threshold settings.
16.
Msg: EST. MIXED GA DATARATE FAIL

The the loop supports only a very low data rate.
17.
Msg: * FAULT FOUND ON LINE

A BT test was requested, but the bridge tap test was not run due to faults
found on the line.
7-166
Summary Messages

18.
Msg: * INVALID ACCESS POINT

Wideband tests were not performed because the request requires
wideband access, but the loop is currently accessed at the voiceband
point.
19.
Msg: INVALID TEST REQUEST FOR RTU

A TDR request was submitted for a Harris RTU.
20.
MSG INVALID TEST REQUEST

This message indicates that a test has been requested, but the feature
required for the test is turned off.
21.

NO WIDEBAND ACCESS AVAILABLE
This message indicates that a test has been requested and no broadband
access points exist; or a broadband access point exists, but no test
equipment exists; or the requested tests are not supported by the version
of hardware associated with the line under test.
22.

NO WIDEBAND TEST EQUIP AVAILABLE
This message indicates that a test has been requested and a broadband
access point exists; but no CLT test equipment exists; or the requested
tests are not supported by the version of hardware associated with the line
under test.
23.
Msg: INVALID TEST REQUEST FOR TV

SUPPORTED ONLY ON USER GUI
This message indicates that a test has been requested from the TV mask
that is not supported by this interface. The End User GUI must be used for
for these test requests.
24.
Msg: LIMITED TEST RESULTS DISPLAYED
Summary Messages
A FULL or LOOP request was performed on a xDSL line, but the bridge tap
test was not completed properly. Loop capacity calculations and noise
margin comparisons are not available.
25.
Msg: MIN PRED RATE **** KBPS > SUBSCRIBED

The Data Rate Prediction algorithm has determined that the minimum
predicted data rate is greater than the subscribed data rate obtained from
user input or from the Loop Terminating Equipment (LTE) digital interface.
A specific disturber has not been identified, so an assumption is made that
the noise measured at the near end is actually dissipated far end noise.
Because this is a worst case assumption, it is presumed that the predicted
data rate is at least **** KBPS.
26.
Msg: MIN PRED RATE **** KBPS < SUBSCRIBED

The Data Rate Prediction algorithm has determined that the minimum
predicted data rate is less than the subscribed data rate obtained from user
input or from the Loop Terminating Equipment (LTE) digital interface. A
specific disturber has not been identified, so an assumption is made that
the noise measured at the near end is actually dissipated far end noise.
Because this is a worst case assumption, it is presumed that the predicted
data rate is at least **** KBPS.
27.
Msg: NOISE-LOSS TOO HIGH FOR DSL ON 24GA

Measured wideband noise prohibits any ADSL service for the measured
loop topology for 24 gauge cable.
28.
Msg: NOISE-LOSS TOO HIGH FOR DSL ON 26GA

Measured wideband noise prohibits any ADSL service for the measured
loop topology for 26 gauge cable.
29.
Msg: NO LOOK-IN ACCESS AVAILABLE

A request was performed which requires look-in capability but the current
access point does not provide this capability.
7-168
Summary Messages
30.
Msg: * NO WIDEBAND ACCESS AVAILABLE

Wideband tests were not performed because appropriate access was not
available. Either the Line Record did not provide wideband access
information, or the test equipment assigned to the loop does not provide
wideband access.
31.
Msg: * NO WIDEBAND TEST EQUIP AVAILABLE

Wideband tests were not performed because the testhead associated with
the line under test is not wideband capable.
32.
Msg: NT1 OR SDSL TERMINATION SEEN

A termination similar to that of an ANSI NT1 was detected on a line which
either via Line Record information or DSL digital results was determined to
be DSL. The termination is probably a SDSL modem, but could be an
ANSI NT1 if the Line Record information was in error.
33.
Msg: PARTIAL TEST DATA RECEIVED

Not enough data was received to compute the length of the line under test
and therefore data rate prediction cannot be done.
34.
Msg: POTS LINE CIRCUIT FOUND ON ADSL LINE

LINE NOT TESTABLE
A CO line circuit that cannot be removed was found on the line. This line
circuit makes the results of all LoopCare tests invalid.
35.
Msg: PREDICTED 24 GA DATA RATE: **** KBPS

Measured wideband noise limits ADSL data rate to the indicated rate for
the measured loop topology for 24 gauge cable
Summary Messages
36.
Msg: PREDICTED 26 GA DATA RATE: **** KBPS

Measured wideband noise limits ADSL data rate to the indicated rate for
the measured loop topology for 26 gauge cable
37.
Msg: PREDICTED DR= **** KBPS>=SUBSCRIBED

The Data Rate Prediction algorithm has calculated that the predicted data
rate is greater than or equal to the subscribed data rate obtained from user
input or from the Loop Terminating Equipment (LTE) digital interface.
38.
Msg: PREDICTED DR= **** KBPS<SUBSCRIBED

The Data Rate Prediction algorithm has calculated that the predicted data
rate is less than the subscribed data rate obtained from user input or from
the Loop Terminating Equipment (LTE) digital interface.
39.
Msg: SHORT DETECTED - POSSIBLE DSL MODEM

This message is displayed when a T-R resistance
40.
Msg: TDR DISPLAY NOT AVAILABLE

The Time Domain Reflectometer Display is not available. The cause may
be that the Bridged Tap data could not be retrieved.
41.
Msg: UP RATE CAN BE IMPROVED TO **** K

* BY REMOVING BRIDGED TAP [#]
The Data Rate Optimization algorithm has calculated that the upstream
data rate can be improved by **** Kbps by removing Bridged Tap [#] from
the loop. The Bridged Tap # matches a bridged tap identified in the Bridged
Tap Test Results section of the Test Results page (see Chapter 2 of the
End User GUI Guide - Data Rate Prediction Feature).
42.
7-170
Msg: UP RATE CAN BE IMPROVED TO **** K
Summary Messages

* BY REMOVING DISTURBER [#]
The Data Rate Optimization algorithm has calculated that the upstream
data rate can be improved by **** Kbps by removing Disturber [#] from the
loop. The Disturber # matches a disturber identified in the Rate
Improvement section of the test results page for Data Rate Optimization
(see Chapter 2 of the End User GUI Guide - Data Rate Prediction Feature).
43.
Msg: USER GUI REQUIRED FOR WIDEBAND DATA

The TV mask from which a LOOP or FULL request was performed is not
capable of displaying the returned wideband results. The End-User GUI is
required.
44.
Msg: WIDEBAND TEST EQUIP FAILURE

The wideband portion of a FULL or LOOP test on a xDSL line was not
performed. This could be caused by an equipment failure in a wideband
test unit or possibly a database error, for example, when a testhead is
flagged in the LoopCare database as being wideband capable but is not
equipped for wideband tests.
45.
Msg: WIDEBAND TESTS NOT DONE

performed. The reason will be noted in a subsequent message.
46.
Msg: WIDEBAND TESTS NOT DONE

* WIDEBAND TEST EQUIP FAILURE
performed. This could be caused by an equipment failure in a wideband
test unit or possibly a database error, for example, when a testhead is
flagged in the LoopCare database as being wideband capable but is not
equipped for wideband tests.
Summary Messages

Summary Messages
1.
Msg: ACTIVE DSL MODEM DETECTED ON LINE

* IMPLIES ZERO LOAD COILS ON LINE
This message is displayed when the xTU-R Detect feature is enabled and
a request that supports the feature is run and detects a DSL modem.
2.
Msg: DSL MODEM DETECTION NOT DONE

This message is displayed when the xTU-R Detect test returns a failure
code.
3.
Msg: NO POTS TERMINATION FOUND ON LINE

This message is displayed when the xTU-R Detect feature is enabled and
a request that supports the feature is run and detects a DSL modem, but
no phone is detected.
If it is known that there is no POTS service on the line (that is, the line
supports stand-alone ADSL service), this message is not displayed.
7-172
Summary Messages
FDR (Frequency Domain Reflectometry

Summary Messages
1.
Msg: FAULT LOCATION TEST NOT DONE

This message is displayed when the tester has submitted the
LOCATOR(X) test request and the system does not perform FDR fault
location measurements. Possible reasons for the display of this message
include:
Excessive foreign voltage was detected.
An active DSL modem was detected and there was no override for
this condition.
There was an open-in condition.
7-174
Summary Messages
Contents
8-2

Overview
The EFFECTS ON TESTING tables in Appendices A through D show the effects

on testing due to specific types of line equipment or service. The DC, AC, and
THERMISTOR SIGNATURE tables in Appendices E, F, and G show the electrical
signatures associated with the various types of line equipment. Appendix H
contains a list of the Protocol Error Codes (PER) provided by the switch, and a
description of what each PER means.
The EFFECTS ON TESTING tables include entry numbers to the DC, AC, and
THERMISTOR tables. For example, to find what effect a range extender has on
testing, you would see that:
REG is in the Narrative column in Appendix A (CO EQUIPMENT

EFFECTS)
REG is associated with byte C2
a REG prevents the Receiver-Off-Hook (ROH) test from being run
the entry to the DC signature table is 19
entry 19 in the DC SIGNATURE table in Appendix E shows that it is valid to

have a DC signature of:
>800 Kohms
T-R
(tip-ring)
>1000 Kohms
<3 volts
T-G
(tip-ground)
>1000 Kohms
<3 volts
R-G
(ring-ground)
8-2

(Continued)
Overview
(continued)
Similarly, if you wanted to know how a key system affected LoopCare, you would
see that:
KEY SYSTEM (byte T8) is in Appendix C (TERM EQUIPMENT EFFECTS)
LoopCare will not run the ROH or ringer tests
the entry to the AC SIGNATURE table in Appendix F is 7
the entries to the THERMISTOR SIGNATURE table in Appendix G are 1, 2

and 3
entry 7 in Appendix F shows that a key system may have an AC signature

in the range of
2-18 Kohms
T-R
>25 Kohms
T-G
>25 Kohms
R-G
entry numbers 1, 2, and 3 in Appendix G show that a key system may have
either a thermistor T-R (with no thermistors T-G and R-G), thermistors T-G
and R-G (with none T-R), or a thermistor R-G (with none T-R or T-G).
8-4
Contents
Release 2.15, December, 2006 A-1
Central Office Equipment Effects on

Testing
Overview
The Central Office field is an input/output field. The tester can override the line
record information retrieved from the LoopCare database and provide to
LoopCare the type of central office equipment that the tester knows is on the line.
If the tester overrides the line record information, this will not change the line
record information in the database. The next time the a tester runs a test on that
particular line, the original line record information will be returned. It is suggested
that the tester inform the system administrator that the line record information is
incorrect so the line record information can be corrected.
Central Office
Equipment and
Effects
Below is a table which lists the following information:
Byte number of the central office equipment
The type of central office equipment
The effects it will have on testing
The allowable signatures
Table B-1.

Allowable
Signaturesb
Byte
Number
Narrative
Effect on Testinga
AC
DC
C1
Office Bridge
MDF test recommended if fault

found on line
C2
Reg
No ROH test
C3
Minibridge Lifter
No ROH or longitudinal balance

tests, AC signature and ringer
tests performed but no opens
analysis
C4
Bridge Lifter

tests, ringer count may be
inaccurate
C5
2A Range
Extended
No ROH test
C6
Loop Sig
Extender
No ROH test
A-2 Release 2.15, December, 2006
19
Allowable
Signaturesb
Byte
Number
Effect on Testinga
Narrative
AC
DC
C7
Phys Pair, Carrier
C8
Phys Pair, SLC-1
C9
Uncataloged
Equipment
No ROH test, AC Signature and

ringer tests performed but no
open analysis
C10
Derived Pair,
Carrier
Physical pair accessed, no

Central Office testing, no ringer
or soak tests
C11
Derived Pair,
SLC-1
Physical pair accessed, no

Central Office testing, no ringer
or soak tests
C12
CREG
No bias voltage used in ROH

test, allow higher voltage for
ESS line-in-use
C13
7A REG
No ROH test in Crossbar

offices, MDF test
recommended if Crossbar linein-use signature
C14
8A REG
No ROH test
C20
LSS
None
C40
SLC-96
Verify the COT signature and

make metallic access
C41
SLC Series 5

C44
Testable DLCS

C81
Relay Bridge
Lifter
Central Office testing only
C82
E6 Repeater
No ROH test
C84
DLL
C85
Remote MSG
Repeater
No ROH test
C86
DLL W/E6
Repeater
Release 2.15, December, 2006 A-3
Byte
Number
Allowable
Signaturesb
Narrative
Effect on Testinga
C87
Loop Sig
Repeater
C88
Uncat Opaque
Equipment
C90
ADSL
ADSL service - testing may

include Data Rate Prediction
C91
ADSL-L
ADSL-Lite service - testing may

C92
SDSL
SDSL service - testing may

C161
U-1 Carrier
C162
SLM
C163
SLC-8
C164
SLC-40
C165
Uncataloged
Carrier
Not testable by LoopCare

AC
DC
a. The effects on testing are only those that are directly caused by the equipment listed. Other
tests may be omitted due to faults found on a line. Also, the Central Office testing consists of
line circuit identification and the draw-and-break dial tone tests.
b. If a piece of equipment has more than one entry to the AC, DC, or Thermistor tables, then any
of the listed signatures are valid.
A-4 Release 2.15, December, 2006
Contents
Release 2.15, December, 2006 B-1

Overview
The Outside Plant field is an input/output field. The tester can override the line
record information retrieved from the LoopCare database and provide to
LoopCare the type of outside plant equipment that the tester knows is on the line.
record information in the LoopCare database. The next time the a tester runs a
test on that particular line, the original line record information will be returned. It is
suggested that the tester inform the system administrator that the line record
information is incorrect so the line record information can be corrected.
Outside Plant
Equipment and
Effects
Below is a table which lists the type of Outside Plant Equipment and their Code.
Byte
Number
Allowable Signaturesb
AC
DC
01
Line
Concentrator
None
02
Bridge Lifter

inaccurate
03
Pressure
Contractor
11
04
Air Dryer
11
05
Pressure
Transducer
06
Uncataloged
Equipment
010
B-2
Effects on Testinga
Narrative
Thermistor
No ROH test, AC signature and

opens analysis
020
None
Used for processing lines

served by single line subscriber
carriers
021
None

carriers
Byte
Number

Effects on Testinga
Narrative
022
None

carriers
034
603 Ringer
Isolator
None
050
D18 Ringer
Isolator
AC Signature test performed

but no opens analysis
051
28A Ringer
Isolator
052
10A Ringer
Isolator

053
11A Ringer
Isolator

054
E6 Repeater
No ROH test
055
DLL

opens analysis
056
Uncat Opaque
Equipment

opens analysis
057
Uncat Ringer
Isolator
AC signature and ringer tests

performed but no opens
analysis
058
DLL with E6
Repeater

opens analysis
0100
Unigauge Loop No ROH test
0101
Unigauge with
Line Conen
No ROH test
0102
Unigauge with
Bridge Lifter

inaccurate
0103
Unigauge with
Press Contact
No ROH test
0104
Unigauge with
Air Dryer
No ROH test
AC
DC
Thermistor
Byte
Number

Effects on Testinga
Narrative
0105
Unigauge with
Press Trans
No ROH test
0106
Unigauge with
Uncat
Equipment

opens analysis
0134
Unigauge with
603 Ringer
Isolator
No ROH test
0150
Unigauge with
D18 Ringer
Isolator

opens analysis
0151
Unigauge with
28A Ringer
Isolator

opens analysis
0152
Unigauge with
10A Ringer
Isolator

opens analysis
0153
Unigauge with
11A Ringer
Isolator

opens analysis
0154
Unigauge with
E5 Repeater

opens analysis
0155
Unigauge with
DLL

opens analysis
0156
Unigauge with
Uncat Opaque

opens analysis
0157
Unigauge with
Uncat Isolator

opens analysis
0158
Unigauge with
DLL and E6
Repeator

opens analysis
AC
DC
Thermistor
a. The effects on testing are only those directly caused by the equipment listed. Other tests may be omitted due
to faults found on the line.
B-4
b. If a piece of equipment has more than one entry to the AC, DC or Thermistor tables, then any of the listed
signatures are valid.
B-6
Contents
Release 2.15, December, 2006 C-1

Overview
The Termination Equipment field is an input/output field. The tester can override
the line record information retrieved from the LoopCare database and provide to
LoopCare the type of outside plant equipment that the tester knows is on the line.
record information in the LoopCare database. The next time the a tester runs a
test on that particular line, the original line record information will be returned. It is
suggested that the tester inform the system administrator that the line record
information is incorrect so the line record information can be corrected.
Termination
Equipment and
Effects
Below is a table which lists the type of Termination Equipment and their Code.
Byte
Number
Allowable Signaturesc d
Effects on Testinga b
Narrative
AC
T1
Single Party
None
T2
Two Party
No longitudinal balance test, no 13,1

capacitive balance or distance
information (neither length of
loop nor open distances)
T3
Multi-Partye
T4
Coin
Certain line circuit

configurations permitted, and
ground supplied to draw dial
tone when needed
T5
Chimes
5,11
T6
Dummy Ringer
5,11
T7
Tone Ringer
5,11
T8
Key System
No ROH or ringer tests
T9
505 PBX
T10
506 PBX
T11
507 PBX
DC
Thermistor
5, 11
1,2,3
1,2
C-2 Release 2.15, December, 2006
Byte
Number

Narrative
AC
DC
Thermistor
T12
550 PBX
T13
551 PBX
T14
552 PBX
T15
555 PBX
1,2
T16
557 PBX
1,2
T17
558 PBX
T18
607 PBX
T19
608 PBX
t20
701 PBX
30,36 1
T21
Two Party One Disc
No longitudinal balance test, no 9,11

capacitive balance or distance
information (neither length of
loop nor open distances)
T22
740 PBX
T23
750 PBX
T24
755 PBX
T25
756 PBX
30,36
T26
757 PBX
30,36
T27
761 PBX
30,36
T28
770 PBX
30,36
T29
800 PBX
38,42
T30
801 PBX
38,42
T31
805 PBX
30
T32
812 PBX
30,36
T33
Uncataloged
PBX
No ROH or ringer tests, AC

signature tests performed but
no opens analysis
1,2,3
T34
Uncataloged
Termination

opens analysis
1,2
30,36 1
Byte
Number

Narrative
AC
DC
Thermistor
T35
605 PBX
T36
1000 Data
Coupler
T37
1001 Data
Coupler
T38
3A Data
Coupler
None
T39
401H Data Set
T40
Auto Reporting
Telephone
T41
401L Data Set
T42
Dimension PBX No ROH or ringer tests
40
T43
PBX Coupler
32,33 1
T44
Station Coupler No ROH or ringer tests
T45
Key Set
Coupler
T46
711 PBX
30,36 1
T47
Horizon
T50
Class A PBX
1,2,3
T51
Class B PBX
1,2,3
T52
Class C PBX
1,2,3
T61
Centrex-CU
T62
Centrex-CO
T63
101 ESS
T64
Outward Wats
5,11
T65
Inward Wats
5,11
T66
101C Data Set
T67
103 Data Set
5,11
5,11

T68
113 Data Set
T69
201 Data Set
Byte
Number

Narrative
AC
DC
Thermistor
T70
202 Data Set
T71
203 Data Set
T72
208 Data Set
T73
212 Data Set
T74
401 Data Set
T75
402 Data Set
T76
403 Data Set
T77
407 Data Set
T78
601 Data Set
T79
603 Data Set
T80
604 Data Set
T81
Uncataloged
Data Set
7
No ROH or ringer tests, AC
signature test performed but no
open analysis
T87
Coinless Public
Telephone
T98
Four Party

tests performed but no open
analysis, no capacitive balance
printed. Also used to determine
correct ringing signal.
T99
Eight Party

tests performed but no opens
analysis, no capacitive balance
printed. Also used to determine
correct ringing signal.
Tnullf
None
Permits recognition of various

types of terminations
5,9,
11,15
1,2,3
a. The effects on testing are only those that are directly caused by the equipment listed. Other tests may be
omitted due to faults on a line.
b. Length of loop will only be provided for the following terminations: Single Party (T1), Centrex CO (T62), Coin
(T4), and No termination (Tnull).
c. If a piece of equipment has more than one entry to the AC, DC, or Thermistor tables, then any of the listed
d. The thermistor test is performed under either of the following conditions: 1. If the AC signature does not match
the entry in Appendix F, and a thermistor signature is expected. 2. If the AC signature does not match the
entry in Appendix F, and a thermistor signature is not expected, and the measured tip-ring AC resistance is
between 20 Kohms and 100 Kohms
e. The Multi-Party (T3) is used for greater than eight party service.It was previously used for four and eight party
lines, and must still be used for these lines with old Front End software releases.
f. No termination - Tnull - is set by the Front End when there is no line record available or the line record
termination has been overridden.
Contents
Release 2.15, December, 2006 D-1

Below is a table which lists the type of Special Effects on Test and their Code.
Special Effects
Byte
Number
Narrative
TAC
AC
DC
Thermistor
15,22
INWARD
No Central Office Testing.
PROT
Customer permission required

for testing.
HUNT
Certain line circuit

configurations permitted, and
ground supplied to draw dial
tone when needed.
PARTY#
Used to determine type of

ringing signal.
NBR OF
RINGERS
Compared with number of

ringers measured.
ASSOC TEST
TN
Number accessed for testing.
F1
NEON LAMP
F2
LSI
F3
REMOTE FWD *Not testable by either LTF or

LoopCare.
F4
INT PGS
No central office testing; no

MDF testing.
F5
TOUCHTONE
Used in LoopCare when calling

on a subscribers line
F6
STV TEST
Indicates the line is non-locally

switched, served by a DLCS,
and can only be accessed
through LoopCare with the
Special Services Access (SSA)
request from an STV mask.
D-2 Release 2.15, December, 2006
Byte
Number

Narrative
F7
NON
SWITCHED
None at present
F8
FOUR WIRE
Used in LoopCare to disallow

certain tests for 4-wire circuit
accessed via the SSA request
from an STV mask.
F9
DPA
REQUIRED
Indicates a multi-legged circuit

with at least one leg testable by
a Remote Measurement Unit
(RMU). The Different Premises
Address (DPA) information
allows LoopCare to know which
legs are RMU-testable.
AC
DC
Thermistor
a. The effects on testing are only those that are directly caused by the equipment listed. Other tests may be
omitted due to faults on a line.
b. Length of loop will only be provided for the following terminations: Single Party (T1), Centrex CO (T62), Coin
(T4), and No termination (Tnull).
c. If a piece of equipment has more than one entry to the AC, DC, or Thermistor tables, then any of the listed
d. The thermistor test is performed under either of the following conditions: 1. If the AC signature does not match
the entry in Appendix F, and a thermistor signature is expected. 2. If the AC signature does not match the
entry in Appendix F, and a thermistor signature is not expected, and the measured tip-ring AC resistance is
between 20 Kohms and 100 Kohms
Release 2.15, December, 2006 D-3
D-4 Release 2.15, December, 2006
Valid DC Signatures
Contents
Valid DC Signatures
Release 2.15, December, 2006 E-1
Valid DC Signatures
Valid DC Signatures
DC Signatures
Resistance (Kohms)
Ent. No.
T-R
T-G
Voltage (V)
R-G
T-G
R-G
Equipment allowing
this signature
(Notes a b c d)
>12
>1000
>1000
<3
<3
C7, C8, C10, C11
>20
>1000
>1000
<3
<3
F1
>35
>1000
>1000
<3
<3
C5
>90
>1000
>1000
<3
<3
C6
>90
>1000
>1000
<3
<3
O5, O105, F2
>150
>1000
>1000
<3
<3
O51, O57, O151,

O157
11
>270
>1000
>1000
<3
<3
O3, O4, O103, O104
15
>400
>1000
>1000
<3
<3
TAC
19
>800
>1000
>1000
<3
<3
C2
22
>1000
>1000
>1000
<3
<3
TAC
30
18-29
>200
>200
32
>54
27-35
>200
18-29
<3
T43
33
>54
27-35
27-35
18-29
18-29
T43
35
>54
7-13
7-13
40-55
40-55
36
>54
7-13
>200
40-55
<3
T20, T22, T25, T26,

T27, T28, T32, T46
38
>54
27-35
>200
40-55
<3
T29, T30
40
>54
7-20
27-35
40-55
40-55
T42
42
>54
27-35
27-35
40-55
40-55
T29, T30
50
17-30
25-35
>200
<3
<3
SLC96 COT (coin)
51
>200
145-190
>200
<3
<3
SLC96 COT (other)
60
>1000
75-90
75-90
-(9-14)
-(9-14)
MFT Loop Sig Ext
T20, T22, T25, T26,

T27, T28, T32, T46
E-2
Valid DC Signatures
Resistance (Kohms)
Ent. No.
T-R
Voltage (V)
T-G
R-G
T-G
R-G
Equipment allowing
this signature
(Notes a b c d)
62
>1000
50-1000
50-1000
-(55-65)
-(55-65)
Digital Carrier
63
>1000
30-40
30-40
-(36-40)
-(36-40)
Digital Carrier
64
>1000
140-150
140-150
-(40-48)
-(40-48)
Digital Carrier
a. Lines without special equipment are expected to have all resistances (T-R, T-G, R-G) >1000 Kohms, and all voltages (T-R,
T-G, R-G) <3 volts.
b. A piece of equipment may have more than one valid DC signature
c. Entries 32 through 42 are ground-start PBXs. Recognition of any of any of these signatures is permitted for a ground-start
PBX.
d. Voltages listed for entries 60 through 64 indicate negative values.
Release 2.15, December, 2006 E-3
E-4
Valid DC Signatures
Valid AC Signatures
Contents
AC Signatures
Release 2.15, December, 2006 F-1
Valid AC Signatures
AC Signatures
NOTE:
The signatures listed in the following table apply to mechanical ringers, and
the values may vary with other types of equipment, such as Tone Ringers.
Table of AC
Signatures
Resistance (Kohms)
Entry Number
T-R
T-G
R-G
Equipment allowing this

signature a b
1-10
>25
>25
C7, C8
1-13
>25
>25
T9, T10, T23, T24
1-20
>25
>25
T1, T4, T5, T6, T7, T44,

T62, T64, T65, T87, Tnull
2-18
>25
>25
T8, T36, T37, T39, T40,

T41, T47, T66, T67, T68,
T69, T70, T71, T72, T73,
T74, T75, T76, T77, T78,
T79, T80, T81 (Note c
>25
1-20
>25
T21, Tnull
11
>25
>25
1-20
T1, T5, T6, T7, T21, T44,

T62, T64, T65, Tnull
13
18-25
1-20
1-20
T2
15
>25
1-20
1-20
T2, Tnull
a. A piece of equipment may have more than one valid signature.

b. No termination - Tnull - is set by the Front end when a line is tested with no termination information (e.g., no
line record, or override termination condition).
c. For all terminations except ground - start PBXs, entry 7 is an allowable signature
F-2
Contents
Release 2.15, December, 2006 G-1

Thermistor
Signatures Table
Valid Thermistor Configurations (Note a
Entry Number
T-R
T-G
R-G
Equipment allowing this

configuration (Note b
yes
no
no
T8, T11, T12, T13, T14,

T15, T16, T17, T18, T19,
T20, T22, T25, T26, T27,
T28, T33, T34, T35, T36,
T37, T43, T45, T46, T50,
T51, T52, T66, T67, T68,
T69, T70, T72, T73, T77,
T81, Tnull
no
yes
yes
T8, T11, T15, T16, T33,

T34, T50, T51, T52, Tnull
no
no
yes
T8, T33, T50, T51, T52,

Tnull
a. A piece of equipment may have more than one valid thermistor configuration
b. No termination - Tnull - is set by the Front End when a line is tested with no termination information (e.g.,
no line record, or override termination connection).
G-2
Contents
Release 2.15, December, 2006 H-1

Error Codes Tables
ABN NET RESET
-X.25
Network received an abnormal reset request for

the local DTE interface for which the local
interface did not originate a request.
ABNORMAL CLR REG
-X.25
Received a clear request packet from remote

DET or network which was not solicited by the
local DTE
ABNORMAL RESET
-X.25
A reset request packed was received from the

remote DTE for which the DCE did not
originate.
ABNORM RESTART
-X.25
Network received an abnormal restart request

for local DTE interface for which the local
interface did not originate request.
BAD BYTE COUNT
-LAPB/
LAPD
The frame was rejected due to a bad byte count

within the frame.
BAD CLASS
-Q.931
The clearing message indicated that the call

was terminated due to a non-normal event. It
was reported in the class code of the cause
information element.
BAD SETUP INFO
-Q.931
The message received did not contain

mandatory information elements.
BEAR CAP INV
-Q.931
The message contained an invalid bearer

capability information element.
BEAR CAP MISS
-Q.931
The message contained no bearer capability

CAC FAIL
-Q.931
The call activity check procedure failed. No

response was received to the STATUS INQuiry
message transmitted from the switch.
CALL AP GLARE
-Q.931
The message contained call appearance glare.
CALL COLLISION
-X.25
Call request received for logical channel that is

in the process of clearing.
CALL EXISTS
-Q.931
A call setup message was received when a call

already existed.
H-2
CALL NOT D/F
-Q.931
A message with a display or features

information element was received when no
display or feature process was active.
CALL REF GLOB
-Q.931
The GLOBAL call reference value was used

improperly. Only the RESTART and
management informations (MIMs) are allowed
to use the global call ref.
CALL REF ILLEG
-Q.931
The message contained an illegal call reference

CALL REF MISS
-Q.931
The message contained no call reference

CALL REF NULL
-Q.931
The message received illegally used a null call

reference value to identify a call. Only the
INFOrmation message is allowed to use the
null call ref.
CAUSE MISSING
-Q.931
A message was received missing a mandatory

cause information element.
CHAN ID INV
-Q.931
The message contained an invalid channel

identifier information element.
CHAN ID MISS
-Q.931
The message contained no channel identifier

CHAN NEGO NIMP
-Q.931
The message requested channel negotiation,

which is not currently implemented.
CHAN NOT AVAIL
-Q.931
The channel specified by the message was

unavailable.
CHAN NOT PRI B
-Q.931
A feature specific to extended digital subscriber

line (EDSL) B-channels was requested in a
message containing a channel identifier that did
not denote an EDSL B-channel.
CHG STAT MISS
-Q.931
The message contained no change status

CLAIM CLR
-X.25
The call was cleared because of called line

address modified notification procedure errors.
CLR REQ
-X.25
Received packet indicates that clear

procedures for local DTE interface have been
initiated.
CONFIRM RESET
-X.25
Received reset request in state for which the

interface has already been reset. DCE
responded to reset request which reset
confirmation.
CPE MSG UNEXP
-Q.931
A message was received from the customer

premises equipment (CPE) while the call was in
a state in which none was expected.
CRC ERR
-LAPB/
LAPD
The frame was rejected due to a bad cyclic

redundancy code (CRC).
DCE RESET
-X.25
Received an invalid packet that resulted in a

reset of the local interface from the DCE.
DGN PKT
-X.25
Interface entered restart procedures; packets

pending DCE or network acknowledgments are
discarded.
DISCARD PKTS
-X.25
Interface entered restart procedures; packets

pending DCE or network acknowledgments are
discarded.
DS1/0 MISMATCH
A DS1/DSO mismatch in CONnect or CONnect

Acknowledgment has occurred.
DTE RESET
-X.25
Received an invalid packet while in the DTERSE- REQ state.
DTE RESTART
-X.25
Received an restart request packet from the

DTE while a virtual circuit was active.
DYN DATA ERROR
Unable to store an incoming segment in an

RTMSGBUF or transmit the segments which
constitute a ROSE APDU due to a dynamic
data related failure.
ELEMENT MISSIN
A message was received that was missing one

or more mandatory elements.
EPID NOT FINS
-Q.931
An origination was rejected because the

identification procedure has not finished.
EXP RST CONF
-X.25
Received a packet while in the DCE-RST-IND

state. All packets except the restart
confirmation are discarded.
FA KEY MEXCL
-Q.931
The message contained both feature activation

and keypad information elements.
FA/SWHK MISS
-Q.931
The message contained no feature activation

switch-hook information element.
H-4
FRAME ABORT
-LAPB/
LAPD
Level 1 received an abort signal during

transmission/reception of the frame.
FRAM OUT SEQ
-LAPB/
LAPD
The frame was received out of sequence.
FRAM REJ
-LAPB/
LAPD
A frame reject was received from the customer

premises equipment.
FRAME TOO LONG
-LAPB/
LAPD
The frame exceeded the maximum total frame

size for the interface.
FRM UNEXPECTED
-LAPB/
LAPD
The frame is unexpected for the current logical

link state.
FRM UNNUMBERED
-LAPB/
LAPD
Received an unexpected unnumbered frame.
I FIELD EXPECT
-LAPB/
LAPD
The frame did not contain an information field

that was expected.
I FLD LEN -REJ
-LAPB/
LAPD
The frame contained an information field that

exceeded the maximum information field size
for the interface.
IDLE CHAN TIMR
-LAPB/
LAPD
The idle channel timer expired indicating an

excessive idle channel condition.
ILL NUM FORMAT
-Q.931
A SETUP message was received with an illegal

destination address. Possible conditions are
that the called party number (CdPN) or transit
network selection (TNS) information element
(IE) contained an unimplemented type of
number, the operator system access (OSA) IE
contained an unimplemented type of access, or
the CdPN received in a Keypad, TNS, or OSA
IE was unknown.
ILLEGAL ADDR
-LAPB/
LAPD
The frame contained an illegal address field.

ILLEGAL IES
ILLEGAL SPID

-Q.931
-Q.931
This PER only applies to the National ISDN

standard interface. An INFOrmation message
containing a service profile ID (SPID) cannot
contain a non-null call reference value or other
information elements (IEs). For example:
1.
An INFO message was received with a

SPID and an existing non-null call
reference value.
2.

SPID, an existing non-null call reference
value, and other IEs.
3.

SPID, other IEs, and the null call
reference value.
This PER only applies to the National ISDN

standard interface. An illegal SPID was
received for one of the following reasons:
1.
the SPID was not assigned to the

interface
2.
the SPID received is currently active
3.
a SPID was received from a CPE with an

active call
4.
the SPID had the wrong format
5.
the SPID contained invalid data
INC CALL BARR
-Q.931
The destination side of the call has incoming

calls barred.
INC MSG
-Q.931
The message received was incompatible for the

interface (custom versus standard).
INFO ELEM ERR
A message was received that contained an

information element content error.
INFO ELEM MISS
A message was received that was missing a

mandatory information element.
INFO TOO LOGN
-Q.931
The message exceeded the maximum allowed

length.
INT FACIL ERR
-X.25
Local DCE received internal network packet

containing facility errors. Packet re-formatted
without errors and transmitted to DTE.
H-6
INTR PKT80 RST
-X.25
An Interrupt packet from the network contains

more than one byte of interrupt data. This is
disallowed for a DTE using the 1980 X.25
version and the call is reset. This applies to
software releases 5E6(1) and later.
INV CALL REF
-Q.931
The message received contained an invalid or

unallocated call reference value in the call
reference information element.
INV COMND/RESP
-LAPD
The frame contained an invalid command/

response (C/R) field.
INV CR SUFFIX
A message was received with an invalid call

reference suffix.
INV CR VALUE
A message was received with an invalid call

reference value.
INV E BIT
A segment was received with an invalid

Extension (E) bit value.
INV ERR CNTL
A segment was received with an invalid Error

Control (C1 and C2 bits) value.
INV I FLD -REJ
-LAPB/
LAPD
The frame contained an invalid information

field.

INV IE

-Q.931
INV INVOKE ID
The SETUP message received contained one

or more invalid information elements (IEs).
Therefore, the switch was not able to transfer
the calling party subaddress information
element to the receiving switch for the following
conditions:
1.
The calling party number IE or the call

appearance IE were not present in the
SETUP message.
2.
The calling party subaddress (CgPS) IE

was less than 5 octets in length.
3.
The ISDN calling number identification

service was not subscribed to. An initial
SETUP message was received with a
bearer capability IE for a packet-mode
access connection and also incorrectly
contained one or more of the following
optional IEs: low layer compatibility
(LLC), high layer compatibility (HLC),
called party subaddress (CdPS), or
CgPS.
The message contained an invalid invoke ID.
INV MAN INF EL
-Q.931
The message contained an invalid

management information element.
INV N/R FSD
-LAPB/
LAPD
The N(R) sequence field in the frame header

contained an invalid value.
INV OBJ CLASS
The object class of a message is invalid.
INV OBJ INST
The object instance of a message is invalid.
INV OPERATION
The CMIP operation is invalid.
INV PKT - CLR
-X.25
Received an invalid internal message from the

network at the DCE. The virtual circuit was
cleared.
INV PKT LENGTH
-X.25
The received packet has an invalid length. The

received packet was discarded.
INV PKT SIZE
-X.25
The received packet had an invalid length. The

INV PROTO DISC
-Q.931
The message received contained an invalid

protocol discriminator.
H-8
INV T NET SPEC
Q.931
The clearing message indicated that the call

could not be routed because of an invalid
transmit network specification.
INVALID HEADER
-LAPB/
LAPD
The frame contained an invalid header field.

INVALID SAPI- LAPD- The SAPI field in the
frame header was invalid.
INVALID TEI
-LAPD
The TEI field in the frame header was invalid.
IP NET RESET
-X.25
Received an invalid packet from the DTE or an

invalid internal message from the network. The
local interface is reset from the DCE.
KEY INVALID
-Q.931
The message contained an invalid keypad

KEY MISSING
-Q.931
The message contained no keypad information

element.
KEY NO DISPLA
-Q.931
A message with a keypad information element

was received when no display process existed.
LINK DOWN
-X.25
The packet-level state is NOT-INIT. The

LOCAL ERROR
-X.25
Local procedure error was detected for the DTE

call request.
LONG CALL REF
-Q.931
The message received contained a call

reference value with a length greater than two
bytes.
MCA CONGESTION
-Q.931
All call appearances were busy for a multiple

call appearance (MCA) line.
MCA NON SUB
-Q.931
The message requested MCA for a nonsubscribing D-channel.
MSG TYPE INV
-Q.931
The message contained an invalid message

type information element.
MSG UNEXPECTED
-Q.931
The message was unexpected given the state

of the call.
MULT B CHAN
-Q.931
The message specified more than one Bchannel.
MULT CALL PROC
-Q.931
More than one call-proceeding message was

received
NET CONGESTION
-X.25
Insufficient resources were available to

establish the requested virtual circuit. The call
request attempt was denied.
NET CONGESTION
-Q.931
The call could not be completed because of

network congestion.
NET RESTART IP
-X.25
Received a packet in state DCE-RST-IND. The

NEW STAT INV
-Q.931
The message contained an invalid new status

NO CALL
-Q.931
The message received was irrelevant as no call

existed.
NON TMF SWHK
-Q.931
A CPE that does not subscribe to the terminal

management function (TMF) sent a message
containing a switch-hook information element.
OBJ CL MISMTCH
The object class of a message does not match

what is expected.
OBJ INST MISMA
The object instance of a message does not

match what is expected.
OCA MISSING
-Q.931
The message contained no origination call

appearance information element.
ODD READ ERROR
-Q.931
Failure to read the office dependent data.
OPER MISMATCH
OTHER CRV INV
The CMIP operation does not match what is

expected.
-Q.931
OSDS ERROR
The message contained an invalid other call

reference information element.
Unable to transmit the segments which
constitute a ROSE APDU due to an OSDS
related failure.
PORT OOS
-Q.931
Destination port was out-of-service.
PRI ODB N IMPT
-Q.931
On-demand B (ODB) channel packet switching

is not implemented for the primary rate
interface (PRI).
PVC OUT ORDER
-X.25
Received an internal message at the DCE

indicating that the permanent virtual circuit
(PVC) is out of order at the remote interface.
The local interface has been reset.
H-10
PVC RESET
-X.25
The local interface procedures indicate that the

PVC should be placed out of order. The local
interface has been reset.
PVN D CALL BAR
-Q.931
Origination of data calls is barred on digital

subscriber lines dedicated to PVNs.
R FACIL 80 CLR
-X.25
An X.25 facility is present in a call request or

call connected packet received from the
network, which is not supported by the local
DTE. The local DTE is using 1980 X.25 version
and the packet is coming from a 1984 DTE.
This applies to software releases 5E6(1) and
later.
RCVD ABORT
Received an ABORT segment.
RCVD BEGIN
Received a BEGIN segment while in the

MIDDLE STATE.
RCVD NONBEGIN
Received a non-BEGIN segment while in the

BEGIN STATE.
REJ NON SYS OP
-Q.931
A non synchronous operation reject

management information message was
received.
REJ PR VIO MIM
-Q.931
A protocol violation reject management

information message was received.
REJ SEMI PERM
RT rejects the DS1/DSO because it is believed

to be semi-permanent. This can occur when
either the terminating side sends a SETUP
message or the originating side sends a
CONnect message.
REJ UNK OP MIM
-Q.931
An unrecognized operation reject management

REJ UNSPEC MIM
-Q.931
An unspecified error reject management

REJECT CKT OOS
RT rejects the setup message because the

circuitry is out-of-service.
REJECT PRETRIP
RT rejects the SETUP message because of the

failure of the ring pretrip test.
RELS NO CALL
-Q.931
A release request was received when no call

was in progress.
REQ SVC NSUB
-Q.931
Request does not match subscriber services.

RESET OOO IP
-X.25
The local interface was placed out-of-service

unconditionally. The local interface DCE sent
an internal restart request to the network.
RETRY EXCEEDED
-LAPB/
LAPD
The transmission retry count for the frame was

exceeded.
ROUTE FAIL -CLR
-X.25
Call request attempt failed during network

internal routing. DCE cleared virtual call
request.
RST IND INV
-Q.931
The message contained an invalid restart

indicator information element.
RST IND MISS
-Q.931
The message contained no restart indicator

RTMSGBUF EXHAU
RTMSGBUF free pool exhaustion has

occurred.
RTMSGBUF LIMIT
The maximum number of RTMSGBUF tuples

allowed per ROSE APDU has been exceeded.
SHORT MESSAGE
-Q.931
The message received contained less than 4

bytes of information.
SHORT PKT
-X.25
Received a packet that did not contain the

minimum allowed information. Diagnostic
packet sent to DTE indicating this condition.
STANDBY EOC
A message was received on standby EOC.
STANDBY TMC
A message was received on the standby TMC.
SWITCH TIMEOUT
The V.120 layer timed out waiting for a path

switch to complete, no segments of the APDU
were transmitted.
SYSTEM ERROR
-Q.931
A system error has occurred.
T10 TIMEOUT
-X.25
Timer T10, delay between the DCE

transmission of a restart indication packet to
DCE reception of a restart confirmation packet,
has expired. Restart procedures have been reinitiated from the DCE.
T10 2ND TIMOUT
-X.25
Timer T10, delay between DCE transmission of

a restart indication packet to DCE reception of a
restart confirmation packet, has expired for the
second time. Diagnostic packet send to DTE.
H-12
T11 TIMEOUT
-X.25
Timer T11, delay between DCE transmission of

the incoming call packet to the DCE reception
of the call accept packet, has expired.
Diagnostic packet sent to the DTE.
T12 TIMEOUT
-X.25

transmission of a reset indication packet to
DCE reception of a reset confirmation packet,
has expired. Reset procedures have been reinitialized from the DCE.
T12 2ND TIMEOUT
-X.25

transmission of a reset indication packet to
DCE reception of a reset confirmation packet,
has expired for the second time. The network
has been notified that local interface is out of
order.
T13 TIMEOUT
-X.25

transmission of a clear indication packet to
DCE reception of clear confirmation packet, has
expired. Clear procedures have been reinitiated from the DCE.
T301 TIMEOUT
-Q.931
Timer 301, delay from CPE-transmitted callalerting message to CPE-transmitted callcollect message, expired.
T303 TIMEOUT
-Q.931
Timer 303, delay from network transmitted call

setup message to CPE response, expired.
T305 TIMEOUT
-Q.931

disconnect message to CPE call disconnect or
release response, expired.
T308 TIMEOUT
-Q.931

release message to CPE call release complete
response, expired.
T310 TIMEOUT
-Q.931
Timer 310, delay from CPE transmitted call

proceeding message to CPE transmitted call
alerting or connect message, expired.
T313 TIMEOUT
-Q.931
Timer T313 (delay from CONNect to CONNect

ACKnowledge) expired.
T320 EXP
-X.25
Timer 320 expired while waiting for layer 2 to

come up.
T322 TIMEOUT
Timer T322 expired. STATus ENQuiry

message response timer expired.
T377 TIMEOUT
-Q.931
Timer T3YY, delay from on-demand packet Bchannel connection to B-channel level 2 peer
protocol establishment request, expired.
TERM MISMTCH
-Q.931
A message was received indicating a mismatch

between the protocol version used by the CPE
and that specified for the interface. Either a
management information message (MIM) was
received on a standard interface, or an
INFOrmation message with service profile ID
(SPID) information element (IE) was received
on a custom interface. The most probable
cause of this protocol error was that the wrong
type (standard or custom) of ISDN terminal was
connected to the interface.
TERM NOT INSP
-Q.931
The CPE was not in inspect mode.
TIMER EXPIRED
TMF OTHER CR
A timer fired while waiting for a response for a

specific CMIP operation.
-Q.931
A message was received from a terminal

management function (TMF) terminal which
contained an unexpected other call reference
TRAN OVERFLOW
The transmitter was unable to successfully

write a segment to the PI FIFO due to FIFO
overflow.
TRANSMITR FAIL
The transmitter was unable to successfully

write a segment to the PI FIFO for reasons
other than a PI FIFO overflow.
TSC EXCEEDED
-X.75
UNASSIGND LINE
The switch cleared the call because the transit

subnetwork count was exceeded.
An unassigned line is generating message
traffic.
UNEXP FRM -REJ
-LAPB/
LAPD
The frame is unexpected for the current logical

link state.
UNEXP I FIELD
-LAPB/
LAPD
The frame contained an unexpected

information field.
UNEXPECTED MSG
-Q.931
The message was unexpected for the given

state of the call.
H-14
UNKNOWN ERROR
-LAPB/
LAPD
Error code for detected event currently

undefined. Reserved for future expansion.
UNKNOWN ERROR
-X.25
State not known. See technical assistance.
UNKNOWN ERROR
-Q.931
The detected error was unknown. Reserved for

future PECs.
UNKNOWN FRM
-LAPB/
LAPD
The frame type is unknown.
UXP MAN INF EL
-Q.931
An unexpected management information

element was received.
X FACIL 80 CLR
-X.25
An X.25 call request or call connected packet to

be sent to the DTE contains a facility length
field greater than 63 octets, which is disallowed
for a DTE using 1980 X.25 version. This applies
to software releases 5E6(1) and later.
H-16
DN RATE CAN BE IMPROVED TO **** K * BY REMOVING

BRIDGED TAP, 7-165
DN RATE CAN BE IMPROVED TO **** K * BY REMOVING
DISTURBER, 7-165
UP RATE CAN BE IMPROVED TO **** K * BY REMOVING
BRIDGED TAP, 7-170
UP RATE CAN BE IMPROVED TO **** K * BY REMOVING
DISTURBER, 7-170
Index
Symbols
Summary Messages
A
AC, 2-20
AC Resistance, 1-12
AC Signature Summary Messages, 7-15, 7-16

AC Signature Test, 1-17
AC Signatures
Valid, F-1
AC Voltage, 1-11
Access Tests, 1-13
ADSL Splitter Signature Summary Messages, 7-16
ADTRAN 3000 Summary Messages, 7-17
Analysis
LoopCare System, 1-12
B
BATTERY IS PROVISIONED, BUT MISSING, 7-54
BATTERY PRESENT, BUT WILL NOT RECHARGE, 7-54
BOARD INSTALLATION ALARM, 7-54
BOARD INSTALLATION ALARM (SB CARD), 7-54
BOARD INSTALLATION MISSING ALARM, 7-54
BOARD INSTALLATION MISSING ALARM (SB CARD, 7-55
BOARD MISSING ALARM, 7-55
BOARD MISSING ALARM (SB CARD), 7-55
BOARD RESET PROTECTION, 7-55
BOARD RESET PROTECTION (SB CARD), 7-55
BOARD TYPE MISMATCH, 7-55
bPON, 2-38, 2-59
bPON Summary Messages, 7-24
Release 2.15, December, 2006 -1
Index
C
Capacitive Balance Measurement, 1-19
CELL PHASE ERROR, 7-55
Central, A-1
Central Office Equipment Effects on Testing, A-2
Codes
Protocol Error, H-1
Coin Tests, 1-23
CROSS, 2-19
D
DC Resistance, 1-10
DC Resistance Test, 1-15
DC Signature Raw Data, field on the custenv screen, 1-10
DC Signatures
Valid, E-1
DC Tests, 1-15
DC Voltage, 1-11
DC Voltage Test, 1-16
DEFENSE ALARM, PLUG-IN UNIT DISCONN (SB CARD), 7-56
DEFENSE ALARM, PLUG-IN UNIT DISCONNECTED, 7-55
Dial Test, 1-22
Digtest Test, 1-24
DOWNSTREAM CELL DISCARD, 7-56
Draw and Break Dial Tone Test, 1-20
E
END-TO-END VC-RDI GENERATING INDICATION, 7-56
Equipment
Outside Plant, B-2
Termination, C-1
F
FEMF, see Foreign Electromotive Force
Foreign Electromotive Force (FEMF) Tests, 1-13
H
HAZARDOUS, 2-20
-2
Index
I
impact of bPON testing, 2-4
Intercept Test, 1-15
ISDN Tests, 1-24
L
Length of Loop Measurement, 1-21
Line Circuit Test, 1-19
Line in Use Tests, 1-14
Linespecs Test, 1-25
Longitudinal Balance Test, 1-18
LoopCare System
Analysis, 1-12
M
Measurements, 1-9
AC Resistance, 1-12
AC Voltage, 1-11
DC Resistance, 1-10
DC Voltage, 1-11
MODULE, 7-59
N
NETWORK ELEMENT (OR PART) NOT PROVISIONED, 7-59
NETWORK ELEMENT (OR PART) OOS, 7-59
NETWORK ELEMENT OUT OF SERVICE, 7-59
NO METALLIC TEST FACILITY, 7-111
NPANXX OVERLAYED OPTION EWUIEWS, 7-111
NT1 SENT DYING GASP, 7-78
O
Opens Test, 1-18
Other Terminations
AC Test, 1-17
Outside Plant Equipment, B-2
Index
P
PBX Identification Test, 1-16
PEC, see Protocol Error Codes, H-1
Per Test, 1-26
PML1 Test, 1-27
PML2 Test, 1-28
PML3 Test, 1-29
POTS Terminations, AC Test, 1-17
Protocol Error Codes (PEC), H-1
R
Receiver Off Hook (ROH), 1-14
Resistive Fault Sectionalization Tests, 1-23
Restore Test, 1-30
Results
Detailed, 1-4
Results Section
General Rules, 1-8
Ringer Test, 1-20
ROH, see Receiver Off Hook
RSA Line 24 Messages, 6-1
S
SELF TEST FAILURE, 7-62
Signatures
AC, F-1
DC, E-1
Thermistor, G-1
Soak Test, 1-20
Special Effects on Testing, D-1
Specialized Tests, 1-22
Status Test, 1-30
Summary Messages
*POTS CALL MAINTAINED, 7-29
500 FT. MAX. ERROR IN DISTANCE, 7-121
5ESS TRAFFIC BUSY - ACCESS DROPPED, 7-70
5ESS TRAFFIC BUSY - NON-VERIFIABLE, 7-70
5ESS TRAFFIC BUSY - ONLY TALK, 7-70
5ESS TRAFFIC BUSY - VERIFIABLE, 7-70
A RELAY POLARITY GUARD-POSS FAULT, 7-40
AC FEMF CURRENT, 7-12
AC FEMF FAULGCANT MEASURE VOLT, 7-10
AC FEMF FAULT R-G ***** V, 7-12
AC FEMF FAULT T-G ***** V, 7-10
AC FEMF MARGINAL R-G ***** V, 7-12
AC FEMF MARGINALT-G ***** V, 7-11
-4
Index
AC IMPEDANCE IS OUT OF TOLERANCE, 2-15, 7-20

AC Signature, 7-15
AC SIGNATURE NOT DEFINED, 7-15
AC SIGNATURE NOT EXPECTED FOR PBX, 7-136
ACCESS DROPPED, 7-121
ACTIVE DSL MODEM DETECTED ON LINE, 7-172
ADSL C.O. SPLITTER SIGNATURE FOUND, 7-16, 7-164
ADTRAN TA 3000, 7-17
AGREE WITH TERMINATION CODE, 7-139
ALL TIMING REFERENCES FAILED, 7-54
AM RADIO DISTURBER AT **** KHZ, 7-164
AMAS CHANNEL OOS, 7-108
AMI LC - ANSI NT1, 7-82
AMI LC - POSSIBLE ANSI COT CU, 7-82
AND DETERMINE FURTHER ACTION, 7-112
ANSI LC - AMI NT1, 7-82
ANSI LC - POSSIBLE AMI COT CU, 7-82
AT&T AMI NT1 DETECTED, 7-83
ATM LOOPBACK
VG-ONT
ABORTED, 7-24
FAILED, 7-24
PASSED, 7-24
UNABLE TO RUN, 7-24
ATM LOOPBACK FAILURE, 7-27
ATM LOOPBACK SUCCEEDED, 7-27
ATM PVC TRAFFIC PRESENT ON LINE, 7-27
ATTEMPT TO VERIFY BEFORE DISPATCH, 7-71
ATTEMPTING TO SYNC, 7-27
BAD COT CHANNEL UNIT, 7-139
BAD DLC OR DC TEST PAIR, 7-45
BAD RT CHANNEL UNIT, 7-139
BATTERY BOTH SIDES, 7-34
BATTERY CHARGE IS LOW, 7-54
BATTERY IS PROVISIONED, BUT MISSING, 7-54
BATTERY OUT OF LIMITS, 7-34
BATTERY PRESENT, BUT WILL NOT RECHARGE, 7-54
BENCHMARK DATA NOT STORED, 7-22
BENCHMARK DATA STORED, 7-22
BMDB DATABASE NOT AVAIL. - NOTIFY ADMIN., 7-21
BOARD INSTALLATION ALARM, 7-54
BOARD INSTALLATION ALARM (SB CARD), 7-54
BOARD INSTALLATION MISSING ALARM, 7-54
BOARD INSTALLATION MISSING ALARM (SB CARD), 7-55
BOARD MISSING ALARM, 7-55
BOARD MISSING ALARM (SB CARD, 7-55
BOARD RESET PROTECTION, 7-55
BOARD RESET PROTECTION (SB CARD), 7-55
BOARD TYPE MISMATCH, 7-55
bPON, 7-24
bPON Line, 7-24
BREAK INCORRECT **** %, 7-133
BREAK OK **** %, 7-133
BRIDGE LIFTERS, 7-67
BRIDGE TAP TEST NOT DONE DATA RATE HIGH= **** KBPS, 7-164
BUSY - NO SPEECH, 7-69
Index
BUSY - SPEECH, 7-69

BUSY ISDN LOOP - CANNOT TEST, 7-99
BUSY PACKET, 7-72
BUSY -SPEECH VALID REQUESTS ARE MON, SSA, OR X, 7-140
C.O. BATTERY ON PAIR GAIN SYSTEM, 7-45
C.O. TEST NOT DONE- SPECIAL DLCS, 7-145
CALIBRATION DATA LOADED IN DATABASE, 7-124
CALIBRATION FAILED, 7-124
CALL ANALYSIS IN PROGRESS, 7-27
CALL IN PROGRESS, 7-27
CALL TERMINATED PREMATURELY, 7-27
CALL TIMED OUT, 7-27
CALLED PARTY DISCONNECTED, 7-27
CANT BREAK DIAL TONE, 7-35
CANT DO CHANNEL TEST, 7-137, 7-138
CANT DO CO TEST - INWARD SVC, 7-36
CANT DO CO TEST- LOOP FAULT, 7-35
CANT DO CO TEST ON, 7-36
CANT DO CO TEST- XBAR OFFICE, 7-35
CANT DO HAZARDOUS POTENTIAL CHECK, 7-12
CANT DO LONG LOOP ANALYSIS, 7-107
CANT DO RING REQUEST ON DLCS AFTER METALLIC ACCESS DROP ACCESS, THEN REPEAT REQUEST,
7-143
CANT DO RING REQUEST ON DLCS BEFORE METALLIC ACCESS USE FULL OR LOOP TO GET MET ACCESS,
7-143
CANT DO RING REQUEST ON THIS, 7-143
CANT DO RINGER TEST, 7-131
CANT DO TALK REQUEST ON DLCS AFTER METALLIC ACCESS DROP ACCESS, THEN REPEAT REQUEST,
7-143
CANT DO TALK REQUEST ON DLCS BEFORE METALLIC ACCESS USE FULL OR LOOP TO GET MET ACCESS,
7-143
CANT DO TALK REQUEST ON THIS, 7-143
CANT DO TT TEST ON, 7-142
CANT DO TT TEST ON DLCS AFTER METALLIC ACCESS DROP ACCESS, THEN REPEAT REQUEST, 7-142
CANT DO TT TEST ON DLCS BEFORE METALLIC ACCESS USE FULL OR LOOP TO GET MET ACCESS, 7-142
CANT DRAW DIAL TONE, 7-34
CANT GET MEMORY TO COMPLETE REQUEST, 7-147
CANT OBTAIN DC SIGNATURE, 7-123
CANT OPEN SLEEVE LEAD, 7-67
CANT RELEASE PERMANENT SIGNAL, 7-67
CANT RUN PSR REQUEST, 7-123
CANT TEST- POSS TRUNK CALIB PROB, 7-147
CANNOT APPLY TONE ON THIS DLCS BEFORE METALLIC ACCESS USE FULL OR LOOP TO GET MET ACCESS,
7-144
CANNOT APPLY TONE WITH CALLBACK PRESENT ON 5ESS/DCTU USE XCB TO DROP CALLBACK AND THEN
RUN TONE REQUEST, 7-160
CANNOT EXECUTE - LMOS/MLT group must be up., 7-53
CANNOT OBTAIN CALLBACK WITH TONE PRESENT ON 5ESS/DCTU USE XTONE TO DROP TONE AND THEN
ADD CALLBACK, 7-160
CANNOT SECTIONALIZE FAULT, 7-114
CANNOT SEND TO APPLICATION PROCESS, 7-147
CANNOT VERIFY SWITCH ATTRIBUTES, 7-83
CANT DO DIAL TEST, 7-134
CANT SEND REQUEST TO APPROPRIATE FE, 7-147
CANT SEND REQUEST TO APPROPRIATE FE OR DATA SET LOCKUP, 7-154
CANT VERIFY RNGR TERM- UNCATALOGED, 7-131
CAPACITIVE BALANCE *** %, 7-19
-6
Index
CAPACITIVE BALANCE IS OUT OF TOLERANCE, 2-15, 7-20

CAPACITIVE BALANCE POOR *** %, 7-19
CAUTION
LINE RECORD WC USED. IF, 7-141
LINE RECORD WC USED. IF INCORRECT, CHANGE WC VIA RTE MASK, 7-141
CELL PHASE ERROR, 7-55
CHANGED DIRECTORY NUMBER, 7-36
CHANGED DIRECTORY NUMBER INDIV, 7-36
CHANNEL FAILURE, 7-137
CHANNEL ISOLATION TEST RESULTS NOT READY, 7-139
CHANNEL MISMATCH, 7-72
CHANNEL PROVISIONED FOR 56R, 7-83
CHANNEL PROVISIONED FOR 64R, 7-83
CHANNEL STATUS NOT IDENTIFIED, 7-137
CHANNEL UNIT ** UNDER TEST, 7-72
CHANNEL-COIN SERVICE, 7-138
CHANNEL-MULTIPLE PARTY SERVICE, 7-138
CHANNEL-SINGLE PARTY SERVICE, 7-138
CHECK SERVICE TYPE, 7-107
CIRCUIT IDENTIFIER EXCEEDS MAXIMUM FIELD LENGTH, 7-27, 7-29, 7-31, 7-116
CKT INFO NOT in BENCHMARK DATABASE, 7-21
CKTID NOT IN BENCHMARK DATABASE, 7-21
CLIENT SIDE ERROR, 7-27
C-MESSAGE NOISE DETECTED, 7-38
CO BATTERY AND EQUIPMENT, 7-68
CO EQUIP BAD, 7-72
CO TESTING NOT POSSIBLE, 7-138
CO TESTS NOT DONE, 7-33
CO TESTS NOT DONE - NO POTS SERVICE, 7-36
CO TESTS NOT DONE * NOT SUPPORTED BY TEST UNIT, 7-46
CONFIGURATION SUCCEEDED, 7-27
CONFLICTING CIRCUIT INFO ENTERED, 7-21
CONNECTION ESTABLISHED, 7-27
COT CU BAD, 7-72
COT CU SUSPECT, 7-72
COULD BE COT CU, 7-84
COULD BE CO-WIRING, 7-84
COULD BE CUST PREM EQUIP, 7-84
COULD BE CUSTOMER LOOP, 7-84
COULD BE FROM ROH OR FAULT, 7-70
COULD BE LINE CARD, 7-84
COULD BE NT1, 7-84
COULD BE RT CU, 7-84
COULD BE T1 FACILITY, 7-85
COULD BE TDSL LOOP, 7-85
COULD BE T-INTERFACE, 7-84
COULD NOT ACCESS, 7-147
COULD NOT ACCESS* NO USABLE DIALER, 7-141
COULD NOT COMPLETE METALLIC TEST, 7-85
COULD NOT DO CHANNEL ISOLATION TESTS * NO USABLE DIALER, 7-141
COULD NOT DO ROH TEST, 7-67
COULD NOT GAIN METALLIC ACCESS, 7-85
COULD NOT MAKE METALLIC ACCESS, 7-137
CO-WIRING SPAN L1 PM BAD, 7-83
CPE (NT1) ON SECONDARY POWER, 7-72
CPE (NT1) POWER SUSPECTED, 7-72
CPE (STATION SET) BAD OR INVALID, 7-73
Index
CPE (T-INTERFACE) BAD, 7-73

CPE GENERATING ERRORS, 7-85
CPE IS OUT OF SERVICE, 7-85
CPE LOOPBACK NOT DONE - NON FIT, 7-85
CPE or HIGH RESISTANCE OPEN, 7-113
CPE REQUESTED OUT OF SERVICE, 7-72, 7-86
CRAFT ACTION, 7-73
CROSS TO WORKING PAIR, 7-107
RING-SIDE, 7-42
TIP-SIDE, 7-42
CU NOT EQUIPPED FOR TEST ACCESS, 7-108
CUST PREM EQUIP BAD, 7-73
CUST PREM EQUIP IN TEST MODE, 7-73
CUST PREM EQUIP SUSPECT, 7-73
CUSTOMER LOOP SPAN L1 PM BAD, 7-86
CUSTOMER PERMISSION NEEDED TO TEST, 7-135
DANGER- ADVISE SUPERVISOR, 7-11
DATA LINK FAILURE, 7-148
DATA RATE HIGH > **** KBPS, 7-164
DATA RATE LOW > **** KBPS, 7-165
DATA RATE LOW= **** KBPS, 7-164
DATA RATE MEDIUM > **** KBPS, 7-165
DATA RATE MEDIUM= **** KBPS, 7-165
DATABASE DOWNLOAD IN PROGRESS, 7-147
DC BUSY, 7-70
DC FEMF, 7-67
DC RESISTANCE IS NOT SWINGING, 7-127
DC RESISTANCE OUT OF RANGE, 7-127
DC RESISTANCE TOO HIGH, 7-124
DC SIGNATURE LOOKS LIKE PBX, 7-136
DC VALUES LOOK LIKE PBX, 7-162
DEFAULT BSU PROFILE USED, 7-18
DEFENSE ALARM, PLUG-IN UNIT DISCONN (SB CARD), 7-56
DEFENSE ALARM, PLUG-IN UNIT DISCONNECTED, 7-55
DENIED CPE, 7-44, 7-73
DENIED SERVICE, 7-44
DENIED SERVICE - ADD ANALYSIS, 7-44
DENIED SERVICE - ORIGINATING, 7-44
DENIED SERVICE - TERMINATING, 7-44
DENIED/INTERCEPT - MIXED, 7-44
DENIED/RESTRICTED SERVICE - MIXED, 7-44, 7-74
DERIVED PAIR NOT TESTED PHYSICAL PAIR NOT SERVED BY MLT, 7-148
DHCP ADDRESS RESOLUTION FAILURE, 7-28
DHCP ADDRESS RESOLUTION SUCCEEDED, 7-28
DIAGNOSTICS REQUESTED, 7-148
DIAGNOSTICS RUNNING, 7-148
DIAL NOT OK, 7-134
DIAL OK, 7-134
DIAL SPEED INCORRECT **** PPS, 7-133
DIAL SPEED OK **** PPS, 7-133
DIAL TONE BURST DETECTED, 7-35
DIAL TONE GROUND SUPPLIED, 7-36
DIFFERENCE
RECORDS SAY ** RINGERS, 7-131
DIGITAL ANALYSIS REQUIRED, 7-74
DIGITAL AND METALLIC TEST OK, 7-86
DIGITAL CHANNEL CARRIER, 7-135
-8
Index
DIGITAL DATA NOT AVAILABLE, 7-46

DIGITAL TEST BUSY, 7-74, 7-86
DIGITAL TEST MARGINAL, 7-74
DIGITAL TEST OK, 7-86
DIMENSION TRUNK REVERSAL, 7-136
DIST FROM STATION ****** FT, 7-121
DISTANCE FROM C.O. ****** FT, 7-119
DISTANCE FROM LTE nnnn FT, 7-52
DISTANCE FROM RT ****** FT, 7-120
DISTANCE FROM STATION ****** FT, 7-119
DLCS AFTER METALLIC ACCESS, 7-36
DLCS BEFORE METALLIC ACCESS, 7-144
DLCS CONFIGURATION MISMATCH, 7-86
DLSAM/RT INTERNAL ERROR, 7-108
DN NOT IN SWITCH DATABASE, 7-74
DO FULL TEST FOR COMPLETE ANALYSIS, 7-35
DO LCOILX TEST TO LOCATE COILS, 7-102
DOUBLE LOAD DETECTED = ***MH, 7-102
DOWNLOAD IN PROGRESS, 7-148
DOWNSTREAM CELL DISCARD, 7-56
DPA REC NOT FOUND, 7-148
DROP ACCESS, THEN REPEAT REQUEST, 7-143
Drop Test OK, 7-24
DSL CIRCUIT DATA FOR REQUESTED LINE NOT AVAILABLE FROM NSDB, 7-116
DSL CIRCUIT DATA QUERY TO NSDB FAILED, 7-116
DSL IN SERVICE, 7-86
DSL MODEM DETECTION NOT DONE, 7-172
DSL OOS LAYER 1, 7-87
DSL OOS LAYER 1 ALL TEST OK, 7-87
DSL OOS LAYER 2 ALL TEST OK, 7-87
DSL OUT OF SERVICE, 7-87
DSL SYNC FAILURE, 7-28
DSL SYNC LOST, 7-28
DSL SYNC SUCCEEDED, 7-28
DSP DATA NOT RETRIEVED * UNSUPPORTED LTE CARD TYPE, 7-46
DT NOT DONE, 7-41
DUE TO BUSY ACCESS SYSTEM, 7-137
DUE TO DC FAULTS ON LINE, 7-107
DUE TO DLL ON LINE, 7-133
DUE TO LOOP ELECTRONICS, 7-15
DUE TO MAJOR ALARM, 7-137
DUE TO TEST SYSTEM FAILURE, 7-137
DUE TO TYPE TERMINATION, 7-67
DUPLICATE NNX-EXK IN DATABASE, 7-105
EMS Login Failure, 7-36
END SECTION TOO LONG = ***FT, 7-102
END-TO-END VC-AIS RECEIVING INDICATION, 7-56
END-TO-END VC-RDI GENERATING INDICATION, 7-56
END-TO-END VC-RDI RECEIVING INDICATION, 7-56
ENTER Y OR N IN XMT FIELD TO SPECIFY, 7-139
EQPMT SHUTDOWN DUE TO HIGH TEMP (SB CARD), 7-56
EQUIPMENT SHUTDOWN DUE TO HIGH TEMPERATURE, 7-56
EQUIPMENT VERSION MISMATCH, 7-56
ERROR IN LINE RECORD, 7-87
EST. MIXED GA DATARATE ***** KBPS, 7-166
Index
EST. MIXED GA DATARATE FAIL, 7-166

EST. MIXED GA DATARATE HIGH, 7-166
EST. MIXED GA DATARATE LOW, 7-166
EST. MIXED GA DATARATE MEDIUM, 7-166
EXAMINE DETAILED TEST RESULTS, 7-112
EXCESS AC FEMF, 7-123
EXCESS AC FEMF R-G ***** V, 7-13
EXCESS AC FEMF T-G ***** V, 7-12
EXCESS AC FEMF VOLTAGE, 7-127
EXCESS DC FEMF R-G ***** V, 7-13
EXCESS DC FEMF T-G ***** V, 7-13
EXCESS FOREIGN VOLTAGE, 7-13, 7-124
EXCESSIVE FAR--END BLOCK ERRORS, 7-56
EXCESSIVE LINE BIT ERRORS, 7-57
EXCESSIVE SECTION BIP-8 ERRORS, 7-57
EXK NOT IN DATABASE, 7-106
EXK/LRN REQUIRED FOR PORTED NUMBER, 7-105
FAN ALARM FOR FAN-1, 7-57
FAN ALARM FOR FAN-2, 7-57
FAR-END RINGING, 7-28
FAULT FOUND ON LINE, 7-124, 7-166
FAULT LOCATION TEST NOT DONE, 7-173
FEMF ON PAIR GAIN ACCESS TN, 7-140
FURTHER DIGITAL ANALYSIS REQUIRED, 7-88
FURTHER PER ANALYSIS REQUIRED, 7-88
FURTHER TEST REQUIRED, 7-74
FUSE ALARM. POWER FUSE BLOWN, 7-57
GOOD COT CHANNEL UNIT, 7-139
GOOD DC VALUES- SPECIAL EQUIPMENT, 7-136
GOOD PBX SIGNATURE, 7-136
GOOD PBX SIGNATURE- COUPLER, 7-136
GOOD RT CHANNEL UNIT, 7-139
HARD BATTERY R-G ***** V, 7-43
HARD BATTERY T-G ***** V, 7-43
HARD GROUND R-G, 7-127
HARD GROUND R-G IN NETWORK, 7-129
HARD GROUND R-G ON PREMISES, 7-128
HARD GROUND T-G, 7-126
HARD GROUND T-G IN NETWORK, 7-129
HARD GROUND T-G ON PREMISES, 7-128
HARD SHORT, 7-132
HARD SHORT T-R, 7-126
HARD SHORT T-R IN NETWORK, 7-128
HARD SHORT T-R ON PREMISES, 7-128
HAVE USER ACCESS HIGHLIGHTED IP ADDRESS, 7-28
HAZARDOUS POTENTIAL, 7-10
HDSL2 RATE ESTIMATED USING SDSL ALGORITHM, 7-46
HTTP ADDRESS TEST FAILURE, 7-28
HTTP ADDRESS TEST SUCCEEDED, 7-28
ID FIELD BLANK, ENTER DIGITS, 7-141
IDSL RATE ESTIMATED USING SDSL ALGORITHM, 7-46
ILLEGAL TRANSACTION FOR EMU, 7-53
ILLEGAL TRANSACTION FOR RMU, 7-125
INCOMPATIBLE VERSIONS, 7-75, 7-149
INCORRECT LOAD COIL DETECTED = ***MH, 7-102
INCORRECT LOAD COIL SECTION DETECTED = ***FT, 7-102
INCORRECT NUMBER OF LOADS, 7-102
-10
Index
INCORRECT NUMBER OF PULSES, 7-133

INFO MISMATCH - RESULTS NOT STORED, 7-22
INITIAL RATE OR FRAUD CONTACT OPEN, 7-40
INTEGRATED PGS DETECTED, 7-145
INTERCEPT, 7-111
INTERCEPT - ADD ANALYSIS, 7-34, 7-111
INVALID AC SIGNATURE, 7-15
INVALID ACCESS POINT, 7-167
INVALID ACCESS PT FOR 4 WIRE CIRCUIT, 7-141
INVALID CALLBACK TELEPHONE NUMBER, 7-149
INVALID CIRCUIT ID - COMPANY MUST BE UP TO 4 ALPHANUMERICS OR EMPTY, 7-116
INVALID CIRCUIT ID - PREFIX MUST BE UP TO 2 NUMERICS OR EMPTY, 7-116
INVALID CIRCUIT ID - SEGMENT MUST BE UP TO 3 ALPHANUMERICS OR EMPTY, 7-116
INVALID CIRCUIT ID - SERIAL NO MUST BE UP TO 6 NUMERICS, 7-117
INVALID CIRCUIT ID - SUFFIX MUST BE UP TO 3 ALPHANUMERICS OR EMPTY, 7-117
INVALID CIRCUIT ID - SVC CODE/MODIFIER MUST BE UP TO 4 ALPHANUMERICS, 7-117
INVALID COMMAND, 7-75
INVALID DCTU/NTT/PORT FOR NXX/EXK, 7-149
INVALID DN - EXTRA DIGITS REQUIRED, 7-75
INVALID LINE CKT ARRANGEMENT, 7-33
INVALID NPA-NNX, 7-149
INVALID OVERRIDE FOR ISDN, 7-149
INVALID OVERRIDE FOR MDF, 7-150
INVALID OVERRIDE FOR REQUEST TYPE, 7-150
INVALID OVERRIDE FOR SWITCH TYPE, 7-88
INVALID OVERRIDE FOR TEST HEAD TYPE, 7-150
INVALID PAIR GAIN ACCESS TN SIGNATURE, 7-140
INVALID PAIR GAIN C.O. SIGNATURE, 7-45
INVALID PHYSICAL PAIR TN OR- INVALID MDF DEDICATED NUMBER, 7-150
INVALID REQUEST
SPECIFY TN OR CIRCUIT ID BUT NOT BOTH, 7-117
INVALID REQUEST FOR 4 WIRE CIRCUIT, 7-140
INVALID REQUEST FOR ISDN LINE, 7-99
INVALID REQUEST FOR SPECIAL SERVICE ACCESS, 7-140
INVALID REQUEST FOR SWITCH TYPE, 7-88
INVALID REQUEST FOR TDSL, 7-75
INVALID REQUEST FOR THIS, 7-144
INVALID REQUEST FOR THIS DLCS BEFORE METALLIC ACCESS USE FULL OR LOOP TO GET MET ACCESS,
7-144
INVALID REQUEST FOR THIS DLCS LINE, 7-142
INVALID TERM FOR ISDN LINE, 7-99
INVALID TEST REQUEST, 7-20, 7-167
INVALID TEST REQUEST FOR RTU, 7-167
INVALID TEST REQUEST FOR TV SUPPORTED ONLY ON USER GUI, 7-167
INVALID TEST REQUEST NO WIDEBAND ACCESS AVAILABLE, 7-167
INVALID TEST REQUEST NO WIDEBAND TEST EQUIP AVAILABLE, 7-167
INVALID TEST REQUEST REQUEST NOT SUPPORTED FOR THIS LTE TYPE, 7-47
INVALID TEST REQUEST THIS TYPE OF DSLAM IS NOT SUPPORTED, 7-47
INVALID THERMISTOR ARRANGEMENT, 7-112
INVALID TN, 7-150
INVALID WIRE-CENTER IN LINE RECORD, 7-151
IP PING FAILURE, 7-28
IP PING SUCCEEDED, 7-28
IP TRACE ROUTE FAILURE, 7-28
IP TRACE ROUTE SUCCEEDED, 7-28
ISDN TERMINATION ERROR, 7-99
ISDN TERMINATION MISMATCH, 7-99
Index
ISDN TRAINING UNAVAILABLE - NOTIFY INSTRUCTOR, 7-161

ISLU BAD, 7-88
ISTF BAD, 7-88
ISTF UNAVAILABLE, 7-75
LAYER 1 PM COUNT BAD, 7-89
LAYER 1 PM COUNT CORRUPT, 7-89
LAYER 1 PM COUNT GOOD, 7-89
LAYER 1 PROBLEM, 7-75
LAYER 2 PM COUNT BAD, 7-89
LAYER 2 PM GOOD, 7-89
LAYER 2 PM SHOWS HIGH CRC ERRORS, 7-89
LAYER 2 PM SHOWS PERS EXIST, 7-89
LAYER 2 PM SHOWS UNEXPECTED MESSAGES, 7-90
LAYER 3 COUNT BAD, 7-90
LAYER 3 PM GOOD, 7-90
LAYER 3 PM SHOWS PERS EXIST, 7-90
LAYER 3 PROBLEM, 7-76
LCEN NOT IN SW DATABASE, 7-76
LEAD REV OR POLARITY GUARD PROBLEM, 7-40
LIGHT BATTERY R-G ***** V, 7-43
LIGHT BATTERY T-G ***** V, 7-43
LIGHT GROUND R-G, 7-127
LIGHT GROUND R-G IN NETWORK, 7-129
LIGHT GROUND R-G ON PREMISES, 7-128
LIGHT GROUND T-G, 7-126
LIGHT GROUND T-G IN NETWORK, 7-129
LIGHT GROUND T-G ON PREMISES, 7-128
LIGHT SHORT T-R, 7-126
LIGHT SHORT T-R IN NETWORK, 7-128
LIGHT SHORT T-R ON PREMISES, 7-128
LIMITED TEST RESULTS DISPLAYED, 7-167
LINE ALARM INDICATION SIGNAL, 7-57
LINE CARD AND COT MISMATCH, 7-90
LINE CARD AND NEAREST TERM MISMATCH, 7-90
LINE CARD AND NT1 MISMATCH, 7-91
LINE CARD BAD, 7-76
LINE CARD SUSPECT, 7-76
LINE CKT RESISTANCE TOO HIGH, 7-34
LINE HIGH AND DRY, 7-68
LINE IN GALVANIC ISOLATION MODE, 7-47
LINE IN SERVICE, 7-76
LINE IN USE, 7-66
LINE IS OUT OF SERVICE, 7-91
LINE NOT MLT TESTABLE, 7-151
LINE NOT SERVED BY MLT, 7-151
LINE OUT OF SERVICE, 7-91
LINE RECORD DATA NOT AVAILABLE, 7-18
LINE RECORD ERROR, 7-107
LINE RECORD ID AND LT OVERRIDDEN, 7-145
LINE RECORD INDICATES 4 WIRE CIRCUIT, 7-139
LINE RECORD INDICATES ISDN, 7-98, 7-100
LINE RECORD INDICATES NON-ISDN, 7-98
LINE RECORD INDICATES NOT-IN-SERVICE, 7-105
LINE RECORD INDICATES PORTED-OUT, 7-105
LINE RECORD INDICATES TERM MISMATCH, 7-91
LINE RECORD RETRIEVED FROM CACHE DB, 7-18
LINE RECORD SHOWS TERM MISMATCH, 7-76
-12
Index
LINK REMAINS IN DSL INIT STATE, 7-91

LINK TRANSITIONING BETWEEN STATES, 7-91
LISTEN FOR SPEECH, 7-107
LOAD COIL DETECTED, 7-103
LOAD COIL DETECTION INDETERMINATE, 7-103
LOAD COIL TESTS NOT DONE, 7-103
LOAD COIL VALUE *** IN QUESTION, 7-103
LOAD COILS DETECTED - ?, 7-102, 7-103
LOAD COILS DETECTED - NOT COUNTED, 7-103
LOCATION PORTABILITY, 7-37
LONG BAL TEST NOT DONE, 7-19
LONGER TEST IS NEEDED, 7-92
LONGITUDINAL BAL MARGINAL ** DB, 7-19
LONGITUDINAL BAL POOR ** DB, 7-19
LONGITUDINAL NOISE = ***DB RNC, 7-38
LOOP ACCESS NOT ATTEMPTED, 7-45
LOOP BAD, 7-76
LOOP ELECTRONICS, 7-68
LOOP LENGTH IS OUT OF TOLERANCE, 7-20
LOOP RESIST TOO HIGH, 7-134
LOOP SUSPECT, 7-77
LOOP TESTING FRAME POWER FAILURE, 7-151
LOOPBACK PASS AT CO LINE CARD, 7-92
LOOPBACK PASS AT NT1, 7-92
LOSS OF ACKNOWLEDGEMENT, 7-57
LOSS OF ATM CELL DELINEATION, 7-57
LOSS OF CELL DELINEAFTION (FE), 7-47
LOSS OF CELL DELINEAFTION (NE), 7-47
LOSS OF CELL DELINEATION, 7-58
LOSS OF EXTERNAL POWER, 7-58
LOSS OF FRAME AT THE DS1 INTERFACE, 7-58
LOSS OF PROTECTION SWITCHING CAPABILITY, 7-58
LOSS OF SIGNAL, 7-58
LOSS OF SIGNAL AT THE DS1 INTERFACE, 7-58
LOW RESISTANCE, 7-131
LPBK PASS AT CO LINE CARD, 7-92
LPBK PASS AT NT1, 7-92
LRN NOT IN DATABASE, 7-106
LT FIELD BLANK, ENTER DIGITS, 7-141
LTE COMMUNICATION FAILURE, 7-108
LTE EQUIPMENT BUSY, 7-109
LTE LOGIN ERROR, 7-109
LTE SLOT NOT EQUIPPED, 7-109
LTF POWER CLEAR, 7-151
LTF POWER CLEAR REQUESTED, 7-152
MAINTENANCE UNIT FOUND ON LINE, 7-114
MCU FOUND BY LOAD COIL DETECT, 7-104
MDF ACCESS REQUIRED FOR THIS REQUEST, 7-142
MDF NEEDED TO TEST CO, 7-35
MDF TEST RECOMMENDED, 7-126
MDF TESTABLE ONLY, 7-111
MDF TESTING NOT POSSIBLE, 7-138
MEASUREMENT ERROR, 7-68, 7-123
MEASURING CKT FAILURE, 7-67, 7-127
MEASURING CKT OVERLOAD, 7-131
MESSAGE ERROR, 7-58
METALLIC ACCESS NOT ALLOWED WITH CALLBACK PRESENT, 7-125
Index
METALLIC BYPASS NOT ALLOWED, 7-98

METALLIC NOISE = ***DB RNC, 7-38
METALLIC TEST INDICATES LC AND NT1 MISMATCH, 7-92
METALLIC TEST NOT AVAILABLE - T-DSL, 7-93
METALLIC TEST NOT RUN, 7-47, 7-93
METALLIC TEST OK, 7-93
METALLIC TEST REQUEST NOT ALLOWED, 7-28
MFT LOOP SIGNAL EXTENDER, 7-135
MIN PRED RATE **** KBPS, 7-168
MIN PRED RATE **** KBPS > SUBSCRIBED, 7-168
MISSING DATA IN TEST UNIT, 7-152
MISSING LOAD DETECTED = ***FT, 7-104
MLT CANT SEE LINE CKT, 7-34
MLT CANT TEST THROUGH CO EQPT, 7-111
MLT RINGER COUNT SAYS ** RINGERS, 7-131
MODERATE BATTERY R-G ***** V, 7-43
MODERATE BATTERY T-G ***** V, 7-43
MODERATE GROUND R-G, 7-127
MODERATE GROUND R-G IN NETWORK, 7-129
MODERATE GROUND R-G ON PREMISES, 7-128
MODERATE GROUND T-G, 7-126
MODERATE GROUND T-G IN NETWORK, 7-129
MODERATE GROUND T-G ON PREMISES, 7-128
MODERATE SHORT T-R, 7-126
MODERATE SHORT T-R IN NETWORK, 7-128
MODERATE SHORT T-R ON PREMISES, 7-128
MODULE INSERTED, 7-58
MODULE REMOVED, 7-59
MODULE TEMPERATURE EXCEEDED LIMIT, 7-59
MONITOR AND X REQUESTS ALLOWED, 7-70
MUST DROP ACCESS FIRST, 7-29
NEED ACCESS POINT INFORMATION TO ACCESS THIS LINE. ENTER R, C OR L IN APT FIELD, 7-139
NETWORK ELEMENT (OR PART) NOT PROVISIONED, 7-59
NETWORK ELEMENT (OR PART) OOS, 7-59
NETWORK ELEMENT NOT PROVISIONED, 7-59
NETWORK ELEMENT OUT OF SERVICE, 7-59
NEWLY DISCOVERED BUT NOT ENTERED/PROVISIONED, 7-59
NNX NOT IN DATA BASE, 7-152
NO 5ESS LINE CARD, 7-77
NO ALARMS PRESENT, 7-59
NO ATM PVC TRAFFIC DETECTED, 7-29
NO BENCHMARK DATA AVAILABLE, 7-20
NO CPE STATUS AVAILABLE, 7-77
NO FAULTS to BENCHMARKED LENGTH, 7-21
NO LIL CALIBRATION MODULE DETECTED, 7-124
NO LINE RECORD IN SYSTEM- TN NOT TESTABLE WITHOUT LINE RECORD, 7-152
NO LOOK-IN ACCESS AVAILABLE, 7-109, 7-168
NO METALLIC TEST FACILITY, 7-111
NO PDN AVAILABLE FOR METALLIC ACCESS, 7-93
NO PERMANENT SIGNAL, 7-123
NO PERS FOUND, 7-77
NO PGS DETECTED, 7-145, 7-146
NO POTS SERVICE, 7-35
NO POTS TERMINATION FOUND ON LINE, 7-172
NO RINGERS EXPECTED, 7-131
NO RINGERS FOUND, 7-131
NO TEST PACKAGE AVAILABLE, 7-152
-14
Index
NO TONES DETECTED, 7-41

NO TONES DETECTED **** MA, 7-39
NO UNIGAUGE TRUNK AVAILABLE, 7-152
NO USABLE BUSY DETECTOR, 7-152
NO USABLE DIALER, 7-153
NO USABLE PORT, 7-153
NO USABLE TRUNK, 7-153
NO VALID BENCHMARK DATA AVAILABLE, 7-20
NO WIDEBAND ACCESS AVAILABLE, 7-169
NO WIDEBAND TEST EQUIP AVAILABLE, 7-169
NOISE, 7-131
NOISE BALANCE MARGINAL = ***DB, 7-38
NOISE BALANCE POOR = ***DB, 7-38
NOISE-LOSS TOO HIGH FOR DSL ON 24GA, 7-168
NOISE-LOSS TOO HIGH FOR DSL ON 26GA, 7-168
NON SERVICE AFFECTING ALARMS PRESENT, 7-59
NON SIGNATURED SPLITTER DETECTED, 7-16
NONSTANDARD TERMINATION, 7-120
NOT A STEP BY STEP SWITCH, 7-123
NOT AN ISDN LINE, 7-77
NOT HIGH AND DRY, 7-67
NOT PRIMARY DN, 7-77
NOT ROH, 7-66
T-R RESISTANCE HIGH, 7-66
NPA-NNX NOT IN DATA BASE, 7-153
NPANXX OVERLAYED OPTION EWUIEWS, 7-111
NSA-LOOPCARE TEST ON ISDN - RESULTS SUSPECT, 7-100
NT1 BAD, 7-78
NT1 FOUND, 7-78
NT1 OR SDSL TERMINATION SEEN, 7-169
NT1 POWER SUPPLY BAD, 7-78
NT1 PRIMARY POWER FAIL, 7-78
NT1 PRIMARY PWR FAIL, 7-93
NT1 SECONDARY PWR FAIL, 7-94
NT1 SENDING TOO MANY ERRORS, 7-94
NT1 SUSPECT, 7-78
NTT ACCESS MUST BE DROPPED, 7-94
NTT/PORT OUT-OF-SERVICE, 7-153
NTT/PORT SELECTION PROHIBITED DROP ACCESS AND RETEST, 7-153
OE MISMATCH, 7-79
OEN NOT IN SW DATABASE, 7-75
OFFICE OVERFLOW, 7-111
OMCI COMMUNICATION DOWN, 7-59
ON CIRCUIT SWITCHED SERVICE, 7-98
ON DEMAND PACKET B SERVICE, 7-98
ONE RINGER WIRED TO GROUND OR, 7-107
ONE SIDE OF LINE IS OPEN OR, 7-107
ONLY LOGICAL LOOPBACKS DONE, 7-94
ONT AUTONOMOUSLY DISABLED(MISBEHAVING TRANSMISSION), 7-60
ONT FAILED TO RETURN EXPECTED PASSWORD, 7-60
ONT IS INACTIVE, 7-60
ONT Self Test - No test results available, 7-25
ONT Self Test Failed, 7-24
ONT Self Test in Progress, 7-24
ONT Self Test Passed, 7-25
OPEN - NO RINGER SEEN, 7-25
OPEN IN, 7-118
Index
OPEN IN LTE, 7-120

OPEN IN REMOTE TERMINAL, 7-120
OPEN LINE CKT TIP AND RING, 7-33
OPEN MEASUREMENTS NOT PERFORMED, 7-119
OPEN ON PREMISES, 7-120
OPEN OUT
HIGH RESISTANCE, 7-119
OPEN OUT- 2 PTY OR BRIDGE LIFTER, 7-118
OPEN OUT BALANCED- CAP BAL *** %, 7-119
OPEN OUT CABLE RING- CAP BAL *** %, 7-118
OPEN OUT CABLE TIP- CAP BAL *** %, 7-118
OPEN OUT NEAR DROP- CAP BAL *** %, 7-118
OPEN-CANNOT MEASURE DISTANCE, 7-119
OR BUSY ACCESS SYSTEM, 7-142
OR INVALID ACCESS POINT, 7-140
OR INVALID ID OR LT, 7-140
OR ON INTERCEPT, 7-137
OR OPEN OUT NEAR CO, 7-121
OVRD-EXK/NNX COMBO DUPLICATED IN DATABASE, 7-106
OVRD-EXK/NNX COMBO NOT IN DATABASE, 7-154
PACKET D SERVICE, 7-98
PAIR GAIN ACCESS EQUIPMENT BUSY, 7-137, 7-154
PAIR GAIN ACCESS TN ON INTERCEPT, 7-140
PAIR GAIN EQUIPMENT FAILURE, 7-137
PAIR GAIN SYSTEM BUSY, 7-138
PAIR GAIN SYSTEM FAILURE, 7-138
PARITY BIT ERROR ON UTOPIA BUS, 7-60
PARTIAL DIGITAL TEST OK, 7-94
PARTIAL TEST DATA RECEIVED, 7-169
PBX INWARD SERVICE IDENTIFIED, 7-112
PBX LINE WITH POSSIBLE ROUTE ADVANCING, 7-137
PCRs cross--connected into POTS VP has exceeded warning threshold, 7-60
PEER BOARD LOSS OF COMMUNICATION ERROR, 7-60
PERMANENT PACKET B SERVICE, 7-98
PERMANENT SIG, 7-68
PERMANENT SIGNAL, 7-68
PERMANENT SIGNAL NOT RELEASED, 7-123
PERMANENT SIGNAL RELEASED, 7-123
PERS INDICATE SEVERAL PROBLEMS, 7-94
PERS SHOW SEVERAL PROBLEMS, 7-94
PERS SHOW UNIQUE PROBLEM, 7-95
PHYSICAL EQUIPMENT ERROR OF ONT, 7-60
PHYSICAL PAIR TN ON INTERCEPT, 7-112
PLUG-IN MODULE AND CONFIGURATION MISMATCH, 7-60
PON COMMUNICATION FAILURE ON OLT PORT, 7-61
PORTED DIRECTORY NUMBER, 7-36
PORTED NUMBER TESTING INACTIVE, 7-106
POSSIBLE AMI BRITE DETECTED, 7-100
POSSIBLE BUSY DSL, 7-95
POSSIBLE CO WIRING ERROR, 7-35
POSSIBLE CO-WIRING ERROR, 7-79
POSSIBLE FAULTY TELEPHONE SET, 7-132
POSSIBLE INTERFACE-TERMINAL MISMATCH, 7-115
POSSIBLE INVALID ACCESS, 7-34
POSSIBLE KEY SET, 7-132
POSSIBLE LAYER 2 PROTOCOL PROBLEM, 7-95
POSSIBLE LAYER 3 PROTOCOL PROBLEM, 7-95
-16
Index
POSSIBLE LINE CKT DETECTED, 7-35

POSSIBLE LINE IN USE OR, 7-69
POSSIBLE LONG LOOP, 7-107
POSSIBLE NON-ANSI NT1, 7-95
POSSIBLE PERMANENT SIGNAL ON LINE, 7-69
POSSIBLE PROTOCOL PROBLEM, 7-79
POSSIBLE RECEIVER-OFF-HOOK, 7-129
POSSIBLE RECORD ERROR, 7-162
POSSIBLE RT CALIBRATION ERROR, 7-121
POSSIBLE TRANSIENT PROBLEM, 7-96
POTS LINE CIRCUIT FOUND ON ADSL LINE LINE NOT TESTABLE, 7-169
PPP AUTHENTICATION FAILUR, 7-29
PPP AUTHENTICATION SUCCEEDED, 7-29
PREDICTED 24 GA DATA RATE
**** KBPS, 7-169
PREDICTED 26 GA DATA RATE
**** KBPS, 7-170
PREDICTED DR= **** KBPS, 7-170
PREDICTED DR= **** KBPS>=SUBSCRIBED, 7-170
PREFERRED TIMING REFERENCES FAILED, 7-61
PROBABLE MISWIRED RINGERS OR, 7-107
PROBABLE NT1 COULD BE LOOP, 7-79
PROBABLY TEST OK, 7-23
PROTECTED SERVICE, 7-135
PROTOCOL HANDLER BAD, 7-96
PROTOCOL HANDLER SUSPECT, 7-79
PSU BAD, 7-96
READY TO AUTHENTICATE, 7-29
READY TO RESOLVE ADDRESS, 7-29
READY TO VERIFY ADDRESS, 7-29
RECEIVED ALARM INHIBIT FROM ONT, 7-61
RECEIVER-OFF-HOOK OR SHORT, 7-107
RECEIVING AIS AT THE DS1 INTERFACE, 7-61
RECEIVING RAI AT THE DS1 INTERFACE, 7-61
REG, 7-68
REGISTRATION SUCCEEDED, 7-29
RELAY CURRENT **** MA, 7-40
RELAY IS FAST **** MSEC, 7-40
RELAY IS SLOW **** MSEC, 7-40
RELAY NOT OPERATED **** MA, 7-40
RELAY OPERATED
ATTEMPT **, 7-40
REMAINS IN TRANSITION STATE, 7-96
REMOTE DSL MODEM DETECTED, 7-30
REMOTE EAIU - RUN FULL OR LOOP FIRST, 7-125
REMOTE FACILITY DETECTED, 7-154
REMOTE FAILURE/DEFECT INDICATION, 7-61
REMOTE SIG LOSS
UNKNOWN CAUSE, 7-48
REQUEST REDIRECTED, 7-30
REQUEST REJECTED
MISSING DSLAM INFO, 7-48
RESTORAL FAILED, 7-96
RETEST IF DESIRED, 7-133
RINGER COUNT MAY BE WRONG- BL, 7-130
RINGER COUNT NOT DONE - ISDN LINE, 7-100
Index
RINGER TERM LIKE 2 PTY-1 ASN, 7-130

RINGER TERM LIKE 2 PTY-2 ASN, 7-130
RINGER TERM LIKE SINGLE PARTY, 7-130
RINGER TERMINATION OK, 7-131
ROH, 7-66
HIGH AND DRY, 7-66
ROH DETECTED DURING TEST, 7-113
ROTARY DIAL ANALYZER NOT AVAILABLE, 7-134
RT CU BAD, 7-79
RT CU SUSPECT, 7-79
RUN XCB REQUEST TO DROP CALLBACK BEFORE FULL OR LOOP, 7-125
RUNAWAY TOTALIZER **** MA, 7-39
S X S SPLIT C.O. BATTERY, 7-43
SANITY OR DIAG IN PROGRESS, 7-154
SBOARD TEMPERATURE EXCEEDED, 7-61
SEARCH STRING NOT IN HTML SOURCE, 7-30
SECTION *** IN QUESTION, 7-104
SECTION LOSS OF CLOCK, 7-61
SECTION LOSS-OF-FRAME, 7-61
SECTION LOSS-OF-SIGNAL, 7-62
SECTIONALIZE WITH LONGER LPBK, 7-80
SERVER SIDE ERROR, 7-30
SERVICE CLASS MISMATCH, 7-18
SHORT - PROBABLY ROH, 7-70
SHORT OR GROUND, 7-25
SIGNAL DEGRADATION, 7-62
SIGNAL LOSS FROM REMOTE END, 7-48
SIMULTANEOUS TEST REQUEST MADE, 7-154
SLOW DIAL SPEED **** PPS, 7-133
SLOW DIAL TONE, 7-34
SOAK TEST NOT ATTEMPTED, 7-127
SOFTWARE ACTIVATION FAILURE, 7-62
SOFTWARE DOWNLOAD FAILED, 7-62
SOFTWARE DOWNLOAD IN PROGRESS, 7-62, 7-155
SPECIAL DLCS EQUIPMENT, 7-138
SPECIAL SERVICE ACCESS UP, 7-113
SPECIAL SERVICES ACCESS UP, 7-6
SPECIAL SERVICES IDENTIFIED, 7-135
SSA ACCESS REQUIRED BEFORE REQUEST IS PERFORMED ENTER SSA IN THE REQUEST FIELD, 7-155
STALLED TOTALIZER **** MA, 7-39
STANDARD INTERFACE-CPE NOT TESTED, 7-115
STANDBY EXCESSIVE FAR--END BLOCK ERRORS, 7-62
STANDBY EXCESSIVE LINE BIT ERRORS, 7-62
STANDBY EXCESSIVE SECTION BIP-8 ERRORS, 7-63
STANDBY LINE ALARM INDICATION SIGNAL, 7-63
STANDBY LOSS OF ATM CELL DELINEATION, 7-63
STANDBY REMOTE FAILURE/DEFECT INDICATION, 7-63
STANDBY SECTION LOSS-OF-CLOCK, 7-63
STANDBY SECTION LOSS-OF-FRAME, 7-63
STANDBY SECTION LOSS-OF-SIGNAL, 7-63
STARTUP FAILURE IN RANGING OF ONT, 7-63
STATUS SHOWS CU HAS PROBLEM, 7-96
STATUS SHOWS CUST T-INT PROBLEM, 7-97
STATUS SHOWS LINK AFTER COT BAD, 7-97
SW OE DOES NOT MATCH LR OE, 7-97
SWINGING TROUBLE, 7-127
SWINGING TROUBLE- DRIED OUT, 7-127
-18
Index
SWITCH COMMON EQUIP BAD, 7-80

SWITCH EQUIP NOT AVAILABLE, 7-80
SWITCH INDICATES IDLC, 7-101
SWITCH INDICATES ISDN SERVICE, 7-100
SWITCH INDICATES NON-ISDN, 7-99
SWITCH INDICATES NON-ISDN SERVICE, 7-100
SWITCH INDICATES T-DSL LINE CARD, 7-97
SWITCH INTERFACE UPDATE REQUIRED, 7-155
SWITCH INTERNAL ERROR, 7-80
SWITCH OVERFLOW, 7-80
SWITCHID NOT IN DATABASE, 7-106
SYNC FAILURE - DSLAM DETECTED, 7-30
SYNC FAILURE - DSLAM NOT DETECTED, 7-30
SYNCOUT FAILURE - CPE DETECTED, 7-30
SYNCOUT FAILURE - CPE NOT DETECTED, 7-30
SYSTEM AND BACKUP MEMORY RESET, 7-64
SYSTEM TIMEOUT, 7-155
T1 FACILITY BAD, 7-81
T1 FACILITY L1 PM BAD, 7-97
TA 3050 SHELF OR MTC NOT PRESENT, 7-17
TAKE NOT ALLOWED ON CMUs, 7-155
TAKE NOT ALLOWED ON SPECIAL SERVICES ACCESSES, 7-156
TALK REQUEST MAY INTERRUPT CALL, 7-70
TDR DISPLAY NOT AVAILABLE, 7-170
T-DSL LOOP OR CPE PROBLEM, 7-97
TERMINATION MISMATCH, 7-81
TEST COMPLETE - EXAMINE RESULTS, 7-30
TEST EQUIPMENT BUSY, 7-48, 7-156
TEST EQUIPMENT BUSY - COULD NOT ACCESS, 7-157
TEST EQUIPMENT CANT TEST LOAD COILS, 7-104
TEST EQUIPMENT FAILURE, 7-157
TEST EQUIPMENT NOT AVAILABLE FOR WC, 7-157
TEST EQUIPMENT NOT CALIBRATED, 7-157
TEST EQUIPMENT OUT OF SERVICE, 7-158
TEST NOT MADE, 7-158
TEST OK, 7-111
TEST OK CPE/MTU, 7-114
TEST OK MTU, 7-114
TEST OK NOW, 7-81
TEST OK PARTIAL TEST DONE, 7-81
TEST SESSION FAILURE, 7-81
TEST STOPPED-EXCESS AC CURRENT, 7-11
TEST STOPPED-EXCESS AC VOLTAGE, 7-11
TEST SYSTEM ERROR, 7-158
TEST UNIT CANNOT LOCATE LOAD COILS, 7-104
TESTABLE VIA GUI ONLY, 7-156
TESTABLE VIA STV OPTION - ENTER STV IN THE REQ FIELD, 7-156
TESTABLE VIA THE STV MASK ONLY, 7-156
TESTED USING OVERRIDE DSL TYPE * LTE INIDCATES DIFFERENT DSL TYPE, 7-48
TESTED WITH PARTIAL LINE RECORDS, 7-112
TESTED WITHOUT LINE RECORD, 7-117
TESTED WITHOUT LINE RECORDS, 7-112
THERMISTOR FOUND- NOT EXPECTED, 7-112
THROUGHPUT TEST FAILURE, 7-30
THROUGHPUT TEST SUCCEEDED, 7-31
TIME OUT IN ACCESS, 7-158
TIME OUT IN DIAL TEST, 7-133
Index
TIME OUT IN TESTING, 7-158

TIMEOUT IN CALL TEST, 7-32
TIMEOUT IN TT TEST, 7-134
TIMEOUT-POSSIBLE LINE ON INTERCEPT, 7-158
T-INTERFACE HAS PROBLEM, 7-80
TIP **** V, RING-GROUND, 7-33
TIP **** V, RING-OPEN, 7-33
TIP-GROUND, RING-OPEN, 7-33
TIP-OPEN, RING **** V, 7-33
TIP-OPEN, RING-GROUND, 7-33
TN FROM FE IN DIFFERENT FE GROUP, 7-158
TN NOT IN 5ESS DATABASE, 7-159
TN NOT IN BENCHMARK DATABASE, 7-21
TONE RINGER DETECTED, 7-132
TONES DETECTED, 7-40
TOT NOT HOME AND/OR ROH, 7-41
TOTALIZER
HOMED OR SHORT, 7-41
TOTALIZER HOMED
ATTEMPT **, 7-39
TOTALIZER NOT HOMED, 7-39
TOTALIZER STALLED AND/OR ROH, 7-40
TOTALIZER WAS STALLED **** MA, 7-39
T-R SHORT, 7-34
TRAINING SCRIPT UNAVAILABLE, 7-161
TRANSACTION STOPPED, 7-31
TRANSMIT OR RECEIVE PAIR, 7-139
TRANSMITTER FAILURE ON OLT PORT, 7-64
TT NOT AVAILABLE FOR THIS ACCESS POINT, 7-144
TT PAD NOT OK, 7-134
TT PAD OK, 7-134
UNABLE TO ACTIVATE OSWP/LK-DB, 7-64
UNABLE TO COMMUNICATE WITH SNTP SERVER, 7-64
UNACCEPTABLE REQUEST IN THIS CASE - TRY AGAIN, 7-161
UNEQUIPPED COMMAND, 7-82
UNEXPECTED INTEGRATED PGS/UNEXPECTED UNIVERSAL PGS, 7-162
UNEXPECTED ISDN TERMINATION, 7-100
UNEXPECTED PBX INWARD SERVICE, 7-162
UNEXPECTED RINGER TERM IDENTIFIED, 7-162
UNEXPECTED THERMISTOR FOUND, 7-162
UNIGAUGE LOOP, 7-67
UNIVERSAL PGS DETECTED, 7-146
UNOBTAINABLE DIRECTORY NUMBER, 7-37
UPSTREAM CELL DISCARD, 7-64
USE CO REQ FOR LINE CKT & DIALTONE, 7-113
USE CSET REQUEST FOR COIN TESTS, 7-142
USE EXK or LRN OVERRIDE TO TEST, 7-106
USE EXTREME CAUTION, 7-12
USE FULL OR LOOP TO GET MET ACCESS, 5-94, 7-125, 7-142
USE MON AND TALK TRANSACTIONS TO, 7-107
USE MONITOR OR TALK REQUEST FOR ACCESS, 7-70
USE S OR R OVERRIDE, 7-97
USE XCB REQUEST TO DROP CALLBACK THEN RUN SSA, 7-144
USE XTONE REQUEST TO DROP TONE, 7-145
USE XTONE REQUEST TO DROP TONE THEN RUN SSA, 7-145
USED SHELF BANDWIDTH ABOVE 75% CAPACITY, 7-64
USER GUI REQUIRED FOR WIDEBAND DATA, 7-171
-20
Index
USER MANUALLY OUT OF SERVICE, 7-97

VALID AMI NT1 SIGNATURE, 7-101
VALID ANSI NT1 SIGNATURE, 7-101
VALID ENTRIES ARE 1-12 for port and 1-192 for DCTU, 7-159
VALID ENTRIES ARE 1-16 FOR LTS/EMU, 7-159
VALID NT1 SIGNATURE, 7-101
VALID OE NEEDED TO TEST PORTED NUMBER, 7-106
VALID REQUESTS ARE SSA OR X, 7-144
VERY HARD BATTERY R-G ***** V, 7-43
VERY HARD BATTERY T-G ***** V, 7-43
VERY HARD GROUND R-G, 7-127
VERY HARD GROUND R-G IN NETWORK # stopped here 170, 7-129
VERY HARD GROUND R-G ON PREMISES, 7-128
VERY HARD GROUND T-G, 7-126
VERY HARD GROUND T-G IN NETWORK, 7-129
VERY HARD GROUND T-G ON PREMISES, 7-128
VERY HARD SHOR T T-R, 7-126
VERY HARD SHORT T-R IN NETWORK, 7-128
VERY HARD SHORT T-R ON PREMISES, 7-128
VERY LIGHT BATTERY R-G ***** V, 7-43
VERY LIGHT BATTERY T-G ***** V, 7-43
VERY LIGHT GROUND R-G, 7-126
VERY LIGHT GROUND R-G IN NETWORK, 7-129
VERY LIGHT GROUND R-G ON PREMISES, 7-128
VERY LIGHT GROUND T-G, 7-126
VERY LIGHT GROUND T-G ON PREMISES, 7-128
VERY LIGHT GROUND T-R IN NETWORK, 7-128
VERY LIGHT SHORT T-R, 7-126
VERY LIGHT SHORT T-R IN NETWORK, 7-128
VERY LIGHT SHORT T-R ON PREMISES, 7-128
VIDEO LOSS OF SIGNAL, 7-64
VOICE GATEWAY TO ONT CONN DOWN, 7-25
VOICE GATEWAY TO ONT CONN UNKNOWN, 7-25
VOICE GATEWAY TO ONT CONN UP, 7-25
VOICE GATEWAY TO SWITCH CONN DOWN, 7-25
VOICE GATEWAY TO SWITCH CONN FAILURE, 7-26
VOICE GATEWAY TO SWITCH CONN UNKNOWN, 7-26
VOICE GATEWAY TO SWITCH CONN UP, 7-26
WAIT ONE MINUTE THEN TRY AGAIN, 7-159
WAITING FOR SOFTWARE, 7-64
WAITING FOR SOFTWARE (SB CARD), 7-64
WEB SITE NOT FOUND, 7-31
WIDEBAND TEST EQUIP FAILURE, 7-171
WIDEBAND TESTS NOT DONE, 7-171
WIDEBAND TESTS NOT DONE * WIDEBAND TEST EQUIP FAILURE, 7-171
WIRING ERROR - NT1 REVERSED, 7-101
WRONG RINGER TERM
LIKE 2 PTY-1 ASN, 7-130
LIKE 2 PTY-2 ASN, 7-130
LIKE SINGLE PTY, 7-130
WRONG RINGER TERMINATION, 7-131
XDSL CARD IS NOT IN SERVICE, 7-48
XDSL CPE EQUIP PROBLEM, 7-49
XDSL DSLAM EQUIP PROBLEM, 7-49
XDSL LINE OUT OF SERVICE, 7-49
XDSL LINE SELF TEST FAILURE, 7-49
XDSL LOSS OF SIGNAL DETECTED, 7-50
Index
XDSL MODEM IN TRANSITION PHASE, 7-50

XDSL MODEM IN UNKNOWN STATE, 7-50
XTUC NOT RESPONDING, 7-51
XTUR NOT RESPONDING, 7-51
T
Termination Equipment Effects, C-1, C-2
Tests
AC Signature, 1-17
Access, 1-13
Capacitive Balance Measurement, 1-19
Coin, 1-23
DC, 1-15
DC Resistance, 1-15
DC Voltage, 1-16
Dial, 1-22
Digitest, 1-24
Draw and Break Dial Tone, 1-20
Foreign Electromotive Force, 1-13
Individual, 1-13
Intercept, 1-15
Length of Loop Measurement, 1-21
Line Circuit, 1-19
Line in Use, 1-14
Linespecs, 1-25
Longitudinal Balance, 1-18
Opens, 1-18
Other Terminations, 1-17
PBX Identification, 1-16
Per, 1-26
PML1, 1-27
PML2, 1-28
PML3, 1-29
POTS Terminations, 1-17
Resistive Fault Sectionalization, 1-23
Restore, 1-30
Ringer, 1-20
Soak, 1-20
Specialized, 1-22
Status, 1-30
Thermistor, 1-18
Touch-Tone, 1-22
Testsw
ISDN, 1-24
Thermistor Signatures
Valid, G-1
Thermistor Test, 1-18
Touch-Tone Test, 1-22
-22
Index
V
VER 0, 2-4
VER AJ SEARCH STRING NOT IN HTML SOURCE, 3-10
VER Codes
AC FEMF MARGINAL (VER 16), 2-26
AMAS CHANNEL (VER ES), 4-21
ANALYSIS OF FULL RESULTS NEEDED (VER 98), 2-94
ANOTHER USER IS ACCESSING THIS REMOTE TEST EQUIPMENT (VER TR), 5-65
AS COMMUNICATION FAILURE (VER FP), 4-45
AS PORT OR DMU CONFIG ERROR (VER FR), 4-47
ATM FAILURE - CHECK VPI/VCI (VER AV), 3-22
BAD COT AND RT UNITS (VER 58), 2-74
BAD COT CHANNEL UNIT (VER 56), 2-72
BAD DLC OR DC TEST PAIR (VER DT), 3-74
BAD RT CHANNEL UNIT (VER 57), 2-73
BSU MODULE EQUIPAGE ERROR (VER EB), 4-15
BUSY DETECTOR FAILURE (VER FA), 4-32
BUSY PACKET (VER 60), 2-76
CALL FAILED, 5-76
CALL NOT ANSWERED (VA), 5-74
CANT BREAK DIAL TONE (VER 33), 2-43
CANT CONNECT TO CMU (VER BW), 3-54
CANT CONNECT TO RMU (VER BU), 3-52
CANT DRAW DIAL TONE (VER 32), 2-42
CHAN UNIT NOT EQUIPPED FOR TEST ACCESS (VER NE), 5-26
CHANNEL MISMATCH (VER IV), 4-86
C-MESSAGE NOISE (VER 90), 2-87
CO BATTERY ON PAIR GAIN SYSTEM (VER 51), 2-67
CO EQUIP BAD - ISTF BAD - LINE CARD BAD - PROTOCOL HANDLER BAD (VER 39), 2-50
CO EQUIP SUSPECT (VER 40), 2-52
COIN RELAY PROBLEMS (VER C4), 3-60
COIN SUPERVISORY CKT PROBLEMS (C5), 3-61
COMMUNICATION OR MML ERROR (VER EC), 4-16
CONNECT FAIL - PROTOCOL FAILURE (VER FT), 4-49
CONTROL FAILURE - ISLC/DCTU (VER FE), 4-36
CONTROL FAILURE - USLC/DCTU (VER FF), 4-37
CONTROLLER-LTF OR FRONT END-LTS DATA LINK FAILURE (VER DL), 3-72
COT CU SUSPECT (VER 50), 2-66
CPE (NT1) ON SECONDARY POWER (VER IR), 4-82
CPE (NT1) POWER SUSPECTED (VER IN), 4-79
CPE (STATION SET) BAD OR INVALID (VER P7), 5-45
CPE (T-INTERFACE) BAD (VER P8), 5-46
CRAFT ACTION (VER 63), 2-78
CROSS TO WORKING PAIR
MARGINAL (VER 14), 2-22
CUST PREM EQUIP IN TEST MODE (VER P6), 5-44
CUST PREM EQUIP SUSPECT (VER P5), 5-43
CUSTOMER PREMISE EQUIPMENT BAD (VER P4), 5-42
DC FEMF MARGINAL (VER 15), 2-24
DC RESIST MARGINAL
PREMISES (VER P2), 5-39
DC RESISTANCE- MARGINAL (VER 27), 2-37
DC RESISTIVE FAULT
Index
PREMISES (VER P1), 5-37

DCTU NOT AVAILABLE (VER BB), 3-34
DEFECTIVE DC TEST PAIR - (OPEN, SHORT, GROUND or BATTERY) (VER DP), 3-73
DEFECTIVE DIST OR SCAN CP (VER FV), 4-50
DENIED CPE (VER D4), 3-68
DENIED SERVICE - ADD ANALYSIS (VER IJ), 4-75
DENIED SERVICE - ORIGINATING (VER D2), 3-66
DENIED SERVICE - TERMINATING (VER D1), 3-65
DENIED SERVICE (VER D3), 3-67
DENIED SERVICE MIXED (VER D5), 3-69
DENIED/INTERCEPT - MIXED (VER DI), 3-71
DERIVED PR NOT TESTED-PHYSICAL PR NOT SERVED (VER 97), 2-93
DIAL NOT OK (VER 81), 2-86
DIAL OK (VER 80), 2-85
DIAL TONE BURST DETECTED (VER 37), 2-47
DIALER FAILURE (VER FB), 4-33
DIGITAL ANALYSIS REQUIRED (VER IZ), 4-88
DIGITAL TEST BUSY (VER TB), 5-64
DIGITAL TEST MARGINAL (VER IM), 4-78
DLC CONCENTRATOR COMM FAILURE, 4-17
DOUBLE LOAD DETECTED (VER L5), 5-10
DOWNLOAD IN PROGRESS (VER B6), 3-30
DROP ACCESS TO CHANGE TEST PORT (VD), 5-77
END SECTION TOO LONG (VER L3), 5-8
EQUIPMENT ACCESS FAILURE (VER FH), 4-39
FOLLOWING CONFIG NOT PROV IN VG, 4-66
FURTHER TEST REQUIRED (VER IG), 4-73
GATEWAY FAILURE (VER DG), 3-70
GDXC FAILURE (VER FK), 4-41
GROUND FAULT (VER 21), 2-29
HAZARDOUS POTENTIAL (VER 13), 2-21
HDT INITIALIZING (VER BZ), 3-56
HIGH RESISTANCE OPEN (VER 43), 2-57
HOSTNAME (DNS) TRANSLATION FAILURE, 3-21
INCORRECT COIL DETECTED (VER L1), 5-6
INCORRECT NUMBER OF LOADS (VER L4), 5-9
INCORRECT SECTION DETECTED (VER L2), 5-7
INITIAL RATE OR FRAUD CONTACT PROBLEMS (VER C6), 3-63
INTERCEPT - ADD ANALYSIS (VER ST), 5-59
INTERCEPT (VER SU), 5-60
INVALID 2 PARTY RINGER TERMINATION (VER G2), 4-56
INVALID AC SIGNATURE (VER 92), 2-89
INVALID LINE CIRCUIT ARRANGEMENT (VER 31), 2-41
INVALID PAIR GAIN CO SIGNATURE (VER 52), 2-68
INVALID PBX SIGNATURE (VER 91), 2-88
INVALID RINGER TERMINATION (VER G1), 4-55
INVALID TDSL REQUEST (VER NG), 5-28
INVALID TERM FOR ISDN LINE (VER IF), 4-72
INVALID TEST REQUEST (VER XR), 5-96
INVALID TN (VER XI), 5-93
INVALID WIRE CENTER IN LINE RECORD (IW), 4-87
INVALID/INCOMPLETE CIRCUIT INFO (VER XF), 5-90
ISDN TERMINATION MISMATCH (VER ID), 4-71
LAYER 2 PROBLEM (VER PA), 5-48
LAYER 3 PROBLEM (VER PC), 5-50
LDS NAME UNKNOWN TO SDV-EM (VER XG), 5-91
LINE CIRCUIT AND DIAL TONE PROBLEMS (VER 36), 2-46
-24
Index
LINE IN USE (VER 61), 2-77

LINE IN USE (VER LU), 5-19
LINE IN USE OR PERMANENT SIGNAL (VER 73), 2-81
LINE NOT MLT TESTABLE (VER NT), 5-34
LINE NOT SERVED BY MLT (VER NS), 5-33
LINE NOT VERIFIED (VER NV), 5-36
LINE RECORD ERROR (VER NK), 5-29
LINE RECORD ERROR (VER XH), 5-92
LINE RECORD SHOWS TERM MISMATCH (VER IU), 4-85
LOADING REQUIRED ON LOOP (VER L0), 5-5
LOGIN FAILURE (VER FN), 4-44
LONG TEST-EXPECT DELAYED RESULTS (VER LT), 5-18
LOOP BAD (VER LB), 5-12, 5-13, 5-14
LOOP SUSPECT (VER LS), 5-17
LTE BUSY (VER BY), 3-55
LTE COMMUNICATION FAILURE (VER ER), 4-20
LTE INTERNAL ERROR (VER F5), 4-30
LTE SLOT NOT EQUIPPED (VER EP), 4-19
MARGINAL BALANCE (VER 96), 2-92
MDF TEST RECOMMENDED (VER MD), 5-21
MDF TEST RECOMMENDED- LOW RESISTANCE (VER 26), 2-35
MDF TEST RECOMMENDED- PERMANENT SIGNAL (VER 72), 2-80
MDF TESTABLE ONLY (VER MT), 5-23
MEASUREMENT UNIT FAILURE (VER FC), 4-34
MEMBER OF MLHG (VER MH), 5-22
MISSING LOAD DETECTED (VER L6), 5-11
MODEM CONNECTION FAILURE (VER FL), 4-42
MSU OUT OF SERVICE (VER FS), 4-48
MULTIPLE FAULTS DETECTED (VER 99), 2-95
NETWORK MANAGER FAILURE (NM), 5-31
NO BUSY DETECTOR AVAILABLE (VER BR), 3-49
NO DIALER AVAILABLE (VER BQ), 3-48
NO GDXC AVAILABLE (VER BC), 3-35
NO LINE RECORD IN SYSTEM (VER NL), 5-30
NO MA PACK AVAILABLE (VER BF), 3-38
NO MAB AVAILABLE (VER BG), 3-39
NO MODEM PORT AVAILABLE (VER BV), 3-53
NO MTB AVAILABLE (VER BD), 3-36
NO MTB TO PGTC AVAILABLE (VER BI), 3-41
NO MTB TO PGTC PORT AVAILABLE (VER BJ), 3-42
NO MTIB AVAILABLE (VER BE), 3-37
NO PMU AVAILABLE (VER BP), 3-47
NO PORT AVAILABLE (VER BL), 3-44
NO PRTC AVAILABLE (VER BH), 3-40
NO RINGERS FOUND (VER G8), 4-60
NO TEST PACKAGE AVAILABLE (VER BN), 3-46
NO TRUNK AVAILABLE (VER BM), 3-45
NOT AN ISDN LINE (VER IK), 4-76
NOT VALID IDENTIFIER (VER NP), 5-32
NT1 PRIMARY POWER FAIL (VER P9), 5-47
OE MISMATCH (VER IH), 4-74
OPEN IN (VER 3), 2-39
OPEN IN AND CROSS (VER 35), 2-45
OPEN IN REMOTE TERMINAL (VER 47), 2-62
OPEN ON PREMISES (VER 46), 2-61
OPEN OUT 2-PARTY OR BRIDGE LIFTERS (VER 44), 2-58
OPEN OUT AND CROSS (VER 18), 2-28
Index
OPEN OUT BALANCED (VER 41), 2-53

OPEN OUT IN CABLE (VER 42), 2-55
OPEN OUT NEAR DROP (VER 45), 2-59
OSCILLATOR PROBLEMS (VER C7), 3-64
OVRD-EXK/NNX COMBO NOT IN DATABASE (VER XA), 5-89
PAIR GAIN CHANNEL FAILURE (VER 55), 2-71
PAIR GAIN SYSTEM BUSY (VER 53), 2-69
PAIR GAIN SYSTEM FAILURE (VER 54), 2-70
PBX ROUTE ADVANCED TELEPHONE NUMBERS (VER SX), 5-61
PERMANENT SIGNAL (VER 74), 2-83
PGTC PATH SETUP BLOCKAGE (other) (VER BK), 3-43
POLARITY GUARD PROBLEMS (VER C3), 3-59
POOR BALANCE (VER 93), 2-90
POSSIBLE AMI BRITE DETECTED (VER IC), 4-70
POSSIBLE CO WIRING ERROR (VER 38), 2-48
POSSIBLE FAULTY TELEPHONE SET (VER P3), 5-41
POSSIBLE INVALID ACCESS (VER 34), 2-44
POSSIBLE PROTOCOL PROBLEM (VER PB), 5-49
POTS DETECTED ON DRY DSL LINE (VER ET), 4-22
POTS ONLY OR NON-COMBO CIRCUIT (VER EU), 4-23
POWER FAILURE (VER PF), 5-52
PROBABLY TEST OK (VER 0P), 2-13
PROTECTED SERVICE (VER SP), 5-56
REGISTRATION FAILED, 5-79
REMOTE SIG LOSS
UNKNOWN CAUSE (VER PI), 5-53
REMOTE TEST-EXPECT DELAYED RESULTS (VER LM), 5-16
REQUEST NOT ALLOWED IN THIS MODE (VER XN), 5-94
RESISTIVE FAULT AND DC FEMF (VER 17), 2-27
RESISTIVE FAULT AND OPEN (VER 95), 2-91
RINGER TEST- UNCATALOGED EQUIPMENT (VER G6), 4-59
RINGER TEST WITH NO RECORDS (VER G4), 4-57
RMU IN USE (VER BT), 3-51
RMU/CMU CONNECT FAILURE (VER FM), 4-43
ROH (VER 71), 2-79
RT COMM FAIL (VER FW), 4-51
RT CU SUSPECT (VER 59), 2-75
SECTIONALIZE WITH LONGER LPBK (VER IS), 4-83
SHORT - PROBABLY ROH (VER 75), 2-84
SHORT AND GROUND (VER 25), 2-34
SHORT FAULT (VER 22), 2-31
SHORT OR GROUND (VER 28), 2-38
SIGNAL LOSS FROM REMOTE END (VER PD), 5-51
SLEEVE CONTROL FAILURE (VER FD), 4-35
SPECIAL SERVICES REQUIRED (VER SS), 5-57
SSA ACCESS REQUIRED BEFORE REQUEST IS PERFORMED (VER TS), 5-66
STUCK RELAY - MA CP (VER FQ), 4-46
SWINGING RESISTANCE
FAULT (VER 23), 2-32
MARGINAL (VER 24), 2-33
SWITCH COMMON EQUIP BAD (VER 30), 2-40
SWITCH LOGIN FAILURE (VER EL), 4-18
SWITCH PROCESS TIMEOUT (VER T2), 5-63
SWITCH TEST ACCESS BLOCKAGE (VER BS), 3-50
SWITCH TEST ACCESS FAILURE (VER FJ), 4-40
SWITCH TO VG COMMUNICATION DOWN, 4-65
SYSTEM TIMEOUT (VER T1), 5-62
-26
Index
T1 FACILITY BAD (VER 48), 2-64

TBCU PROTOCOL TEST FAILURE - (OPEN) (VER FG), 4-38
TERMINATION MISMATCH (VER IT), 4-84
TERMINATION MISMATCH SUSPECTED (VER IL), 4-77
TEST EQUIP BUSY (VER F4), 4-29
TEST EQUIPMENT BUSY - PAIR GAIN ACCESS EQUIPMENT BUSY (VER B5), 3-29
TEST EQUIPMENT BUSY - SANITY OR DIAG IN PROGRESS (VER B2), 3-26
TEST EQUIPMENT BUSY - SIMULTANEOUS TEST REQUEST MADE (VER B3), 3-27
TEST EQUIPMENT FAILURE (VER F0), 4-25
TEST EQUIPMENT FAILURE (VER FX), 4-52
TEST EQUIPMENT OUT OF SERVICE (VER B4), 3-28
TEST HEAD COMM FAILURE (VER FZ), 4-53
TEST NOT MADE FROM THIS FE (VER ND), 5-25
TEST OK MTU (VER 0M), 2-12
TEST OK NOW (VER I0), 4-67
TEST OK PARTIAL TEST DONE (VER IP), 4-80
TEST OK WITH CPE AND MTU CONDITION (VER MC), 5-20
TEST SYSTEM ERROR (VER E0), 4-4
TEST SYSTEM ERROR (VER X7), 5-88
TEST TRANSFERRED - EXPECT DELAY (VER LF), 5-15
TESTABLE VIA STV OPTION (VER XO), 5-95
TESTABLE VIA THE STV MASK ONLY (VER XS), 5-98
TESTING ON DEDICATED PORT / DROP ACCESS FIRST (VT), 5-80
TOTALIZER DEFECT (VER C2), 3-58
TOTALIZER OPERATION PROBLEMS (VER C1), 3-57
TRAINING SCRIPT UNAVAILABLE (VER XT), 5-99
UDLC SIGNATURE FOUND - LTS TEST (VER NA), 5-24
UNEXPECTED CHANNEL TEST RESULTS (VER U5), 5-71
UNEXPECTED INTEGRATED PGS/UNEXPECTED UNIVERSAL PGS (VER U6), 5-72
UNEXPECTED INWARD SERVICE (VER U4), 5-70
UNEXPECTED ISDN TERMINATION (VER IB), 4-69
UNEXPECTED PBX SIGNATURE (VER U2), 5-68
UNEXPECTED RINGER TERMINATION (VER U3), 5-69
UNEXPECTED THERMISTORS (VER U1), 5-67
VALID 2 PARTY TERMINATION (VER G5), 4-58
VALID RINGER COUNT AND TERMINATION (G0), 4-54
VER 0 TEST OK, 2-4
bPON Testing, 2-4
VER 05 CHANNEL NOT TESTED, 2-16
VER 0A TEST OK ADSL, 2-5, 2-6
VER 0C CPE or HIGH RESISTANCE OPEN, 2-7
VER 0L NO FAULTS TO BENCHMARKED LENGTH, 2-11
VER 0M TEST OK - MTU CONDITION, 2-12
VER 0R TEST OK, 2-14
VER 0T OUT OF TOLERANCE CONDITION, 2-15
VER 11 CROSS FAULT, 2-19
VER 11 CROSS TO WORKING PAIR
FAULT, 2-18
Index
VER 12
AC FEMF FAULT, 2-20
VER 6 BUSY-SPEECH, 2-17
VER AA STATIC ADDRESSING VERIFICATION FAILED, 3-4
VER AB LOOK OUT ATM LOOPBACK FAILURE, 3-5
VER AC TRANSACTION STOPED, 3-6
VER AD DHCP ADDRESS RESOLUTION FAILURE, 3-7
VER AH HTTP ADDRESS TEST FAILURE, 3-8
VER AI IP PING FAILURE, 3-9, 3-11
VER AL ATM LOOPBACK FAILURE, 3-12
VER AM SYNC FAILURE - MODEM NOT DETECTED, 3-13, 3-14, 3-15
VER AP PPP AUTHENTICATION FAILURE, 3-16
VER AR IP TRACE ROUTE FAILURE, 3-18
VER AS SYNC FAILURE - MODEM DETECTED, 3-19
VER AS SYNC FAILURE - MODEm DETECTED, 3-19
VER AT THROUGHPUT TEST FAILURE, 3-20
VER AU HOSTNAME (DNS) TRANSLATION FAILURE, 3-21
VER AZ TEST COMPLETE - EXAMINE RESULTS, 3-23
VER B1 TEST NOT MADE, 3-25
VER B7 TEST EQUIP BUSY, 3-31
VER B8 ALL TRUNKS ARE BUSY BY OTHER USERS, 3-32
VER BA NO DCTU PORT AVAILABLE, 3-33
VER BO TEST EQUIPMENT BUSY - TIME OUT IN ACCESS, 3-24
VER E8 CANT SEND REQUEST TO APPROPRIATE FE, 4-12
VER E9 ISDN DIGITAL LINK NOT AVAILABLE, 4-13
VER EA LTE LOGIN ERROR, 4-14
VER ED DLC CONCENTRATOR COMM FAILURE, 4-17, 4-18
VER F6 DLC CONCENTRATOR INTERNAL ERROR, 4-31
VER HA ONT IS INACTIVE, 4-61
VER HB NON SERVICE AFFECTING ALARM PRESENT, 4-62
VER HJ SYSTEM AND BACKUP MEMORY RESET, 4-63
VER HK NON SERVICE AFFECTING ALARM PRESENT, 4-64
VER MH
MEMBER OF MADN, 5-22
VER OD OPEN IN OR DSL TERM, 2-8
VER OE OPEN OUT BALANCED OR DSL TERM, 2-9
VER PR XDSL CPE EQUIP PROBLEM, 5-54
VER S0 LINE IN SERVICE - ADD ANALYSIS, 5-55
VER W4 POTS Line Circuit Found On ADSL Line, 5-83
VER WC XTUC NOT RESPONDING, 5-84
VER WT XDSL MODEM IN TRANSITION PHASE, 5-85
VER XU ONT TEST HEAD NOT AVAILABLE, 5-100
VLAN PARAMETER MISMATCH, 3-17
VOICE QUALITY BELOW THRESHOLD (VQ), 5-78
VOIP EQUIPAGE ERROR (EV), 4-24
VOIP SERVER BUSY (VB), 5-75
VOIP TEST FAILURE (V0), 5-73
W2 LOAD COIL DETECTED, 5-82
WC XDSL LTE EQUIP PROBLEM, 5-84
WIDEBAND NOISE PROBLEM (VER W1), 5-81
WIRING ERROR - NT1 REVERSED (VER IA), 4-68
XDSL CARD IS NOT IN SERVICE (VER WX), 5-87
XDSL MODEM IN UNKNOWN STATE (VER WU), 5-86
Ver Codes
LOOK-OUT ATM LOOPBACK FAILURE, 3-5
VER AS SYNC FAILURE - MODEM DETECTED, 3-19
VER EB BSO MODULE EQUIPAGE ERROR, 4-15
-28

Test Results User Guide Toolgrade PDF

Uploaded by

Copyright:

Available Formats

You might also like

Test Results User Guide Toolgrade PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Test Results User Guide Toolgrade PDF

Uploaded by

Copyright:

Available Formats

Consumer Access Solutions

LoopCare Test OSS

Test Results User Guide

ELECTRONIC EMISSION NOTICE

2006, Tollgrade Communications, Inc., All Rights Reserved

Tollgrade Communications, Inc.

Revision Q (p/n 040-0357)

Release 2.15, December, 2006 ii

Test Results User Guide

About this Guide

Organization of This Guide

Individual LoopCare Tests

LoopCare VER Code Enhancement Features - DCTU and non-DCTU1-31

LoopCare Verification Codes (0-99)

VER 0A: TEST OK

VER 0B: CPE or HIGH RESISTANCE OPEN

VER 0C: CPE or HIGH RESISTANCE OPEN

VER 0D: OPEN IN OR DSL TERM

VER 0E: OPEN OUT BALANCED OR DSL TERM

VER 0H: ROH DETECTED DURING TEST

VER 0L: NO FAULTS TO BENCHMARKED LENGTH

VER 0M: TEST OK MTU

VER 0P: PROBABLY TEST OK

VER 0R: TEST OK

VER 0T: OUT OF TOLERANCE CONDITION

VER 05: TEST OK - CHANNEL NOT TESTED

VER 11: CROSS TO WORKING PAIR- FAULT

VER 12: AC FEMF FAULT

VER 13: HAZARDOUS POTENTIAL

Revision Q (p/n 040-0357)

Release 2.15, December, 2006 -iii

Test Results User Guide

VER 14: CROSS TO WORKING PAIR: MARGINAL

VER 15: DC FEMF MARGINAL

VER 16: AC FEMF MARGINAL

VER 17: RESISTIVE FAULT AND DC FEMF

VER 18: OPEN OUT AND CROSS

VER 21: GROUND FAULT

VER 22: SHORT FAULT

VER 23: SWINGING RESISTANCE: FAULT

VER 24: SWINGING RESISTANCE: MARGINAL

VER 25: SHORT AND GROUND

VER 26: MDF TEST RECOMMENDED- LOW RESISTANCE

VER 27: DC RESISTANCE- MARGINAL

VER 28: SHORT OR GROUND

VER 30: SWITCH COMMON EQUIP BAD

VER 31: INVALID LINE CIRCUIT

VER 32: CANNOT DRAW DIAL TONE

VER 33: CANT BREAK DIAL TONE

VER 34: POSSIBLE INVALID ACCESS

VER 35: OPEN IN AND CROSS

VER 36: LINE CIRCUIT AND DIAL TONE PROBLEM

VER 37: DIAL TONE BURST DETECTED

VER 38: POSSIBLE CO WIRING ERROR

VER 40: CO EQUIP SUSPECT

VER 41: OPEN OUT BALANCED

VER 42: OPEN OUT IN CABLE

VER 43: HIGH RESISTANCE OPEN