Mike, This sometimes happens although I have not seen it lately on any of my systems nor has anyone else reported it. On the BBB we did add a dnsmgr.conf file in /etc/asterisk with the following : [general] enable=yes ; enable creation of managed DNS lookups ; default is 'no' refreshinterval=300 ; refresh managed DNS lookups every <n> seconds ; default is 300 (5 minutes) You might try that. It can be a dns issue. Also when it happens go into the client and issue an 'iax2 reload' command. That will often fix it. Check it with an 'iax2 show registry' command. If it does then you could execute that command on a regular basis from a script. If that does not fix it there should be no need to reboot the system though as astres.sh at the linux prompt will restart asterisk and should clear the problem without a reboot. If it does not then you might have network or dns issues with your Linux system. 73 Doug WA3DSP http://www.crompton.com/hamradio Date: Wed, 21 Jan 2015 15:27:41 -0800 From: ka6oij@arrl.net To: app_rpt-users@ohnosec.org Subject: [App_rpt-users] Node becomes unregistered after many weeks (no reply from registration server) I've seen this problem on various nodes now for a while and finally had a minute to actually grab ethernet packets from the WAN side of the firewall to see if I could dig deeper to figure out what is breaking after sometime. This is not a major problem since a reboot fixes it but more of a curiosity. I tried to search the forums to see if this had been asked before but didn't find anything of help. The issue is that after a node sits unused for a long time it becomes unregistered. I'm not sure how long a long time is but it is in weeks. A reboot of the box always bring is back. Today I went looking on the WAN side of the firewall and I can see the box sending IAX2 packets out to the registration server but the registration server never replying. I used the WAN side so as to rule out local network issues. As far as I can tell the IAX registration UDP packet looks fine to me. The contents of the failed one look the same to a successful one. It appears to be sending the REGREQ message and waiting 2 seconds before resending the same REGREQ message again and waiting 10 seconds and repeating once more after 10 seconds. Finally waiting 28 seconds and starting again with a new REGREG message with a new Source Call. When it works the REGREQ is replied to from the registration server with a CALL TOKEN, etc and the rest of the IAX handshake and authentication happens. Not sure if helps in figuring this out but when the node is in this state the call to get nodes.pl is rejected. Call to uhandler are replied with "OK!". Since it takes a long time to reproduce this issue I'm wondering if I should be looking for something else the next time this happens. The fact that a reboot always bring it back implies that there is something else on the local node that is causing this to break and the registration server to ignore the IAX requests on purpose. Mike _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.