[asterisk-bugs] [JIRA] (ASTERISK-22546) Despite persistentmembers=yes, various queue member attributes set with AMI actions or QUEUE_MEMBER function are not stored in ASTDB

[Joshua Colp (JIRA)]

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

Joshua Colp updated ASTERISK-22546:
-----------------------------------

    Affects Version/s: 13.18.4

> Despite persistentmembers=yes, various queue member attributes set with AMI actions or QUEUE_MEMBER function are not stored in ASTDB
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-22546
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22546
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_queue, Core/ManagerInterface
>    Affects Versions: SVN, 11.2.1, 11.5.1, 13.18.4
>         Environment: Debian 6.0.4
>            Reporter: Chano Klinck Andersen
>         Attachments: queue_member_test.txt
>
>
> When a queue has persistent members, and the penalty is changed through the manager interface, the new penalty is not saved to the asterisk database.
> When asterisk is restarted the penalties are lost.
> Steps to recreate:
> * Enable the asterisk manager interface in manager.conf
> * Create one or more queues in queues.conf
> * Add one or more agents to the queue, either via manager or a dialplan function
> * Use the manager interface to change the penalty. (In my case I use the http interface.
> * Restart Asterisk
> After the restart the queue should have been exactly as before the restart, however, after the restart the penalties are lost, and have to be set again.
> Browsing through the source code reveals that dump_queue_members are never called when the penalties (Or ringinuse) are changed through manager.
> I am not using the QUEUE_MEMBER dialplan function to change the penalties, so I do not know if that is affected too.



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