- Joined
- Mar 27, 2004
- Messages
- 383
- Reaction score
- 31
Well looks like I am SOL on both my pagers. Hardware in one is Basic(built in Bluetooth) and the other is SAW filter.
not anymore!In the Unication Programming software 'Create New Profile' page it tells you what Hardware your device uses - Version B is 'G5N'
As above V2.04 is only compatible with Version B at present
View attachment 196138
AES 256 did work with FW V2.04 on Version B Hardware
So AES 256 does or does not work on P25 Phase II with FW V2.04 on Version B hardware?In the Unication Programming software 'Create New Profile' page it tells you what Hardware your device uses - Version B is 'G5N'
As above V2.04 is only compatible with Version B at present
View attachment 196138
AES 256 did work with FW V2.04 on Version B Hardware
It did work when tested late last year.So AES 256 does or does not work on P25 Phase II with FW V2.04 on Version B hardware?
Is this on the TasGRN?It did work when tested late last year.
P25 Trunked Phase II system, tested with multiple keys.
YesIs this on the TasGRN?
Interesting in a very bad way.We tested trying to get the pagers to reliably decode ADP on a Motorola Phase 2 system for about six months and finally after many back and forth attempts Unication gave up and said we needed a higher signal strength. It is clear about 70% of the time and the rest is garbled. Unication support suggested we only use our pagers outside. This is a system of over 250 pagers in an active volunteer firefighter service. For what it's worth the signal strength indicator on the screen is NOT an accurate representation of the actual signal strength you are receiving. Our radios.do not have AES capability so we never made it that far in test.
I am sitting in a system where it didn't work...at all on P25 phase 2. The software fix seems to be hit or miss.It did work when tested late last year.
P25 Trunked Phase II system, tested with multiple keys.
Looks like 2.04 might work on older pagers now according to estone4009Ok and I have ADP encryption working on an older model with SAW filter hardware. I am trying to get AES 256 to work however it appears I need a pager with the newer G5N hardware and v2.04 fw.
Are you absolutely sure that both the CKR ID and Key ID are correct for your system? I know in mine the Key ID was not consistent with the CKR IDNo luck, I have upgraded to Firmware v2.04-T02B and before I upgraded, when I did a ptt, the pager showed the encrypted tg but no audio. Now it does not even show the tg on the pager. Also, shows missing key(which I have loaded).
And confirming you used the Unication Encryption Key Utility to load the key into the device(s) following the appropriate steps for doing so?I have checked and my Key ID was entered incorrectly. I changed it and also confirmed the CKR ID was correct. Still no audio.