[asterisk-bugs] [Asterisk 0016775]: Queue with autofill=no and strategy=ringall sometimes rings non-oldest caller through to agents

Asterisk Bug Tracker noreply at bugs.digium.com
Thu Feb 4 14:47:36 CST 2010


The following issue has been SUBMITTED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16775 
====================================================================== 
Reported By:                tbpsn
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16775
Category:                   Applications/app_queue
Reproducibility:            random
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           Older 1.4 - please test a newer version 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-02-04 14:47 CST
Last Modified:              2010-02-04 14:47 CST
====================================================================== 
Summary:                    Queue with autofill=no and strategy=ringall
sometimes rings non-oldest caller through to agents
Description: 
I'm experiencing a possible bug in 1.4.26 x86_64 with app_queue.  I have a
queue set to strategy=ringall and autofill=no, but I am seeing autofill
behavior (non FIFO), with latter callers ringing through before the oldest
caller has been answered.

Example: A caller sits on hold for 2 minutes (due to all agents being
busy), then a new caller enters the queue.  An agent becomes free, and as
it happens, the newer caller (with a shorter hold time) rings through to
the agent and the call is answered, leaving the caller with the longest
hold time still unserviced.

Reviewing the logs, it's clear that asterisk is correctly retrying to send
the oldest caller through at the correct interval.  It just looks like the
newer caller seems to have squeezed through, and happened to be answered
first.

My queue definition is listed in 'Additional Information' 
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-02-04 14:47 tbpsn          New Issue                                    
2010-02-04 14:47 tbpsn          Asterisk Version          => Older 1.4 - please
test a newer version
2010-02-04 14:47 tbpsn          Regression                => No              
2010-02-04 14:47 tbpsn          SVN Branch (only for SVN checkouts, not tarball
releases) => N/A             
======================================================================




More information about the asterisk-bugs mailing list