ISDN Denial Event 1211 - Incompatible destination

[Nick44]

Hi,
This is an ACM 4 using 96xx handsets and PRI trunks.
Customer cannot dial certain destinations , may be co-incidence but all have same prefix.
I have separated out these numbers in the ARS table and toll table and sent them via a separate route patern for testing purposes.
I have set up a remote access node to the ACM for test purposes.
By dialling into the PBX and breaking out (effectively a trunk-to-trunk call) the call connects fine. But still the local extensions [both 96xx and 64xx handsets) get the denial event message.

LIST TRACE

time data

12:11:10 dial 901697473476 route:ARS
12:11:10 term trunk-group 2 cid 0x305e
12:11:10 dial 901697473476 route:ARS
12:11:10 route-pattern 10 preference 1 cid 0x305e
12:11:10 seize trunk-group 2 member 5 cid 0x305e
12:11:10 Calling Number & Name NO-CPNumber Iain Tuffill
12:11:10 Proceed trunk-group 2 member 5 cid 0x305e
12:11:13 denial event 1211: Incompatible dest D1=0x8bdc D2=0xf58
12:11:13 idle trunk-group 2 member 5 cid 0x305e
12:11:19 idle station 373 cid 0x305e

Any Ideas?
Thank.


Speak softly and carry a big switch

 

[mikeydidit]

Cause Value 88
[0x58/0xD8] -
Incompatible destination
The call could not 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 should always be passed back through the
network to the user.
Troubleshooting
? Check Communication Manager administration (network generated the Cause Value).
- Route pattern: An incorrect ITC and/or BCIE 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, and/or
the speed options in the device itself might be incorrect for calls over these ISDN
facilities.
- 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.
- A call tandeming through Communication Manager ISDN trunk group to ISDN trunk
group might have a bearer capability that is not supported by the outgoing ISDN facilities
or network.
- A call tandeming through Communication Manager on a non-ISDN trunk group
inter-working to an ISDN trunk group might have an incorrect bearer capability assigned
on the incoming trunk group. The BC and ITC fields on the incoming trunk group might
be set wrong.
? Communication Manager administration that can affect sending this Cause Value:
- The extension number assigned in Communication Manager that was received in the
incoming SETUP message for this data call is assigned to an analog extension.
- The extension number assigned in Communication Manager that was received in the
incoming SETUP message for this voice call is assigned to a data extension.
Denial Events
172 Maintenance Alarms for Avaya Communication Manager 3.1, Media Gateways and Servers
- 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.

Here is the book version for you. Someone may come along that has had this same problem and post more for you. But this gives you someplace to start.

When is the last time you helped someone, just because you were able to?

For the best response to a question, read faq690-6594

 

[Nick44]

Thanks for the reply, I have that document already. My problem is almost the reverse of Call Tandem CM ISDN example.
A Call Tandem works, but a direct extension/trunk does not.


Speak softly and carry a big switch

 

[Nick44]

Update.
Fix has been found.
DS1 capabilty was set to 3.1k. Changed this to speech and call proceeded OK.
This is highlighting a configuration error at the remote end.

Speak softly and carry a big switch