cancel
Showing results for 
Search instead for 
Did you mean: 
cancel

Cisco extend and connect

Michael Schmidt
Beginner
Beginner

Hi,

 

I configured Cisco extend and connect (https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/211427-Configure-Jabber-Extend-and-Connect-and.html).

 

At one customer it working without any problems. At the other customer (configured in the same way) the remote destination is ringing and when I pickup the call the call will be ended automatically and no new call to called party will be placed.

 

In the attachement the one call from the customer where it`s working and the other one where it`s not working. What could be the problem?

 

BR

Michael

2 REPLIES 2

Maren Mahoney
VIP Advocate VIP Advocate
VIP Advocate

The first error is you sending "Cause i = 0x80A9 - Temporary failure" which is a (0x80) normal call clearing but due to a (A9) which is a network malfunction.
Later there is you sending "Cause i = 0x80E262 - Message not compatible with call state or not implemented". E2 indicates a D-Channel problem. In both cases, contacting the telco is recommended.
So the errors are pointing towards a technical problem, not a numbering problem. Is this the same telco for both customers?

And it looks to me like it is a telco problem. Take a look at the received "Invoke ID". In the unsuccessful call it equals zero, which I'm guessing isn't valid.

Successful Call:
Jun 10 19:17:11.835: ISDN Se0/0/0:15 Q931: RX <- FACILITY pd = 8  callref = 0x9FFD
        Facility i = 0x91A11302022B29020122300AA1053003020104820100
                Protocol Profile = Remote Operations Protocol
                0xA11302022B29020122300AA1053003020104820100
                Component = Invoke component
                        Invoke Id = 11049
                        Operation = AOCDChargingUnit

Unsuccessful Call:
Jun 10 20:55:52: ISDN Se0/0/0:15 Q931: RX <- FACILITY pd = 8  callref = 0xD806
        Facility i = 0x91A115020100020122300DA1053003020104820100830100
                Protocol Profile = Remote Operations Protocol
                0xA115020100020122300DA1053003020104820100830100
                Component = Invoke component
                        Invoke Id = 0
                        Operation = AOCDChargingUnit
Jun 10 20:55:52: ISDN Se0/0/0:15 **ERROR**: Ux_BadMsg: Invalid Message for call state 11, call id 0xD612, call ref 0x5806, event 0x62
Jun 10 20:55:52: ISDN Se0/0/0:15 Q931: TX -> STATUS pd = 8  callref = 0x5806
        Cause i = 0x80E262 - Message not compatible with call state or not implemented
        Call State i = 0x0B

 

So I'd say take this to your telco.

Maren

 

Yes at both customers it`s CUCM.

 

At working customer it`s CUCM 10.5 with MGCP voicegateway.

 

At non working customer it`s CUCM 11.5 with H.323 voicegateway

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: