Yes, that's what we are doing.<br><br><div class="gmail_quote">2009/11/24 Brian West <span dir="ltr"><<a href="mailto:brian@freeswitch.org">brian@freeswitch.org</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
You do realize that the whole concept is OLD skewl. You should be<br>
popping this info via external resources when the agent is bridged to<br>
the caller and the info is there before they are done saying "thanks<br>
for calling spacely sprockets, this is George how may I help you .... "<br>
<font color="#888888"><br>
/b<br>
</font><div class="im"><br>
<br>
On Nov 23, 2009, at 7:07 PM, Michael Collins wrote:<br>
<br>
> Tony and Brian were discussing this today. They bring up a really<br>
> good point: do you want to risk having calls remain on hold as they<br>
> bounce around looking for an agent? This can happen if you pre-<br>
> determine which caller goes to which agent and the agent doesn't<br>
> answer. I do understand why this feature matters to many people -<br>
> it's how old school ACD systems work. However, mod_fifo is more<br>
> efficient. It's hard to justify decreasing call routing efficiency<br>
> in order to display the caller's info to the on-hook agent prior to<br>
> answering.<br>
><br>
> -MC<br>
<br>
<br>
</div><div><div></div><div class="h5">_______________________________________________<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" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</div></div></blockquote></div><br>