Difference between revisions of "Mumble"

From ArchWiki
Jump to navigation Jump to search
(Created page with "From [http://en.wikipedia.org/wiki/Mumble_%28software%29 Wikipedia, the free encyclopedia]: :''Mumble is a voice over IP (VOIP) application primarily designed for use by game...")
 
(→‎Push-to-talk on Wayland: updated merge request status from submitted to merged)
 
(50 intermediate revisions by 26 users not shown)
Line 1: Line 1:
From [http://en.wikipedia.org/wiki/Mumble_%28software%29 Wikipedia, the free encyclopedia]:
+
[[Category:Voice over IP]]
 +
[[ja:Mumble]]
 +
From [[Wikipedia:Mumble (software)|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.''
+
: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).
 
This page goes over installation and configuration of both the client portion of the software (Mumble) and the server portion (Murmur).
Line 8: Line 10:
  
 
=== Installation ===
 
=== Installation ===
[[pacman|Install]] {{pkg|mumble}} from the [[Official Repositories]].
+
[[Install]] the {{pkg|mumble}} package (or {{AUR|mumble-git}} for the development version).
 +
 
 +
For [[JACK]] support, install the {{AUR|mumble-jack}} package.
 +
 
 +
To use the Mumble overlay with 32-bit games, install {{AUR|lib32-libmumble}}.
  
 
=== Configuration ===
 
=== Configuration ===
Line 15: Line 21:
  
 
For a discussion of advanced settings, see the
 
For a discussion of advanced settings, see the
[http://mumble.sourceforge.net/ official documentation].
+
[https://wiki.mumble.info/wiki/ official documentation].
 
The
 
The
[http://mumble.sourceforge.net/Mumbleguide Mumbleguide]
+
[https://wiki.mumble.info/wiki/Mumbleguide Mumbleguide]
 
is a good starting point.
 
is a good starting point.
  
Line 26: Line 32:
  
 
=== Installation ===
 
=== Installation ===
[[pacman|Install]] {{pkg|murmur}} from the [[Official Repositories]].
+
[[Install]] the {{pkg|murmur}} or {{AUR|murmur-git}} package.
 +
Both come with ICE support.
  
 
The postinstall script will tell you to reload dbus and set the supervisor password.
 
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.
+
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.
 
Setting the supervisor password is recommended, however.
  
Line 35: Line 42:
  
 
==== Network ====
 
==== Network ====
If you use a [[Firewall]], you'll need to open TCP and UDP ports 64738.
+
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.
 
Depending on your network, you may also need to set a static IP, port forwarding, etc.
  
 
==== Config File ====
 
==== Config File ====
The default murmer config file is at {{ic|/etc/murmur.ini}} and is heavily commented.
+
The default Murmur config file is at {{ic|/etc/murmur.ini}} and is heavily commented.
 
Reading through all the comments is highly recommended.
 
Reading through all the comments is highly recommended.
 +
More information can be found on the Mumble wiki [https://wiki.mumble.info/wiki/Murmur.ini here].
  
 
==== Startup ====
 
==== Startup ====
[https://bugs.archlinux.org/task/33675 There is currently a bug] that causes systemctl to hang when starting the murmur service after installing.
+
[[Enable]] and then [[start]] {{ic|murmur.service}}. If all went smoothly, you should have a functioning Murmur server.
A reboot will clear the issue, or you can create /run/murmur manually.
 
  
{{bc|
+
==== SSL/TLS ====
systemd-tmpfiles --create /usr/lib/tmpfiles.d/murmur.conf}}
 
  
Start and/or murmur with {{ic|systemctl start murmur}} and {{ic|systemctl enable murmur}}.
+
Obtain either a self-signed certificate as described in [[OpenSSL]], or a publicly trusted one with [[Let's Encrypt]].
If all went smoothly, you should have a functioning murmur server.
 
  
<!-- Not sure if this works when reverse lookups don't work properly and want to test before uncommenting
+
Please note, that there is currently no released version with support for Elliptic Curve certificates, but {{AUR|murmur-git}} supports it.
==== Self-Signed Certificate ====
 
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.
+
Edit {{ic|murmur.ini}} and tell it where your key and cert are:
{{bc|
+
 
mkdir /etc/murmur/ssl
+
{{hc|/etc/murmur.ini|2=
chmod 700 /etc/murmur/ssl
+
sslCert=/etc/letsencrypt/live/$domain/cert.pem
chown murmur.murmur /etc/murmur/ssl
+
sslKey=/etc/letsencrypt/live/$domain/privkey.pem
cd /etc/murmur/ssl
+
sslCA=/etc/letsencrypt/live/$domain/fullchain.pem
 
}}
 
}}
  
Generate a private key, create a certificate signing request from it, strip the password from your private key,  
+
==== SuperUser ====
{{bc|
+
To set the SuperUser password, use the following command.
openssl genrsa -des3 -out voip.example.com.key 1024
+
# murmurd -ini /etc/murmur.ini -supw PASSWORD
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
+
== Troubleshooting ==
openssl x509 -req -days 365 -in voip.example.com.csr -signkey voip.example.com.key -out voip.example.com.crt
+
 
}}
+
=== Push-to-talk on Wayland ===
  
Edit murmur.ini and tell it where your key and cert is.
+
Currently with [[Wayland]]/[[GNOME]]/[[Sway]], push-to-talk won't 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 [https://github.com/mumble-voip/mumble/issues/3243?_pjax=%23js-repo-pjax-container repository] and a [https://github.com/mumble-voip/mumble/pull/3675 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.
{{hc|/etc/murmur.ini|2=
 
sslKey=/var/lib/murmur/ssl/voip.example.com.key
 
sslCert=/var/lib/murmur/ssl/voip.example.com.crt
 
}}
 
-->
 

Latest revision as of 06:46, 26 September 2019

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).

For JACK support, install the mumble-jackAUR package.

To use the Mumble overlay with 32-bit games, install lib32-libmumbleAUR.

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-gitAUR 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.

Please note, that there is currently no released version with support for Elliptic Curve certificates, but murmur-gitAUR supports it.

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

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 won't 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.