Re: [asterisk-dev] magic number 128- for concurrent meetme monitoring calls.
In article CALLKq0S4TvEdbnCez_9soe9kEVbGyyO6_ru-_SJEHaxS=m0...@mail.gmail.com, Paul Belanger paul.belan...@polybeacon.com wrote: 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. Yup, next limit you'll hit is dahdi pseudo channels, which is 512. Is that limit configurable or fixed? Tony -- Tony Mountifield Work: t...@softins.co.uk - http://www.softins.co.uk Play: t...@mountifield.org - http://tony.mountifield.org -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] magic number 128- for concurrent meetme monitoring calls.
On Fri, Mar 14, 2014 at 7:32 AM, Tony Mountifield t...@softins.co.uk wrote: In article CALLKq0S4TvEdbnCez_9soe9kEVbGyyO6_ru-_SJEHaxS=m0...@mail.gmail.com, Paul Belanger paul.belan...@polybeacon.com wrote: 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. Yup, next limit you'll hit is dahdi pseudo channels, which is 512. Is that limit configurable or fixed? Yes[1]. [1] http://lists.digium.com/pipermail/dahdi-commits/2011-January/002717.html -- Paul Belanger | PolyBeacon, Inc. Jabber: paul.belan...@polybeacon.com | IRC: pabelanger (Freenode) Github: https://github.com/pabelanger | Twitter: https://twitter.com/pabelanger -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] magic number 128- for concurrent meetme monitoring calls.
On Fri, Mar 14, 2014 at 3:02 AM, Olle E. Johansson o...@edvina.net wrote: On 13 Mar 2014, at 23:54, Richard Mudgett rmudg...@digium.com wrote: On Thu, Mar 13, 2014 at 5:07 PM, beiyan jin jinbeiyan2...@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? -- Paul Belanger | PolyBeacon, Inc. Jabber: paul.belan...@polybeacon.com | IRC: pabelanger (Freenode) Github: https://github.com/pabelanger | Twitter: https://twitter.com/pabelanger -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] magic number 128- for concurrent meetme monitoring calls.
On 14 Mar 2014, at 14:13, Paul Belanger paul.belan...@polybeacon.com wrote: On Fri, Mar 14, 2014 at 3:02 AM, Olle E. Johansson o...@edvina.net wrote: On 13 Mar 2014, at 23:54, Richard Mudgett rmudg...@digium.com wrote: On Thu, Mar 13, 2014 at 5:07 PM, beiyan jin jinbeiyan2...@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 -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] magic number 128- for concurrent meetme monitoring calls.
On Fri, Mar 14, 2014 at 02:40:22PM +0100, Olle E. Johansson wrote: On 14 Mar 2014, at 14:13, Paul Belanger paul.belan...@polybeacon.com wrote: On Fri, Mar 14, 2014 at 3:02 AM, Olle E. Johansson o...@edvina.net wrote: 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. I think this is the thread: http://thread.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/51750 But basically, there is still a fixed number of conferences DAHDI can support since that is still stored as an array in the code and not a dynamic list. The current limit is 1024 [1]. [1] https://github.com/asterisk/dahdi-linux/blob/master/include/dahdi/user.h#L294 FYI, that DAHDI_MAX_SPANS and DAHDI_MAX_CHANNELS in include/dahdi/user.h are only for legacy userspace. As far as the kernel is concerned, there is no longer a fixed upper bound on the number of spans or channels. This work for channels was done as part of the dahdi channel hotplug work. -- Shaun Ruffell Digium, Inc. | Linux Kernel Developer 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at: www.digium.com www.asterisk.org -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] magic number 128- for concurrent meetme monitoring calls.
On Fri, Mar 14, 2014 at 10:02 AM, Shaun Ruffell sruff...@digium.com wrote: On Fri, Mar 14, 2014 at 02:40:22PM +0100, Olle E. Johansson wrote: On 14 Mar 2014, at 14:13, Paul Belanger paul.belan...@polybeacon.com wrote: On Fri, Mar 14, 2014 at 3:02 AM, Olle E. Johansson o...@edvina.net wrote: 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. I think this is the thread: http://thread.gmane.org/gmane.comp.telephony.pbx.asterisk.devel/51750 But basically, there is still a fixed number of conferences DAHDI can support since that is still stored as an array in the code and not a dynamic list. The current limit is 1024 [1]. [1] https://github.com/asterisk/dahdi-linux/blob/master/include/dahdi/user.h#L294 FYI, that DAHDI_MAX_SPANS and DAHDI_MAX_CHANNELS in include/dahdi/user.h are only for legacy userspace. As far as the kernel is concerned, there is no longer a fixed upper bound on the number of spans or channels. This work for channels was done as part of the dahdi channel hotplug work. Interesting, thanks checking them out. Based on some initial testing, we seen a 2 to 1 performance increase switching from app_meetme to app_confbridge, so interesting to read about some other limits we didn't hit. -- Paul Belanger | PolyBeacon, Inc. Jabber: paul.belan...@polybeacon.com | IRC: pabelanger (Freenode) Github: https://github.com/pabelanger | Twitter: https://twitter.com/pabelanger -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
[asterisk-dev] magic number 128- for concurrent meetme monitoring calls.
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? Thanks in advance for your help! Beiyan-- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] magic number 128- for concurrent meetme monitoring calls.
On Thu, Mar 13, 2014 at 5:07 PM, beiyan jin jinbeiyan2...@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. Richard -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [asterisk-dev] magic number 128- for concurrent meetme monitoring calls.
On Thu, Mar 13, 2014 at 6:54 PM, Richard Mudgett rmudg...@digium.com wrote: On Thu, Mar 13, 2014 at 5:07 PM, beiyan jin jinbeiyan2...@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. Yup, next limit you'll hit is dahdi pseudo channels, which is 512. -- Paul Belanger | PolyBeacon, Inc. Jabber: paul.belan...@polybeacon.com | IRC: pabelanger (Freenode) Github: https://github.com/pabelanger | Twitter: https://twitter.com/pabelanger -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
