Echolink - follow-up

[KD0BVQ]

Thanks, everybody, for the encouragement. Finally got in to Echolink after only 5 more tries and a 3-day wait after finding the successful way to upload. (It won't take the stuff you get from the FCC in the internet; you gotta wait till the hard copy comes by slow mail.)

Still doesn't work, though - UDP and DSL router problems, apparently.

BTW, to the writer who said - "why not a radio?" (or words that effect) - yeah, I have a 2-meter 50-watt mobile, but I'm in "radio shadow" in a deep valley and can only attempt it while in town - or at least, up the hill. No success there either, yet.

[K0RGR]

You may need to do some things to configure around your router's firewall.

Another option would be to try to use one of the EchoLink proxies. You can read the help pages for info on how to use the public proxies - that should get you around any firewall issues. Also, version 2.0 of EchoLink and higher offers "firewall friendly" connections. Unfortunately, not everybody is using a compatible version. But, you should be able to connect to the conference servers that way.

Portforward (http://www.portforward.com/) contains info on setting up port forwarding on many different kinds of home routers. You need to forward ports 5198 through 5200. Technically, the two lower ones need to be enabled for UDP and 5200 for TCP, but I just set mine for "all".