<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">Phil,<br><br> Sounds like a neat setup. If you have taken photos I would love to put some up on the web page for all to see.<br><br>The RF issue is usually HF but I suppose it could be any frequency if conditions were right.<br><br>I generally put both RF and low frequency bypasses on the input and output of those modules. I have seen RF getting into them, even the node itself. A .01 ceramic and a 220uf or higher electrolytic in parallel are a good idea and of course short leads and ferrites. <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">http://www.crompton.com/hamradio</font></b><font style="font-size:16pt;" size="4"><br></font><br><br><div><hr id="stopSpelling">Date: Fri, 12 Aug 2016 10:10:35 -0400<br>To: arm-allstar@hamvoip.org<br>Subject: Re: [arm-allstar] URI "shuts down"<br>From: arm-allstar@hamvoip.org<br>CC: phil@philv.net<br><br><div dir="ltr">Company PIcnic yesterday afternoon so I have not had a chance to try any suggestions yet. I'll get some time tonight.<div><br></div><div>Just to respond to a few of the follow up questions:</div><div><br></div><div>* I have tried a new USB cable</div><div><br></div><div>* I have also tried a new Pi</div><div><br></div><div>* The wires from the radios to the URI are definately a bit longer than they need to be. So I'll definitely address that</div><div><br></div><div>* Im powering the entire setup off of a 12v battery array hooked up to a charge controller/solar panel. The pi is powered by a 12v to 5v converter. I have another converter that i can swap out and see if that helps. My solar setup is a pretty nice setup, its not one of those cheapy charge controllers.... and i've run my allstar node on it issue free since last october-ish.... so i do think im leaning towards RF being the problem and not power.... but i certainly cant rule out power completely yet.</div><div><br></div><div>* Its been so intermittent that i have not yet been able to catch an error while logged into the asterisk console</div><div><br></div><div>Thanks for all the input/feedback. I'll get some time to play tonight and I'll report back with any findings.</div><div><br></div><div>~P</div><div>K2ELV<br><div class="ecxgmail_extra"><br><div class="ecxgmail_quote">On Thu, Aug 11, 2016 at 12:00 PM, <span dir="ltr"><<a href="mailto:arm-allstar-request@hamvoip.org" target="_blank">arm-allstar-request@hamvoip.org</a>></span> wrote:<br><blockquote class="ecxgmail_quote" style="border-left:1px #ccc solid;padding-left:1ex;">Send arm-allstar mailing list submissions to<br>
<a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar" rel="noreferrer" target="_blank">http://lists.hamvoip.org/cgi-<wbr>bin/mailman/listinfo/arm-<wbr>allstar</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:arm-allstar-request@hamvoip.org">arm-allstar-request@hamvoip.<wbr>org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:arm-allstar-owner@hamvoip.org">arm-allstar-owner@hamvoip.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of arm-allstar digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Fwd: Data Usage (David McGough)<br>
2. Re: Fwd: Data Usage (Doug Crompton)<br>
3. URI "shuts down" (Phil Visalli)<br>
4. Re: URI "shuts down" (Roselito de los Reyes)<br>
5. Re: URI "shuts down" (Doug Crompton)<br>
6. Re: URI "shuts down" (Doug Crompton)<br>
<br>
<br>
------------------------------<wbr>------------------------------<wbr>----------<br>
<br>
Message: 1<br>
Date: Wed, 10 Aug 2016 18:59:28 -0400 (EDT)<br>
From: David McGough <<a href="mailto:kb4fxc@inttek.net">kb4fxc@inttek.net</a>><br>
To: Phil Hebert via arm-allstar <<a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a>><br>
Subject: Re: [arm-allstar] Fwd: Data Usage<br>
Message-ID:<br>
<<a href="mailto:Pine.LNX.4.44.1608101855520.1460-100000@goliath.inttek.net">Pine.LNX.4.44.1608101855520.<wbr>1460-100000@goliath.inttek.net</a><wbr>><br>
Content-Type: TEXT/PLAIN; charset=US-ASCII<br>
<br>
<br>
That's a good question? ...If the node isn't registered, and sitting<br>
completely idle, probably not. Even if registered, maybe not. I've always<br>
run across VPNs (OpenVPN) when using 4G and specifically generate<br>
keep-alive traffic.<br>
<br>
Anyone got a definitive answer?<br>
<br>
73, David KB4FXC<br>
<br>
<br>
On Wed, 10 Aug 2016, Phil Hebert via arm-allstar wrote:<br>
<br>
> A related question<br>
> If the node is idle, then is there still enough activity to keep a mifi hotspot not go to sleep ?<br>
><br>
> Sent from my Mobile Device<br>
><br>
><br>
> > On Aug 10, 2016, at 17:53, David McGough via arm-allstar <<a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a>> wrote:<br>
> ><br>
> ><br>
> > No. An idle node has very, very low bandwidth requirements.<br>
> ><br>
> ><br>
> >> On Wed, 10 Aug 2016, Tom Hayward via arm-allstar wrote:<br>
> >><br>
> >> On Wed, Aug 10, 2016 at 2:16 PM, Mark Johnston via arm-allstar<br>
> >> <<a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a>> wrote:<br>
> >>> Including overhead I would estimate 100 kb/sec each way depending on codec -<br>
> >>> ALaw or ULaw vs GSM which is about half that.<br>
> >>><br>
> >>> Multiply that out for however long you stay connected...<br>
> >><br>
> >> Does a connected but idle link consume much data? I'd like to<br>
> >> permanently link a couple very low-usage repeaters.<br>
> >><br>
> >> Tom KD7LXL<br>
> >> ______________________________<wbr>_________________<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-<wbr>bin/mailman/listinfo/arm-<wbr>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>
> ><br>
> > ______________________________<wbr>_________________<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-<wbr>bin/mailman/listinfo/arm-<wbr>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>
><br>
> ______________________________<wbr>_________________<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-<wbr>bin/mailman/listinfo/arm-<wbr>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>
><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Wed, 10 Aug 2016 19:18:48 -0400<br>
From: Doug Crompton <<a href="mailto:doug@crompton.com">doug@crompton.com</a>><br>
To: ARM Allstar <<a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a>><br>
Subject: Re: [arm-allstar] Fwd: Data Usage<br>
Message-ID: <BLU171-<wbr>W1348822DF5A41E37425BFB6BA1D0@<wbr>phx.gbl><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
If you are using a limited bandwidth or metered circuit that you pay for by data use I would recommend ilbc - or internet low bandwidth codec. It is very close to the quality of G726 with BW more like GSM.<br>
<br>
All hamvoip images have ilbc. Acid and other versions do not. So you would not be compatible but the best way to run a mobile node is to connect to a fixed node you control. Then other user can connect there to find you. The codec between your mobile node and fixed node would be ilbc and from the fixed node to wherever whatever you want.<br>
73 Doug<br>
WA3DSP<br>
<a href="http://www.crompton.com/hamradio" rel="noreferrer" target="_blank">http://www.crompton.com/<wbr>hamradio</a><br>
<br>
<br>
Date: Wed, 10 Aug 2016 17:06:49 -0400<br>
To: <a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a><br>
Subject: [arm-allstar] Fwd: Data Usage<br>
From: <a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a><br>
CC: <a href="mailto:kd4hlv@gmail.com">kd4hlv@gmail.com</a><br>
<br>
I was wondering what the data usage or minimum bandwidth requirements for Allstar link?<br>
<br>
73,<br>
Marty KD4HLV<br>
<br>
<br>
<br>
<br>
______________________________<wbr>_________________<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-<wbr>bin/mailman/listinfo/arm-<wbr>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>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20160810/d5654a91/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.hamvoip.org/<wbr>pipermail/arm-allstar/<wbr>attachments/20160810/d5654a91/<wbr>attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Thu, 11 Aug 2016 09:55:51 -0400<br>
From: Phil Visalli <<a href="mailto:phil@philv.net">phil@philv.net</a>><br>
To: <a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a><br>
Subject: [arm-allstar] URI "shuts down"<br>
Message-ID:<br>
<<a href="mailto:CAAMk9h8qduj9RpfFjTD-VOsnrMszv6ZwK-%2BY2Hz54St_FEaSxw@mail.gmail.com">CAAMk9h8qduj9RpfFjTD-<wbr>VOsnrMszv6ZwK-+Y2Hz54St_<wbr>FEaSxw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
I've been struggling with an intermittent issue on my allstar node for a<br>
few weeks now and I figured I'd see if anyone else has run into this. For<br>
the most part everything is running perfect, but every now and then my URI<br>
will stop working. I cant find any pattern to when/why this happens and i<br>
haven't found any clues in /var/log/asterisk/messages. When i look at the<br>
URI the green heartbeat light has stopped flashing (both lights off). If i<br>
unplug it from the USB port and plug it back in, everything goes back to<br>
normal. Its worth noting that nothing else stops working. Any connections<br>
to other nodes are maintained... the pi is still running and working fine,<br>
its just that the radio is no longer working due to the dead URI.<br>
<br>
I've swapped the URI out for another one..... same thing. I've pulled the<br>
SD card out of the pi, put it in a new pi ..... same results. The only<br>
thing I have not done yet is replace and reload the SD card, and i am<br>
probably going to try that over the weekend.<br>
<br>
Im running the RPi2-3_V1.02beta_Allstar.img release<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20160811/a9898bbe/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.hamvoip.org/<wbr>pipermail/arm-allstar/<wbr>attachments/20160811/a9898bbe/<wbr>attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Thu, 11 Aug 2016 08:21:39 -0700<br>
From: Roselito de los Reyes <<a href="mailto:tolitski@hotmail.com">tolitski@hotmail.com</a>><br>
To: ARM Allstar <<a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a>><br>
Subject: Re: [arm-allstar] URI "shuts down"<br>
Message-ID: <BLU403-<wbr>EAS2550DB7E38A643F88B7F087D41E<wbr>0@phx.gbl><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Hi Phil,<br>
<br>
Have you tried swapping out the USB cable?<br>
<br>
Best regards,<br>
<br>
Roselito De Los Reyes<br>
<br>
<br>
> On Aug 11, 2016, at 6:55 AM, Phil Visalli via arm-allstar <<a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a>> wrote:<br>
><br>
> I've been struggling with an intermittent issue on my allstar node for a few weeks now and I figured I'd see if anyone else has run into this. For the most part everything is running perfect, but every now and then my URI will stop working. I cant find any pattern to when/why this happens and i haven't found any clues in /var/log/asterisk/messages. When i look at the URI the green heartbeat light has stopped flashing (both lights off). If i unplug it from the USB port and plug it back in, everything goes back to normal. Its worth noting that nothing else stops working. Any connections to other nodes are maintained... the pi is still running and working fine, its just that the radio is no longer working due to the dead URI.<br>
><br>
> I've swapped the URI out for another one..... same thing. I've pulled the SD card out of the pi, put it in a new pi ..... same results. The only thing I have not done yet is replace and reload the SD card, and i am probably going to try that over the weekend.<br>
><br>
> Im running the RPi2-3_V1.02beta_Allstar.img release<br>
><br>
><br>
><br>
> ______________________________<wbr>_________________<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-<wbr>bin/mailman/listinfo/arm-<wbr>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>
<br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Thu, 11 Aug 2016 11:22:05 -0400<br>
From: Doug Crompton <<a href="mailto:doug@crompton.com">doug@crompton.com</a>><br>
To: ARM Allstar <<a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a>><br>
Subject: Re: [arm-allstar] URI "shuts down"<br>
Message-ID: <BLU171-<wbr>W11729E89CDA16045C6ABC8EBA1E0@<wbr>phx.gbl><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
This is obviously not normal and a rather rare thing. Things to check are the power supply. Supply spikes or irregularities could cause this as could high RF (HF etc.) fields getting into the wiring or components. Several people I know have had problems with HF stations getting into electronic devices not just Allstar and causing havoc.<br>
<br>
Those two things, dirty power and RF are the major cause of intermittent problems with the Allstar hardware.<br>
<br>
What are you using to supply power to the Pi and thus the URI? Are the leads to the URI long? They act as antennas, extra wire should be would in tight circles. Ferrite's over the wiring in and out of the URI and Pi are a good idea.<br>
<br>
One thing to check if you can catch it is to see what error you get when this happens. Open a client session to Asterisk in Linux - asterisk -rvvv - and look for any error messages when it occurs.<br>
<br>
Beyond the power and RF which are first choices I would try a different Pi and/or burn a new image.<br>
<br>
Lets us know what you find.<br>
73 Doug<br>
WA3DSP<br>
<a href="http://www.crompton.com/hamradio" rel="noreferrer" target="_blank">http://www.crompton.com/<wbr>hamradio</a><br>
<br>
<br>
Date: Thu, 11 Aug 2016 09:55:51 -0400<br>
To: <a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a><br>
Subject: [arm-allstar] URI "shuts down"<br>
From: <a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a><br>
CC: <a href="mailto:phil@philv.net">phil@philv.net</a><br>
<br>
I've been struggling with an intermittent issue on my allstar node for a few weeks now and I figured I'd see if anyone else has run into this. For the most part everything is running perfect, but every now and then my URI will stop working. I cant find any pattern to when/why this happens and i haven't found any clues in /var/log/asterisk/messages. When i look at the URI the green heartbeat light has stopped flashing (both lights off). If i unplug it from the USB port and plug it back in, everything goes back to normal. Its worth noting that nothing else stops working. Any connections to other nodes are maintained... the pi is still running and working fine, its just that the radio is no longer working due to the dead URI.<br>
I've swapped the URI out for another one..... same thing. I've pulled the SD card out of the pi, put it in a new pi ..... same results. The only thing I have not done yet is replace and reload the SD card, and i am probably going to try that over the weekend.<br>
Im running the RPi2-3_V1.02beta_Allstar.img release<br>
<br>
<br>
<br>
<br>
______________________________<wbr>_________________<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-<wbr>bin/mailman/listinfo/arm-<wbr>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>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20160811/d0ae1ded/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.hamvoip.org/<wbr>pipermail/arm-allstar/<wbr>attachments/20160811/d0ae1ded/<wbr>attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Thu, 11 Aug 2016 12:00:42 -0400<br>
From: Doug Crompton <<a href="mailto:doug@crompton.com">doug@crompton.com</a>><br>
To: ARM Allstar <<a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a>><br>
Subject: Re: [arm-allstar] URI "shuts down"<br>
Message-ID: <BLU171-<wbr>W5A52FB8DFCDAE723BED8DBA1E0@<wbr>phx.gbl><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
Another thing to check is the radio power supply. I think Dave can elaborate on this because at one time he had the problem. Spikes at turn on/off or maybe otherwise from the node radio supply can cause glitches downstream.<br>
73 Doug<br>
WA3DSP<br>
<a href="http://www.crompton.com/hamradio" rel="noreferrer" target="_blank">http://www.crompton.com/<wbr>hamradio</a><br>
<br>
<br>
To: <a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a><br>
Date: Thu, 11 Aug 2016 11:22:05 -0400<br>
Subject: Re: [arm-allstar] URI "shuts down"<br>
From: <a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a><br>
CC: <a href="mailto:doug@crompton.com">doug@crompton.com</a><br>
<br>
<br>
<br>
<br>
This is obviously not normal and a rather rare thing. Things to check are the power supply. Supply spikes or irregularities could cause this as could high RF (HF etc.) fields getting into the wiring or components. Several people I know have had problems with HF stations getting into electronic devices not just Allstar and causing havoc.<br>
<br>
Those two things, dirty power and RF are the major cause of intermittent problems with the Allstar hardware.<br>
<br>
What are you using to supply power to the Pi and thus the URI? Are the leads to the URI long? They act as antennas, extra wire should be would in tight circles. Ferrite's over the wiring in and out of the URI and Pi are a good idea.<br>
<br>
One thing to check if you can catch it is to see what error you get when this happens. Open a client session to Asterisk in Linux - asterisk -rvvv - and look for any error messages when it occurs.<br>
<br>
Beyond the power and RF which are first choices I would try a different Pi and/or burn a new image.<br>
<br>
Lets us know what you find.<br>
73 Doug<br>
WA3DSP<br>
<a href="http://www.crompton.com/hamradio" rel="noreferrer" target="_blank">http://www.crompton.com/<wbr>hamradio</a><br>
<br>
<br>
Date: Thu, 11 Aug 2016 09:55:51 -0400<br>
To: <a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a><br>
Subject: [arm-allstar] URI "shuts down"<br>
From: <a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a><br>
CC: <a href="mailto:phil@philv.net">phil@philv.net</a><br>
<br>
I've been struggling with an intermittent issue on my allstar node for a few weeks now and I figured I'd see if anyone else has run into this. For the most part everything is running perfect, but every now and then my URI will stop working. I cant find any pattern to when/why this happens and i haven't found any clues in /var/log/asterisk/messages. When i look at the URI the green heartbeat light has stopped flashing (both lights off). If i unplug it from the USB port and plug it back in, everything goes back to normal. Its worth noting that nothing else stops working. Any connections to other nodes are maintained... the pi is still running and working fine, its just that the radio is no longer working due to the dead URI.<br>
I've swapped the URI out for another one..... same thing. I've pulled the SD card out of the pi, put it in a new pi ..... same results. The only thing I have not done yet is replace and reload the SD card, and i am probably going to try that over the weekend.<br>
Im running the RPi2-3_V1.02beta_Allstar.img release<br>
<br>
<br>
<br>
<br>
______________________________<wbr>_________________<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-<wbr>bin/mailman/listinfo/arm-<wbr>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>
<br>
______________________________<wbr>_________________<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-<wbr>bin/mailman/listinfo/arm-<wbr>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>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20160811/34e4a548/attachment.html" rel="noreferrer" target="_blank">http://lists.hamvoip.org/<wbr>pipermail/arm-allstar/<wbr>attachments/20160811/34e4a548/<wbr>attachment.html</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
______________________________<wbr>_________________<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-<wbr>bin/mailman/listinfo/arm-<wbr>allstar</a><br>
<br>
<br>
------------------------------<br>
<br>
End of arm-allstar Digest, Vol 27, Issue 17<br>
******************************<wbr>*************<br>
</blockquote></div><br></div></div></div>
<br>_______________________________________________
arm-allstar mailing list
arm-allstar@hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
Visit the BBB and RPi2 web page - http://hamvoip.org</div> </div></body>
</html>