AllStar Link vs. EchoLink

W7RPT • Technical Education • Las Vegas, Nevada

AllStarLink vs. EchoLink

A practical guide to internet-linked amateur radio, audio quality, repeaters, hubs and radioless operation

How the systems really work, what separates them, and how to get on the air with the Sin City Repeater Group.

Radio communication, connected by IPRF REPEATERLINKED IP NETWORKRADIO OR APP

Sin City Repeater Group, Inc. | Technical resource | Updated November 20, 2026

Imagine keying a handheld radio in Las Vegas and talking to an operator in Buffalo, New York, as though both of you were using the same local repeater. Or imagine checking into a net while traveling, with only a smartphone and an internet connection. AllStarLink and EchoLink make these kinds of conversations possible by transporting amateur radio voice over IP networks. Both are valuable tools, but they solve different problems exceptionally well.2,3

At the Sin City Repeater Group, Inc. (W7RPT), we use internet linking to extend the reach of amateur radio, connect operators across different communities and encourage hands-on technical education. This guide is intended for newly licensed amateurs, experienced operators and repeater trustees who want to understand the technology behind these connections and choose the right tools for their stations.31,25

AllStarLink

Build and link a network.

Ideal for configurable repeater controllers, hubs, remote bases and personal nodes. A clean μ-law path can sound less processed than a traditional GSM link.2,7

EchoLink

Connect wherever you are.

Low-barrier access for licensed operators using a phone, computer or browser, plus RF gateways and conferences.3,9

1. How AllStarLink and EchoLink actually work

EchoLink: easy access, worldwide station directory

EchoLink validates licensed amateur radio operators and makes participating stations discoverable by callsign and node number. Its Windows software supports individual users and RF-connected station operators (sysops); it also offers free Android, iOS and web editions. An RF gateway can connect an amateur frequency to the network, an individual user can operate with a microphone and speaker, and a conference server can bring several participating stations together. A callsign ending in -R designates a repeater gateway; -L designates a simplex link.3,4,5

EchoLink is sometimes described as entirely centralized. That is an oversimplification: its directory and validation services are centralized, but traditional direct station-to-station EchoLink audio normally travels between the two stations rather than through the directory. Proxy and web connections are exceptions; a dedicated conference server also carries the audio of its participants.6,10

AllStarLink: a programmable radio-linking and control platform

AllStarLink uses Asterisk, an open-source telephony platform, with the amateur-radio-specific app_rpt application. Nodes exchange voice and signaling using IAX2 (Inter-Asterisk eXchange, version 2). A server may host a repeater node, a simplex radio, a personal radioless node or a hub, and multiple nodes can reside on one server. AllStarLink uses registration, authentication and directory/DNS services to establish public-node connections, but the voice path of a direct link runs between the nodes.2,7,11,12

EchoLink direct connection

EchoLink direct voice pathDirectoryValidation and lookupUser / RFgatewayDestinationstationVoiceAudioLookup / validation

Directory helps stations find and validate each other. Web/proxy and conference paths can have an intermediary.6,10

AllStarLink repeater network

AllStarLink hub and node topologyRepeaterASL nodeRemoterepeaterPersonalnodeLocal hotspotASL hubIAX2 linksVoice

Registration and DNS help establish authorized links; audio travels via node-to-node IAX2 links.2,12

For repeater trustees, the distinction is control. AllStarLink provides configurable repeater logic, link management, timeouts, hang time, courtesy tones, telemetry, remote commands and audio-interface settings. EchoLink also supports RF gateways and sysop functions, but it does not replace the full programmable repeater controller and interconnected hub architecture offered by app_rpt.13,14,15

2. AllStarLink vs. EchoLink at a glance

FeatureEchoLinkAllStarLink
Best fitIndividual contacts, travel, casual operating, RF gateways and conferences.Permanent repeater linking, controllable hubs, hotspots and personal nodes.
Getting startedValidated callsign; free official app or web browser.Validated portal account; compatible client, or register and configure your own node.
Media pathUsually direct between traditional stations; proxies, web and conferences are exceptions.Direct IAX2 node links, optionally through one or more hubs.
Typical voice encodingTraditional EchoLink interoperability uses GSM full-rate narrowband audio.Negotiated codec; ASL3 defaults prioritize G.711 μ-law, then ADPCM, then GSM.
Multiple linksSupports gateway conferencing and dedicated conferences.Router-like hub and node topology; configurable monitor and transceive links.
RF integrationSysop mode or compatible gateway, with PTT and carrier detection or VOX.Radio interface drivers, PTT, COS, audio tuning, duplex and repeater control.
FirewallLegacy direct mode: UDP 5198–5199; outbound TCP 5200. Web/proxy can avoid forwards.Inbound node service normally UDP 4569; alternate IAX2 ports possible.
CostOfficial user software is free; RF equipment or dedicated conference may add costs.Software is open source; node computers, interfaces, hosting or third-party apps may cost money.

Comparison sources.2,3,5,6,7,8,10,16,17,18,19

3. Why can AllStarLink sound better?

A codec is a method of representing audio digitally for transport. The sample rate describes how many measurements of a waveform are made per second; the bit rate is how much encoded audio data is sent per second. They are different measurements. A codec can use fewer bits to represent speech efficiently, but aggressive compression may remove detail or introduce audible artifacts.8,18

Typical encoding choices

Voice payload bit rates compared
Codec voice payload rates064128192256kbit/sGSM full rateADPCM / G.726G.711 μ-law / A-lawG.722Linear PCM, 8 kHzLinear PCM, 16 kHz13.2326464128256
Red: traditional EchoLink GSM. Charcoal: commonly preferred ASL3 μ-law. Bars are proportional to encoded voice payload, not audio quality, and exclude transport overhead.7,8,18,20,43
CodecTypical payload bit rateWhat it means for amateur radio
GSM full rate13.2 kbit/s, 8 kHz samplingSpeech-oriented compression used by traditional EchoLink links; also supported by ASL3.
G.711 μ-law / A-law64 kbit/s, 8 kHz samplingLow-complexity companded PCM; μ-law is preferred in the documented ASL3 default radio stanza.
ADPCM / G.726Typically 32 kbit/sLower-bandwidth alternatives. ASL3 defaults enable ADPCM; G.726 AAL2 is a configurable option.
G.72264 kbit/s, widebandAvailable in Asterisk and configurable in ASL3, but not enabled in the documented default radio stanza.
Signed linear PCM128 kbit/s at 8 kHz, 16-bit mono; 256 kbit/s at 16 kHzHigher-bandwidth option when both endpoints and the complete audio chain support it.

Payload rates exclude network headers, signaling, retransmissions and other traffic. Sources.7,8,18,20,43

Understanding codec negotiation: AllStarLink’s standard radio configuration explicitly orders μ-law, ADPCM and GSM; it shows G.722, G.726 AAL2 and iLBC as optional commented-out entries. Neither Codec2 nor Opus is a documented default ASL3 radio-link codec. Traditional EchoLink interoperability uses GSM audio, rather than a universal iLBC default. Support in a general-purpose telephony package does not mean that a codec is deployed, negotiated or passed end-to-end by a repeater network.7,18,20

Bandwidth is not the same as fidelity

Traditional EchoLink’s 8 kHz sampled audio and the usual ASL3 μ-law link are both narrowband. Their different encoding methods can nevertheless yield substantially different listening experiences. GSM is designed to represent speech economically, while G.711 uses more bits to retain the waveform. A clean μ-law path may sound less processed, but it is not automatically 7 kHz wideband or broadcast-quality. A radio’s microphone, audio filters, deviation and receiving equipment can impose much narrower limits than the codec. A typical RF repeater remains a voice communications system, not a hi-fi stereo service.7,8,18,21

Latency depends on the entire path: encoding, packetization, network travel, jitter buffers, bridge processing, hub hops and RF hang time. A higher-quality codec does not guarantee lower delay. During a linked net, wait for the repeater or network to finish transmitting before keying, pause briefly after pressing PTT, and leave room for remote stations to break in.9,14

Five things to check before blaming the codec

01Microphone

Check gain, noise and distortion.

02RF signal

Compare local RF with the IP monitor.

03Audio levels

Verify RX, then TX with test equipment.

04Network

Look for packet loss, jitter and weak Wi-Fi.

05Codec / bridge

Verify the negotiated format and transcoding.

Suggested diagnostic sequence.9,21,22,23 For an isolated EchoLink audio test, connect to *ECHOTEST*, which plays back your transmitted audio. For an ASL node, use an authorized echo/parrot test or compare through a known-good node.

4. Nodes, hotspots and radioless amateur radio

New operators frequently assume they must purchase a radio, Raspberry Pi or repeater before using internet-linked amateur radio. That is not true. There are four distinct approaches, and choosing the right one can avoid unnecessary equipment purchases.3,17,24,25

Phone and computer
No RF hardware

1. Software client

Equipment: Phone, PC or browser; validated account; internet access.

Operate using EchoLink or a supported AllStarLink app, subject to destination permissions.

Radioless AllStar node
No RF transmitter

2. Personal radioless ASL node

Equipment: Supported computer, ASL software, microphone/PTT and speaker or client; node number for public registration.

Your own programmable endpoint and identity without transmitting RF.

RF hotspot and handheld radio
Local low-power RF

3. RF hotspot / simplex node

Equipment: Computer, radio interface or integrated RF module, antenna and handheld radio.

Creates a local RF access point. A SHARI-style node with a radio module is not strictly radioless.

Repeater and cloud hub
Infrastructure

4. Repeater or cloud hub

Equipment: Repeater and radio interface, or supported server/VM; network and access controls.

Repeaters provide RF coverage. Hubs connect nodes and may operate without RF equipment.

Sources.17,24,26,27 A generic USB sound card may work for some audio-only uses; radio control requires appropriate PTT/COS support and a compatible interface.

A modern 64-bit Raspberry Pi, repurposed x86-64 thin client or mini PC, or Debian virtual machine can be suitable for ASL3, depending on the application. When building an RF node, budget for its power supply, storage, enclosure, audio interface, cables, radio and antenna, not just the computer. A cloud hub needs hosting and network resources but not a physical radio interface. For many first-time operators, starting with an existing smartphone or PC is the lowest-cost route. Confirm current pricing, complete kit contents and compatibility before buying.26,27,28

How to start with AllStarLink

  1. Create a verified account at allstarlink.org and complete the licensing verification process.
  2. If using an external application, choose a supported client and connect to a node that allows app access; a personal node number is not always necessary.
  3. If building a registered node, request a node number, select supported hardware and install the current ASL3 distribution.
  4. Configure the correct node type, test audio, and make a controlled first connection to an authorized destination.11,17,24,26

How to start with EchoLink

  1. Install an official app or open EchoLink Web.
  2. Validate your callsign through EchoLink and sign into your individual-user account.
  3. Test microphone audio with *ECHOTEST*; then find the desired station by callsign or node number.
  4. Listen before transmitting, follow the destination system’s rules, and identify properly.3,4,9,10

5. When both systems work together

One network, multiple access technologies
Illustrative analog and digital network bridgeEchoLinkGateway interfaceAllStarLinkHub / app_rpt nodeAnalog FMRF repeater / nodePCM audioDVSwitch bridgeAudio / vocoder conversionDMRP25NXDNSystem Fusion
Conceptual topology, not a claim that every W7RPT mode is directly interconnected. All links require appropriate software, vocoder support, configuration and authorization.23,29,30,31

AllStarLink can support EchoLink gateway connections using the chan_echolink channel driver. A repeater network may expose both services, allowing an EchoLink user to communicate with operators on an AllStar-linked RF repeater. This does not make the protocols interchangeable: the gateway terminates each protocol and translates the audio between them. Administrators should also understand EchoLink’s restrictions for dedicated conference servers and its documented channel-driver limitations.5,29

DVSwitch can bridge analog PCM audio to digital voice systems using components such as Analog_Bridge and MMDVM_Bridge. Depending on the bridge, vocoder and network configuration, systems such as DMR, P25, NXDN and Yaesu System Fusion can be interconnected. The RF modes themselves do not become interchangeable: an analog FM handheld does not gain the ability to transmit P25 or DMR modulation. A properly configured gateway can translate the voice and signaling between supported networks. Each additional conversion is also an opportunity for quality loss, delayed PTT or incompatible metadata.23,30,31

Systems engineering principle: More connections are not always better. Avoid redundant audio paths that can cause echoes, unintended keying or loops. Maintain documented topology and only bridge networks where the administrators permit it. EchoLink’s dedicated conference policy prohibits most cross-network linking, even though AllStarLink supports an EchoLink gateway. Those are separate capabilities and policies.5,29

6. Frequently asked questions about AllStarLink and EchoLink

Operator experiences illustrate why both platforms deserve a place in amateur radio. Some prefer the audio and flexibility of AllStarLink, while others value EchoLink for travel, monitoring a familiar repeater or getting on the air before purchasing a radio. Still others prioritize the ability to communicate directly on RF when internet infrastructure is unavailable. These are complementary priorities rather than mutually exclusive choices.1

Q1. What are the actual audio sample rates of the two systems?

Traditional EchoLink GSM audio is sampled at 8,000 samples per second. Its GSM payload is roughly 13.2 kbit/s. ASL3’s commonly preferred G.711 μ-law codec also operates at 8,000 samples per second, but carries 64 kbit/s of voice payload (approximately 4.85 times the data rate). G.722 uses 16 kHz sampling and can carry roughly 7 kHz of audio bandwidth, as can compatible 16 kHz signed linear PCM paths; that is not the ASL3 default or a guarantee of RF audio bandwidth. The negotiated codec and actual path determine the sample rate, rather than the platform name alone.7,9,18,20,43

Q2. Does AllStarLink keep working if the internet goes down?

What survives a WAN outage?
Local RF and remote IP resilienceLocal RFPublic WAN outageRemote RFMay continue locallyMay continue locallyRemote path unavailableIf powered and configuredNo audio across broken WANIf powered and configured
Illustration of a failed internet path, not a universal guarantee of station operation. Local repeaters and private IP links may remain usable depending on configuration, power and network conditions.12,38,39

It depends on what goes down. If the WAN route between a Las Vegas node and a Buffalo node fails, the public internet link cannot carry audio. Depending on configuration, a powered local repeater may continue local RF operation. Private ASL nodes on an intact LAN or private IP network can be configured with static routes and node mappings without using the public directory. An already-established direct link may survive a directory outage while its actual IP path remains available, but new public connections or app authentication can be affected. EchoLink likewise distinguishes directory services from the media path.6,12,38

For emergency communications, build layers of resilience: independent RF paths, local repeater operation, backup power, redundant backhaul where practical, and a rehearsed fallback plan. AREDN amateur-radio mesh networking can provide private IP connectivity for suitable services without depending on the public internet. A mesh is itself infrastructure and requires planning, power and radio coverage.39,38

Q3. Can I use these services to follow emergency or weather activity remotely?

Yes, provided the relevant system is available and authorizes the connection. The VoIP Hurricane Net, for example, uses EchoLink conference *WX_TALK* (7203) and IRLP reflector 9219 to help collect and relay reports to the amateur station at the National Hurricane Center. Follow current instructions for directed nets, listen-only feeds and reportable criteria; do not check in merely to satisfy curiosity during priority traffic. Internet linking complements, rather than replaces, local RF and other independent emergency communications capabilities.40,39

Q4. Can I get started with a Raspberry Pi 3 or 4? Is more RAM necessary?

Yes. ASL3’s installation documentation supports suitable 64-bit Arm and x86-64 systems, including Raspberry Pi 3, 4, 5 and Zero 2 W. Current recommended memory depends on installation type: the general Debian guide lists 2 GB as recommended, while the Pi appliance guide recommends 4 GB and a Pi 4B or 5B. A modest single-node system can have lower requirements than a multi-radio server or busy hub. Reuse supported hardware before buying anything, and consult the current compatibility documentation.28,41

Q5. Is a CM108 USB sound card all I need to build an AllStarLink node?

Not for a conventional radio-connected node. A CM108/CM119-family audio interface supplies the audio path and can provide GPIO for push-to-talk (PTT), carrier-operated switch/carrier detect (COS/COR) and sometimes CTCSS signaling. A simple unmodified USB audio dongle may omit accessible radio-control connections. DIY builders can modify compatible fobs, while commercial radio interfaces are designed to expose these connections. Confirm voltage levels, pinout, PTT polarity, audio type and compatibility with the radio before soldering or keying the transmitter. A radioless app needs none of these RF control connections.27,42,21

Q6. Why does audio sometimes drop out on my phone or a linked repeater?

A dropout is not by itself proof that one platform uses an inferior codec. Mobile networks may have variable coverage, congestion, packet loss or restrictive NAT; local Wi-Fi, gain settings, buffering and node configuration can contribute as well. Test on a different network, use an echo test, note which direction has the problem, and ask the remote node operator whether other stations are affected. For incoming ASL node connections, ensure that the configured IAX2 port and registration match the router; EchoLink Web or proxy access may provide an alternative when direct ports are unavailable.9,10,22,37

Q7. Do full duplex and multiple links mean everyone can talk at once?

No. Full duplex describes a system’s ability to transmit and receive simultaneously, such as a conventional repeater using separated input and output frequencies. A configured AllStar node supports various duplex and repeater-control modes, while a handheld or smartphone PTT session is normally operated as a one-person-at-a-time conversation. EchoLink also supports multiple stations in a conference. Wait for the channel to clear before transmitting, even if the network can technically mix audio.5,14

Q8. Can AllStarLink be used without a radio or personal node? What apps work?

Yes. Compatible clients include RepeaterPhone for iOS, DVSwitch Mobile for Android and other applications documented by AllStarLink. W7RPT also provides a QSO One setup guide for supported devices. Login-based app access uses your validated AllStarLink account and depends on the destination node’s authorization. A personal node number is needed when operating a registered node, not solely for app-based access.17,32

Important 2026–27 update: The AllStarLink project has published a transition from legacy WebTransceiver authentication to App Authentication (AppAuth). According to its current schedule, the transition begins December 5, 2026; legacy app login is scheduled to stop June 3, 2027, and unupdated nodes will lose app-connection support December 6, 2027. App users and node operators should keep software current and consult the official schedule. The change concerns authentication, not the replacement of the apps themselves.34

Q9. If I can see a node or repeater online, am I automatically allowed to use or link it?

No. A valid callsign, node registration or directory listing is not blanket permission to access another trustee’s equipment. Obtain authorization and observe system rules, particularly before sending DTMF commands or creating permanent links. U.S. repeater restrictions are permitted under 47 CFR § 97.205(e). Station identification requirements for applicable amateur transmissions remain in force under § 97.119. Use your own callsign, identify appropriately and remember that a radioless transmission may be retransmitted on RF.19,33,35,36

Q10. Will one platform eventually replace the other?

There is no technical necessity for one to eliminate the other. EchoLink remains an accessible route for licensed operators, while AllStarLink provides infrastructure control and highly configurable linking. Operators who travel may prefer EchoLink or an AllStar app; repeaters and multi-site networks may benefit from AllStarLink as a backbone and EchoLink as an additional gateway. Our practical conclusion is to select the platform based on its role, and to operate both when doing so improves access without compromising network stability or rules.2,3,29

7. Connect with W7RPT in Las Vegas and beyond

The Sin City Repeater Group is building an interconnected, operator-focused amateur radio community in Southern Nevada. Licensed operators can participate from local RF systems or through authorized internet-linked access. The primary general-operating starting point is AllStarLink hub 42230.25,31,32

AllStarLink · Start here
42230

Primary national feed and general operating.

EchoLink
N4NJJ-R · 881948

EchoLink repeater gateway.

AllStarLink
47366

High Desert feed.

AllStarLink
422314

Soapbox hub.

TGIF DMR
TG 1952 / 42230

Separate digital talkgroups through compatible access methods.

MMDVM P25
TG 47366

P25 talkgroup, distinct from the like-numbered ASL hub.

Destinations as published November 20, 2026; availability and permissions may change. Refer to the current W7RPT repeater directory and individual system policies.31

Our recommendation for first-time users: start with the radioless ham radio guide or QSO One setup guide, make a test connection, and introduce yourself on an authorized destination. If you wish to build your own node, contact the group and ask for technical mentoring. Do not assume that the existence of a public directory entry grants access to every affiliated repeater or remote control function.25,32,33

On your own node, or one you are authorized to control, the standard AllStarLink DTMF commands include *342230 to connect to hub 42230 in transceive mode, *242230 to monitor it, and *142230 to disconnect that link. These commands affect node links, not just your individual radio; consult local configuration and never issue them on another trustee’s system without permission.19,33

Learn. Build. Get on the air.

Whether you are newly licensed, returning to amateur radio after years away, or developing your own repeater or hotspot, you belong in a community that learns by doing. Come meet the operators behind W7RPT and become part of an active amateur radio network.

Clark County, Nevada

Join us locally.

Live in Las Vegas, Henderson, North Las Vegas or elsewhere in Clark County? Apply for local membership and get involved in technical training, on-air activities, repeater projects and mentoring.

Apply for Local Membership
Outside Clark County

Distance is no barrier.

Qualified licensed operators whose primary residence is outside Clark County may apply for free Non-Resident Associate membership, subject to membership consideration and applicable policies.

Apply for Free Non-Resident Membership

Membership information and application details.44

73 from W7RPT | lasvegashamradio.com

8. References and further reading

Online technical documentation and W7RPT resources reviewed November 20, 2026. Superscript reference numbers throughout the guide link directly to the corresponding entries below.

  1. Jeremy, N2UGS (member, Sin City Repeater Group, Inc., W7RPT). AllStar vs. EchoLink. September 17, 2025. Buffalo Amateur Radio Repeater Association Tech Net discussion and accompanying presentation. barra-tech.com/allstar-vs-echolink/
  2. AllStarLink. Welcome to AllStarLink. allstarlink.org
  3. EchoLink. Introducing EchoLink. echolink.org
  4. EchoLink. Callsign validation. echolink.org/validation/
  5. EchoLink. Conference Server Validation and Terms. echolink.org/validation/conf.jsp
  6. EchoLink. Frequently Asked Questions: Servers. echolink.org/faq_servers.htm
  7. AllStarLink Manual. iax.conf. allstarlink.github.io/config/iax_conf/
  8. Asterisk Documentation. Codec Modules. docs.asterisk.org/Fundamentals/Asterisk-Architecture/Types-of-Asterisk-Modules/Codec-Modules/
  9. EchoLink. Frequently Asked Questions: Audio Issues. echolink.org/faq_audio.htm
  10. EchoLink. EchoLink Web FAQ. echolink.org/faq_webapp.htm
  11. AllStarLink Manual. AllStarLink Portal. allstarlink.github.io/basics/portal/
  12. AllStarLink Manual. DNS Servers. allstarlink.github.io/adv-topics/dns-servers/
  13. AllStarLink. app_rpt software repository. github.com/AllStarLink/app_rpt
  14. AllStarLink Manual. rpt.conf. allstarlink.github.io/config/rpt_conf/
  15. EchoLink Help. Interfacing. echolink.org/help_ex/interfacing.htm
  16. EchoLink. Firewall Solutions. echolink.org/firewall_solutions.htm
  17. AllStarLink Manual. External Applications. allstarlink.github.io/user-guide/externalapps/
  18. Bruce Mack. MicroLink: EchoLink protocol supplement. Firsthand interoperable implementation and packet observations. github.com/brucemack/microlink/blob/main/docs/el_supplement.md See also AllStarLink releases, documenting GSM frames in its EchoLink channel driver: ASL3 Asterisk release notes.
  19. AllStarLink Manual. AllStarLink Standard Commands. allstarlink.github.io/basics/standardcommands/
  20. Asterisk Documentation. Audio and Video Capabilities. docs.asterisk.org/Operation/Asterisk-Audio-and-Video-Capabilities/
  21. AllStarLink Manual. Tuning a Radio Interface. allstarlink.github.io/web-ui/tuning/
  22. AllStarLink Manual. Basic Troubleshooting Tips. allstarlink.github.io/user-guide/troubleshooting/
  23. DVSwitch. Amateur Radio Digital Voice. dvswitch.org and DVSwitch software repository.
  24. AllStarLink Manual. Setting Up Your First Node. allstarlink.github.io/web-ui/first-setup/
  25. Sin City Repeater Group. Radioless Ham Radio: Apps & Setup Guide. lasvegashamradio.com/radioless-ham-radio/
  26. AllStarLink Manual. ASL3 Installation. allstarlink.github.io/install/
  27. AllStarLink Manual. USB Audio Interfaces. allstarlink.github.io/adv-topics/usbinterfaces/
  28. AllStarLink Manual. Debian Install and System Requirements. allstarlink.github.io/install/debian/install/
  29. AllStarLink Manual. EchoLink Configuration. allstarlink.github.io/adv-topics/echolink/
  30. DVSwitch. Analog_Bridge sample configuration. github.com/DVSwitch/Analog_Bridge/blob/bookworm/opt/Analog_Bridge/Analog_Bridge.ini
  31. Sin City Repeater Group. Repeater Directory. lasvegashamradio.com/repeaters-2/
  32. Sin City Repeater Group. QSO One Setup Guide. lasvegashamradio.com/qso-one-sin-city/
  33. Sin City Repeater Group. Closed Repeater System Policy. lasvegashamradio.com/scrg-closed-repeater-system-policy/
  34. AllStarLink Manual. App Authentication Changes. allstarlink.github.io/adv-topics/appauth/
  35. Electronic Code of Federal Regulations, 47 CFR § 97.205. Repeater station. ecfr.gov/current/title-47/chapter-I/subchapter-D/part-97/subpart-C/section-97.205
  36. Electronic Code of Federal Regulations, 47 CFR § 97.119. Station identification. ecfr.gov/current/title-47/chapter-I/subchapter-D/part-97/subpart-B/section-97.119
  37. AllStarLink Manual. 44Net Connect. allstarlink.github.io/adv-topics/44net-connect/
  38. AllStarLink Manual. Private Nodes. allstarlink.github.io/adv-topics/privatenodes/
  39. Amateur Radio Emergency Data Network. AREDN Overview. docs.arednmesh.org/en/latest/aredn_overview.html
  40. VoIP Hurricane Net. VoIP Hurricane Net Purpose. voipwx.net/voip-hurricane-net-purpose/
  41. AllStarLink Manual. ASL3 Appliance (Raspberry Pi). allstarlink.github.io/install/pi-appliance/
  42. AllStarLink Manual. Radio Connections. allstarlink.github.io/adv-topics/radio-connections/
  43. Internet Engineering Task Force. Schulzrinne, H. and Casner, S. (2003). RFC 3551: RTP Profile for Audio and Video Conferences with Minimal Control. § 4.5, audio encodings. rfc-editor.org/rfc/rfc3551.html
  44. Sin City Repeater Group, Inc. Application for Membership Consideration. lasvegashamradio.com/membership/

Educational material only. Network access, supported software, hardware compatibility and technical settings may change. Consult the current documentation, your station trustee and applicable regulations before configuring or operating a linked RF station.