Queue Timeout

Home » Asterisk Users » Queue Timeout
Asterisk Users 1 Comment

Hello, We’re running asterisk 16 with Realtime.

We have queues configured in realtime.

The “Timeout” setting appears to have an upper 2 minute limit. Even when setting the timeout in the queue to 600 seconds, the agent is no longer rung after exactly 120 seconds. The asterisk CLI claims “Exiting due to time-out cycle”.

We are calling the queue with options “tin”. Removing “n” does keep the entire queue from exiting. But the agent is still stopped from ringing and then rung again after the announcements fire.

I have also tried dynamically passing a timeout (and not) when calling the queue from the dial plan.

IE. Queue(queuename,tin,,,600).

This does make the queue completely exit after 600 seconds. But does not cause the agent to just ring for 600 seconds straight.

We are answering the call in the dial plan first before entering the queue. So this is not an instance of the incoming call being canceled by some underlying carrier for being in the ring state > 60 seconds.

Any thoughts?

One thought on - Queue Timeout

  • Hi, To answer your questions.

    1. Not sure on statically configured queues. This is a production system that I can’t break down currently to test.
    2. Our member table has the following fields, uniqueid, member name, queue name, interface, penalty, paused. Which are 425, Nick Test Phone, nickactest, pjsip/ENDPOINTNAME, 1, null respectively.
    3. The relevant log bits
    1644245159|sip7-1644245037.26849|nickactest|Nick Test Phone|RINGNOANSWER|120000
    1644245159|sip7-1644245037.26849|nickactest|NONE|EXITWITHTIMEOUT|1|1|120

    I will mention that despite there not being a great way to query the timeout variable and see what asterisk really loaded from realtime (That I
    can find). If I set the timeout to something low, like 15 seconds. It does seem to respect it. So it appears it’s properly reading it. It just appears there is an upper limit.

    Strangely as well. My test queue I used to reproduce it terminates at 120
    seconds. The original queue that brought it to my attention terminates at
    60 seconds. Despite nothing being set to 120 or 60 seconds respectively.