Cause value 88

Last Updated : Oct 15, 2014 |
[0x58/0xD8]

Incompatible destination

Cause

The call cannot be completed because the call request in the SETUP message has low layer compatibility, high layer compatibility, or other compatibility attributes, for example, data rate, DN, or sub-address information, which the remote endpoint or network cannot accommodate.

This cause value has end-to-end significance and must always be passed back through the network to the user.

Proposed Solution

Procedure

  1. Check Communication Manager administration for the cause value generated by the network.
    1. Route pattern: An incorrect ITC or BCIE specified, these fields affect how the bearer capability is encoded in the SETUP message.
    2. The ITC administered on the originating endpoint is incorrect for this call, or the speed options for calls over these ISDN facilities in the device itself are incorrect or both.
    3. Incorrect data speed option set in the BRI device causes a call from a BRI endpoint sequencing through Communication Manager to create a SETUP message with the wrong bearer capability.
    4. A call sequencing through Communication Manager ISDN trunk group to ISDN trunk group has a bearer capability that is not supported by the outgoing ISDN facilities or network.
    5. A call sequencing through Communication Manager on a non-ISDN trunk group transferring to an ISDN trunk group has an incorrect bearer capability assigned to the incoming trunk group. The BC and ITC fields on the incoming trunk group are administered incorrectly.
  2. Communication Manager administration that can affect sending this cause value:
    1. The extension number received in the incoming SETUP message for a data call is incorrectly assigned to an analog extension.
    2. The extension number received in the incoming SETUP message for a voice call is incorrectly assigned to a data extension.
    3. The outgoing route pattern for a data call sequencing through Communication Manager to ISDN trunk group does not have the bearer capability activated.
    4. The outgoing route pattern for Temporary Signaling Connection (TSC) setup attempt sequencing through Communication Manager does not have the TSC bearer capability activated.