Someone needs to use something like DSD Plus or Unitrunker to verify encryption. Relying on a device like a scanner isn't very reliable, they decode terrible so it's hard to say if its encryption, or a bad decode.
Someone needs to use something like DSD Plus or Unitrunker to verify encryption. Relying on a device like a scanner isn't very reliable, they decode terrible so it's hard to say if its encryption, or a bad decode.
Somebody has, see Post #15.
of course I will lose my membership here.
I have terminated the OFS scanner feed. It's no longer readable.
And of course I will lose my membership here.
FWIW, thank you for putting in the time to provide it.
For what it's worth, I don't think its ENC. I've been fighting the same symptoms for a while now. I'm only hearing it when using my Whistler scanner. My HomePatrol works perfectly.ENC is now across several (possibly all) TGs. Dispatchers in the clear, district chiefs also clear
mostly (for now). Apparatus responding/on-scene largely ENC now, seems to be in and out.For
Suggest scanner users (temporarily) disable muting on ENC voice and have a listen, to get
a better idea what's happening. Not sure what the next step is.
Found at 5am sunday morning a lot of ENC activity on TG 12; radio techs keying/re-keying radios maybe?
Dave
For what it's worth, I don't think its ENC. I've been fighting the same symptoms for a while now. I'm only hearing it when using my Whistler scanner. My HomePatrol works perfectly.
I just reformated the SD card that I use in my Whistler and Ottawa Fire is now working perfectly. Odd but true.
I hope this helps.
Unitrunker reports encrypted comms as P, P1, P2, etc. in the service column.
The P stands for encrypted. Graphic attached.
Just noticed this, the plot thickens. Is UniTrunker also responding badly to (possible) simulcast?Unitrunker reports encrypted comms as P, P1, P2, etc. in the service column.
The P stands for encrypted. Graphic attached.
Does nobody up there use DSD+? That'll tell you toot-suite if it's encrypted or not, and what algo is in use. Problem solved! Well, not solved I guess but answered at least....
If it is a simulcast thing it's odd that it only happened now. My 996P2 and T before that were fine up until last weekend when this was reported.
I've deleted OFS out of my scanners, so I can't contribute further.