¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. SHARI
  2. Topics

ASL3 echolink

 

Greetings:

Has anyone gotten the echolink module in ASL3 working?

Mine downloads the database, as shown by

asterisk -rx "echolink dbdump"

however, any call results in a message like this.

asl508422*CLI>

rpt fun 508422 *33009999
*CLI>???? -- Call for node el0/009999 on echolink/el0-0, failed. Node not found in database.

However, if I do

asterisk -rx "echolink dbdump" | grep 9999

root@asl508422:/home/patrick# asterisk -rx "echolink dbdump" | grep 9999
899993|SK6RIC-R|70.34.202.109
9999|*ECHOTEST*|54.176.61.77
999972|KJ6YSS|44.31.127.3
root@asl508422:/home/patrick#

All those nodes matched the non-explicit pattern of 9999, but *echotest* was listed, as you can see above.

Though I'm pretty sure my firewall is configured correctly (tested with another known-working HamVoIP chan_echolink module, only replacing the IP address), incoming connections never seem to make it to the server in the first place.

If I change the forwarded IP back to the HamVoIP node and re-enable it's echolink module (yes, I made sure it was off while the ASL3 chan_echolink was enabled), I can make outgoing connections and accept incoming ones on that node, so I'm not sure what's going on there.


If I do

netstat -n --udp --listen

to list all UDP listeners, among those are:

udp??????? 0????? 0 0.0.0.0:5198??????????? 0.0.0.0:*
udp??????? 0????? 0 0.0.0.0:5199??????????? 0.0.0.0:*

so that looks good.


73

N2DYI
 

In short, we found an issue with connecting to nodes that, as 6-digits, have leading zeros. ?A fix is on the way.

For details, you can look at :?
 

You can not run 2 echolinks on the same network


On Sat, Jul 6, 2024, 9:10 AM Allan, WA3WCO via <ajn=[email protected]> wrote:
In short, we found an issue with connecting to nodes that, as 6-digits, have leading zeros.? A fix is on the way.

For details, you can look at :?
 

¿ªÔÆÌåÓý

I am aware. That is why I disabled the echolimk module on the other node, and forwarded the port range to the new one when testing.

Sent from my zippo


On Jul 6, 2024, at 10:03, Brad N8PC via groups.io <bradn8pc@...> wrote:

?

You can not run 2 echolinks on the same network


On Sat, Jul 6, 2024, 9:10 AM Allan, WA3WCO via <ajn=[email protected]> wrote:
In short, we found an issue with connecting to nodes that, as 6-digits, have leading zeros.? A fix is on the way.

For details, you can look at :?
 

Also saw that same error. Somewhere along the way, things started to work; though I'm not quite sure what single thing did it. For what it's worth: A couple of notes of what I tried (in addition to the documented steps out there):

Get a clean configuration file; and make sure it's owned by the same user that runs the asterisk application ("asterisk"user and group).

bash $ sudo rm /etc/asterisk/echolink.conf
bash $ sudo cp /usr/share/doc/asl3-asterisk-config/examples/configs/asl3/echolink.conf /etc/asteriskbash $ chown asterisk: /etc/asterisk/echolink.conf

Carefully edit the config file. My not doing so contributed to my issues.

After enabling the module (/etc/asterisk/module.conf), I opted to restart the server entirely (probably overkill; but why not).

You can also try to manually load it in Asterisk CLI.
CLI> module load chan_echolink

In my case, doing so help reveal to me that I had an invalid password.

Occasionally, the after reboot, the simpleusb module would fail. Still working through that; but it seems that restarting the asterisk service does the trick.
bash $ sudo systemctl restart asterisk.service

Somewhat related: I noticed that a firewall was enabled out of the box; but without "echolink" service added; the symptom being my echolink node was registered; but could not receive incoming calls. The following command added the echolink service to the firewall.

bash $ sudo firewall-cmd --zone-allstarlink --add-service=echolink

I hope some or all of this helps. Good luck and 73
 

¿ªÔÆÌåÓý

The firewall problem has been resolved in the latest asl3-appliance package update a couple of days ago. Just install the package maintainers version of ?firewall.xml, and the zone should exist from that point.
Sent from my zippo


On Jul 8, 2024, at 21:44, Omar Asfour via groups.io <ve3kdc@...> wrote:

?Also saw that same error. Somewhere along the way, things started to work; though I'm not quite sure what single thing did it. For what it's worth: A couple of notes of what I tried (in addition to the documented steps out there):

Get a clean configuration file; and make sure it's owned by the same user that runs the asterisk application ("asterisk"user and group).

bash $ sudo rm /etc/asterisk/echolink.conf
bash $ sudo cp /usr/share/doc/asl3-asterisk-config/examples/configs/asl3/echolink.conf /etc/asteriskbash $ chown asterisk: /etc/asterisk/echolink.conf

Carefully edit the config file. My not doing so contributed to my issues.

After enabling the module (/etc/asterisk/module.conf), I opted to restart the server entirely (probably overkill; but why not).

You can also try to manually load it in Asterisk CLI.
CLI> module load chan_echolink

In my case, doing so help reveal to me that I had an invalid password.

Occasionally, the after reboot, the simpleusb module would fail. Still working through that; but it seems that restarting the asterisk service does the trick.
bash $ sudo systemctl restart asterisk.service

Somewhat related: I noticed that a firewall was enabled out of the box; but without "echolink" service added; the symptom being my echolink node was registered; but could not receive incoming calls. The following command added the echolink service to the firewall.

bash $ sudo firewall-cmd --zone-allstarlink --add-service=echolink

I hope some or all of this helps. Good luck and 73

 

Hm, minutes after sending my previous question, I ran into some rather important information, and my problem now comes down to this known problem:

but more specifically this:

73
Sander


On Wed, 10 Jul 2024 at 17:34, djtomny <djtomny.ingress@...> wrote:
I've tried to get echolink working on ASL3 and have been following this thread. I was wondering how I can check that my configuration is set up for echolink, e.g., that the correct module is actually loaded. Or modules (plural)? Trying to connect to the parrot node 9999 failed, for example. DTMF is correctly received, though, I can see that in the asterisk*CLI.

Any thoughts on how to tackle this problem?

73
Sander


On Tue, 9 Jul 2024 at 12:18, Patrick Perdue via <borrisinabox=[email protected]> wrote:
The firewall problem has been resolved in the latest asl3-appliance package update a couple of days ago. Just install the package maintainers version of ?firewall.xml, and the zone should exist from that point.
Sent from my zippo


On Jul 8, 2024, at 21:44, Omar Asfour via <ve3kdc=[email protected]> wrote:

?Also saw that same error. Somewhere along the way, things started to work; though I'm not quite sure what single thing did it. For what it's worth: A couple of notes of what I tried (in addition to the documented steps out there):

Get a clean configuration file; and make sure it's owned by the same user that runs the asterisk application ("asterisk"user and group).

bash $ sudo rm /etc/asterisk/echolink.conf
bash $ sudo cp /usr/share/doc/asl3-asterisk-config/examples/configs/asl3/echolink.conf /etc/asteriskbash $ chown asterisk: /etc/asterisk/echolink.conf

Carefully edit the config file. My not doing so contributed to my issues.

After enabling the module (/etc/asterisk/module.conf), I opted to restart the server entirely (probably overkill; but why not).

You can also try to manually load it in Asterisk CLI.
CLI> module load chan_echolink

In my case, doing so help reveal to me that I had an invalid password.

Occasionally, the after reboot, the simpleusb module would fail. Still working through that; but it seems that restarting the asterisk service does the trick.
bash $ sudo systemctl restart asterisk.service

Somewhat related: I noticed that a firewall was enabled out of the box; but without "echolink" service added; the symptom being my echolink node was registered; but could not receive incoming calls. The following command added the echolink service to the firewall.

bash $ sudo firewall-cmd --zone-allstarlink --add-service=echolink

I hope some or all of this helps. Good luck and 73

 

I've tried to get echolink working on ASL3 and have been following this thread. I was wondering how I can check that my configuration is set up for echolink, e.g., that the correct module is actually loaded. Or modules (plural)? Trying to connect to the parrot node 9999 failed, for example. DTMF is correctly received, though, I can see that in the asterisk*CLI.

Any thoughts on how to tackle this problem?

73
Sander


On Tue, 9 Jul 2024 at 12:18, Patrick Perdue via <borrisinabox=[email protected]> wrote:
The firewall problem has been resolved in the latest asl3-appliance package update a couple of days ago. Just install the package maintainers version of ?firewall.xml, and the zone should exist from that point.
Sent from my zippo


On Jul 8, 2024, at 21:44, Omar Asfour via <ve3kdc=[email protected]> wrote:

?Also saw that same error. Somewhere along the way, things started to work; though I'm not quite sure what single thing did it. For what it's worth: A couple of notes of what I tried (in addition to the documented steps out there):

Get a clean configuration file; and make sure it's owned by the same user that runs the asterisk application ("asterisk"user and group).

bash $ sudo rm /etc/asterisk/echolink.conf
bash $ sudo cp /usr/share/doc/asl3-asterisk-config/examples/configs/asl3/echolink.conf /etc/asteriskbash $ chown asterisk: /etc/asterisk/echolink.conf

Carefully edit the config file. My not doing so contributed to my issues.

After enabling the module (/etc/asterisk/module.conf), I opted to restart the server entirely (probably overkill; but why not).

You can also try to manually load it in Asterisk CLI.
CLI> module load chan_echolink

In my case, doing so help reveal to me that I had an invalid password.

Occasionally, the after reboot, the simpleusb module would fail. Still working through that; but it seems that restarting the asterisk service does the trick.
bash $ sudo systemctl restart asterisk.service

Somewhat related: I noticed that a firewall was enabled out of the box; but without "echolink" service added; the symptom being my echolink node was registered; but could not receive incoming calls. The following command added the echolink service to the firewall.

bash $ sudo firewall-cmd --zone-allstarlink --add-service=echolink

I hope some or all of this helps. Good luck and 73

 

On Wed, Jul 10, 2024 at 07:58 AM, Sander [VK6PI] wrote:
I've tried to get echolink working on ASL3 and have been following this thread. I was wondering how I can check that my configuration is set up for echolink, e.g., that the correct module is actually loaded. Or modules (plural)? Trying to connect to the parrot node 9999 failed, for example. DTMF is correctly received, though, I can see that in the asterisk*CLI.
There's a ASL3 bug that prevents you from connecting to 4/5 digit EchoLink nodes. ?The fix should be out real soon. ?If you want to test your setup without the fix then try connecting to 6-digit node (with no leading zeros) like?ARRLNEWS, #826983.

1 - 9 of 9