Mechanism for Unknown Talkgroups

102 views
Skip to first unread message

chris g

unread,
Apr 23, 2026, 8:45:56 PMApr 23
to sdrtrunk
I am on my first few days of SDRTrunk and I really like this software. I made the jump from Unitrunker because of it not supporting Phase2 and that's 90% of the traffic around me. I have SDRTrunk working with TrunkingRecorder pretty well now with all the tags imported from RR. 

The only thing I can't find a great flow path for from this set up is capturing the talkgroups that are not yet identified in RR. From what I can tell, it is only recording and making folders for the talkgroups with aliases.

What I have been doing is when I see a TG pop up that does not have a tag, I create a TG alias and just call it 'TG # UKN'. TrunkingRecorder then creates a folder for it and starts capturing audio so I can begin to gather some context for the TG. I feel like recording the audio from the unknown talkgroups is pretty important for many people as this is a great way to learn what the unknown TGs have going on. 

Is there any current settings I have missed that allow the capture and recording of untagged TGs? If not, is there anything on the horizon for adding this?

Thanks!

Jim Kovalsky

unread,
Apr 23, 2026, 9:02:41 PMApr 23
to sdrtrunk

You can define an alias for TG ID from 0-65334 and set that to record.  It will catch everything that you don’t have defined somewhere else.

 

On the alias definition:

2026-04-23 20 58 42.jpg

Austin Hruskach

unread,
May 12, 2026, 3:05:15 PM (4 days ago) May 12
to sdrtrunk
When you make an alias for 0-65535, expect the program to stop responding for a few minutes, not sure why, but it happens to me. It may also happen if you add that "wildcard" alias to your recording selection.

Zach Rutledge

unread,
May 14, 2026, 1:02:17 AM (3 days ago) May 14
to sdrtrunk
A caveat that I experienced when doing an alias for 0-65535 is that it seems to have messed up the logging of certain talkgroups.  I am not totally sure, but it seems like it causes a clash with any entry that uses a talkgroup range instead of a single talkgroup entry.  I've got a few encrypted groups that I just lump all their TGs into one entry, and those talkgroups suddenly show up in the logs under the catcall 0-65535 entry instead of their proper names.  

I haven't had a chance yet to experiment and see if moving those groups to individual entries fixes the issue.  I don't really wanna do it because it's like 50 extra entries I'd have to create!

Reply all
Reply to author
Forward
0 new messages