[asterisk-bugs] [JIRA] (ASTERISK-17049) [patch]Setting linear queue strategy requires asterisk restart

[Sean Bright (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-17049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Bright updated ASTERISK-17049:
-----------------------------------

    Description: 
According to app_queue.c sources, this message occurs only for realtime. And, actually, one can't see this message if queue strategy was changed in queues.conf. 
But, after altering queues config file and invoking either "config reload /etc/asterisk/queues.conf" or "queues reload all", members order in queue is not the same as in .conf file, and incoming calls are routed to queue members also in wrong order.
PS If used strategy is set to "linear" and asterisk is restarted, order of members in queue and config file is the same, and the bug doesn't reproduce. 

Of course, adding a message "Please, restart asterisk" for static configuration reload wouldn't be a best solution. I'd prefer not to restart asterisk at all.

  was:
Currently (also in 1.8.0): "Changing to the linear strategy currently requires asterisk to be restarted."

Though it can be proudly represented as a "feature, not a bug", I don't think this behaviour is suitable for 24/7 systems where users can often change their settings. In this case asterisk restart would hangup all active calls, which is a BAD THING. (This part is more like a feature request, and the bug goes below)

So, here goes the bug:
According to app_queue.c sources, this message occurs only for realtime. And, actually, one can't see this message if queue strategy was changed in queues.conf. 
But, after altering queues config file and invoking either "config reload /etc/asterisk/queues.conf" or "queues reload all", members order in queue is not the same as in .conf file, and incoming calls are routed to queue members also in wrong order.
PS If used strategy is set to "linear" and asterisk is restarted, order of members in queue and config file is the same, and the bug doesn't reproduce. 

Of course, adding a message "Please, restart asterisk" for static configuration reload wouldn't be a best solution. I'd prefer not to restart asterisk at all.


> [patch]Setting linear queue strategy requires asterisk restart
> --------------------------------------------------------------
>
>                 Key: ASTERISK-17049
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-17049
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Applications/app_queue
>    Affects Versions: 1.8.4, 13.18.4
>            Reporter: Vadim Mikhnevych
>              Labels: patch
>         Attachments: app_queue_linear_v2.patch, linear_rrordered_update_11.21.patch, linear_update_11.5.patch
>
>
> According to app_queue.c sources, this message occurs only for realtime. And, actually, one can't see this message if queue strategy was changed in queues.conf. 
> But, after altering queues config file and invoking either "config reload /etc/asterisk/queues.conf" or "queues reload all", members order in queue is not the same as in .conf file, and incoming calls are routed to queue members also in wrong order.
> PS If used strategy is set to "linear" and asterisk is restarted, order of members in queue and config file is the same, and the bug doesn't reproduce. 
> Of course, adding a message "Please, restart asterisk" for static configuration reload wouldn't be a best solution. I'd prefer not to restart asterisk at all.



--
This message was sent by Atlassian JIRA
(v6.2#6252)