[Asterisk-bugs] [Asterisk 0010126]: If 'retry' is set to 0, it gets treated as though it's set to 5.

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10126 
====================================================================== 
Reported By:                bcnit
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10126
Category:                   Applications/app_queue
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
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:13 CDT
Last Modified:              07-06-2007 02:30 CDT
====================================================================== 
Summary:                    If 'retry' is set to 0, it gets treated as though
it's set to 5.
Description: 
A queue is defined as follows:

---------------------
[testq]
timeout=10
retry=0
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 a call is placed in a queue, the phones ring for 10 seconds (as per
'timeout') and then wait for about 5 seconds before ringing again.

If 'retry' is changed to '1' (retry=1), then when a call is placed in a
queue, the phones ring for 10 seconds (as per 'timeout') and then wait for
one second before ringing again.

In 1.2.x, a value of '0' was allowed for 'retry'. I've searched the docs
and can't see any reference to this having changed.
====================================================================== 

---------------------------------------------------------------------- 
 bcnit - 07-06-07 02:30  
---------------------------------------------------------------------- 
I should add that I listed this as major as it has just broken a
dialplan/system which was working fine on 1.2.x! 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-06-07 02:30  bcnit          Note Added: 0066579                          
======================================================================