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: Violations of the ISDN-BRI signaling protocol. Timers associated with certain layer-3 messages have expired before a required response was received. In the following table, the aux data field indicates what timer has just expired.

The switch sent a message to the endpoint that did not respond in the allotted time. This can happen occasionally due to failure of the point-to-point signaling link or because of a problem in the BRI endpoint or ASAI adjunct or Avaya adjunct. Execute test station extension sh and note the results of the BRI Layer 3 Query test (#629). If this test fails, follow the repair procedure for BRI Layer 3 Query Test 629.

Error type 130: The media module has been removed or has been insane for more than 11 minutes. To clear the error, replace or reinsert the media module.

Error type 257: The endpoint does not respond to the service state query message sent to the adjunct or 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 the adjunct.

For BRI endpoints, the Aux Data field for this error contains “0.” When it occurs, execute test station extension sh and note the results of the BRI Layer 3 Query test (#629). If this test fails, follow the repair procedure for BRI Layer 3 Query Test 629.

When this error occurs for an ASAI or Avaya adjunct, the Aux Data field indicates the state of the ASAI link or Avaya 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 Serversfor an explanation of the ASAI link states.

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

When this error occurs for an ASAI or Avaya adjunct:

1. Execute test station extension and note tests that fail. Perform the associated repair procedures for those tests.
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.
3. If the above steps do not resolve the problem and the alarm persists, follow normal escalation procedures.

Error type 351 and associated WARNING alarm are logged against an ASAI or Avaya endpoint when the adjunct has asked the switch to suspend Maintenance on the ASAI or Avaya endpoint. Busy out and release the ASAI station or ADJLK station to clear the alarm.

Error Type 513: The endpoint sends more messages than the switch can 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: A BRI endpoint’s signaling-associated link has too much traffic related to link establishment. This could occur if the signaling link is bouncing between assigned and established states. Software suspends activity to this endpoint for 75 minutes when the endpoint is alarmed due to this problem. Note that service suspension does not occur if the endpoint is an ASAI or Avaya adjunct. If this problem persists, replace the endpoint. If replacing the endpoint does not fix the problem, follow normal escalation procedures.

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 or Avaya adjunct. Attempt to resolve the problem by following the repair procedures issued by the manufacturer of the adjunct. If these attempts fail, the problem should be escalated because re-engineering of the traffic on the signaling link, or adjunct may be necessary.

Error 2567: The version of ASAI is not supported, check version of the software running on the ASAI or Avaya adjunct.

Error type 2568: The adjunct ID is invalid, check the vender ID or software running on the Avaya adjunct

Error type 2817: There is a layer-2 problem over the D-Channel between the switch and the endpoint. When this error occurs, an alarm is raised against the station or adjunct. Execute test station extension short and note the results of the BRI XID test (#628). If this test fails, follow the repair procedure for BRI XID Test 628.

Error type 3073: There is a problem with the B-Channel connection between the switch and the endpoint. When this error occurs, a warning alarm is raised against the endpoint. Execute test station extension long and note the results of the BRI Remote Loopback Test (#627). If this test fails, follow the repair procedure for BRI Remote Loopback Test 627.

Error type 3329: Occurs whenever the point-to-point signaling link to the endpoint goes down except when it goes down because either the PKT-BUS has failed or has been busied out by system technician. When this error occurs, an alarm is raised 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 reestablished to the endpoint or adjunct.

Error type 3584-3839: Certain ASAI protocol-specific cause codes are logged by switch software. The cause code can be determined from the following formula:

If the Error Type is greater than 3712, then the ASAI cause code is equal to the Error Type minus 3712. This code was sent to the adjunct by the switch.

If the Error Type is less than 3712, then the ASAI cause code is equal to the Error Type minus 3584. This code was sent to the switch by the adjunct.

A description of the various ASAI cause values is contained in the table. This table also contains recommended actions associated with the cause value. In addition, the Aux Data field of the Error Log entry contains additional diagnostic information additional diagnostic.

Error type 3840-4095: Certain ISDN-BRI cause codes are logged by switch software. The cause code can be determined from the following formula:

If the Error Type is greater than 3968, then the ISDN-BRI cause code is equal to the Error Type minus 3968. This code was sent to the endpoint by the switch.

If the Error Type is less than 3968, then the ISDN-BRI cause code is equal to the Error Type minus 3840. This code was sent to the switch by the endpoint.

A description of the various ISDN-BRI cause values is contained in the table. This table also contains recommended actions associated with the cause value. In addition, the Aux Data field of the Error Log entry contains additional diagnostic information.

Error 3847: Sets on the port do not support level 3 initialization. Consult the set service documentation.