ISDN error message

sebastiandm · ‎07-06-2009

Hi Guys,

I am experiencing an issue with incoming calls on certain numbers within a range of ddi`s. The debug isdn q931 is returning the following:

Jul 6 11:39:59.743 UTC: ISDN Se0/0/0:23 Q931: RX <- SETUP pd = 8 callref = 0x0050

Bearer Capability i = 0x9090A2

Standard = CCITT

Transfer Capability = 3.1kHz Audio

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA193040000

Preferred, Channel 4

Progress Ind i = 0x8581 - Call not end-to-end ISDN, may have in-band info

Calling Party Number i = 0x0083, '4421836482930'

Plan:Unknown, Type:Unknown

Called Party Number i = 0x80, '1234567'

Plan:Unknown, Type:Unknown

Jul 6 11:39:59.763 UTC: ISDN Se0/0/0:23 Q931: TX -> CALL_PROC pd = 8 callref = 0x8050

Channel ID i = 0xA993040000

Exclusive, Channel 4

TK-VCE-RT01#

Jul 6 11:39:59.983 UTC: ISDN Se0/0/0:23 **ERROR**: Ux_BadMsg: Invalid Message for call state 9, call id 0x1BED, call ref 0x8050, event 0x89

Jul 6 11:39:59.983 UTC: ISDN **ERROR**: Module-l3_sdl_u Function-Ux_BadMsg Error-Source ID = 400 Event = 89

TK-VCE-RT01#

Jul 6 11:40:09.856 UTC: ISDN Se0/0/0:23 **ERROR**: Ux_BadMsg: Invalid Message for call state 9, call id 0x1BED, call ref 0x8050, event 0x89

Jul 6 11:40:09.856 UTC: ISDN **ERROR**: Module-l3_sdl_u Function-Ux_BadMsg Error-Source ID = 400 Event = 89

Jul 6 11:40:09.992 UTC: ISDN Se0/0/0:23 Q931: RX <- DISCONNECT pd = 8 callref = 0x0050

Cause i = 0x82E6333130 - Recovery on timer expiry

Jul 6 11:40:09.996 UTC: ISDN Se0/0/0:23 Q931: TX -> RELEASE pd = 8 callref = 0x8050

Jul 6 11:40:10.044 UTC: ISDN Se0/0/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x0050

I have tried adjusting the ISDN timer but this has not made any difference. Does anyone know why this would affect only certain numbers in a range and what can be done to fix this, thanks.

paolo bevilacqua · ‎07-06-2009

Exact IOS used ?

sebastiandm · ‎07-06-2009

Hi,

c2800nm-spservicesk9-mz.124-20.T.bin

paolo bevilacqua · ‎07-06-2009

Can you use a mainline like 12.4(3j) - much less buggier.

Also check what is going on with these DIDs what the final destination is doing.

sebastiandm · ‎07-06-2009

Hi Bevil,

Unless i can definately prove it is an IOS issue it would be a bit difficult to change the IOS.

When the call comes in i have a translation rule which is translating this number into 0201010 which is a mobile voice access number.

I then have a pots dial peer and a voip dial peer to match this newly translated number but it is not even hitting my pots dial peer, config is as follows :

dial-peer voice 0201010 pots

description Mobile Voice Access

service ccm

incoming called-number 0201010

no digit-strip

dial-peer voice 124 voip

description Mobile Voice Access Calls

preference 1

destination-pattern 0201010

progress_ind setup enable 3

session target ipv4:10.10.10.10

dtmf-relay h245-alphanumeric

no vad

When dialling this number in particular i get a message from the carrier something about the call not being completed its in Tokyo.

If i ring another number in the same range it goes through perfectly fine.

paolo bevilacqua · ‎07-06-2009

I don't have to prove anything, the abnormality is evident.

Either "service ccm" does something wrong, or router becomes confused so telco disconnects.

sebastiandm · ‎07-06-2009

Hi,

Sorry i think you misunderstood what i was saying. I am not asking you to prove something i just mean my client would want me to be sure it is the IOS before letting me change it. I do agree with you tho so sorry if it sounded wrong.

I will try remove the config altogether and start again in case something has been missed.

Thanks for taking a look i appreciate it.

andres.pasten · ‎09-04-2009

This message resolved my problem!!

I've been trying to resolve the same error for more than 5 days, and it's not a problem of configuration, only IOS.

The 12.4T IOS drops the call because of facility information that comes from the PBX, but the mainline IOS doesn't.

Thanks!!

Andres Pasten

Adexus S.A.