that is not always true, Echolink will change where nasouth/ naeast point depending on the load on the servers..

So pointing directly at a server number could lead to a overloaded server while another server could be idle.

So would it be better to use 5 server in the configs? and start from 5 down to 1 in order?

or leave echolink deal with the server load?

From: doug@crompton.com
To: app_rpt-users@ohnosec.org
Date: Wed, 3 Dec 2014 13:38:50 -0500
Subject: Re: [App_rpt-users] Echolink Parsing Errors

The default 1,3,5 servers should work just fine. As you can see the naeast and nasouth are just referred back to server3. From the echolink site:

Where are the servers located, and how are they managed? The primary servers are located in Tier 1 hosting facilities in Atlanta, GA, and Scottsdale, AZ, each with OC-3 connections to the Internet. These facilities are staffed 24/7 and are equipped with emergency power. Secondary servers are located in Stamford, CT, and Ridgefield, CT. It is estimated that this arrangement of servers can support about 5 times the current worldwide load.

Ping the servers as I did below to see if you have connection. Also make sure your port forwarding is setup correctly in your router for echolink.

[root@WA3DSP_Allstar asterisk]# 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=42 time=27.2 ms

[root@WA3DSP_Allstar asterisk]# ping server3.echolink.org
PING server3.echolink.org (174.129.209.125) 56(84) bytes of data.
64 bytes from ec2-174-129-209-125.compute-1.amazonaws.com (174.129.209.125): icmp_seq=1 ttl=42 time=22.6 ms

[root@WA3DSP_Allstar asterisk]# ping server5.echolink.org
PING server5.echolink.org (68.178.144.151) 56(84) bytes of data.
64 bytes from ip-68-178-144-151.ip.secureserver.net (68.178.144.151): icmp_seq=1 ttl=51 time=81.5 ms

[root@WA3DSP_Allstar asterisk]# ping naeast.echolink.org
PING server3.echolink.org (174.129.209.125) 56(84) bytes of data.
64 bytes from ec2-174-129-209-125.compute-1.amazonaws.com (174.129.209.125): icmp_seq=1 ttl=42 time=22.0 ms

[root@WA3DSP_Allstar asterisk]# ping nasouth.echolink.org
PING server3.echolink.org (174.129.209.125) 56(84) bytes of data.
64 bytes from ec2-174-129-209-125.compute-1.amazonaws.com (174.129.209.125): icmp_seq=1 ttl=42 time=19.0 ms

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

From: petem001@hotmail.com
To: steve@m0hoy.com; app_rpt-users@ohnosec.org
Date: Wed, 3 Dec 2014 11:15:03 -0500
Subject: Re: [App_rpt-users] Echolink Parsing Errors

change the server for echolink in the echolink.conf file

the normal server in the conf file is:

server1=server1.echolink.org
server2=server2.echolink.org
server3=server3.echolink.org

Change that to the server you use for your own setup like for me its:

server1=naeast.echolink.org
server2=nasouth.echolink.org
server3=servers.echolink.org

From: steve@m0hoy.com
Date: Wed, 3 Dec 2014 08:55:36 +0000
To: app_rpt-users@ohnosec.org
Subject: [App_rpt-users] Echolink Parsing Errors

Hi All,

I am trying to set up echolink on on the BBB 1.2 but I keep getting the following parsing error on all servers:

server1.echolink.org

[Dec 2 17:50:18] ERROR[1522]: chan_echolink.c:2410 do_el_directory: Error in parsing header on

Does anyone know what I am doing wrong!?

Many thanks

Steve M0HOY

Sent from my iPhone

_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.