<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote">On Mon, Oct 21, 2013 at 11:41 AM, Anthony Minessale <span dir="ltr"><<a href="mailto:anthony.minessale@gmail.com" target="_blank">anthony.minessale@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">It already is an option on the conference configs: timer-name.<div></div></div></blockquote><div><br></div>
<div>in the latest 1.2.x version, and also an older master version that we're using for production at a couple of sites, the timer name in mod_conference.c was hard-coded to "soft". If it's now a configurable parameter in mod_conference.c, then that's great, the admin will just need to set that "timer-name" config to "dahdi", and they'll be good to go.</div>
<div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><br></div><div>For scale-ability I also recommend looking at mod_timerfd and doing it in a similar fashion to use one single dadhi channel to service N threads.<br>
</div><div><br></div></div></blockquote><div><br></div><div>Yes, that's how I did it. I learned a lot by studying mod_timerfd and also switch_time.c - there's just one ~1mS loop in my code.</div><div><br></div><div>
Bob</div><div><br></div><div><br></div></div></div></div>