Thanks for the clarification. When you say channels is that the number of frequencies in the pool/site? So, if our county Phase II has 25 frequencies in the site that means there can be 50 simultaneous active TG and the SDR can monitor all of them?
"The SDR" -- I'm speaking specifically about SDRTrunk. Not just every SDR-based tool can do it.
And yes, if your computer system has enough resources and SDRTrunk is set up properly, including giving Java the additional memory it needs, then if you have a 25-channel county site (one active control channel, 24 voice channels with up to 48 talkpaths) then yeah SDRTrunk can handle it. I don't use anything else so I can't speak of anything else.
It's important to note that many sites that have a lot of frequencies assigned to them often do not use them all for TDMA (Phase II) but have some in use to support Phase I radios. So usually, that system with 25 freqs is unlikely to be carrying 48 simultaneous voice calls under any normal circumstance.
You need to have enough dongles / Airspys / RSPs / etc to cover the whole range of frequencies though. For instance, in Ohio we've got a lot of sites that have both 769-775 and 851-859.xxx frequencies on them. For those, there has to be enough SDR capacity to potentially cover any active frequencies on the site in those ranges -- that's 15 mhz. That's a lot of dongles, or a combination of dongles and higher end devices that allow 6-10 (5-8 mhz) of spectrum to be monitored.
The site I monitor is Phase-I only simulcast, 8 voice channels, with all of the voice channels between 851.1625 and 858.4625. I use a single Airspy R2 to monitor all 8 voice channels of that simultaneously. In addition, that same setup also allows me to monitor the local AEP Phase II P25 site because its frequencies fall within the range that the Airspy can handle. So that's another two voice channels.
With the sites I monitor, rarely are more than 4-5 voice channels active out of those 10, and in fact 4-5 active at once is rare. Of course, I've seen other systems (like the simulcasts up in Northern ohio (Stark / Summit / Cuyahoga) be extremely busy at times.
And of course you can monitor less voice channels, but you'll miss some traffic. For instance, I could set SDRTrunk to monitor only four voice calls instead of 8. When the system isn't busy, I'd still pick up everything. But if the system gets busy and there were more than 4 voice calls, I wouldn't pick them all up.
SDRTrunk seems to work great, even throwing 10 or 20 voice conversations at it simultaneously. I've never monitored a site that had more than 20 simultaneous voice conversations on it. I'm sure they are out there, but I've never monitored them.