[asterisk-bugs] [Asterisk 0010155]: autofill reports and behaves in 2 different ways

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10155 
====================================================================== 
Reported By:                irroot
Assigned To:                bweschke
====================================================================== 
Project:                    Asterisk
Issue ID:                   10155
Category:                   Applications/app_queue
Reproducibility:            always
Severity:                   trivial
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.6 
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        No 
Request Review:              
====================================================================== 
Date Submitted:             07-08-2007 10:29 CDT
Last Modified:              08-24-2007 14:24 CDT
====================================================================== 
Summary:                    autofill reports and behaves in 2 different ways
Description: 


in function  is_our_turn only interfaces in states unknown/not inuse are
concidered for availability (this bypasses all call-limit settings and the
like)
yet when the call is placed normal strategy rules are applied.

this is confusing ... 

i came accross this when implementing a call-limit bypass on a per member
basis that will only concider them when free.

if there is a demand for this ill post the patch.
====================================================================== 

---------------------------------------------------------------------- 
 bweschke - 08-24-07 14:24  
---------------------------------------------------------------------- 
The only thing I see us not doing that we should probably be doing is
excluding members that are paused in the current queue from being counted
as "available". As far as call-limits,etc I think these are being imposed
on the channel driver level and it should be the responsibility of the
channel driver to report itself as "BUSY or INUSE" back to the core which
app_queue will in turn receive and act on appropriately. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-24-07 14:24  bweschke       Note Added: 0069382                          
======================================================================