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.

Table 303: Ringing Application Test (#51) 2 of 2<br />

Error<br />

Code<br />

Test<br />

Result<br />

Ringing Application Test (#51)<br />

2000 ABORT There was no response from the board.<br />

1. If Error Type 1538 (hyperactivity) is present in the <strong>error</strong> log, follow<br />

the maintenance strategy that is recommended for this Error Type.<br />

2. Reset the circuit pack or media module <strong>and</strong> rerun the <strong>test</strong>.<br />

3. If the <strong>test</strong> still aborts, check the off-board wiring <strong>and</strong> the terminal.<br />

4. Retry the <strong>test</strong>. If the <strong>test</strong> still aborts, replace the circuit pack.<br />

2100 ABORT Could not allocate the necessary system resources to run <strong>test</strong>.<br />

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

FAIL No ringing current is detected. The ringing application circuitry on this<br />

circuit pack probably is not healthy.<br />

1. Retry the comm<strong>and</strong> again.<br />

2. If the <strong>test</strong> continues to fail, look for RING-GEN <strong>error</strong> in Error Log.<br />

a. If there are RING-GEN <strong>error</strong>s, see RING-GEN (Analog Ring<br />

Generator) <strong>and</strong> try to resolve any problem(s).<br />

b. If there are no RING-GEN <strong>error</strong>s, replace the circuit pack.<br />

PASS Ringing current is detected or this <strong>test</strong> is not executed on this circuit pack.<br />

0 NO<br />

BOARD<br />

Description / Recommendation<br />

See NO BOARD for the repair procedures.<br />

2 of 2<br />

Issue 5 May 2009 1157

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

Saved successfully!

Ooh no, something went wrong!