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

Question on MCC7500 Consoles

Status
Not open for further replies.

RadioGuy3007

Member
Database Admin
Joined
Jan 27, 2013
Messages
316
I have a question related to the MCC7500 console. Our state is going live in some areas with a new 800mhz P2 P25 system. I am curious how patching works. Currently one of the local PDs is unencrypted on 800 but it's passing back through VHF with encryption and showing the dispatch console ID and when an officer keys up it continues to show the console ID. I am genuinely curious how this works. I would think if they are encrypted on one channel they should be encrypted on the talk group. This new system is supposed to utilize ÆS encryption with OTAR. Since the system is still being built is it possible the encryption is not built out or ready?
 

TJX400

Member
Joined
Apr 26, 2020
Messages
313
Probably being overlooked. Patching between two talkgroups on one system just tunes radios on either talkgroup to the same frequency. Patching two systems together essentially just opens the air when audio is heard, like VOX. I'd imagine they will fix it as the system continues being built out. In this case it seems like the VHF side is a different "system", so when it's patched to the 800, the console is just repeating the audio under it's own ID.
 

jeepsandradios

Member
Feed Provider
Joined
Jul 29, 2012
Messages
2,336
Location
East of the Mississippi
All depends on how the system is configured. If they want secure on P25 they can. I have multiple patches with clear/encrypted in the mix for various reasons.
 

Ubbe

Member
Joined
Sep 8, 2006
Messages
9,890
Location
Stockholm, Sweden
it's passing back through VHF with encryption and showing the dispatch console ID and when an officer keys up it continues to show the console ID.
Are you sure it's the console id and not the patch id? When patching between two systems it's usually done using analog audio with VOX or EM signaling but no user ID are passed over the link. Only the mechanical patch id and the TG it is linked to will be known. Any encryption can be added by the base station at either end.

If it is the console ID then you are listening to the system that has the dispatcher and the mobile are transmitting from the other patched system, not able to show it's own user id and the console id will still be shown.

/Ubbe
 

GTR8000

NY/NJ Database Guy
Database Admin
Joined
Oct 4, 2007
Messages
16,168
Location
BEE00
Are you sure it's the console id and not the patch id? When patching between two systems it's usually done using analog audio with VOX or EM signaling but no user ID are passed over the link. Only the mechanical patch id and the TG it is linked to will be known. Any encryption can be added by the base station at either end.

If it is the console ID then you are listening to the system that has the dispatcher and the mobile are transmitting from the other patched system, not able to show it's own user id and the console id will still be shown.

/Ubbe
Patching has come a long way since what you've describing. Modern systems, especially when patching P25 resources (conventional or trunked) together via an ISSI link or system consoles, is normally IP/digital end-to-end, not "analog with VOX". The IDs of the subscribers on either end of the patch are normally passed through that link/patch.
 
Status
Not open for further replies.
Top