[Asterisk-bugs] [Asterisk 0010127]: Queue timeouts are considerably higher than expected

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10127 
====================================================================== 
Reported By:                bcnit
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10127
Category:                   Applications/app_queue
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.6 
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        Yes 
Request Review:              
====================================================================== 
Date Submitted:             07-05-2007 20:31 CDT
Last Modified:              07-17-2007 15:24 CDT
====================================================================== 
Summary:                    Queue timeouts are considerably higher than expected
Description: 
A queue is defined as follows:

----------------------------
[testq]
timeout=10
retry=5
strategy=ringall
wrapuptime=0
maxlen=0
joinempty=no
leavewhenempty=yes
eventmemberstatus=no
eventwhencalled=no
reportholdtime=no
memberdelay=0
weight=0
timeoutrestart=0
autopause=no
member => SIP/100
member => SIP/101
member => SIP/102
----------------------------

When called with 'Queue(testq,n)':
1 - The phones ring for 10 seconds.
2 - There is 5 seconds silence
3 - The phones ring for 10 seconds.
4 - There is 5 seconds silence
5 - The call exits the queue on the time-out cycle

So, despite the queue having a timeout of 10 seconds, the call is in the
queue for 30.

When called with 'Queue(testq,n,,,10):
1 - The phones ring for 10 seconds.
2 - There is 5 seconds silence
3 - The call exits the queue (no mention is made of the time-out cycle).

So, despite coding an explicit 10 seconds timeout, the call is in the
queue for 15.


====================================================================== 

---------------------------------------------------------------------- 
 blitzrage - 07-17-07 15:24  
---------------------------------------------------------------------- 
The real issue I think is that it should not actually exit after failure to
reach _any_ member, but rather if it can't reach any member(s) depending on
the strategy involved.

Exiting right away makes sense when the strategy is ringall, like in the
example given, but exiting after the first called member when you've got a
strategy of rrmemory seems wrong to me. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-17-07 15:24  blitzrage      Note Added: 0067483                          
======================================================================