Summary:ASTERISK-13257: DNSmgr causes port numbers to be set to zero
Reporter:Leif Madsen (lmadsen)Labels:
Date Opened:2008-12-22 09:29:24.000-0600Date Closed:2008-12-22 09:33:51.000-0600
Versions:Frequency of
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


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).
Comments:By: Leif Madsen (lmadsen) 2008-12-22 09:33:51.000-0600

I am bad... I fail.