EchoLink for Ham Radio: VoIP Linking Done Right

Somewhere around 2003, a ham in Connecticut keyed up his local repeater and talked to an operator in Australia. No HF rig, no massive antenna, no favorable propagation window. Just a 2-meter handheld, a linked repeater, and an internet connection bridging the gap.

That's EchoLink. It routes audio between amateur radio stations over the internet using VoIP (Voice over IP). Love it or hate it (and plenty of hams fall into both camps), it's been a fixture of amateur radio since Jonathan Taylor, K1RFD, released it in 2002.

This guide covers how it works, how to set it up, and whether it actually belongs in your operating toolkit.

How EchoLink Works

The basic concept: EchoLink software runs on a computer (or phone) and connects to a central directory of EchoLink nodes. Each node is either a repeater, a link radio, or a user running the software directly. When two nodes connect, audio from one side gets digitized, sent over the internet, and played on the other side.

Three connection modes exist:

Sysop mode (repeater/link): A computer with EchoLink software connects to a radio (usually a repeater). Anyone keying up that repeater can talk to whoever's on the other end of the EchoLink connection. This is the infrastructure mode — the node is always available for incoming/outgoing connections.

Single-user mode: You run EchoLink on your PC and use a headset/microphone directly. No radio involved (on your end). You're essentially using the internet to connect to a distant repeater's EchoLink node. The distant repeater retransmits your audio over RF.

Phone app (iOS/Android): Same as single-user mode, but from your phone. Log in with your callsign, connect to a node, talk.

All modes require a valid amateur radio callsign — the system verifies your license before granting access. This isn't Zello or Discord with radio branding. It's access-controlled to licensed operators.

Setting Up EchoLink: User Mode

The simplest way to get started. You just want to connect from your computer or phone to a remote repeater.

Registration

Before anything else, you need to validate your callsign. Go to echolink.org, download the software, and register. EchoLink will ask for proof of license — typically you upload a scan of your license or reference your FCC ULS record. Validation usually takes 24-48 hours (it's reviewed by humans, or at least it was — the process has gotten faster with automated FCC database lookups for US callsigns).

Without validation, you can't connect. No exceptions.

Desktop Software

• Download from echolink.org (Windows natively; macOS/Linux users can run via Wine or use the mobile app instead)
• Install, enter your callsign and password
• Configure your audio device (headset recommended over speakers to avoid feedback)
• You'll see the node directory — repeaters, links, and users currently online

The interface is... functional. Let's say it hasn't won any design awards since its 2002 release. But it works and it's stable.

Mobile App

• Available for iOS and Android
• Same callsign/password as the desktop version
• Actually has a more modern interface than the desktop client
• Works over WiFi or cellular data

The phone app is honestly how most casual EchoLink users interact with the system these days. You're sitting at a coffee shop, pull out your phone, connect to a repeater in England, have a QSO. Zero radio hardware involved on your end.

Setting Up EchoLink: Sysop Mode (Repeater Linking)

This is where it gets more interesting — and more complex. You're connecting your repeater (or simplex link radio) to the EchoLink network so that any RF user on your repeater can talk to distant nodes.

What You Need

• A dedicated computer (even an old Raspberry Pi or Windows laptop works)
• EchoLink software in Sysop mode
• A radio interface connecting the computer to your repeater or link radio
• Internet connection (doesn't need to be fast — audio is heavily compressed)
• Your repeater or a dedicated simplex link radio

The Interface

You need to get audio from EchoLink into the radio's transmit path and from the radio's receive audio into EchoLink. Plus PTT control.

Options:

• A purpose-built interface (SignaLink USB, RIGblaster, or the various URI-based interfaces)
• A homebrew interface (audio transformers, VOX or serial-port PTT, isolation)
• Direct connection to a repeater controller that has an internet port

Some modern repeater controllers (like the SCOM 7330) have built-in internet linking ports specifically designed for EchoLink and IRLP connections. If your repeater has one, setup is much simpler.

Configuration Notes

• Set audio levels carefully. Too hot and you'll distort on the air. Too low and distant users can't be heard over repeater noise.
• Configure DTMF control so RF users can connect/disconnect nodes from the repeater.
• Set a timeout so connected nodes automatically disconnect after inactivity (prevents someone from accidentally tying up your repeater for hours).
• Consider access control — you can whitelist/blacklist specific nodes or require a DTMF code to enable linking.

Getting levels right is the part most sysops struggle with. I helped a club set up EchoLink on their 2m repeater a few years back, and we spent an entire Saturday afternoon going back and forth adjusting audio levels. The EchoLink audio was either blasting at full scale or inaudible depending on who connected. Different nodes send audio at wildly different levels, and your interface needs to handle that range gracefully.

A limiter/compressor in the audio path helps enormously. Either in software (EchoLink has some built-in level control) or external hardware.

Using EchoLink Day-to-Day

Once you're set up, the actual operation is straightforward.

Finding Nodes

The EchoLink directory shows all online nodes organized by:

• Location (country, state)
• Type (repeaters, links, users)
• Node number
• Callsign

You can search by callsign, location, or node number. If you know the specific repeater you want to connect to, searching by callsign is fastest.

Connecting

From the software/app: double-click a node (or tap Connect). That's it. If the node accepts connections, you're linked. Audio flows in both directions.

From RF (via a Sysop node): send the node number via DTMF tones. The standard is: key up, send the digits, unkey. The repeater controller confirms the connection via announcement.

To disconnect: send ## via DTMF, or use the disconnect command in the app.

Conferences

EchoLink supports conferences — multiple nodes connected simultaneously. This is used for nets (scheduled on-air meetups) that span multiple repeaters. A net control station connects several repeaters via conference, and operators from various cities can check in through their local repeater.

The ECHOTEST conference is useful for testing your audio — connect to it, transmit, and it plays your audio back to you. Use it before connecting to a real QSO to check your levels and quality.

The Controversy: Is EchoLink "Real" Ham Radio?

Alright, let's address the elephant in the room.

A segment of the amateur radio community dismisses EchoLink (and similar linking systems like IRLP, AllStar, and DMR network linking) as "not real ham radio." The argument: if the internet is carrying your signal, you're not really doing radio. You're making a glorified phone call.

I get the argument. There's something philosophically different about an RF signal bouncing off the ionosphere versus audio packets routing through data centers. The magic of radio — working DX through propagation, building antennas, understanding physics — is genuinely diminished when you replace it with a broadband connection.

But here's my take, and I'll defend this one: EchoLink fills a legitimate niche that pure RF can't always cover.

Consider:

• A Technician-class operator who can't access HF but wants to talk to hams internationally. EchoLink lets them do that from their HT.
• A ham with antenna restrictions (HOA, apartment) who can't put up anything that works on HF.
• Emergency communication scenarios where internet is available but propagation isn't cooperating.
• Nets that need reliable connections between fixed locations regardless of band conditions.
• Hams with disabilities who can't easily maintain outdoor antenna systems.

Is it the same as working DX on 20 meters with a wire antenna you built yourself? No. Does it still facilitate genuine human connections between licensed operators who share a hobby? Absolutely.

The two modes of operation aren't in competition. Use EchoLink for what it's good at. Use RF for what it's good at. They coexist.

EchoLink vs. Other Linking Systems

EchoLink isn't the only game in town. Here's how it compares:

IRLP (Internet Radio Linking Project): Similar concept, but IRLP is sysop-only — there's no user mode where you connect from a computer without a radio. Every connection requires a radio on both ends. Some consider this "more pure" since RF is always involved. More popular in Canada.

AllStar Link: Open-source, highly configurable, runs on Asterisk (phone system software). More flexible than EchoLink but more complex to set up. Gaining popularity with technically-minded sysops. Can bridge to EchoLink nodes.

DMR network linking (Brandmeister, TGIF): Digital voice over the internet connecting DMR repeaters and hotspots worldwide. Different technology (AMBE codec, talkgroups) but similar concept. Requires DMR radio hardware.

Wires-X (Yaesu System Fusion): Yaesu's proprietary linking system. Works well within the Fusion ecosystem, less interoperable with other systems.

EchoLink's advantage: it's the most accessible. You can get on from a phone with zero hardware investment. The validation system is straightforward. The user base is large and established.

EchoLink's disadvantage: the software is aging. The audio codec (GSM) is dated compared to newer systems. The architecture is somewhat centralized (the registration/directory servers are single points of failure, and they've gone down before).

Tips for Good EchoLink Etiquette

The RF side and the internet side have slightly different social dynamics.

Leave a pause between transmissions. Internet latency means there's a delay. If you quick-key right after the other station unkeys, you'll clip the beginning of their last transmission on the EchoLink side. Wait a full second or two before keying up.

Don't monopolize a linked repeater. Remember that connecting your repeater to a distant node uses both repeaters' airtime. Long ragchews over EchoLink tie up two repeaters' worth of users. Be considerate.

Announce your link status. If you connect your local repeater to a distant node, announce it: "This is [callsign], connecting to [node] via EchoLink." This lets other repeater users know the link is active.

Disconnect when done. Don't leave connections hanging. If you connected to a distant repeater for a QSO, disconnect when you're finished so both repeaters return to normal local operation.

Test your audio. Connect to ECHOTEST first. Overdriven, distorted, or too-quiet audio is the number one complaint about EchoLink users. Get your levels right before inflicting them on others.

Common Problems and Fixes

"I can hear them but they can't hear me" — Audio input level issue. Your microphone gain is too low or the audio device isn't selected correctly in EchoLink settings. Also check that your firewall isn't blocking outbound UDP.

"Connection refused" or timeout — EchoLink uses UDP ports 5198-5199 and TCP port 5200. Your router/firewall needs these open. NAT can cause issues — UPnP usually handles it, but manual port forwarding is more reliable.

"My audio sounds robotic/choppy" — Network latency or packet loss. EchoLink needs consistent (not necessarily fast) internet. If your connection has jitter or drops packets, audio degrades quickly. Wired ethernet is better than WiFi for sysop nodes.

"I can't find the node I want" — It might be offline, or it might not accept your connection (some nodes restrict access to local users only). Check the node's status page on echolink.org.

Security Considerations

Briefly: EchoLink validates callsigns but the system isn't immune to abuse. Someone could theoretically register with a callsign that isn't theirs (though the validation process reduces this). Audio is transmitted unencrypted. Don't say anything on EchoLink you wouldn't say on an open repeater — because that's essentially what it is.

For sysop nodes: restrict DTMF commands to prevent random users from connecting your repeater to inappropriate nodes. Use a DTMF prefix or password for link control. Some repeater owners have had their machines connected to random conferences by pranksters sending DTMF tones.

Worth Using?

If you're a Technician wanting to talk beyond your local repeater coverage, EchoLink gives you that reach immediately with zero hardware investment. Download the app, validate, connect. You'll be talking to hams in other countries within 48 hours of your license being issued.

If you're an experienced HF operator, EchoLink probably isn't going to replace your daily operating. But it has utility — checking into a net when you're traveling, staying connected to your home repeater from overseas, or participating in events when your station isn't available.

The tool serves its purpose. Use it when it makes sense. Don't apologize for using it, and don't pretend it's the same as working DX on HF. Both positions are equally wrong.