Please help **ERROR**: Ux_BadMsg: Invalid Message for call state 4

[shinyoooo]

Hi all of IPT professionals in this community,

I have a problem getting a call setup to a specific number using H.323 GW. (4431 IOS-XE 3.14)

Please find below for the captured debug of this failed call.

Every other calls are working without any problem except for this number.

I see there is a NOTIFY message coming back from the called party trying to notify this call is being forwarded or something.

Right after that message, I am getting the **ERROR** and can't process the call any further.

According to telco, called party is using Avaya as their PBX.

Any other successful calls would have ALERTING message coming back instead of NOTIFY and call gets established smoothly.

I have pasted key voip configuration below as well.

It is appreciated if you can shed a light on this issue.

Thanks for your time.

Bearer Capability i = 0x8090A3
                                Standard = CCITT
                                Transfer Capability = Speech 
                                Transfer Mode = Circuit
                                Transfer Rate = 64 kbit/s
                Channel ID i = 0xA9839B
                                Exclusive, Channel 27
                Calling Party Number i = 0x2181, '2218XXXXX'
                                Plan:ISDN, Type:National
                Called Party Number i = 0x81, '0355XXXXX'
                                Plan:ISDN, Type:Unknown
Sep  1 10:34:37.794: ISDN Se0/1/0:15 Q931: RX <- CALL_PROC pd = 8  callref = 0xD660
                Channel ID i = 0xA9839B
                                Exclusive, Channel 27
Sep  1 10:34:38.518: ISDN Se0/1/0:15 Q931: RX <- PROGRESS pd = 8  callref = 0xD660
                Progress Ind i = 0x8282 - Destination address is non-ISDN
Sep  1 10:34:38.540: ISDN Se0/1/0:15 Q931: RX <- NOTIFY pd = 8  callref = 0xD660
                Notification Ind i = 0xFB
                Display i = 'Call is forwarded'
Sep  1 10:34:38.540: ISDN Se0/1/0:15 **ERROR**: Ux_BadMsg: Invalid Message for call state 4, call id 0xD5E1, call ref 0x5660, event 0x6E
Sep  1 10:34:38.540: ISDN Se0/1/0:15 Q931: TX -> STATUS pd = 8  callref = 0x5660
                Cause i = 0x80E26E - Message not compatible with call state or not implemented
                Call State i = 0x04
Sep  1 10:34:38.572: ISDN Se0/1/0:15 Q931: RX <- DISCONNECT pd = 8  callref = 0xD660
                Cause i = 0x82E57D - Message not compatible with call state

!GW Config

voice service voip
 allow-connections h323 to h323
 allow-connections h323 to sip
 allow-connections sip to h323
 allow-connections sip to sip
 fax protocol pass-through g711ulaw
 modem passthrough nse codec g711ulaw
 sip
  bind control source-interface Loopback0
  bind media source-interface Loopback0
  registrar server
!
voice class codec 1
 codec preference 1 g722-64
 codec preference 2 g711ulaw
 codec preference 3 g711alaw
 codec preference 4 g729r8
!
voice class h323 1
  h225 timeout tcp establish 3
  call preserve limit-media-detection
!
dial-peer voice 1001 voip
 destination-pattern 88....
 session target ipv4:
 voice-class codec 1 
 voice-class h323 1
 dtmf-relay h245-signal
 ip qos dscp cs3 signaling
 no vad
!
dial-peer voice 11 pots
 description Outbound PSTN calls
 destination-pattern 0.T
 incoming called-number .
 direct-inward-dial
 port 0/1/0:15
!

[Wilson Samuel]

Just so that you know, Telcos can create amazing and mesmerizing kinds of issues and still shrug and say, everything was always fine at your end.

However upon bit of dissection of the err message, the following is that comes to highlight:

E2

Message not compatible with call state or not implemented

The remote equipment receives an invalid message with no standard cause. This cause indicates that the equipment receives a message that is not permissible in the call state according to the procedures. This cause can also indicate that the equipment receives a STATUS message to indicate an incompatible call state. The issue occurs due to a D-channel error. If the error recurs, report the error to your ISDN service provider.

The info could be accessed here:

http://www.cisco.com/c/en/us/support/docs/dial-access/integrated-services-digital-networks-isdn-channel-associated-signaling-cas/8607-isdn-disc-code.html

Btw, is the Calling Number an issue or Called Number? In either case, you would want to speak to your Telco and ask the Calling Number Party's Telco as well and raise a Trouble Ticket at both the ends

HTH

[shinyoooo]

Thanks for your input Sam.

I am the calling party in this case making the call to '0355XXXXX'

So the called number is being the issue in my case.

I have already raised this issue with my service provider in Taiwan but they were not so helpful and just came back with the response saying that called party is sending the NOTIFY and I am not processing this message properly and disconnecting the call...  It is true in a way but it was so much easier if they could generate the usual ALERTING message instead of NOTFY in the first place.

Is there any way to ignore this NOTIFY message and just wait for the ALERTING message to follow?

[shinyoooo]

I end up opening a TAC case and issue was resolved by changing the isdn switch-type to "primary-net5" as "primary-5ess" was not capable of processing some complicated message such as "NOTIFY" in my case.

Although I was told to use "primary-5ess" from the provider but changing this has fixed everything without any errors.

Thanks again Sam for your input.