Keep Zello in the conversation
Link one encrypted push.tt channel to one Zello channel. Voice moves both ways, so teams can work together while you move one crew, site or shift at a time.
One channel, both teams
You do not need a fleet-wide cutover to let the two sides talk. Start with the conversation that matters, keep everybody else where they are, and move the next group when the operation is ready.
- One push.tt channel maps to one Zello channel. Dispatch can cross over without exposing every other conversation
- Channel voice works in both directions. A transmission on either service is heard live by the people on the other
- Everything else stays separate. Unconnected push.tt channels and Zello channels are untouched
- Move at your own pace. Shift by shift, site by site, team by team — rather than picking one disruptive changeover day
What crosses the connector
Voice is the common language. Both services use 16 kHz Opus for the connected path, so the connector can relay packets instead of decoding and re-encoding every call.
- Live channel voice only. No one-to-one calls, text, locations, images or emergency alerts cross the boundary
- Nothing is re-recorded on the way through. The audio is passed along as it is, so it does not get thinner each time it crosses
- A handset too old for this is not passed through. It tells you so, rather than sending audio the other side would hear as noise
- No delayed collision replay. A Zello transmission that arrives while the push.tt floor is busy is dropped and counted, not played after the conversation has moved on
Encryption stops at an honest boundary
The connector is a real push.tt endpoint with its own device key. It decrypts on the host you operate, then submits that audio to Zello. That is the boundary, and every person in the push.tt channel can see it.
- Our servers still cannot hear any of it. The connector is treated like one more handset in the channel, nothing special
- Audio leaves push.tt end-to-end encryption at the connector. From that point onward, it is governed by the configured Zello network
- The notice is permanent. Connected channels carry a Zello disclosure wherever members choose or use them; an administrator cannot hide it
- Only governed, encrypted channels are eligible. Public or unencrypted push.tt channels cannot be connected
Run it where you control it
The connector runs on an always-on Linux host rather than inside either vendor's cloud. You control the machine, the Zello credential and the moment the link is revoked.
- Set it up in the console. Pick the channel, read what leaving push.tt means for privacy, and copy the one-time code
- Use a dedicated Zello Work user. Give it access only to the channel being connected
- Run Node.js 20 or later. The process reconnects both sides and reports its liveness back to the Console
- One active connector uses one standard device licence. Revoke it from the Console to stop its sessions and return that licence
Move one conversation, not everyone
Start with the channel that crosses teams most often. Tell us which Zello network, which channel and who needs to hear it on push.tt; that is enough to plan the first link.