When DNS (or outside connection to the network, not sure which) is broken and you have "register=>" lines in iax.conf, Asterisk gets whacky.
First of course you'll the message "Host (whatever) not found at line (whatever)" in iax2.c at startup. It takes a long time for the lookup to timeout.
Later, I get some other generally bizzare behavior including:
1. I get "everyone is busy at this time" from devices that aren't.
2. The dual-redirect crash is 100% repeatable now. One of the last things you see is "planning to masqerade 0sd8(*&(& INTO ...." just before it crashes.
If you remove the "register" lines from iax.conf (or fix your DNS/Internet problem) it runs fine.
My first thought is it could be a timing issue due to the timeout taking so long during startup. Looking at the IAX2 registration code, it doesn't immediately appear that a failed registration would wreak any particular havoc.
Does this sound similar to anyone else's experience? Anyone else care to verfiy? Our Asterisk version is pretty close to CVS, maybe a few weeks out but I didn't see any bugs listed that seemed to address this.
_______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
