How Repeaters Work, Part 2: Microwave and Fiber-Linked P25 Multisite Simulcast

Independence notice: RunBoard is an independent operations platform and is not affiliated with, endorsed by, or sponsored by any company, product, network, or agency named in this article. Names are used only for identification and education.

From one site to many

A single repeater covers whatever its antenna can reach. On good terrain with a tall tower that might be a large area, but terrain is rarely good everywhere. Hills block signals, valleys swallow them, and a portable radio held at waist level inside a metal building has very little power to work with. The moment a jurisdiction is larger than one repeater can cover, or has dead spots that matter for safety, the answer is more sites.

The naive version of "more sites" is just several independent repeaters on different channels. That works, but it pushes the problem onto the user. Crews have to know which channel covers which part of the county, and they have to remember to switch as they drive. During a fast-moving incident that is exactly the kind of manual step that gets missed. The goal of a modern system is the opposite: the radio user should not have to think about which tower is carrying them. They key up, they are heard, they hear the reply, and the system quietly figures out the plumbing.

Reaching that goal means the separate sites have to stop behaving like separate radios and start behaving like one coordinated system. That coordination is the whole subject of this article, and it rests on two things a single hilltop repeater never needed: a reliable way to move audio and control data between the sites, and a way to keep every site agreeing on time.

Backhaul: the wires between the towers

Backhaul is the industry word for the transport that connects tower sites back to each other and to the system's central equipment. If the RF is what the radios hear, the backhaul is the nervous system nobody hears but everybody depends on. There are two common forms, and many systems use both.

• Microwave radio links. These are point-to-point beams between dish antennas on two towers that have line of sight to each other. A microwave hop can carry a large amount of digital traffic across many miles of open country without anyone trenching a cable. Systems chain hops together to reach remote mountaintop sites where running fiber would be impractical or impossibly expensive.
• Fiber optic links. Where a site can be reached by cable, fiber offers very high capacity and is not affected by weather the way a microwave beam can be. Agencies often lease fiber from a carrier or ride on a government fiber network that also serves other public buildings.

Each has trade-offs. Microwave is flexible and can be built to sites that fiber will never reach, but the path can be degraded by heavy rain, and a physical obstruction in the beam path, even a newly built structure or a grown tree line, can hurt it. Fiber is robust against weather but can be cut by a backhoe, and the agency may not control the route. This is why serious systems build the backhaul as a ring or a mesh rather than a single chain, so that if one link fails, traffic can travel the other way around and reach the site by an alternate path.

The network core that ties it together

Somewhere behind the towers is a set of central equipment usually called the core, or the master site. Think of it as the brain and switchboard of the system. The core is what turns a collection of tower sites into a single coordinated network. Its jobs include deciding how a call gets routed to every site that needs to carry it, keeping track of which radios are affiliated with the system and where they are, managing the assignment of channels, and connecting the radio system to other things such as dispatch consoles and, where authorized, other agencies' systems.

The core is also the natural point of failure to worry about, which is why well-designed systems make it redundant. That can mean duplicated core equipment, geographically separated so a fire or flood at one location does not take down the whole region, with automatic failover so the backup takes over if the primary stops responding. Some architectures also allow individual sites to keep operating in a limited, local-only mode if they lose their connection to the core, so that at least radios on the same tower can still hear each other when the backhaul is severed. That fallback is a safety net, not a substitute; wide-area coverage and cross-site talk depend on the core and the transport being up.

P25, short for Project 25, is the suite of standards that defines how these digital systems behave, published under the TIA-102 family of documents. The important thing P25 gives an agency is interoperability at the standardized boundaries: subscriber radios and systems built by different manufacturers can work together where the standard defines the interface. That matters for mutual aid, because a neighboring agency's radios should be able to operate on your system if they are authorized to.

Simulcast explained plainly

Here is the concept that trips people up, so we will take it slowly. In a simulcast system, several transmitter sites all send the same signal, on the same frequency, at the same instant. "Simulcast" is literally simultaneous broadcast. Instead of Tower A using one channel and Tower B using another, both towers, and possibly a dozen more, transmit identical audio on identical frequencies at identical times.

The payoff is that from the radio user's point of view there is only one channel and one seamless coverage blanket. A crew can drive across the entire simulcast area without ever changing channels and without any audible handoff. They are always inside the signal because every tower in the cell is painting the same signal over the whole region. No dead zones between towers, no "you are breaking up, switch to the north repeater." One system, one channel, everywhere it reaches.

If that sounds like it should not work, you have good instincts. Normally, two transmitters on the same frequency interfere with each other and turn into noise. The only reason simulcast works at all is that the transmissions are made identical to an extreme degree, and that requires precise coordination of both timing and signal content across every site. Get that coordination right and the overlapping signals reinforce into something a radio can decode cleanly. Get it wrong and you are back to interference.

• The audio and data sent to every transmitter must be the same bits.
• The moment each transmitter emits those bits must be aligned across all sites to a very small tolerance.
• The transmitters' frequencies must be locked to a common reference so they do not drift apart.

All three of those are the responsibility of the system's timing and distribution equipment, fed by the backhaul we just described. Which brings us to the single most important word in simulcast: synchronization.

Why timing is everything

To make many transmitters behave like one, the system needs a shared, extremely accurate clock. The common source is GPS. Every simulcast site has a GPS-disciplined timing reference, and because they are all locking to the same satellite time, they all agree on "now" to a very fine precision. The core distributes the audio and control data over the backhaul, and the timing equipment ensures each site launches its transmission at the coordinated instant so that the signals arrive at a radio in the overlap zones close enough together to reinforce rather than fight.

When synchronization is good, a radio in the overlap between two towers hears one clean signal. When synchronization drifts, that same radio hears the two copies arriving at slightly different times, and in a digital system the receiver can no longer line the copies up into a decodable stream. The result is audio that sounds garbled, watery, or that drops out, and the strange part is that it is often worst exactly in the overlap areas that were supposed to have the best coverage. Users right under good signal from two towers can have the most trouble, because that is where two slightly-misaligned copies collide most strongly.

None of this precision is visible to the person keying the microphone, and that is the point. The engineering exists so the user never has to think about it. But an administrator should understand that the smoothness of a simulcast system is not free; it is continuously maintained by clocks and transport working correctly every second.

Voting receivers and the uplink problem

Everything above is about the transmit side, the signal going out to the radios. The receive side has its own challenge. A portable radio held by a firefighter deep inside a building transmits with a small amount of power from a poor location. Getting that weak signal heard across a wide area is harder than blanketing the area with strong transmitters.

The solution is many receive sites and a process called voting. Rather than relying on one tower to hear the portable, the system places receivers at multiple sites across the coverage area. When the portable transmits, several of those receivers may pick it up, each with a different quality depending on distance and obstructions. Comparator equipment continuously evaluates all the incoming copies and picks, or votes for, the best one at each moment, stitching together the cleanest possible version of what the portable said. The result is retransmitted out through the simulcast transmitters to everyone.

• Transmit is a broadcast problem: one strong signal, painted everywhere, from many synchronized sites.
• Receive is a listening problem: many sensitive ears, with the system choosing the best-hearing one instant by instant.

Voting is why a member can be heard from inside a stairwell or a basement where a single distant tower would never have caught them. It quietly rescues the weakest and most safety-critical transmissions, and like the rest of the system it depends entirely on the backhaul carrying all those received copies to the comparator for judging.

Simulcast versus multisite trunking

Two terms get used loosely and are worth separating, because they describe different ways to cover a wide area.

Simulcast is what we have been describing: multiple sites transmitting the same thing on the same frequency at the same time, so the whole cell behaves as one channel. Its strength is seamless, dead-zone-free coverage over the simulcast area with the user never switching channels. Its cost is the demanding timing and the reuse of the same frequencies across every site in the cell.

Multisite trunking, sometimes discussed alongside the term multicast, takes a different approach. Each site has its own set of frequencies, and radios roam between sites, registering with whichever site they are currently using, similar in spirit to how a cell phone hands off between towers. The core routes a given call to whichever sites currently have radios that need to hear it. Rather than every site painting the same frequency in lockstep, sites operate more independently and the core coordinates who gets connected to whom.

Real regional systems frequently combine both ideas. A dense urban core might be covered by a simulcast cell for smooth in-building coverage, while outlying areas are separate sites that the radios roam between. From the user's seat the distinction is invisible; the radio handles it. From the administrator's seat the distinction matters because the two approaches fail in different ways and are planned, funded, and troubleshot differently.

It is also worth being clear about vendors. The two names most commonly encountered in P25 land-mobile systems are L3Harris and Motorola Solutions. Each builds complete P25 systems with its own internal architecture, its own core equipment, and its own approach to simulcast timing, voting, and network management. Both conform to the P25 standard at the defined interfaces, which is what preserves interoperability between agencies and between subscriber radios and infrastructure. The right way to think about it is that the standard defines the shared language, and each vendor implements a full system that speaks it. Neither approach is universally better; the fit depends on the region, the existing infrastructure, the budget, and the surrounding agencies a department has to interoperate with.

What a small department should understand

Most small fire and EMS agencies do not own the regional radio system. They are subscribers on a system owned and operated by a county, a state, or a shared regional authority. That is usually a good deal, because a single department could never afford to build and maintain a network of synchronized towers, microwave rings, redundant cores, and voting receivers on its own. But being a subscriber means your communications depend on infrastructure you do not control, and it is worth being honest about that.

• Your coverage depends on backhaul you cannot see. When crews report bad audio near a boundary or in a specific area, the cause may be a microwave path, a fiber cut, or a timing fault at a site, not the radio in their hand. Knowing that changes who you call and what you report.
• Timing failures look like radio failures. Garbled or watery audio, especially in normally strong areas, is a classic sign of a synchronization problem in a simulcast system. Report the symptom clearly and let the system's engineers diagnose it.
• Know the fallback behavior. Ask the system operator what happens if a site loses its connection to the core. Does it drop entirely, or does it keep local site radios talking? Ask whether there is a conventional or direct radio-to-radio mode your crews can fall back to when the wide-area system is unavailable. Practice it before you need it.
• Keep your own records straight. Which of your radios are programmed for which talkgroups, when they were last updated, which units carry which portables, and who your points of contact are at the system authority. When something goes wrong, that information is what lets you respond instead of guess.

The lesson of Part 2 is that a modern public-safety radio system is not a bigger repeater; it is a distributed system held together by transport and timing. The RF is only the visible surface. Underneath it, microwave and fiber move the traffic, a redundant core routes it, GPS keeps every site agreeing on the instant, and voting receivers rescue the weakest voices. When it all works, a crew member never thinks about any of it, and that invisibility is the whole achievement.

Independence notice: RunBoard is an independent operations platform and is not affiliated with, endorsed by, or sponsored by any company, product, network, or agency named in this article. Names are used only for identification and education.