[asterisk-bugs] [Asterisk 0018485]: [patch] IAX2 Retry Time Review
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu May 12 05:59:50 CDT 2011
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=18485
======================================================================
Reported By: netfuse
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 18485
Category: Channels/chan_iax2
Reproducibility: have not tried
Severity: tweak
Priority: normal
Status: ready for review
Asterisk Version: SVN
JIRA: SWP-2754
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-12-16 09:41 CST
Last Modified: 2011-05-12 05:59 CDT
======================================================================
Summary: [patch] IAX2 Retry Time Review
Description:
Guys,
The IAX2 channel driver has a number of timeout settings for
communication. I have found that customers with network problems are not
particularly benefitted by these timeouts because they are so incredibly
high.
If you look at the maths, it will be at least 30 seconds with absolutely
no traffic before a DIAL on an IAX2 host fails. However, a SIP peer with
qualify=yes defaults to 2000ms. I recommend that the 2 seconds timeout
should be applied to dialling on IAX trunks also.
Patch attached for your consideration. I have tested this in production
use with good results.
Cheers
Leo
======================================================================
----------------------------------------------------------------------
(0134824) netfuse (reporter) - 2011-05-12 05:59
https://issues.asterisk.org/view.php?id=18485#c134824
----------------------------------------------------------------------
Hi
Re: the exponential timer, I do think 1.5x would be more appropriate if
we're retrying 4 times.
The question is, where is the 4x retry chosen from?
It doesn't make sense if you think about real world scenarios, we would
never keep trying on a dead call for 30 seconds!
Leo
Issue History
Date Modified Username Field Change
======================================================================
2011-05-12 05:59 netfuse Note Added: 0134824
======================================================================
More information about the asterisk-bugs
mailing list