Skip to content
Respondr

RoIP gateways connect your radio network.

The gateways connect your analog, DMR, TETRA, NEXEDGE and P25 infrastructure to Respondr, without replacing the radio fleet or rebuilding the existing installation.

Schedule a demo
A hand holds a smartphone with the Respondr app open on the PTT screen of a channel, in front of a Radio Data BS2500 master base station mounted in a rack.
Compatibility

Supported gateways and base stations

The table shows the radio networks each gateway connects to Respondr and whether the gateway works with the standalone console or only with the server.

  • FT636B

    FunkTronic, RoIP gateway

    Radio networks
    • Analog VHF/UHF
    Works with
    Standalone console and Respondr server

  • FT638

    FunkTronic, RoIP gateway

    Radio networks
    • DMR Tier I, II, III
    • TETRA
    Works with
    Standalone console and Respondr server

  • BS2500

    Radio Data, Base station

    Radio networks
    • Analog VHF/UHF
    • DMR Tier II, III
    Works with
    Respondr server only

  • RSP-Z2, ACU-Z1, STR-Z3

    JPS, RoIP gateway

    Radio networks
    • Analog VHF/UHF
    • P25
    Works with
    Respondr server only

  • NXR-1000

    Kenwood, Base station

    Radio networks
    • Analog VHF/UHF
    • DMR Tier II
    • NEXEDGE
    Works with
    Respondr server only

  • Kairos

    Radio Activity, Base station

    Radio networks
    • Analog VHF/UHF
    • DMR Tier II, III
    Works with
    Respondr server only

  • RA

    Radio Activity, Base station

    Radio networks
    • Analog VHF/UHF
    • DMR Tier II
    Works with
    Respondr server only

  • TG660

    Becker Avionics, Base station

    Radio networks
    • Aeronautical VHF
    Works with
    Standalone console and Respondr server
01. Interoperability

Multiple radio networks on one platform.

You can connect analog VHF/UHF radio networks, including maritime and aeronautical VHF, with DMR, TETRA, NEXEDGE and P25 digital radio networks.

A VHF gateway serving a helicopter, a boat and a handheld radio, and a TETRA gateway serving a fire engine, a patrol car and a handheld radio: both are cabled to the same Respondr core, which feeds a desktop console and a touchscreen console.
02. Connection methods

Donor radio or direct IP.

You can install the gateway quickly through a donor radio, or connect it directly over IP to master and remote base stations, depending on the site.

A smartphone with the Respondr app on the PTT screen of a channel, in front of a radio rack: a radio gateway is mounted above two vehicle radios used as donor radios.
03. Reliability

The gateways have built-in redundancy.

The FT636B and FT638 gateways have two LAN ports: you can connect them to two separate networks. If one network fails, the gateway stays connected through the other. If a link drops, Respondr restores it by itself within a few seconds.

The FunkTronic FT636B gateway seen from the back: two RS232 ports, the Radio 1 and Radio 2 connectors and two Ethernet ports, ETH 1 and ETH 2.

All the technologies the gateways support

The gateways connect the analog and digital radio networks you already have to Respondr, without replacing your radios.

Analog VHF / UHF

Professional analog VHF and UHF radios, base stations and repeaters connect through a 4-wire E&M interface.

Maritime and aeronautical VHF

It covers the maritime band for ports and coastal traffic, and the aeronautical band for the tower, the apron and ground handling.

DMR

It covers conventional Tier I and Tier II plus trunked Tier III, with the radio IDs kept along the whole path.

TETRA

Terrestrial trunked radio for mission-critical operations connects through the FT638 gateway.

NEXEDGE / NXDN

It covers conventional and trunked NXDN digital radio through Kenwood NXR base stations.

P25

P25 digital radio connects through the JPS RSP-Z2 and ACU-Z1 gateways (DFSI interface) or through a donor radio.

Radio over IP: the protocols Respondr uses

Radio over IP (RoIP) means carrying the voice and signaling of a radio network over an IP network. These are the protocols Respondr uses to communicate with the gateways.

RTP over UDP

The voice travels in RTP packets over UDP, the standard for real-time audio: a lost packet does not hold up the packets that follow.

Control over TCP

PTT, channel status and call control travel over a TCP link that is separate from the voice.

RoIP+

Voice and control travel over the same TCP link. The gateway can also open the link to the server itself, which is useful when the gateway sits behind a firewall.

Shared key

Where the protocol provides for it, the gateway and the server identify each other with a shared key before they exchange any voice.

G.711 toward the radios

Toward the gateways, the voice uses G.711 coding at 8 kHz, the telephony standard.

Opus toward the app

Between the server and the smartphone app, the voice is coded with Opus, a codec that needs less bandwidth on the mobile network. The server converts the voice between G.711 and Opus.

Frequently asked questions

A RoIP (radio over IP) gateway connects a radio network to an IP network. It turns the radio audio and call signaling into IP packets, so the Respondr server can deliver them to smartphones, consoles and other radio networks, and it does the reverse for the voice to be transmitted on the radio network.

We’ll show you Respondr in a live demo.

We offer a 30-minute live demo built around your radio infrastructure.

Schedule a demoContact us
RoIP Gateway Integration: Analog, DMR, TETRA | Respondr