[asterisk-bugs] [Asterisk 0014123]: DNSmgr causes port numbers to be set to zero

[Asterisk Bug Tracker]

The issue 0013628 has been set as DUPLICATE OF the following issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14123 
====================================================================== 
Reported By:                blitzrage
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14123
Category:                   Core/PBX
Reproducibility:            sometimes
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.1 
SVN Revision (number only!): 166164 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-12-22 09:29 CST
Last Modified:              2008-12-22 09:33 CST
====================================================================== 
Summary:                    DNSmgr causes port numbers to be set to zero
Description: 
I've found over the last couple of days that my peers would start giving me
warnings that it couldn't connect with a peer because there was no respond
on port 0 (makes sense). It would give me a sip_xmit error.

I think I've found why it is happening now though. I just noticed this
happen this morning:

    -- Refreshing DNS lookups.
[Dec 22 09:37:37] NOTICE[16527]: dnsmgr.c:170 dnsmgr_refresh: dnssrv: host
'pbx.BLANKED.com' changed from 216.207.xxx.xxx:5060 to 216.207.xxx.xxx:0
[Dec 22 09:37:38] NOTICE[16527]: dnsmgr.c:170 dnsmgr_refresh: dnssrv: host
'switch1-mia.BLANKED.net' changed from 64.251.xxx.xxx:5060 to
64.251.xxx.xxx:0

etc...

Notice how it changed the port from 5060 to 0? I also see that when do a
'sip show peer FOO' where FOO is the peer that is associated with the
registration (i.e. same IP address).
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
has duplicate       0013628 IAX port change using dnsmgr
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-12-22 09:33 blitzrage      Relationship added       has duplicate 0013628
======================================================================