Summary:ASTERISK-29796: app_queue: Invalid agents status on queues.
Reporter:Jose Miguel Rivera (jmiguel26@2016)Labels:
Date Opened:2021-12-08 11:00:27.000-0600Date Closed:2022-01-19 14:27:09.000-0600
Versions:18.8.0 Frequency of
duplicatesASTERISK-29806 app_queue: extension state incorrect
Environment:CentOS Linux release 7.9.2009Attachments:
Description:After updating Asterisk to version 18.8.0, the status of the agents started changing randomly. Available agents started showing it as In Use or Unavailable. Additionally, disconnecting agents or login out agents made others' status unavailable.

My first impression is that the issue is related to the fix in the link below because it is the only change on queues mentioned in this version.
Comments:By: Asterisk Team (asteriskteam) 2021-12-08 11:00:28.440-0600

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].

By: Joshua C. Colp (jcolp) 2021-12-08 11:04:40.124-0600

We require additional debug to continue with triage of your issue. Please follow [the instructions on the wiki|https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information] for how to collect debugging information from Asterisk. For expediency, where possible, attach the debug with a '.txt' file extension so that the debug will be usable for further analysis.


As well, the configuration is also needed.

By: Luke Escude (lukeescude) 2021-12-08 15:53:52.395-0600

I have been trying to track this down too in ASTERISK-29782

Our current "fix" is an hourly cron job to touch queues.conf and queue reload all, in order to keep the agent statuses correct.

By: Asterisk Team (asteriskteam) 2021-12-23 12:00:00.991-0600

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

By: Luke Escude (lukeescude) 2022-01-19 09:00:50.312-0600

Jose, try the patch located in Issue ASTERISK-29806 - This fixed all of our inconsistency issues with agent state and agent statistics.

By: Jose Miguel Rivera (jmiguel26@2016) 2022-01-19 14:21:07.644-0600

Luke, thanks for the info. I will try the patch.

By: Asterisk Team (asteriskteam) 2022-01-19 14:21:07.956-0600

This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable.

By: Jose Miguel Rivera (jmiguel26@2016) 2022-01-19 14:27:09.947-0600

It seems the fix for this issue will be available on Asterisk 18.10.0.