<div dir="ltr">Doug,<div><br></div><div>Good wright up. I would only add that the port, if different from the default, must not only be defined in the [nodes] stanza but also on the AllStar Portal. That's because the port that's defined on the portal is the port is put into rpt_extnodes. </div><div><br></div><div>This step is often forgotten and can be a cause of inbound connects not working. </div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Aug 16, 2015 at 5:20 AM, Doug Crompton <span dir="ltr"><<a href="mailto:doug@crompton.com" target="_blank">doug@crompton.com</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 color="#000000" face="Tahoma,sans-serif">I guess I should do a how-to on this since this question gets asked so often!<br><br>When connecting nodes they need both the information to connect and the path to connect. The information to connect is found either in the rpt_extnodes file (in /tmp on the RPi2 and BBB and /var/lib/asterisk in Acid) or in a specific path entered in your rpt.conf file under the [nodes] stanza.<br><br>To check use grep on the database or view the nodes section in rpt.conf<br><br>grep 42285 /tmp/rpt_extnodes<br><br>grep 28302 /tmp/rpt_extnodes<br>28302=<a href="http://radio@50.93.230.87:4569/28302,50.93.230.87" target="_blank">radio@50.93.230.87:4569/28302,50.93.230.87</a><br><br></font><font face="Tahoma,sans-serif">As you can see one node turned up an address the other did not here this morning but perhaps the 42285 node is off the air. <br><br>Nodes have to have routing information at BOTH ends to work. This includes the IP address AND proper port. Often ports are the issue because people do not specify them if they are different then the default 4569. The port must be defined in the local ( [nodes] stanza ) information if it is different than the default.<br><br>The master database ( rpt_extnodes ) is usually used to determine how to get to another node but for local or private connections it is often specifically defined in the rpt.conf [nodes] stanza. <br><br>You can use the Asterisk client (asterisk -rvvv at the Linux prompt) to troubleshoot this as it gives messages at BOTH ends about what went wrong. If you connect from one node to another and you do not see any messages at the node you are connecting to then it did not get through and you can suspect a routing problem due to a misaddress or port either in the database or port forwarding if it is outside your LAN. Of course outside your LAN it could also be a hopefully temporary Internet routing problem beyond your control.<br></font><br><font face="Tahoma,sans-serif">Some more background can be found here -</font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"><br></font><font face="Tahoma,sans-serif"><a href="http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/multi-server%20howto.pd" target="_blank">http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/multi-server%20howto.pd</a></font>f<br><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 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><br><div><hr>Date: Sun, 16 Aug 2015 11:35:34 +0000<br>From: <a href="mailto:n7jys@yahoo.com" target="_blank">n7jys@yahoo.com</a><br>To: <a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a><br>Subject: [arm-allstar] node connections<br><br><div style="color:#000;background-color:#fff;font-family:HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif;font-size:24px"><div>I have put two new nodes on line and all is working great. Yesterday my 42285 node </div><div dir="ltr"> stopped being able to connect to the reset of my nodes 2351,2578,28302. But</div><div dir="ltr">it can connect to any other node that's on line. </div><div dir="ltr"><br></div><div dir="ltr">2351,2578,28302 cannot connect to 42285 but they all will connect to any other nodes on line.</div><div dir="ltr">This is strange behavior and not understanding why this is happening. </div><div dir="ltr"><br></div><div dir="ltr">2351,2578,28302 all live on one RPI2 and on its own IP at my repeater site. 42285 is on </div><div dir="ltr">an ACID install P4 computer at my home qth and its own IP. Port 4569 is forward correctly</div><div dir="ltr">on both routers as they all will connect to other nodes on line. Both IP address at my repeater</div><div dir="ltr">site and at my home are from the same provider. <br></div><div dir="ltr"><br></div><div dir="ltr"><br></div><div></div><div> </div><div>Eric (N7JYS) Marshall's Communications</div></div><br>_______________________________________________
arm-allstar mailing list
<a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a>
<a href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar" target="_blank">http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar</a>
Visit the BBB and RPi2 web page - <a href="http://hamvoip.org" target="_blank">http://hamvoip.org</a></div> </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><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>--<br></div><div>Tim</div></div></div></div></div>
</div>