[arm-allstar] Question on Echolink configuration

[Doug Crompton]

Joel,

 Can you ping the servers?

[root at WA3DSP_Allstar ~]# ping server1.echolink.org
PING server1.echolink.org (174.129.36.165) 56(84) bytes of data.
64 bytes from ec2-174-129-36-165.compute-1.amazonaws.com (174.129.36.165): icmp_seq=1 ttl=47 time=19.3 ms
64 bytes from ec2-174-129-36-165.compute-1.amazonaws.com (174.129.36.165): icmp_seq=2 ttl=47 time=19.9 ms

Also make sure your node call name and PW are correct in the config file. I think case matters in the call and it certainly does in the PW. Also the node number is the one for that call.

73 Doug
WA3DSP
http://www.crompton.com/hamradio


Date: Wed, 27 Aug 2014 11:44:05 -0500
From: w0kgw3 at gmail.com
To: arm-allstar at hamvoip.org
Subject: Re: [arm-allstar] Question on Echolink configuration

Still no luck, none of the servers seem to respond. 

I guess it's time to get out the sniffer and see what's going on.



On Tue, Aug 26, 2014 at 7:22 PM, Doug Crompton <doug at crompton.com> wrote:




Joel,

 I never had any luck with those servers. Here are the ones I use that work -

server1=server1.echolink.org

server2=server5.echolink.org
server3=server3.echolink.org

Also go into the client and you can do -  'echolink dbdump' and it should display the entire list.


You can also display specifically by node number or callsign -

WA3DSP_Allstar*CLI> echolink dbget c WA3DSP-L
147090|WA3DSP-L|50.191.8.33

WA3DSP_Allstar*CLI> echolink dbget n 147090
147090|WA3DSP-L|50.191.8.33


73 Doug
WA3DSP
http://www.crompton.com/hamradio



Date: Tue, 26 Aug 2014 18:59:57 -0500
From: w0kgw3 at gmail.com
To: arm-allstar at hamvoip.org

Subject: [arm-allstar] Question on Echolink configuration

I'm receiving a pile of errors connecting to echolink.

[Aug 26 18:46:50] ERROR[405] chan_echolink.c: Error in parsing header on naeast.echolink.org


[Aug 26 18:47:10] ERROR[405] chan_echolink.c: Error in parsing header on nasouth.echolink.org
[Aug 26 18:47:30] ERROR[405] chan_echolink.c: Error in parsing header on servers.echolink.org



(repeat each one every 20 seconds)

I tried with the default server1 setup, then with nawest which is what I'm supposed to be using, then naeast, but the errors constantly crop up and it does not show up on the echolink node lists. Currently a fresh BBB 1.1 image is loaded, with node configuration changes as listed in the setup documents



I've forwarded the correct ports to the BBB from the internet through my firewall (and tested them).

asterisk]# cat echolink.conf
[el0]
confmode=no
call=W0KGW-R
pwd=Yes I changed this
name=W0REA/R Isle, MN Repeater


qth=Isle, MN
email=w0kgw3 at gmail.com
maxstns=5
rtcptimeout=10
node=234724
recfile=/tmp/recorded.gsm

astnode=41187
context=radio-secure
server1=naeast.echolink.org


server2=nasouth.echolink.org
server3=servers.echolink.org
server4=backup.echolink.org



Cheers,
Joel
W0KGW


_______________________________________________

arm-allstar mailing list
arm-allstar at hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar

Visit the BBB web page - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/ 		 	   		  

_______________________________________________



arm-allstar mailing list

arm-allstar at hamvoip.org

http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar



Visit the BBB web page - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/



_______________________________________________

arm-allstar mailing list
arm-allstar at hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar

Visit the BBB web page - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/ 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20140827/cca3111a/attachment.html>