开云体育

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