[asterisk-bugs] [JIRA] (ASTERISK-28369) app_queue: Unable to join queue (only on third call when second is ringing)

[Boolah (JIRA)]

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

Boolah  edited comment on ASTERISK-28369 at 4/8/19 9:05 AM:
------------------------------------------------------------

1.  Steps to reproduce the problem:  Have an agent (1305) logged into a queue (500) talking on an active call (1307).  A second call comes in (1306) and begins ringing the queue.  While this call is ringing the queue, a third call attempts to ring the queue (1300), but is not allowed to join the queue and this call goes to the queue fail over destination.
2.  Expected behavior:  As documented in queues.conf, since ringinuse=yes and joinempty=strict, as long as at least one agent is logged into the queue and the agent is reachable (not necessarily available, but simply reachable), any number of calls should be allowed to join the queue.  Moreover, setting joinempty to invalid OR unavailable OR unknown all yield the same result.
3.  Behavior encountered: The third call attempting to join a queue with a single agent who is talking on an active call (inuse), will not be allowed to join the queue if a second call is actively ringing the queue.

The requested debug log is now attached.


was (Author: boolah at mailvoid.net):
1.  Steps to reproduce the problem:  Have an agent (1305) logged into a queue (500) talking on an active call (1307).  A second call comes in (1306) and begins ringing the queue.  While this call is ringing the queue, a third call attempts to ring the queue (1300), but is not allowed to join the queue and this call goes to the queue fail over destination.
2.  Expected behavior:  As documented in queues.conf, since ringinuse=yes and joinempty=strict, as long as at least one agent is logged into the queue and the agent is reachable (not necessarily available, but simply reachable), any number of calls should be allowed to join the queue.
3.  Behavior encountered: The third call attempting to join a queue with a single agent who is talking on an active call (inuse), will not be allowed to join the queue if a second call is actively ringing the queue.

The requested debug log is now attached.

> app_queue: Unable to join queue (only on third call when second is ringing)
> ---------------------------------------------------------------------------
>
>                 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, 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)