KEYID not shown on encrypted P25 Trunked TGs, Fastlane 3.60, -v4

[Echo4Thirty]

I am monitoring a P25 P2 TRS via FastLane 3.60 and cannot see KEYID even with the -V4 switch. It shows as ENC GRP Call yadda but no algo or keyid. I am using an MCS2000, discriminator audio into a USB sound card. Decode rate is fine in both DSD and Legacy Unitrunker. What am I missing? I saw a thread on here about this issue, but did not see a resolution posted. The logfile.txt file is also empty, so i suspect this is an issue due to me being a neophyte with DSD.


Batch File: start DSDPlus.EXE -- -O NUL -v2 -i1L -o1 -g0 -u3 -f1 -rc -v4 >logfile.txt

 

[natedawg1604]

I believe the the KeyId is transmitted over voice channels as opposed to the CC. Frankly it would be easier to get 2 rtl dongles and use FMP24 in trunk tracking mode with DSD+.

However with your current setup, try monitoring 1 individual voice channel at a time, and the KeyId should eventually show up.

 

[Forts]

Yes... you need to be monitoring the voice channel. Also, I've noticed that if the KEYID=0... DSD+ won't show it in the event log. If you are just using 1 dongle enable Voice/Data Call Following & Follow Encrypted Voice Calls, then just hold on the encrypted talkgroup that you are interested in.

Since you are using discriminator audio you would have to program in the voice channels and try to tune to the active channel while it's in use. A bit of a pain when you can't see the control channel activity at the same time, but do-able.

 

[Echo4Thirty]

Yep. that was exactly it. Now to learn how to use an RTL with it and retire the MCS2000

 

[racingfan360]

noticed that if the KEYID=0... DSD+ won't show it in the event log.

Same thing will happen on a NXDN encrypted channel where the KEYID=0, it won't show in the event log.
From memory an EP encrypted DMR signal will always show a KEYID as it can never be zero (I'm sure someone will correct me if that's wrong).
A DMR BP encrypted signal wont show a KEYID, BP doesnt have a KEYID as such, as it can be 1-255 possible preset keys.

 

[natedawg1604]

Yep. that was exactly it. Now to learn how to use an RTL with it and retire the MCS2000

You will be very impressed with the RTL dongles; when you use FMP24 with a TCP link, you can trunk track P-25, NXDN and DMR, and run numerous instances of DSD+ at once (as many as you want!). There will be a bit of a learning curve but it's totally worth it.

 

[slicerwizard]

The logfile.txt file is also empty, so i suspect this is an issue due to me being a neophyte with DSD.

Batch File: start DSDPlus.EXE -- -O NUL -v2 -i1L -o1 -g0 -u3 -f1 -rc -v4 >logfile.txt

Lose the start

when you use FMP24 with a TCP link

Direct link. These days, TCP linking is for remote monitoring.

 

[natedawg1604]

Direct link. These days, TCP linking is for remote monitoring.
[/QUOTE]
Ohhh I see that now in the documentation; What protocol does direct link use? I've been using it for several years, I always thought it was TCP.

 

[jets1961]

; protocols:
;
; ProVoice
; dPMR
; IDAS
; NEXEDGE48
; NEXEDGE96
; DMR
; TIII
; DCDM
; Cap+
; Con+
; XPT
; P25
; X2-TDMA