09.12.2012 Views

Server Alarms - Avaya Support

Server Alarms - Avaya Support

Server Alarms - Avaya Support

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Cause Value 50<br />

Event Data<br />

[0x32/0xB2] -<br />

Requested facility not subscribed<br />

The call could not be completed because the user has not subscribed to the service, feature, or<br />

supplementary service requested in the SETUP message. If the user is supposed to have<br />

access to this service, feature, or supplementary service, then complete the required ordering<br />

process with the ISDN service provider.<br />

This Cause Value has end-to-end significance and should always be passed back through the<br />

network to the user.<br />

Communication Manager does not originate this Cause Value for PRI. A BRI or Adjunct Switch<br />

Application Interface (ASAI) application might generate this Cause Value.<br />

Communication Manager translations that can affect receiving this Cause Value from the<br />

network are:<br />

Cause Value 51<br />

● Route Pattern: service or feature: An incorrect service or feature is specified for the call<br />

being made on this CBC trunk group preference. An incorrect ITC and/or BCIE is<br />

specified. These fields affect how the bearer capability is encoded in the SETUP message.<br />

● The ITC administered on the originating endpoint might be incorrect for this call.<br />

- Incorrect data speed option is set in the BRI device, causing a call from a BRI endpoint<br />

tandeming through Communication Manager to create a SETUP message with the<br />

wrong bearer capability.<br />

● On tandem calls through Communication Manager from ISDN trunks to ISDN trunks, an<br />

inappropriate NSF can be tandemed from one D-channel to the other D-channel.<br />

● The problem is that the outgoing trunk group is CBC but no service or feature was<br />

specified on the outgoing route pattern to overwrite the incoming NSF. Add the correct<br />

service or feature to the route pattern or make the outgoing trunk group a static trunk<br />

group (for example, public-network or tie) as appropriate.<br />

● System Parameters Features: The US NI send Calling Name ID field is y. Communication<br />

Manager sends the Bellcore calling name ID but the customer has not subscribed to that<br />

service. Set the US NI send Calling Name ID field to n.<br />

[0x33/0xB3] -<br />

Bearer capability incompatible with service request (NI-1: National ISDN 1)<br />

The requested action could not be completed. The requested action is incompatible with the<br />

bearer capability of the call (for example, trying to place a data call on hold).<br />

Communication Manager Release 5.0 Issue 4 January 2008 175

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!