[cisco-voip] Re: Callmanager Maximum Active Calls

[Kevin Thorngren]

Hi Ryan,

I have not seen the message "Maximum Active calls reached" in a 
CallManager event log before.  The "requested circuit unavailable" 
disconnect cause is many times the result of a glare condition where an 
outbound call from CCM and an inbound call form the PBX are setup using 
the same channel.   To avoid this we recommend setting the channel 
order in CallManager opposite of the PBX, ie, Bottom Up.  The "recovery 
on timer expiry" is due to one of the media setup timers expiring.  We 
see this issue many times when the destination is a cell phone.  We 
would have to see where you are in the call setup to determine the 
timer.  The timers are found under CCMAdmin > Service > Service 
Parameters > Publisher > Cisco CallManager.  If you have detailed 
SDL/CCM traces running then you should see the timer that expires, ie, 
the T3XX timers.

Your problem description bring to mind  a couple of defects that I have 
seen in the past with older CallManager versions might be affecting 
you:
CSCea69109 - Call_Proceeding not mapped when received on a Route List
This is an issue where, when using Route Lists, there is a problem with 
CallManager not mapping the Call Proceeding messages.  The workaround 
is to point the Route Pattern directly to the GW instead of using a 
Route List.

CSCdx41500 - CM should not respond with Restart when cause=channel not 
available
Depending on your configuration, this could cause the B-Channels to 
become locked up.

These two defects may or may not be your issue, Detailed CCM and 
SDL/CCM traces will help to determine this.  Please feel free to open a 
TAC case to have the traces reviewed.

Kevin
On Jan 31, 2005, at 5:05 AM, Ryan Fields wrote:

> Hi,
>
> Let me correct myself. Its "requested circuit unavailable" and 
> "recovery on
> timer expiry" on the pabx
>
> Thanks.
>
> On Mon, 31 Jan 2005 17:30:06 +0800, Ryan Fields 
> <jryan.fields at gmail.com> wrote:
>> Hi All,
>>
>> I've got two E1 isdn registered on a single callmanager 3.1(2c) and
>> a pabx/predictive dialer configured on the other end.
>> At the end of the day, calls could not go through anymore.
>> On the Pabx, I get "requested circuit unavailable" and "disconnect
>> timer expiry"
>>
>> The cisco event log gives an error "Maximum Active calls reached".
>> I had to restart the callmanager service to get calls goin again.
>>
>> What is the maximum active call value for the callmanager,
>> is there anyway to increase it?
>>
>> If this is an improper disconnect or disconnect timer issue between
>> the dialer/pabx and callmanager, what other settings can I tweak on
>> callmanager for it to clear calls that may have hung?
>>
>> Thanks
>> Ryan
>>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>