ASL3 w/EchoLink

App_rpt-users
1

I’ve been watching the various ASL3 forums (community, FB, …) and noticed that a few are having issues with EchoLink.

Let me start off saying that “I” have NOT configured Echolink on any of my nodes. But, I want to help.

For those using the ASL3 Raspberry Pi Appliance I noticed that the installed firewall does not allow traffic on ports 5198 and 5199. As these ports are needed for EchoLink it seems like that’s a place to start. You can open the firewall from the Cockpit web pages. Click on “Networking”, look for “Firewall” and click on “Edit rules and zones”, click on “Add services”, click on “Custom ports”, and here you add 5198,5199 to UDP and some informative names for ID and Description like “echolink”. Lastly, click “Add ports”

Please let us all know if this helped.

For those who succeed, would you be willing to help put together a step-by-step “how to” that we could add to the ASL Manual?

2

I will fix this for the next software update too.

3

Howdy,

For those keeping track, which is probably like two people :slight_smile: … the Pi imager works great with NVDA under Windows. Well, Windows 7, so I assume later Windowses too. But forget about it on the Mac with VoiceOver. But I got a good image, and now have a pretty much working node, I think. Except Echolink.

Well…I thought that opening the firewall ports on ASL would work. Also note that I do have the ports forwarded in my router. However, still no Echolink connection. Here’s what happens when I attempt to connect to the Echo test server (009999):

– Call for node el0/009999 on echolink/el0-3, failed. Node not found in database.

– Hungup ‘DAHDI/pseudo-497565875’

– Hungup ‘DAHDI/pseudo-309924142’

> Received OK from Echolink server nasouth.echolink.org.

> Directory completed downloading(partial,compressed), 364 records.

> Received OK from Echolink server naeast.echolink.org.

– <DAHDI/pseudo-1390865131> Playing ‘rpt/node.gsm’ (language ‘en’)

– <DAHDI/pseudo-1390865131> Playing ‘digits/3.ulaw’ (language ‘en’)

– <DAHDI/pseudo-1390865131> Playing ‘digits/0.ulaw’ (language ‘en’)

– <DAHDI/pseudo-1390865131> Playing ‘digits/0.ulaw’ (language ‘en’)

– <DAHDI/pseudo-1390865131> Playing ‘digits/9.ulaw’ (language ‘en’)

– <DAHDI/pseudo-1390865131> Playing ‘digits/9.ulaw’ (language ‘en’)

– <DAHDI/pseudo-1390865131> Playing ‘digits/9.ulaw’ (language ‘en’)

– <DAHDI/pseudo-1390865131> Playing ‘digits/9.ulaw’ (language ‘en’)

– <DAHDI/pseudo-1390865131> Playing ‘rpt/connection_failed.gsm’ (language ‘en’)

– Hungup ‘DAHDI/pseudo-1390865131’

kb5elv-hotspot*CLI>

Except…if I do
echolink dbdump

actually,
asterisk -rx echolink dbdump > echodb
and search for node 9999, it’s definitely there in the output.

Anyone have any idea where this is going wrong?

I’m almost there. I just have to make sure my old simpleusb tuning values still work. And this, of course.

Vy 73,
–Buddy, KB5ELV