[asterisk-bugs] [Asterisk 0010320]: 1.4.9 changes to app_queue breaks 'joinempty=yes'

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10320 
====================================================================== 
Reported By:                jfitzgibbon
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10320
Category:                   Applications/app_queue
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.9  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             07-27-2007 07:04 CDT
Last Modified:              07-27-2007 07:10 CDT
====================================================================== 
Summary:                    1.4.9 changes to app_queue breaks 'joinempty=yes'
Description: 
1.4.9 introduced changes to app_queue that change the logic associated with
exiting the queue due to a timeout.

The 1.4.8 logic would only ever be executed if the 'n' option was passed
to Queue(), as designed.

The 1.4.9 logic can be executed in the absence of the 'n' option if the
queue is empty.  The net effect is that a queue configured as
'joinempty=yes' with no members in it cannot be enqueued to in 1.4.9 -
calls will immediately be kicked back to the dialplan.  Depending on how
the dialplan was built, this could result in calls being unceremoniously
hung up if there are no further steps in the extension that called Queue()
====================================================================== 

---------------------------------------------------------------------- 
 jfitzgibbon - 07-27-07 07:10  
---------------------------------------------------------------------- 
Though I can't seem to lock onto the circumstances, I also oberved this
breaking queues configured as "leavewhenempty=no".

I can't seem to replicate it using a single queue and a single member (on
pause or on a call or letting their phone ring through), but last night
when I had 4 agents on a queue (3 on calls), I saw this on my console just
as one agent didn't pick up:

    -- Nobody picked up in 20000 ms
    -- Exiting on time-out cycle

All of my queues are configured as "joinempty=yes" and
"leavewhenempty=no".  I never want to kick a caller out of my queue based
on agent availability.

I am assuming that the same changes as broke joinempty are responsible for
this, and hopefully reviewing those changes will bring the cause of this
other situation to light as well. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-27-07 07:10  jfitzgibbon    Note Added: 0067969                          
======================================================================