Oh, in that case, should be pretty easy to trunk, assuming I got all the right iden_ups and voice grant assignemnts correct in the software, the dev branch should able to trunk with the rtl input or the rigctl to GQRX/SDR++ But again, you say most traffic is on one frequency, I've noticed similar on another P25 system, where the voice priority always seems to go to one frequency, and the other two are used for overflow, but it never seems to get busy enough to use more than one frequency most times.
That's funny you mention that, because some of the code in the dev branch for tuning rigctl comes from 'gqrx-scanner' by neural75 on Github. The method I use for looking for a control channel (or just sync) is literally just using snippets of tuning code to cycle through imported frequencies, or frequencies stored in an array from the appropriate P25 PDUs and could honestly be used as is as a make shift digital scanner, albeit one with a 1 second delay between tunes. I've found that trying to run software like gqrx-scanner or just trying to tune rapidly with a dongle isn't going to work well, it needs a very small delay to adjust the noise floor and so on, thus I use a one second hangtime delay as a minimum.
Yeah, OP25 does have a steep learning curve, that's for sure. I have a handful of configurations saved, and end up doing a copy/paste and changing things in one or two of them when I want to set something different up. But, if you get it set up and working, it works extremely well.
I honestly have no idea. I switched to SDR++ and haven't looked back. I was just going by what another user posted in here quite a while back.