Analyzing the various security issues and demonstrating the insecurity of P25 systems.Extend the !WireShark sniffer to allow sniffing of P25 message.Implement a decoder which takes P25 signals and produces a message stream.

Understand P25, the physical layer and the messages being passed over the air.In increasing order of difficulty these are: Project Tasks♯rom here we have a number of tasks that immediately suggest themselves. When I reprogrammed my XTS3000 ASTRO ID with my DMR ID and set the ‘OverrideUIDCheck’ parameter on the hotspot back to ‘0’, it all worked as expected, displaying my callsign as well.A short video that demonstrates OP25 transmitting audio from a PC's microphone input, then to a USRP being received by a GRE scanner is available on Youtube Youtube. The hotspot then works with P25, but the hotspot doesn’t display your callsign (obviously) on the Hotspot OLED or the pi-star Dashboard.

The workaround if you don’t have the ID’s matched is that you need to set ‘OverrideUIDCheck’ to ‘1’ on the hotspot. So the result is that it appears that the hotspot isn’t working, when actually it is. I would have thought that it would at least decode but report an error, but that’s not the case. The trap for the uninitiated is that there is no decode at all and no error reported if you have this mismatch. I had my ACMA License Number as the ASTRO ID programmed into my XTS3000 (as was recommended years ago – before hotspots were around) and that obviously didn’t match the DMR ID programmed into the hotspot. I could use the hotspot with DSTAR and DMR, but the hotspot would not decode P25.Īpparently you do need to program the transceiver’s ASTRO ID field with your DMR ID for the hotspot to decode P25 transmissions. I'm not sure how to debug this facet further? Is there some sort of tunable needed to adjust for P25 for a successful decode - perhaps some sort of audio strength adjustment?Īny hints or ideas would be appreciated.

I don't see anything in any log on the unit that there is a failed decode or anything remotely wrong when the P25 signal is present.

The same thing is experienced on three different systems (all with different RX radios). Whenever the P25 signal is received, the board indicator shows that the squelch is open but the 'P25' light to indicate successful P25 decode never lights up. The setup works perfectly for D-Star, DMR, and YSF. The board is running the latest MMDVM firmware available for the board (FW v20180723 per the Pi-Star dashboard). All three repeaters (full duplex) are running Pi-Star on a Raspberry Pi3 with a STM32-DVM 'Pi-Hat' board from. I'm working with a friend on a series of multi-mode digital repeaters and we're having an identical problem with all of them receiving/decoding P25. Hello, looking for some P25 help or wisdom.

Decrypt P25