Avaya S8700 Maintenance Manual page 615

UDS1-BD (UDS1 Interface Circuit Pack)
Table 8-544. Test #1420 Echo Canceller Test — Continued
Error Test
Code Result Description / Recommendation
2012 ABORT Internal system error.
1. Retry the command at 1-minute intervals up to 5 times.
2100 ABORT Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
2500 ABORT Internal system error.
1. Retry the command at 1-minute intervals up to 5 times.
1400, FAIL The Echo Cancellation test has failed:
1401
Echo Cancellation is no longer being supplied by the board. Clear the alarm
using the following commands: busyout board UUCSS, test board UUCSS
long, release board UUCSS. If the test still fails, replace the circuit pack.
PASS The Echo Cancellation feature is functioning properly.
0 NO The test could not relate the internal ID to the port (no board). This could be
BOARD due to incorrect translations, no board is inserted, an incorrect board is
inserted, or an insane board is inserted.
1. Verify that the board's translations are correct. Execute the add ds1
2. If the board was already administered correctly, check the error log to
3. If the board was found to be correctly inserted in step 1, then issue the
4. Issue the reset board command.
5. Issue the release busy board command.
6. Issue the test board long command.
This should re-establish the linkage between the internal ID and the port.
555-233-142
Error 1400 - Echo canceller function failed. The Echo Canceller Function
test, which is executed by firmware, failed.
Error 1401 - Echo canceller memory failed. The Echo Canceller Memory
test, which is executed by firmware, failed.
NOTE:
When this test fails, echo cancellation will be bypassed on every channel
of the board. The circuit pack can still be used for a T1/E1 line interface
without echo cancellation. This capability provides limited service for the
customer until the circuit pack can be changed out.
UUCSS command to administer the UDS1 interface if it is not already
administered.
determine whether the board is hyperactive. If so, the board was shut
down. Reseating the board will re-initialize it.
busyout board command.
Continued on next page
Issue 1 May 2002 8-1311