Unitrunker and User ID's

[jetskiman98]

I've searched for an answer with no luck, so please excuse me if this has already been discussed. I've been running Unitrunker on my local P25 system for some time and have noticed an issue with decoding unit IDs. While my 396XT will show the ID of the dispatch console being used, Unitrunker displays a '0'. The dispatch center has consoles ID'd 5001 thru 5005 but each one shows as '0' in the software. All other ID's show up fine. Could this be a bug, or a setting that I can tweak?

 

[SCPD]

The program only looks at the control channel, not the voice channel.

With that in mind, what you describe could be:

a. a bug
b. the call grant message has a zero as the source ID.

P25 voice channels may provide the unit ID of the party talking which is likely what you see on your 396XT.

Turn on decode logging and examine the call grant messages to verify whether it's (a) or (b).

http://www.unitrunker.com/logging.html

 

[jetskiman98]

Is there a guide out there to help me learn how to read the raw data? I've found the files, but cannot decipher the decode log.

Here is a sample conversation:
20140620133654,257,Call,I,1704,G,15,570, 4
20140620133656,257,Call, ,0,G,15,570, -
20140620133658,257,Call,I,1404,G,15,570, 4
20140620133709,257,Call, ,0,G,15,660, -

Here is the decode log for the transmission in question:

2014-06-20 13:36:56 26 of 40 (65%)

-B4 00 05 83 C0 64 05 F7 40 90 5A B8 Identifier Update 0 Base 500450000 Spacing 12500 Tx Offset 3000000
-B4 00 15 83 C0 64 05 F5 E1 00 A4 9A Identifier Update 1 Base 500000000 Spacing 12500 Tx Offset 3000000
-BB 00 00 92 6B 95 82 00 00 70 66 15 Network Status Broadcast Mfg 00 LRA 00 WACN 926B9 Sys 582 channel 0-000(500.45000)(data,voice,registration)
-BA 00 00 35 82 01 01 00 00 70 FF A9 RFSS Status Broadcast Mfg 00 LRA 00 Sys 582 Sub 01 Site 01 channel 0-000(500.45000) (data,voice,registration)
-B8 00 00 2C 2E 7F 2C 2E 7F 01 E0 AF System Service Broadcast Available 2C2E7F Supported 2C2E7F
-B4 00 05 83 C0 64 05 F7 40 90 5A B8 Identifier Update 0 Base 500450000 Spacing 12500 Tx Offset 3000000
-B4 00 15 83 C0 64 05 F5 E1 00 A4 9A Identifier Update 1 Base 500000000 Spacing 12500 Tx Offset 3000000
-BB 00 00 92 6B 95 82 00 00 70 66 15 Network Status Broadcast Mfg 00 LRA 00 WACN 926B9 Sys 582 channel 0-000(500.45000)(data,voice,registration)
-BA 00 00 35 82 01 01 00 00 70 FF A9 RFSS Status Broadcast Mfg 00 LRA 00 Sys 582 Sub 01 Site 01 channel 0-000(500.45000) (data,voice,registration)
-B8 00 00 2C 2E 7F 2C 2E 7F 01 E0 AF System Service Broadcast Available 2C2E7F Supported 2C2E7F
-B4 00 05 83 C0 64 05 F7 40 90 5A B8 Identifier Update 0 Base 500450000 Spacing 12500 Tx Offset 3000000
-B4 00 15 83 C0 64 05 F5 E1 00 A4 9A Identifier Update 1 Base 500000000 Spacing 12500 Tx Offset 3000000
-BB 00 00 92 6B 95 82 00 00 70 66 15 Network Status Broadcast Mfg 00 LRA 00 WACN 926B9 Sys 582 channel 0-000(500.45000)(data,voice,registration)
-BA 00 00 35 82 01 01 00 00 70 FF A9 RFSS Status Broadcast Mfg 00 LRA 00 Sys 582 Sub 01 Site 01 channel 0-000(500.45000) (data,voice,registration)
-B8 00 00 2C 2E 7F 2C 2E 7F 01 E0 AF System Service Broadcast Available 2C2E7F Supported 2C2E7F
-B4 00 05 83 C0 64 05 F7 40 90 5A B8 Identifier Update 0 Base 500450000 Spacing 12500 Tx Offset 3000000
-B4 00 15 83 C0 64 05 F5 E1 00 A4 9A Identifier Update 1 Base 500000000 Spacing 12500 Tx Offset 3000000
-BB 00 00 92 6B 95 82 00 00 70 66 15 Network Status Broadcast Mfg 00 LRA 00 WACN 926B9 Sys 582 channel 0-000(500.45000)(data,voice,registration)
-BA 00 00 35 82 01 01 00 00 70 FF A9 RFSS Status Broadcast Mfg 00 LRA 00 Sys 582 Sub 01 Site 01 channel 0-000(500.45000) (data,voice,registration)
-B8 00 00 2C 2E 7F 2C 2E 7F 01 E0 AF System Service Broadcast Available 2C2E7F Supported 2C2E7F
-B4 00 05 83 C0 64 05 F7 40 90 5A B8 Identifier Update 0 Base 500450000 Spacing 12500 Tx Offset 3000000
-B4 00 15 83 C0 64 05 F5 E1 00 A4 9A Identifier Update 1 Base 500000000 Spacing 12500 Tx Offset 3000000
-BB 00 00 92 6B 95 82 00 00 70 66 15 Network Status Broadcast Mfg 00 LRA 00 WACN 926B9 Sys 582 channel 0-000(500.45000)(data,voice,registration)
-BA 00 00 35 82 01 01 00 00 70 FF A9 RFSS Status Broadcast Mfg 00 LRA 00 Sys 582 Sub 01 Site 01 channel 0-000(500.45000) (data,voice,registration)
-B8 00 00 2C 2E 7F 2C 2E 7F 01 E0 AF System Service Broadcast Available 2C2E7F Supported 2C2E7F
-B4 00 05 83 C0 64 05 F7 40 90 5A B8 Identifier Update 0 Base 500450000 Spacing 12500 Tx Offset 3000000
-B4 00 15 83 C0 64 05 F5 E1 00 A4 9A Identifier Update 1 Base 500000000 Spacing 12500 Tx Offset 3000000

 

[PhillyPhoto]

I haven't done any debugging in UT, but looking at your output:

Here is a sample conversation:
20140620133654,257,Call,I,1704,G,15,570, 4
20140620133656,257,Call, ,0,G,15,570, -
20140620133658,257,Call,I,1404,G,15,570, 4
20140620133709,257,Call, ,0,G,15,660, -

1704 & 1404 might be the HEX values for the dispatchers. They are 5892 & 5124 in DEC. I would guess 15 is the HEX talkgroup they're talking on even though I don't see that in the DB (EMS maybe?).

The guide is here: UniTrunker Guide - UtahRadio

 

[jetskiman98]

1704 and 1404 are field units and the TG 15 is a know talkgroup on this system (South Response 1). Why the dispatcher always comes up zero is the mystery to me. In the event log it doesn't even look like there is a source type or call type given for those transmissions. The decode log is a whole different beast.

 

[SCPD]

Look for "Group Voice Grant" messages. These have the source radio ID and target group ID.

If you find "Group Voice Grant Update" messages, these follow the initial grant message and only carry the group ID, not the unit ID.

Beware the site logs use UTC time while the decode logs are local time.