Hello, I'v found the right command to use. originate {fifo_bridge_uuid=THE_UUID_OF_QUEUED_CHANNEL,sip_auto_answer=true,origination_caller_id_number=CALLING_NUMBER}user/AGENT_EXTENSION &fifo('myqueue@mydomain.org out nowait undef undef') In such a way the operator receive a second call and then (at answer) the desired queued call get pulled out from the fifo queue. In my application I use uuid_kill to cut the other ringing call for that operator, so he see only one call. The only thing I have to fix is the auto respond of the originated call. My CISCO 8811 refuse to auto answer only a specific call. I used any sort of parameters such - answer-time=0 - intercom=1 - sip_h_Call-info=\;answer-after=0 - sip_h_Alert-Info: <http://www.notused.com>;info=alert-autoanswer;delay=0 but none seems to work. Any suggestions? Il giorno gio 13 giu 2019 alle ore 15:44 Marco Foschian <marco.foschian@gmail.com> ha scritto:

Hello,

I'm writing a node.js / esl monitor for a fifo queue that show on a web page the incoming calls and their status (waiting, answered, ringing, etc).

The page is used by some operators with a phone registered as member of the queue: they can see who is calling (the number is decoded in a caller-name by the application) before answering the call.

Is there a way for the user of the webpage to choose the ringing call to pick-up instead of the oldest one ? When the operator click on the page there is an HTTP call to the node.js server where I have the esl connection and the info of each channel involved in the queue.

I already tried some uuid_bridge commands, or "fifo myqueue out nowait" and uuid_setvar fifo_bridge_uuid combinations, but none works.

It's possible to implement such a feature with mod_fifo ? There is any alternative ?

Best regards, Marco Foschian