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

Andrej (JIRA) noreply at issues.asterisk.org
Mon Mar 13 08:59:10 CDT 2017


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

Andrej commented on ASTERISK-26400:
-----------------------------------

Hi,

if this helps: I've originally opened a ticket ASTERISK-26757 which was closed as duplicate; our situation was similar, but not same - we are using yealink phones with built-in blind and attended transfer functions/buttons. 

I've used the patch against asterisk 13.14.0 and after first tests bug seems to be gone.

When call comes into the queue and agent (308) answers it, we can see:

asterisk3*CLI> queue show 298
298 has 0 calls (max unlimited) in 'leastrecent' strategy (3s holdtime, 62s talktime), W:0, C:2, A:0, SL:100.0% within 15s
   Members:
      Local/381 at from-queue/n (ringinuse disabled) (dynamic) (Unavailable) has taken no calls yet
      Local/308 at from-queue/n with penalty 4 (ringinuse disabled) (dynamic) (in call) (In use) has taken 2 calls (last was 595 secs ago)
      Local/301 at from-queue/n with penalty 4 (ringinuse disabled) (dynamic) (Unavailable) has taken no calls yet
   No Callers

Agent transfers the call:

asterisk3*CLI> queue show 298
298 has 0 calls (max unlimited) in 'leastrecent' strategy (3s holdtime, 62s talktime), W:0, C:2, A:0, SL:100.0% within 15s
   Members:
      Local/381 at from-queue/n (ringinuse disabled) (dynamic) (Unavailable) has taken no calls yet
      Local/308 at from-queue/n with penalty 4 (ringinuse disabled) (dynamic) (in call) (Not in use) has taken 2 calls (last was 743 secs ago)
      Local/301 at from-queue/n with penalty 4 (ringinuse disabled) (dynamic) (Unavailable) has taken no calls yet
   No Callers

Asterisk is reporting agent 308 as in call, but he is able to take new calls.

Thanks for your time and energy, good work.

Andrej


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



More information about the asterisk-bugs mailing list