<div dir="ltr">Success!!! After going into my router and making a port rule for 4569 I was able to connect!! Thanks for all the help!! I would never have figured that one out.<div><br></div><div>Thanks again!!</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div dir="ltr"><br><div><br></div><div><font color="#cc0000" face="arial, helvetica, sans-serif">Vincent Riley</font></div><div><font color="#cc0000">K4OZEcho</font></div><div><br></div></div></div></div></div>
<br><div class="gmail_quote">On Sat, Jul 9, 2016 at 2:13 PM, Doug Crompton via arm-allstar <span dir="ltr"><<a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div dir="ltr"><font face="Tahoma,sans-serif" color="#000000">I wanted to add one more thing and that is there is a waiting period for connections when a node first comes online. This is more apparent in nodes that may be going on and off line often. <br><br>When you bring a node up the node database is downloaded to your server during the boot process but other nodes that you would connect to also must have your connection information. The update interval is 10 minutes. That is your node refreshes its node database every ten minutes. This is a random update and if a node you wanted to connect to happened to do an update 30 seconds after you booted and registered then you could connect that fast. On the other hand if they had done an update 30 seconds before you registered then it would be another 9.5 minutes before they would again update and have knowledge of you so you could connect.<br><br>So don't be disturbed if you get connection failure messages in the first 10 minutes after booting. This is normal.<br><br>If on the other hand you try to connect to a valid online node after boot and you get no message back about connect or failure then that node is not in your database. This is probably due to a failure of your system to download the database. Look for the file /tmp/rpt_extnodes after boot. If it is not there then your server failed to download the database. Next check if you are actually registered -<br><br>asterisk -rvvv<br>iax2 show registry<br></font><font face="Tahoma,sans-serif" color="#000000"><br>If not then you might have a connection problem. Also check that your node password is correct in the registration line in /etc/asterisk/iax.conf<br><br>Failures to download the database have occurred with some cell systems most notably AT&T so far. We are looking at a work around for this. If you experience these kind of problems we would like to know. Let us know your hotspot model, and your provider. <br><br></font><span class=""><b><font style="font-size:16pt" size="4">73 Doug</font><font style="font-size:16pt" size="4"><br></font><font style="font-size:16pt" size="4">WA3DSP</font><font style="font-size:16pt" size="4"><br></font><font style="font-size:16pt" size="4"><a href="http://www.crompton.com/hamradio" target="_blank">http://www.crompton.com/hamradio</a></font></b><font style="font-size:16pt" size="4"><br></font><br> </span></div></div>
<br>_______________________________________________<br>
<br>
arm-allstar mailing list<br>
<a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a><br>
<a href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar" rel="noreferrer" target="_blank">http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar</a><br>
<br>
Visit the BBB and RPi2 web page - <a href="http://hamvoip.org" rel="noreferrer" target="_blank">http://hamvoip.org</a><br></blockquote></div><br></div></div>