ASL3 and Echolink "Node Not Found In Database" - Do I Have A Current Version?

I built a new ASL3 node back on December 30, and I’m struggling with the Echolink “node not found” message on Allmon3 for a few users. I’m running out of ideas on how to troubleshoot.

First thing I wanted to try was to be sure I’m up to a current release of the code. I will paste the output of an “apt update” below. I think I’m checking the correct AllStar repository, and it’s not offering me an upgrade. So, I assume I’m current.

However, then I get stuck. I see references to using “asl-show-version” to see all ASL3 packages. I don’t seem to have that command.

As root, I did a “find / -name asl-show-version” and found nothing. What would cause me to not have that command/script? I

I set “core set debug 9 chan_echolink.so” in Asterisk, and I see periodic updates. I’ve tried a node lookup (“echolink dbget callsign user’s callsign”) while a user is showing “not in database”, and I don’t see the record locally. But, if I look them up on EchoLink Node Number Lookup, I see that they are active.

I’ve read many posts with similar problems about the “node not found” issue, but I just haven’t found the one that moves me forward.

Output of an apt update follows…
root@allstarhub:/etc/allmon3# apt update
Get:1 file:/etc/apt/mirrors/debian.list Mirrorlist [39 B]
Get:5 file:/etc/apt/mirrors/debian-security.list Mirrorlist [27 B]
Hit:6 http://security.debian.org bookworm-security InRelease
Hit:2 Index of /debian/ bookworm InRelease
Hit:7 https://repos-droplet.digitalocean.com/apt/droplet-agent main InRelease
Hit:8 Index of /public/ bookworm InRelease
Get:3 Index of /debian/ bookworm-updates InRelease [55.4 kB]
Get:4 Index of /debian/ bookworm-backports InRelease [59.0 kB]
Get:9 Index of /debian/ bookworm-backports/main Sources.diff/Index [63.3 kB]
Get:10 Index of /debian/ bookworm-backports/main amd64 Packages.diff/Index [63.3 kB]
Get:11 Index of /debian/ bookworm-backports/main Sources T-2025-01-27-0812.00-F-2025-01-27-0812.00.pdiff [1041 B]
Get:11 Index of /debian/ bookworm-backports/main Sources T-2025-01-27-0812.00-F-2025-01-27-0812.00.pdiff [1041 B]
Get:12 Index of /debian/ bookworm-backports/main amd64 Packages T-2025-01-27-0812.00-F-2025-01-27-0812.00.pdiff [1220 B]
Get:12 Index of /debian/ bookworm-backports/main amd64 Packages T-2025-01-27-0812.00-F-2025-01-27-0812.00.pdiff [1220 B]
Fetched 243 kB in 1s (232 kB/s)
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
1 package can be upgraded. Run ‘apt list --upgradable’ to see it.
root@allstarhub:/etc/allmon3# apt list --upgradable
Listing… Done
linux-image-amd64/stable-updates 6.1.124-1 amd64 [upgradable from: 6.1.119-1]
N: There are 2 additional versions. Please use the ‘-a’ switch to see them.

Are you seeing it on an Android device using the RELAY mode? You’re likely hitting this bug:

1 Like

Well, that didn’t take long! I put my Android in Relay mode, and immediately saw the error. The node on Allmon3 is correct once I strip off the leading “3”. But, “echolink dbget” doesn’t find me either by node or callsign. I’m also not in a dbdump list by node number or callsign.

I changed from Relay mode to Public Proxy, and I show up.

I will take a closer look at the link you posted. Thanks!

Does anyone know/where the Echolink info that is retrieved is stored? Just wondering if it might be possible and useful to see a lookup where the user is connecting with Relay vs Direct. I can reproduce the bug almost at will by switching my phone from Direct to Relay. Sometimes I get “Node not found”. Other times I get the wrong node and callsign. When in relay mode I do not find my node with a dbget, so if I found the data store it may just not have me listed.

I check the astdb.sqlite3 database. Nothing there.

All of the logic is within chan_echolink. The issue is well understood,it’s just not on the top of the list of issues right now.

1 Like