[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=235683#comment-235683 ] 

David Brillert edited comment on ASTERISK-26400 at 3/10/17 2:40 PM:
--------------------------------------------------------------------

[~seanbright] Correct, the Polycom is transferring to another extension.
Keep in mind my ticket regarding transfers ASTERISK-26715 was closed out as a duplicate. I never reported an issue using AMI or external redirect (that was Etienne).

I also run into issues with a transfer to PARK extension after retrieving the call from the parking lot.

{noformat}
debcomainbtn-reception has 0 calls (max unlimited) in 'ringall' strategy (0s holdtime, 0s talktime), W:0, C:0, A:0, SL:0.0% within 60s
   Members:
      Local/214 at debcomainbtn-agent/n (ringinuse disabled) (dynamic) (in call) (Not in use) has taken no calls yet
   No Callers

debcomainbtn-sales has 0 calls (max unlimited) in 'rrmemory' strategy (0s holdtime, 0s talktime), W:0, C:0, A:0, SL:0.0% within 10s
   Members:
      Local/214 at debcomainbtn-agent/n (ringinuse disabled) (dynamic) (in call) (Not in use) has taken no calls yet
   No Callers

master88*CLI> core show channels
Channel              Location             State   Application(Data)
SIP/debcomainbtn213- 701 at debcomainbtn-man Up      ParkedCall(parkinglot_debcomai
SIP/debcomainbtn216- s at debcomainbtn-appli Up      Queue(debcomainbtn-reception,t
Local/214 at debcomainb s at debcomainbtn-agent Up      AppQueue((Outgoing Line))
Local/214 at debcomainb 214 at debcomainbtn-loc Up      Dial(SIP/debcomainbtn214,,tk)
{noformat}


was (Author: aragon):
[~seanbright] Correct, the Polycom is transferring to another extension.
Keep in mind my ticket regarding transfers ASTERISK-26715 was closed out as a duplicate. I never reported an issue using AMI or external redirect (that was Etienne).

> 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
>            Assignee: David Brillert
>              Labels: regression
>         Attachments: 0001-app_queue-Handle-the-caller-being-redirected-out-of-.patch, 13reviewboardtests.txt
>
>
> 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)