<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><font style="" color="#000000" face="Tahoma,sans-serif">Mike,<br><br> You probably won't find anything formal that fits the description of exactly what you want to do. Here is how I do it:<br id="FontBreak"></font><br><font style="" face="Tahoma,sans-serif">In rpt.conf in the node section add -</font><font style="" face="Tahoma,sans-serif"><br></font><font style="" face="Tahoma,sans-serif"><br></font><font style="" face="Tahoma,sans-serif">startup_macro=*A999</font><font style="" face="Tahoma,sans-serif"><br></font><font style="" face="Tahoma,sans-serif"><br>The function code can be anything you want that is not in conflict with any other function. Using the A,B,C,D codes is a good way to do it as it is unlikely anyone would enter that code on the RF side.<br><br></font><font style="" face="Tahoma,sans-serif">and in the function section add -</font><font style="" face="Tahoma,sans-serif"><br></font><font style="" face="Tahoma,sans-serif"><br></font><font style="" face="Tahoma,sans-serif">A999=cmd,/etc/asterisk/local/reconnect_local</font><font style="" face="Tahoma,sans-serif"><br></font><font style="" face="Tahoma,sans-serif"><br></font><font style="" face="Tahoma,sans-serif">File reconnect_local in /etc/asterisk/local</font><font style="" face="Tahoma,sans-serif"><br></font><font style="" face="Tahoma,sans-serif"><br></font><font style="" face="Tahoma,sans-serif">#! /bin/bash</font><font style="" face="Tahoma,sans-serif"><br></font><font style="" face="Tahoma,sans-serif"><br></font><font style="" face="Tahoma,sans-serif">/usr/sbin/asterisk -rx "rpt fun yournode *73distantnode1"</font><font style="" face="Tahoma,sans-serif"><br></font><font style="" face="Tahoma,sans-serif">sleep 1</font><font style="" face="Tahoma,sans-serif"><br></font><font style="" face="Tahoma,sans-serif">/usr/sbin/asterisk -rx "rpt fun yournode *73distantnode2"</font><font style="" face="Tahoma,sans-serif"><br></font><font style="" face="Tahoma,sans-serif">sleep 1</font><font style="" face="Tahoma,sans-serif"><br></font><font style="" face="Tahoma,sans-serif">/usr/sbin/asterisk -rx "rpt fun yournode *73distantnode3"</font><font style="" face="Tahoma,sans-serif"><br></font><font style="" face="Tahoma,sans-serif"><br></font><font style="" face="Tahoma,sans-serif">and of course more could be added.</font><font style="" face="Tahoma,sans-serif"> The script has to be executable. The sleeps are probably not necessary but it certainly does not hurt anything putting them in. You could also do these multiple connects right within the function command in rpt.conf but I like to use external scripts. You also have the choice of running them via a cron job or manually from the command line. <br></font><font style="" face="Tahoma,sans-serif"></font><br><font style="" face="Tahoma,sans-serif">As I mentioned before you also have the choice of inbound permanent connections to the hub which also work but in the opposite direction. Each remote site would have a startup macro that would connect to the hub</font>. <font style="" face="Tahoma,sans-serif">Doing it this way you could come in RF and enter the function code to connect to the hub if necessary.</font><font style="" face="Tahoma,sans-serif"><br></font><br><font style="" face="Tahoma,sans-serif">There is no need to test it. It works. Permanent connections will reconnect if this is a link disruption or the distant station is restarted or rebooted but remember they go away when the originating system is restarted or rebooted. That is why you use a startup macro</font>.<br><br><font style="" face="Tahoma,sans-serif">I don't think it really makes much difference which way you do it inbound or outbound. Either way it depends on the hub being there. You could setup some redundancy with some more scripting if you were using inbound connections to the hub that in the event the hub was not there the remote nodes would create alternate connections.</font><br><br><font style="font-size: 16pt;" face="Tahoma,sans-serif" size="4"><b>73</b></font><font style="font-size: 16pt;" face="Tahoma,sans-serif" size="4"> </font><b><font style="font-size:16pt;" size="4">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">http://www.crompton.com/hamradio</font></b><font style="font-size:16pt;" size="4"><br></font><br><br><div><hr id="stopSpelling">Date: Fri, 19 Dec 2014 12:18:30 -0500<br>From: mike.lussier@gmail.com<br>To: app_rpt-users@ohnosec.org<br>Subject: [App_rpt-users] Linking private network nodes to hub<br><br><div dir="ltr"><div>We are working on building out a Broadband Hamnet in our area. I have placed both of my repeaters on the network and I built a hub to connect them too. The hub sits on the edge of the network touching both the internet and the boradband hamnet network. <br><br>I have seen multiple messages about linking private repeaters to a hub however there hasn't been a specific conclusion. <br><br></div>I will say that I did like Doug's Idea of having each individual node auto connect to the the hub. There is no formal documentation that I have been able to find to test this. <br clear="all"><div><div><div><br><br></div><div>Mike AE4ML<br><br><br></div><br></div></div></div></div> </div></body>
</html>