Add P25 neighbor site logging - #1162
Open
penguinzephyr wants to merge 3 commits into
Open
penguinzephyr wants to merge 3 commits into
penguinzephyr wants to merge 3 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
P25 adjacent-status messages include neighboring site IDs and control-channel information, but Trunk Recorder was only logging them at debug level.
This change records neighbors from TSBK and MBT messages and includes them in the periodic control-channel status output. Neighbor frequencies come from the radio messages. An optional knownSitesFile adds site names using a CSV with RFSS,SITEID,NAME columns. Unknown sites are highlighted in yellow when console colors are enabled, and are still listed when no lookup file is configured.
I have run this in my own environment and it appears to be working successfully.