Mumble

The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

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-git^AUR for the development version).

To use the Mumble overlay with 32-bit games, install lib32-libmumble^AUR.

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 here: Murmurguide. What follows is a quick-and-dirty, abridged version of that guide.

Installation

Install the murmur or murmur-git^AUR package. Both come with ICE support.

The postinstall 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.

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.

Config File

The default Murmur config file is at /etc/murmur.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 and then start murmur.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 murmur.ini and tell it where your key and cert are:

/etc/murmur.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 ^{(commit 1742f8)}.

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 murmurd"

SuperUser

To set the SuperUser password, use the following command.

# murmurd -ini /etc/murmur.ini -supw PASSWORD

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. A proposal for a patch exists at their source repository and a merge request has been merged and is slated for Mumble version 1.4.0. Tips for integrating this patch with Sway exist in the merge request.

undefined symbol: glPopClientAttrib

To use the overlay on a on 32-bit games, install lib32-libglvnd and preload libGL.so along with lib32-libmumble^AUR. With mumble-git^AUR, lib32-libmumble^AUR is no longer needed.

To display the overlay on a Steam 32-bit game, preload both with the shared libraries with the following launch options:

LD_PRELOAD=/usr/lib/mumble/libmumbleoverlay.x86.so:/usr/lib32/libGL.so %command%