Cross-Patching and System Bridging

Two-Way Radio Concepts and Electronics Fundamentals · Last updated · About 5 min read

Overview

Organizations routinely need radios on one system to talk to radios on another: a VHF (Very High Frequency) analog fleet to a UHF (Ultra High Frequency) digital fleet, a public-safety P25 (Project 25) system to a business DMR (Digital Mobile Radio) system, or a radio channel to a telephone. Cross-patching (or bridging) is the family of techniques that join two dissimilar channels or systems so audio — and sometimes signaling — flows between them. Every approach involves trade-offs in audio quality, delay, feature transparency, and operational risk; this page surveys the main options and their pitfalls.

Console/Dispatch Patch

The simplest bridge: a dispatch console operator selects two (or more) channels and activates a patch, and the console re-transmits whatever it receives on one channel out the other(s). No new hardware — any multi-channel console can usually do it, and the patch can be set up and torn down in seconds, which is why it's the workhorse of incident-driven interoperability (see Interoperability and Mutual Aid Channels).

Pitfalls to expect:

  • Audio levels: each patched channel was leveled independently; through the patch, one side often sounds hot and the other weak. Levels must be checked through the patch, not just per channel — see Audio Levels and Radio Interfacing.
  • Hang time and keying overlap: repeater hang time (the transmitter tail after each transmission) on one side can hold the patch keyed and block the other side's replies, or clip the start of them. Slow trunked-channel access on one side clips first syllables arriving from the other.
  • ID information lost: caller ID (PTT ID), unit aliases, and emergency indications generally do not cross a patch — the receiving system sees only the console transmitting. Dispatchers must relay identity by voice when it matters.
  • The patch occupies console resources and the operator's attention; an unmonitored patch left up after an incident is a common source of mystery traffic.

Donor-Radio Gateway Bridges

A donor radio on each system — each an ordinary subscriber radio — wired back-to-back so that receive audio and COR (Carrier Operated Relay, the receive-activity signal) from radio A drive transmit audio and PTT (Push-To-Talk) on radio B, and vice versa. The interconnection can be a direct cross-connect cable/interface box at one location, or an RoIP (Radio over IP) link with a gateway on each radio, letting the two systems be bridged across any distance — see RoIP (Radio over IP).

Strengths: works between any two systems a radio can subscribe to — analog or digital, any vendor, trunked or conventional — with no cooperation from either system's core. Weaknesses: consumes a subscriber radio (and channel grant) on each system; inherits every discrete-interface issue (levels, keying timing, COR accuracy); and passes only audio — no IDs, no emergency signaling. Proper COR-driven keying (not VOX — voice-operated switch — audio detection) is essential to avoid clipped and stuck transmissions.

Where both systems speak a common standard, a wireline interface preserves far more than audio. Standards-based links cost more and require coordination (and licensing of the interface on both cores) but are the right answer for permanent, high-trust interconnections. Analogous vendor-specific wireline interfaces exist within single-vendor ecosystems.

Analog↔Digital Bridging and Vocoder Tandeming

Bridging analog to digital channels (or one digital standard to another) forces the audio through multiple lossy conversions. Digital radio audio is compressed by a vocoder (voice codec) optimized for speech; when bridged audio is decoded and then re-encoded by another vocoder — tandeming — quality and intelligibility degrade, and transmission delay accumulates.

But the degradation is not uniform, and the distinction is practically important:

  • Same vocoder on both sides is nearly free. Measured intelligibility for a same-type tandem is essentially unchanged — roughly 91–92% for double-AMBE or double-CVSD, i.e. no meaningful additional loss beyond the first pass. Bridging DMR↔DMR, where both sides use the same vocoder family, costs far less than intuition suggests.
  • Crossing between different vocoders is where the damage happens. One study measured an average loss of more than 12% intelligibility transcoding between AMR and AMBE+2.

Design rule: count the encode/decode cycles end-to-end, and pay particular attention to how many times the audio changes vocoder family — not merely how many conversions occur. The strongest mitigation is to keep every talker on the same vocoder end to end, which is the core argument for standards-based links (below) on permanent digital-to-digital connections.

Delay Accumulation and Feedback

Every element in a bridge adds delay: channel-access time on each system, vocoder framing, RoIP buffering. Users experience late talk-permit, clipped openings, and "doubling" (both sides keying simultaneously because neither hears the other start).

The uglier failure is ping-ponging/feedback: system A's transmission keys the bridge into system B; something on system B (its repeater tail, a courtesy tone, noise opening squelch, or a second bridge back to A) keys the path back toward A, which re-keys toward B — and the patch oscillates, locking up both channels. Multiple parallel patches between the same systems, or a patch plus a phone interconnect (see Radio System and Phone System Integration), create loops nobody designed. Defenses: never bridge the same pair of systems by two simultaneous paths, use COR-based keying with sensible hold-off timers, respect hang times, and always supervise temporary patches.

Choosing an Approach

  • Momentary/incident need, channels already on one console → console patch: instant, reversible, operator-supervised.
  • Recurring bridge between systems with no common standard (or different vendors) → donor-radio gateway bridge, locally or over RoIP.
  • Permanent, feature-preserving link between like systems (e.g., P25↔P25) → standards-based interface such as ISSI.
  • Anything involving several digital hops → count vocoder passes first; if audio quality is mission-critical, favor the option with the fewest.

References

See also: CTI product documentation

This article is part of the CTI Products Knowledge Base. Questions about RadioPro or MCN products? Call +1 (513) 595-5900 or email info@ctiproducts.com.

Informational only. This article is general background and is not engineering, safety, legal or regulatory advice. Verify requirements with the equipment manufacturer and the applicable authority before relying on it. Product names and trademarks belong to their respective owners.