Network status: all regions nominal

Coverage map

Dealer login

/

/

Connecting legacy two-way radios to a modern push-to-talk system

Product

Connecting legacy two-way radios to a modern push-to-talk system

You do not have to retire a working radio fleet to get wide-area push-to-talk. A gateway bridges selected channels between the old system and the new one. Here is how it works and what to check first.

Integrated Radio

·

A working radio fleet does not have to be replaced to add wide-area push-to-talk. A gateway, installed against the existing repeater or console, carries voice both ways between selected channels on the old system and talk groups on the new one, so a crew on old handhelds and a crew on new radios hear each other. This guide explains what the gateway does, what you need to know about your current system before anyone quotes, which channels to bridge, and the limits to plan around.

What a gateway actually does

The gateway sits between your radio system and the push-to-talk platform. On one side it connects to the repeater or a donor radio tuned to the channel you want bridged; on the other it carries the audio over IP to the push-to-talk service. When someone on an old handheld presses to talk, the audio is heard by everyone in the bridged talk group, including radios on the far side of the country. When a push-to-talk user speaks, the gateway keys the old system and the local handhelds hear it. Neither group changes how it works.

Only the channels you nominate are bridged. Local-only traffic stays local, so the wide-area fleet is not flooded with chatter that does not concern it, and the old system is not filled with calls from three counties away.

What we need to know about your current system

Compatibility depends on the specific equipment, and it is confirmed against your system before a design is proposed. Four details settle most of it:

  • Make and model of the repeater or base station, and of the handhelds.

  • Whether the system is analog or digital, and if digital, which standard, for example DMR.

  • How it is licensed and on which frequencies.

  • Roughly how many radios are in service and how the channels are used today.

With that, we can usually say whether bridging is practical before anyone commits to anything. Some systems bridge cleanly; others do not, and we would rather say so early.

Choosing what to bridge

Most operations bridge one or two shared channels and leave the rest separate. A plant might bridge its maintenance channel so that remote technicians and the on-site crew share it, while production traffic stays local. A town might bridge its public-works channel to the county system for storm response and keep parks and water separate. The design question is which conversations genuinely need both fleets in them, and the answer is usually short.

Permanent bridge or staged migration

Both are common. Some customers bridge permanently because the existing system does its job well: a licensed in-building system with good coverage has no reason to be retired, and the bridge extends it to vehicles and remote sites. Others use the bridge to move across in stages, keeping the old fleet running while new radios roll out department by department, then dropping the bridge once everyone has migrated. The gateway makes either plan workable without a flag day.

The limits to plan around

A gateway introduces a small amount of latency from the network path. It is normally acceptable for coordination traffic, and we discuss it in advance if your use case is sensitive to it. Audio quality is bounded by the older system: a narrowband analog channel sounds like one on both sides. Features that only exist on the push-to-talk side, such as GPS location, private calling and dispatch history, do not reach the legacy handhelds. And the licensed system remains the licensee’s responsibility; bridging does not change that.

What it looks like in practice

A facility fleet on the old repeater talks with regional and mobile users on push-to-talk. An existing system is extended to remote and traveling teams without a second repeater. A migration is phased rather than done in one weekend. A licensed system is kept for local use while wide-area coverage is added on top. The radio interoperability page sets out the service, and the municipal and public works and manufacturing pages show where it is used most.

If your old system was Nextel Direct Connect rather than a conventional repeater, the path is different: there is nothing left to bridge to, and what happened to Nextel explains what replaced it. For everything else, send us the four details above and we will tell you whether a bridge is practical.

Get started

Talk to a specialist

Tell us how your team communicates today and we will tell you what we would deploy.