[asterisk-bugs] [JIRA] (ASTERISK-22589) shared_lastcall is not reliable with realtime queues

[Rusty Newton (JIRA)]

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

Rusty Newton commented on ASTERISK-22589:
-----------------------------------------

That is fine. My intent was that the patch may help others who look into the issue. It is not intended for commit to source, so you marked it correctly. Thanks!
                
> shared_lastcall is not reliable with realtime queues
> ----------------------------------------------------
>
>                 Key: ASTERISK-22589
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22589
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_queue, Resources/res_realtime
>    Affects Versions: 1.8.23.0
>         Environment: Debian Squeeze 64-bit
>            Reporter: hristo
>            Severity: Minor
>         Attachments: app_queue-debug-shared_lastcall.diff
>
>
> I have the following setup:
> - queues and queue_members are both realtime 
> - 2 queues: Q1 with wrapuptime=60; Q2 without wrapuptime
> - 1 agent, who is in both queues
> - shared_lastcall is set to 'yes'
> The problem is that shared_lastcall doesn't have any effect unless both realtime queues are already cached by asterisk. As a result the agent sometimes receives calls from Q2 during the 'wrapuptime' period of Q1.
> I did find several tickets that describe similar problems, but none of them mentions realtime, that's why I am opening a new one.
> I have managed to track the problem by adding a debug message for every time the app_queue iterates over the queues to find the agent and update his last call time. The iteration only seems to be finding *cached* realtime queues, which in turn is causing the problem I have described above.

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