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

Suggestion: Set Priority Channel for Duplicate Calls #1871

Open
JamesK455 opened this issue Mar 8, 2024 · 3 comments
Open

Suggestion: Set Priority Channel for Duplicate Calls #1871

JamesK455 opened this issue Mar 8, 2024 · 3 comments
Labels
feature Feature Request

Comments

@JamesK455
Copy link

Situation:
I am located within listening range of 4 P25 sites that are all part of one provincial system (not simulcast). As they're part of the provincial trunked system the same talkgroup is often active on more than one of the sites -- but not always. 2/4 of the control traffic channels are at the outer limit of my reception range so the audio isn't always as clear as the site that is a block away. I sometimes have recordings that are patchy/garbled due to weak decodes but when I watch the channel activity the same audio was available from the stronger site.

Describe the solution you'd like
It would be great if, in addition to the duplicate call detection that is currently working exactly as advertised, I could select priority channels.

Basically: if there is a duplicate call, prefer {channel} otherwise use whatever is available.

Describe alternatives you've considered
I considered separate alias lists per channel even though the talkgroups and radio IDs are shared throughout the system but this approach caused missed calls when the departments are all connected to a different site than the one I have set to record.

I also tried turning off the duplicate detection but this became difficult to manage due to the volume of calls I am streaming/recording.

Additional context
The program is awesome and I appreciate the work put into it! This is by no means a dealbreaker for me but would make monitoring slightly easier during high call volume events and mutual aid situations.

@JamesK455 JamesK455 added the feature Feature Request label Mar 8, 2024
@thisisfakediy
Copy link

I would love this feature as well.

@leoninelion
Copy link

Error counts per channel could be maintained in a table, events like SYNC LOSS, etc would count to a total "channel quality" score for the control channel. If assumed that every channel spawned by that control channel would have that same quality score, automatic channel quality voting could occur.

@ArrEssJay
Copy link

I would suggest tracking the short term moving average of voice frame bit-error-rates on a per-traffic-channel basis for each site, then feeding the decoder from the least erroneous source as the call progresses, noting that as the call may hop between traffic channels and observed channel error rate at the receiver can change abruptly, there could be a need to switch source mid-call.

For example, I have a receiver located such that co-channel interference is a problem. Some traffic/control channels are used by multiple sites with similar received signal strength. The likelihood of trunking/traffic being received from a given site is predominantly a function of site distance, time of day (system utilisation) and channel allocation/re-use between the sites.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Feature Request
Projects
None yet
Development

No branches or pull requests

4 participants