Dispatch your TETRA network.
TETRA is the network emergency services and critical infrastructure are built on, and it is not going away. Respondr bridges it into an IP dispatch console so a browser operator, a smartphone in the field and a TETRA handset share the same channel.
Related pages
This page is about dispatching a TETRA network. The gateway hardware, the DMR equivalent and the public-safety use case have their own pages.
TMO and DMO, onto IP.
The FunkTronic FT638 sits between the TETRA network and Respondr and translates both audio and signalling. The control channel carries call state and the ISSI of the transmitting subscriber, so the console knows who is speaking, not just that someone is.
Talkgroups, patching and priority.
Each TETRA talkgroup becomes a channel the dispatcher can monitor, transmit on, and patch to another network. Per-channel permissions decide who hears what, so a shared platform does not mean a shared radio picture.
What was said, and when.
Critical networks come with accountability. Every transmission is recorded with its channel, time and subscriber, searchable from the console, with optional transcription — and every administrative action is logged separately.
Why bridge a TETRA network at all
TETRA does voice and resilience extremely well. These are the things it was never meant to do, which the platform adds around it.
Talkgroups as channels
Emergency alerting
Positions and coverage
Recording and audit
Cross-network patching
People without a terminal
TETRA support at a glance
| Capability | Detail |
|---|---|
| Modes | TMO trunked and DMO direct |
| Gateway | FunkTronic FT638 (also covers DMR Tier I, II and III) |
| Signalling | Call state and subscriber ISSI over the control channel |
| Audio on the radio side | G.711 over RTP, with jitter buffering |
| Mixed networks | TETRA, DMR and analog channels in the same console |
| Deployment | On-premise, EU cloud or hybrid |
Frequently asked questions
The FunkTronic FT638. It is the active TETRA gateway, and the same unit also covers DMR Tier I, II and III — so a mixed TETRA and DMR site does not need two different products.
Yes. The control channel carries the ISSI of the transmitting subscriber, so the console shows the identity live and stores it with the recording.
Both. Trunked (TMO) and direct (DMO) operation are supported through the gateway.
Yes. Both networks are bridged into the same platform, and a dispatcher can patch a TETRA talkgroup to a DMR talkgroup for as long as an incident lasts, then separate them.
No, because the TETRA network keeps operating on its own. Bridging adds a dispatch layer alongside it; if the platform or its connection were lost, the radios keep talking to each other exactly as before.
Yes. The whole platform installs on your own hardware inside your network, which is the usual choice for operators running TETRA in the first place.
See Respondr on your networks.
A 30-minute live demo with your radio infrastructure in mind.