Official Mumble VoIP Forums

Force push-to-talk on server

How to do...
Hi

I need to force PTT on my server. How can I do that.

The suggest function is not enough.
You can't.

It's called a suggest function because that is all the assurance we can make, you can't ever force someone to use PTT. Anyone with a hex editor or the ability to build the software themselves could ignore it.

Decent moderators is about the only thing you can do - simply kick users who aren't using PTT until they get the message.
You just can't make it easy, can you!?

Maybe I can't force someone to use PTT but You could force them to be muted if they don't.
dennis wrote:You just can't make it easy, can you!?

Maybe I can't force someone to use PTT but You could force them to be muted if they don't.
You really can't, unless you control the machine the user is on. Like I said, decent moderators and/or users who respect the rules is the only actual solution to this. A way to enforce PTT or any other client setting is writing checks we can't cash - it's akin to enforcing a user wear pants while they use the PC.
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.

It should be the admin of the server who decides what the clients can do or not.
Except, all the server knows is that there is audio being transmitted. It has no way of knowing what method the audio is being inputting in to mumble. As far as the server is concerned there is no difference between continuous, PTT, and voice activated.

That said, if properly setup, listeners should not be able to tell the difference between VA and PTT.
The client can be changed so it transfers that information to the server and the server need to be changed so it can handle that information.

This is the only thing that is bad with Mumble. It would be sweet if it got changed.



"...if properly setup, listeners should not be able to tell the difference between VA and PTT"

All the people on the server does not live alone. Children are noisy. TV and music and what not.
As soon as you start transfering more information then Mumble is no longer Low-Latency and becomes as high latency as all the others.
Sending a few bits telling the server about PTT can't raise the latency notably.

Why not send the information while not talking!?
Except it wouldn't be only a few bites. Its "a few bites" (if that few) per person per server instance. and it would have to poll a lot in order to stay up to date. The best would be if it polled every time the mic actives but that would create latency too as the server would have to turn around and allow the mic to pass audio.

I bet if it is something you are really interested in, you could run some sort of script in python and mumo to do this, but I'm guessing the appetite is not there from the devs to do this as it would probably be a huge resource and bandwith hog.