Radio IDs and Digital Addressing
Digital two-way radio standards give every radio a numeric identity and address calls to numeric group and individual IDs. This is what enables features analog radio never had natively: private (individual) calls, caller identification at the console, selective emergency alarms, and system-level access control. This page covers how DMR, NXDN, and P25 handle addressing, why unique IDs matter, and how fleets plan their ID space.
DMR Addressing
DMR (Digital Mobile Radio — see DMR Digital Mobile Radio) gives each radio an individual radio ID and addresses group calls to talkgroup IDs. Both live in a 24-bit address space — over 16 million possible values — which is far more than any private system needs; the size exists so large networks and shared infrastructures never run out. In a MOTOTRBO system, the radio ID identifies the unit for private calls, radio check, remote monitor, and emergency signaling, while the talkgroup ID determines which group of listeners unmutes (see Talkgroups and Fleet Mapping).
NXDN Addressing
NXDN (the standard behind Kenwood NEXEDGE — see NXDN Digital Standard) uses unit IDs for individual radios and group IDs for talkgroups, in a smaller address space than DMR's (a 16-bit-scale space, on the order of 65,000 IDs). The concepts are identical: unit ID for individual calls and identification, group ID for shared conversations, both programmed into the codeplug and required to match the system's plan.
P25 Addressing
P25 (Project 25 — see P25 Project 25) has the richest hierarchy because it is designed for nationwide, multi-system interoperability. A P25 identity has several layers:
| Identifier | Width | How you normally see it in the field |
|---|---|---|
| WACN (Wide Area Communications Network ID) | 20 bits | 5 hexadecimal digits — the top-level network, assigned so networks are globally distinguishable |
| System ID | 12 bits | 3 hexadecimal digits — a specific system within a WACN |
| Unit ID | 24 bits | the individual radio within the system |
| Talkgroup ID | 16 bits | 4 hexadecimal digits, usually written in decimal |
Together, WACN + System ID + Unit ID uniquely identify a radio anywhere, which is what makes inter-system roaming over ISSI (the Inter-RF Subsystem Interface) workable — a visiting radio's full identity says exactly which home network and system it belongs to.
Why Unique IDs Matter
Every radio on a system must have a unique individual ID. Two radios sharing an ID cause problems that are maddening to diagnose because they are intermittent and depend on which unit is in range:
- Private calls and radio checks reach the "wrong" radio, or apparently random ones.
- The console shows the same identity for two different field users, so dispatch cannot tell who is transmitting or who declared an emergency.
- On trunked systems, registration/affiliation conflicts can cause one unit to be deregistered when its twin registers, producing mysterious "radio stopped receiving" complaints.
- Selective features (stun/revive, remote monitor) hit both radios or the wrong one.
Duplicate IDs typically enter a fleet through cloned codeplugs that were never individualized (see Radio Cloning / Clone Programming for how and why this happens) — a strong argument for treating ID assignment as a managed record, not an afterthought.
Alias Tables
Raw IDs are just numbers; humans need names. Dispatch consoles and system management software maintain alias tables mapping IDs to display names ("Engine 3", "Unit 214", "J. Smith"). When a radio transmits, the console looks up the incoming ID and shows the alias. Two support implications follow: an alias table that is out of date shows wrong or missing names even though the radio system itself is healthy, and alias tables live in the console/dispatch layer — reprogramming the radio does not update them, and vice versa. See Two-Way Radio Dispatch and CAD.
ID Planning for Fleets
Well-run fleets plan their ID space the way network administrators plan IP addresses:
- Block by department or function — e.g., one numeric range per department, so an ID's leading digits tell you roughly whose radio it is.
- Embed structure sparingly — a little meaning in the digits (department, unit number) helps; overloading every digit with meaning collapses when the organization changes.
- Reserve growth ranges — leave gaps between department blocks for expansion.
- Keep one authoritative document — a master ID roster (radio serial number, ID, alias, assigned user/vehicle) maintained alongside the fleetmap, updated every time a radio is added, replaced, or reprogrammed.
The same planning discipline applies across DMR, NXDN, and P25; only the numeric ranges differ.
Related Pages
References
- What Every Communications Manager Should Know about P25 Roaming — RR Media Group — why WACN + System ID + Unit ID together make inter-system roaming work.
P25 WACN (20-bit), System ID (12-bit), and Talkgroup ID (16-bit) widths verified August 2026 via their published hexadecimal digit counts. Not independently confirmed in these sources: the 24-bit P25 Unit ID and the NXDN "16-bit-scale" figure — both are consistent with the standards as generally documented, but if either drives a decision, confirm against the TIA-102 documents or the Kenwood/NXDN specification directly.
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.