Summary:	ASTERISK-29620: Changing queue strategy to Linear does not order agents properly
Reporter:	Luke Escude (lukeescude)	Labels:
Date Opened:	2021-08-27 16:58:51	Date Closed:	2021-09-14 12:00:05
Priority:	Minor	Regression?
Status:	Closed/Complete	Components:	Applications/app_queue
Versions:	16.20.0	Frequency of Occurrence	Constant
Related Issues:
Environment:		Attachments:
Description:	Hello! To recreate this bug, set up a queue of "ringall" strategy with some agents in it. Let's say 101, 102, 103 Then, change the strategy from "ringall" to "linear" and change your members around to a different order (say 103, 101, 102). Issue a core reload, and the strategy will change, but the linear queue order will not. The only way to get it to work is to restart asterisk. The following potential solutions do NOT work: 1. 'core reload' a bunch of times 2. touch queues.conf & core reload 3. module reload app_queue So, restarting Asterisk is the only way to get Linear queue ordering working on a queue that was previously non-linear.
Comments:	By: Asterisk Team (asteriskteam) 2021-08-27 16:58:53.964-0500 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: Luke Escude (lukeescude) 2021-08-27 17:00:31.898-0500 Forgot to mention, we are NOT using realtime. Just good old fashioned conf files. That's why I figured a new issue may be required (since this is similar to a realtime-related issue already filed) By: Benjamin Keith Ford (bford) 2021-08-30 07:14:58.809-0500 Just to clarify, are you changing the strategy and order in queues.conf, then doing a core reload? By: Luke Escude (lukeescude) 2021-08-30 09:50:57.856-0500 Correct - You can change the strategy without changing the order, or you can do both, and no matter what it will never honor any order changes after the strategy change (unless you restart Asterisk) By: Benjamin Keith Ford (bford) 2021-08-30 13:24:13.912-0500 It looks like this may be a duplicate of ASTERISK-17049 - can you try the patch listed there and see if it resolves the issue? By: Asterisk Team (asteriskteam) 2021-09-14 12:00:05.300-0500 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