Error Type 0: Run the short test sequence first. If every test passes, run the long test sequence. Refer to each appropriate test’s description, and follow its recommended procedures.

Error Type 2: ISDN-BRI signaling protocol violation. Timers associated with layer-3 messages expired before a required response was received. In the following table, the aux data column indicates which timer has just expired.

The switch sent a message to an endpoint that did not respond in the time allowed. This may be due to failure of the point-to-point signaling link or because of a problem in the ASAI adjunct. To repair, enter test station extension and perform the associated repair procedures for those tests.

Error Type 257: An endpoint is not responding to the service state query message sent to the adjunct or to the endpoint. This error causes an alarm to be raised. The alarm is retired when the switch receives a response to the service state query to the endpoint or to the adjunct.

When this error occurs for an ASAI adjunct, the Aux Data field indicates the state of the ASAI link and whether an invalid response or no response was received to the query from the switch, as shown in the following table:

See the section on maintenance SAT commands in Maintenance Commands for Avaya Aura® Communication Manager, Branch Gateways and Servers for an explanation of the ASAI link states.

For ASAI or Avaya adjuncts, the switch queries the adjunct every two minutes. The Layer 3 Query test is not executed for ASAI or Avaya adjuncts through a command entered from the management terminal. While alarmed for this error, the switch takes the associated port out-of-service for five seconds every 15 minutes. This action attempts to stimulate recovery actions to be taken by the adjunct.

When this error occurs for an ASAI or Avaya adjunct, the service technician should:

1. Execute test station extension and perform the associated repair procedures.

2. Check the health of the adjunct by following the recommended repair procedures of the manufacturer of the adjunct if the preceding step does not resolve the problem.

Error Type 351: logged against an ASAI endpoint when the adjunct asks the switch to suspend maintenance on the ASAI endpoint. Clear with busyout and release of the ASAI station.

Error Type 513: the endpoint sent more messages than the switch could handle. The switch suspends the reception of messages from the endpoint for a short period of time. There is no repair procedure for this error. If the condition persists, replace the endpoint.

Error Type 769: an ASAI endpoint’s associated signaling link has too much traffic related to link establishment. This occurs when the signaling link is alternating between assigned and established states. If this problem persists, replace the endpoint.

Error Type 2562 - 2566: the ASAI message is not transmitted because the transmit buffer for the ASAI link is full, causing the link to be flow-controlled. Frequent or persistent occurrence of these events may indicate a hardware problem or traffic overload on the signaling link or the ASAI adjunct. Follow the repair procedures issued by the manufacturer of the adjunct. If these attempts fail, re-engineering of the traffic on the signaling link or adjunct may be necessary.

Error Type 2567: This version of ASAI is not supported. Check the software version that is running on the ASAI adjunct.

Error Type 2568: The adjunct identification is invalid. Check the vendor ID or software running on the ASAI adjunct.

Error Type 3329: the point-to-point signaling link to the endpoint went down, except when the link goes down because either a system technician has busied out the PKT-BUS, or it has failed. This error raises an alarm against the endpoint or adjunct. Execute test station extension short and note the results of the Signaling Link Status Test (#626). If this test fails, follow the repair procedure for Signaling Link Status Test 626. The alarm is retired when the signaling link is re-established to the endpoint or adjunct.

The table contains a description of the various ASAI cause values and recommended system technician actions associated with the cause value.