Demand test descriptions and error codes - Avaya Support

ATM-BCH (ATM B-Chel Trunk)
● Outgoing call renegotiated by the far end to another B-Chel in the absence of SETUP
message glare
● Near end attempted a call on a B-Chel that the far end has marked OOS
When running the short test sequence, note the results of the Call State Audit Test (#257).
c. Error Type 129: the far-end switch changed its ISDN service state to either out-of-service
or maintenance. This may be a temporary condition because the far end is testing that trunk
or a hardware problem with the trunk. Outgoing calls may not be allowed over that trunk.
1. Investigate the trunk’s status (status trunk grp#/mem#).
d. Error Type 130: the circuit pack has been removed or has been insane for more than 11
minutes. Reinsert or replace the circuit pack to clear the error.
e. Error Type 257: SETUP received for a B-Chel that is in an invalid service state. Service
states may be incompatible at the two ends of the trunk. A normal call was received while
the B-Chel was MTC/FE, MTC/NE, OOS/FE, or OOS/NE or a test call was received while
the B chel was OOS/FE or OOS/NE.
f. Error Type 513: RELease COMplete message received with cause value 82 (nonexistent
chel). The B-Chel may not be administered at the far end. The trunk has been placed in the
OOS/FE state.
g. Error Type 769: inconsistent SERVice or SERVice ACKnowledge message. Possible
causes:
● SERVice or SERVice ACKnowledge message received containing a change status
that is more available than the previously-transmitted SERVice message.
● Unsolicited SERVice ACKnowledge message received containing a change status that
does not match the current B-Chel state.
ISDN-PRI service-state negotiation rules have been violated and may indicate that a
pending service-state audit is failing. The system:
● cancels the maintenance timer
● increments the Service State Audit counter
● attempts a Service State Audit
When running the short test sequence, note the results of the Service State Audit Test
(#256).
h. Error Type 1793: TN230x circuit pack failed. The maintenance system
● places the trunk in the OOS/NE state
● sends a SERvice message to the far end (if possible) containing a change status of
OOS for the B-Chel
● returns the trunk to service when the ATM trunk circuit pack reports the failure cleared
i. Error Type 3073: Service State Audit attempt failed. See Service State Audit Test (#256).
Calls can be received but not placed until the test passes and the trunk state returns to
In-Service. Check the trunk’s status with status trunk grp#/mem#.
Issue 5 May 2009 119