[arm-allstar] Echolink Hiccup

John wb5nfc at gmail.com
Tue Jan 31 16:33:07 EST 2017 

Sorry, Doug. I should have been more specific. We travel full-time, so
there is no such thing as a normal Internet connection for us. Internet
service in most RV RV parks is deplorable. I've never been able to make any
park connection work for very long with Allstar/Echolink. My best bet has
always been to use our ATT WiFi hotspot for Allstar/Echolink.

We use a (WifiRanger Go2) router that is designed primarily for RVers. It's
a Mikrotic with custom firmware that automatically scans for available Wifi
signals and performs some other magic that makes life easier for travelers.
I would normally connect my node to the Go2. The Go2 router would be
connected to the ATT hotspot via Wifi. With OpenVPN configured on the Pi
and an open port plan through Strong VPN, this setup worked well for
several months. Since we have been in the Tucson area, I've had trouble
staying logged into Allstar and great difficulty receiving calls on
Echolink. With the new image available, I've been trying to simplify my
setup and get things going with less hastle. I had already configured the
VPN as part of setting up the new image and I knew it was working before --
that's why I chose to give it a try.  As for the port forwarding... in
addition to the ATT hotspot, I also have a Verizon hotspot. It's on a
different IP range than the ATT. In some areas the ATT works, in others the
Verizon. When I switch hotspots because of poor performance OR because we
are running out of minutes, it requires changing the port forwarding to a
different IP address -- and it's a real pain on this router.

That's the background on why I'm going about things the way I have. I'm
just looking for the easiest way to make all these parts and pieces work
and play well together.

After receiving your last email, I went back to check the configuration of
my nodes on the allstarlink.org web site. I have several node numbers
assigned, but I only keep one active while traveling. I'm attempting to
configure Allstar node 27911 with v1.5 firmware. Node 27911 resides on my
"WB5NFC-RPi" server. My 2347 node is aso assigned to that server (but it is
not turned on). I noticed that my Echolink node (41398 - WB5NFC-R) is
currently assigned to Allstar node 2347. When I try to change it to Allstar
node 27911, the change won't "stick". I've tried several times (even logged
out/logged back in and changed browsers). I have double-checked to ensure
I'm clicking on the "Save" button after making changes on the Allstar site.
I remember that one of your emails mentions that only a few parameters on
Allstarlink.org page directly impact node operation -- but I don't remember
exactly what (except probably the bind port).

Sorry for the tome...

John



On Tue, Jan 31, 2017 at 1:30 PM, "Doug Crompton via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

> John,
>
>  It is difficult to troubleshoot not knowing exactly how you have things
> setup. My question would be if you are going to abandon the VPN in a month
> then why use it now just because you have a month left. If you have a
> normal Internet connection you do not need VPN for Allstar or Echolink.
> Setup your router with Echolink and Allstar port forwarding if that is
> possible to do in your situation.
>
>
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
> On Tue, Jan 31, 2017 at 2:38 PM, "John via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > Yes, worked before... BUT... rather than blow away an old operational and
> > fully-configured node, I'm trying to bring up one of my other node
> numbers.
> > I'm going back over server-side configuration now. As I mentioned
> earlier,
> > I'm using a VPN server for the time being since it's paid up for another
> > month or so. The VPN appears to be connecting properly and serving up an
> IP
> > to the Pi.
> >
> > Clarification, please:  Don't I remember reading that if a VPN is in use
> > (properly configured on the Pi) that port forwarding is not needed -- IF
> > the ports are open on the VPN? If that's not the case, that's my
> issue....
> >
> > John
> >
> > On Tue, Jan 31, 2017 at 11:32 AM, "Doug Crompton via arm-allstar" <
> > arm-allstar at hamvoip.org> wrote:
> >
> > > John,
> > >
> > >  You have to give me more details about this. Did it work the way you
> had
> > > it connected to the network in the prior way? I doubt this has anything
> > to
> > > do with Allstar unless you changed something in one of the files
> > manually.
> > >
> > > Remember Echolink unlike Allstar requires port forwarding. If that is
> not
> > > in place it is not going to work.
> > >
> > >
> > >
> > > *73 Doug*
> > >
> > > *WA3DSP*
> > >
> > > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> > >
> > > On Tue, Jan 31, 2017 at 12:37 PM, "John via arm-allstar" <
> > > arm-allstar at hamvoip.org> wrote:
> > >
> > > > I completed rebuilding node 27911 recently with the new image. Many
> > > thanks
> > > > to everyone involved in its development. Other than self-inflicted
> > > > problems, the install was a piece of cake. GREAT work, team!
> > > >
> > > > Doug's recent email addressing multiple routers in a network got me
> to
> > > > thinking about my situation using a hotspot while traveling. The
> > hotspot
> > > > acts as a router AND then I was connecting it through another router
> > for
> > > my
> > > > motorhome network. I've reconfigured the Pi3 to connect directly to
> the
> > > > hotspot via WiFi. This seems to have helped a great deal with the
> > dropped
> > > > IP problems I was experiencing. I left the system "up" last night and
> > CLI
> > > > prompts this morning showed everything to be operating normally.
> > However,
> > > > when an Echolink station attempted to connect this morning, he was
> > unable
> > > > to do so. Here's what the CLI has to say about the session:
> > > >
> > > >     -- Received OK from Echolink server server1.echolink.org
> > > >     -- Directory pgm done downloading(partial,compressed), 570
> records
> > > >     -- Remote UNIX connection
> > > >     -- Remote UNIX connection disconnected
> > > >     -- <DAHDI/pseudo-1781694877> Playing '/tmp/current-time'
> (language
> > > > 'en')
> > > >     -- Hungup 'DAHDI/pseudo-1781694877'
> > > >     -- Received OK from Echolink server server1.echolink.org
> > > >     -- Directory pgm done downloading(partial,compressed), 432
> records
> > > >   == Refreshing DNS lookups.
> > > >     -- new CALL=K0JXI,ip=75.64.107.181,name=        Dale
> > > >   == Starting echolink/el0-0 at radio-secure,47911,1 failed so
> falling
> > > back
> > > > to exten 's'
> > > >   == Starting echolink/el0-0 at radio-secure,s,1 still failed so
> > falling
> > > > back to context 'default'
> > > >     -- Sent into invalid extension 's' in context 'default' on
> > > > echolink/el0-0
> > > >     -- Executing [i at default:1] Hangup("echolink/el0-0", "") in new
> > stack
> > > >   == Spawn extension (default, i, 1) exited non-zero on
> > 'echolink/el0-0'
> > > >     -- new CALL=K0JXI,ip=75.64.107.181,name=        Dale
> > > >   == Starting echolink/el0-1 at radio-secure,47911,1 failed so
> falling
> > > back
> > > > to exten 's'
> > > >   == Starting echolink/el0-1 at radio-secure,s,1 still failed so
> > falling
> > > > back to context 'default'
> > > >     -- Sent into invalid extension 's' in context 'default' on
> > > > echolink/el0-1
> > > >     -- Executing [i at default:1] Hangup("echolink/el0-1", "") in new
> > stack
> > > >   == Spawn extension (default, i, 1) exited non-zero on
> > 'echolink/el0-1'
> > > >     -- Received OK from Echolink server server1.echolink.org
> > > > [Jan 31 10:03:26] ERROR[427]: chan_echolink.c:2036 sendcmd: connect()
> > > > failed to connect to the Echolink server server5.echolink.org
> > > >     -- Directory pgm done downloading(partial,compressed), 213
> records
> > > >     -- Received OK from Echolink server server3.echolink.org
> > > >     -- new CALL=K0JXI,ip=75.64.107.181,name=        Dale
> > > >   == Starting echolink/el0-2 at radio-secure,47911,1 failed so
> falling
> > > back
> > > > to exten 's'
> > > >   == Starting echolink/el0-2 at radio-secure,s,1 still failed so
> > falling
> > > > back to context 'default'
> > > >     -- Sent into invalid extension 's' in context 'default' on
> > > > echolink/el0-2
> > > >     -- Executing [i at default:1] Hangup("echolink/el0-2", "") in new
> > stack
> > > >   == Spawn extension (default, i, 1) exited non-zero on
> > 'echolink/el0-2'
> > > >     -- new CALL=K0JXI,ip=75.64.107.181,name=        Dale
> > > >   == Starting echolink/el0-3 at radio-secure,47911,1 failed so
> falling
> > > back
> > > > to exten 's'
> > > >   == Starting echolink/el0-3 at radio-secure,s,1 still failed so
> > falling
> > > > back to context 'default'
> > > >     -- Sent into invalid extension 's' in context 'default' on
> > > > echolink/el0-3
> > > >     -- Executing [i at default:1] Hangup("echolink/el0-3", "") in new
> > stack
> > > >   == Spawn extension (default, i, 1) exited non-zero on
> > 'echolink/el0-3'
> > > >     -- Received OK from Echolink server server1.echolink.org
> > > >     -- Received OK from Echolink server server1.echolink.org
> > > >     -- Directory pgm done downloading(partial,compressed), 350
> records
> > > >     -- new CALL=K0JXI,ip=75.64.107.181,name=        Dale
> > > >   == Starting echolink/el0-4 at radio-secure,47911,1 failed so
> falling
> > > back
> > > > to exten 's'
> > > >   == Starting echolink/el0-4 at radio-secure,s,1 still failed so
> > falling
> > > > back to context 'default'
> > > >     -- Sent into invalid extension 's' in context 'default' on
> > > > echolink/el0-4
> > > >     -- Executing [i at default:1] Hangup("echolink/el0-4", "") in new
> > stack
> > > >   == Spawn extension (default, i, 1) exited non-zero on
> > 'echolink/el0-4'
> > > >     -- new CALL=K0JXI,ip=75.64.107.181,name=        Dale
> > > >   == Starting echolink/el0-5 at radio-secure,47911,1 failed so
> falling
> > > back
> > > > to exten 's'
> > > >   == Starting echolink/el0-5 at radio-secure,s,1 still failed so
> > falling
> > > > back to context 'default'
> > > >     -- Sent into invalid extension 's' in context 'default' on
> > > > echolink/el0-5
> > > >     -- Executing [i at default:1] Hangup("echolink/el0-5", "") in new
> > stack
> > > >   == Spawn extension (default, i, 1) exited non-zero on
> > 'echolink/el0-5'
> > > >     -- Received OK from Echolink server server1.echolink.org
> > > >     -- Directory pgm done downloading(partial,compressed), 49
> records
> > > > [Jan 31 10:05:51] ERROR[427]: chan_echolink.c:2036 sendcmd: connect()
> > > > failed to connect to the Echolink server server5.echolink.org
> > > >     -- Received OK from Echolink server server3.echolink.org
> > > >   == Refreshing DNS lookups.
> > > >     -- Received OK from Echolink server server1.echolink.org
> > > >
> > > > I rebooted the Pi3 and asked the station to try connecting again.
> Same
> > > > result.
> > > >
> > > > It's likely another fat-fingered error on my part during
> > configuration...
> > > > but help deciphering the cause and cure appreciated.
> > > >
> > > >
> > > > John
> > > > WB5NFC
> > > > _______________________________________________
> > > >
> > > > 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