It has already been done. It wasn't hard. Acquire repeaters. Flash with Linked Capacity Plus. Install microwave backbone (way easier than it sounds, and not expensive -- just time and a few headaches). Connect sites. A few remote sites connect via Internet, but they're not as reliable due to UDP/packet loss when people are watching porn and Netflix at peak hours.W9BU said:Let's stick to the question. What are the technological and administrative hurdles that must be crossed to put a trunked system on the air in the amateur radio service? Is it possible? How would you go about it? If you aren't answering those questions, don't post. It's as simple as that.
In terms of a need, here goes: (point form)
- As stated multiple times, with timeslot-trunking, there's no timeslot-strapping, which ties up resources (voice channels, aka "rest channels" in Moto-speak) system-wide.
- With Linked Capacity Plus (and other trunking formats), talkgroups can be programmed into the controller with routing settings. That means we can have wide-area groups, or groups that bring up certain sites only. Or, just simple "local" talkgroups which only involve activity on the site they originate on.
- We can send out-of-band (not on active voice channel) data, such as Radio Check commands, Call Alert, individual or group text messaging or security packets, such as Radio Disable/Enable, if a radio goes missing.
- We can control who accesses the system via Restricted Access to System (RAS), which is essentially infrastructure protection. It keeps CCRs and improperly programmed radios off the network. It is not encryption. (But we run encryption anyway, because we can)
- Repeater health monitoring via admin software. We can check VSWR, voltages, power output, temperatures, power status (AC or battery backup), control channel status (revert one or many repeaters into analog service, if required for ARES whackers), etc. Admins get instant emails if a site sends out any error message. I don't know of any ham analog CSQ setups that do that.
- We get two talk-paths for each physical repeater at a given site, with a maximum of 16 timeslots per-site. Can't do that with DSTAR, Fusion or P25 (without a trunking controller, which also ties up an RF frequency as a dedicated control channel at each site).
- We have a log of every PTT access on our system. Useful for troubleshooting. We can disable/block Radio IDs if needed (stolen, someone drunk, etc.)
- A site goes down (on IP), and the rest of the network stays together. This includes the master site. In the analog world, if the hub site went down, your backbone would fail.
- Consistent audio quality across our entire network. No problems with distortion/poor levels. Anyone who wants to argue this obviously hasn't optimized their MOTOTRBO subscribers with the latest firmware/enhancements. I had a large role in that process, back in 2015.
- The ability to engage AES-256 digital voice encryption to stop unauthorized listeners from recording or streaming us without our consent. It has had a major benefit to our group. We are only required to provide service to those licensed to operate in the Amateur Radio Service (in Canada). Our law is worded as such: "You may not use a code or cipher that is SECRET". Once we share it with authorized persons, it's no longer a secret. Our government agrees with us.
I'm sure there's more reasons.
Last edited by a moderator: