Call State Audit Test (#257)

If a call is active on the trunk, the switches on both sides of the connection should agree on the ISDN state of the call, as defined in the ISDN Protocol Specification. This test audits internal call state data by querying the far-end switch as to the ISDN state of the call. It can be helpful when trying to clear a hung call. If the internal call state data on the near-end switch is different than that of the far-end switch, then the call will be torn down.

As with Test #256 (Service State Audit), a PASS simply means that an appropriate message was composed and sent to the far-end switch. The ISDN Specification allows up to 2 minutes for a reply. If a reply is not received within the 2 minute window, a protocol time-out violation will be recorded in the error log against the associated signaling channel (ISDN-LNK, Error Type 1).

Table 50. TEST #257 Call State Audit Test �
Error Code	Test Result	Description/ Recommendation
1018	ABORT	Maintenance is disable on this trunk. Enable maintenance by entering "y" in the "Maintenance Tests?" field on page 2 of the change trunk-group form.
1019	ABORT	An audit is already in progress. Wait 2 minutes and try again.
1113	ABORT	The signaling link has failed, so the system cannot send any messages on behalf of this trunk. Check the results of Test #255 (Signaling Link State Check).
1114	ABORT	The signaling link is in a transitional state. Retry the command at 1-minute intervals for a maximum of 5 times.
1116	ABORT	The trunk is in an out-of-service ISDN service state. A call cannot be present if the trunk is in an ISDN out-of-service state, so a call state audit would be inappropriate. No action necessary. (Use the status trunk group#/member# command to investigate the ISDN state of the trunk).
2100	ABORT	Could not allocate the necessary system resources to run this test. Retry the command at 1-minute intervals for a maximum of 5 times.
	FAIL	Internal system error Retry the command at 1-minute intervals for a maximum of 5 times.
	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 GGGVS command to administer the DS1-MM 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 issue the busyout board command. Issue the reset board command. Issue the release busy board command. Issue the test board long command. This should re-establish the linkage between the internal ID and the port.