Check the association among the radio ID, the displayed alias and the location report before treating a surprising map position as the radio's current location. An alias problem, duplicate field-radio ID or old location report can produce a misleading display.
- Check the timestamp. Identify the last received report and which radio ID it belongs to. A stale position is different from a fresh but unexpected report.
- Compare the radio inventory and programming. Distinct field radios should use the intended unique IDs. A copied codeplug can accidentally assign one ID to two units.
- Review Contacts/aliases. Confirm the ID, contact type, displayed name and any fixed Gateway assignment. Check whether Dispatch PCs have different copies of an alias table.
- Check the data path. Verify subscriber GPS destinations, the voice/data-revert arrangement and the correct Gateway, using the relevant installation guide.
- Test one known radio. At a known outdoor position, request a supported location update and compare the ID and timestamp with the displayed result.
Do not indiscriminately change all duplicate IDs. A voice control station and its associated data-revert radio can intentionally share an ID according to the CTI guide. That pairing is different from two unrelated subscriber radios accidentally sharing an ID.
If the mismatch remains, supply CTI with the affected IDs, aliases, timestamps, software/radio versions and the test result. Avoid sending unrelated personal location history.