[asterisk-bugs] [Asterisk 0009561]: agents assigned to multiple queues and weight=0 cause callers be handled in wrong order

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=9561 
====================================================================== 
Reported By:                hehol
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   9561
Category:                   Core/Configuration
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:            1.2.17  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        Yes 
Request Review:              
====================================================================== 
Date Submitted:             04-19-2007 07:00 CDT
Last Modified:              08-12-2007 07:16 CDT
====================================================================== 
Summary:                    agents assigned to multiple queues and weight=0
cause callers be handled in wrong order
Description: 
Assume the following setup:

- two queues
- weight=0 or undefined (thus default 0) in queues.conf 
- one dynamic agent logged onto the server

When placing calls in both queues, the calls are being handled
first-in-last-out instead of first-in-first-out, i.e. the last caller to
join either of the two queues will be served to the agent first.
====================================================================== 

---------------------------------------------------------------------- 
 hehol - 08-12-07 07:16  
---------------------------------------------------------------------- 
> be served to the agent first." Does this mean that calls within a single
queue > are handled last-in-first-out

Yes.

> Furthermore, does this ALWAYS happen, or does it happen only some of the
time? 

It always happens.

> When you say that changing the weight to a non-zero value fixes the
problem, 
> are you setting both queues' weights to non-zero values or just one of
them? 
> If you're changing both, are you changing them both to the same value?

I set the value of both queues to 1. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-12-07 07:16  hehol          Note Added: 0068753                          
======================================================================