<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">There are a few ways to do what you want — that is permanently tie multiple repeaters together — if I understand your question.<div><br></div><div>First, permanent connections are not as permanent as you might expect. If the computer that initiated the permanent connections goes down the connection will not reestablish. However you can have a startup macro make the connection as Asterisk starts. Also, there seems to be some intermittent bug, which I’ve never pinned down, where permanent connections won’t reestablish with out forcing a disconnect first. <br><div><br></div><div>Second way is with RTCMs. They are a whole lot easier to deploy and way more reliable than a bunch of USB type nodes, with the trade off in expense. Although by the time you buy a BBB and a URI you’re getting close to the expense of an RTCM. Of course you can go with a cheep sound dongle and an eBay used thin client PC. It’s the ‘ol time/money/reliability trade off. I strongly recommend the RTCM approach. </div><div><div><br></div></div><div>And a third option is called app_radbridge. If you don’t want to buy RTCMs this is probably the way to go. I’ve never tried to use it. The only documentation I am aware of is in the source which is reproduced here. </div><div><div><div><span style="font-family: Monaco; font-size: 12px;"><br></span></div><div><span style="font-family: Monaco; font-size: 12px;">/* This application is intended to provide a generic "bridging"</span></div><div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> functionality for radio-oriented Asterisk channels.</div><div style="margin: 0px; font-size: 12px; font-family: Monaco; min-height: 16px;"><br></div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> The idea here is that certain radio applications lend themselves</div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> to needing a "generic" (passes audio and tx/rx keying completely</div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> transparently) to and from two or more endpoints.</div><div style="margin: 0px; font-size: 12px; font-family: Monaco; min-height: 16px;"><br></div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> An example of such an appication might be replacing (or providing</div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> equivlent new functionaliy of) one or more full-duplex UHF control</div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> links with an IP-based one(s).</div><div style="margin: 0px; font-size: 12px; font-family: Monaco; min-height: 16px;"><br></div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> app_radbridge allows multiple instances of radio-oriented channels</div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> transparently "bridged" together.</div><div style="margin: 0px; font-size: 12px; font-family: Monaco; min-height: 16px;"><br></div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> The config file (radbridge.conf) allows specification of each</div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> "bridging" instance and what radio-oriented Asterisk channels</div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> are to be associated with it. There is no need for any other</div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> specificaiton of configuration.</div><div style="margin: 0px; font-size: 12px; font-family: Monaco; min-height: 16px;"><br></div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> The file format for radbridge.conf departs somewhat from the standard</div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> usage (at least for radio stuff) of the Asterisk config file architecture.</div><div style="margin: 0px; font-size: 12px; font-family: Monaco; min-height: 16px;"><br></div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> In most other radio-oriented cases, an instance of whatever it is</div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> gets defined as a "Stanza" in the config file. In this case, because</div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> of limitations in the way that Asterisk parses config files, that </div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> was not possible. Instead, all config information goes into the</div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> [general] stanza, and each line of config info defines a different</div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> instance of radio bridging. For example:</div><div style="margin: 0px; font-size: 12px; font-family: Monaco; min-height: 16px;"><br></div><div style="margin: 0px; font-size: 12px; font-family: Monaco;">[general]</div><div style="margin: 0px; font-size: 12px; font-family: Monaco; min-height: 16px;"><br></div><div style="margin: 0px; font-size: 12px; font-family: Monaco;">instance1 = Voter/1234,Radio/5678</div><div style="margin: 0px; font-size: 12px; font-family: Monaco;">instance2 = Voter/1235,Radio/5679</div><div style="margin: 0px; font-size: 12px; font-family: Monaco; min-height: 16px;"><br></div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> This example would define two radio bridging instances "instance1"</div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> and "instance2", each with 2 channels associated with them.</div><div style="margin: 0px; font-size: 12px; font-family: Monaco; min-height: 16px;"><br></div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> The supported channel types are "Voter" (chan_voter), "Radio"</div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> (chan_usbradio), "SimpleUsb" (chan_simpleusb), and "Zap" ("Dahdi")</div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> (chan_dahdi, for the couple of devices that use this channel</div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> driver, such as the PCIRadio card, and separate analog channels</div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> using an ARIB board or such).</div><div style="margin: 0px; font-size: 12px; font-family: Monaco; min-height: 16px;"><br></div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> Rather then "adding" (which would actually be a lot of *removing*</div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> optionally) this functionality in app_rpt, it made more sense to</div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> create a separate application specifically for this purpose. In</div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> addition, this allows for a system that is merely provided for</div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> doing this bridging application and nothing else radio-oriented,</div><div><div style="margin: 0px; font-size: 12px; font-family: Monaco;"> to not have to run app_rpt at all. </div></div><div>*/</div><div><br class="webkit-block-placeholder"></div><div>
<span class="Apple-style-span" style="border-collapse: separate; font-family: Verdana; border-spacing: 0px;"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Verdana; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">--<br>Tim<br>:wq</div></span></span>
</div>
<br><div><div>On Sep 28, 2014, at 12:28 PM, Robert Newberry <<a href="mailto:N1XBM@amsat.org">N1XBM@amsat.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><p dir="ltr">So as it stands I have a one node system. I have another URI on the way and will have BBB soon. The eventual plan is to have a few repeaters and some simplex nodes at people's houses for RF hot spot access. </p><p dir="ltr">What is the best way to tie these together? I understand you can set permanent links that will reestablish connection if lost.</p><p dir="ltr">Is there other ways of accomplishing this? I only ask because I have my one node setup with email, autopatch and all other kinds of bells and whistles. I'd like to be able to do all of this from other RF locations and I wonder if I need to just set each node up accordingly or can one node be the workhorse and the other nodes just be dumb connections. </p><p dir="ltr">Did I make any sense with that question? </p>
_______________________________________________<br>App_rpt-users mailing list<br><a href="mailto:App_rpt-users@ohnosec.org">App_rpt-users@ohnosec.org</a><br>http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users<br><br>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"<br>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. </blockquote></div><br></div></div></div></div></body></html>