Cause value 02

Last Updated : Oct 14, 2014 |
[0x2/0x82]

No route to specified transit network/ Calling party off hold (5ESS: 5 Electronic Switching System)

Cause

The ISDN service provider’s equipment cannot route the call through the specified network. The network either does not exist or is incompatible with the equipment of the ISDN service provider.

This cause value has local significance only. The ISDN network between the user and the equipment generating the cause value sends:

  • A no cause indication through the network

  • A more generic cause value through the network

Since this cause value has only local significance on tandem calls, Communication Manager maps it to Cause value 31 instead of passing it back through the network.

Proposed Solution

Procedure

  1. Check the diagnostic information (DIAG) for the transit network identity of the unreachable network. See Event data 2.
  2. Check if any prefix or service value is missing from the cause value numbers.
  3. Check that the call type (data, voice, fax) can be routed between the ISDN networks serving both ends of the call.
  4. Check that the bearer capabilities of the call are acceptable to the ISDN network serving both ends of the call.
  5. Check Cause Value Information Element (LOC). See Location codes.
  6. Check Communication Manager administration.
    1. AAR/ARS digit analysis: Call type is incorrect for the call made with an incorrect number type or incorrect number plan information or both, or the call type prevents code conversion. Call routes to an incorrect route pattern with incorrect digit manipulation and/or code conversion.
    2. Route pattern: Incorrect digits or IXC were inserted. Incorrect number of digits were deleted. An incorrect ITC or BCIE or both has affected the encoding of the SETUP message bearer capability. An incorrect service or feature specified for the preference. The number format specified is incorrect for the call type.
    3. The ITC administered on the originating endpoint is incorrect for this call.
    4. Incorrect data speed option set in the BRI device causes a call from a BRI endpoint to sequence through Communication Manager creating a SETUP message with the wrong bearer capability.