<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
you got a bbb hooked to the system on your end? bring up LSnodes<br>
use <a class="moz-txt-link-freetext" href="http://your">http://your</a> BBB local IP address/lsnodes/lsnodes_form.html to
bring it up<br>
<div class="moz-cite-prefix">On 10/14/14 10:50, Doug Crompton wrote:<br>
</div>
<blockquote cite="mid:BLU172-W42FEC5321CB1BB5A673640BAAD0@phx.gbl"
type="cite">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div dir="ltr"><font style="" color="#000000"
face="Tahoma,sans-serif">I notice that in spite of its low
power consumption many users operate BBB nodes in an up and
down fashion. That is if they only use it in the evening or
some other time of the day they turn it on use it for awhile
and then turn it off. The problem arises when you expect your
node to come up and be ready for a connect immediately after
boot. This is not always the case for a number of reasons.
Here is what happens at boot.<br>
<br>
The Linux OS boots rather fast, within 10 seconds or so.
Approximately 15-30 seconds later Asterisk starts and
registers your node. If the registration is successful at that
point, and it usually is, the node list located at
/tmp/rpt_extnodes is populated with the currently active nodes
from allstarlink.org. This would include your node as it was
just registered. This is the list that Allstar uses to map
nodes to actual IP addresses and ports.<br>
<br>
OK so you then try to connect to a distant node and you get a
failure. Why? The reason is that the local node list only
updates from allstarlink.org every 10 minutes at the request
of the node. If you happened to register and download the node
list just 10 seconds after the node you were trying to connect
to requested an update you would have to wait 9+ minutes
before that node knew about you in its next update and allowed
your connection. Since these windows are different for each
node the time to be able to connect to a specific node could
be seconds to almost 10 minutes.<br>
<br>
The answer is to not expect everything to just work at startup
and if you can connect to one node and not another it could
likely be because of this delay. Start your node and go get a
cup of coffee then try to connect.<br>
<br>
Note that this problem would probably not exist if you were
just rebooting a node that has been running or if the node was
unregistered for a short amount of time and it would not exist
at all if you left your BBB running.<br>
<br>
Because this question often comes up I will be including a
message about this in the next BBB release.<br id="FontBreak">
</font><br>
<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 class="moz-txt-link-freetext" href="http://www.crompton.com/hamradio">http://www.crompton.com/hamradio</a></font></b><font
style="font-size:16pt;" size="4"><br>
</font> </div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
arm-allstar mailing list
<a class="moz-txt-link-abbreviated" href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a>
<a class="moz-txt-link-freetext" href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar">http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar</a>
Visit the BBB web page - <a class="moz-txt-link-freetext" href="http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/">http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/</a></pre>
</blockquote>
<br>
</body>
</html>