Maintenance-Object Repair Procedures
555-233-143
8-510
Issue 1 May 2002
Table 8-206.
Test #7 Conference Circuit Test
Error
Code
Test
Result
Description / Recommendation
ABORT
Could not allocate the necessary system resources for this test.
1. Retry the command at 1-minute intervals up to 5 times.
1000
ABORT
System resources required for this test were not available. The port may be
busy with a valid call.
1. Use display port UUCSSpp to determine the trunk group/member number
of the port. Use status trunk to determine the service state of the port. If
the port is in use, wait until it is idle before testing.
2. If the port status is active but the port is idle (no calls), check the error log
for Error Type #1025. The port may be locked up.
3. If the port status is idle, retry the command at 1-minute intervals up to 5
times.
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.
1. If the system has no TDM-BUS errors and is not handling heavy traffic and
the port status is idle, retry the command at 1-minute intervals up to 5
times.
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. Issue the list measurements tone-receiver command to display
information about the tone receivers.
1. Resolve any TTR-LEV errors.
2. Resolve any TONE-PT errors.
3. If neither condition exists, retry the command at 1-minute intervals up to 5
times.
1004
ABORT
The port was seized by a user for a valid call.
1. Use display port UUCSSpp to determine the trunk group/member number
of the port. Issue the status trunk command to determine the service
state of the port. If the port is in use, wait until it is idle before testing.
2. If the port status is idle, retry the command at 1-minute intervals up to 5
times.
Continued on next page
Summary of Contents for S8700 Series
Page 50: ...Maintenance Architecture 555 233 143 1 26 Issue 1 May 2002 ...
Page 74: ...Initialization and Recovery 555 233 143 3 12 Issue 1 May 2002 ...
Page 186: ...Alarms Errors and Troubleshooting 555 233 143 4 112 Issue 1 May 2002 ...
Page 232: ...Additional Maintenance Procedures 555 233 143 5 46 Issue 1 May 2002 ...
Page 635: ...status psa Issue 1 May 2002 7 379 555 233 143 status psa See status tti on page 7 406 ...
Page 722: ...Maintenance Commands 555 233 143 7 466 Issue 1 May 2002 ...