<br><br><div><span class="gmail_quote">On 16/01/2008, <b class="gmail_sendername">Nitzan Kon</b> <<a href="mailto:nk3569@yahoo.com">nk3569@yahoo.com</a>> wrote:</span><blockquote class="gmail_quote" style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex">
After doing some googling I think I found your problem.. if you look in<br>chan_iax2.c you'll see there is a hard-coded limit of 256 channels:<br><br>} else if (iaxthreadcount > 256) {<br>ast_log(LOG_NOTICE, "limiting iaxthreadcount to 256\n");
<br>iaxthreadcount = 256;<br><br>and:<br><br>} else if (iaxmaxthreadcount > 256) {<br>ast_log(LOG_NOTICE, "Limiting iaxmaxthreadcount to 256\n");<br>iaxmaxthreadcount = 256;<br></blockquote></div><br><div><br class="webkit-block-placeholder">
</div><div>Hi,</div><div><br class="webkit-block-placeholder"></div><div>You have a misunderstanding. chan_iax does not use one thread per call. It has a pool of threads, and allocates them on an as-required basis when it has frames to process or other tasks.
</div><div><br class="webkit-block-placeholder"></div><div>So there's no reason why 256 active calls should mean 256 threads in use. Seeing each call only has a packet arriving every 20 milliseconds, and packets usually take much less than that time to process, usually much fewer than 256 threads will be in use.
</div><div><br class="webkit-block-placeholder"></div><div>We have a customer who runs up to 500 concurrent IAX calls on Asterisk <a href="http://1.4.10.1">1.4.10.1</a>. So at that version, at least, you can go to more than 256 calls.
</div><div><br class="webkit-block-placeholder"></div><div>Regards,</div><div>Steve</div><div><br class="webkit-block-placeholder"></div><div><br class="webkit-block-placeholder"></div><div><br class="webkit-block-placeholder">
</div>