Allstar and EchoLink: Linking Repeaters Over the Internet

How Allstar Link and EchoLink connect ham repeaters over the internet. Setup guides, use cases, differences, and tips for getting the most from VoIP linking.

· Updated · 7 min read · By HamPost Editorial Team

Your local 2-meter repeater covers maybe a 40-mile radius. That's great for ragchewing with locals. But what if you want to chat with a ham in Arizona from your HT in New Jersey? Or monitor a net happening on a repeater 800 miles away?

Internet linking makes that happen. Your local repeater connects to a remote repeater (or a conference hub) via the internet, and suddenly your 5-watt HT is talking across the country. Two systems dominate this space: AllStar Link and EchoLink. They solve similar problems differently, and understanding both gives you access to thousands of linked systems worldwide.

The Basic Concept

Internet linking for ham radio works like this:

  1. Your voice goes into a local repeater (or a simplex node)
  2. That repeater has a computer running linking software
  3. The software digitizes your audio, packetizes it, sends it over the internet
  4. The remote system receives it, converts back to audio, keys up the remote repeater
  5. Everyone listening on the remote repeater hears you

Bidirectional. Both sides can talk. Latency is typically 200-500ms depending on the internet path and codec buffering. You get used to the slight delay.

The whole thing is legal under Part 97 because both endpoints are amateur radio systems with proper identification. The internet is just a relay mechanism, similar in concept to a phone patch but for repeater-to-repeater connections.

AllStar Link (ASL) is built on the Asterisk PBX framework — the same open-source telephony software that runs VoIP phone systems. The ham-specific module is called app_rpt, written by Jim Dixon, WB6NIL (SK), starting around 2003.

Each AllStar node has a unique node number (typically 5-6 digits). To connect to another node, you send a DTMF command from your radio: *3 followed by the node number connects you. *1 followed by the node number disconnects.

Why Hams Love AllStar

  • Full duplex, low latency: Audio quality is noticeably better than EchoLink in most configurations. The CODEC2 and ULAW codecs used give clear, natural-sounding audio.
  • Permanent links: Repeater owners can set up permanent connections between nodes. Some regional networks (like the WInsystem in Texas or NE-Link in New England) maintain linked repeater networks 24/7.
  • Hub architecture: Conference bridges (hubs) let dozens of nodes connect simultaneously. The HamVoIP hub system during Sunday morning nets can have 50+ nodes connected.
  • Raspberry Pi friendly: A complete AllStar node runs on a Raspberry Pi with a USB sound interface (like a CM108-based dongle). Total hardware cost: $50-80.
  • Private nodes: You can run a personal node from home — no repeater needed. Connect your HT to a hotspot node in your house, link to any AllStar node worldwide.

Running Your Own AllStar Node

This is where AllStar shines for the individual operator. You don't need a repeater. You don't need club permission. You need:

  • Raspberry Pi 3B+ or 4 (2GB RAM is plenty)
  • CM108/CM119 USB sound fob (modified for PTT) or a URIx/simpleUSB interface ($30-50)
  • A radio connected to the interface (can be a cheap Baofeng for simplex use)
  • Internet connection
  • A registered AllStar node number (free from allstarlink.org)

The current recommended image is ASL3 (based on Debian Bookworm), which simplified a lot of the old configuration headaches. Previous versions required editing Asterisk config files by hand. ASL3 has a web dashboard.

I set up my first AllStar node in 2019 on a Pi 3B+ with a modified CM108 dongle and a retired Motorola CDM1250 as the RF interface. Total cost was about $75 (I had the radio already). Connected to the local repeater's AllStar system and suddenly I could monitor from home without being in RF range.

The learning curve is real though. If something breaks, you're debugging Asterisk dial plans and app_rpt configuration. It's Linux administration, and the documentation (while improving) still assumes some comfort with the command line.

The AllStar Network

As of mid-2026, there are over 30,000 registered AllStar nodes. Not all are online at any given time — many are personal hotspots that operators turn on when they want to use them.

Popular uses:

  • Linking a home repeater to a group of other repeaters for a regional net
  • Connecting to the Allstar "superlink" hubs to participate in nationwide ragchews
  • Running a personal simplex node to access AllStar from an HT in the house or yard
  • Emergency communications networks (some ARES groups maintain AllStar infrastructure)

EchoLink was created by Jonathan Taylor, K1RFD, and first released in 2002. It's Windows-based software (with mobile apps for iOS and Android) that connects repeaters, simplex links, and individual users over the internet.

The key difference from AllStar: you can connect directly from a smartphone or computer without a radio. The EchoLink app gives you access to the entire network from your phone. No hardware needed.

How EchoLink Works

  • Repeaters and links run EchoLink on a connected PC
  • Individual users (prefixed with -L for link or -R for repeater) appear in a directory
  • You can connect node-to-node (repeater to repeater), user-to-node, or user-to-user
  • Audio uses the GSM codec by default — functional but sounds compressed
  • DTMF commands from a radio: similar to AllStar, type the node number to connect

Why EchoLink Persists

Despite being older technology with simpler architecture:

  • Mobile apps work. Stuck in a hotel with no radio? Open the EchoLink app, connect to your home repeater. Done. This is EchoLink's killer feature.
  • Massive user base. Over 350,000 validated callsigns in the system. The validation process (you must prove you hold a valid license) keeps it ham-only.
  • Low barrier for repeater owners. A Windows PC with a sound card and a radio interface is all you need. No Linux, no Asterisk, no command-line configuration.
  • Conference servers. EchoLink conference nodes (prefixed with *) host round-the-clock nets and ragchew rooms.

The EchoLink Experience

I'll be blunt: audio quality on EchoLink is noticeably worse than AllStar in most cases. The GSM codec at 13 kbps sounds it. If you grew up with FM repeater audio, EchoLink will sound thin and robotic by comparison.

But it works. And the app access is genuinely useful. I've participated in my club's weekly net from an airport terminal, a hotel room in Tokyo, and a rental car (as a passenger, relax) using nothing but my phone. That's not something AllStar can easily match for the casual user.

Feature AllStar Link EchoLink Platform Linux (Raspberry Pi, x86) Windows + mobile apps Audio codec ULAW/CODEC2 (better quality) GSM 13kbps (adequate) Phone/app access Limited (some bridges exist) Native apps, iOS + Android Configuration complexity High (Asterisk/Linux) Low (GUI-based) Hardware cost for node $50-80 $100+ (Windows PC + interface) Registered nodes ~30,000+ ~350,000 validated users Private node support Yes, easy Yes, but less flexible DTMF control Extensive, customizable Standard set, less flexible Permanent linking Native, stable Possible but less common Community Technical, DIY-oriented Broader, more casual

IRLP: The Third Option (Briefly)

Internet Radio Linking Project (IRLP) deserves mention. It predates both AllStar and EchoLink (launched 1997) and still has active nodes, particularly in Canada and the Pacific Northwest. It uses Linux, supports reflectors (conference hubs), and has a reputation for excellent audio quality.

However, IRLP is a closed system — you can't build your own node without purchasing their hardware board. This has limited its growth compared to the open-source AllStar. Many former IRLP repeaters have migrated to AllStar or run both.

Practical Tips for Using Linked Systems

Whether you're accessing AllStar or EchoLink from your radio, some etiquette and technical tips apply:

Wait for the beep. Linked systems have inherent delay. After keying up, wait a solid second before talking. The other end needs time to key up their repeater. If you quick-key, your first syllable gets clipped.

Keep it short. When you're going through multiple linked nodes, you're occupying all of them. Keep transmissions reasonable and leave gaps for others to break in.

Identify properly. Your signal is being retransmitted on a remote repeater in a different area. You still ID with your own call. The linked system handles the rest.

Listen first. Connect to a node and listen for a few minutes before jumping in. You might be walking into a conversation already in progress.

Don't link without permission. If you're connecting a repeater to another repeater, make sure both repeater trustees are okay with it. Linking someone else's machine without asking is poor form. Really poor form.

Internet dependence is real. If your home internet drops, your node goes offline. If you're using linked repeaters for emergency communications, have a backup plan for when the internet fails (which is exactly when you might need the radio most).

Getting Started

If you just want to listen and talk:

  1. Download the EchoLink app (free, iOS or Android)
  2. Register with your callsign (takes 24-48 hours for validation)
  3. Browse the node list, connect to an active repeater or conference
  4. Listen, then key up and introduce yourself

That's it. Five minutes to worldwide ham radio from your phone.

If you want to run your own node:

  1. Decide: AllStar (more powerful, Linux required) or EchoLink (simpler, Windows/apps)
  2. For AllStar: get a Pi, download ASL3, register for a node number, build or buy a radio interface
  3. For EchoLink: install the software on a Windows PC, connect a radio via interface
  4. Test locally, then announce your node to your local club

My recommendation: start with the EchoLink app to experience linking. If you get hooked (and you probably will), build an AllStar node. The Pi-based setup is a fun weekend project, and having a personal node you control is addictive.

The Future of Internet Linking

AllStar's ASL3 release modernized the platform significantly. The web dashboard, easier installation, and better documentation are bringing in operators who previously found it too intimidating.

EchoLink remains stable but hasn't seen major updates in several years. It works, it has massive adoption, and it fills the phone-access niche perfectly.

Some newer systems like SVXLink (open-source, Linux-based, similar to AllStar but different architecture) are gaining traction in Europe. And there's always DMR, Fusion, and D-STAR doing their own internet-backbone linking through brandmeister, YSF reflectors, and ircDDB.

But for analog FM repeater linking — which is still what most local repeaters run — AllStar and EchoLink remain the dominant pair. Learn both, use whichever fits your situation, and enjoy the fact that your little HT can talk around the world.

Frequently asked questions

Is internet linking of repeaters legal under Part 97?
Yes. Both endpoints are amateur radio systems with proper identification, so the internet simply acts as a relay mechanism between them. The concept is similar to a phone patch, applied to repeater-to-repeater connections instead of a telephone line.
Should I choose AllStar or EchoLink?
Start with the EchoLink app to experience linking with no hardware, since it has native iOS and Android clients and about 350,000 validated callsigns. If you get hooked, build an AllStar node on a Raspberry Pi for better audio, permanent links, and far more DTMF control.
What do I need to build my own AllStar node?
A Raspberry Pi 3B+ or 4 with 2 GB of RAM, a CM108 or CM119 USB sound fob modified for PTT or a URIx style interface at 30 to 50 dollars, any radio including a cheap Baofeng for simplex, an internet connection, and a free node number from allstarlink.org.
Is AllStar still hard to configure?
It is easier than it was. The current recommended image is ASL3, based on Debian Bookworm, which adds a web dashboard and removes much of the hand editing of Asterisk config files. When something breaks you are still debugging Asterisk dial plans and app_rpt, so expect real Linux work.
How many AllStar nodes are out there?
As of mid-2026 there are over 30,000 registered AllStar nodes, though not all are online at once because many are personal hotspots that operators switch on only when they want to use them. Hub conferences can carry 50 or more nodes during Sunday morning nets.
Can I link my repeater to another repeater on my own?
Only with permission from both repeater trustees. Connecting someone else's machine without asking is considered very poor form. Also listen for several minutes after connecting to a node, because you may be walking into a conversation already in progress.

Put it into practice

Reader field notes — share yours

Log in to share your field notes and photos.