IP Site Connect

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

Overview

IP Site Connect is a Motorola MOTOTRBO technology that links multiple digital repeaters together over a standard IP network (the internet or a private WAN), so that they all re-transmit a call at essentially the same moment and behave as a single, unified conventional radio system spanning multiple physical locations.

Rather than being confined to the coverage area of one repeater at one site, an IP Site Connect network lets radios at geographically separate locations — different buildings, warehouses, cities, or even countries — communicate with each other in real time on the same logical channel, without users having to manually change channels as they move between sites.

IP Site Connect is not simulcast. Each linked site keeps its own repeater pair — its own transmit and receive frequencies — and a radio physically moves from one site's coverage footprint to another's by passively roaming between them based on signal strength, the same way it would roam between cell towers. True simulcast is a different technique entirely: multiple sites transmitting on the exact same frequency at the exact same instant, tightly synchronized against a shared GPS time reference, so a radio never has to leave one frequency at all. IP Site Connect achieves wide-area coverage with per-site frequencies and roaming; simulcast achieves overlapping coverage on one shared frequency with no roaming. Don't use "simulcast" to describe IP Site Connect's site-linking behavior — it's a different architecture solving a related but distinct problem.

How the IP Linking Works Conceptually

Each repeater site in an IP Site Connect network connects — over Ethernet, using IP/UDP — back to the rest of the network, with one repeater designated the Master and the others acting as Peers. When a radio at any one site keys up, that site's repeater digitizes the call and forwards it as IP packets to the Master, which in turn replicates and forwards the call out to every other linked site. Each of those remote repeaters then re-transmits the call over the air at its own site, on its own frequency pair, essentially simultaneously. The practical effect is that all linked sites behave as one unified conventional channel: a user at any site hears and can respond to a user at any other site without changing channels, even though the sites may be many miles (or countries) apart, and even though each site is physically transmitting on a different frequency. Because coordination is carried on the same IP path as the voice traffic itself, no separate system controller is required — the repeaters and the network handle call routing and relay timing between themselves. See MOTOTRBO Roaming for how a radio decides which site to use as it moves.

How IP Site Connect carries one call to every site A radio keys up at Site A. The Site A repeater, which holds the Peer role, sends the digitised call over IP using UDP to the Master repeater. The Master replicates the call to every peer, including Site A. Each site then retransmits on its own frequency pair, so radios at Site A, Site B and Site C all hear it. There is no separate system controller: the repeaters route the call between themselves over the same IP path that carries the voice. One call, every site, over the same IP linkThe repeaters route the call between themselves — there is no separate controllerRadio keys up at Site ASite A repeaterholds the Peer roledigitised callover IP (UDP)Master repeaterone repeater holds this roleThe Master replicates the call to every peer — including Site ASite Aretransmits on itsown frequency pairthe site the call came fromSite Bretransmits on itsown frequency paira radio here hears itSite Cretransmits on itsown frequency paira radio here hears itEvery site keeps its own frequency pair, so a radio never has to change site to be heard.Coordination rides the same IP path as the voice, which is why that link's delay and loss matter so much.
Because the coordination and the audio share one link, a site link that is merely “up” is not enough — it has to be steady.

The key idea the diagram makes concrete: every site transmits on its own frequency pair, yet users experience one unified channel. There is no separate system controller — the Master repeater and the IP path do the routing and relay timing themselves.

Because every site's repeater is depending on the IP link to receive and forward real-time voice packets, the WAN connection at each site needs to meet certain network-quality baselines or call quality and site synchronization will suffer:

  • Bandwidth — each site needs enough sustained IP bandwidth to carry the digital voice/control traffic reliably; the requirement scales with the number of simultaneous calls a site can be part of, but is modest compared to typical broadband or leased-circuit capacities.
  • Latency — Motorola's design target for round-trip latency between sites is under roughly 90 ms, with practical deployments reported to still function acceptably up to roughly 700 ms round-trip; end-to-end system delay is ideally kept under about 254 ms. The lower the latency, the tighter and more natural the cross-site relay behavior.
  • Jitter and packet loss — because voice is carried as a steady stream of small IP packets, the link also needs low jitter (variation in packet arrival time) and low packet loss; excessive jitter or lost packets manifest as choppy, garbled, or dropped audio, similar to problems seen on any real-time voice-over-IP link.

See IP Networking in Two-Way Radio Systems for a broader look at these network-quality considerations across all IP-linked radio systems.

Typical Failure Modes

Because each site depends on its IP/WAN connection to participate in the network, the most common failure mode is a site losing WAN connectivity — for example, an internet outage, a router/port-forwarding misconfiguration, or a failed leased circuit at one location. When that happens, the affected site is normally isolated from the rest of the linked network: its local repeater can typically still serve local users directly (falling back to local-only conventional coverage), but it can no longer relay calls to or from the other linked sites until connectivity is restored. Because IP Site Connect coordination is embedded in the repeaters themselves rather than a separate controller, a WAN outage at one site does not usually bring down the other sites' ability to talk to each other — only the isolated site drops out of the shared conversation.

Scale

IP Site Connect can link up to 15 repeaters at up to 15 different sites into a single network. For example, a manufacturing plant in one location could use IP Site Connect to let its radio users talk in real time with staff at up to 14 other warehouses, distribution centers, or satellite offices.

Infrastructure

  • No separate system controller is required — coordination among sites is handled by the repeaters themselves.
  • Motorola's RDAC (Repeater Diagnostics And Control) tool allows remote access to all linked sites for maintenance, configuration, and firmware updates.
  • Because it rides over a standard IP connection, there are no additional monthly service or spectrum access fees beyond the network connectivity itself.

Digital Requirement

IP Site Connect is a digital-conventional feature and requires DMR-capable MOTOTRBO repeaters and radios, since the cross-site linking and roaming behavior relies on DMR's digital protocol.

Supported Radio Series

IP Site Connect is supported by the following Motorola MOTOTRBO radio series:

  • XPR 3000 series
  • XPR 7000 series
  • SL 3500e
  • SL 7000 series
  • XPR 5000 series mobiles

Relationship to Trunked Systems

IP Site Connect itself is a conventional (channel-selection) technology, not a trunked one. However, the same multi-site IP-linking concept is reused by Motorola's trunked offerings — MOTOTRBO Linked Capacity Plus is described by Motorola as acting like IP Site Connect, but across Capacity Plus trunked sites rather than conventional ones.

Scope vs. Capacity Plus / Linked Capacity Plus

IP Site Connect and Linked Capacity Plus rely on the same underlying idea — link multiple repeater sites together over IP so they behave as one system — but they apply it to fundamentally different channel models. IP Site Connect links conventional repeaters, where every linked site relays the same fixed logical channel on its own local frequency pair; there is no dynamic channel pooling, so its "capacity" per channel is essentially that of a single conventional repeater channel, just extended geographically across up to 15 sites. Linked Capacity Plus instead links trunked Capacity Plus sites, where each site (and the network as a whole) dynamically pools channels across talkgroups rather than relaying one fixed channel — meaning Linked Capacity Plus supports substantially more simultaneous users and talkgroups per site than IP Site Connect can on the same repeater count, at the cost of the greater configuration complexity that trunking entails. In short: IP Site Connect is about extending simple conventional coverage across sites, while Linked Capacity Plus (and, at larger scale, Capacity Max) is about extending trunked capacity and efficiency across sites.

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.