DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126 Issue 4
June 1999
Maintenance Object Repair Procedures
9-1045MET-LINE (MET Line)
9
Table 9-414. TEST #35 Port Diagnostic Test
Error
Code Test
Result Description/ Recommendation
ABORT Internal system error.
1. 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 with a valid call.
1. Use the display port UUCSSpp command to determine the station
extension of the port. Use the status station command to determine the
service state of the port. If the port is in use, wait until the port is idle before
testing.
2. If the port status is idle, then retry the command at 1-minute intervals a
maximum of 5 times.
1004 ABORT The port was seized by a valid c all during the test. The test has been aborted.
1. Use the display port UUCSSpp command to determine the station
extension of the port. Use the status station command to determine the
service state of the port. If the port is in use, wait until the port is idle before
testing.
NOTE:
The battery feed circuitry is tested for proper battery voltage b y testing
the switchhook state. In response to the test message, the on-board
firmware terminates the line and checks for switch-hook presence. The
termination is then removed, a nd a check is made for no sw itch-hook
presence. The MET set must be on-hook for the test to execute.
2. If the port status is idle, then retry the command at 1-minute intervals a
maximum of 5 times.
1018 ABORT Test disabled via software patc h.
2000 ABORT This port may have been busied out.
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.
2100 ABORT Could not allocate the necessary system resources to run this test. This could
be due to a failure to sei ze the port.
1. Retry the command at 1-minute intervals a maximum of 5 times.
Continued on next page