Ok - looking at the config, I see two (three) systems defined (two appear to be the same with different system aliases/names - but only one is in use in your zone/knob config).
- TRWS-P
- TRWS-F (seems to be a copy of TRWS-P and unused)
- RWC
TRWS-P has 3 sites defined - 1 site looks to be a 9 tower simulcast and the other two "appear" to be stand-alone towers/sites.
RWC also has 3 sites defined - 1 site looks to be a multi tower simulcast and the other two "appear" to be stand-alone towers/sites.
At this point, I'm not sure which system you are monitoring when the radio is going silent. However, given the nature of the sites programmed for each of the two systems, a couple of questions:
- which system are you having this issue on (or is it doing it on both)?
- when you stop receiving, are you seeing/hearing and indications of "Out Of Range"?
- when you are receiving, which RFSS/Site is being displayed on the radio when no voice call is being received?
- most important question: when things go quiet, is the radio still displaying that same site or a different one?
I have encountered at least two systems - one in NC and one in FL - where a multi-site system has at least one site that carries little to no voice traffic. In a more general sense, some "stand-alone" towers tend to provide specific purpose/coverage (specific agency and/or gap filling) and if your radio locks onto and stays on that tower, the radio appears to no longer be receiving anything (note that when you do something like switching systems and/or power cycling may cause the radio to start searching for a site again and having it revert back to the simulcast/busy site).
Without any further details, I would not be surprised if the radio is potentially over time switching from the simulcast site on one or the other system to a stand-alone tower that may not be carrying as much/the same traffic and/or the talkgroups that you have programmed. I am only speculating at this point and don't want to say that it could not be some other issue related to the radio or firmware itself - just looking at possibilities. Depending upon the questions (and answers) above, we can try some things to verify and/or solve what you are experiencing (maybe).
Let's keep digging.