Before this:Anatomy of a trunked call: request, grant, release
Control-channel signaling: what the data says
Key takeaways The control channel is a constant stream of short, typed data messages. Grants and grant updates announce calls and their voice channels; registration/affiliation messages track which radios and talkgroups are active; system status and network status describe the system; adjacent-site broadcasts list neighbor control channels; and crucially, identifier/frequency-band updates carry the formula that turns a channel number into a real frequency. In P25 these ride in TSBKs; in DMR, in CSBKs. A trunk-tracker assembles all of this into a live channel map.
You’ve watched a single call flow through the control channel. Now we catalogue the full vocabulary — the message types that, taken together, let a decoder reconstruct the entire system. This is the most data-dense part of trunking, and it’s where a “trunk-tracker” earns its name.
The carrier: TSBK and CSBK
Control-channel messages aren’t free-form; each is a short, structured block with a type field. Two concrete carriers dominate the digital world:
- P25 packs its signaling into TSBKs — Trunking Signaling Blocks. Each TSBK is a fixed-size block whose opcode says what kind of message it is.
- DMR Tier III uses CSBKs — Control Signaling Blocks — the analogous unit on the DMR control channel.
The idea is the same in both: a stream of small, typed packets. A decoder reads the type, then parses the fields that type defines. Everything below is just which types matter and what they tell you.
The message families
| Message family | What it carries | Why a tracker needs it |
|---|---|---|
| Group voice channel grant | Talkgroup + assigned voice channel + source radio ID | The cue to tune a receiver to a new call |
| Grant update | Re-announcement of an active call’s channel | Late entry; staying locked to ongoing calls |
| Unit/group registration & affiliation | A radio registering or declaring its talkgroup | Live roster of active radios and groups |
| System service / status | System capabilities and operating parameters | Confirms identity and features of the system |
| Adjacent (neighbor) site broadcast | Control-channel frequencies of nearby sites | Following roaming; finding a stronger site |
| Identifier / frequency-band update | Base frequency, spacing — the channel-number formula | Converting channel numbers into real frequencies |
| Network status | Network/system identifiers (e.g. system ID, WACN) | Pinning down exactly which system this is |
Each family answers a different question. The grants say where calls are happening. The registration and affiliation messages say who is on the system. The status and network messages say what system this is. The neighbor broadcasts say what’s around it. And the identifier updates — easy to overlook — are what make the grants usable at all.
From channel number to frequency
Here’s the subtlety that trips up newcomers: a grant doesn’t contain a frequency. It says “go to channel 3,” where channel 3 is an abstract number. To turn that number into a real frequency you tune, the decoder needs the identifier / frequency-band update messages (P25 calls these IDEN updates). These carry a base frequency, a channel spacing, and related parameters — effectively a formula:
frequency = base + (channel number × spacing) ± offset
Until a tracker has collected the relevant identifier update, a grant for “channel 3” is meaningless — there’s no way to know which frequency channel 3 is. This is why a freshly locked control channel sometimes takes a moment before calls become followable: the tracker is waiting to hear the identifier updates that complete its map.
Assembling the live channel map
Put the families together and a trunk-tracker maintains a continuously updated model of the whole system:
This map is what GopherTrunk’s CC Activity panel exposes: the raw, typed messages decoded in real time. Watching them is the clearest way to understand a system — and to spot, for example, that you’ve locked a control channel but haven’t yet seen the identifier update you need.
Quick check: a grant says "go to channel 3." Which message tells you what frequency channel 3 is?
Recap
- Control-channel signaling is a stream of short, typed blocks — TSBK (P25), CSBK (DMR).
- Grants and grant updates announce calls; affiliation/registration track active radios.
- System/network status identify the system; adjacent-site broadcasts list neighbor control channels.
- Identifier/frequency-band updates carry the formula that turns channel numbers into frequencies.
- A trunk-tracker fuses these into a live channel map — exactly what CC Activity shows.
Next, we step back and compare the trunking flavors — dedicated vs. distributed control, and message vs. transmission trunking.
Frequently asked questions
What kinds of messages are on a trunking control channel?
A control channel carries channel grants and grant updates for calls, registration and affiliation messages from radios, system service and status broadcasts, adjacent-site (neighbor) announcements, identifier or frequency-band updates that map channel numbers to real frequencies, and network status. Together these let a decoder build a complete live picture of the system.
How does a channel number become an actual frequency?
Grants reference a channel number, not a frequency. Identifier or frequency-band update messages provide the formula — a base frequency, channel spacing, and other parameters — that converts a channel number into a real transmit frequency. A trunk-tracker must collect these before it can tune to a granted voice channel.
What are TSBK and CSBK?
TSBK (Trunking Signaling Block) is the message unit P25 uses to carry control-channel signaling on its dedicated control channel. CSBK (Control Signaling Block) is the equivalent in DMR. Both are short, structured data blocks whose type field says whether they carry a grant, an affiliation, a status broadcast, and so on.
Why does a trunk-tracker need neighbor-site messages?
Adjacent-site broadcasts list the control-channel frequencies of neighboring sites in a multi-site system. A tracker uses them to know where a radio might roam and which other control channels exist, which is useful both for following roaming users and for finding a stronger site to monitor.