Secondary Signaling Link Hardware Check (#639) - Avaya G250 Maintenance Manual

Avaya Communication Manager controlled maintenance
Table 82: TEST #637 Remote Layer 3 Query (continued)
Error Test
Code Result
PASS
Any NO
BOARD

Secondary Signaling Link Hardware Check (#639)

The ISDN-PRI Signaling Group D-Channel port depends on the health of the MM710 on which
it resides. This test will fail if there are problems with either the ISDN-PRI Secondary D-channel
port or the MM-DS1 media module. This test will abort if a Secondary D-channel is not
administered for the signaling group. If there are problems with the ISDN-PRI Secondary
Signaling Channel port (ISDN-LNK), also investigate the MM710.
180 Maintenance for the Avaya G250 and Avaya G350 Media Gateways
Description/ Recommendation
A message was composed and sent to the far-end switch or terminal
adapter. The ISDN PRI specification allows up to 2 minutes for a reply.
Check the Error Log for ISDN-SGR (ISDN-PRI Signaling Group) for
errors of type 2305 for evidence of a Remote Layer 3 Query failure. If no
new errors were logged since this test was run, then this switch and the
far-end switch or terminal adapter can exchange call control messages. If
there is still a problem with a particular ISDN trunk or PRI endpoint,
busyout the trunk and run the long test sequence, paying particular
attention to the results of Test #258 (ISDN Test Call).
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
GGGVS command to administer the MG-DS1 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 use the
busyout board command.
Use the reset board command.
Use the release busy board command.
Use the test board long command.
This should re-establish the linkage between the internal ID and the port.
2 of 2