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

Yury Kirsanov (JIRA) noreply at issues.asterisk.org
Sun Mar 21 14:36:16 CDT 2021


    [ https://issues.asterisk.org/jira/browse/ASTERISK-17049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=254261#comment-254261 ] 

Yury Kirsanov commented on ASTERISK-17049:
------------------------------------------

This far patch works fine for us, when we do changes to configuration files they're reflected in the actual queue. Notices from this patch are a bit confusing as they're saying 'Moving DYNAMIC members of the queue' while we're using only static members, like SIP devices, not Agents who can log in/out to/from the queue. Also we're still testing this as usually for some reason this incorrect behaviour was appearing not immediately after restart but a week or even more later. Asterisk used is 16.15.0. Thanks.

> [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)



More information about the asterisk-bugs mailing list