DEFINITY ECS Release 8.2 Maintenance for R8.2csi
555-233-119 Issue 1
April 2000
Maintenance Objects
3-831MET-LINE (MET Line)
3
Table 3-360. TEST #62 MET Line Ringer Update Test
Error
Code
Test
Result Description/ Recommendation
3 ABORT This port may have been busied out by system technician.
1. Look in the Error Log for Error Type 18 (port busied out) for this
port. If this error type is present, then release the port via the
release station <extension> command and run the test again.
2. Make sure that the terminal is connected.
3. Retry the command at 1-minute intervals a maximum of 5 times.
1000 ABORT System resources required to run this test are not available. The port
may be busy wit h a vali d call. Us e 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. 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 idle, then retry the command at 1-minute
intervals a maximum of 5 times.
FAIL Internal System Error.
1. Retry the command at 1-minute intervals a maximum of 5 times.
PASS Hybrid Station Ringer Update passed.
1. If complaints still exist, investigate using other circuit pack tests,
and by examining the terminal, wiring, and connec tions.
0NO
BOARD The test could not relate the internal ID to the port (no board). This
could be due to incorrect translations, no board is inserted, an
incorrect board is inserted, or an insane board is inserted.
1. Check to ensure that the board translations are correct. Use the list
config command, and resolve any problems that are found.
2. If the board was found to be correctly inserted in step 1, issue the
busyout board command.
3. Issue the reset board command.
4. Issue the release busy board command.
5. Issue the test board long command. This should re-establish the
linkage between the internal ID and the port. If this is not the case,
check to ensure that there is a valid board inserted.
Continued on next page