1. Major and Minor alarms for this MO may be downgraded to Warning alarms based on the value used with set options.

Notes:

1. 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.

2. 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.

   Aux Data	Timer Type
   2	First T303 (SETUP timer)
   3	Second T303 (SETUP timer)
   4	T305 (DISConnect timer)
   5	First T308 (RELease timer)
   6	Second T308 (RELease timer)
   10	T316 (RESTart timer)
   12	T309 (Layer-2 Failure timer)
   16	TM100 (Management Information message Timer 1)
   17	TM200 (Management Information message Timer 2)
   102	TASAI (ASAI Routing timer)

   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.

3. 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.

4. 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:

   Aux Data	ASAI Link State	Error
   102	13-restarting	No response to RESTART message
   104	13-restarting	Invalid response to RESTART message
   152	13-restarted	No response to layer-3 query
   154	13-restarted	Invalid response to layer-3 query
   202	13-established	No response to layer-3 query
   204	13-established	Invalid response to layer-3 query

   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.

5. 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.

6. 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.

7. 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.

8. 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.

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

   Table 2: ISDN-BRI CAUSE VALUES; (BRI-SET/ASAI-ADJ Error Log Notes)

   Error Code	Test Result	Description / Recommendation
   1	Channel in use	Another station is using requested channel on the BRI-PORT. Not applicable for ASAI or Avaya adjuncts. For BRI endpoints: Try to originate a call to or from this port. If the error persists, busyout and release the port. If the problem still persists, replace stations on the port. If the problem still persists, escalate to the next tier.
   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 or Avaya Adjuncts: 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 commands from the SAT or by requesting a trunk group query or queries from the adjunct. Perform trunk diagnostic procedures such as test trunk. If step 3 does not resolve the problem, escalate to the next tier.
   42	Switch Equipment Congestion	Switch takes control to limit received traffic. For BRI endpoints: This cause value is not logged. For ASAI or Avaya Adjuncts: Refer to the CallVisor protocol reference manual. If step 1 does not resolve the problem, escalate to the next tier.
   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. If step 2 does not resolve the problem, escalate to the next tier. For ASAI adjuncts: Display the Customer Optional Features screen also known as 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. If step 2 does not resolve the problem, escalate to the next tier. For Avaya adjuncts: Display the Customer Optional Features screen also known as administration screen on the switch to determine whether the Avaya adjunct is set enabled on in the switch. If Error Type 2567 or 2568, verify the Avaya adjunct version, and re-administer if needed. If step 2 does not fix the problem, escalate to the next tier of support
   58	Bearer Capability Not Currently Available	Requested bearer capability is implemented, but not administered. No B-Channel is administered. See recommendation for Error Code 50 above.
   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. If step 1 does not resolve the problem, escalate to the next tier.
   81	Invalid CRV	An invalid CRV was sent by the adjunct. This may indicate a CRV inconsistency between the switch and the adjunct. Refer to the CallVisor protocol reference manual. If step 1 does not resolve the problem, escalate to the next tier.

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

11. 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.

12. 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.

13. 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.

14. 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.

    Table 3: ASAI CAUSE VALUES; (BRI-SET/ASAI-ADJ Error Log Entries Notes)

    Error Code	Test Result	Description / Recommendation
    0	Unrecognized ASAI Protocol Operation	Requested ASAI protocol operation is not implemented by the switch or adjunct. Aux Data field of Error Log entry contains protocol identifier for unrecognized operation. Consult switch and adjunct documentation to determine which set of operations is supported by the switch and the adjunct. Adjunct administration turning off operations not implemented by the switch may resolve the problem. If step 1 does not resolve the problem, escalate to the next tier.
    40	Resources not available	No available internal resources to service switch or adjunct request. System transaction capacity for adjunct or switch is exceeded. Re-engineering of adjunct services my be required. If problem persists, escalate problem to the next tier.
    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 resources. 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 exists across any adjunct connected to the switch. For example, requesting notifications on a single domain by multiple adjuncts or multiple adjuncts attempting to control a single call. If an overlap exists, then re-administer the adjuncts to guarantee that each adjunct is associated with a unique set of switch resources. If step 1 does not resolve the problem, escalate to the next tier.
    79	SERVICE OROPTION NOT IMPLEMENTED	Requested service or option or combination of selected options is not supported or 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, for more information see Customer Optional Feature screen or those of the adjunct may be necessary to correct the problem. If step 1 does not provide the set of desired services due to deficient implementation, escalate the problem to the next tier.
    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. If a number of these errors continue to occur, then escalate to next tier.

15. 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.

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