[arm-allstar] Echolink Problems

[Doug Crompton]

Rolland,

   You can disregard the server5 message. It is usually down and does not
matter. The echolink setup requires that 3 servers be assigned in the
config.

In the client do  'echolink dbdump'

You should see a bunch of nodes go by.  You can also specifically look for
a node with:

echolink dbget

wa3dsp-27225-hub*CLI> echolink dbget c WA3DSP-L
147090|WA3DSP-L|67.165.29.63

If you are getting the node list and you can lookup your echolink call then
you should be good to go.

Be aware echolink has some problems. We have fixed many of them but not in
the code you are using. That's not to say what you have does not work. It
does but at times some things may be a little flaku and there are some
situations where echolink could lock up the system. The next update will
fix much of that.

Also the common echolink rules - you can only have one echolink running per
public IP unless you use a proxy and of course the port forwarding has to
be in place.



*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*

On Sat, Nov 19, 2016 at 12:05 PM, Roland Smith via arm-allstar <
arm-allstar at hamvoip.org> wrote:

> I'm trying to get echolink working on node 42287. I have an RF node 42284
> and a "conference" node 42287. My plan is to activate echolink on 42287 and
> then connect from 42284 when I want echolink connectivity.
>
> I've built the config file echolink.conf as follows: (password is x'd out,
> otherwise everything else is exactly as configured):
>
> [el0]
> confmode=no
> call=K7OJL-L
> pwd=xxxxxxx
> name=Roland
> qth=Hauula, HI
> email=rolandksmith at gmail.com
> maxstns=20
> rtcptimeout=10
> node=499821
> recfile=/tmp/recorded.gsm
> astnode=42287
> context=radio-secure
> server1=server1.echolink.org
> server2=server5.echolink.org
> server3=server3.echolink.org
> ;naeast.echolink.org
> ;nasouth.echolink.org
> ;servers.echolink.org
> ;backup.echolink.org
> ; Change following setting to your parameters
> freq=147.495
> tone=100.0
> lat=21.618438
> lon=-157.917803
> power=5
> height=0
> gain=3
> dir=0
> ;deny=
> ;permit=
>
> When I restart asterisk, the following shows up in asterisk:
>
> [Nov 19 05:31:52] ERROR[1286]: chan_echolink.c:2341 do_el_directory: Unable
> to connect to directory server server5.echolink.org
>
> [Nov 19 05:31:52] ERROR[1286]: chan_echolink.c:2410 do_el_directory: Error
> in parsing header on server3.echolink.org
>
> [Nov 19 05:32:12] ERROR[1286]: chan_echolink.c:2410 do_el_directory: Error
> in parsing header on server1.echolink.org
>
> [Nov 19 05:34:38] ERROR[1286]: chan_echolink.c:2143 sendcmd: connect()
> failed to connect to the Echolink server server5.echolink.org
>
> ... repeated
>
> [Nov 19 05:36:46] ERROR[1286]: chan_echolink.c:2410 do_el_directory: Error
> in parsing header on server3.echolink.org
>
> [Nov 19 05:49:20] ERROR[1286]: chan_echolink.c:2143 sendcmd: connect()
> failed to connect to the Echolink server server5.echolink.org
>
> [Nov 19 05:51:28] ERROR[1286]: chan_echolink.c:2341 do_el_directory: Unable
> to connect to directory server server5.echolink.org
>
> [Nov 19 05:51:28] ERROR[1286]: chan_echolink.c:2410 do_el_directory: Error
> in parsing header on server3.echolink.org
>
> [Nov 19 05:51:48] ERROR[1286]: chan_echolink.c:2410 do_el_directory: Error
> in parsing header on server1.echolink.org
>
> [Nov 19 06:16:57] ERROR[1546]: chan_echolink.c:2341 do_el_directory: Unable
> to connect to directory server server5.echolink.org
>
>     -- Received OK from Echolink server server3.echolink.org
>
> [Nov 19 06:16:57] ERROR[1546]: chan_echolink.c:2410 do_el_directory: Error
> in parsing header on server3.echolink.org
> The port forwarding is set up in the router with 5198 and 5199 UDP
> forwarded to the Pi and 5200 TCP allowed (although that shouldn't be
> necessary as all outbound ports are allowed). The router logs (such as they
> are) don't show anything remotely useful.
>
> Where have I gone astray?
>
> Thanks!
> --
> Elder Roland Smith K7OJL
> Laie Hawaii Temple Visitors' Center
> Blog: www.rnsmith.com
> Cell: 208-406-8449
> _______________________________________________
>
> 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
>
>