FAQ

The fastest way is to sign in with your Google account from the Register page (or the Sign in with Google button on the Login page). The reflector administrator then performs a manual check:

• Your Google email address is compared against the e-mail you have published on qrz.com for your callsign.
• If they match, the account is approved and your callsign is added to the reflector’s user list.
• If they do not match, the admin may ask you to update your QRZ entry or to use a different e-mail address. This is the only way we have to reasonably verify that the person registering is actually the holder of the callsign.

You can still register without Google by entering a callsign and password directly, but a refadmin will need to verify your identity through another channel before approving the account, which usually takes longer.

The reflector is in the process of setting up an automatic provisioning procedure for new nodes (callsign + CSR upload → signed certificate, all from the web UI). It is not yet finished.

In the meantime, node registration is handled by e-mail:

1. Send a request to a reflector administrator including your callsign, the kind of node you want to connect (repeater, simplex, link, bridge, …), and the location.
2. The admin will reply with the connection parameters and either a pre-signed certificate or a CSR-signing exchange.
3. Once your node is up, expect a few short test transmissions while the admin tunes audio levels and verifies the link is well-behaved.

Please be patient — administration is done in our free time. Thanks for understanding.

No. Nodes connected to a satellite are free to select and monitor any talkgroup they want. The parent’s LOCAL_PREFIX only governs routing out to the wider trunk mesh — talkgroups whose number falls under that prefix are eligible to be carried over the parent’s trunk links to other reflectors. Talkgroups outside the prefix stay within the parent and its satellites.

Communication between satellites of the same parent always works, regardless of TG number: anything keyed on one satellite is relayed to every other satellite attached to the same parent.

One big caveat: each satellite admin can apply a TG filter on their side, which narrows the set of talkgroups carried in and out of that particular satellite. If you expect to hear traffic on a satellite and you do not, check with the satellite admin first — the filter on their end is the most common reason.