User manual
DEFINITY ECS Release 8.2 Maintenance for R8.2csi
555-233-119 Issue 1
April 2000
Maintenance Objects
3-1118TIE-TRK (Tie Trunk)
3
Audit Update Test (#36)
This test sends updates of the Tie Trunk port translation for all ports on the circuit
pack that have been translated. The update is non-disruptive and guards against
possible corruption of translation data contained on the board. No response
message is expected from the circuit pack once it receives translation updates.
The port translation data for non-TN497 circuit packs includes the following:
Immediate, automatic, wink-start or delay dial trunk, rotary or DTMF
senderization in or out, disconnect timing from 10 to 2550ms in 10ms increments,
and DMTF time slot. (Continuous-seize-ack is also included for the TN2140B
circuit pack.)
Table 3-493. TEST #36 Audit Update Test
Error
Code
Te s t
Result Description/ Recommendation
ABORT Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals a maximum of 5 times.
1006 ABORT (TN497 circuit pack only.) The port is in the out-of-service state. The test
cannot be run.
1. Retry the command once the port is in service.
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 a maximum of 5 times.
FAIL Internal System Error.
1. Retry the command at 1-minute intervals a maximum of 5 times.
PASS This test passed. Translation information was successfully updated on the
circuit pack.
1. If signaling troubles are reported, verify translation information for this
port.
(Non-TN497 circuit packs only.) If the trunk is busied out, the test does not
run, but it does return PASS.
To verify that the trunk is in-service:
1. Enter status trunk command to verify 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.
2. Enter release trunk command to put trunk back into in-service.
3. Retry the test command.
Continued on next page