Queue automatic voice is not correct works


Queue voice about number of positions works only after (After the timeout of the first call, when the queue is sort of restarted.)

Connected to Asterisk 18.5.0 currently running on s353 (pid = 125752)
– Accepting AUTHENTICATED call from
– > requested format = alaw,
– > requested prefs = (alaw),
– > actual format = alaw,
– > host prefs = (alaw),
– > priority = mine
– Executing [2057@office:1] Goto(“IAX2/pbxtors0061-2674”, “test4admins,s,1”) in new stack
– Goto (test4admins,s,1)
– Executing [s@test4admins:1] Answer(“IAX2/pbxtors0061-2674”, “”) in new stack
– Executing [s@test4admins:2] Set(“IAX2/pbxtors0061-2674”, “CHANNEL(language)=en”) in new stack
– Executing [s@test4admins:3] Wait(“IAX2/pbxtors0061-2674”, “2”) in new stack
– Executing [s@test4admins:4] GotoIfTime(“IAX2/pbxtors0061-2674”, “10:00-20:00|mon-fri||?test4admins,s,201”) in new stack
– Goto (test4admins,s,201)
– Executing [s@test4admins:201] BackGround(“IAX2/pbxtors0061-2674”, “Welcome”) in new stack
– <IAX2/pbxtors0061-2674> Playing ‘Welcome.alaw’ (language ‘en’)
– Executing [s@test4admins:202] Wait(“IAX2/pbxtors0061-2674”, “2”) in new stack
– Executing [s@test4admins:203] Queue(“IAX2/pbxtors0061-2674”, “test4admins,t,300”) in new stack
– Started music on hold, class ‘default’, on channel ‘IAX2/pbxtors0061-2674’
– Called Local/2830@office
– Executing [2830@office:1] Dial(“Local/2830@office-000006d3;2”, “SIP/2830”) in new stack
== Using SIP VIDEO CoS mark 6
== Using SIP RTP CoS mark 5
– Called SIP/2830
– Local/2830@office-000006d3;1 connected line has changed. Saving it until answer for IAX2/pbxtors0061-2674
– SIP/2830-000057e5 is ringing
– Local/2830@office-000006d3;1 is ringing

== Everyone is busy/congested at this time (1:0/0/1)
– Timeout on Local/2830@office-000006d3;2
– Executing [t@office:1] Congestion(“Local/2830@office-000006d3;2”, “1”) in new stack

– Local/2830@office-000006d3;1 is circuit-busy
– Nobody picked up in 69000 ms
== Spawn extension (office, t, 1) exited non-zero on ‘Local/2830@office-000006d3;2’
– Stopped music on hold on IAX2/pbxtors0061-2674
!!! – Playing periodic announcement
– <IAX2/pbxtors0061-2674> Playing ‘queue-periodic-announce.alaw’ (language ‘en’)
– Started music on hold, class ‘default’, on channel ‘IAX2/pbxtors0061-2674’

Why? How to fix it?
exten => s,1,Answer()
exten => s,n,Set(CHANNEL(language)=en)
exten => s,n,Wait(2)
exten => s,n,Queue(test4admins,t,300)

name test4admins
context test4admins
timeout 120
strategy ringall
periodic-announce queue-periodic-announce
periodic-announce-frequency 10

Maintain a “state interface” for each agent, so that the queue application knows that no-one is actually available. Asterisk cannot play announcements and ring agents at the same time, and it seems fairly sensible that it should try to ring an agent that appears to be free, rather than wasting time announcing that you are at the head of the queue, and possibly losing its place in the process.

It won’t try to call anyone in the retry interval, so it can afford to make an announcement, then.

This may be tricky here, as you are getting a, presumably delayed, unavailable, not a busy, so you are, presumably, not dealing with a local device, so you can’t tell the status of the underlying device.

69 seconds is a very long timeout for a queue calling round. Asterisk cannot add in agents that come free until the end of this period.

Incidentally, please don’t screen scrapes; use the full log, as it contains time stamps, and timing is significant here. Also please mark logs up as pre-formatted text, for the forum.

I use realtime peers with mysql. It’s possible ?

Maybe you can give advices for me?

The queue system assumes that agents will answer quickly if they are available, and will pause themselves or log out, if they are not.

In any case, I can’t see how a caller is going to be happy being told, effectively, that they can be answered immediately, then finding that they are stuck on ringing for over a minute, so I don’t see how it helps to announce their position at the start.

Thanks for your reply. But it sounds like an excuse, but in reality you just don’t know. It’s not about position, per se. This happens with any message.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.