[asterisk-bugs] [Asterisk 0013628]: IAX port change using dnsmgr

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13628 
====================================================================== 
Reported By:                pananix
Assigned To:                jpeeler
====================================================================== 
Project:                    Asterisk
Issue ID:                   13628
Category:                   Channels/chan_iax2
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           1.6.1-beta1 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-10-06 10:59 CDT
Last Modified:              2008-12-22 10:05 CST
====================================================================== 
Summary:                    IAX port change using dnsmgr
Description: 
When dnsmgr is enabled, a iax peer that is connected will go unreachable
when the dnsmgr runs and subsequently changes the port.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
duplicate of        0014123 DNSmgr causes port numbers to be set to...
====================================================================== 

---------------------------------------------------------------------- 
 (0096789) blitzrage (administrator) - 2008-12-22 10:05
 http://bugs.digium.com/view.php?id=13628#c96789 
---------------------------------------------------------------------- 
This seems to work for me. The issue I closed and related will be something
I need to wait over the next day or so to see if this fixes that issue or
not, but for the dnsmgr refresh part of it, yes, it appears to be fixed! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-12-22 10:05 blitzrage      Note Added: 0096789                          
======================================================================