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 2560 · AllStar 51018
Node 2560 is the WIN System destination used for Insomniac Trivia and TechNet; node 51018 is the W6EK destination used for Coffee Break and the weekly club net. They are hangouts and scheduled destinations, not personal K6RCS nodes.
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 number | AllStarLink network identity for a node. |
|---|---|
| Callsign/account | Portal/user identity associated with the node. |
| IAX/VoIP | Network transport layer used for node linking. |
| Radio interface | USB/audio/radio hardware and COS/PTT configuration for RF nodes. |
Setup order
- Request/confirm the AllStarLink account and node number before installation.
- Install current ASL3 using the official path appropriate to the hardware.
- Secure the host and management access before exposing services.
- Configure one node and local audio/PTT first.
- Make one known connection, verify audio levels and disconnect behavior, then add automation or bridges.
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.