<br><br><div class="gmail_quote">On Fri, Sep 21, 2012 at 1:27 AM, Ali Işık <span dir="ltr"><<a href="mailto:fenlisesi@gmail.com" target="_blank">fenlisesi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
All right, thank you, João. I will have to set up a little lab here<br>
and see what I can get done with these parameters.<br>
<br>
How about my original question, by the way, about the maturity of<br>
mod_callcenter, as you see it, and its place in the roadmap?<br>
<br>
Best,<br>
<br>
-- Ali Işık<br>
<br></blockquote><br>
</div>mod_callcenter was donated by a long-time user named Marc-Olivier Chouinard, aka "Moc" on IRC. He's been rather busy lately but I can tell you that he uses it for his customers up in Canada for small and medium-sized call centers. I would say that it is pretty stable and well-documented. A number of people are using it in lieu of mod_fifo. Both mod_callcenter and mod_fifo have the same basic goal: getting inbound calls to agents as quickly as possible and queuing them up while they are waiting. The primary differences are in how they handle the routing/selecting of which call goes to which agent. mod_cc follows a more traditional "ACD-like" approach. mod_fifo is really a "first in, first out" queue that has a bunch of options for customizing how calls get to agents. They both have their place and they both work well, so the big challenge for you is researching them to see which one fits your needs best.<br>
<br>-MC<br>