Avaya 03-300430 User Manual
Denial Events
152 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Cause Value 50
[0x32/0xB2] -
Requested facility not subscribed
The call could not be completed because the user has not subscribed to the service, feature, or
supplementary service requested in the SETUP message. If the user is supposed to have
access to this service, feature, or supplementary service, then complete the required ordering
process with the ISDN service provider.
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.
Communication Manager translations that can affect receiving this Cause Value from the
network are:
Requested facility not subscribed
The call could not be completed because the user has not subscribed to the service, feature, or
supplementary service requested in the SETUP message. If the user is supposed to have
access to this service, feature, or supplementary service, then complete the required ordering
process with the ISDN service provider.
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.
Communication Manager translations that can affect receiving this Cause Value from the
network are:
●
Route Pattern: service or feature: An incorrect service or feature is specified for the call
being made on this CBC trunk group preference. An incorrect ITC and/or BCIE is
specified. These fields affect how the bearer capability is encoded in the SETUP message.
being made on this CBC trunk group preference. An incorrect ITC and/or BCIE is
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.
- 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.
wrong bearer capability.
●
On tandem calls through Communication Manager from ISDN trunks to ISDN trunks, an
inappropriate NSF can be tandemed from one D-channel to the other D-channel.
inappropriate NSF can be tandemed from one D-channel to the other D-channel.
●
The problem is that the outgoing trunk group is CBC but no service or feature was
specified on the outgoing route pattern to overwrite the incoming NSF. Add the correct
service or feature to the route pattern or make the outgoing trunk group a static trunk
group (for example, public-network or tie) as appropriate.
specified on the outgoing route pattern to overwrite the incoming NSF. Add the correct
service or feature to the route pattern or make the outgoing trunk group a static trunk
group (for example, public-network or tie) as appropriate.
●
System Parameters Features: The US NI send Calling Name ID field is y. Communication
Manager sends the Bellcore calling name ID but the customer has not subscribed to that
service. Set the US NI send Calling Name ID field to n.
Manager sends the Bellcore calling name ID but the customer has not subscribed to that
service. Set the US NI send Calling Name ID field to n.
Cause Value 51
[0x33/0xB3] -
Bearer capability incompatible with service request (NI-1: National ISDN 1)
The requested action could not be completed. The requested action is incompatible with the
bearer capability of the call (for example, trying to place a data call on hold).
Bearer capability incompatible with service request (NI-1: National ISDN 1)
The requested action could not be completed. The requested action is incompatible with the
bearer capability of the call (for example, trying to place a data call on hold).