<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I think order by outbound_call_count will cause problem. Think about the fifo run a few days, and we added a new member, the outbound_call_count will always less than others in a certain time. What about use order by next_avail?<div><br></div><div><br><div><html>On May 4, 2009, at 10:55 PM, François Delawarde wrote:</html><br class="Apple-interchange-newline"><blockquote type="cite"> <div> Hello,<br> <br> Anthony, I would like to provide a patch allowing having different call distribution strategies, at least for "call back" agents.<br> <br> Do you think the simple approach of modifying the SQL query in find_consumers (given strategy that would be set from dialplan) would be enough?<br> <br> Thanks,<br> François.<br> <br> On Mon, 2009-05-04 at 08:25 -0500, Anthony Minessale wrote:<br> <blockquote type="CITE"> <br> <br> </blockquote> <blockquote type="CITE"> On Sun, May 3, 2009 at 11:01 PM, seven <<a href="mailto:dujinfang@gmail.com">dujinfang@gmail.com</a>> wrote: </blockquote> <blockquote type="CITE"> <blockquote> Actually, for the "call back" agents, because the fifo use originate to start a new session, the new session won't hang up unless one agent answered or timeout. Agents will hear nothing and wait(member_wait=wait) on the queue or hanup(nowait) if caller hang up before an agent answer the phone. ' </blockquote> </blockquote> <blockquote type="CITE"> <blockquote> <br> </blockquote> </blockquote> <blockquote type="CITE"> <br> <br> When you are using on-hook agents, it's presumed to be under low call volume, you can just set the agents to get popped<br> into the queue in nowait mode so if the caller changed his mind the agent will get a hangup. Remember, if there are X customers in the queue, mod_fifo generates X outbound calls to try to service them. <br> <br> <br> </blockquote> <blockquote type="CITE"> <blockquote> <br> <br> </blockquote> </blockquote> <blockquote type="CITE"> <blockquote> And I also found out the the member timeout doesn't work but call_timeout works in a dial string. Is it a bug I should reported to jira? </blockquote> </blockquote> <blockquote type="CITE"> <blockquote> <br> <br> </blockquote> </blockquote> <blockquote type="CITE"> <blockquote> <fifo name="sales_fifo@$${domain}" importance="0"> </blockquote> </blockquote> <blockquote type="CITE"> <blockquote> <member timeout="10" simo="1" lag="5">{call_timeout=6,fifo_member_wait=nowait}user/1009@$${domain}</member> </blockquote> </blockquote> <blockquote type="CITE"> <blockquote> </fifo> </blockquote> </blockquote> <blockquote type="CITE"> <blockquote> <br> </blockquote> </blockquote> <blockquote type="CITE"> <br> <br> call_timeout is only valid on inbound legs to set the timeout it's willing to wait for a caller to answer. You are confusing it with leg_timeout which is designed to go in the {}<br> <br> </blockquote> <blockquote type="CITE"> <blockquote> <br> <br> </blockquote> </blockquote> <blockquote type="CITE"> <blockquote> And even the timeout works, it's not ideal. It's better to bridge to an agent other than originate I think. Keep looking. </blockquote> </blockquote> <blockquote type="CITE"> <blockquote> <br> </blockquote> </blockquote> <blockquote type="CITE"> <blockquote> <br> </blockquote> </blockquote> <blockquote type="CITE"> <br> I am not sure what you mean by that. bridge instead of originate? The process is to originate the call and then bridge the agent to the caller. All calls in FS start out as origiante???? <br> <br> If you want app_queue you are welcome to download and use it from <a href="http://www.asterisk.org">http://www.asterisk.org</a><br> <br> </blockquote> <blockquote type="CITE"> <blockquote> <br> </blockquote> </blockquote> <blockquote type="CITE"> <blockquote> On Apr 29, 2009, at 4:27 PM, François Delawarde wrote: </blockquote> </blockquote> <blockquote type="CITE"> <blockquote> <blockquote type="CITE"> Hi,<br> <br> It should be easy to modify mod_fifo to include this functionality.<br> <br> Correct me if I'm wrong:<br> For "call back" agents at least, when X calls are in the the queue, Freeswitch tries to search for up to X agents in database. This algorithm is much more optimized than Asterisk, as Asterisk will take calls one by one and try to connect them to an agent, it should then stay as it is.<br> <br> The simplest idea to control the call distribution algorithm would be to modify the database query in the "find_consumers" function (right now, the algorithm is: "order by outbound_call_count"). A variable could control the "order by" of this query, and the problem would be solved at least for "call back" agents. I guess sqlite3 should allow very complex queries, but I don't know if there could be performance issues.<br> <br> Do you think it is a possible -trivial- solution?<br> <br> François.<br> <br> On Wed, 2009-04-29 at 08:46 +0200, Antonio Gallo wrote: <blockquote type="CITE"> <pre>seven ha scritto:
> oh, thank you Antonio. I think it would be better to collect more
> ideas before open a bounty. And I more interested in playing(including
> patching the code) with that than use the function.
>
I was working on other stuff yesterday and just looked at the wiki:
- it seems there is already a bounty for something like that;
- there is a wiki page about how to implement it with Javascript, ofc
you need to tailor it to your own needs;
AgX
_______________________________________________
Freeswitch-users mailing list
<a href="mailto:Freeswitch-users@lists.freeswitch.org">Freeswitch-users@lists.freeswitch.org</a>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users">http://lists.freeswitch.org/mailman/options/freeswitch-users</a>
<a href="http://www.freeswitch.org">http://www.freeswitch.org</a>
</pre> </blockquote> </blockquote> </blockquote> </blockquote> <blockquote type="CITE"> <blockquote> <blockquote type="CITE"> _______________________________________________<br> Freeswitch-users mailing list<br> <a href="mailto:Freeswitch-users@lists.freeswitch.org">Freeswitch-users@lists.freeswitch.org</a><br> <a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br> UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br> <a href="http://www.freeswitch.org">http://www.freeswitch.org</a> </blockquote> </blockquote> </blockquote> <blockquote type="CITE"> <blockquote> <br> <br> </blockquote> </blockquote> <blockquote type="CITE"> <blockquote> <br> _______________________________________________<br> Freeswitch-users mailing list<br> <a href="mailto:Freeswitch-users@lists.freeswitch.org">Freeswitch-users@lists.freeswitch.org</a><br> <a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br> UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br> <a href="http://www.freeswitch.org">http://www.freeswitch.org</a><br> <br> </blockquote> </blockquote> <blockquote type="CITE"> <br> <br> <br> -- <br> Anthony Minessale II<br> <br> FreeSWITCH <a href="http://www.freeswitch.org/">http://www.freeswitch.org/</a><br> ClueCon <a href="http://www.cluecon.com/">http://www.cluecon.com/</a><br> <br> AIM: anthm<br> <a href="mailto:MSN%3Aanthony_minessale@hotmail.com">MSN:anthony_minessale@hotmail.com</a><br> GTALK/JABBER/<a href="mailto:PAYPAL%3Aanthony.minessale@gmail.com">PAYPAL:anthony.minessale@gmail.com</a><br> IRC: <a href="http://irc.freenode.net">irc.freenode.net</a> #freeswitch<br> <br> FreeSWITCH Developer Conference<br> <a href="mailto:sip%3A888@conference.freeswitch.org">sip:888@conference.freeswitch.org</a><br> <a href="http://iax:guest@conference.freeswitch.org/888">iax:guest@conference.freeswitch.org/888</a><br> <a href="mailto:googletalk%3Aconf%2B888@conference.freeswitch.org">googletalk:conf+888@conference.freeswitch.org</a><br> pstn:213-799-1400 <pre>_______________________________________________
Freeswitch-users mailing list
<a href="mailto:Freeswitch-users@lists.freeswitch.org">Freeswitch-users@lists.freeswitch.org</a>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users">http://lists.freeswitch.org/mailman/options/freeswitch-users</a>
<a href="http://www.freeswitch.org">http://www.freeswitch.org</a>
</pre> </blockquote> </div> _______________________________________________<br>Freeswitch-users mailing list<br><a href="mailto:Freeswitch-users@lists.freeswitch.org">Freeswitch-users@lists.freeswitch.org</a><br>http://lists.freeswitch.org/mailman/listinfo/freeswitch-users<br>UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users<br>http://www.freeswitch.org<br></blockquote></div><br></div></body></html>