|Summary:||ASTERISK-09812: If 'retry' is set to 0, it gets treated as though it's set to 5.|
|Reporter:||Nick Barnes (bcnit)||Labels:|
|Date Opened:||2007-07-05 20:13:42||Date Closed:||2011-06-07 14:02:36|
|Description:||A queue is defined as follows:|
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.
|Comments:||By: Nick Barnes (bcnit) 2007-07-06 02:30:29|
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!
By: Jason Parker (jparker) 2007-07-06 10:48:59
I believe this actually correct behavior. I'm trying to find the commit right now, but I think this was changed because if only one device was in the queue, and the retry time was set to 0, it would constantly spam the device with calls, causing a large amount of load on the server. If I'm remembering correctly, this was also changed in 1.2.
By: Jason Parker (jparker) 2007-07-06 10:53:41
Please see http://bugs.digium.com/view.php?id=7574 - this was intended.