[asterisk-bugs] [JIRA] (ASTERISK-21879) app_queue's autofill=yes effectively fails to deliver all calls when those calls are preceded by a call with a min/max penalty that can't be delivered

[Rusty Newton (JIRA)]

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

Rusty Newton edited comment on ASTERISK-21879 at 6/20/13 5:24 PM:
------------------------------------------------------------------

I reproduced this (in SVN-branch-1.8-r391778) following your description. I've talked with some of the developers here and it seems that it's a limitation of the current design. 

Essentially app_queue is stuck on waiting to deliver the call with the min penalty since there are no members available that it can take it. Yes you would expect that with autofill=yes app_queue would then skip that call and attempt delivering the others. Apparently the penalties throws some confusion into the mix.

Good thing you found a workaround for now.
                
      was (Author: rnewton):
    I reproduced this following your description. I've talked with some of the developers here and it seems that it's a limitation of the current design. 

Essentially app_queue is stuck on waiting to deliver the call with the min penalty since there are no members available that it can take it. Yes you would expect that with autofill=yes app_queue would then skip that call and attempt delivering the others. Apparently the penalties throws some confusion into the mix.

Good thing you found a workaround for now.
                  
> app_queue's autofill=yes effectively fails to deliver all calls when those calls are preceded by a call with a min/max penalty that can't be delivered
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-21879
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21879
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_queue
>    Affects Versions: 1.8.20.1
>         Environment: Gentoo Linux 3.0.65
>            Reporter: Ksenia
>            Severity: Minor
>         Attachments: channels_info.txt, full.log
>
>
> We have 2 queues - at-test and at-test1.
> A user calls extension 8100 and after 20s timeout waiting in at-test we set QUEUE_MIN_PENALTY=20 for the call, then it goes to queue at-test1. We have an autofill parameter set to 'yes' in at-test1. Only agent Agent/903 from at-test1 can receive the call with minimal penalty set to 20. So, if this agent Agent/903 is busy or unavailable, the call is waiting in the queue. But if another user calls extension 8101, he has to wait untill that call with QUEUE_MIN_PENALTY=20 is answered or dropped, though autofill parameter is set to 'yes' and there are free agents 904 and 905. Is it a normal behavior?
> P.S. I've fixed it using QUEUE_PRIO variable for extension 8101, but still it's very interesting to know why the calls have to wait in such circumstances.
> exten => 8100,1,Answer()
> exten => 8100,n,Queue(at-test,t,,,20)
> exten => 8100,n,Set(QUEUE_MIN_PENALTY=20)
> exten => 8100,n,Queue(at-test1,t,,,3600)
> exten => 8100,n,Hangup()
> exten => 8101,1,Answer()
> exten => 8101,n,Queue(at-test1,t,,,3600)
> exten => 8101,n,Hangup()
> [at-test1]
> autofill = yes
> setinterfacevar = yes
> setqueuevar = yes
> strategy = leastrecent
> announce-frequency = 60
> wrapuptime = 12
> announce-round-seconds = 30
> announce-holdtime = yes
> announce-position = yes
> queue-thankyou = no
> reportholdtime = no
> ringinuse = no
> joinempty = yes
> member => Agent/903,20,(903) Test Operator
> member => Agent/904,,(904) Test Operator
> member => Agent/905,,(905) Test Operator

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