[Freeswitch-users] Questions about mod_fifo

[Seven Du]

from the log you can see that it routed to eavesdrop 779 but not
fifo_in 779 as you expected. In other words, either there are two 779
entries in your dialplan or your fifo_in 779 dialplan not been loaded
into freeswitch. Did you run reloadxml after you edited the dialplan
file?

2010/1/18 Jingwei Yang <jingwei.yang at gmail.com>:
> Yes, I'm able to see the inbound channel created:
>
> freeswitch at localhost.localdomain> show channels
> API CALL [show(channels)] output:
> uuid,direction,created,created_epoch,name,state,cid_name,cid_num,ip_addr,dest,application,application_data,dialplan,context,read_codec,read_rate,write_codec,write_rate,secure,hostname,presence_id,presence_data
> 6d347eaa-aea8-47e3-b915-8cfdf0f8fd9c,inbound,2010-01-19
> 17:04:22,1263891862,skypiax/interface5,CS_EXECUTE,Jingwei,jingwei.yang,,779,eavesdrop,all,XML,default,L16,16000,L16,16000,,localhost.localdomain,,
>
> Hmmm, may I know how you could tell it's a dialplan problem?
>
> Regards,
> -Jingwei
>
> On Mon, Jan 18, 2010 at 3:25 PM, Seven Du <dujinfang at gmail.com> wrote:
>>
>> did you happened to run "show channels" ?
>>
>> clearly it's a dialplan problem other than a fifo one.
>>
>>
>> Dialplan: skypiax/interface8 Regex (PASS) [eavesdrop]
>> destination_number(779) =~ /^779$/ break=on-false
>> Dialplan: skypiax/interface8 Action answer()
>> Dialplan: skypiax/interface8 Action
>> set(eavesdrop_indicate_failed=tone_stream://%(500, 0, 320))
>> Dialplan: skypiax/interface8 Action
>> set(eavesdrop_indicate_new=tone_stream://%(500, 0, 620))
>> Dialplan: skypiax/interface8 Action
>> set(eavesdrop_indicate_idle=tone_stream://%(250, 0, 920))
>> Dialplan: skypiax/interface8 Action eavesdrop(all)
>>
>>
>>
>> 2010/1/18 Jingwei Yang <jingwei.yang at gmail.com>:
>> > Logs submitted: http://pastebin.freeswitch.org/11836
>> >
>> > I was trying to check whether the call had been added into the queue via
>> > telnet, but failed to find the fifo events. Here's my simplified
>> > dialplan:
>> >
>> > <extension name="in_fifo">
>> >    <condition field="destination_number" expression="^779$">
>> >      <action application="answer"/>
>> >      <action application="fifo" data="myq in undef undef"/>
>> >   </condition>
>> > </extension>
>> >
>> > Please advise where went wrong.
>> >
>> > Thanks and best regards,
>> > -Jingwei
>> >
>> >
>> > On Mon, Jan 18, 2010 at 11:42 AM, Seven Du <dujinfang at gmail.com> wrote:
>> >>
>> >> better to pastebin your log.
>> >>
>> >> 2010/1/18 Jingwei Yang <jingwei.yang at gmail.com>:
>> >> > Thanks for replying. This is my dialplan
>> >> >
>> >> >     <extension name="in_fifo">
>> >> >       <condition field="destination_number" expression="^779$">
>> >> >         <action application="set" data="fifo_music=$${hold_music}"/>
>> >> >         <action application="answer"/>
>> >> >         <action application="fifo" data="myq in undef undef"/>
>> >> >       </condition>
>> >> >     </extension>
>> >> >
>> >> > And I created a queue in fifo.conf.xml like this
>> >> >
>> >> >     <fifo name="myq" importance="0">
>> >> >       <!--<member timeout="60" simo="1"
>> >> > lag="20">{member_wait=nowait}user/1005@$${domain}</member>-->
>> >> >     </fifo>
>> >> >
>> >> > However, I'm still not able to see the incoming call get queued.
>> >> >
>> >> > freeswitch at localhost.localdomain> fifo list myq
>> >> > API CALL [fifo(list myq)] output:
>> >> > <fifo_report>
>> >> >   <fifo name="myq" consumer_count="0" caller_count="0"
>> >> > waiting_count="0"
>> >> > importance="0">
>> >> >     <callers></callers>
>> >> >     <consumers></consumers>
>> >> >   </fifo>
>> >> > </fifo_report>
>> >> >
>> >> > I tried both mod_skypiax and mod_dingaling, but with the same result.
>> >> >
>> >> > Regards,
>> >> > -Jingwei
>> >> >
>> >> > On Sun, Jan 17, 2010 at 11:37 AM, Seven Du <dujinfang at gmail.com>
>> >> > wrote:
>> >> >>
>> >> >> 2010/1/15, Jingwei Yang <jingwei.yang at gmail.com>:
>> >> >> > Hi Guys,
>> >> >> >
>> >> >> > I'm implementing an ACD system using ESL and mod_fifo. Based on
>> >> >> > what
>> >> >> > Anthony
>> >> >> > suggested in this post:
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > http://www.mail-archive.com/freeswitch-users@lists.freeswitch.org/msg01652.html
>> >> >> >
>> >> >> > *You can make an event socket application that listens for FIFO
>> >> >> > events
>> >> >> > and
>> >> >> > keeps track of what FIFOs are currently busy and when there are
>> >> >> > people
>> >> >> > waiting you can have that script generate a call to a group of SIP
>> >> >> > phones so
>> >> >> > when the first one answers, it sends them in as an agent where
>> >> >> > they
>> >> >> > can
>> >> >> > field the calls.
>> >> >> > *
>> >> >> >
>> >> >> > 1. How should I handle the concurrent issues? If I bridge a user
>> >> >> > to
>> >> >> > two
>> >> >> > agents and both of them answers, how does FS take care of this
>> >> >> > situation?
>> >> >> > Will a slower agent get a busy tone automatically?
>> >> >> >
>> >> >>
>> >> >> I think it just follow the standard originate dialstring rules.
>> >> >>
>> >> >> > 2. If the socket application is brought up after some users have
>> >> >> > called
>> >> >> > in,
>> >> >> > what command should I use to check the busy queues? fifo list?
>> >> >> >
>> >> >> Yes. Perhaps you can also check the fifo db, either sqlite or ODBC.
>> >> >>
>> >> >> > 3. Am I using fifo list and fifo count correctly?
>> >> >> >
>> >> >> > here's the testing dialplan:
>> >> >> >
>> >> >> >     <extension name="in_fifo">
>> >> >> >       <condition field="destination_number" expression="^779$">
>> >> >> >         <action application="set"
>> >> >> > data="fifo_music=$${hold_music}"/>
>> >> >> >         <action application="answer"/>
>> >> >> >         <action application="fifo" data="*myq *in"/>
>> >> >> >       </condition>
>> >> >> >     </extension>
>> >> >> >
>> >> >> > when a call comes in and gets queued, these are the results of
>> >> >> > some
>> >> >> > commands
>> >> >> > I tried.
>> >> >> >
>> >> >> > freeswitch at localhost.localdomain> fifo list
>> >> >> > API CALL [fifo(list)] output:
>> >> >> > <fifo_report>
>> >> >> >   <fifo name="cool_fifo at 192.168.1.104" consumer_count="0"
>> >> >> > caller_count="0"
>> >> >> > waiting_count="0" importance="0">
>> >> >> >     <callers></callers>
>> >> >> >     <consumers></consumers>
>> >> >> >   </fifo>
>> >> >> > </fifo_report>
>> >> >> >
>> >> >> >
>> >> >> > freeswitch at localhost.localdomain> fifo list myq
>> >> >> > API CALL [fifo(list myq)] output:
>> >> >> > <fifo_report></fifo_report>
>> >> >> >
>> >> >> >
>> >> >> > freeswitch at localhost.localdomain> fifo count myq
>> >> >> > API CALL [fifo(count myq)] output:
>> >> >> > none
>> >> >> >
>> >> >> > It seems *myq* doesn't get created at all? Please enlighten.
>> >> >> >
>> >> >> > Thanks and best regards,
>> >> >> > -Jingwei
>> >> >> >
>> >> >> AFAIK, thant means the channel didn't queued in. Did you see any
>> >> >> error
>> >> >> logs? I think you need to remove the stars in   <action
>> >> >> application="fifo" data="*myq *in"/>.
>> >> >>
>> >> >> _______________________________________________
>> >> >> FreeSWITCH-users mailing list
>> >> >> FreeSWITCH-users at lists.freeswitch.org
>> >> >> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>> >> >>
>> >> >>
>> >> >> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
>> >> >> http://www.freeswitch.org
>> >> >
>> >> >
>> >> > _______________________________________________
>> >> > FreeSWITCH-users mailing list
>> >> > FreeSWITCH-users at lists.freeswitch.org
>> >> > http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>> >> >
>> >> > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
>> >> > http://www.freeswitch.org
>> >> >
>> >> >
>> >>
>> >> _______________________________________________
>> >> FreeSWITCH-users mailing list
>> >> FreeSWITCH-users at lists.freeswitch.org
>> >> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>> >>
>> >> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
>> >> http://www.freeswitch.org
>> >
>> >
>> > _______________________________________________
>> > FreeSWITCH-users mailing list
>> > FreeSWITCH-users at lists.freeswitch.org
>> > http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>> > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
>> > http://www.freeswitch.org
>> >
>> >
>>
>> _______________________________________________
>> FreeSWITCH-users mailing list
>> FreeSWITCH-users at lists.freeswitch.org
>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
>> http://www.freeswitch.org
>
>
> _______________________________________________
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
>
>