Server Alarms - Avaya Support

Cause Value 89
Event Data
- A data call attempt tandeming through Communication Manager ISDN trunk group to
ISDN trunk group the outgoing route pattern has the Bearer Capability Class (BCC)
required for making this call set to “NO” and/or the ITC and BCIE are not compatible with
the incoming bearer capability.
- A Temporary Signaling Connection (TSC) setup attempt that is tandeming through
Communication Manager, the outgoing route pattern does not have the TSC bearer
capability activated.
[0x59/0xD9] -
Network Congestion (1TR6: AT&T ISDN Protocol)
The call could not be completed because the switching equipment generating this Cause Value
is experiencing a period of high traffic.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Troubleshooting
Wait and try the call again later.
Cause Value 90
[0x5A/0xDA] -
Non-existent closed user group (CUG)/
Remote user initiated clearing (1TR6: AT&T ISDN Protocol)
The packet mode call was rejected because the equipment that sent the Cause Value did not
recognize the requested Closed User Group (CUG), which is a feature associated with packet
mode calls similar to X.25 connection made over the ISDN D-channel.
Communication Manager does not support packet mode sessions on D-channels, therefore this
is not applicable to Communication Manager.
Cause Value 91
[0x5B/0xDB] -
Invalid transit network selection
The call could not be completed because the equipment that sent this Cause Value received a
request to route a call to a transit network that it does not have a connection to, or the transit
network identification that was received is of an incorrect format as defined in Annex C of the
ITU Q.931 specification for either the TNS IE or the NSF IE.
Communication Manager does not originate Cause Value 91.
Communication Manager Release 5.0 Issue 4 January 2008 187