Calls Feature Request - Search by Source ID

Status
Not open for further replies.

TheAlmightyZach

Member
Feed Provider
Joined
Oct 19, 2018
Messages
65
Reaction score
18
Location
Raleigh, NC
I love the ability to pull archives from talk group ID, it's a great feature. One thing I'd love to be able to do is pull archives based on radio source ID (maybe in parity with talk group as well?). For example, the fire departments near me each have their own Radio ID for their robo dispatch. While that radio ID sits on a certain talk group, it would be nice to see just the dispatcher robot's calls when I'm searching for a specific tone out.

From what I can tell, it looks like the only functionality of source right now is showing what talk group it was seen on.
 

HarryWilly

Member
Joined
Jul 4, 2007
Messages
272
Reaction score
20
I agree with the idea, sort of looks like it would be easy-ish to implement since you can click on an RID and see where it's activity was. The one problem with your idea has to do with some of the software and the way trunking systems work. Lindsay flagged in the Trunk Recorder repository that some calls were basically "run ons" where if the person responding keyed up, Trunk Recorder could not separate the initial call and the response - basically there needs to be enough "hang time" between calls so the software picks up a new transmission and treats it as a separate call. I know for the automated voice dispatches on a fixed TG that would be easier since most folks aren't having a conversation with a robot that can't hear you, but the problem would not be the platform, rather the capture software.
 

TheAlmightyZach

Member
Feed Provider
Joined
Oct 19, 2018
Messages
65
Reaction score
18
Location
Raleigh, NC
Lindsay flagged in the Trunk Recorder repository that some calls were basically "run ons" where if the person responding keyed up, Trunk Recorder could not separate the initial call and the response

I had noticed this issue on other sites as well.. thankfully my site uses SDRTrunk, so not a problem here, but of course it’s not just about me.. still, I think there’s be a benefit here. I’ve setup my SDRTrunk to record all dispatches front hose UID’s, and then Linux deletes them after 24 hours with a simple script. It works well, but I don’t have a great way to access them remotely.

Plus, my 24 hour rule is really only because I don’t have a ton of space available on the VM, where calls saves for 30 days. Obviously there are solutions to this, but still, could be nice.
 
Status
Not open for further replies.
Top