SOLVED: Changing queue behavior : does the Queue script need to Answer() the call?

Not sure if this warrants a new topic,
but currently I configured my flow like this:

incoming trunk/route -> ring group

ring group (normal) -> extensions (ringall)
ring group (failover) -> queue

queue (normal) -> extensions (ringall)
queue (failover)-> terminate/busy

This is to catch the situation, when more than 1 incoming call ring()s at the same time (ring group, by the users/operators/office preference MUST use ringall strategy… ) - the call that starts to ring() slightly later was, without the queue, just terminated/busy, which was annoying.

And with queue, it works - the waiting call is picked up and rings all remaining phones when the first , no more no less;

The queue is very basic (10s timeout, no MOH - just ring) - but, the Answer() in the queue script means my PBX answers the queued call just to place it on the queue and play it a ringing signal… be it for short period but still, this will incur charges on the caller.

TL;dr: will the queue script as found in extensions_additional.conf still function properly if the Answer() is just removed ? (i would know where to put it, I read Just being weary of copying entire queue extension context over…

1 Like

Looks like, it doesn’t have to Answer():

in Advanced Settings, set “Hide Queue No Answer Option” to False - default is TRUE.

1 Like