Capabilities
Explore what DIGI HAM LINK does, what each account can control, and which capabilities depend on server configuration.
On the application sign-in page, choose Register new account. Administrator approval is required.
Open DIGI HAM LINK on a desktop computer or Android phone using the secure application address. Microphone access requires a compatible browser, an available audio input and permission to use it.
You can listen and transmit without a local MMDVM hotspot for the browser audio path. Browser support and device permissions still matter.
Add the supported web app to your Android home screen for a focused way to launch DIGI HAM LINK. Installation happens through the app’s install option or the browser’s available install menu.
This is an installable web app, not a native background radio service. Screen locking, app switching and power-saving settings may interrupt audio.
Choose shared access when registering. You supply your callsign, name, email and DIGI HAM LINK password; your own AllStar number and node registration password are not needed.
After approval, the assigned shared room provides access to its linked systems. The owner controls those links; membership does not automatically grant network administration.
The personal-node option collects your AllStar node number, node registration password and hosting authorization alongside your account details.
Administrator approval and successful server configuration are required. An already operating registration must be coordinated before hosting the same node here.
A prominent PTT control, Disconnect and Reconnect audio controls support the everyday operating flow. Incoming playback, microphone gain and server audio tests are grouped in Settings.
Gain adjusts your microphone level; it does not turn PTT on or fix network routing. The configured transmission limit is 120 seconds.
Reported callsigns appear prominently in the radio display, with observed activity and last-heard information when available.
A callsign can be unavailable or reported by a linked system. A moving microphone meter or transmit indication does not prove a distant station heard intelligible audio.
Search the active reporting-node directory by number, callsign or location. Enter a known number directly, use favorites and recent nodes, and review connected links from Nodes.
Listen, two-way and disconnect actions depend on account permissions. Single destination can disconnect other remote links before making a new connection. Active listings are not guarantees of availability.
The shared bridge connects the hosted system to a selected BrandMeister talkgroup. Owner controls select the group, request connection or disconnection, and show observed bridge and service status.
Shared users follow the room’s selected group. This is not an individual DMR device identity or private talkgroup session for every user. A configured network login and working audio bridge are required.
Owner tools review registration requests and license documents, manage accounts, inspect dashboard sessions, set permissions and monitor server health.
The Users page separates registrations, accounts, connected dashboard sessions and settings. Monitoring supports capacity planning; it does not promise a fixed maximum number of users.
Additional configurations
A separately configured shared YSF bridge can provide supported narrow voice (DN) access to a selected reflector. Reflector selection and permissions depend on the enabled bridge. Wide voice and direct browser-to-reflector UDP operation are not implied.
EchoLink requires its own validated station and appropriate server configuration. Available connection controls depend on the station type, permissions and network setup. A website account does not create an EchoLink registration.
Start with your callsign
Request an account, wait for approval, and explore the systems linked to your assigned room. Shared access does not require your own AllStar node credentials.
For licensed amateur radio operators. Approval is required before you can sign in. Available controls depend on your account permissions and configured bridges.