DEFINITY Enterprise Communications Server Release 6
Maintenance for R6vs/si
555-230-127
Issue 1
August 1997
Maintenance Object Repair Procedures
Page 10-411DID-TRK (DID Trunk)
10
1000 ABORT System resources required to run this test are not available. The port may
be busy with a valid call. Use the display port PCSSpp command to
determine the station extension, attendant number, or trunk group/member
number of the port. Use the status station, status attendant, or status
trunk command to determine the service state of the port. If the service
state indicates that the port is in use, then the port is unavailable for certain
tests. (Refer to the "Status Commands" section in Chapter 10,
"Maintenance Commands and Trouble-Clearing Aids", for a full description
of all possible states.) You must wait until the port is idle before retesting.
Attendants are always in use (off-hook) if the handset is plugged in and the
port is not busied out.
1. If the port status is active but the port is not in use (no calls), then
check the Error Log for Error Type 513 (see Error Log table for
description of this error and required actions). The port may be locked
up.
2. If the port status is idle, then retry the command at one-minute
intervals a maximum of five times.
3. If the test continues to abort, escalate the problem.
1001 ABORT Could not allocate the necessary system resources to run this test. This
could be due to a failure to seize the port.
1. Retry the 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 (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 one-minute intervals a maximum of five 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 test at one-minute intervals a
maximum of five times.
4. If the test continues to abort, escalate the problem.
Table 10-133. TEST #6 NPE Crosstalk Test — Continued
Error
Code
Test
Result Description/ Recommendation
Continued on next page