-
To anyone looking to acquire commercial radio programming software:
Please do not make requests for copies of radio programming software which is sold (or was sold) by the manufacturer for any monetary value. All requests will be deleted and a forum infraction issued. Making a request such as this is attempting to engage in software piracy and this forum cannot be involved or associated with this activity. The same goes for any private transaction via Private Message. Even if you attempt to engage in this activity in PM's we will still enforce the forum rules. Your PM's are not private and the administration has the right to read them if there's a hint to criminal activity.
If you are having trouble legally obtaining software please state so. We do not want any hurt feelings when your vague post is mistaken for a free request. It is YOUR responsibility to properly word your request.
To obtain Motorola software see the Sticky in the Motorola forum.
The various other vendors often permit their dealers to sell the software online (i.e., Kenwood). Please use Google or some other search engine to find a dealer that sells the software. Typically each series or individual radio requires its own software package. Often the Kenwood software is less than $100 so don't be a cheapskate; just purchase it.
For M/A Com/Harris/GE, etc: there are two software packages that program all current and past radios. One package is for conventional programming and the other for trunked programming. The trunked package is in upwards of $2,500. The conventional package is more reasonable though is still several hundred dollars. The benefit is you do not need multiple versions for each radio (unlike Motorola).
This is a large and very visible forum. We cannot jeopardize the ability to provide the RadioReference services by allowing this activity to occur. Please respect this.
OTA Key ID Alias
- Thread starter KevinC
- Start date
The hex KID is sent in the HDU payload as I assume your familiar with. I am not aware of OTA aliasing of the KID to a alias. What is usually done is the matching KID in the secure configuration > secure wide > Encryption key name is set to the desired alias. This then displays the alias if the > multikey check boxes are set to "key name".
Reconrider
Inside the Galaxy
Alias OTA doesn't work on conventional p25
Someone needs to tell my 8K's that...
And I wasn't talking about OTS radio aliasing, I was talking about key ID alias.
I believe the answer is no. I don't think MSI wants to put the effort in to something that doesnt really accomplish a lot and after Harris' disastrous"suppress KID" functions, I think everyone is happy how KID is sent for unmute without any extraneous data
Reconrider
Inside the Galaxy
Can you cite this?
I was told it's not possible
Cite it? It works on my radios, is that enough for you?
Reconrider
Inside the Galaxy
That would work lol.
Must be the systems I have near me don't have aliases set
Interesting fact on the OTA radio (RID) alias. if its on a trunked system the alias data is encrypted. If its on a conventional freq its not encrypted The current DSD Fastlane decodes the OTA aliases. It also captures the OTA data packets. So far I have not captured a conventional OTA packet. I would like to get a few and analyze them. FYI for anyone interested the OTA data can bee seen in the DSD .radios file.
I agree the Harris suppressed KID was a disaster. Any interop went down the toilet so to speak. I also understand that multi key Harris systems Had issues.
I too cannot see Moto adding in any type of OTA Key alias. The end user does not need to have it or display the key. 99% of encrypted TG are strapped encrypted and to a specified key. Agencies that have user selectable keys will have all the keys in the secure configuration and they will be aliased in the codeplug. Again meaning that OTA key aliasing would be redundant anyway.
I agree the Harris suppressed KID was a disaster. Any interop went down the toilet so to speak. I also understand that multi key Harris systems Had issues.
I too cannot see Moto adding in any type of OTA Key alias. The end user does not need to have it or display the key. 99% of encrypted TG are strapped encrypted and to a specified key. Agencies that have user selectable keys will have all the keys in the secure configuration and they will be aliased in the codeplug. Again meaning that OTA key aliasing would be redundant anyway.
If they were encrypted, DSD+, SDRTrunk, and as of this afternoon Unitrunker 2.2 would not be able to decode them. APX subscribers without any encryption capability whatsoever are able to decode the OTA aliases with Group Services in the FLASHcode.
And all of the OTA subscriber alias talk is off topic, but I guess it's comforting to know that nothing around here will change in 2025 with regard to off topic posts, bad information being posted, etc.
Doubtful.
Similar threads
