<div dir="ltr">Great information, Doug. Thank you. Once I have all the bugs out of this node I'll start on another and primarily stay connected to that node. I was mainly thinking about Echolink, but your codec suggestions will be useful too. I have a couple friends who don't have access to Allstar yet. That will change - even if I have to build nodes for them <grin>... right now one is building an experimental aircraft so his efforts aren't ham radio oriented. I think both have static IPs, so I may be able to get by with minimal Echolink database updates - if at all. Worth an try. The Echolink node list updates pretty often as configured. Thought there might be a way to update upon request instead of periodically or enable/disable Echolink connectivity as needed with a command. <div>
<br></div><div>John </div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Aug 27, 2014 at 1:28 PM, 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 face="Tahoma">John,<br><br> As far as connections are concerned you could use ilbc as your codec but that depends on where you are connected to. The ilbc codec uses about 1/3 the BW of G726 but it is only currently supported on the BBB or a PC system where it has been installed. You could also use gsm at reduced audio quality if the system you are connecting to allows it. Codec priority is setup in iax.conf<br>
<br>If you are connected to a node or nodes that have light traffic that may not matter but if it is a busy channel a higher BW codec could eat up a lot of BW.<br><br>The only things that are downloaded are the node list once every 5 minutes and the node details which download once a day in a cron job. If you always connected to the same place and their IP address was static or did not change you could dispense with the node list download and specifically add the node or nodes in you rpt.conf file.<br>
<br>To stop the node list updates comment out the line in /etc/rc.local<br><br>/usr/local/etc/rc.updatenodelist &<br><br>and reboot.<br><br>You could also update that script and change the update period but keep in mind that nodes are changing constantly and there would be more stale data that way.<br>
<br>The nodes stanza in rpt.conf would then be used to connect to nodes you commonly connect to -<br><br>[nodes]<br>; Note, if you are using automatic update for allstar link nodes,<br>; no allstar link nodes should be defined here. Only place a definition<br>
; for your local nodes, and private (off of allstar link) nodes here.<br><br>node = radio@IPaddress:port/node,NONE<br><br>So if your friends node was 12345 and his ip was 50.60.70.80 the line would be -<br><br>12345 = <a href="http://radio@50.60.70.80/12345,NONE" target="_blank">radio@50.60.70.80/12345,NONE</a><br>
<br>If he was on port 4568 it would be -<br><br></font><font face="Tahoma"><font face="Tahoma"><font face="Tahoma">12345 = <a href="http://radio@50.60.70.80:4568/12345,NONE" target="_blank">radio@50.60.70.80:4568/12345,NONE</a></font></font><br>
<br>The ':port' is only used if the port is other than the default 4569<br><br>I don't know about echolink being negligible. They have a fairly substantial list (larger than Allstar) and depending on how often it downloads it might be more than you think. I would turn off echolink if you don't need it. If it is just you using it to your own system perhaps an iax client like zoiper might be a better choice. It would only use up BW when you are actually using it. No database involved.<br>
<br>I am not sure how much these suggestions are going to buy you. It really depends on your usage but it is worht a try.<br></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 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>> From: <a href="mailto:wb5nfc@gmail.com" target="_blank">wb5nfc@gmail.com</a><br>> Date: Wed, 27 Aug 2014 12:45:57 -0500<br>> To: <a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a><br>
> Subject: [arm-allstar] Data Conservation<div class=""><br>> <br>> I'm looking for ways to be as frugal as possible on data usage for my node. Ideally, I want to leave the node on all the time (at least during the day). I'm sure the data consumed for constant Echolink node updates is negligible, but every byte adds up when utilizing a hotspot with a data cap. Is there a way to refresh data less often or only when needed for an outgoing call? <br>
> <br>> John<br>> <br>> Sent from my iPhone<br></div>> _______________________________________________<br>> <br>> arm-allstar mailing list<br>> <a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a><br>
> <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><br>> <br>> Visit the BBB web page - <a href="http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/" target="_blank">http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/</a><br>
> <br></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" target="_blank">http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar</a><br>
<br>
Visit the BBB web page - <a href="http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/" target="_blank">http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/</a><br></blockquote></div><br><br clear="all"><div><br>
</div>-- <br>John Kenney
</div>