Service State Audit (#256)

As noted in the general description for DS1 ISDN Trunk, these trunks may be in one of several service states. This test performs a Service State Audit with the far-end switch.

For interfaces using country protocol 1 (including the US) the Service State Audit executes in all trunk service states. A message is sent to the far-end switch to ensure that both sides agree on the service state. A PASS for this test simply means that the message has been successfully sent. Two minutes are allowed for a reply. If no reply is received within that 2 minute window, the message is sent out again. If that attempt fails, an Error Type 3073 will be logged and the switch will attempt another Service State Audit every 15 minutes. If the trunk was initially in-service, it is placed in the maintenance/far-end state. No outgoing calls will be placed over this trunk, but incoming calls will be accepted. If an incoming call is presented with the trunk in such a state, a Service State Audit is immediately be attempted (the switch does not wait for the 15-minute cycle, but tries to recover immediately).

For interfaces not using country protocol 1, the Service State Audit executes only if the trunk is in the out-of-service/far-end state. A message is sent to the far-end switch to attempt to bring the trunk back into the in-service state. A PASS for this test simply means that the message has been successfully sent. Two minutes are allowed for a reply. If no reply is received within that two minute window, the message is sent out again. If again no response is received within two minutes, the trunk remains in the out-of-service/far-end state. The switch will attempt another Service State Audit after an hour has passed.

To investigate the service state of the DS1 ISDN Trunk, issue the status trunk group#/member# command.

Table 49. TEST #256 Service State Audit Test �
Error Code	Test Result	Description/ Recommendation
1000	ABORT	Resources required to run this test were not available. The port may be on a valid call or initializing. Use status station or status trunk to determine when the trunk is available for testing. Check the results of Test #255.
1018	ABORT	Maintenance is disabled on this trunk. Enable maintenance by entering "y" in the "Maintenance Tests?" field on page 2 of the change trunk-group form.
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 and consult procedures for ISDN-SGR (ISDN-PRI Signaling Group) in this chapter.
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 not in the out-of-service/far-end state, which is required to run this test on systems using a country protocol other than 1.
1117	ABORT	A service state audit message is outstanding. Wait 2 minutes and then try again.
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.
1113	FAIL	The signaling link has failed; the system cannot send any messages on behalf of this trunk. Consult procedures for ISDN-SGR (ISDN-PRI Signaling Group) and ISDN-LNK (ISDN Signaling Link Port).
	FAIL	Internal system error Retry the command at 1-minute intervals for a maximum of 5 times.
	PASS	Wait 4 minutes and then check the Error Log for any new errors of type 3073. If there are none, then both sides of the ISDN connection agree on the service state; the negotiation succeeded. If there is a new 3073 error, then the negotiation failed (the far-end switch twice failed to respond within 2 minutes). The switch will automatically retry every 15 minutes. If the trunk was initially in-service, it is now placed in the maintenance/far-end state. Incoming calls will be accepted, but no outgoing calls can be originated. If an incoming call is presented, another Service State Audit will be immediately performed in an attempt to put the DS1 ISDN Trunk in the proper state.
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.