Bearer Capability Cisco Call Manager issue

[U2JCR13]

Hello Everyone,

I have a Cisco Call Manager V 7.15 in a main site ans two remote regions using G729 for regions calls and G711 for Telephone calls in every region.

I got an Issue with incomming calls espeacially from a mobile number, when calling for more than 5 times to the same Extension Number, the last call can't be completed I got the following log, when the call fails:

ccCallSetupRequest:

cisco-username=8112632016

----- ccCallInfo IE subfields -----
cisco-ani=sip:8112632016@172.25.0.60
cisco-anitype=0
cisco-aniplan=0
cisco-anipi=0
cisco-anisi=0
dest=2657
cisco-desttype=0
cisco-destplan=0
cisco-rdie=FFFFFFFF
cisco-rdn=
cisco-lastrdn=
cisco-rdntype=0
cisco-rdnplan=0
cisco-rdnpi=-1
cisco-rdnsi=-1
cisco-redirectreason=-1 fwd_final_type =0
final_redirectNumber =
hunt_group_timeout =0

Feb 21 17:33:58.163: //3606/98FC2A89ADDF/CCAPI/ccIFCallSetupRequestPrivate:
Interface=0x488626D4, Interface Type=3, Destination=, Mode=0x0,
Call Params(Calling Number=sip:8112632016@172.25.0.60, (Calling Name=)(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed),

Called Number=2657(TON=Unknown, NPI=Unknown), Calling Translated=FALSE,
Subscriber Type Str=Unknown, FinalDestinationFlag=TRUE, Outgoing Dial-peer=2006, Call Count On=FALSE,
Source Trkgrp Route Label=, Target Trkgrp Route Label=, tg_label_flag=0, Application Call Id=)
Feb 21 17:33:58.163: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

Feb 21 17:33:58.163: :cc_get_feature_vsa malloc success
Feb 21 17:33:58.163: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

Feb 21 17:33:58.163: cc_get_feature_vsa count is 2
Feb 21 17:33:58.163: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:
SPI Call Setup Request Is Success; Interface Type=3, FlowMode=1
Feb 21 17:33:58.163: //3607/98FC2A89ADDF/CCAPI/ccCallSetContext:
Context=0x4A696638

Feb 21 17:33:58.163: //3606/98FC2A89ADDF/CCAPI/ccSaveDialpeerTag:
Outgoing Dial-peer=2006
Feb 21 17:33:58.167: //3607/98FC2A89ADDF/CCAPI/cc_api_call_proceeding:
Interface=0x488626D4, Progress Indication=NULL(0)
Feb 21 17:33:58.227: //3607/98FC2A89ADDF/CCAPI/cc_api_call_alert:
Interface=0x488626D4, Progress Indication=NULL(0), Signal Indication=SIGNAL RINGBACK(1)
Feb 21 17:33:58.227: //3607/98FC2A89ADDF/CCAPI/cc_api_call_alert:
Call Entry(Retry Count=0, Responsed=TRUE)
Feb 21 17:33:58.227: //3606/98FC2A89ADDF/CCAPI/ccCallAlert:
Progress Indication=NULL(0), Signal Indication=SIGNAL RINGBACK(1)
Feb 21 17:33:58.227: //3606/98FC2A89ADDF/CCAPI/ccCallAlert:
Call Entry(Responsed=TRUE, Alert Sent=TRUE)
Feb 21 17:34:01.019: //3607/98FC2A89ADDF/CCAPI/cc_api_call_disconnected:
Cause Value=65, Interface=0x488626D4, Call Id=3607
Feb 21 17:34:01.019: //3607/98FC2A89ADDF/CCAPI/cc_api_call_disconnected:
Call Entry(Responsed=TRUE, Cause Value=65, Retry Count=0)
Feb 21 17:34:01.023: //3606/xxxxxxxxxxxx/CCAPI/ccCallReleaseResources:
release reserved xcoding resource.
Feb 21 17:34:01.023: //3607/98FC2A89ADDF/CCAPI/ccCallSetAAA_Accounting:
Accounting=0, Call Id=3607
Feb 21 17:34:01.023: //3607/98FC2A89ADDF/CCAPI/ccCallDisconnect:
Cause Value=65, Tag=0x0, Call Entry(Previous Disconnect Cause=0, Disconnect Cause=65)
Feb 21 17:34:01.023: //3607/98FC2A89ADDF/CCAPI/ccCallDisconnect:
Cause Value=65, Call Entry(Responsed=TRUE, Cause Value=65)

This cause as I know is related to "bearer capability not implemented", I am using the codecs listed in the upper part of this message, which other could the cause related with this issue since it only happens ramdomly. It is possible to change the bearer capability?

Regards

 

[whykap]

It looks like you are using sip trunks?
What do you mean calling more than five times? Elaborate a little.
Can you tell us more about your topology and how calls are taking place?