|Summary:||ASTERISK-08406: IAX2 outgoing calls not working|
|Reporter:||Corneliu Doban (cdoban)||Labels:|
|Date Opened:||2006-12-20 23:17:30.000-0600||Date Closed:||2007-01-25 16:25:03.000-0600|
|Environment:||Attachments:||( 0) putty.log|
|Description:||If the managed DNS lookups are enabled in dnsmgr.conf, IAX2 peers show "Unspecified" in the host clumn, and no outgoing calls can be made:|
*CLI> iax2 show peers
Name/Username Host Mask Port Status
voipjet (Unspecified) (S) 255.255.255.255 4569 Unmonitored
firefly1/firefl (Unspecified) (D) 255.255.255.255 0 Unmonitored
fwd-gw/267563 (Unspecified) (S) 255.255.255.255 4569 Unmonitored
3 iax2 peers [0 online, 0 offline, 3 unmonitored]
If the managed DNS lookups are disabled in dnsmgr.conf, the correct IP addesses of the IAX2 peers are showing.
Attaced is a putty capture ofasterisk starting with managed DNS lokups enabled followed by a start with the DNS lookup disabled.
After several hours the IAX2 peers IP showed up and outgoing calls started working.
This problem was observed for asterisk running on embedded device: Linksys NSLU2 (intel IXP4020 - ARMv5te).
Thie same configuration was worink perfect on previous versions up to 188.8.131.52
But after finding the problem on 1.4 I've tried the 1.2.14 and 1.2.13 and found the same problem.
|Comments:||By: Corneliu Doban (cdoban) 2006-12-20 23:27:35.000-0600|
Apparently during the startup asterisk gets the peer IP address and logs the change but the change does not reflect when interrogating from the CLI: iax2 show peers:
Dec 17 23:16:24] �[1;33;40mNOTICE�[0;37;40m: �[1;37;40mdnsmgr.c�[0;37;40m:�[1;37;40m177�[0;37;40m �[1;37;40mdnsmgr_refresh�[0;37;40m: host 'iax2.fwdnet.net' changed from 0.0.0.0 to 184.108.40.206
By: Joshua C. Colp (jcolp) 2007-01-09 23:13:25.000-0600
I was unable to reproduce this issue... but I suspect it either has something to do with the timing of things, or the architecture... rather interesting. The new IP address should be put into the memory that iax2 show peers uses.
By: Joshua C. Colp (jcolp) 2007-01-25 16:25:03.000-0600
I'm closing this out since this is obviously an issue with dnsmgr and not something we can solve, dnsmgr was/is experimental and as you see can easily be turned off.