You can't just turn the radio to the required channel and just "monitor" the MDT data through a computer that has the proper software. The point of my post above was to give a brief and less than detailed idea of how the system works and how it is that the mobile terminals are able to access the data being transmitted.
Maybe you missed the part about ENcryption coding, and that you will need the software and a valid log-in for BOTH the system level AND the CAD level, all of which requires a transmitter with a valid ESN in order to GET the current DEcryption coding so that you can "monitor" the data. Without a way to respond to polling, there's no way to get the coding updates as they occur. No DEcrypt coding, no "monitoring." None of this process has anything at all to do with running wants/warrant checks. That's another level altogether.
The system looks at the ESN of the radio to determine if it's a registered unit, then it looks at your system log-in to see if you're an authorized user. If you pass those tests, you're logged in as "active" in the system. Now you can begin your log-in to the CAD system using the last encryption coding your computer has on board. If you pass the log-in, the CAD will do the little coding change dance with your unit and you'll be logged into the CAD as "active." Then and only then will your computer be able to DEcrypt the CAD data being transmitted. As long as your computer is fully logged in, the periodic polling sessions will keep your unit logged in.
Since unit polling is individual, the little coding change dance is also frequently done with short individually encrypted exchanges, so forget a blanket coding exchange that might work for all units. Outgoing Encryption coding can be different than incoming coding, too, so add that to the mix, not that any of that would affect just receiving data so long as the incoming coding hasn't changed.
The system tracks which units have updated and which haven't. Those that haven't (like being out of range for a set number of polling intervals but not long enough to drop the system) won't have the new coding and may revert to being logged into the system but not to the CAD. No CAD log-in, no updates, so the operator has to log-in to the CAD again to get the current coding so his computer will DEcrypt properly. The system knows this MDT hasn't updated and allows it a set number of log-in attempts with the old coding before it pulls the plug. If your unit has been out of range or out of service for a sufficient period of time, and the last coding in your computer is old enough to have been discarded by the system, you'll have to call the "help desk" and get initially logged in manually by the system people. Then you can log into the CAD itself if all else is still valid.
As to plain text transmissions, those are now pretty much limited to local option preset text type status and disposition codes, if in fact any plain text is still used at all. You are correct about older systems still in service that may use plain text, but even those systems go to encryption when the data is anything dealing with secured info because that's a part of the software that allows access to the secured sites.