[asterisk-bugs] [JIRA] (ASTERISK-23378) [patch]Queue with 'ringinuse=no' and members in realtime can get several calls at the same time (with patch)

[Rusty Newton (JIRA)]

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

Rusty Newton closed ASTERISK-23378.
-----------------------------------

    Resolution: Duplicate
    
> [patch]Queue with 'ringinuse=no' and members in realtime can get several calls at the same time (with patch)
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-23378
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23378
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_queue
>    Affects Versions: 1.8.23.0, 11.6.0
>         Environment: Debian 7 64 bit (11), Centos 5.8 (1.8) 64 bit
>            Reporter: Shlomi Gutman
>         Attachments: app_queue.c.patch
>
>
> We have queue with realtime config on both 1.8 and 11 (including 11.6-cert1) versions.
> As well we have queue members and sip devices in realtime. 
> Scenario is:
> Q with realtime members (local sip devices with config in realtime as well).
> Set the timeout of Q to small number ( 5-10s) so it would be easier to reproduce.
> Have 1 member in Q with ringinuse=no, call him and start talking to him.
> Call second time and it would work as expected - in other words the agent would not have waiting call . 
> Now call again and run "sip reload" in CLI a lot of times(so it would be in perfect timing of sip not being reachable after sip reload and before it checks if it should call the sip) till at some point it would ring the same talking agent and you'll have waiting call.
> Afaik  It would be displayed as (not in use) at some point if you run queue show $QUEUE_NAME
> The solution was to add new check if agent is realtime - i would check if there is channel that device is involved with. But the tricky thing is to only check if it has channel and set to inuse and do not change status if there is no channel ( so we would not get not in use in case the sip device is unavailable)
> The patch i'm applying is for 11.6-cert1 but it was copied from 1.8.23 which is now more than month in production and customers we have there told that issue was resolved.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira