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-1376TIE-TRK (Tie Trunk)
10
7 ABORT The conference circuit test was aborted.
1. Retry the command at 1-minute intervals a maximum of 5 times.
2. If the test continues to abort, escalate the problem.
129 ABORT The 404-Hz reflective loop around test aborted. Response to the test
request was not received within the allowable time period.
131 The 1004-Hz reflective loop around test aborted. Response to the test
request was not received within the allowable time period.
133 The 2804-Hz reflective loop around test aborted. Response to the test
request was not received within the allowable time period.
1. Retry the command at 1 minute intervals for a maximum of 5 times.
2. If the test continues to abort, escalate the problem.
1000 ABORT System resources required to run this test are not available. The trunk may
be busy with a valid call. Use the display trunk xx command 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, the port is unavailable for certain tests.
(Refer to the "Status Commands" section in Chapter 8, ‘‘
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 active, but the port is not in use (no calls), check
the Error Log for Error Type 1025 (see Error Log table for a description
of this error and required actions). The port may be locked up.
2. If the port status is idle, retry the command at one-minute intervals a
maximum of five times.
3. 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 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.
Table 10-477. TEST #33 Loop Around and
Conference Circuit Test — Continued
Error
Code
Test
Result Description/ Recommendation
Continued on next page