Filter
Top Products
Communication Manager Maintenance-Object Repair Procedures
1466 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ISDN Test Call Test (#258)
Note:
Note: S8300 / G700: On the G700, this test aborts with Error Code 1412.
This test performs a far-end loop around to a far-end switch over an ISDN trunk. The trunk’s
service state must be in service, maint-NE, or out-of-service/NE, and no call can be active on
the trunk. The test call can be initiated as part of a long test sequence, or as an individual test,
as described below. This test is valid only for systems using country protocol 1 (including US),
or when the far end has loop-around capability.
A test call connection is established to a far-end switch over the ISDN trunk to be tested. The
digital port on a TN711D Maintenance/Test circuit pack generates a test-pattern bit stream that
is sent to the far-end switch and echoed back. The received pattern is then compared to the
sent pattern and checked for errors that indicate a loss of integrity on the communications path.
If a test call is running when scheduled maintenance starts, the green LED is turned off. To
determine whether a test call is still running:
● Enter list isdn-testcall and status isdn-testcall.
● Check for a lit amber LED on the Maintenance/Test circuit pack.
PASS This switch sent a call state auditing message to the far-end switch to verify
the state of the call active on this trunk. If a call state mismatch is found,
then the call will be torn down within two minutes. If no call was active, then
no message was sent.
Any
NO
BOARD
The test could not relate the internal ID to the port (no board). This could be
due to incorrect translations, no board is inserted, an incorrect board is
inserted, or an insane board is inserted.
Ensure that the board translations are correct. Execute the add ds1
location to administer the MM710 interface if it is not already
administered.
If the board was already administered correctly, check the error log to
determine whether the board is hyperactive. If this is the case, the board is
shut down. Reseating the board will re-initialize the board.
If the board was found to be correctly inserted in step 1, then enter the
busyout board location.
Enter reset board location.
Enter release board location.
Enter test board location long.
This should re-establish the linkage between the internal ID and the port.
Table 529: Test #257 Call State Audit Test (continued)
Error
Code
Test
Result
Description / Recommendation
2 of 2