• 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.

APX P25 radio aliases

Status
Not open for further replies.

N0BDW

Member
Joined
Dec 1, 2010
Messages
488
Location
Livingston Co., NY
Howdy.

Is it possible to display P25 RIDs as an alias on the APX series radios? For example instead of RID "612504" to display I'd like to have it say "LFD 2504." I know our dispatch consoles already do this.

Also: is it possible for the system to transmit these aliases? So that if an alias needs to be changed it doesn't need to be updated in each piece of subscriber equipment?

Thanks.
 

Project25_MASTR

Millennial Graying OBT Guy
Joined
Jun 16, 2013
Messages
4,201
Location
Texas
I don't remember if enhanced ID has to be in the flash for the APX line but yes, ID's can be aliased.

Can the radios send the alias over the air...not in any current Astro25 releases.
 
Joined
Aug 9, 2016
Messages
80
Here's a copy/paste from one of my posts. This should help:

"1) As N1GTL explained, you must first go to Radio Ergonomics > Display, and scroll down to “ID Display”. Use the dropdown next to the “PTT ID DISPLAY”, and select “Dispatch and Scan”.
2) Going back to the “Codeplug Configuration” tree, scroll down to “Conventional Configuration”, and select the “Conventional System” menu.
3) Right-click on the “Conventional System” menu, and select “Add”.
4) Now select the system that was just created, and left-click on it to open it.
5) Under “Conventional System Name”, erase the generic name and call it whatever you want. For this exercise, I’ve called mine “FIRE”.
6) Directly beneath that, locate the “System Type”. Mine is defaulted to “Astro”.
7) Use the dropdown to select “MDC”.
8) Now, go back to the “Codeplug Configuration” tree, and select “Conventional Personality”.
9) Assuming you already have created personalities, click on a personality that you want to assign the MDC system to. In this exercise, I’ve created “SGFD”. If you haven’t yet created a personality, go ahead and create one that will have this MDC system assigned to it.
10) Once you’ve built out the personality (an exercise I won’t go into here), continue scrolling down beyond the frequency inputs and options, and find the “Signaling” sub-menu.
11) Within the “Non-Astro” menu area, locate the “Signaling Type” dropdown menu, and select “MDC”.
12) Directly beneath that, locate the “System Number”. Change that to the system you created in step 5.
13) Going back to the “Codeplug Configuration” tree, scroll down to “Call List Configuration”, and click on “Unified Call List”.
14) Across the top of the screen are symbols. Click the “+” symbol to add a new “Contact Name”. This will create a generic contact; something along the lines of “Contact 00126”, in my case.
15) Highlight the generic contact name, and call it whatever you want. In my case, I’m going to call this contact “Battalion 1”.
16) After you’ve named your contact, click the little arrow to the left of the contact, so that the contact is highlighted blue.
17) Looking back up at your symbols across the top of the screen (where the “+” symbol is), select the blue folder (to the right of the trashcan). This opens additional options.
18) You now have several ID options, as well as the option to rename your contact if you so wish. Technically, you could have skipped step 4, and simply renamed the contact here. I learned that it’s easier to name it first, so that you are ensured that you have the correct contact open in this screen. Keeping the generic name, and renaming it from here, caused me confusion as I entered hundreds of these ID’s.
19) The option you want is “MDC Conventional ID”.
20) Along the “MDC” ribbon, click the “+” symbol.
21) Select the “System Name” from the dropdown menu. (Created in step 5, and assigned in step 12).
22) Under “Primary ID”, enter the MDC ID number
23) At this point, you are done. Your radio will read the ID and, if the ID has been created as per these steps, your screen will display the alias as opposed to the number.

The steps here are the same for Astro ID’s. The differences are:
1) When you build your system in steps 5, 6, and 7, you’ll select “Astro” as the signaling type.
2) When you build your conventional personality in steps 10, 11, and 12, you’ll instead use the “Astro” signaling sub-menu, and change the “Astro System” to whatever you created in steps 5, 6, and 7 (reference 1 above).
3) Then, instead of creating a “MDC” ID in step 19, you’ll create an “Astro Conventional ID” by selecting the Astro system you just created, and changing the “Individual ID” to whatever the correct number is.
 

Outerdog

T¹ ÆS Ø
Premium Subscriber
Joined
Jul 1, 2016
Messages
641
The off-topic diatribe about MDC posted above is utterly useless. Aliasing in APX CPS is different than XTS/L aliasing anyway.

For APX CPS, on the main codeplug configuration tree, look at Call List Configuration. The idea is to create Contacts within a Unified Call List. You can assign different IDs to different system types. In your example, you would want to create an entry under Astro 25 Trunking ID associated with the trunking system in question.

It is possible for the system to OTA alias information to the fleet, but I don't work at that level and am unfamiliar with the configuration. Note that any changes made to aliases in CPS will overwrite any OTA alias information the radio may have previously received.

The APX CPS has additional information.
 

N0BDW

Member
Joined
Dec 1, 2010
Messages
488
Location
Livingston Co., NY
Thank you Outerdog. I'm going to pursue the OTA option with the county and see what they have to say about it. If they aren't open to the idea I'll look at doing it through CPS.
 
Joined
Aug 9, 2016
Messages
80
The off-topic diatribe about MDC posted above is utterly useless. Aliasing in APX CPS is different than XTS/L aliasing anyway.

For APX CPS, on the main codeplug configuration tree, look at Call List Configuration. The idea is to create Contacts within a Unified Call List. You can assign different IDs to different system types. In your example, you would want to create an entry under Astro 25 Trunking ID associated with the trunking system in question.

It is possible for the system to OTA alias information to the fleet, but I don't work at that level and am unfamiliar with the configuration. Note that any changes made to aliases in CPS will overwrite any OTA alias information the radio may have previously received.

The APX CPS has additional information.

Fighting with phonies is useless. Never mind. Thanks for the "CPS has additional help". That's very helpful!
 
Last edited:

N0BDW

Member
Joined
Dec 1, 2010
Messages
488
Location
Livingston Co., NY
Sounds like the county would like to do the OTA aliasing, but they need to install a service pack or somesuch. Hopefully that works out as it would save frequently having to reprogram radios (we don't have OTA programming).
 

ResQguy

Meh
Joined
Dec 19, 2002
Messages
1,319
Sounds like the county would like to do the OTA aliasing, but they need to install a service pack or somesuch. Hopefully that works out as it would save frequently having to reprogram radios (we don't have OTA programming).

The subscribers and the system both need to group services option enabled to do OTA aliasing. The system needs to be at release 7.17 or later to support this as well.
 
Status
Not open for further replies.
Top