Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Demote conventional "Group Mismatch" errors #871

Merged
merged 1 commit into from
Nov 22, 2023

Conversation

taclane
Copy link
Contributor

@taclane taclane commented Nov 16, 2023

Using a channelFile allows users to assign arbitrary talkgroup numbers to conventional frequencies for ease of management and add identifying metadata to these calls.

While it is helpful in a trunked environment that Trunk Recorder can decode talkgroup data from digital voice channels to identify group mismatches, conventional p25 systems are often set as the default TG 1. Any conventional p25 frequency not assigned TG 1 in the channel file is likely to spam the console logs for the duration of the call.

Group Mismatch - Recorder Received TG: 1 Recorder state: recording incoming samples: 1440
Group Mismatch - Recorder Received TG: 1 Recorder state: recording incoming samples: 1440
Group Mismatch - Recorder Received TG: 1 Recorder state: recording incoming samples: 1440
Group Mismatch - Recorder Received TG: 1 Recorder state: idle incoming samples: 1440
Group Mismatch - Recorder Received TG: 1 Recorder state: recording incoming samples: 1440
Group Mismatch - Recorder Received TG: 1 Recorder state: recording incoming samples: 1440
Group Mismatch - Recorder Received TG: 1 Recorder state: recording incoming samples: 1440
Group Mismatch - Recorder Received TG: 1 Recorder state: recording incoming samples: 1440
Group Mismatch - Recorder Received TG: 1 Recorder state: recording incoming samples: 1440
Group Mismatch - Recorder Received TG: 1 Recorder state: recording incoming samples: 1440
...

While it may be helpful in the future to capture and use the "Received TG" for conventional p25, there is presently no practical solution for a conventional system where multiple channels may all report the same talkgroup.

The line changed is only shown for conventional systems, and should be set to the debug level for now.

@robotastic
Copy link
Owner

Good call - that got annoying

@robotastic robotastic merged commit 25d0fa0 into robotastic:master Nov 22, 2023
1 check passed
@taclane taclane deleted the conv-mismatch branch December 13, 2023 04:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants