Page 1 of 1

APX Trunking System Affiliation Data

Posted: Thu Dec 12, 2019 7:16 pm
by Adealia
I was looking through the APX CPS and learning a lot more about how trunking systems work. The question I have is in regards to what is shared to a trunking system controller. So far I am aware that the WACN and System ID are needed (which requires a valid system key) to be on the system. Then the "Unit ID" is what defines that particular radio on the system, is there any other parameters (serial number, alias, etc) that are shared/viewed by a trunked system?

Re: APX Trunking System Affiliation Data

Posted: Fri Dec 13, 2019 1:29 pm
by Karl NVW
An internally programmed unique ID field might also be shared, in order to provide positive verification that the sending radio is indeed authorized on the system and carries the other detected unit ID. Different network security management products may do that in different ways.

Re: APX Trunking System Affiliation Data

Posted: Sat Dec 14, 2019 1:13 am
by Adealia
Thanks for the reply Karl, is this unique ID field mentioned the same as a Unit ID or it something separate? It seems to me that a system would be easily compromised by unprotected (non-password protected) CPS cloning or even scanning for that specific unit ID.

I would suspect something to being used in addition to the unit ID, such as the ESN which would be specific and hardcoded to that particular subscriber unit. Is that the case?

Re: APX Trunking System Affiliation Data

Posted: Sun Dec 15, 2019 8:25 pm
by Karl NVW
As a recent ex-Mo, I can't answer your questions or discuss details of specific security methods that might be usable. I will only say that your general security analysis is reasonably accurate.

Re: APX Trunking System Affiliation Data

Posted: Tue Dec 17, 2019 12:06 am
by Adealia
Thanks again Karl. My assumption also is that it's system dependent based on capabilities of that system. No reply needed unless you have more insight that is safe to share and relevant.