Get desktop application:
View/edit binary Protocol Buffers messages
When this audio is sent by the client to the server, this is set to the target of the audio data. This target is a number in the range [0, 2^{32} - 1], where 0 means "normal talking", 2^{5} - 1 means "server loopback" and all other targets are understood as shout/whisper targets that have previously been registered via a VoiceTarget message (via TCP).
When this audio is sent by the server to the client, this indicates the context in which the audio has been sent. 0: Normal speech 1: Shout to channel 2: Whisper to user 3: Received via channel listener
The session of the client (sender) this audio was originally sent from. This field is not required when sending audio to the server, but will always be set when receiving audio from the server.
The number of the first contained audio frame (indicating the position of that frame in the overall audio stream)
The actual voice data payload in the Opus format.
Optional positional data indicating the speaker's position in a virtual world (in meters). This "list" is really expected to be an array of size 3 containing the X, Y and Z coordinates of the position (in that order).
A volume adjustment determined by the server for this audio packet. It is up to the client to apply this adjustment to the resulting audio (or not). Note: A value of 0 means that this field is unset.
A flag indicating whether this audio packet represents the end of transmission for the current audio stream
* Ping message for checking UDP connectivity (and roundtrip ping) and potentially obtaining further server details (e.g. version).
Timestamp as encoded by the client. A server is not supposed to attempt to decode or modify this field. Therefore, clients may choose an arbitrary format for this timestamp (as long as it fits into a uint64 field).
A flag set by the sending client, if it wants to obtain additional information about the server.
The version of the server in the new version format. The new protobuf Ping packet introduced with 1.5 drops support for the legacy version format since both server and client have to support this new format. (See https://github.com/mumble-voip/mumble/issues/5827)
The amount of users currently connected to the server
The maximum amount of users permitted on this server
The maximum bandwidth each user is allowed to use for sending audio to the server