Zello

None of these can be done from QSP, and each one is a common reason a first attempt does not connect. The channel must be joined by the gateway's own account in the Zello app before QSP can use it: logging on from a server does not join a channel. A Zello user has no radio, so the gateway transmits under a DMR ID of its own; sharing a repeater's or a hotspot's makes Zello traffic indistinguishable from that station's everywhere it is logged.

Read from this server's health report, the same one the overview page shows. It updates when you press Check again, and after every save. Green on all four means Zello users and radio users can hear each other.

Off keeps everything you entered, so pausing Zello never means typing it all again. On asks QSP to serve the connector a logon and to route the talkgroup below to the vocoder. It needs a restart of QSP to take effect.

The password and the private key never come back out of QSP. This page shows only whether each is stored and when it changed. They are kept encrypted in QSP's credential store and are not handed to anything but the connector, which is given a short-lived logon made from them and never the key itself. Each credential is stored the moment you press its button, separately from Save changes at the foot of the page. If your browser offers to fill the password, check it is not your console password.

The dongle turns DMR audio into ordinary audio and back. QSP reaches it through AMBEserver, usually on the machine the dongle is plugged into, port 2460. If the checklist says the vocoder cannot be reached, start AMBEserver; if it stops answering, unplug the dongle for ten seconds — a software reset does not clear a wedged chip.

AMBEserver runs as its own service, next to QSP, so the dongle keeps working whatever QSP is doing. Restarting it costs at most the call in progress: QSP sets the dongle up again at the next call. The buttons need the polkit rule in deploy/polkit/; without it they say so and change nothing. Every use is recorded in the audit trail, including a refused one.

A Zello user is not necessarily licensed, and their audio goes out over the air. So no repeater hears Zello until its owner has agreed, and none is chosen for you. The repeaters you list here both hear Zello and are heard on it; a repeater not listed is left out in both directions, so its users never hold half a conversation. This covers Motorola repeaters too, by their repeater ID; a Motorola repeater only keys up for a talkgroup and timeslot its own channel carries.

qsp-zello is a separate program because Zello's audio codec is a C library QSP does not include. It holds no password and no key: it asks QSP for a logon every time it connects. The two talk over two local ports, and the connector's file below is generated from these settings, so it cannot disagree with them.