EchoLink does not register on ASL3 3.18 (chan_echolink loads but never creates el0)

AllStarLink
1

Sorry in advance for the long question.

I’m looking for some help getting EchoLink working on a new ASL3 installation.

System

· Raspberry Pi using the official ASL3 Pi image

· ASL3 Version: 3.18

· Asterisk: 22.9.0+asl3-3.9.3

· AllStar Node: 54384

· EchoLink Call: N8TIM-L

· EchoLink Node: 450813

Problem

The node works normally on AllStarLink, but it never appears online in EchoLink.

On a Windows EchoLink client it shows as N8TIM-L (Off).

Configuration

My echolink.conf contains:

· call = N8TIM-L

· node = 450813

· astnode = 54384

The EchoLink password is correct (verified by logging into the Windows EchoLink client).

What I’ve verified

· chan_echolink.so loads successfully.

· core show channeltypes lists the EchoLink channel driver.

· echolink show stats works.

· echolink show nodes is empty.

· echolink dbget el0 call returns “Entry not found.”

· DNS resolution to the EchoLink servers works.

· ICMP ping to nasouth.echolink.org succeeds.

· The configuration file parses correctly.

· The module loads without configuration errors.

CLI Output

module show like chan_echolink

chan_echolink.so
Status: Running

core show channeltypes

echolink Echolink channel driver

echolink show stats

Inbound connections 0
Outbound connections 0

echolink show nodes

(no nodes)

What seems unusual

The EchoLink driver loads, but it never appears to initialize the el0 instance.

There are no database entries created for el0, and I never see any debug messages such as:

· Trying to register with EchoLink server

· Registration successful

· Downloading directory

It appears the driver loads successfully but never attempts registration.

Has anyone seen this with ASL3 3.18 or know what else I should check?

Thank you.

2

Here's a few sudo asterisk -r -vvvv commands to try :

CLI> module unload chan_echolink.so
CLI> module load chan_echolink.so
CLI> echolink dbget nodename 9999
3

Also, can we assume that you have looked over :

ASL Manual : EchoLink Configuration

4
N8TIM-L HALE [0/10] ON 22:06 450813

Direct from the Echolink Active node site. Make sure the ports are open as I didnt see any info if they were

5

I ran those commands and here is what I got. I was not getting these outputs before. I did a shutdown and restart. As I did a backup of my SD card. But it is still not showing ON in the Echolink app.

asl3-58348*CLI> module unload chan_echolink.so
Unloaded chan_echolink.so

Unloading chan_echolink.so
asl3-58348CLI> module load chan_echolink.so
Loaded chan_echolink.so
Total of 1 Echolink instances found.
Loaded chan_echolink.so => (Echolink Channel Driver)
Received OK from Echolink server nasouth.echolink.org.
Received OK from Echolink server nasouth.echolink.org.
Directory completed downloading(full,compressed), 6593 records.
Received OK from Echolink server nasouth.echolink.org.
Received OK from Echolink server naeast.echolink.org.
Directory completed downloading(partial,compressed), 924 records.
asl3-58348CLI> echolink dbget nodename 9999
9999|ECHOTEST*|13.57.14.183
asl3-58348CLI> echolink dbget nodename 450813
450813|N8TIM-L|44.27.136.72
asl3-58348*CLI>

I had this all working on and old version of Allstar.

k8upe: I looked at the echolink active node site today at 7:30am and did not see N8TIM-L. Am surprised it showed up last night.

6

The CLI output looks good.

Re: before/after a shutdown restart

I hope you know that after making changes to most of the /etc/asterisk configuration files that you need to give asterisk a kick in order to have the changes be applied. (astres.sh, reboot, ...). Could you have missed a restart/reboot?

Re: But it is still not showing ON in the Echolink app

Are you aware that each [public] IP address can only be associated with a single EchoLink node? This means that you can't have an EL node and an EL app on the same network.

And, if you haven't already done so, please check out EchoLink, Firewalls, and Routers

7

Yes am a were to restart asterisk and reboot. Am using my phone (thru the 5G not wifi) to check if the node is on or off. Not sure if this matters or not, but you mention to check echolink, firewalls and routers. I'm running the node thru a 44Net tunnel (WireGuard). I will look at the catagorys Echolink, Firewalls, and routers again to see if I missed something.

8

I will check out check out EchoLink, Firewalls, and Router. Here is some more info.

I verified that chan_echolink is loading and contacting the EchoLink servers successfully. On module load I get:

Total of 1 Echolink instances found.
Received OK from Echolink server...
Directory completed downloading...

echolink dbdump contains my own station:

450813|N8TIM-L|44.27.136.72

However:

echolink dbget el0 call

returns:

Error: Entry for call not found!

and

echolink dbget el0 node

also returns "Entry not found".

echolink show nodes is empty, and my station never registers as online in EchoLink. echolink.conf is in /etc/asterisk, is ASCII text, and chan_echolink.so loads without configuration errors.

9

The syntax of the command is :

wa3wco-rpi*CLI> echolink dbget 
Usage: echolink dbget <nodename|callsign|ipaddr> <lookup-data>
       Looks up echolink db entry

So :

wa3wco-rpi*CLI> echolink dbget callsign N8TIM-L
450813|N8TIM-L|44.27.136.72
wa3wco-rpi*CLI> echolink dbget nodename 450813
450813|N8TIM-L|44.27.136.72
10

Just a question but are you running Echolink on another node or on the same network. Last time I seen something like this it was because there were two instances of echolink running. If you are unsure shut one node down and see if echolink works then. Echolink can only be run one at a time from the same external IP address. The only way to get around that is to use an echolink proxy

11

Thanks for the reply. Am only running echolink on the one node. The others are not on echolink.

12

Hi Tim, were you able to resolve the Echolink issue? I'm having the same problem.
On the page Current Logins my link (IK4PKL-L) appears correctly, but in the list of available links on my smartphone (which connects via 5G and not my Wi-Fi...), I don't appear, and obviously no one can connect to me with the Echolink app (or software). Obviously, all ports, both at the router and ASL3 level, are open. I don't know what else to do...

Thanks de IK4PKL

13

What problem are both of you really trying to solve? The command with the "el0" red-herring I thought was resolved?

Can you please provide specifics exactly on what problem you're having? Echolink issues area almost always a firewall forwarding issue.

14

Am no networking guru, heck I had to look up a lot of commands and figure out how to use them. I even had AI help me with some of the command’s but in the end it was just an Hmmm moment of let me just try this… So here is what I did after hours of checking Firewalls, 44Net tunnel settings, Echolink settings, network paths loading and unloading. Watching network traffic. I found what was working.

N8TIM-L registration :white_check_mark:
44Net/WireGuard :white_check_mark:
ip ##.##.###.## reachable :white_check_mark:
UDP 5198 :white_check_mark:
UDP 5199 :white_check_mark:
ASL3 firewall :white_check_mark:
chan_echolink.so :white_check_mark:
EchoLink Firewall/Router Test :white_check_mark: SUCCESS
EchoLink → Asterisk connection :white_check_mark: SUCCESS
el0 channel :white_check_mark: WORKING

And after all that, it was still not showing that N8TIM-L was online in echolink on my pc or my phone that was on 5G.

The sequence I did to get it to work for me was as follows (dumb luck):

  1. Phone on Relay
    • EchoTest wouldn't connect.
    • Another known-good node wouldn't connect.
    • N8TIM-L wasn't appearing in search.
  2. I changed the phone to Public Proxy
    • EchoTest connected.
    • The known-good node connected.
    • N8TIM-L appeared in the search.
    • I connected to N8TIM-L successfully.
    • I saved it as a favorite and it showed Online.
  3. I changed the phone back to Relay
    • N8TIM-L continued working.
    • My computer now showed N8TIM-L as Online.

I think that the Public Proxy connection caused the phone to refresh/re-establish its EchoLink connection to the directory/servers, and something changed on the EchoLink side after that and it seems to be working. Good luck.