you could use the intercept app to unpark the caller without using fifo out, then it would only work if the caller existed.<br><br><br><div class="gmail_quote">On Tue, Feb 3, 2009 at 7:51 AM, Tamas Cseke <span dir="ltr"><<a href="mailto:cstomi.levlist@gmail.com">cstomi.levlist@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hello,<br>
<br>
We have a problem with mod_fifo.<br>
<br>
we monitor fifo push event on event socket,<br>
call consumer with originate & fifo out nowait<br>
Similar like fifo_outbound works, but we have an external strategy for<br>
consumer selection (eg.: skill-based routing)<br>
<br>
The problem is when a caller stops waiting in fifo, the originated calls<br>
kepp ringing the consumer, and when the consumer answer the call,<br>
he or she may grab somebody else from the fifo, which is a problem<br>
because the callers are identified and some data (eg name, phonenumber<br>
is shown for the consumer).<br>
so it can happen these data will be wrong.<br>
<br>
We tried to resolve this issue by a call tracking in the external script<br>
using event socket.<br>
we pushes a variable into the CHANNEL_ORIGINATE event calling the<br>
consumer containing the caller uuid.<br>
and if the caller aborts the fifo, we hangup the consumer call with<br>
(uuid_kill)<br>
But it's not prefect becasue it can happen that the consumer pop another<br>
caller from the fifo.<br>
and we hangup this call, so as a side-effect we loosing another caller.<br>
<br>
Could anybody advise a solution for this please?<br>
we thinking about to have a fifo_caller_uuid variable, that we set<br>
before calling fifo with the out method.<br>
and if this uuid is in the top of the fifo then pop it else don't pop<br>
anybody.<br>
it seems to be a hack anyway....<br>
<br>
Thanks in advance,<br>
Tamas<br>
<br>
<br>
<br>
<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" 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>
</blockquote></div><br><br clear="all"><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<br>