Nick Adams
2007-Nov-14 10:54 UTC
[asterisk-users] Asterisk ignoring manager events when busy
Hello, I currently have a pretty standard 1.2.21 Asterisk system running purely SIP termination (no zap/IAX/H323..etc). We have an auto-dialing system that generates calls via the manager API. The system runs beautifully until it gets to about 200 calls. I can generate these calls in quite literally seconds if desired (or minutes). The kicker: I can't seem to get past this 200 call point even though the system is/seems very idle. Low CPU utilisation (~40%), plenty of RAM, close to zero disk usage (I/O Wait ~2%), bandwidth is plentiful (1Gbit) and the current calls are crystal clear. I get the feeling Asterisk is ignoring or dumping manager events. We watch for the "Success" from the originate command and it comes if there is less than roughly 200 calls but is unreliable after that. I could understand if this was happening at 100% cpu but not at the under-utilised state the box is at. Any hints? Thanks, Nick.
Doug Lytle
2007-Nov-14 12:15 UTC
[asterisk-users] Asterisk ignoring manager events when busy
Nick Adams wrote:> The kicker: I can't seem to get past this 200 call point even though the >What does your console show at this time? When testing, I've noted the 200 call limit was because I had too many open files. I had to increase this by typing ulimit -n 4096 before starting Asterisk. The default is 1024. Doug -- Ben Franklin quote: "Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety."
Reasonably Related Threads
- compiz plugins and window types
- gtk-window-decorator segfault?
- allofmp3.com provides ogg downloads
- [PATCH RFC v5 5/8] pvqspinlock, x86: Enable unfair queue spinlock in a KVM guest
- [PATCH RFC v5 5/8] pvqspinlock, x86: Enable unfair queue spinlock in a KVM guest