sdrtrunk: Alias Identifier Overlap - Multiple P25 conventional systems

[MaineGuy]

I'm using sdrtrunk to monitor my four local P25 police and fire systems, and a NBFM channel for the EMS service.

It all works great - listening, logging, recording.

Except: I can't get the aliases to work right.

I have to set up alias identifiers to make recording work. It's also makes the display a little nicer.

The NBFM channel is fine with the identifier set at 1. It looks and works great!

Each of the P25 systems uses some talkgroup ID's that are the same the others.

Everyone likes using '1' for dispatch, and 65535 for 'All call'.

If I set the talkgroup ranges for all of the P25 systems to 0 - 65535, I get the overlap error. It works well enough to make recording work, but the display just uses the alias from whatever it loaded first, it seems.

All the P25 systems display the same thing. Police, fire, sheriff - all labeled 'Police' in the display.

Do any of you know how to work around this? It's the last piece of the puzzle - at least for today....

 

[Enforcer52]

What P25 systems are you monitoring, so we can look at the TGID structure.

Are you importing the TGIDs to an alias list or just setting one alias list entry as 0-65535?

 

[MaineGuy]

In the RR database: Maine - Kennebec - County Systems - Kennebec - Kennebec County - Augusta.

Augusta Police and fire have the same NAC. Capital police have their own NAC, but they are almost never on, so I don't know if they display correctly. All on different frequencies.

The db doesn't have TGID info for those like it does for MSCommNet, for instance.

 

[rhughes6]

If I’m following correctly, it sounds like you are only using one alias list? If so, try creating a different one for each system you are trying to monitor. Those look like they’re P25 conventional, so if all users on that frequency are the same then you could create an alias list like police with 1-65535 and assigning it to the police frequency in the channels tab.

 

[MaineGuy]

Thanks to Enforcer52 for helping me out - The problem is solved.
rhughes6 also saw the problem - using one alias list.
I was trying to figure out what to do using the pictures in the documentation for sdrtrunk.
It wasn't obvious what was happening there.

Multiple aliases in an alias list seem to be more useful for trunked systems where the talkgroup IDs have known assignments.
For my conventional systems, they don't have any talkgroup IDs in the RR database. I suspect they aren't using that, or use the same one for all.

I think I can use radio IDs for these systems - at least for the dispatcher ( 0 ) and 'all call' ( 65535 )