Server Alarms - Avaya Support

Cause Value 56
Event Data
[0x38/0xB8] -
Number changed (1TR6: AT&T ISDN Protocol)
The called party number indicated has been changed to a new number that might be sent in the
diagnostic information (DIAG) for this Cause Value. See Cause Values and their meanings/
interpretations on page 151. If this Cause Value is not supported by the ISDN network, Cause
Value 01 is used instead.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Communication Manager does not originate this Cause Value for PRI. A BRI or Adjunct Switch
Application Interface (ASAI) application might generate this Cause Value.
Cause Value 57
[0x39/0xB9] -
Bearer capability not authorized/
Out of order (1TR6: AT&T ISDN Protocol)
Cause Value 57 indicates that the call could not be completed because the user has requested
a bearer capability in the SETUP message which is implemented by the equipment generating
this Cause Value, but user has not subscribed to it or in other ways is not authorized to use.
Cause Value 57 (1TR6) indicates that the call cannot be delivered to the remote endpoint
because the interface to the endpoint is not functioning correctly. A signaling message could not
be delivered to the remote device (for example, due to a physical or data link layer failure at the
remote device, or the remote device is turned off).
Troubleshooting
● Check the diagnostic information (DIAG) for the unauthorized bearer capability attributes.
See Cause Values and their meanings/interpretations on page 151.
● Check Communication Manager administration (network generated the Cause Value).
- Route pattern: An incorrect ITC and/or BCIE specified, these fields affect how the bearer
capability is encoded in the SETUP message.
- The ITC administered on the originating endpoint might be incorrect for this call, and/or
the speed options in the device itself might be incorrect for calls over these ISDN
facilities.
- Incorrect data speed option is set in the BRI device, causing a call from a BRI endpoint
tandeming through Communication Manager to create a SETUP message with the
wrong bearer capability.
- A call tandeming through Communication Manager ISDN trunk group to ISDN trunk
group might have a bearer capability that is not supported by the outgoing ISDN facilities
or network.
Communication Manager Release 5.0 Issue 4 January 2008 177