[asterisk-dev] magic number 128- for concurrent meetme monitoring calls.

[Olle E. Johansson]

On 14 Mar 2014, at 14:13, Paul Belanger <paul.belanger at polybeacon.com> wrote:

> On Fri, Mar 14, 2014 at 3:02 AM, Olle E. Johansson <oej at edvina.net> wrote:
>> 
>> On 13 Mar 2014, at 23:54, Richard Mudgett <rmudgett at digium.com> wrote:
>> 
>> On Thu, Mar 13, 2014 at 5:07 PM, beiyan jin <jinbeiyan2002 at yahoo.com> wrote:
>>> 
>>> In my load test calls,
>>> 1. each call has two parties connected by meetme conference.
>>> 2. Each call is recorded by monitor.
>>> 
>>> For every load test, before the number of concurrent calls reach 128,
>>> everything is fine. But after 128, newly started calls get dropped.
>>> Both CPU and memory are ok in the linux box hosting asterisk.
>>> 
>>> The behavior is like asterisk is configured to only allow 128 concurrent
>>> calls or 256 concurrent channels.
>>> 
>>> If this is configured like this by default, where can I change the
>>> configuration?
>>> If it is not configured, then why it only allows 128 concurrent calls?
>> 
>> 
>> Sounds like the ulimit is at the default 1024.  You need to increase it
>> because
>> Asterisk needs a lot of file descriptors.
>> 
>> This kind of question is better asked on the asterisk-users list.
>> 
>> 
>> Don't forget that if you are using DAHDI there are dahdi file handles that
>> will
>> expire at some point and give you strange problems. We had a discussion
>> about that
>> a year or two ago on the list.
>> 
> Interesting, I missed that discussion, can you sum it up to a few
> lines while I look for the thread?

Did not find it either. We had big issues when running hundreds of meetme's.
Someone on the Dahdi teem confirmed and had no solution, so we had to move
to app_konference, which is not a fun place either.

/O