Except we can't assure that it will never happen that the client will lie and say it's using PTT when it's not. So us advertising functionality that "enforces PTT" is effectively a lie, we're promising things we can't deliver.dennis wrote:The audio stream goes to the server before it gets transferred to the other clients.
It can't be hard to mute audio from a user that doesn't have PTT enabled.
That's the entire reason behind the suggest* configuration knobs, because we can only suggest these things, and have no way of enforcing them. I could be overridden by one of the primary devs of course, but I can't see this ever changing. That is to say that from where I'm sitting, it will not ever happen that we will include so it's a waste of time arguing about it.
If your users' voice activation is being triggered by their kids or their TV, put them in a time out (admin mute, separate channel, whatever) until they fix their mic or switch to PTT. You can enforce this yourself with decent admins! If your users don't care enough about the people they talk with to not have kids shrieking in the background or the TV going, that's not really a software problem.