19.12.2012 Views

Demand test descriptions and error codes - Avaya Support

Demand test descriptions and error codes - Avaya Support

Demand test descriptions and error codes - Avaya Support

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Maintenance <strong>Dem<strong>and</strong></strong> Tests<br />

Table 293: Port Diagnostic Test (#35) 2 of 6<br />

Error<br />

Code<br />

Test<br />

Result<br />

Description / Recommendation<br />

1000 ABORT System resources required to run this <strong>test</strong> are not available.<br />

ALARM-PT: The port may be reporting an external device alarm.<br />

1. Enter <strong>test</strong> external-device-alarm port location to<br />

determine whether the port is reporting an EXT-DEV failure.<br />

2. If the port has no EXT-DEV failures, retry the comm<strong>and</strong> at<br />

1-minute intervals up to 5 times.<br />

ANL-16-L, ANL-LINE, AN-LN-PT, MET-LINE, RANL-STA: The port<br />

may be busy with a valid call.<br />

1. Enter display port location to determine the station<br />

extension or attendant number of the port.<br />

2. Enter status station extension or status attendant<br />

extension to determine the service state of the port. If the<br />

service state indicates that the port is in use, wait until the port is<br />

idle before re<strong>test</strong>ing. Attendants are always in use (off-hook) if the<br />

h<strong>and</strong>set is plugged in <strong>and</strong> the port is not busied out.<br />

3. If the port status is idle, retry the comm<strong>and</strong> at 1-minute intervals a<br />

maximum of 5 times.<br />

DID-TRK: The port may be busy with a valid call.<br />

1. Enter display port location to determine the trunk group/<br />

member number of the port.<br />

2. Enter status trunk to determine the service state of the port. If<br />

the port is in use, wait until it is idle before <strong>test</strong>ing.<br />

3. If the port status is active but the port is idle (no calls), check the<br />

<strong>error</strong> log for Error Type 513 for this maintenance object. The port<br />

may be locked up.<br />

4. If the port status is idle, busyout <strong>and</strong> release the trunk, <strong>and</strong> retry<br />

the comm<strong>and</strong> at 1-minute intervals up to 5 times.<br />

5. If the <strong>test</strong> continues to abort, check for wiring <strong>error</strong>s toward the<br />

CO which may cause the trunk to lock up.<br />

6. If the wiring is good <strong>and</strong> the <strong>test</strong> continues to abort, replace the<br />

circuit pack or media module.<br />

1126 Maintenance Alarms for Communication Manager, Media Gateways <strong>and</strong> Servers<br />

2 of 6

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!