Filter
Top Products
DEFINITY Enterprise Communications Server Release 6
Maintenance for R6vs/si
555-230-127
Issue 1
August 1997
Maintenance Object Repair Procedures
Page 10-1454UDS1-BD (UDS1 Interface Circuit Pack)
10
Table 10-493. TEST #135 Internal Loop Around Test
Error
Code
Test
Result Description/ Recommendation
2012 ABORT Internal System Error
1. Retry the reset board command at 1-minute intervals a maximum of 5
times.
2. If the test continues to abort, escalate the problem.
1002 ABORT The system could not allocate time slots for the test. The system may be
under heavy traffic conditions or it may have time slots out-of-service due
to TDM-BUS errors. Refer to TDM-BUS Maintenance documentation to
diagnose any active TDM-BUS errors.
1. If system has no TDM-BUS errors and is not handling heavy traffic,
repeat test at 1-minute intervals a maximum of 5 times.
2. If the test continues to abort, escalate the problem.
1003 ABORT The system could not allocate a tone receiver for the test. The system may
be oversized for the number of Tone Detectors present or some Tone
Detectors may be out-of-service.
1. Look for TTR-LEV errors in the Error Log. If present, refer to TTR-LEV
(TTR Level) Maintenance documentation.
2. Look for TONE-PT errors in the Error Log. If present, refer to TONE-PT
(Tone Generator) Maintenance documentation.
3. If neither condition exists, retry the reset board command at 1-minute
intervals a maximum of 5 times.
4. If the test continues to abort, escalate the problem.
1004 ABORT Received an incoming call on a port of the UDS1 circuit pack during the
test.
1. Enter the busyout board PCSS command to put all trunks or ports of
the UDS1 Interface circuit pack to out-of-service state.
2. Retry the reset board command at 1-minute intervals a maximum of 5
times.
3. If the test continues to abort, escalate the problem.
1015 ABORT Ports on the UDS1 Interface circuit pack have not been busied out to
out-of-service.
1. Enter the busyout board PCSS command to put all trunks or ports of
the UDS1 Interface circuit pack into the out-of-service state.
2. Retry the reset board command.
3. If the test continues to abort, escalate the problem.
Continued on next page