echolink issues

I am trying to get echolink going for a buddy of mine and running into a few snags…

I noticed that his station doesn’t appear online, nor does it have the echolink directory stored, looking at his logs, I see:

[Aug 18 13:33:03] ERROR[19489] chan_echolink.c: Error in parsing header on nawest.echolink.org
[Aug 18 13:33:08] ERROR[19489] chan_echolink.c: Error in parsing header on servers.echolink.org

I have tried some other servers (that I got from the Windows program) and regardless of what server I use, I am getting the errors above.

Few things I have checked so far:

  1. Login information - I was able to login successfully via the Windows program using the callsign and password that I have stored in echolink.conf

  2. Update - I just updated and rebuild the astsrc tree (I thought maybe I had an outdated version of chan_echolink).

Here is his echolink.conf (password hidden to protect the innocent):

[el0]
confmode=no
call=WU7Q-R ; Change this!
pwd= ; Change this!
name=Mike
qth=Elk Grove, CA
email=wmflud@yahoo.com
maxstns=20

rtcptimeout=10
node=3590 ; Change this!
recfile=/tmp/recorded.gsm
astnode=2336 ; Change this to your active Allstar node number!
context=radio-secure
server1=nawest.echolink.org

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

Any pointers would be much appreciated.

Thanks!

Jim, K6JWN/AG

Nodes 2165, 27137

You may want to double check your router settings and by sure that the ports are enabled for Echolink to work.

Ports:

UDP 5198,5199

TCP 5200

73, Vince VE3ELB

···

On 2013-08-18, at 4:40 PM, James Nessen nessenj@jimsoffice.org wrote:

I am trying to get echolink going for a buddy of mine and running into a few snags…

I noticed that his station doesn’t appear online, nor does it have the echolink directory stored, looking at his logs, I see:

[Aug 18 13:33:03] ERROR[19489] chan_echolink.c: Error in parsing header on nawest.echolink.org
[Aug 18 13:33:08] ERROR[19489] chan_echolink.c: Error in parsing header on servers.echolink.org

I have tried some other servers (that I got from the Windows program) and regardless of what server I use, I am getting the errors above.

Few things I have checked so far:

  1. Login information - I was able to login successfully via the Windows program using the callsign and password that I have stored in echolink.conf
  1. Update - I just updated and rebuild the astsrc tree (I thought maybe I had an outdated version of chan_echolink).

Here is his echolink.conf (password hidden to protect the innocent):

[el0]
confmode=no
call=WU7Q-R ; Change this!
pwd= ; Change this!
name=Mike
qth=Elk Grove, CA
email=wmflud@yahoo.com
maxstns=20

rtcptimeout=10
node=3590 ; Change this!
recfile=/tmp/recorded.gsm
astnode=2336 ; Change this to your active Allstar node number!
context=radio-secure
server1=nawest.echolink.org

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

Any pointers would be much appreciated.

Thanks!

Jim, K6JWN/AG

Nodes 2165, 27137


App_rpt-users mailing list
App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

Try this out too. Don’t forget to forward your ports to the linux box IP…

[el0]

confmode=no

call=YOURCALL ; must be in capital letters or your node won’t allow connections ;change

pwd=your echolink password ;change

name=node name ;change

qth=your qth ;change

email=your e-mail ; change

maxstns=4

rtcptimeout=10

node=echolink node number ;change

recfile=/tmp/recorded.gsm

astnode=your allstar node number ; change

context=radio-secure

server1=nasouth.echolink.org

server2=naeast.echolink.org

server3=servers.echolink.org

server3=backup.echolink.org

freq=your frequency ; change

tone=your ctcss tone ; change

lat=23.12647 ; change

lon=-81.67739 ; change

power=6 ; 0=0W, 1=1W, 2=4W, 3=9W, 4=16W, 5=25W, 6=36W, 7=49W, 8=64W, 9=81W (Power in Watts) ;change

height=5 ; 0=10’ ,1=20’,2=40’,3=80’ ,4=160’ ,5=320’ ,6=640’ ,7=1280’,8=2560’,9=5120’ (AMSL in Feet) ;change

gain=9 ;change antenna gain

dir=0 ; 0=omni, 1=45deg, 2=90deg, 3=135deg, 4=180deg, 5=225deg, 6=270deg, 7=315deg, 8=360deg (Direction) ;change

;deny=w6xxx

permit=wiaw,w5yi ; add up to 29 nodes. no one seem to know why there is a limit on the number of allowed nodes

permit=- ; permit statement must be last line

···

From: James Nessen nessenj@jimsoffice.org
To: App_rpt-users@ohnosec.org
Sent: Sunday, August 18, 2013 4:40 PM
Subject: [App_rpt-users] echolink issues

I am trying to get echolink going for a buddy of mine and running into a few snags…

I noticed that his station doesn’t appear online, nor does it have the echolink directory stored, looking at his logs, I see:

[Aug 18 13:33:03] ERROR[19489] chan_echolink.c: Error in parsing header on nawest.echolink.org
[Aug 18 13:33:08] ERROR[19489] chan_echolink.c: Error in parsing header on servers.echolink.org

I have tried some other servers (that I got from the Windows program) and regardless of what server I use, I am getting the errors above.

Few things I have checked so far:

  1. Login information - I was able to login successfully via the Windows program using the callsign and password that I have stored in echolink.conf

  2. Update - I just updated and rebuild the astsrc tree (I thought maybe I had an outdated version of chan_echolink).

Here is his echolink.conf (password hidden to protect the innocent):

[el0]
confmode=no
call=WU7Q-R ; Change this!
pwd= ; Change this!
name=Mike
qth=Elk Grove, CA
email=wmflud@yahoo.com
maxstns=20
rtcptimeout=10
node=3590 ; Change this!
recfile=/tmp/recorded.gsm
astnode=2336 ; Change this to your active Allstar node number!
context=radio-secure
server1=nawest.echolink.org
server2=servers.echolink.org
server3=backup.echolink.org

Any pointers would be much appreciated.

Thanks!

Jim, K6JWN/AG

Nodes 2165, 27137


App_rpt-users mailing list
App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users