[asterisk-bugs] [JIRA] (ASTERISK-26400) app_queue: Queue member stops being called after AMI "Redirect" action for queues with wrapuptime

[David Brillert (JIRA)]

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

David Brillert edited comment on ASTERISK-26400 at 1/31/17 1:02 PM:
--------------------------------------------------------------------

IMHO the commit at ASTERISK-19820 needs to be reverted until the original problem reported there can be fixed properly and thoroughly tested.  That change undermines all the work that went into state_interface

This logic does not make sense, since any parking or transfer done by the queue member will result in the (in call) flag being set.

2015-12-29 05:44 +0000 [1943cfc53c] Martin Tomec <tomec.martin at gmail.com>

    app_queue: Add member flag "in_call" to prevent reading wrong lastcall time

Member lastcall time is updated later than member status. There was chance to
check wrapuptime for available member with wrong (old) lastcall time.
New boolean flag "in_call" is set to true right before connecting call, and
reset to false after update of lastcall time. Members with "in_call" set to true
are treat as unavailable.


was (Author: aragon):
IMHO the commit at ASTERISK-19820 needs to be reverted until the original problem reported there can be fixed properly and thoroughly tested.  That change undermines all the work that went into state_interface

> app_queue: Queue member stops being called after AMI "Redirect" action for queues with wrapuptime
> -------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-26400
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26400
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_queue
>    Affects Versions: 13.11.2
>            Reporter: Etienne Lessard
>
> Hello,
> Given I have a queue with a *nonzero wrapuptime* and one queue member
> And Alice calls this queue
> And the queue member answers
> When an AMI "Redirect" redirects Alice's channel to a different extension
> Then the queue member won't receive any new call from the queue until Alice's channel is hung up
> Note that after the AMI Redirect, the queue member is available / not in use, but won't receive any new call because the queue still think it's "in call", as shown by the "queue show" command.
> This is especially noticeable if your queue member is member of many queues (all with wrapup) and you have "shared_lastcall = yes" in your queues.conf.
> Also, if you find yourself in a scenario similar to the one described in ASTERISK-25844, this gets worse, i.e. your queue member won't receive any new calls even after Alice's channel is hung up.
> This bug (which happens to be a regression) has been introduced by commit 338a8ffed673e4c3a828c7c216575f8e3e712350 and this commit references ASTERISK-19820.
> Thanks



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