ABORT

Necessary system resources could not be allocated to run this test.

Retry the command at 1-minute intervals no more than 5 times.

If the test continues to abort, escalate the problem.

1004

ABORT

A valid call seized the port during the test and aborted the test.

Use the display board GGGVSpp command to determine the station extension.

Use the status station extension command to determine the service state of the port.

If the port is in use, wait until the port is idle before testing. Retry the command at 1-minute intervals no more than 5 times.

If the test continues to abort, escalate the problem.

1005

ABORT

This test was aborted due to a configuration problem. The test is not applicable for this type of analog port. This error can be ignored.

1006

ABORT

The port is out-of-service. The busy station extension command has been given to this port.

Look for error type 18 (port busied out) for this port. If this error is present, release the port (release station extension), and run the test again.

Make sure that the terminal is connected and in service, and then retest.

2000

ABORT

Response to the test request was not received within the allowable time period.

2100

ABORT

System resources required to run this test are not available.

Retry the command at 1-minute intervals no more than 5 times.

If the test continues to abort, escalate the problem.

1

FAIL

The switchhook audit failed. This result does not indicate a hardware problem. The other updates were not performed because of this failure. This may occur if the audit is performed at the same time the terminal equipment goes off-hook.

Use the status station extension command to determine when the port is available.

Retry the command at 1-minute intervals no more than 5 times.

If the test continues to fail, escalate the problem.

5

FAIL

The message waiting lamp update failed. This may be an internal software error. The translation and ringer updates were not performed because of this failure.

7

FAIL

The translation update failed. There may be an internal software error. The ringer update was not performed because of this failure.

8

FAIL

The ringer update failed. There may be an internal software error.

Retry the command at 1-minute intervals no more than 5 times.

If the test continues to fail, escalate the problem.

PASS

The software and the port processor have the same status. Investigate user-reported troubles on this port by running other port tests, by examining station wiring, or by inspecting the station.

Any

NO BOARD

The test could not relate the internal ID to the port (no board). This result could be due to incorrect translations, no board is inserted, an incorrect board is inserted, or an insane board is inserted.

Check to make sure that the board translations are correct. Use the list configuration command, and resolve any problems.

If the board is correctly inserted, issue the busy board GGGVS command.

Issue the reset board GGGVS command.

Issue the release board GGGVS command.

Issue the test board GGGVS long command. This re-establishes the link between the internal ID and the port.

If this is not the case, check to make sure that a valid board is inserted.