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

[noreply at bugs.digium.com]

The following issue has been REOPENED. 
====================================================================== 
http://bugs.digium.com/view.php?id=10127 
====================================================================== 
Reported By:                bcnit
Assigned To:                qwell
====================================================================== 
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-09-2007 08:56 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.


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

---------------------------------------------------------------------- 
 bcnit - 07-09-07 08:56  
---------------------------------------------------------------------- 
I take your point.

However, if what you say is the case, the first example should ring the
handsets for ten seconds.

It doesn't - it rings them for 20 (two lots of 10).

Since the queue is called with the 'n' paramter (no retry on timeout) and
the timeout does occur and a retry does take place, there is clearly
something wrong.

Also, shouldn't 'retry' be ignored if the call is going to timeout? i.e.
if timeout=10, retry=5 and the call is queued with 'Queue(testq,n)', then
surely it should be 10 seconds before the call bounces out and not 15. If
this is not the case, we waste 5 seconds of the caller's life during which
we can do nothing with the call.

As an aside (and I appreciate that this is not the ideal place to ask),
just how is one supposed to dump a call to a queue for a specific amount of
time, regardless of what that queue is doing with the call? 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-09-07 08:56  bcnit          Status                   closed => feedback  
07-09-07 08:56  bcnit          Resolution               no change required =>
reopened
07-09-07 08:56  bcnit          Note Added: 0066787                          
======================================================================