This is the whole system at once: a core, three sites, a fleet in the field — and a crisis whose telemetry lies to you. Full signal bars while calls collapse. A healthy RF link while audio turns to hash. Your job is to read past the obvious reading, query the right subsystem, and fix the actual root cause. Two incidents. No hand-holding.
Incident behaviors modeled on verified LMR/ASTRO 25 principles (simulcast timing/ISI, KMF/OTAR key rollover). System Release 2024.1 baseline. Telemetry values are illustrative teaching signals, not a live system. The simulcast incident tests timing-in-overlap, not a "Phase 1 fallback" — that mechanism isn't real; radios lose the control channel and reaffiliate.
Master site · wide-area operationssystem: nominal
Select an incident to work
Signal (RSSI)
strong
Inbound BER
0.1%
Encryption
keys valid
Affiliations
stable
Telemetry checkpoints — query the subsystems
Remediation — commit the root-cause fix
Session
Metrics
Time to resolve—
Diagnostic precision—
System statusstandby
Master-site mindset
At the core, the trap is trusting the loudest reading. Full signal doesn't mean healthy — a simulcast timing slip garbles audio in overlap while RSSI stays pinned. A connected call doesn't mean intelligible — a missed key turns clean RF into hash. Query the subsystem the symptom implicates, not the one that's easiest to read.