Published reference

Node number · Asterisk/app_rpt · VoIP linking · RF interfaces

AllStarLink / ASL3

AllStar can be reached through fixed-site software and network nodes, but the troubleshooting order remains local audio, identity, network and destination. Change one variable at a time.

When the audio dies, guessing is not diagnostics.

Regular linked-system destinations

AllStar 51018 · W6EK

W6EK node 51018 is retained for regional conversation and scheduled nets. Check current connection policy; monitoring is intermittent.

Current AllStar node list

What it is

AllStarLink links amateur repeaters, remote bases and hotspots over VoIP. ASL3 is the current generation, built on modern Asterisk and Debian-based systems.

Where it fits at K6RCS

K6RCS uses AllStar as both an operating network and a systems-learning target through clients such as QSO One. It deserves its own setup discipline because a node is a server, network host, audio interface and radio system at the same time.

Identity and addressing

Node numberAllStarLink network identity for a node.
Callsign/accountPortal/user identity associated with the node.
IAX/VoIPNetwork transport layer used for node linking.
Radio interfaceUSB/audio/radio hardware and COS/PTT configuration for RF nodes.

Setup order

  1. Request/confirm the AllStarLink account and node number before installation.
  2. Install current ASL3 using the official path appropriate to the hardware.
  3. Secure the host and management access before exposing services.
  4. Configure one node and local audio/PTT first.
  5. Make one known connection, verify audio levels and disconnect behavior, then add automation or bridges.
Test sequence: prove receive first, then local RF/audio, then the network connector, then the destination, and only then cross-mode or bridging. Change one layer at a time. The goal is to know which layer works, not to get one lucky connection.

Common failure modes

  • Following ASL2-era instructions against ASL3 configuration files.
  • Giving services unnecessary root/sudo privileges.
  • Opening ports or dashboards broadly before authentication and firewall rules are understood.
  • Tuning RF audio and network routing at the same time.

Security and privacy

Do not publish passwords, API keys, device UIDs, hotspot security values, local IP addresses, management URLs, or detailed behavioral schedules. Keep backups of known-good codeplugs/configurations, use unique credentials, and document firmware/software versions before changing them.

Primary sources and directories

Established K6RCS AllStar favorites

AllStar is now an established fixed-site operating layer through QSO One. Geography still chooses the node.

RoleNodeSystemUse
Home VHF East57364W6RHC / GEARS146.850 − / PL 110.9, Forest Ranch; EchoLink companion 7818.
Home UHF East56934W6RHC / GEARS440.650 + / PL 110.9, Forest Ranch; WIN available on request.
WIN2560WIN SystemDirect QSO One favorite or link from GEARS UHF. WIN also publishes IRLP 9100 and EchoLink 126012.
Sierra / I-8051018W6EKAuburn/SFARC regional anchor and scheduled nets.
Bay Area55915Bay-NetUsually bridged to DMR TG 31075.

GEARS UHF → WIN from RF

On the GEARS 440.650 AllStar repeater, connect WIN with *3 2560, ask status with *70, and clear it with *1 2560 when finished. GEARS describes WIN as an on-request path rather than a permanent link.

Travel candidates stay candidates

Big Sur node 58633 and Utah node 43335 remain test candidates. Confirm current ownership, availability, RF linkage and client acceptance before relying on either.