[asterisk-bugs] [JIRA] (ASTERISK-26975) app_queue: Non-zero wrapup time can cause agents not to receive queue calls after transfer queue call

[George Joseph (JIRA)]

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

George Joseph updated ASTERISK-26975:
-------------------------------------

    Target Release Version/s: 14.6.0

> app_queue: Non-zero wrapup time can cause agents not to receive queue calls after transfer queue call
> -----------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-26975
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26975
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_queue
>    Affects Versions: 13.14.0
>         Environment: FreePBX Distro 13, Centos 6.6, Asterisk 13.14.0
>            Reporter: Lorne Gaetz
>            Assignee: Joshua Colp
>            Severity: Minor
>      Target Release: 13.17.0, 14.6.0
>
>         Attachments: full.rar
>
>
> This took some effort to reproduce reliably, because I was seeing different behavior immediately after an Asterisk restart (and sometimes reload) vs. the second test after restarting. To successfully test for this condition you must always test twice after restarting Asterisk or after reloading changes to queue wrapuptime.
> Steps to reproduce:
> # Create queue with settings noted below and reload
> # callers dial into to queue, have agent answer a queue call and transfer the call away to another destination. I tested with both blind and attended using both the phone transfer buttons and the Asterisk in-call feature codes. All transfers do the same thing.
> # at this point the queue agent's phone is idle, but 'queue show' reveals the agent's extension is (in call) and (Not in use)
> {code}dev2*CLI> queue show 703
> 703 has 3 calls (max unlimited) in 'ringall' strategy (12s holdtime, 31s talktime), W:0, C:7, A:29, SL:100.0% within 60s
>    Members:
>       2014 Sangoma (Local/2014 at from-queue/n from hint:2014 at ext-local) (ringinuse disabled) (Ringing) has taken no calls yet
>       2004 Grandstream (Local/2004 at from-queue/n from hint:2004 at ext-local) (ringinuse disabled) (in call) (Not in use) has taken 1 calls (last was 32 secs ago){code}
> # Once the queue timeout cycles again, one of two things will happen. If Asterisk has just been restarted, the phone of the queue agent in question will once again ring with a queue call, exactly as expected. If this is the second queue call transfer that the agent has made since restarting then their phone will no longer ring with queue calls until the transferred call is completed.
> # The work around is to set wrapup time to 0 and reload. Once wrapuptime=0, the queue agent extension will continue to ring as normal.
> Queue Settings
> {code}[703]
> announce-frequency=0
> announce-holdtime=no
> announce-position=no
> autofill=no
> autopause=no
> autopausebusy=no
> autopausedelay=0
> autopauseunavail=no
> joinempty=yes
> leavewhenempty=no
> maxlen=0
> memberdelay=0
> min-announce-frequency=15
> penaltymemberslimit=0
> periodic-announce-frequency=0
> queue-callswaiting=silence/1
> queue-thereare=silence/1
> queue-youarenext=silence/1
> reportholdtime=no
> retry=0
> ringinuse=no
> servicelevel=60
> setinterfacevar=yes
> strategy=ringall
> timeout=15
> timeoutpriority=app
> timeoutrestart=no
> weight=0
> wrapuptime=5
> context=
> member=Local/2014 at from-queue/n,0,"2014 Sangoma",hint:2014 at ext-local
> member=Local/2004 at from-queue/n,0,"2004 Grandstream",hint:2004 at ext-local
> lazymembers=no{code}



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