Summary:	ASTERISK-23809: IAX2 registration fails after temporary dns failure
Reporter:	Birger "WIMPy" Harzenetter (wimpy)	Labels:
Date Opened:	2014-05-30 14:26:43	Date Closed:	2014-05-30 20:58:37
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Channels/chan_iax2
Versions:	11.9.0	Frequency of Occurrence
Related Issues:	duplicates ASTERISK-23767 [patch] Dynamic IAX2 registration stops trying if ever not able to resolve is duplicated by ASTERISK-23813 DNS Manager (dnsmgr) does not restore port is related to ASTERISK-19106 SIP registration fails after temporary dns failure
Environment:	dnsmgr enabled	Attachments:
Description:	I have iax2 registrations using DNS name, and dnsmgr enabled. If I get temporary DNS lookup failure at asterisk startup, the IAX2 registrations will fail. Once DNS works again, the IP is updated correctly, but the port number stays 0. This is a duplicate of ASTERISK-19106 but for IAX2.
Comments:	By: Shaun Ruffell (sruffell) 2014-05-30 14:57:57.631-0500 Just adding a "me too" on this one. I ran into this issue on my home server (not sure what flavor of the 12 branch I was running at the time).  I actually opened a ticket with Digium's IT department before I fixed my registration failure by restarting Asterisk.  I eventually figured out it was a DNS issue. By: Michael L. Young (elguero) 2014-05-30 20:58:37.167-0500 You might want to follow ASTERISK-23767 as that appears to be the same issue as this one. By: David Herselman (bbs2web) 2014-05-31 04:52:22.507-0500 I disagree. I mention the issue with dnsmgr not restoring the port number (remains as 0), but specifically note that it is a separate issue from the one logged in ASTERISK-23767 (https://issues.asterisk.org/jira/browse/ASTERISK-23767). Please re-open this request. Extract from ASTERISK-23767: {quote}We are not using Asterisk's dnsmgr module, as it correclty switches the IP from 0.0.0.0 to whatever it should be but doesn't restore the port from 0 (when unavailable) to 4569 (when available). The dnsmgr issue is, as such, a separate issue from the one reported here.{quote} By: Birger "WIMPy" Harzenetter (wimpy) 2014-06-03 11:19:58.428-0500 Indeed. This is to https://issues.asterisk.org/jira/browse/ASTERISK-23767 what https://issues.asterisk.org/jira/browse/ASTERISK-18351 is to https://issues.asterisk.org/jira/browse/ASTERISK-19106 dnsmgr enabled vs. dnsmgr disabled. By: Rusty Newton (rnewton) 2014-06-03 11:25:55.422-0500 Reporter of ASTERISK-23767 reports that the patch for ASTERISK-23767 fixes the issue reported here as well.