Queue agent availability status


We upgraded to vitalpbx 3.1.4 and it looks like it broke the way queues are monitoring the device state. So as you can see below I have a queue with 2 agents logged in, I placed a call from on extension, and in the queue it shows that the extension that placed the call is not in use, and the other agent which is actually available, it shows as in use. What’s more interesting is that the issue is not consistent (and therefor hard to reproduce), sometimes it will show both agents in use, sometimes only one but the wrong one, and sometimes it will work as expected.


Tested with SIP and PJSIP, tested on a newly created queue with new extensions, reinstalled vitalpbx and asterisk, but nothing seems to help.

I Even tried to manually add the members to the queue from the CLI and set the state interface to directly monitor the PJSIP device, but had the same issue.


I do see that asterisk made some changes to the way queues are monitoring hints in version 18.8.0 the question is if that fix perhaps broke something, does anyone here have similar issues?

Thank you.


Nice find. Can not tell you if it happens here. Not been able to check yet.
Will “Ring Busy Agents” set to YES help a little till this is fixed?

1 Like

Thank you both! This is happening on our side too, on v3.1.4 and Ring Busy Agents set to YES does indeed seem to make a big difference.

Please see 3.1.4 R2:

Downgrade asterisk with this command:

yum downgrade asterisk asterisk-paging asterisk-dpma asterisk-core asterisk-voicemail asterisk-pjsip asterisk-doc asterisk-curl asterisk-odbc asterisk-dahdi -y

Can you please help here?


Unfortunately I don’t have 3.1.4-1 and asterisk 18.8 installed, and I can’t downgrade vital / upgrade asterisk because asterisk 18.8 has been removed from vitals repo

It seems there’s a patch for this issue. The official fix will come on Asterisk 18.10.0.


Though my problem was a little different, your solution worked for me.

I created WebRTC extensions(and registered them in my Odoo VoIP integration) and it could only make outgoing calls. Any attempt to call the number said “the extension is unavailable, please try again later”.

Once I ran this command and rebooted my server, everything started working!

I think this is a bug that needs to be fixed.

Thanks for sharing