Sunday, 27 July 2008

Yet more issues with CallManager 6.0

Yet another bug with Cisco CallManager 6.0. Sigh. This was identified in version UCOS_ES_6.0.1.3103-1.

We found similarly to a previous post that when we tried to dial out, we got the following debug with "Bearer/channel not available". However we found in that this instance, changing the CLID made no difference, we verified that the customer had specified the correct number of B channels on their PRI, and attempts to use commands such as "bchan-order ascending" made no difference.

*Jan 26 09:01:29.606: ISDN Se0/0/0:15 Q931: Applying typeplan for sw-type 0x12 is 0x0 0x0, Calling num 01234115200*Jan 26 09:01:29.610: ISDN Se0/0/0:15 Q931: Applying typeplan for sw-type 0x12 is 0x0 0x0, Called num 07989163892*Jan 26 09:01:29.610: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8 callref = 0x0117 Bearer Capability i = 0x8090A3 Standard = CCITT Transfer Capability = Speech Transfer Mode = Circuit Transfer Rate = 64 kbit/s Channel ID i = 0xA98399 Exclusive, Channel 25 Progress Ind i = 0x8183 - Origination address is non-ISDN Calling Party Number i = 0x0081, '01234115200' Plan:Unknown, Type:Unknown Called Party Number i = 0x80, '07989163892' Plan:Unknown, Type:Unknown*Jan 26 09:01:29.822: ISDN Se0/0/0:15 Q931: RX <- CALL_PROC pd = 8 callref = 0x8117 Channel ID i = 0xA98399 Exclusive, Channel 25 Notification Ind i = 0xE8*Jan 26 09:01:33.614: ISDN Se0/0/0:15 Q931: RX <- ALERTING pd = 8 callref = 0x8117*Jan 26 09:01:33.654: ISDN Se0/0/0:15 Q931: TX -> DISCONNECT pd = 8 callref = 0x0117 Cause i = 0x80AC - Requested circuit/channel not available*Jan 26 09:01:33.830: ISDN Se0/0/0:15 Q931: RX <- RELEASE pd = 8 callref = 0x8117*Jan 26 09:01:33.834: ISDN Se0/0/0:15 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x0117

As it turned out, we were using 7945 and 7965 phones (Which id never seen before, though are worth the money over a 7961 etc!). Turning off G.722 Wideband codec on the phone fixed the problem! You may wish to think about changing the Enterprise parameter and resetting all phones if you aren't going to use this codec in your enterprise.


Anonymous said...

Wow. Thanks for blogging this. We had the same symptoms with our 7962 phones, but once we disabled advertise g.722 codec, the outbound calls on our PRI started working!

Name: Michael Gerrard said...

Awesome matey, glad to hear it got you sorted!


isaac said...

Same issue here... it can also be solved with the following dial-peer if you don't want to disable g722:

dial-peer voice 1 voip
incoming called-number .
codec g711alaw

Anonymous said...

top [url=]uk casino bonus[/url] brake the latest [url=]las vegas casino[/url] unshackled no store bonus at the foremost [url=]casino online