Difference between revisions of "Mumble"

From ArchWiki
Jump to: navigation, search
m (Remove empty line.)
(update Pkg/AUR templates)
(Tag: wiki-scripts)
 
(33 intermediate revisions by 17 users not shown)
Line 1: Line 1:
[[Category:Sound]]
+
[[Category:Telephony and voice]]
From [http://en.wikipedia.org/wiki/Mumble_%28software%29 Wikipedia, the free encyclopedia]:
+
[[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 9: 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 (or {{AUR|mumble-jack-git}}{{Broken package link|package not found}} for the development version).
 +
 
 +
If you're on a x86_64 system and would like to use the Mumble overlay with 32-bit games, you'll need to install {{AUR|lib32-libmumble}}.
  
 
=== Configuration ===
 
=== Configuration ===
Line 27: Line 32:
  
 
=== Installation ===
 
=== Installation ===
[[pacman|Install]] {{pkg|murmur}} from the [[Official Repositories]].
+
[[Install]] the {{pkg|murmur}} package.
 +
 
 +
For ICE support, install the {{AUR|murmur-ice}}{{Broken package link|package not found}} package.
  
 
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.
+
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 36: Line 43:
  
 
==== 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.
  
 
==== 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}}.
+
{{Merge|Let's Encrypt|Most of this is covered elsewhere.}}
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
+
Obtain either a self-signed certificate as described in [[OpenSSL]], or a publicly trusted one with [[Let's Encrypt]] according to the following directions:
==== 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.
+
[[Install]] the {{Pkg|certbot}} package.
{{bc|
+
Temporarily turn off any webservers listening on port 443, if any (apache/nginx/etc)
mkdir /etc/murmur/ssl
+
# systemctl stop nginx
chmod 700 /etc/murmur/ssl
+
Generate the Let's Encrypt certificate for Murmur
chown murmur.murmur /etc/murmur/ssl
+
# certbot certonly --standalone --standalone-supported-challenges tls-sni-01
cd /etc/murmur/ssl
+
Re-enable webservers, if any
}}
+
# systemctl start nginx
  
Generate a private key, create a certificate signing request from it, strip the password from your private key,
+
Edit {{ic|murmur.ini}} and tell it where your key and cert are:
{{bc|
 
openssl genrsa -des3 -out voip.example.com.key 1024
 
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
 
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.
 
 
{{hc|/etc/murmur.ini|2=
 
{{hc|/etc/murmur.ini|2=
sslKey=/var/lib/murmur/ssl/voip.example.com.key
+
sslCert=/etc/letsencrypt/live/$domain/cert.pem
sslCert=/var/lib/murmur/ssl/voip.example.com.crt
+
sslKey=/etc/letsencrypt/live/$domain/privkey.pem
 +
sslCA=/etc/letsencrypt/live/$domain/fullchain.pem
 
}}
 
}}
-->
 

Latest revision as of 07:27, 30 October 2017

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 (or mumble-jack-gitAUR[broken link: package not found] for the development version).

If you're on a x86_64 system and would like to use the Mumble overlay with 32-bit games, you'll need to 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 package.

For ICE support, install the murmur-iceAUR[broken link: package not found] package.

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

Startup

Enable and then start murmur.service. If all went smoothly, you should have a functioning Murmur server.

SSL/TLS

Merge-arrows-2.pngThis article or section is a candidate for merging with Let's Encrypt.Merge-arrows-2.png

Notes: Most of this is covered elsewhere. (Discuss in Talk:Mumble#)

Obtain either a self-signed certificate as described in OpenSSL, or a publicly trusted one with Let's Encrypt according to the following directions:

Install the certbot package. Temporarily turn off any webservers listening on port 443, if any (apache/nginx/etc)

# systemctl stop nginx

Generate the Let's Encrypt certificate for Murmur

# certbot certonly --standalone --standalone-supported-challenges tls-sni-01

Re-enable webservers, if any

# systemctl start nginx

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