[asterisk-bugs] [JIRA] (ASTERISK-25442) using realtime queue agents do not be updated if there are changes in DB

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-25442:
------------------------------------------

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.

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].

> using realtime queue agents do not be updated if there are changes in DB
> ------------------------------------------------------------------------
>
>                 Key: ASTERISK-25442
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25442
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_queue
>    Affects Versions: 1.8.25.0, 13.4.0
>         Environment: Debian 7.9
>            Reporter: Carlos Oliva
>            Severity: Minor
>
> using realtime (mysql) queue members are never updated  in wait_our_turn function (app_queue.c) 
> Asterisk never refreshes queue members from db until another event occurs (for example a new call joins the queue or a queue show is executed in cli)
> This issue causes that if a call enters the queue and a new queue member is inserted in database after it, this member never will receive the call until new call joins the queue



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