HYB-LINE (Hybrid Line)
Issue 1 May 2002
8-913
555-233-143
1004
ABORT
The port was seized by a valid call during the test. The test has been aborted.
1. Use the display port UUCSSpp command to determine the station
extension number of the port. Use the status station command to
determine the service state of the port. If the port is in use, wait until it is
idle before testing.
2. Retry the command at 1-minute intervals up to 5 times.
1392
ABORT
This port is currently a TTI port and the test will not execute on it.
1. Verify that the port is a TTI port using either the display port command
(the display shows that the port is a TTI port) or the list config command
(the display shows a
t
for the port).
2. If either list config or display port indicate that the port is not a TTI port,
escalate the problem. If both commands indicate that the port is a TTI port,
the abort is correct, and no action is necessary.
2000
ABORT
Response to the test request was not received within the allowable time period.
1. Retry the command at 1-minute intervals up to 5 times.
2012
ABORT
Internal system error.
1. Retry the command at 1-minute intervals up to 5 times.
2100
ABORT
The system could not allocate a tone generator for the test.
1. Resolve any TONE-PT errors.
2. If no TONE-PT errors appear in the Error Log, retry the test at 1-minute
intervals up to 5 times.
2103
ABORT
The system could not make the conference connection for the test.
1. Retry the command at 1-minute intervals up to 5 times.
7
FAIL
Conference test failed. User may be able to use conference circuit without
difficulty in some cases. In other extreme cases, conference calling will be
totally restricted.
The failure may be due to off-board circumstances, the most common of which
is an off-hook occurring during the test. Also, check the error logs against the
GPTD-BD, the TONE-BD, and the TONE-PT.
1. This error can be caused by a disconnected terminal. First, ensure that the
terminal is connected and the wiring is OK.
2. Then, issue the display port and status station commands to determine
whether the station is idle. If so, issue the test port command for this port.
3. If test continues to fail, issue the busyout port and the release port
commands, and then retest the port.
4. It is possible that the port may still be functional from a user’s point of view.
Table 8-352.
Test #57 Hybrid Circuit and Conference Circuit Test —
Continued
Error
Code
Test
Result
Description / Recommendation
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 ...