[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:                     feedback
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-30-2007 08:00 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-30-07 08:00  
---------------------------------------------------------------------- 
I had a major problem with our queues on Friday - almost every member was
reported as state "Unknown" in the output of "show queues".  This was
causing agents to get calls when they were already on one (even though I
have ringinuse=no), and for calls to get stuck in the queue without being
deqeueued to idle agents.

I tried to restart *, but the problem reappeared.  I was forced to
downgrade to 1.4.7.1, where I have not seen the problem since.

In short, I'm not in a position to test this patch on my production
system, nor do I expect that I will be any time soon.  It has been a very
bad couple of weeks for Asterisk patching for us, and I'm not going to be
able to convince anyone that going back to 1.4.9 is worth the perceived
risk ATM. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-30-07 08:00  jfitzgibbon    Note Added: 0068037                          
======================================================================