Mumble¶

In this article

• Mumble. Key Features
• Deployment Features
• Getting started after deploying Mumble
• Client Configuration
• Connecting to the Server
• Server Management
• Security and Maintenance
• Ordering a server with Mumble using the API

Mumble. Key Features¶

• The client applications for this platform are available on Windows, Linux, macOS, iOS, and Android, making it cross-platform compatible.
• The Opus audio codec is used to ensure low latency and high sound quality.
• Voice traffic is encrypted using the TLS protocol to maintain confidentiality of conversations.
• The server can handle thousands of simultaneous users, making it highly scalable.
• Spatial audio and directional speech are supported, providing realistic audio in games and virtual reality.
• The plug-in architecture can be used to extend the functionality of both client and server components.

Deployment Features¶

• Installed Software:
  • Mumble server.

Getting started after deploying Mumble¶

A notification will be sent to the e-mail specified during registration that the server is ready for work after paying for the order. It will contain the IP address of the VPS, as well as the login and password for the connection. Clients of our company manage the hardware in the server`s and API control panel — Invapi.

• Login and Password for server connection: sent in an email to your email address when the server is ready after software deployment.

Getting the Administrator Password¶

Step 1: Connect to the server via SSH:

ssh root@YOUR_IP_ADDRESS

Step 2: Find the Docker container ID for Mumble:

docker ps

The output will show a line similar to this:

CONTAINER ID   IMAGE                  COMMAND        PORTS
a1f296c17976   ajmandourah/mumble    /start.sh    0.0.0.0:64738->64738/tcp,
                                                  0.0.0.0:64738->64738/udp

Remember the CONTAINER ID (first column): a1f296c17976

Step 3: Enter the container and view the log:

docker exec -it <container_ID> /bin/bash

tail -100 /mumble/mumble-server.log | grep Password for 'SuperUser'

The output will show something like:

<W>2025-12-19 10:15:23.456 Password for 'SuperUser' set to 'aB3dE7gH9kL2'

Save this password!

docker exec -it <container_ID> murmurd -ini /etc/mumble-server.ini -supw NewPassword123

murmurd -ini /etc/mumble-server.ini -supw NewPassword123

Step 4: Exit the container and check the server is running:

exit

docker ps

Client Configuration¶

To start using the service, you need to download the Mumble client to your local device and install it.

On the first launch, you'll need to complete the initial setup through the configuration wizard:

1. Device input and output - you can leave the default options, and also select additional settings (optional):

   • Use echo suppression;
   • Enable positional audio;
   • Attenuate applications while other users talk.

2. Device Tuning - set to minimum value using the slider;

3. Volume Tuning - adjust the level;

4. Voice Activity Detection - set the threshold (on this step you can also assign a button to activate voice communication);

5. Quality & Notifications - set preferences;

6. Positional Audio - adjust settings;

7. Use Existing Certificate - it's recommended to choose Automatic certificate creation;

8. Click the Finish button.

Changing the Interface Language¶

The Mumble interface is in English by default. To change the language settings:

1. Close the server list;
2. Navigate to: Configure → Settings → User Interface → Language;
3. Select language from the dropdown list;
4. Click the Apply and OK buttons:

The application will restart with the selected interface language.

Configuring Audio Output¶

After connecting to the server, it's recommended to configure the Mumble client. All settings are available in the Configure → Settings menu in desktop versions or in the app settings on mobile clients.

Audio Quality¶

Mumble uses the Opus codec with adjustable target audio transmission quality.

Section: Audio Input → Compression → Quality

• 40 kbit/s - standard value, sufficient for comfortable voice communication
• 64-96 kbit/s - high quality for music or professional audio
• 32 kbit/s - traffic savings (mobile internet), possible quality reduction

Audio Transmission Modes¶

Section: Audio Input → Transmission

By default, Voice Activity mode is used. In this mode, the microphone automatically activates when speech is detected.

Sensitivity adjustment:

• Sliders allow you to adjust the trigger threshold;
• Avoid transmitting background noise;
• Ensure correct voice recognition.

Alternative modes:

• Push-to-Talk - microphone activates only when pressing a button (recommended for noisy environments);
• Continuous - microphone works constantly (not recommended).

Audio Processing¶

Section: Audio Input → Audio Processing

The client supports noise suppression algorithms:

• Speex - classic algorithm;
• RNNoise - more effective at suppressing constant background noise (fan, air conditioner, keyboard).

You can use both algorithms together for maximum effect.

Noise suppression:

• Adjust the Speex noise suppression strength slider;
• Enable RNNoise for additional filtering;
• Combine both methods for best results.

Echo Cancellation¶

Echo cancellation parameters should be selected depending on the equipment used:

• When working with speakers - more aggressive echo cancellation mode;
• When using headphones - echo cancellation can be disabled.

Configuring Audio Input¶

Buffering¶

Section: Audio Output

Two key parameters affect playback stability:

1. Default Jitter Buffer

• Accumulates incoming audio before playback;
• Compensates for network instability;
• Default: 10 ms;
• When to increase: if speech stutters when people start talking.

2. Output Delay

• Adds buffering before audio output;
• When to increase: if you hear rapid stuttering or artifacts on some audio drivers.

Volume and Attenuation¶

• Adjust volume with the slider in the client or through the system mixer;
• Attenuation - useful feature that automatically lowers music or game sounds when someone is speaking.

Testing Settings¶

Use Loopback Test for verification:

• Local mode - tests input and output audio;
• Server mode - tests network connection.

Notifications and Chat¶

Section: Messages

In this section, you can flexibly configure which events will:

• Be displayed in the message window;
• Be accompanied by a sound signal;
• Be announced using Text-to-Speech.

By default, main notifications are enabled:

• User connection and disconnection;
• Critical messages and warnings.

Connecting to the Server¶

To connect to the Mumble server, use the following credentials:

• Login - SuperUser;
• Password - automatically generated password (obtained from logs).

Connection Process¶

Step 1: Launch the Mumble client and click the Add New... button

Step 2: Fill in the connection form:

• Label: any name for your server;
• Address: your VPS IP address;
• Port: 64738 (default, if not changed);
• Username: SuperUser;
• Password: password from server logs.

Step 3: Click OK, select the server from the list and click Connect.

Step 4: On first connection, the client will show a warning about a self-signed SSL certificate - this is normal for a new server, click Yes.

After connecting, you'll be in the root channel with the SuperUser name and administrator icon.

Connecting Regular Users¶

To connect to the server, regular users need to:

1. Add a new server in the Mumble client;
2. Specify the server IP address;
3. Specify port 64738;
4. Choose a username;
5. Password is not required for regular users.

Server Management¶

Creating Channel Structure¶

By default, there's only the root channel. For convenience, let's create several sub-channels.

Creating a channel:

1. Right-click on the root channel;
2. Add;
3. Enter the channel name.

Example structure:

Root (Root channel)
├── General Room
├── Games
│   ├── Counter-Strike
│   └── Dota 2
├── Work
│   ├── Meetings
│   └── Communication
└── AFK (for away)

Channel Access Rights¶

Access rights are configured through the channel context menu:

1. Right-click on channel → Edit;
2. ACL tab:

What can be configured:

• Set a password for the channel;
• Restrict access to specific user groups;
• Allow/prohibit speaking in the channel;
• Configure rights for creating sub-channels.

User Management¶

User Registration¶

How a user registers:

1. Connects to the server with any name;
2. Right-click on their name → Register;
3. The server remembers the user's certificate.

After registration:

• User automatically connects on next login;
• Username is reserved;
• Access rights can be assigned.

Manual Account Creation¶

The administrator can create accounts manually:

1. Menu Server → Registered Users → Add;
2. Enter the username.

Security and Maintenance¶

Changing the Port¶

The standard port 64738 is easily found by scanners. If you want to make server discovery more difficult, you can change the port to any other.

Step 1: Copy config to host:

docker cp <container_ID>:/etc/mumble-server.ini ./mumble-server.ini

Step 2: Edit the config:

nano mumble-server.ini

Find the line port=64738 and change to the desired port, for example:

port=25000

Step 3: Copy back:

docker cp ./mumble-server.ini <container_ID>:/etc/mumble-server.ini

Step 4: Restart the server:

docker restart <container_ID>

Step 5: Now users should specify the new port when connecting:

IP:new_port

Backup¶

Backup is important if you're using Mumble not just for family communication.

The Mumble database with user and channel settings is located at /mumble/mumble-server.sqlite inside the container.

Manual Backup¶

Periodically copy the database to yourself:

docker cp <container_ID>:/mumble/mumble-server.sqlite ./mumble-backup-$(date +%Y%m%d).sqlite

This command will create a file with the current date, for example: mumble-backup-20250112.sqlite

Restoring from Backup¶

If the server crashes, you can deploy a new container and restore all settings:

docker cp ./mumble-backup-DATE.sqlite <new_container_ID>:/mumble/mumble-server.sqlite

docker restart <new_container_ID>

Ordering a server with Mumble using the API¶

To install this software using the API, follow these instructions.

Some of the content on this page was created or translated using AI.