[arm-allstar] Advantages of hosted hub node
Joshua Nulton
kg5ebi at gmail.com
Sat Jun 15 16:00:18 EDT 2019
Jesse your use case examples make sense completely for control, and
connectivity of your friends. However you still need to either be within
range of the node/repeater or have internet to use it.
Yes Doug I have a few nodes. :) When I connect to the win or want system I
can hear and communicate using my HT. If that same node were shipped out of
RF range of my HT it would be of no value to me. But you explained it well
when you mentioned the word overkill and I must be in that group.
Thank you for bringing up the matter of dozens of linked nodes, as
efficient as the system is (and you always improving that aspect) I am
certain my little node couldn't handle a social group the size of some of
the larger networks such as the wan system. That is a great use case, as
we're Jesse's points on control and firewalls.
Thank you both,
KG5EBI
On Sat, Jun 15, 2019, 2:39 PM <arm-allstar-request at hamvoip.org> wrote:
> Send ARM-allstar mailing list submissions to
> arm-allstar at hamvoip.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> or, via email, send a message with subject or body 'help' to
> arm-allstar-request at hamvoip.org
>
> You can reach the person managing the list at
> arm-allstar-owner at hamvoip.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of ARM-allstar digest..."
>
>
> Today's Topics:
>
> 1. Re: ERROR[403] chan_echolink.c: (Mike Besemer)
> 2. Re: Advantages of a hosted hub node (Jesse Royall)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 15 Jun 2019 14:52:25 -0400
> From: "Mike Besemer" <mwbesemer at cox.net>
> To: "'ARM Allstar'" <arm-allstar at hamvoip.org>
> Subject: Re: [arm-allstar] ERROR[403] chan_echolink.c:
> Message-ID: <003001d523ab$7bba62d0$732f2870$@cox.net>
> Content-Type: text/plain; charset="us-ascii"
>
> Thanks Doug... been a busy couple of weeks and haven't been keeping up much
> with my emails. Glad it's a simple fix!
>
> 73,
>
> Mike
> WM4B
>
> -----Original Message-----
> From: ARM-allstar [mailto:arm-allstar-bounces at hamvoip.org] On Behalf Of
> "Doug Crompton via ARM-allstar"
> Sent: Saturday, June 15, 2019 11:58 AM
> To: ARM Allstar
> Cc: Doug Crompton
> Subject: Re: [arm-allstar] ERROR[403] chan_echolink.c:
>
> Mike,
>
> Yes that is correct. We had a discussion about this last week. There must
> be three servers defined in echolink.conf but only one has to actually
> work. Server5 has been down for awhile now. You can use server1, 2, and 3
> and that message will go away. That is as long as all of those are working.
> But the bottom line is that as long as one is working and you are getting
> the data from it all is fine. You can check that in the client with -
> echolink dgdump or dbget.
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
> On Sat, Jun 15, 2019 at 11:47 AM "Mike Besemer via ARM-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > Been receiving the error below for several days in AST Log. Echolink
> works
> > fine, so I'm assuming that this is just an issue with a specific Echolink
> > server being unavailable; is that correct?
> >
> > "ERROR[403] chan_echolink.c: connect() failed to connect to the Echolink
> > server server5.echolink.org"
> >
> > 73,
> >
> > Mike
> > WM4B
> >
> >
> >
> > _______________________________________________
> >
> > 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
>
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 15 Jun 2019 14:34:10 -0500
> From: Jesse Royall <w5los at yahoo.com>
> To: ARM Allstar <arm-allstar at hamvoip.org>
> Cc: Doug Crompton <wa3dsp at gmail.com>
> Subject: Re: [arm-allstar] Advantages of a hosted hub node
> Message-ID: <A74DCCC7-3370-43A9-9EBB-D25CC05A7E64 at yahoo.com>
> Content-Type: text/plain; charset=utf-8
>
> Good example of why my radio less node is using google cloud compute.
>
> I travel a lot in my RV and like the echolink connections and the ability
> for people to dial into my node when they choose. However, most parks have
> a firewall I don?t have access to. So I can port forward. At when
> requesting this I get this deer in the headlights look right before it gets
> smacked.
>
> So I setup a ASL node with echolink and a DMR bridge that needed port
> forwarding. The only thing I don?t have is a irlp bridge right now.
>
> Now I can send commands to my remote node and control it and friends can
> connect to me when they want to on demand. So when I?m in a area using
> internet I can?t control, I am connected to it from the park.
>
> Most of the time I just tell people my hosted node if they want to connect
> since I connected to it most of the time.
>
> The other problem I have ran into, my local FD is hosting one of my
> repeaters. Again I can?t control the internet so no one can dial in. Now
> people can dial my hosted node, which is connected permanently, and go out
> the local repeater.
>
> Just a few examples of why I do it.
>
>
> Sent from my iPhone
>
> > On Jun 15, 2019, at 1:59 PM, Doug Crompton via ARM-allstar <
> arm-allstar at hamvoip.org> wrote:
> >
> > Joshua,
> >
> > Are you on Allstar???? It seems like you don't understand the concepts
> of
> > how it operates. The Alstar system connects widely separated nodes via
> the
> > Internet. Your local RF is your business and responsibility. Lets say
> your
> > node was connected to several other repeater nodes throughout the
> country.
> > That means RF users in your area would be able to talk to both operators
> > there and in the other areas you are connected to.
> >
> > I am really not sure what you are missing here? The idea of the hub at a
> > data center is when the owner of the hub does not have good enough
> Internet
> > to have multiple users connecting. So lets say that was the case for you.
> > So you put a hub at a data center, then all those locations including
> > yourself connect to it. You all can talk to each other. You maintain the
> > hub even though it is not at your location.
> >
> > If you are just using Allstar as a repeater controller or you are only
> > connecting on a small scale the data center approach would be way over
> kill.
> >
> >
> > *73 Doug*
> >
> > *WA3DSP*
> >
> > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >
> > On Sat, Jun 15, 2019 at 2:50 PM "Joshua Nulton via ARM-allstar" <
> > arm-allstar at hamvoip.org> wrote:
> >
> >> My final response trying to clarify why I am confused. I guess I am just
> >> stuck on stupid because when I look at my node here in Texas I see an RF
> >> repeater. Sure I could send my node to my brother in Ohio but how would
> >> that help my HT with signal propagation? Whether or not I have internet
> in
> >> Texas, the node being in Ohio certainly will not help me when I press
> the
> >> PTT button from Texas. I am just missing the middle link to how it all
> >> makes sense.
> >>
> >> Computers for example.. I lease servers, but I connect to them with my
> >> laptop. If someone were to lease a node, how would their radio possibly
> >> connect to it?
> >>
> >> Jae
> >> KG5EBI
> >>
> >>> On Sat, Jun 15, 2019, 1:05 PM <arm-allstar-request at hamvoip.org> wrote:
> >>>
> >>> Send ARM-allstar mailing list submissions to
> >>> arm-allstar at hamvoip.org
> >>>
> >>> To subscribe or unsubscribe via the World Wide Web, visit
> >>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >>> or, via email, send a message with subject or body 'help' to
> >>> arm-allstar-request at hamvoip.org
> >>>
> >>> You can reach the person managing the list at
> >>> arm-allstar-owner at hamvoip.org
> >>>
> >>> When replying, please edit your Subject line so it is more specific
> >>> than "Re: Contents of ARM-allstar digest..."
> >>>
> >>>
> >>> Today's Topics:
> >>>
> >>> 1. Re: Advantages of a hosted hub node (Joshua Nulton)
> >>> 2. Help programming ASL on Hamvoip to connect & disconnect at
> >>> particular times (Rachid Karroo)
> >>> 3. Re: Advantages of a hosted hub node (Doug Crompton)
> >>> 4. Re: Help programming ASL on Hamvoip to connect & disconnect
> >>> at particular times (Doug Crompton)
> >>>
> >>>
> >>> ----------------------------------------------------------------------
> >>>
> >>> Message: 1
> >>> Date: Sat, 15 Jun 2019 11:19:16 -0500
> >>> From: Joshua Nulton <kg5ebi at gmail.com>
> >>> To: arm-allstar at hamvoip.org
> >>> Subject: Re: [arm-allstar] Advantages of a hosted hub node
> >>> Message-ID:
> >>> <
> >>> CAOpEAy5SW5VS9tC7xmBKuaerDPfXr7HqffOrFTQmgqZ5SrKUvw at mail.gmail.com>
> >>> Content-Type: text/plain; charset="UTF-8"
> >>>
> >>> I agree most are interested for the "social" aspects. I can think of
> one
> >>> major advantage and that is people that can not forward their ports or
> >> want
> >>> AIX access on the road. They can have their normal node connect
> >>> persistently to their "hub" and forward their DTMF commands to the
> remote
> >>> node, making their personal node more or less act as a proxy to bypass
> >>> connectivity issues.
> >>>
> >>> I guess I am just fishing for more reasons to be interested in the
> >> Pi-Farm
> >>> Doug, where has your marketing intuition gone? haha :)
> >>>
> >>> What would be the advantages of renting space on the farm? I am not
> being
> >>> negative, I really am trying to underatand the idea. :)
> >>>
> >>> KG5EBI
> >>>
> >>>> On Sat, Jun 15, 2019, 11:00 AM <arm-allstar-request at hamvoip.org>
> wrote:
> >>>>
> >>>> Send ARM-allstar mailing list submissions to
> >>>> arm-allstar at hamvoip.org
> >>>>
> >>>> To subscribe or unsubscribe via the World Wide Web, visit
> >>>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >>>> or, via email, send a message with subject or body 'help' to
> >>>> arm-allstar-request at hamvoip.org
> >>>>
> >>>> You can reach the person managing the list at
> >>>> arm-allstar-owner at hamvoip.org
> >>>>
> >>>> When replying, please edit your Subject line so it is more specific
> >>>> than "Re: Contents of ARM-allstar digest..."
> >>>>
> >>>>
> >>>> Today's Topics:
> >>>>
> >>>> 1. Re: use an alternate network interface for vpn (David McGough)
> >>>> 2. Re: Installing SSL cert in HamVoIP image (David McGough)
> >>>> 3. Advantages of hosted hub node (Joshua Nulton)
> >>>> 4. Re: Advantages of hosted hub node (Doug Crompton)
> >>>> 5. ERROR[403] chan_echolink.c: (Mike Besemer)
> >>>> 6. Re: ERROR[403] chan_echolink.c: (Doug Crompton)
> >>>>
> >>>>
> >>>> ----------------------------------------------------------------------
> >>>>
> >>>> Message: 1
> >>>> Date: Sat, 15 Jun 2019 09:45:18 -0400 (EDT)
> >>>> From: David McGough <kb4fxc at inttek.net>
> >>>> To: "\"Tony Ross via ARM-allstar\"" <arm-allstar at hamvoip.org>
> >>>> Subject: Re: [arm-allstar] use an alternate network interface for vpn
> >>>> Message-ID:
> >>>> <Pine.LNX.4.44.1906150943540.26900-100000 at goliath.inttek.net>
> >>>> Content-Type: TEXT/PLAIN; charset=US-ASCII
> >>>>
> >>>>
> >>>>
> >>>> Tony,
> >>>>
> >>>> Did you get this resolved? If not, I'll send you more info for a
> >>>> solution.
> >>>>
> >>>> 73, David KB4FXC
> >>>>
> >>>>
> >>>>
> >>>>> On Thu, 13 Jun 2019, "Tony Ross via ARM-allstar" wrote:
> >>>>>
> >>>>> Sorry for all the "???..." clutter that resulted from a use of
> >>>>> fixed-width font. To re-phrase my request:
> >>>>>
> >>>>> How to use the ztly5vn64v 192.168.192.142 vpn interface, instead of
> >> the
> >>>>> wlan0 192.168.1.30 interface, please.
> >>>>>
> >>>>> _______________________________________________
> >>>>>
> >>>>> 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
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> ------------------------------
> >>>>
> >>>> Message: 2
> >>>> Date: Sat, 15 Jun 2019 09:59:39 -0400 (EDT)
> >>>> From: David McGough <kb4fxc at inttek.net>
> >>>> To: "\"Brad Trogdon via ARM-allstar\"" <arm-allstar at hamvoip.org>
> >>>> Cc: Brad Trogdon <Brad at trogdon.org>
> >>>> Subject: Re: [arm-allstar] Installing SSL cert in HamVoIP image
> >>>> Message-ID:
> >>>> <Pine.LNX.4.44.1906150950120.26900-100000 at goliath.inttek.net>
> >>>> Content-Type: TEXT/PLAIN; charset=US-ASCII
> >>>>
> >>>>
> >>>> Brad,
> >>>>
> >>>> Take a look at the acme-tiny software. It's very easy to use for
> >>>> generating single-site (not wildcard) certificates. If you need info
> >>> for
> >>>> configuring apache/tls in the HamVoIP distro, send me a follow-up
> >>> message.
> >>>>
> >>>> Here is the software. The instructions are on this page, too:
> >>>>
> >>>> https://github.com/diafygi/acme-tiny
> >>>>
> >>>> I'm running apache/tls on several RPi3 systems and it works great.
> >>>>
> >>>>
> >>>> 73, David KB4FXC
> >>>>
> >>>>
> >>>>> On Fri, 14 Jun 2019, "Brad Trogdon via ARM-allstar" wrote:
> >>>>>
> >>>>> Hello all, I anticipate this is kind-off off topic but is specific
> >> to
> >>>> the
> >>>>> HamVoIP image.
> >>>>>
> >>>>> I am current in updates and wanting to install a SSL cert on the
> >>>> Raspberry
> >>>>> Pi which is running my node. I have been directed to Certbot.com and
> >>>> they
> >>>>> have step by step instructions specific to OS and WebServer. In our
> >>> case
> >>>>> Apache and Arch Linux. (URL to Page:
> >>>>> https://certbot.eff.org/lets-encrypt/arch-apache)
> >>>>>
> >>>>> I fail at Step 1 trying to install the packages.
> >>>>>
> >>>>> sudo pacman -S certbot certbot-apache
> >>>>>
> >>>>> Results in error:
> >>>>>
> >>>>> error: target not found: certbot
> >>>>> error: target not found: certbot-apache
> >>>>>
> >>>>> I do not want to break my ability to maintain updates for HamVoIP and
> >>>>> thought I would ask the experts before proceeding.
> >>>>>
> >>>>> Thanks in advance for your wisdom.
> >>>>>
> >>>>> -Brad
> >>>>> ~~
> >>>>> _______________________________________________
> >>>>>
> >>>>> 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
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> ------------------------------
> >>>>
> >>>> Message: 3
> >>>> Date: Sat, 15 Jun 2019 20:59:55 +0700
> >>>> From: Joshua Nulton <kg5ebi at gmail.com>
> >>>> To: arm-allstar at hamvoip.org
> >>>> Subject: [arm-allstar] Advantages of hosted hub node
> >>>> Message-ID:
> >>>> <
> >>>> CAOpEAy4kawustLBR_sByjNNQTSN78mYHSj9ASNM+SndtT7ifZQ at mail.gmail.com>
> >>>> Content-Type: text/plain; charset="UTF-8"
> >>>>
> >>>> I know some have said an off site hosted link node could be
> >> advantageous
> >>> to
> >>>> those with poor to no internet and I can't wrap my head around that,
> >> but
> >>> I
> >>>> am sure there must be numerous advantages to having a hub node. Could
> >>> y'all
> >>>> name as many as you can think of please?
> >>>>
> >>>> Thanks,
> >>>> Jae
> >>>> KG5EBI
> >>>>
> >>>>
> >>>> ------------------------------
> >>>>
> >>>> Message: 4
> >>>> Date: Sat, 15 Jun 2019 11:12:18 -0400
> >>>> From: Doug Crompton <wa3dsp at gmail.com>
> >>>> To: ARM Allstar <arm-allstar at hamvoip.org>
> >>>> Subject: Re: [arm-allstar] Advantages of hosted hub node
> >>>> Message-ID:
> >>>> <
> >>>> CAMp6vsuteaXnqdurX4FLh0gnQW8YamB++68cUFfomiHWwwsNbQ at mail.gmail.com>
> >>>> Content-Type: text/plain; charset="UTF-8"
> >>>>
> >>>> Joshua,
> >>>>
> >>>> In Allstar people tend to conflate the word "hub" with something
> >> special.
> >>>> Maybe it is because on IRLP where you have to ask for permission to be
> >>>> granted and run a reflector. In Allstar terminology a "hub" is simply
> >> a
> >>>> connection point where there are two or more other nodes connected. It
> >> is
> >>>> an understanding among a group of people that they will all connect to
> >>> one
> >>>> node. Anyone can create a "hub" in Allstar. There is nothing special
> >>> about
> >>>> it and no special configuration. As long as you have the Internet
> >>> bandwidth
> >>>> to do it, and in this day and age most do, you can set one up. It is
> >>> more a
> >>>> matter of advertising than anything else. Running hamvoip in turbo
> mode
> >>>> without any radios a single server could easily handle 60+
> connections.
> >>>> There are very few "hubs" that have that many connections and in a
> case
> >>>> where they might the load can be distributed over more than one
> server.
> >>>> This is the beauty of Allstar because you have the flexibility to
> >> create
> >>>> and do this. Here is Philadelphia I run at least three hubs using 10
> >>> local
> >>>> servers and several remote. There are more than 65 direct connections
> >>>> throughout the world. This is all done on Pi's and on a single Comcast
> >>>> Internet connection.
> >>>>
> >>>>
> >>>> *73 Doug*
> >>>>
> >>>> *WA3DSP*
> >>>>
> >>>> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >>>>
> >>>> On Sat, Jun 15, 2019 at 10:01 AM "Joshua Nulton via ARM-allstar" <
> >>>> arm-allstar at hamvoip.org> wrote:
> >>>>
> >>>>> I know some have said an off site hosted link node could be
> >>> advantageous
> >>>> to
> >>>>> those with poor to no internet and I can't wrap my head around that,
> >>> but
> >>>> I
> >>>>> am sure there must be numerous advantages to having a hub node. Could
> >>>> y'all
> >>>>> name as many as you can think of please?
> >>>>>
> >>>>> Thanks,
> >>>>> Jae
> >>>>> KG5EBI
> >>>>> _______________________________________________
> >>>>>
> >>>>> 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
> >>>>>
> >>>>
> >>>>
> >>>> ------------------------------
> >>>>
> >>>> Message: 5
> >>>> Date: Sat, 15 Jun 2019 11:44:49 -0400
> >>>> From: "Mike Besemer" <mwbesemer at cox.net>
> >>>> To: "ARM Allstar" <arm-allstar at hamvoip.org>
> >>>> Subject: [arm-allstar] ERROR[403] chan_echolink.c:
> >>>> Message-ID: <001501d52391$449ba9e0$cdd2fda0$@cox.net>
> >>>> Content-Type: text/plain; charset="us-ascii"
> >>>>
> >>>> Been receiving the error below for several days in AST Log. Echolink
> >>> works
> >>>> fine, so I'm assuming that this is just an issue with a specific
> >> Echolink
> >>>> server being unavailable; is that correct?
> >>>>
> >>>> "ERROR[403] chan_echolink.c: connect() failed to connect to the
> >> Echolink
> >>>> server server5.echolink.org"
> >>>>
> >>>> 73,
> >>>>
> >>>> Mike
> >>>> WM4B
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> ------------------------------
> >>>>
> >>>> Message: 6
> >>>> Date: Sat, 15 Jun 2019 11:57:53 -0400
> >>>> From: Doug Crompton <wa3dsp at gmail.com>
> >>>> To: ARM Allstar <arm-allstar at hamvoip.org>
> >>>> Subject: Re: [arm-allstar] ERROR[403] chan_echolink.c:
> >>>> Message-ID:
> >>>> <CAMp6vsu0Ac4wp-KsWtBg--3CW8vYyL0G=
> >>>> yy2wg0gU8bRrAYrNw at mail.gmail.com>
> >>>> Content-Type: text/plain; charset="UTF-8"
> >>>>
> >>>> Mike,
> >>>>
> >>>> Yes that is correct. We had a discussion about this last week. There
> >>> must
> >>>> be three servers defined in echolink.conf but only one has to actually
> >>>> work. Server5 has been down for awhile now. You can use server1, 2,
> >> and
> >>> 3
> >>>> and that message will go away. That is as long as all of those are
> >>> working.
> >>>> But the bottom line is that as long as one is working and you are
> >> getting
> >>>> the data from it all is fine. You can check that in the client with
> -
> >>>> echolink dgdump or dbget.
> >>>>
> >>>>
> >>>> *73 Doug*
> >>>>
> >>>> *WA3DSP*
> >>>>
> >>>> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >>>>
> >>>> On Sat, Jun 15, 2019 at 11:47 AM "Mike Besemer via ARM-allstar" <
> >>>> arm-allstar at hamvoip.org> wrote:
> >>>>
> >>>>> Been receiving the error below for several days in AST Log. Echolink
> >>>> works
> >>>>> fine, so I'm assuming that this is just an issue with a specific
> >>> Echolink
> >>>>> server being unavailable; is that correct?
> >>>>>
> >>>>> "ERROR[403] chan_echolink.c: connect() failed to connect to the
> >>> Echolink
> >>>>> server server5.echolink.org"
> >>>>>
> >>>>> 73,
> >>>>>
> >>>>> Mike
> >>>>> WM4B
> >>>>>
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>>
> >>>>> 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
> >>>>>
> >>>>
> >>>>
> >>>> ------------------------------
> >>>>
> >>>> Subject: Digest Footer
> >>>>
> >>>> _______________________________________________
> >>>> ARM-allstar mailing list
> >>>> ARM-allstar at hamvoip.org
> >>>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >>>>
> >>>>
> >>>> ------------------------------
> >>>>
> >>>> End of ARM-allstar Digest, Vol 61, Issue 12
> >>>> *******************************************
> >>>>
> >>>
> >>>
> >>> ------------------------------
> >>>
> >>> Message: 2
> >>> Date: Sat, 15 Jun 2019 20:34:58 +0400
> >>> From: Rachid Karroo <rkarroo at gmail.com>
> >>> To: ARM Allstar <arm-allstar at hamvoip.org>
> >>> Subject: [arm-allstar] Help programming ASL on Hamvoip to connect &
> >>> disconnect at particular times
> >>> Message-ID:
> >>> <
> >>> CACOzSbnCqaPVM2+Af+aMjkjtGhiNTEwZx4Ed9kbwyAMbDr9kxg at mail.gmail.com>
> >>> Content-Type: text/plain; charset="UTF-8"
> >>>
> >>> Good day to all
> >>> I need to have my node to connect and disconnect to a particular
> Node(s)
> >>> during week days.
> >>>
> >>> I understand that I will have to define it in Cron jobs.
> >>> Is there any documentation available that I could read and experiment
> >>> please ?
> >>>
> >>> Thank you
> >>> 73's
> >>>
> >>> Rachid
> >>> 3B8FP
> >>> Node 40248
> >>>
> >>>
> >>> ------------------------------
> >>>
> >>> Message: 3
> >>> Date: Sat, 15 Jun 2019 13:44:48 -0400
> >>> From: Doug Crompton <wa3dsp at gmail.com>
> >>> To: ARM Allstar <arm-allstar at hamvoip.org>
> >>> Subject: Re: [arm-allstar] Advantages of a hosted hub node
> >>> Message-ID:
> >>> <
> >>> CAMp6vsuiOApx29iFoiHE+-RoAun8ofvv5HO0Lj-GvaHhe_mTFQ at mail.gmail.com>
> >>> Content-Type: text/plain; charset="UTF-8"
> >>>
> >>> Joshua,
> >>>
> >>> The only reason in my mind to have a server at a data center is if you
> >> do
> >>> not have good or any Internet connectibility. This is the case for more
> >>> people in the US than most know. Obviously not in major metropolitan
> >> areas
> >>> but the US is way behind in both Internet connectivity and quality.
> Many
> >>> other countries surpass us in getting good Internet to everyone that
> >> wants
> >>> it. So in those cases the only alternative is to put the server
> >> somewhere
> >>> that has good Internet like a data center. The Pi farm has that in
> mind.
> >>> Why have a PC running Allstar virtually, which BTW does not always work
> >>> that well, when you can have a real Pi server running there with the
> best
> >>> Internet possible. So that is the reason for the Pi farm. If you have
> >>> Internet and are not having issues with connectivity that you don't
> need
> >> a
> >>> node at a data center. I think in the past, like 10 or more years ago,
> it
> >>> was the norm to have large hubs run from data centers. This is no
> longer
> >>> the case unless you are out in the sticks and have little or no
> Internet.
> >>> Unfortunately that mindset still lingers.
> >>>
> >>>
> >>> *73 Doug*
> >>>
> >>> *WA3DSP*
> >>>
> >>> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >>>
> >>>
> >>> On Sat, Jun 15, 2019 at 12:39 PM "Joshua Nulton via ARM-allstar" <
> >>> arm-allstar at hamvoip.org> wrote:
> >>>
> >>>> I agree most are interested for the "social" aspects. I can think of
> >> one
> >>>> major advantage and that is people that can not forward their ports or
> >>> want
> >>>> AIX access on the road. They can have their normal node connect
> >>>> persistently to their "hub" and forward their DTMF commands to the
> >> remote
> >>>> node, making their personal node more or less act as a proxy to bypass
> >>>> connectivity issues.
> >>>>
> >>>> I guess I am just fishing for more reasons to be interested in the
> >>> Pi-Farm
> >>>> Doug, where has your marketing intuition gone? haha :)
> >>>>
> >>>> What would be the advantages of renting space on the farm? I am not
> >> being
> >>>> negative, I really am trying to underatand the idea. :)
> >>>>
> >>>> KG5EBI
> >>>>
> >>>> On Sat, Jun 15, 2019, 11:00 AM <arm-allstar-request at hamvoip.org>
> >> wrote:
> >>>>
> >>>>> Send ARM-allstar mailing list submissions to
> >>>>> arm-allstar at hamvoip.org
> >>>>>
> >>>>> To subscribe or unsubscribe via the World Wide Web, visit
> >>>>>
> >> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >>>>> or, via email, send a message with subject or body 'help' to
> >>>>> arm-allstar-request at hamvoip.org
> >>>>>
> >>>>> You can reach the person managing the list at
> >>>>> arm-allstar-owner at hamvoip.org
> >>>>>
> >>>>> When replying, please edit your Subject line so it is more specific
> >>>>> than "Re: Contents of ARM-allstar digest..."
> >>>>>
> >>>>>
> >>>>> Today's Topics:
> >>>>>
> >>>>> 1. Re: use an alternate network interface for vpn (David McGough)
> >>>>> 2. Re: Installing SSL cert in HamVoIP image (David McGough)
> >>>>> 3. Advantages of hosted hub node (Joshua Nulton)
> >>>>> 4. Re: Advantages of hosted hub node (Doug Crompton)
> >>>>> 5. ERROR[403] chan_echolink.c: (Mike Besemer)
> >>>>> 6. Re: ERROR[403] chan_echolink.c: (Doug Crompton)
> >>>>>
> >>>>>
> >>>>>
> >> ----------------------------------------------------------------------
> >>>>>
> >>>>> Message: 1
> >>>>> Date: Sat, 15 Jun 2019 09:45:18 -0400 (EDT)
> >>>>> From: David McGough <kb4fxc at inttek.net>
> >>>>> To: "\"Tony Ross via ARM-allstar\"" <arm-allstar at hamvoip.org>
> >>>>> Subject: Re: [arm-allstar] use an alternate network interface for vpn
> >>>>> Message-ID:
> >>>>> <Pine.LNX.4.44.1906150943540.26900-100000 at goliath.inttek.net
> >>>
> >>>>> Content-Type: TEXT/PLAIN; charset=US-ASCII
> >>>>>
> >>>>>
> >>>>>
> >>>>> Tony,
> >>>>>
> >>>>> Did you get this resolved? If not, I'll send you more info for a
> >>>>> solution.
> >>>>>
> >>>>> 73, David KB4FXC
> >>>>>
> >>>>>
> >>>>>
> >>>>>> On Thu, 13 Jun 2019, "Tony Ross via ARM-allstar" wrote:
> >>>>>>
> >>>>>> Sorry for all the "???..." clutter that resulted from a use of
> >>>>>> fixed-width font. To re-phrase my request:
> >>>>>>
> >>>>>> How to use the ztly5vn64v 192.168.192.142 vpn interface, instead of
> >>> the
> >>>>>> wlan0 192.168.1.30 interface, please.
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>>
> >>>>>> 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
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> ------------------------------
> >>>>>
> >>>>> Message: 2
> >>>>> Date: Sat, 15 Jun 2019 09:59:39 -0400 (EDT)
> >>>>> From: David McGough <kb4fxc at inttek.net>
> >>>>> To: "\"Brad Trogdon via ARM-allstar\"" <arm-allstar at hamvoip.org>
> >>>>> Cc: Brad Trogdon <Brad at trogdon.org>
> >>>>> Subject: Re: [arm-allstar] Installing SSL cert in HamVoIP image
> >>>>> Message-ID:
> >>>>> <Pine.LNX.4.44.1906150950120.26900-100000 at goliath.inttek.net
> >>>
> >>>>> Content-Type: TEXT/PLAIN; charset=US-ASCII
> >>>>>
> >>>>>
> >>>>> Brad,
> >>>>>
> >>>>> Take a look at the acme-tiny software. It's very easy to use for
> >>>>> generating single-site (not wildcard) certificates. If you need
> >> info
> >>>> for
> >>>>> configuring apache/tls in the HamVoIP distro, send me a follow-up
> >>>> message.
> >>>>>
> >>>>> Here is the software. The instructions are on this page, too:
> >>>>>
> >>>>> https://github.com/diafygi/acme-tiny
> >>>>>
> >>>>> I'm running apache/tls on several RPi3 systems and it works great.
> >>>>>
> >>>>>
> >>>>> 73, David KB4FXC
> >>>>>
> >>>>>
> >>>>>> On Fri, 14 Jun 2019, "Brad Trogdon via ARM-allstar" wrote:
> >>>>>>
> >>>>>> Hello all, I anticipate this is kind-off off topic but is specific
> >>> to
> >>>>> the
> >>>>>> HamVoIP image.
> >>>>>>
> >>>>>> I am current in updates and wanting to install a SSL cert on the
> >>>>> Raspberry
> >>>>>> Pi which is running my node. I have been directed to Certbot.com
> >> and
> >>>>> they
> >>>>>> have step by step instructions specific to OS and WebServer. In
> >> our
> >>>> case
> >>>>>> Apache and Arch Linux. (URL to Page:
> >>>>>> https://certbot.eff.org/lets-encrypt/arch-apache)
> >>>>>>
> >>>>>> I fail at Step 1 trying to install the packages.
> >>>>>>
> >>>>>> sudo pacman -S certbot certbot-apache
> >>>>>>
> >>>>>> Results in error:
> >>>>>>
> >>>>>> error: target not found: certbot
> >>>>>> error: target not found: certbot-apache
> >>>>>>
> >>>>>> I do not want to break my ability to maintain updates for HamVoIP
> >> and
> >>>>>> thought I would ask the experts before proceeding.
> >>>>>>
> >>>>>> Thanks in advance for your wisdom.
> >>>>>>
> >>>>>> -Brad
> >>>>>> ~~
> >>>>>> _______________________________________________
> >>>>>>
> >>>>>> 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
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> ------------------------------
> >>>>>
> >>>>> Message: 3
> >>>>> Date: Sat, 15 Jun 2019 20:59:55 +0700
> >>>>> From: Joshua Nulton <kg5ebi at gmail.com>
> >>>>> To: arm-allstar at hamvoip.org
> >>>>> Subject: [arm-allstar] Advantages of hosted hub node
> >>>>> Message-ID:
> >>>>> <
> >>>>> CAOpEAy4kawustLBR_sByjNNQTSN78mYHSj9ASNM+SndtT7ifZQ at mail.gmail.com>
> >>>>> Content-Type: text/plain; charset="UTF-8"
> >>>>>
> >>>>> I know some have said an off site hosted link node could be
> >>> advantageous
> >>>> to
> >>>>> those with poor to no internet and I can't wrap my head around that,
> >>> but
> >>>> I
> >>>>> am sure there must be numerous advantages to having a hub node. Could
> >>>> y'all
> >>>>> name as many as you can think of please?
> >>>>>
> >>>>> Thanks,
> >>>>> Jae
> >>>>> KG5EBI
> >>>>>
> >>>>>
> >>>>> ------------------------------
> >>>>>
> >>>>> Message: 4
> >>>>> Date: Sat, 15 Jun 2019 11:12:18 -0400
> >>>>> From: Doug Crompton <wa3dsp at gmail.com>
> >>>>> To: ARM Allstar <arm-allstar at hamvoip.org>
> >>>>> Subject: Re: [arm-allstar] Advantages of hosted hub node
> >>>>> Message-ID:
> >>>>> <
> >>>>> CAMp6vsuteaXnqdurX4FLh0gnQW8YamB++68cUFfomiHWwwsNbQ at mail.gmail.com>
> >>>>> Content-Type: text/plain; charset="UTF-8"
> >>>>>
> >>>>> Joshua,
> >>>>>
> >>>>> In Allstar people tend to conflate the word "hub" with something
> >>> special.
> >>>>> Maybe it is because on IRLP where you have to ask for permission to
> >> be
> >>>>> granted and run a reflector. In Allstar terminology a "hub" is
> >> simply
> >>> a
> >>>>> connection point where there are two or more other nodes connected.
> >> It
> >>> is
> >>>>> an understanding among a group of people that they will all connect
> >> to
> >>>> one
> >>>>> node. Anyone can create a "hub" in Allstar. There is nothing special
> >>>> about
> >>>>> it and no special configuration. As long as you have the Internet
> >>>> bandwidth
> >>>>> to do it, and in this day and age most do, you can set one up. It is
> >>>> more a
> >>>>> matter of advertising than anything else. Running hamvoip in turbo
> >> mode
> >>>>> without any radios a single server could easily handle 60+
> >> connections.
> >>>>> There are very few "hubs" that have that many connections and in a
> >> case
> >>>>> where they might the load can be distributed over more than one
> >> server.
> >>>>> This is the beauty of Allstar because you have the flexibility to
> >>> create
> >>>>> and do this. Here is Philadelphia I run at least three hubs using 10
> >>>> local
> >>>>> servers and several remote. There are more than 65 direct connections
> >>>>> throughout the world. This is all done on Pi's and on a single
> >> Comcast
> >>>>> Internet connection.
> >>>>>
> >>>>>
> >>>>> *73 Doug*
> >>>>>
> >>>>> *WA3DSP*
> >>>>>
> >>>>> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio
> >>> *
> >>>>>
> >>>>> On Sat, Jun 15, 2019 at 10:01 AM "Joshua Nulton via ARM-allstar" <
> >>>>> arm-allstar at hamvoip.org> wrote:
> >>>>>
> >>>>>> I know some have said an off site hosted link node could be
> >>>> advantageous
> >>>>> to
> >>>>>> those with poor to no internet and I can't wrap my head around
> >> that,
> >>>> but
> >>>>> I
> >>>>>> am sure there must be numerous advantages to having a hub node.
> >> Could
> >>>>> y'all
> >>>>>> name as many as you can think of please?
> >>>>>>
> >>>>>> Thanks,
> >>>>>> Jae
> >>>>>> KG5EBI
> >>>>>> _______________________________________________
> >>>>>>
> >>>>>> 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
> >>>>>>
> >>>>>
> >>>>>
> >>>>> ------------------------------
> >>>>>
> >>>>> Message: 5
> >>>>> Date: Sat, 15 Jun 2019 11:44:49 -0400
> >>>>> From: "Mike Besemer" <mwbesemer at cox.net>
> >>>>> To: "ARM Allstar" <arm-allstar at hamvoip.org>
> >>>>> Subject: [arm-allstar] ERROR[403] chan_echolink.c:
> >>>>> Message-ID: <001501d52391$449ba9e0$cdd2fda0$@cox.net>
> >>>>> Content-Type: text/plain; charset="us-ascii"
> >>>>>
> >>>>> Been receiving the error below for several days in AST Log. Echolink
> >>>> works
> >>>>> fine, so I'm assuming that this is just an issue with a specific
> >>> Echolink
> >>>>> server being unavailable; is that correct?
> >>>>>
> >>>>> "ERROR[403] chan_echolink.c: connect() failed to connect to the
> >>> Echolink
> >>>>> server server5.echolink.org"
> >>>>>
> >>>>> 73,
> >>>>>
> >>>>> Mike
> >>>>> WM4B
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> ------------------------------
> >>>>>
> >>>>> Message: 6
> >>>>> Date: Sat, 15 Jun 2019 11:57:53 -0400
> >>>>> From: Doug Crompton <wa3dsp at gmail.com>
> >>>>> To: ARM Allstar <arm-allstar at hamvoip.org>
> >>>>> Subject: Re: [arm-allstar] ERROR[403] chan_echolink.c:
> >>>>> Message-ID:
> >>>>> <CAMp6vsu0Ac4wp-KsWtBg--3CW8vYyL0G=
> >>>>> yy2wg0gU8bRrAYrNw at mail.gmail.com>
> >>>>> Content-Type: text/plain; charset="UTF-8"
> >>>>>
> >>>>> Mike,
> >>>>>
> >>>>> Yes that is correct. We had a discussion about this last week. There
> >>>> must
> >>>>> be three servers defined in echolink.conf but only one has to
> >> actually
> >>>>> work. Server5 has been down for awhile now. You can use server1, 2,
> >>> and
> >>>> 3
> >>>>> and that message will go away. That is as long as all of those are
> >>>> working.
> >>>>> But the bottom line is that as long as one is working and you are
> >>> getting
> >>>>> the data from it all is fine. You can check that in the client
> >> with -
> >>>>> echolink dgdump or dbget.
> >>>>>
> >>>>>
> >>>>> *73 Doug*
> >>>>>
> >>>>> *WA3DSP*
> >>>>>
> >>>>> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio
> >>> *
> >>>>>
> >>>>> On Sat, Jun 15, 2019 at 11:47 AM "Mike Besemer via ARM-allstar" <
> >>>>> arm-allstar at hamvoip.org> wrote:
> >>>>>
> >>>>>> Been receiving the error below for several days in AST Log.
> >> Echolink
> >>>>> works
> >>>>>> fine, so I'm assuming that this is just an issue with a specific
> >>>> Echolink
> >>>>>> server being unavailable; is that correct?
> >>>>>>
> >>>>>> "ERROR[403] chan_echolink.c: connect() failed to connect to the
> >>>> Echolink
> >>>>>> server server5.echolink.org"
> >>>>>>
> >>>>>> 73,
> >>>>>>
> >>>>>> Mike
> >>>>>> WM4B
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>>
> >>>>>> 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
> >>>>>>
> >>>>>
> >>>>>
> >>>>> ------------------------------
> >>>>>
> >>>>> Subject: Digest Footer
> >>>>>
> >>>>> _______________________________________________
> >>>>> ARM-allstar mailing list
> >>>>> ARM-allstar at hamvoip.org
> >>>>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >>>>>
> >>>>>
> >>>>> ------------------------------
> >>>>>
> >>>>> End of ARM-allstar Digest, Vol 61, Issue 12
> >>>>> *******************************************
> >>>>>
> >>>> _______________________________________________
> >>>>
> >>>> 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
> >>>>
> >>>
> >>>
> >>> ------------------------------
> >>>
> >>> Message: 4
> >>> Date: Sat, 15 Jun 2019 14:05:25 -0400
> >>> From: Doug Crompton <wa3dsp at gmail.com>
> >>> To: ARM Allstar <arm-allstar at hamvoip.org>
> >>> Subject: Re: [arm-allstar] Help programming ASL on Hamvoip to connect
> >>> & disconnect at particular times
> >>> Message-ID:
> >>> <
> >>> CAMp6vstANaUzZ-XR4sWiNcx0W49KDs620PDqJ-1N0CfmBjij6A at mail.gmail.com>
> >>> Content-Type: text/plain; charset="UTF-8"
> >>>
> >>> Rachid,
> >>>
> >>> This is very easy. You could do it in rpt.conf but If you want to do it
> >> in
> >>> a cron (that is the way I do it here) you need to understand cron.
> >> There
> >>> are many sites that detail how to use it. Here is one -
> >>>
> >>> https://www.adminschoice.com/crontab-quick-reference
> >>>
> >>> So that shows you how to setup times days etc.
> >>>
> >>> So lets say you want to connect a specific node at a certain time and
> >> day.
> >>> You use crontab -e and you are in the editor. Here is an example.
> There
> >>> are spaces between the parameters! -
> >>>
> >>> # Connect to a node
> >>> 30 20 * * 1 /etc/asterisk/local/connect.sh 40000
> >>>
> >>> Using the script below this would connect node 40000 to your node at
> 8:30
> >>> PM on Monday night. Remember the first parameter is minutes and the
> >> second
> >>> is hour in 24 hour time. The week starts on Sunday which is 0 so the 1
> is
> >>> monday.
> >>>
> >>> Script the cron calls -
> >>>
> >>> #!/bin/bash
> >>> asterisk -rx "rpt fun $NODE1 *73$1"
> >>>
> >>> $NODE1 is your first node. If it is a different node on that server
> >> replace
> >>> with the node number. The $1 is the node parameter passed from the
> cron.
> >>>
> >>> Save this in /etc/asterisk/local/connect.sh and make it executable -
> >> chmod
> >>> 755 connect.sh
> >>>
> >>> Now at the prescribed time it will connect to the requested node. You
> >>> could make another script called disconnect.sh. The lines would just
> be -
> >>>
> >>> #!/bin/bash
> >>> asterisk -rx "rpt fun $NODE1 *71$1"
> >>>
> >>> I show permanent connects here but it could be *3 and *1 if you did not
> >>> want that. Usually you want permanent connects though.
> >>>
> >>> The flexibility of using a script would allow you to add things if you
> >> like
> >>> for instance you could connect to multiple nodes and do other commands
> >>> within the script.
> >>>
> >>>
> >>> *73 Doug*
> >>>
> >>> *WA3DSP*
> >>>
> >>> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >>>
> >>> On Sat, Jun 15, 2019 at 12:39 PM "Rachid Karroo via ARM-allstar" <
> >>> arm-allstar at hamvoip.org> wrote:
> >>>
> >>>> Good day to all
> >>>> I need to have my node to connect and disconnect to a particular
> >> Node(s)
> >>>> during week days.
> >>>>
> >>>> I understand that I will have to define it in Cron jobs.
> >>>> Is there any documentation available that I could read and experiment
> >>>> please ?
> >>>>
> >>>> Thank you
> >>>> 73's
> >>>>
> >>>> Rachid
> >>>> 3B8FP
> >>>> Node 40248
> >>>> _______________________________________________
> >>>>
> >>>> 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
> >>>>
> >>>
> >>>
> >>> ------------------------------
> >>>
> >>> Subject: Digest Footer
> >>>
> >>> _______________________________________________
> >>> ARM-allstar mailing list
> >>> ARM-allstar at hamvoip.org
> >>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >>>
> >>>
> >>> ------------------------------
> >>>
> >>> End of ARM-allstar Digest, Vol 61, Issue 13
> >>> *******************************************
> >>>
> >> _______________________________________________
> >>
> >> 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
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> ARM-allstar mailing list
> ARM-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
>
> ------------------------------
>
> End of ARM-allstar Digest, Vol 61, Issue 16
> *******************************************
>
More information about the ARM-allstar
mailing list