How AllStarLink Works: Technical Overview

What Is AllStarLink?

AllStarLink is a network system that connects amateur radio repeaters, remote base stations, and hotspots worldwide using Voice over Internet Protocol (VoIP). Think of it as a phone system for radios—instead of dialing phone numbers, you "dial" node numbers to connect different radio systems across the internet.

Core Architecture

The Foundation: Asterisk + app_rpt

AllStarLink is built on two key components:

Asterisk PBX - An open-source phone system (Private Branch Exchange) that handles audio routing and call management. Asterisk is essentially a sophisticated audio switching system that was designed for telephone systems.

app_rpt - A custom application written specifically for Asterisk that transforms it into a repeater controller. This is the "secret sauce" that makes Asterisk understand how to work with radios instead of just phones.

How app_rpt Works

The app_rpt application extends Asterisk's capabilities to:

• Control radio transmit/receive functions
• Handle DTMF (touch-tone) commands from radio users
• Manage linking between different nodes
• Generate telemetry and status announcements
• Control timing functions (hang time, timeouts, ID intervals)

A single Asterisk system running app_rpt can control multiple radios simultaneously—from one to a dozen or more separate repeaters, links, and remote bases at the same location.

Node Architecture

What Is a Node?

A node is the basic building block of AllStarLink. Each node consists of:

1. Computer/Server - Runs Linux (typically Debian) with Asterisk and app_rpt software. This can be:
   • Raspberry Pi (models 3, 4, 5, or Zero 2 W)
   • Standard PC (x86_64/AMD64 architecture)
   • Virtual machine in the cloud
   • Embedded systems
2. Radio Interface - Connects the computer to radio equipment via:
   • USB audio adapters (modified or commercial like URI devices)
   • PCI radio interface cards
   • Sound card interfaces
3. Network Connection - Internet connection for linking to other nodes
4. Node Number - A unique identifier (like a phone number) that other nodes use to connect

Current Software: ASL3

The latest version, AllStarLink 3 (ASL3), represents a major upgrade:

• Based on Asterisk 20 LTS (Long Term Support)
• Runs on Debian 12 Linux
• Incorporates 15+ years of bug fixes and security improvements from the older Asterisk 1.4 base
• Better memory management and stability
• Modernized codebase that's easier to maintain

How Connections Work

The IAX2 Protocol

AllStarLink uses the IAX2 (Inter-Asterisk eXchange version 2) protocol for node-to-node communication. This protocol was specifically designed for connecting Asterisk systems together.

Key advantages of IAX2:

• Full-duplex audio linking
• Single port (4569) makes it NAT/firewall friendly
• Built-in authentication and encryption (MD5, RSA)
• DTMF tones sent out-of-band (separate from audio)
• Prevents audio loops in complex network configurations

Authentication and Security

When a node connects to another:

1. The system checks a downloaded table of valid AllStarLink nodes
2. Verifies the calling node number, called node number, and source IP address
3. Validates through IAX2's authentication mechanisms
4. Only connects if all security checks pass

This table of valid nodes is periodically updated from AllStarLink servers, ensuring only legitimate nodes can connect.

Registration System

Nodes register their presence with the AllStarLink network:

New Method (ASL3): Uses HTTP-based registration configured in rpt_http_registration.conf

Legacy Method: IAX registration (still works but discouraged)

When your node successfully registers, it shows up on the AllStarLink nodelist with a green status indicator, meaning other users can connect to it.

Configuration Files

The system is configured through several text files:

• rpt.conf - Main configuration defining node behavior, radio channels, timing parameters, duplex modes
• iax.conf - IAX2 protocol and network settings
• extensions.conf - Dialplan that routes "calls" (connections)
• rpt_http_registration.conf - Registration with network servers

ASL3 uses a template system in rpt.conf that makes configuration much simpler—you only need a few lines per additional node.

Audio Flow

Here's what happens when you transmit on a linked AllStarLink system:

1. Radio Input - Your voice enters through the local repeater/node's receiver
2. Audio Interface - Sound is captured by the computer via USB/PCI interface
3. app_rpt Processing - Audio is processed, mixed with telemetry if needed
4. Asterisk Core - Routes audio to connected nodes via IAX2
5. Network Transmission - Audio packets sent over internet to linked nodes
6. Remote Processing - Receiving nodes decode the audio
7. Radio Output - Remote nodes transmit your audio on their radios

All of this happens in real-time with minimal latency, creating the illusion that all the linked repeaters are directly connected.

Control Methods

Users can control AllStarLink nodes through:

DTMF Commands - Touch-tone sequences from your radio

• Link/unlink to other nodes
• Check system status
• Control autopatch (phone connections)
• Change node settings

Internet Applications - Software that connects directly without a radio:

• IAXRpt (Windows/Linux)
• Transceive (macOS)
• DVSwitch Mobile (Android)
• RepeaterPhone (iOS)

Web Portal - AllStarLink.org account for configuration and management

Different Node Types

Repeater Node - Full repeater system with transmitter, receiver, duplexer

Hotspot Node - Low-power personal node, often handheld-sized

Hub Node - Virtual node for permanently linking multiple nodes together (e.g., linking VHF and UHF repeaters)

Remote Base - Allows remote control of a radio station

Radioless Node - Software-only node for internet-based connections without actual radios

Hardware Requirements

Minimum: Raspberry Pi 3 with 1GB RAM, SD card, USB sound interface

Recommended: Raspberry Pi 4/5 or x86 PC with 2GB+ RAM for better performance and multiple nodes

Enterprise: Dedicated servers can handle 25+ simultaneous connections

Network Architecture

The AllStarLink network operates in a peer-to-peer fashion:

• No central reflector required
• Each node has full conferencing capability
• Direct connections between nodes
• Distributed infrastructure with redundant servers for node lists
• Over 10,000 active nodes as of 2024

Key Advantages

1. No Proprietary Hardware - Runs on commodity computing platforms
2. Open Source - Free software, modifiable by users
3. Flexible - Can support many different use cases and configurations
4. Full-Featured - Complete repeater controller, not just a link adjunct
5. Secure - Owner controls who can connect
6. Scalable - From single-node hotspots to complex multi-site systems

The Result

AllStarLink essentially creates a global network where amateur radio operators can link repeaters and communicate across vast distances using a combination of radio and internet technology—all controlled by sophisticated but accessible open-source software running on inexpensive computers.