[asterisk-bugs] [Asterisk 0017496]: dnsmgr refreshes hostname, but changes SIP port to 0

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17496 
====================================================================== 
Reported By:                ManChicken
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17496
Category:                   Core/Configuration
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.6.2.8 
JIRA:                       SWP-1705 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-06-10 10:48 CDT
Last Modified:              2010-06-16 15:52 CDT
====================================================================== 
Summary:                    dnsmgr refreshes hostname, but changes SIP port to 0
Description: 
Have a SIP 'friend' for outbound calls through Vitelity, set with
host=outbound.vitelity.net.  DNS manager is refreshing the IP for
'outbound.vitelity.net' but changing the SIP port number to 0 for the peer
when it does - see console output below, showing the list of peers with
proper port numbers, a manual 'dnsmgr refresh', and it subsequently setting
the port to 0.
====================================================================== 

---------------------------------------------------------------------- 
 (0123502) pabelanger (manager) - 2010-06-16 15:52
 https://issues.asterisk.org/view.php?id=17496#c123502 
---------------------------------------------------------------------- 
ManChicken: Can you upgrade to the latest 1.6.2 branch?  I suspect this was
just fixed. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-06-16 15:52 pabelanger     Note Added: 0123502                          
======================================================================