Search results

Talkgroup 300, slot 1.

I wouldn't be surprised if they flog it for special events, like they did with their EDACS, then LTR offerings for Pride Week in the past. Given their track record (dead PA on EDACS channel 7 killing emergency comms with TEMS and a conventional analog security channel repeater drifting...

Looks like you're not installing the USB driver properly. Problems like this are usually caused by installing the USB driver for the wrong device. Unplug all dongles, then use Device Manager to delete them. Plug in a dongle and then do the following: Run Zadig. Under Options, make sure to...

I haven't seen mention of aliases in the P25 standard, but that doesn't mean much. What I've seen of Harris systems and OTA talker aliases is "talker alias header" messages followed by "talker alias text" messages; both message types use opcodes that are in the vendor-specific opcode ranges and...

I'd like to know how a scanner that doesn't decode, let's say, NXDN or DMR, is supposed to detect encrypted NXDN or DMR voice comms in order to mute them. And along with providing no citations, the troll doesn't explain in any way how ignoring/muting encrypted voice traffic serves any...

Another billion should get the job done!

Did they get the real stuff that actually costs money or the free toy version?

They write avionics firmware for Boeing from their toasty offices in Bangalore.

Using DSD+ with external signal sources DSD+ can be used with external signal sources such as a properly discriminator-tapped receiver or SDR software such as SDR#. To use DSD+ with these sources, use the menus in DSD+ to select Passive Digital Monitor mode and then to select the...

Pretty much. 40 bit is a joke when it comes to keyspace size, but that doesn't stop the "I found a backdoor!" pronouncements from some parties.

No. If it was, I'd use them. As it stands, I don't even bother to determine if they're present. Truly couldn't care less.

Meanwhile, silence frames aren't actually required when cracking 40 bit encryption, so it's not a dirty little secret.

DSD+ is configured to talk to one of the FMP programs via a direct link, but you're not running any of the FMP programs with direct linking enabled. In the Notes.txt file, look for Using DSD+ with supported SDR devices and Single-dongle monitoring:.

I think he's saying that you have to tune to the voice channels to get aliases, which of course is the case, since radio aliases are only sent on voice channels. Control channels ain't got no time for that jibber jabber!

I would email them.

Folks, sorry for the off-topic ranting going on here, but I feel y'all should be aware of the loons in our midst. As he's stated above, Louie7 sent me a very short sample of part of a DMR EP transmission. And as he's stated, it contained no known plaintext (silence frames). I extracted the full...

Meanwhile, you're the guy who's convinced that DMR EP leaks key bits in the datastream and that the government (which one?) is behind it and is covering it up. And that even your CCR implements it! Guess that means even Winnie the Pooh is in on it. So much for taking you seriously...

It's probably not supported. Wild guess here, but whatever was done to fix the 1A's issue needs to be applied to the dx as well. Try working with the DSD+ developers.

Oh, I agree. Adding all of that stuff is half the fun. I've seen plenty of screen shots here where folks are obviously trunking / hearing comms, but the event log window has no network name, no site name, no neighbor names, no talkgroup names, nada. They're missing out!

Not required for trunk tracking. Those files mainly just define the network and site aliases.