<p>IIRC, some early dialler of the pre-AMI era used this technique to control the number of calls placed simoultaneously - they just counted the number of call files in the spool dir. As they are deleted when the call is over, this was a simple way to do the throttling. </p>
<p>You could use a similar technique; have call files written to a staging directory and then use a simple process to transfer them to the actual spool dir so that there are never more than N in the spool dir.</p><p>Thanks<br>
</p><p>l.</p><p></p><br><div class="gmail_quote">2009/2/27 Bill Michaelson <span dir="ltr"><<a href="mailto:bill@cosi.com">bill@cosi.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Is there a convenient way to limit the number of call files (outgoing directory) that are processed concurrently?<br>
<br>_______________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br></blockquote></div><br><br clear="all"><br>-- <br>Loway - home of QueueMetrics - <a href="http://queuemetrics.com">http://queuemetrics.com</a><br>
<br>