[asterisk-bugs] [JIRA] (ASTERISK-28369) app_queue: Member device state "invalid" when second call is ringing and hint is used

[Joshua C. Colp (JIRA)]

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

Joshua C. Colp updated ASTERISK-28369:
--------------------------------------

    Summary: app_queue: Member device state "invalid" when second call is ringing and hint is used  (was: app_queue: Unable to join queue (only on third call when second is ringing))

> app_queue: Member device state "invalid" when second call is ringing and hint is used
> -------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-28369
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28369
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_queue
>    Affects Versions: 13.25.0
>         Environment: CentOS v7.6.1810
>            Reporter: Boolah 
>            Assignee: Unassigned
>         Attachments: debug_log_28369, extensions.conf, queues.conf
>
>
> In a queue with a single agent who is on an active call and ringinuse=yes is set, if a second call begins ringing the queue, but before the call is answered, the next call will not be allowed to join the queue, irrespective of the joinempty setting.
> I've posted this issue in the community and can be found here: https://community.asterisk.org/t/unable-to-join-queue-only-on-third-call-when-second-is-ringing/79161
> I've also verified that the issue exists in Asterisk version 13.23.1, 13.25.0 and 13.26.0-rc1



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