[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:                     new
Asterisk Version:           1.6.2.8 
JIRA:                        
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-10 13:15 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0123255) pabelanger (manager) - 2010-06-10 13:15
 https://issues.asterisk.org/view.php?id=17496#c123255 
---------------------------------------------------------------------- 
We require a complete debug log to help triage the issue.

This document will provide instructions on how to collect debugging logs
from an Asterisk machine for the purpose of helping bug marshals
troubleshoot an issue:

http://svn.digium.com/svn/asterisk/trunk/doc/HOWTO_collect_debug_information.txt


Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-06-10 13:15 pabelanger     Note Added: 0123255                          
======================================================================