Demand test descriptions and error codes - Avaya Support

BRI-SET, Various Adjuncts
3. If the above steps do not resolve the problem and the alarm persists, follow normal
escalation procedures.
e. 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.
f. 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.
g. 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.
h. 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.
i. Error 2567: the version of ASAI is not supported, check version of the software running on
the ASAI or Avaya adjunct.
Table 60: ISDN-BRI CAUSE VALUES; (BRI-SET/ASAI-ADJ Error Log Notes) 1 of 4
Error
Code
Test Result Description / Recommendation
1 Chel in use Another station is using requested chel on the BRI-PORT. (Not
applicable for ASAI or Avaya adjuncts.)
For BRI endpoints:
1. Try to originate a call to or from this port.
2. If the error persists, busyout and release the port.
3. If the problem still persists, replace stations on the port.
4. If the problem still persists, escalate to the next tier.
1 of 4
Issue 5 May 2009 227