Mumble - ArchWiki

# Mumble

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 mumble from the official repositories, or mumble-git from AUR.

For JACK support, install mumble-jack, or mumble-jack-git from 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 murmur from the official repositories.

The postinstall script will tell you to reload dbus and set the supervisor password. The default configuration doesn't 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.

#### Startup

Enable and then start Murmur with `systemctl enable murmur` and `systemctl start murmur`. If all went smoothly, you should have a functioning Murmur server.

#### Self-Signed Certificate

The factual accuracy of this article or section is disputed.

Reason: Not sure if this works when reverse lookups don't work properly. (Discuss)

By default, murmur will generate a default self-signed certificate. Clients connecting to the server will warn users about the host name not matching and the certificate being untrusted. If your server is in DNS, you can get rid of the hostname mismatch by creating your own self-signed certificate.

Create a secure directory for the certificate and key to live in and switch to it.

    mkdir /var/lib/murmur/ssl
    chmod 700 /var/lib/murmur/ssl
    chown murmur.murmur /var/lib/murmur/ssl
    cd /var/lib/murmur/ssl

Generate a private key for your server:

    openssl genrsa -des3 -out voip.example.com.key 1024

create a certificate sign request and strip the password from your private key

    openssl req -new -key voip.example.com.key -out voip.example.com.csr
    cp voip.example.com.key{,.orig}
    openssl rsa -in voip.example.com.key.orig -out voip.example.com.key

self-sign with your CSR a new server certificate for your mumble server

    openssl x509 -req -days 365 -in voip.example.com.csr -signkey voip.example.com.key -out voip.example.com.crt

Edit murmur.ini and tell it where your key and cert is:

    /etc/murmur.ini

    sslKey=/var/lib/murmur/ssl/voip.example.com.key
    sslCert=/var/lib/murmur/ssl/voip.example.com.crt

## Troubleshooting

### Joystick Binds Not Working or Mouse Binds Get Stuck

Kernel input devices by default are unreadable by Mumble. This causes Mumble to fall back onto a buggy global bind system. This can be fixed temporarily with

    sudo chmod a+r /dev/input/event*

or permanently fixed by creating a udev rule

    /etc/udev/rules.d/99-input-permissions.rules

    KERNEL=="event*", MODE="0644"

but be weary this exposes all your input devices to all your applications!

Category:

- Sound