Jump to content
From ArchWiki

Related articles

- Discord
- TeamSpeak

From Wikipedia, the free encyclopedia:

  Mumble is a voice over IP (VoIP) application primarily designed for use by gamers, similar to programs such as TeamSpeak and Ventrilo.

This page goes over installation and configuration of both the client portion of the software (Mumble) and the server portion (Murmur).

## Client

### Installation

Install the mumble package (or mumble-gitAUR for the development version).

### Configuration

When you first launch the client, a configuration wizard will take you through the setup process. Settings can be changed later through the menu.

For a discussion of advanced settings, see the official documentation. The Mumbleguide is a good starting point.

## Server

The Mumble project maintains a good guide for setting up the server. What follows is a quick-and-dirty, abridged version of that guide.

### Installation

Install the mumble-server or murmur-gitAUR package. Both come with ICE support.

The post-install script will tell you to reload dbus and set the supervisor password. SQLite is used as the default database. The default configuration does not use dbus, so you can ignore that if you want. Setting the supervisor password is recommended, however.

#### Set supervisor password

To set the supervisor password, run this command as the mumble-server user (default `_mumble-server`):

    $ mumble-server -ini /etc/mumble/mumble-server.ini -supw PASSWORD

This will also create a SQLite database in the defined directory inside of the configuration file `/etc/mumble/mumble-server.ini`

### Configuration

#### Network

If you use a firewall, you will need to open TCP and UDP ports 64738. Depending on your network, you may also need to set a static IP, port forwarding, etc.

#### Configuration File

The default Murmur configuration file is at `/etc/mumble/mumble-server.ini` and is heavily commented. Reading through all the comments is highly recommended. More information can be found on the Mumble wiki here.

#### Startup

Enable/start `mumble-server.service`. If all went smoothly, you should have a functioning Murmur server.

#### SSL/TLS

Obtain either a self-signed certificate as described in OpenSSL, or a publicly trusted one with Let's Encrypt.

Edit `mumble-server.ini` and tell it where your key and cert are:

    /etc/mumble/mumble-server.ini

    sslCert=/etc/letsencrypt/live/$domain/cert.pem
    sslKey=/etc/letsencrypt/live/$domain/privkey.pem
    sslCA=/etc/letsencrypt/live/$domain/fullchain.pem

Tip: `SIGUSR1` can be used to live-reload SSL settings since version 1.3.0 [1].

For example, if using a certbot systemd unit, adding this to the end of the `ExecStart` line in the unit file would reload the certificate after a new one is issued:

    --deploy-hook "/usr/bin/killall -SIGUSR1 mumble-server"

## Troubleshooting

### Push-to-talk on Wayland

Currently with Wayland/GNOME/Sway, push-to-talk will not work without the window being in focus. Not allowing clients to sniff on the input when they do not have focus is a feature in Wayland, and it will be kept that way.

Since Mumble 1.4, the Mumble IPC can be used to toggle push-to-talk:

    $ mumble rpc starttalking
    $ mumble rpc stoptalking

Category:

- Voice over IP