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

Who Me Too'd this topic

CUCM 8.6 Call fail with Bearer capability not implemented over sip trunk

Ayodeji Okanlawon
VIP Alumni
VIP Alumni

Guys,

I have an issue I am investigating and just want to know your thoughts..

Call flow...

CUBE---->CUCM---->UnityConnection----->CUCM----->GK------CUBE---SP

Incoming call flow is as described above...

I have attached a detail trace----all explained as the call flows. I have explained each step of the trace so its fairly easy to read.

The problem is this...

1. I get a disconnect cause of 65. Which is bearer capability not implemented..

******H245 error**********

13:22:20.211 |TranslateAndTransport(5526)::wait_SdlCloseInd - ERROR: H245 signaling connection aborted!!!, err=0|28,100,63,1.134678^172.15.10.30^*
13:22:20.211 |SIG-MediaCoordinator-wait_AuDisconnectRequest,CI(484551469,484551483),IFCreated(1,1)|28,100,13,231427.46^10.105.40.84^*

********h225 disconnect cause..65***************

13:22:20.210 |In  Message -- H225ReleaseCompleteMsg -- Protocol= H225Protocol|*^*^*
13:22:20.210 |Ie - Q931CauseIe -- IEData= 08 02 80 C1 |*^*^*
13:22:20.210 |Ie - H225UserUserIe -- IEData= 7E 00 22 05 25 80 06 00 08 91 4A 00 04 11 00 11 00 00 68 63 FA 79 8E D1 F7 DA 13 DA 1C 0A 69 28 4A 10 80 01 00 |*^*^*
13:22:20.210 |MMan_Id= 0. (iep=  0 dsl=  0 sapi=  0 ces= 0 IpAddr=5428690a IpPort=1720)|*^*^*
13:22:20.210 |IsdnMsgData1= 08 02 93 DA 5A 08 02 80 C1 7E 00 22 05 25 80 06 00 08 91 4A 00 04 11 00 11 00 00 68 63 FA 79 8E D1 F7 DA 13 DA 1C 0A 69 28 4A 10 80 01 00 |*^*^*
13:22:20.210 |value H323-UserInformation ::= |*^*^*
13:22:20.210 |{
  h323-uu-pdu
  {
    h323-message-body releaseComplete :
      {
        protocolIdentifier { 0 0 8 2250 0 4 },
        callIdentifier
        {
          guid '006863FA798ED1F7DA13DA1C0A69284A'H

2. Here is the ********sip disconnect cause..65***************


13:22:28.216 |//SIP/SIPTcp/wait_SdlSPISignal: Outgoing SIP TCP message to 172.15.10.30 on port 5060 index 405
[513486,NET]
BYE sip:07567890000@172.15.10.30:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 172.15.10.20:5060;branch=z9hG4bK1e703211043c4
From: <sip:901788239701@172.15.10.20>;tag=74431~ffa80926-5fac-4dd6-b405-2dbbc56ae9a2-484551469
To: <sip:07567890000@172.15.10.30>;tag=23DEB814-124C
Date: Thu, 05 Apr 2012 12:22:19 GMT
Call-ID: C9635D99-7E5011E1-8741D34F-B20E53F1@172.15.10.30
User-Agent: Cisco-CUCM8.6
Max-Forwards: 70
CSeq: 105 BYE
Reason: Q.850;cause=65

3. During the call I see several mid-call invite with SDPs.

The call originally started with G729 codec, but mid-call Changes to G711ulaw...

I suppose this is where the problem is. It looks like the far end cant do G729 or G711ulaw. Would this be the reason why I get aleast 3 mid-call invite?

4. I know that bearer ca[ability can be a few things. But does this look more like the far end wants G711a. Bear in mind its an IPCC call center so I know for certain its G711. But looks like G711ulaw inst working.

Thanks for the ideas guys...

Please rate all useful posts
Who Me Too'd this topic