[arm-allstar] Trouble connecting to nodes at start up
Doug Crompton
wa3dsp at gmail.com
Mon Nov 20 11:09:35 EST 2017
Jim,
The connect command will not take effect until you are registered and have
the valid nodes database. This can vary depending on many factors. The only
way around this at this point is to delay the connect. There are a number
of ways to do this but all would involve a script your would need to
create. Here is an easy example that does not involve messing with asterisk
config files (comment the startup_macro line in rpt.conf) -
In /etc/asterisk/local create this script named start_connect.sh
cd /etc/asterisk/local
nano start_connect.sh
Add the following contents -
#!/bin/bash
sleep 10 # seconds to wait - can be changed up or down
/usr/bin/asterisk -rx "rpt fun <yournode> *73<remotenode>"
# end of script
replace both yournode and remotenode with appropriate node numbers WITHOUT
the < or >
Additional connect lines can be entered.
Make this file executable - chmod 750 start_connect.sh
Run this script manually to test
In the /etc/asterisk/local directory - ./start_connect.sh
Call this script from rc.local -
#!/bin/bash
#
# rc.local file
# Starts Allstar
echo -1> /proc/sys/kernel/sched_rt_runtime_us
/usr/local/etc/rc.allstar
/etc/asterisk/local/start_connect.sh # add this line
exit 0
*73 Doug*
*WA3DSP*
*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
On Mon, Nov 20, 2017 at 7:33 AM, "James Hause via arm-allstar" <
arm-allstar at hamvoip.org> wrote:
> Doug,
>
>
>
> Regarding our conversations on connecting to node at startup:
>
>
>
> As I replied earlier, the only change I made to the rpt.conf file was to
> uncomment the startup_macro = *7, and changed it to startup_macro
> *7343773. When I reboot the Pi, it won’t connect until I execute the
> restart Asterisk from the admin screen. I searched for information on the
> Allstar Environment file (link:
> https://www.hamvoip.org/allstar_environment_howto.pdf), and found the
> following statement:
>
> Boot notes
>
> Any user specific functions or programs that you wish to add to the system
> that must be run automatically at boot and do not have a systemd run script
> should be added to the /etc/rc.local script either before or after the
> rc.allstar script depending on whether you want it to run before or after
> Allstar executes.
>
>
>
> This seems to address the issue of the Pi not connecting until I restart
> Asterisk server, but I am not exactly clear on what file I should update
> with what.
>
> On Sun, Nov 19, 2017 at 12:12 PM, "Doug Crompton via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > Jim,
> >
> > Well as I said in my last message this will not work under the current
> > file lookup system if you do not use hard routing at BOTH ends so that
> you
> > both know about each other at boot.
> >
> > The reason it works when you reboot after a while is because the other
> end
> > now knows about you and the connection can take place. Under the current
> > file lookup method it can take up to 10-15 minutes to establish a
> > connection. You can test this. Take your node down for about 15 minutes
> so
> > you node clears the database. Then when you come up see how long it takes
> > for you to manually connect to that node using *3. If you cannot connect
> > manually the startup_macro will not work until you can.
> >
> >
> > *73 Doug*
> >
> > *WA3DSP*
> >
> > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >
> >
> >
> >
> >
> > On Sun, Nov 19, 2017 at 12:48 PM, "James Hause via arm-allstar" <
> > arm-allstar at hamvoip.org> wrote:
> >
> > > Well did find out that if I did a restart of the Asterisk server, it
> did
> > > connect, but if I have to do a restart of the server to get this to
> work
> > > it kind of defeats the whole purpose, ie, it's not automatically
> > connecting
> > > at boot up.
> > > Will try your suggestion next.
> > > Sure appreciate your help !!!
> > >
> > > On Sun, Nov 19, 2017 at 11:19 AM, "Doug Crompton via arm-allstar" <
> > > arm-allstar at hamvoip.org> wrote:
> > >
> > > > Jim,
> > > >
> > > > Try this -
> > > >
> > > > startup_macro=*52
> > > >
> > > >
> > > > In the macro stanza right after the function stanza and after the 1=
> > > line
> > > > that is already in there add this line -
> > > >
> > > > 2=*7343773#
> > > >
> > > > Restart Asterisk.
> > > >
> > > > Also I am assuming that you can connect to this node manually?
> > > >
> > > > Another issue here is that a startup macro only works if both you and
> > the
> > > > other node are aware of each other. In the normal file lookup method
> in
> > > > Allstar this can take up to 10-15 minutes.
> > > >
> > > >
> > > > *73 Doug*
> > > >
> > > > *WA3DSP*
> > > >
> > > > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio
> >*
> > > >
> > > >
> > > >
> > > >
> > > > On Sun, Nov 19, 2017 at 11:50 AM, "James Hause via arm-allstar" <
> > > > arm-allstar at hamvoip.org> wrote:
> > > >
> > > > > Hi Doug,
> > > > > Well I restored back the rpt.conf file so it was back to what is
> was
> > > > before
> > > > > I did any changes.
> > > > > Down under misc settings for my node there was already a line:
> > > > >
> > > > > ;startup_macro = *7 (note there is a space before and after the =)
> > > > > I removed the : at the beginning of the line and changed it to:
> > > > > startup_macro = *7343773
> > > > >
> > > > > Rebooted Pi. Still did not connect.
> > > > >
> > > > >
> > > > > On Sun, Nov 19, 2017 at 9:37 AM, "Doug Crompton via arm-allstar" <
> > > > > arm-allstar at hamvoip.org> wrote:
> > > > >
> > > > > > Jim,
> > > > > >
> > > > > > Function definitions belong in the [functions] stanza further
> down
> > in
> > > > the
> > > > > > file not in the node definition stanza. In your case
> > > [functions46738]
> > > > So
> > > > > > move
> > > > > >
> > > > > > 951=ilink,11 ; Permanent link disconnect
> > > > > > 952=ilink,12 ; Permanent link receive
> > > > > > 953=ilink,13 ; Permanent link transceive
> > > > > >
> > > > > > down into that functions stanza. The startup_macro line is OK
> > where
> > > it
> > > > > is.
> > > > > > That should be in the node definition stanza for the connection
> > node.
> > > > > Also
> > > > > > you be aware that these three definition already exist there with
> > > > > different
> > > > > > function codes?
> > > > > >
> > > > > > 71=ilink,11
> > > > > > 72=ilink,12
> > > > > > 73=ilink,13
> > > > > >
> > > > > > You need to comment them and use your new ones but also remember
> > > unless
> > > > > you
> > > > > > are trying to obfuscate these functions this is not a good idea
> if
> > > > others
> > > > > > are going to use your node. It would be very confusing.
> > > > > >
> > > > > > When changing something like this you should manually execute the
> > > > command
> > > > > > to see if it works.
> > > > > >
> > > > > > You need to be careful where you change things in the config
> files
> > as
> > > > you
> > > > > > could quickly screw up your system. I highly recommend you make a
> > > > backup
> > > > > > copy of any file before you modify.
> > > > > >
> > > > > >
> > > > > > *73 Doug*
> > > > > >
> > > > > > *WA3DSP*
> > > > > >
> > > > > > *http://www.crompton.com/hamradio <http://www.crompton.com/
> > hamradio
> > > >*
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Sun, Nov 19, 2017 at 9:56 AM, "James Hause via arm-allstar" <
> > > > > > arm-allstar at hamvoip.org> wrote:
> > > > > >
> > > > > > > Hi Doug,
> > > > > > > Sorry for the confusion. I am registered. And I did do the
> > checks
> > > > you
> > > > > > > suggested for Chris, and all seems good when I check.
> > > > > > > I do have the rpt_extnodes file, and it does have the node in
> it
> > > > that I
> > > > > > > want to connect to, but it looks like the way I am trying to
> set
> > up
> > > > > > > start_up macro isn't correct, or not in the correct place in
> the
> > > > > rpt.conf
> > > > > > > file. Below I pasted section of the rpt.conf. I have started
> > the
> > > > > > > Supermon program on my PC, and when I
> > > > > > > reboot my Pi, I can see a very fast flash on the line where is
> > > shows
> > > > > > > connected to, stating I believe connecting to, the node I have
> in
> > > my
> > > > > > start
> > > > > > > up macro, but then status back to no connections.
> > > > > > > Section of my rpt.conf:
> > > > > > > ; The first node definition
> > > > > > >
> > > > > > > [46738] ; Change this to your assigned node number
> > > > > > >
> > > > > > > ; Channel Driver settings
> > > > > > > ; Define a channel driver to use and which
> > > > > > > ; interface within that channel driver
> > > > > > > ; To define a radioless node use the
> > > > > > > ; psuedo channel driver - rxchannel=dahdi/pseudo
> > > > > > > ;rxchannel=Radio/usb46738
> > > > > > > ; Example usbradio channel driver
> > > > > > > rxchannel=SimpleUSB/usb
> > > > > > > ; Example simpleusb channel driver
> > > > > > > ;rxchannel=dahdi/pseudo
> > > > > > > ; Example pseudo channel driver
> > > > > > >
> > > > > > >
> > > > > > > ; Repeater/Simplex node settings
> > > > > > > ; duplex=0 - Half duplex with no telemetry
> > > > > > > ; tones or hang time. Special Case: Full
> > > > > > > ; duplex if linktolink is set to yes.
> > > > > > > ; This mode is preferred when interfacing
> > > > > > > ; with an external multiport repeater controller.
> > > > > > >
> > > > > > > ; duplex=1 - Half duplex with telemetry tones
> > > > > > > ; and hang time. Does not repeat audio.
> > > > > > > ; This mode is preferred when interfacing a
> > > > > > > ; simplex node.
> > > > > > >
> > > > > > > ; duplex=2 - Full Duplex with telemetry tones
> > > > > > > ; and hang time. This mode is preferred when
> > > > > > > ; interfacing a repeater.
> > > > > > >
> > > > > > > ; duplex=3 - Full Duplex with telemetry tones
> > > > > > > ; and hang time, but no repeated audio.
> > > > > > > ; duplex=4 - Full Duplex with telemetry tones
> > > > > > > ; and hang time. Repeated audio only when the
> > > > > > > ; autopatch is down.
> > > > > > > duplex=1
> > > > > > >
> > > > > > > ; Context mapping
> > > > > > >
> > > > > > > controlstates=controlstates
> > > > > > > ; Defines groups of control operator commands
> > > > > > > ; to be executed all at once. Can be combined
> > > > > > > ; with macros to allow changes to a nodes
> > > > > > > ; operating mode to be made quickly.
> > > > > > >
> > > > > > > scheduler=schedule46738
> > > > > > > ; Defines macros to be executed at a specific
> > > > > > > ; time and date. Uses a cron-like syntax
> > > > > > >
> > > > > > > morse=morse46738
> > > > > > > ; Contains definitions for morse code messages.
> > > > > > > ; One common morse stanza is shared across
> > > > > > > ; multiple nodes
> > > > > > >
> > > > > > > macro=macro46738
> > > > > > > ; Defines DTMF macro sequences
> > > > > > >
> > > > > > > functions=functions46738
> > > > > > > 951=ilink,11 ; Permanent link disconnect
> > > > > > > 952=ilink,12 ; Permanent link receive
> > > > > > > 953=ilink,13 ; Permanent link transceive
> > > > > > > ; Defines DTMF function digit sequences. A
> > > > > > > ; function stanza has a reference to it defined
> > > > > > > ; inside a node stanza. Multiple function stanzas
> > > > > > > ; may be defined and used to provide different
> > > > > > > ; function lists for different sources
> > > > > > > ; (radio.phone, and link)
> > > > > > >
> > > > > > > phone_functions=functions46738
> > > > > > > link_functions=functions46738
> > > > > > >
> > > > > > > telemetry=telemetry
> > > > > > > ; Contains definitions for telemetry tones
> > > > > > > ; (courtesy tones, roger beeps, etc). A telemetry
> > > > > > > ; stanza has a reference to it defined inside
> > > > > > > ; a node stanza.
> > > > > > >
> > > > > > > macro=macro
> > > > > > > startup_macro=*95343773 ; macro to run at startup (optional)
> > > > > > >
> > > > > > > wait_times=wait-times46738
> > > > > > > ; Contains time delays used to time audio
> > > > > > > ; telemetry events
> > > > > > >
> > > > > > >
> > > > > > > ; Echolink settings
> > > > > > >
> > > > > > >
> > > > > > > On Sun, Nov 19, 2017 at 8:38 AM, "Doug Crompton via
> arm-allstar"
> > <
> > > > > > > arm-allstar at hamvoip.org> wrote:
> > > > > > >
> > > > > > > > Jim,
> > > > > > > >
> > > > > > > > Well I don't think your problem is the same as Chris. He was
> > > > > > registered
> > > > > > > > but not receiving node updates. I take it you applied for a
> > node
> > > > > number
> > > > > > > and
> > > > > > > > have heard nothing back? That is another issue. How long has
> it
> > > > been
> > > > > > > since
> > > > > > > > you applied?
> > > > > > > >
> > > > > > > >
> > > > > > > > *73 Doug*
> > > > > > > >
> > > > > > > > *WA3DSP*
> > > > > > > >
> > > > > > > > *http://www.crompton.com/hamradio <http://www.crompton.com/
> > > > hamradio
> > > > > >*
> > > > > > > >
> > > > > > > >
> > > > > > > > On Sun, Nov 19, 2017 at 6:41 AM, "James Hause via
> arm-allstar"
> > <
> > > > > > > > arm-allstar at hamvoip.org> wrote:
> > > > > > > >
> > > > > > > > > Hi Doug,
> > > > > > > > > Hey I received the email trail you have with Chris. I
> > seem
> > > to
> > > > > > have
> > > > > > > > the
> > > > > > > > > same problem, and saw you were going to private email Chris
> > > back.
> > > > > > > > > I applied t get registered on ARM-Allstar, and haven't got
> my
> > > > email
> > > > > > > back
> > > > > > > > > yet with approval,
> > > > > > > > > Sure would like to know what the solution is.
> > > > > > > > >
> > > > > > > > > On Sat, Nov 18, 2017 at 4:21 PM, "Doug Crompton via
> > > arm-allstar"
> > > > <
> > > > > > > > > arm-allstar at hamvoip.org> wrote:
> > > > > > > > >
> > > > > > > > > > Chris,
> > > > > > > > > >
> > > > > > > > > > Yes, I will email you privately about this.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > *73 Doug*
> > > > > > > > > >
> > > > > > > > > > *WA3DSP*
> > > > > > > > > >
> > > > > > > > > > *http://www.crompton.com/hamradio <
> > http://www.crompton.com/
> > > > > > hamradio
> > > > > > > >*
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Sat, Nov 18, 2017 at 4:54 PM, Chris Souleles <
> > > > > > > csouleles at prodigy.net
> > > > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Did the suggested checks and here are the results.
> > > > > > > > > > >
> > > > > > > > > > > Node is registered. Checked several times and it
> always
> > > > comes
> > > > > up
> > > > > > > > > > > registered.
> > > > > > > > > > >
> > > > > > > > > > > When it won't connect I get "no such file or directory"
> > > when
> > > > I
> > > > > > > > execute
> > > > > > > > > > the grep
> > > > > > > > > > > 40000 /tmp/rpt_extnodes command with any node number
> > > inserted
> > > > > > > > replacing
> > > > > > > > > > the
> > > > > > > > > > > 40000.
> > > > > > > > > > >
> > > > > > > > > > > When it will connect I get a routing response for any
> > node
> > > > > > number I
> > > > > > > > > > insert
> > > > > > > > > > > when I execute the command.
> > > > > > > > > > >
> > > > > > > > > > > So it appears when it won't connect it doesn't have the
> > > > > > > > > /tmp/rpt_extnodes
> > > > > > > > > > > file and when it does connect it has it.
> > > > > > > > > > >
> > > > > > > > > > > Is there something I can do to make sure it always has
> > the
> > > > > > > > > > /tmp/rpt_extnodes
> > > > > > > > > > > file after start up?
> > > > > > > > > > >
> > > > > > > > > > > Chris - W6CS - 73.
> > > > > > > > > > > ------------------------------
> > > > > > > > > > > *From:* Doug Crompton via arm-allstar <
> > > > arm-allstar at hamvoip.org
> > > > > >
> > > > > > > > > > > *To:* ARM Allstar <arm-allstar at hamvoip.org>
> > > > > > > > > > > *Cc:* Doug Crompton <wa3dsp at gmail.com>
> > > > > > > > > > > *Sent:* Saturday, November 18, 2017 8:21 AM
> > > > > > > > > > > *Subject:* Re: [arm-allstar] Trouble connecting to
> nodes
> > at
> > > > > start
> > > > > > > up
> > > > > > > > > > >
> > > > > > > > > > > Chris,
> > > > > > > > > > >
> > > > > > > > > > > You checked quite a few things and that is good but
> > there
> > > > > are a
> > > > > > > few
> > > > > > > > > > other
> > > > > > > > > > > things to check. Make sure you have you are registered.
> > You
> > > > can
> > > > > > run
> > > > > > > > > > >
> > > > > > > > > > > check_reg.sh
> > > > > > > > > > >
> > > > > > > > > > > at the Linux prompt.
> > > > > > > > > > >
> > > > > > > > > > > Then make sure you have the /tmp/rpt_extnodes file and
> > that
> > > > it
> > > > > > has
> > > > > > > > the
> > > > > > > > > > info
> > > > > > > > > > > for the node you want to connect to. You can type
> > > > > > > > > > >
> > > > > > > > > > > grep 40000 /tmp/rpt_extnodes
> > > > > > > > > > >
> > > > > > > > > > > at the linux prompt, where 40000 is replaced with the
> > node
> > > > > number
> > > > > > > you
> > > > > > > > > > want
> > > > > > > > > > > to check. This will return the routing info for that
> node
> > > or
> > > > > > > nothing
> > > > > > > > if
> > > > > > > > > > it
> > > > > > > > > > > does not exisit.
> > > > > > > > > > >
> > > > > > > > > > > Also how the system responds when you do a connect
> tells
> > > you
> > > > a
> > > > > > > little
> > > > > > > > > > about
> > > > > > > > > > > what is going on. If you just get a beep or nothing in
> > > > response
> > > > > > to
> > > > > > > a
> > > > > > > > > > > connect it means you have no info for that node and
> > > probably
> > > > no
> > > > > > > > > > rpt_exnodes
> > > > > > > > > > > file. If you get a failure to connect it could mean
> many
> > > > things
> > > > > > but
> > > > > > > > one
> > > > > > > > > > > could be that the other end does not have node
> > information
> > > > for
> > > > > > you.
> > > > > > > > > > >
> > > > > > > > > > > I would also say try and run your node wired if you can
> > to
> > > > see
> > > > > if
> > > > > > > > there
> > > > > > > > > > is
> > > > > > > > > > > a difference.
> > > > > > > > > > >
> > > > > > > > > > > We are about to roll out the DNS node lookup code which
> > > > should
> > > > > > > > > eliminate
> > > > > > > > > > > many of these problems but until then the rpt_extnodes
> > file
> > > > > must
> > > > > > be
> > > > > > > > > there
> > > > > > > > > > > and the node you want to connect to must be listed in
> it.
> > > > > > > > > > >
> > > > > > > > > > > Let us know what you find out.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > *73 Doug*
> > > > > > > > > > >
> > > > > > > > > > > *WA3DSP*
> > > > > > > > > > >
> > > > > > > > > > > *http://www.crompton.com/hamradio <
> > > http://www.crompton.com/
> > > > > > > hamradio
> > > > > > > > >*
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > On Sat, Nov 18, 2017 at 10:39 AM, "Chris Souleles via
> > > > > > arm-allstar"
> > > > > > > <
> > > > > > > > > > > arm-allstar at hamvoip.org> wrote:
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > I've been having trouble getting my node to connect
> to
> > > > other
> > > > > > > nodes
> > > > > > > > > > after
> > > > > > > > > > > > start up. I wait 10 or fifteen minutes after start up
> > and
> > > > > there
> > > > > > > is
> > > > > > > > no
> > > > > > > > > > > > response when I try to connect to another node. I
> have
> > > to
> > > > > halt
> > > > > > > and
> > > > > > > > > > turn
> > > > > > > > > > > > power on and off a few times to get it to work. Once
> > it
> > > > > > connects
> > > > > > > > to
> > > > > > > > > a
> > > > > > > > > > > > node, then after that everything is normal and I can
> > > > connect
> > > > > > and
> > > > > > > > > > > disconnect
> > > > > > > > > > > > with no problem.
> > > > > > > > > > > > It properly reports the IP address. Asterisk shows
> the
> > > > proper
> > > > > > > DTMF
> > > > > > > > > > > > commands. Wireless status indicates the proper
> wireless
> > > > > network
> > > > > > > and
> > > > > > > > > the
> > > > > > > > > > > > correct IP address. The echo command will echo my
> > voice.
> > > > COS
> > > > > > and
> > > > > > > > PTT
> > > > > > > > > > > work.
> > > > > > > > > > > > My cable modem and wireless network work for
> everything
> > > > else.
> > > > > > > > > > > > My configuration is RPI 3, URIx, BF888, simplex node,
> > > and I
> > > > > > > > > downloaded
> > > > > > > > > > > the
> > > > > > > > > > > > hamvoip 1.5 a couple weeks ago so it is pretty
> current.
> > > > I'm
> > > > > > > > > connected
> > > > > > > > > > > > wireless. Any ideas?
> > > > > > > > > > > > Chris - W6CS - 73
> > > > > > > > > > > > Simple USB parameters:Card is: 0Name is:
> > > > usbRx
> > > > > > > Level:
> > > > > > > > > > > > 500Rx no-delay: 0Rx audio-delay: 5Tx A Level:
> > > > > 300Tx B
> > > > > > > > > Level:
> > > > > > > > > > > > 0preemphasis: nodeemphasis: noplfilter:
> > > > > > > yesrxboost:
> > > > > > > > > > > > yesPTT: Active LOWPTT status:
> > > > > Un-KeyedCTCSS
> > > > > > > > > (input):
> > > > > > > > > > > > IgnoredCOS (input): CM108/CM119 Active HIGHCOS
> > > (test):
> > > > > > > > > > > > Un-KeyedCOS (composite): Un-Keyed
> > > > > > > > > > > > Web error log (from Supermon) showed the following.
> I
> > > > don't
> > > > > > know
> > > > > > > > if
> > > > > > > > > it
> > > > > > > > > > > is
> > > > > > > > > > > > relevant.AH00558: httpd: Could not reliably determine
> > the
> > > > > > > server's
> > > > > > > > > > fully
> > > > > > > > > > > > qualified domain name, using 127.0.0.2. Set the
> > > > 'ServerName'
> > > > > > > > > directive
> > > > > > > > > > > > globally to suppress this message[Fri Nov 17
> > > > 20:17:00.884764
> > > > > > > 2017]
> > > > > > > > > > > > [lbmethod_heartbeat:notice] [pid 345] AH02282: No
> > slotmem
> > > > > from
> > > > > > > > > > > > mod_heartmonitor[Fri Nov 17 20:17:01.164689 2017]
> > > > > > > > > [mpm_prefork:notice]
> > > > > > > > > > > [pid
> > > > > > > > > > > > 345] AH00163: Apache/2.4.18 (Unix) PHP/7.0.4
> configured
> > > --
> > > > > > > resuming
> > > > > > > > > > > normal
> > > > > > > > > > > > operations[Fri Nov 17 20:17:01.164882 2017]
> > [core:notice]
> > > > > [pid
> > > > > > > 345]
> > > > > > > > > > > > AH00094: Command line: '/usr/bin/httpd -D FOREGROUND'
> > > > > > > > > > > > _______________________________________________
> > > > > > > > > > > >
> > > > > > > > > > > > arm-allstar mailing list
> > > > > > > > > > > > arm-allstar at hamvoip.org
> > > > > > > > > > > > http://lists.hamvoip.org/cgi-
> bin/mailman/listinfo/arm-
> > > > > allstar
> > > > > > > > > > > >
> > > > > > > > > > > > Visit the BBB and RPi2/3 web page -
> http://hamvoip.org
> > > > > > > > > > >
> > > > > > > > > > > _______________________________________________
> > > > > > > > > > >
> > > > > > > > > > > arm-allstar mailing list
> > > > > > > > > > > arm-allstar at hamvoip.org
> > > > > > > > > > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-
> > > > allstar
> > > > > > > > > > >
> > > > > > > > > > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > _______________________________________________
> > > > > > > > > >
> > > > > > > > > > arm-allstar mailing list
> > > > > > > > > > arm-allstar at hamvoip.org
> > > > > > > > > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-
> > > allstar
> > > > > > > > > >
> > > > > > > > > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > > > > > > > > >
> > > > > > > > > _______________________________________________
> > > > > > > > >
> > > > > > > > > arm-allstar mailing list
> > > > > > > > > arm-allstar at hamvoip.org
> > > > > > > > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-
> > allstar
> > > > > > > > >
> > > > > > > > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > > > > > > > >
> > > > > > > > _______________________________________________
> > > > > > > >
> > > > > > > > arm-allstar mailing list
> > > > > > > > arm-allstar at hamvoip.org
> > > > > > > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-
> allstar
> > > > > > > >
> > > > > > > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > > > > > > >
> > > > > > > _______________________________________________
> > > > > > >
> > > > > > > arm-allstar mailing list
> > > > > > > arm-allstar at hamvoip.org
> > > > > > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > > > > > >
> > > > > > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > > > > > >
> > > > > > _______________________________________________
> > > > > >
> > > > > > arm-allstar mailing list
> > > > > > arm-allstar at hamvoip.org
> > > > > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > > > > >
> > > > > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > > > > >
> > > > > _______________________________________________
> > > > >
> > > > > arm-allstar mailing list
> > > > > arm-allstar at hamvoip.org
> > > > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > > > >
> > > > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > > > >
> > > > _______________________________________________
> > > >
> > > > arm-allstar mailing list
> > > > arm-allstar at hamvoip.org
> > > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > > >
> > > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > > >
> > > _______________________________________________
> > >
> > > arm-allstar mailing list
> > > arm-allstar at hamvoip.org
> > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > >
> > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > >
> > _______________________________________________
> >
> > arm-allstar mailing list
> > arm-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >
> > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> >
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
More information about the arm-allstar
mailing list