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:

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.

Error Type 3584 - 3839: The switch software logs certain ASAI cause values. The cause value is determined from the following formulas:

• If the Error Type is greater than 3712, the ASAI cause value is equal to the Error Type minus 3712. The switch sent this value to the adjunct.
• If the Error Type is less than 3712, the ASAI cause value is equal to the Error Type minus 3584. The adjunct sent this value to the switch.

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

Error Type 3841 - 4095: The switch software logs certain ASAI cause values. The cause value is determined from the following formula:

• If the Error Type is greater than 3968, the ASAI cause value is equal to the Error Type minus 3968. The switch sent this value to the endpoint.
• If the Error Type is less than 3968, the ASAI cause code is equal to the Error Type minus 3840. The endpoint sent this value to the switch.

  ASAI cause values

  Code	Explanation	Recommendation
  0	Unrecognized ASAI Protocol Operation.	Requested ASAI protocol is not implemented by switch or adjunct. Aux Datafield of error log entry contains protocol identifier for unrecognized operation. Consult switch and adjunct documentation to determine which set of operations is supported by switch and the adjunct. Turning off adjunct operations not implemented by the switch may resolve the problem.
  34	No circuit or channel available	A resource on the switch is unavailable for a call. For BRI endpoints, this cause value is not logged. For ASAI, this condition means that there are no available trunks for an outgoing call request. Verify that the adjunct is administered to support the trunk capabilities of the switch. Investigate trunk-group status by entering status trunk from the SAT or by requesting trunk-group queries from the adjunct. Perform trunk diagnostic procedures such as test trunk.
  40	Resources not available.	No available internal resources to service switch or adjunct request. Exceeds system transaction capacity for adjunct or switch. May require re-engineering of adjunct services.
  50	Requested facility not subscribed	Requested facility is implemented, but not administered. Potential administration problem with endpoint or adjunct. For BRI endpoints: Verify the switch administration of endpoint using display station or display data-module. If step 1 does not resolve the problem, refer to the endpoint’s service manual and verify administration on the endpoint. For ASAI adjuncts: Display the Customer Optional Features screen (administration screen) on the switch to determine which ASAI capabilities are turned on in the switch. Verify that the adjunct is administered to support the identical capabilities as the switch. If there is a mismatch in the administered capabilities, then re-administer the switch and/or the adjunct to establish a consistent set of desired capabilities on both the switch and the adjunct.
  58	Bearer capability not currently available	Requested bearer capability is implemented, but not administered. No B-Channel is administered. See code 50 above.
  63	Service or option not available	Requested ASAI capability or resource is not available on the switch or adjunct. More than one adjunct may be contending for the same switch resource. Potential administration mismatch between the resource domains administered on the switch and those administered on the adjunct. Verify that no overlapping administration of switch resources (for example, requesting notifications on a single domain by multiple adjuncts attempting to control a single call) exists across any adjunct connected to the switch. If an overlap exists, then re-administer the adjuncts to ensure that each adjunct is associated with a unique set of switch resources.
  65	Bearer service not implemented	Requested service not implemented in switch or endpoint.
  69	Requested facility not implemented	Requested service not supported in switch or endpoint. Consult switch and endpoint documentation to determine service support.
  79	Service or option not implemented	Requested service or option (or combination of selected options) is not supported (implemented) in switch or the adjunct. Consult switch and adjunct documentation to determine ASAI service and options supported by both switch and adjunct. Re-administration of the switch-administered capabilities (see Customer Optional Feature screen) or those of the adjunct may be necessary to correct the problem.
  81	Invalid CRV	An invalid CRV was sent by the adjunct. This may indicate a CRV inconsistency between the switch and the adjunct. See the CallVisor protocol reference manual.
  87	Internal switch audit	There is an inconsistency in switch data records. There is no action needed, since the switch has corrected the data inconsistency.