<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jul 15, 2013 at 7:59 AM, jg <span dir="ltr"><<a href="mailto:webaccounts@jgoettgens.de" target="_blank">webaccounts@jgoettgens.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">When you have many calls, there are usually (read/write=all) a lot of RTP, RTCP, and VarSet events. This might slow down things, but whether they occur or not depends on your configuration.<br>
<br>
This might be another thing to look at.<span class="HOEnZb"><font color="#888888"><br>
<br></font></span></blockquote><div><br></div><div style>When you execute an Originate action, are you doing so synchronously or asynchronously?</div><div style><br></div><div style>A synchronous Originate performs the full outbound dial operation on the thread servicing the AMI request. Since each session in AMI gets its own thread that services both actions and events, a synchronous Originate can block that session from receiving events until it completes.</div>
<div style><br></div><div style>Matt</div></div><div><br></div>-- <br><div dir="ltr"><div>Matthew Jordan<br></div><div>Digium, Inc. | Engineering Manager</div><div>445 Jan Davis Drive NW - Huntsville, AL 35806 - USA</div>
<div>Check us out at: <a href="http://digium.com" target="_blank">http://digium.com</a> & <a href="http://asterisk.org" target="_blank">http://asterisk.org</a></div></div>
</div></div>