Common Misconfigurations That I've Noticed

In my local area there has recently been 3 new Allstar nodes brought online, which is awesome! However all 3 have suffered from the exact same user configuration errors.

Seems like nobody fully reads the documentation so maybe these quick tips will held save you avoid some initial frustration:

1.) Port 4569 UDP needs to be opened for the IP address that the router assigned to your node (called port forwarding). Otherwise you will not be able to receive incoming connections.

2.) If you also going to run Echolink then you must use a -L or -R suffix. Running Echolink in the normal user mode will cause an endless loop, between Allstar and Echolink, upon connection. The only way out is for one of the nodes to restart Asterisk.

3.) Just like opening port 4569, for Allstar, Echolink needs have have UDP ports 5198 & 5199 opened as well (to support incoming connections).

Pro Tip: If you are also using Echolink then assign Echolink to a private node. That way you can turn incoming Echolink connections on and off.

plud not using -l or -r will get you a very nasty email from echolink folks
ask me how I know... (used -l instead of -r) plus they objected strongly to me even using ASL for echolink

GeorgeC W2DB

As much as possible, it's strongly recommended to use apps like RepeaterPhone (iOS), DVSwitch Mobile (Android), or a SIP endpoint on an OS (LinPhone, etc.) over Echolink.

I wonder why the EL people haven't modernized the codec after all this time... there's an EL node attached to the system I hang out on; even though I've used EL on rare occasions when there's no alternative, I routinely ignore "drive-by" EL calls. They sound like they're holding a folded-up towel over their mouth... Sorry; not intending to hijack the thread.

Where do I find the documentation on this?

Echolink documentation is horrible at best, but here's what they have for reading.