Echolink seemingly not registering - Unable to connect via Allmon3

AllStarLink
,
1

I have set up my ASL3 node according to instructions that match the ASL3 instructions.

It would appear echolink is not logging in to its servers to register my node.
I do not show up in the echolink “Current Logins” even after refresh or some time has past. Connecting using a PC/Mac client works 100% no issue. (not connected at the same time as node)

I am at a loss ?? - What am I missing here ??
Gregory.

  • When trying to connect to a known online node via Allmon3 it attempts to connect then fails.
    Per some previous posts the CLI reports: using (core set debug 7 chan_echolink.so)

    KF0ILP-Tx31*CLI>
    [2025-12-16 09:09:06.042] DEBUG[1819]: chan_echolink.c:1478 el_hangup: Sent bye to IP address .
    [2025-12-16 09:09:06.042] DEBUG[1819]: chan_echolink.c:1500 el_hangup: Hanging up (echolink/el0-3).
    [2025-12-16 09:09:06.046] DEBUG[1793]: chan_echolink.c:3554 el_reader: APRS out: )EL-KF0ILP!4144.00NE05023.99W0PHG0000/000000/000 On @ 1609 [0/20].
    [2025-12-16 09:09:06.170] DEBUG[1794]: chan_echolink.c:3269 el_directory: Trying to do directory download Echolink server nasouth.echolink.org.
    [2025-12-16 09:09:06.207] DEBUG[1792]: chan_echolink.c:3327 el_register: Trying to register with Echolink server nasouth.echolink.org.
    [2025-12-16 09:09:06.321] DEBUG[1794]: chan_echolink.c:3084 do_el_directory: Sending: F0 to nasouth.echolink.org.
    [2025-12-16 09:09:06.367] DEBUG[1794]: chan_echolink.c:3138 do_el_directory: Full directory received, deleting all nodes.
    [2025-12-16 09:09:06.369] DEBUG[1794]: chan_echolink.c:871 el_db_put: Directory - Added: Node=0, Callsign=KF0ILP-L, IP address=184.96.49.135.
    [2025-12-16 09:09:06.369] DEBUG[1794]: chan_echolink.c:871 el_db_put: Directory - Added: Node=663717, Callsign=PINGTEST, IP address=52.91.249.47.
    [2025-12-16 09:09:06.369] DEBUG[1794]: chan_echolink.c:871 el_db_put: Directory - Added: Node=9999, Callsign=ECHOTEST, IP address=13.57.14.183.

  • RUNNING: echolink dbget c KF0ILP-L
    0|KF0ILP-L|184.96.49.135 ←- this is my correct external IP

  • When attempting: echolink dbget nodename. ???
    KF0ILP-Tx31CLI> echolink dbget nodename 982594
    Error: Entry for 982594 not found!
    Command 'echolink dbget nodename 982594' failed.
    KF0ILP-Tx31    CLI> echolink dbget nodename KD5FMU-R
    Error: Entry for KD5FMU-R not found!
    Command 'echolink dbget nodename KD5FMU-R' failed.

Echolink port/ping test returns:
Firewall/Router Test

Node KF0ILP-L is logged in at 184.96.49.135.

Running test #1...
Result: Replies received from: 5198 5199

The firewall/router test was successful.
You should see that *PINGTEST* is connected now to this node.
Please note the message in the text area.
You may disconnect.
Test #1 complete.

My configurations:

  • Ports opened on ASL3 node FW & forwarded thru my home FW (UDP 5198/5199)

  • modules.conf set to:
    load = chan_echolink.so ; <-- Echolink Channel Driver

  • echolink.conf set to:
    [el0]
    call = KF0ILP-L ; Change this! ←- DONE.
    pwd = ****** ; Change this! ←- DONE.
    name = Gregory ; Change this! ←- DONE.
    qth = Colorado ; Change this! ←- DONE.
    email = ; Change this! << not configured
    node = 502489 ; Change this! ←- DONE.

    ; Message to show on the echolink connect page. Use \n for new lines.
    ; message = This is the first line\nThis is another line\nThis is another line

    astnode = 671040 ; Change this! ←- DONE.
    context = radio-secure ; Default in code is radio-secure

sudo asl-show-version
********** AllStarLink [ASL] Version Info **********

OS : Debian GNU/Linux 13 (trixie)
OS Kernel : 6.12.47+rpt-rpi-v8

Asterisk : 22.5.2+asl3-3.6.3-1.deb13
ASL [app_rpt] : 3.6.3

2

It appears Echolink is trying to connect to a server name that is no longer valid. The current Echolink server names are as follows:

server1=server1.echolink.org

server2=server2.echolink.org

server3=server3.echolink.org

3

Thank you David - dwh367 - Still no joy on the registration . . . I changed out the old servers for the ones you posted, and rebooted.
Still not registering. . . .
Example:
[2025-12-17 17:33:24.135] DEBUG[1538]: chan_echolink.c:3327 el_register: Trying to register with Echolink server server3.echolink.org.

Same with the other servers.
I am open to any suggestions. :slight_smile:

Gregory

4

Look for other devices already registered on the same IP…

IE - cell phone app on wifi running in the background.

EL allows only one registration per IP.

5

Just double checked . . . nothing else running in the backgound . . Only my node.
I have echoham (for Mac) client but it is closed and not active.

Does echolink use ANY other ports than the two UDP ports mentioned ?

6

Do you have an iphone ? That is what I was talking about.

If you think it is not running while not in the foreground, think again.

I can’t speak for the mac but the iphone would need TCP port 5200 directed to the server along with udp 5198, 5199 for everything else.

But again, something else on your local net is likely registered already.

Normally it is a cell phone with the app installed.

Can’t say in your instance, but a common overlook.

7

HI Mike!

  1. No I do not use an iPhone.
    I use and Android but it does not have an echolink app installed on it.
  2. I have an app on my Mac Book “EchoHam” it is not running and the PID it runs under is killed when I exit the app. (It is the ONLY system I have an app installed) so no background process running.
  3. I have even tried connecting with my Mac Book powered off. - No joy.
  4. I have attempted connection using my starlink mini (completely separate network - unique public IP) but still no luck. :lying_face:

If anyone thinks of anything please let me know - I am stumped.

CLI just repeats:
[2025-12-23 10:14:46.016] DEBUG[1529]: chan_echolink.c:3554 el_reader: APRS out: )EL-KF0ILP!4144.00NE05023.99W0PHG0000/000000/000 On @ 1714 [0/20].
[2025-12-23 10:14:46.143] DEBUG[1530]: chan_echolink.c:3269 el_directory: Trying to do directory download Echolink server ``nawest.echolink.org``.
[2025-12-23 10:14:46.156] DEBUG[1528]: chan_echolink.c:3327 el_register: Trying to register with Echolink server ``nasouth.echolink.org``.
[2025-12-23 10:14:46.996] DEBUG[1530]: chan_echolink.c:3084 do_el_directory: Sending: F0 to ``nawest.echolink.org``.
[2025-12-23 10:14:47.246] DEBUG[1530]: chan_echolink.c:3138 do_el_directory: Full directory received, deleting all nodes.
[2025-12-23 10:14:47.248] DEBUG[1530]: chan_echolink.c:871 el_db_put: Directory - Added: Node=0, Callsign=KF0ILP-L, IP address=44.27.129.83.
[2025-12-23 10:14:47.248] DEBUG[1530]: chan_echolink.c:871 el_db_put: Directory - Added: Node=663717, Callsign=PINGTEST, IP address=52.91.249.47.
[2025-12-23 10:14:47.248] DEBUG[1530]: chan_echolink.c:871 el_db_put: Directory - Added: Node=9999, Callsign=ECHOTEST, IP address=13.57.14.183.

8

Since you can make asl connections, the only thing I'd worry abuot is chan_echolink.conf.

What do you see when you type asterisk -rvvvv and wait awhile? You should see

       > Received OK from Echolink server backup.echolink.org.
       > Received OK from Echolink server servers.echolink.org.
       > Directory completed downloading(full,compressed), 6331 records.
       > Received OK from Echolink server servers.echolink.org.
       > Directory completed downloading(full,compressed), 6342 records.
       > Received OK from Echolink server nasouth.echolink.org.
       > Received OK from Echolink server servers.echolink.org.
       > Directory completed downloading(partial,compressed), 211 records.
       > Received OK from Echolink server servers.echolink.org.
       > Received OK from Echolink server naeast.echolink.org.
       > Directory completed downloading(full,compressed), 6332 records.

if EL is configured correctly. Is it node = 671040 or node = 502489? You have both in the OP.

9

Hi Chuck!
My allstar node is 671040 - the other number 502489 is my echolink node number
In my echolink.conf file both appear:
under: [el0]
node = 502489
astnode = 671040

What shows up with asterisk -rvvvv and core set debug 7 chan_echolink.so enabled is:

[2025-12-24 08:43:18.564] DEBUG[1540]: chan_echolink.c:3554 el_reader: APRS out: )EL-KF0ILP!4144.00NE05023.99W0PHG0000/000000/000 On @ 1543 [0/20].
[2025-12-24 08:43:18.700] DEBUG[1541]: chan_echolink.c:3269 el_directory: Trying to do directory download Echolink server nawest.echolink.org.
[2025-12-24 08:43:18.716] DEBUG[1539]: chan_echolink.c:3327 el_register: Trying to register with Echolink server nawest.echolink.org.

Received OK from Echolink server nawest.echolink.org.
Received OK from Echolink server nawest.echolink.org.
[2025-12-24 08:43:19.489] DEBUG[1541]: chan_echolink.c:3084 do_el_directory: Sending: F0 to nawest.echolink.org.
[2025-12-24 08:43:19.702] DEBUG[1541]: chan_echolink.c:3138 do_el_directory: Full directory received, deleting all nodes.
[2025-12-24 08:43:19.704] DEBUG[1541]: chan_echolink.c:871 el_db_put: Directory - Added: Node=0, Callsign=KF0ILP-L, IP address=44.27.129.83.
[2025-12-24 08:43:19.704] DEBUG[1541]: chan_echolink.c:871 el_db_put: Directory - Added: Node=663717, Callsign=PINGTEST, IP address=52.91.249.47.
[2025-12-24 08:43:19.704] DEBUG[1541]: chan_echolink.c:871 el_db_put: Directory - Added: Node=9999, Callsign=ECHOTEST, IP address=13.57.14.183.
Directory completed downloading(full,un-compressed), 3 records.

10

My bad. The node should be your Echolink node number. The astnode should be the EL node's allstarlink node number. You should be able to make a regular allstarlink connection to 502489.

node = <your node number from echolink.org>
astnode = 502489
11

Hi Chuck - Merry Christmas!

So here is what I noticed between your output and mine:
YOU: > Directory completed downloading(full,compressed), 6331 records.
YOU: > Directory completed downloading(full,compressed), 6342 records.
YOU: > Directory completed downloading(partial,compressed), 211 records.
etc . . .

ME: > Directory completed downloading(full,un-compressed), 3 records.
You are getting 6331 records where I am only receiving 3 records - TOTAL.

When I attempt to connect to an echolink node I get:
-- Call for node el0/100658 on echolink/el0-1, failed. Node not found in database.
-- Hungup 'DAHDI/pseudo-1014520661'

This may be the root issue:
ME: Node not found in database.

I dont know if this sheds any light on the issue but that seems to be the difference.

12

Since you have not valildated KF0ILP-L yet, you must be testing KF0ILP. Checking, your original EL node number is 502489. You have two ASL node numbers, 671040 and 672280. Both of these are online, but are not reporting stats because they are misconfigured, so they appear to be offline. That's the issue you want to fix first. Look at the log messages in /var/log/asterisk/messages for stats errors.

Did you build the nodes from the Pi image?

13

Two node numbers not reporting stats ←- this was intentional.
Did you build the nodes from the Pi image? ←- Yes.

You have not validated KF0ILP-L yet. ←– THIS WAS THE ISSUE.

I cannot say that in any of the videos watched or instructions combed - did I notice it saying that I had to register each one . . . ie. -L or -R separately . . . so my assumption was that registering my callsign alone was sufficient.
Thank you for noticing my misunderstanding and point it out!
I feel like Charlie Brown! ARRRRRRGH !!!

Have a Merry Christmas and happy New Year.

1 Like
14

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.