User manual

DEFINITY Enterprise Communications Server Release 6
Maintenance for R6vs/si
555-230-127
Issue 1
August 1997
Maintenance Object Repair Procedures
Page 10-309CO-TRK (CO Trunk)
10
However, all else being normal, these errors should not affect the
customer.
b. Refer to TIE-TRK (Tie Trunk) Maintenance documentation for a description
of this test.
c. ATMS test are not part of either sequence. They are run either on demand
with the test analog-testcall command or via the ATMS schedule.
Dial Tone Test (#0)
This test attempts to seize a port and checks for the return of a dial tone.
Table 10-101. TEST #0 Dial Tone Test
Error
Code
Test
Result Description/ Recommendation
ABORT Could not allocate system resources to run this test.
1. Retry the command at one-minute intervals a maximum of five times.
2. If the test continues to abort, escalate the problem.
1000 ABORT System resources required to run this test are not available. The port may
be busy with a valid call. Use the command display port PCSSpp to
determine the trunk group/member number of the port. Use the 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.
1. If the port status is idle, then retry the command at one-minute
intervals a maximum of five times.
2. If the test continues to abort, escalate the problem.
1001 ABORT System resources required to run this test were not available. This could
be due to a failure to seize the port.
1. Retry the command at 1 minute intervals for 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 the 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.
Continued on next page