A modern ASTRO 25 system is IP end to end. A call becomes packets at the base radio, gets marked and queued at the site gateway, crosses the backhaul, and is routed and voted at the core. Launch a packet and watch what each box does to it — then flood the link and see why the voice packet still gets through.
Component roles verified against Motorola G-series / ASTRO 25 network datasheets (System Release 2024.1 baseline: GTR 8000, GGM 8000, GCP 8000, GCM 8000, K/L/M cores). Illustrative packet timing for teaching; a specific system's engineering comes from licensed documentation. Teaches the model, not a real network's config.
Packet journey · field site → master corelink: nominal
Link bandwidth used
12 %
Packet latency
8 ms
Voice packet loss
0.0% (QoS)
Tap a node to inspect it
Each box does one job to the packet. Launch a packet, or tap a node to read its role.
Launch traffic
Legend
Voice — EF-marked, priority queue
Data — best-effort, yields to voice
Congestion — background flood
The point
The GGM 8000 gateway marks voice with DSCP EF and puts it in a priority queue, so when the site link is flooded, voice packets leapfrog the backed-up data. The result a tech should trust: under congestion, a file transfer slows and data queues, but voice packet loss stays at 0.0%. That's QoS doing its job — the same principle as the phone-vs-file lesson, now shown as a packet's physical route through real hardware.