Avaya S8700 Maintenance Manual page 2371

TIE-TRK (Analog Tie Trunk)
Audit Update Test (#36)
This test sends to the circuit pack updates of translations for every administered
port on the circuit pack. It is non-disruptive and guards against possible
corruption of translation data contained on the circuit pack. No response is
expected from the circuit pack. Port translation data includes:
Start type: immediate, automatic, wink-start, or delay dial
Rotary or DTMF senderization in or out
Disconnect timing: 10 to 2550 ms in 10-ms increments
DMTF time slot
Continuous-seize-ack? (TN2140)
Table 8-641. Test #36 Audit Update Test
Error Test
Code Result Description / Recommendation
ABORT Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
2100 ABORT Could not allocate the necessary system resources to run the test. This could
be due to a failure to seize the port.
1. Retry the command at 1-minute intervals up to 5 times.
FAIL Internal system error
1. Retry the command at 1-minute intervals up to 5 times.
PASS This test passed. Translation information was successfully updated on the
circuit pack. If the trunk is busied out, the test does not run but returns a PASS
(except on TN439 and TN497).
1. If signaling troubles are reported, verify translation information for this port.
2. To verify that the trunk is in-service, enter status trunk command to verify
3. Enter release trunk command to put trunk back into in-service.
4. Retry the test command.
0 NO The test could not relate the internal ID to the port (no board).
BOARD
1. Verify that the board's translations are correct. Translate the board, if
2. Issue the busyout board command.
3. Issue the reset board command.
4. Issue the release busy board command.
5. Issue the test board command. This should re-establish the linkage
555-233-143
that the trunk is in-service. If the trunk is in-service, no further action is
necessary. If the trunk is out-of-service, continue to Step 2.
necessary.
between the internal ID and the port.
Continued on next page
Issue 1 May 2002 8-1649