This section describes how to set up and run a Murmur server. Murmur is the server of the Mumble voice-over-IP (VoIP) suite.
The service type for the Murmur server. An example configuration can look like this:
(service murmur-service-type (murmur-configuration (welcome-text "Welcome to this Mumble server running on Guix!") (cert-required? #t) ;disallow text password logins (ssl-cert "/etc/letsencrypt/live/mumble.example.com/fullchain.pem") (ssl-key "/etc/letsencrypt/live/mumble.example.com/privkey.pem")))
After reconfiguring your system, you can manually set the murmur
password with the command that is printed during the activation phase.
It is recommended to register a normal Mumble user account
and grant it admin or moderator rights.
You can use the
mumble client to
login as new normal user, register yourself, and log out.
For the next step login with the name
SuperUser password that you set previously,
and grant your newly registered mumble user administrator or moderator
rights and create some channels.
murmur-configuration fields are:
Package that contains
User who will run the Murmur server.
Group of the user who will run the murmur server.
Port on which the server will listen.
Welcome text sent to clients when they connect.
Password the clients have to enter in order to connect.
Maximum of users that can be connected to the server at once.
Maximum voice traffic a user can send per second.
File name of the sqlite database. The service’s user will become the owner of the directory.
File name of the log file. The service’s user will become the owner of the directory.
Maximum number of logins a user can make in
without getting auto banned for
Timeframe for autoban in seconds.
Amount of time in seconds for which a client gets banned when violating the autoban limits.
Percentage of clients that need to support opus before switching over to opus audio codec.
How deep channels can be nested at maximum.
A string in form of a Qt regular expression that channel names must conform to.
A string in form of a Qt regular expression that user names must conform to.
Maximum size in bytes that a user can send in one text chat message.
(* 128 1024))
Maximum size in bytes that a user can send in one image message.
If it is set to
#t clients that use weak password authentication
will not be accepted. Users must have completed the certificate wizard to join.
Should murmur remember the last channel each user was in when they disconnected and put them into the remembered channel when they rejoin.
Should html be allowed in text messages, user comments, and channel descriptions.
Setting to true exposes the current user count, the maximum user count, and the server’s maximum bandwidth per client to unauthenticated users. In the Mumble client, this information is shown in the Connect dialog.
Disabling this setting will prevent public listing of the server.
Should the server advertise itself in the local network through the bonjour protocol.
Should the murmur server version be exposed in ping requests.
Murmur also stores logs in the database, which are accessible via RPC. The default is 31 days of months, but you can set this setting to 0 to keep logs forever, or -1 to disable logging to the database.
Should logged ips be obfuscated to protect the privacy of users.
File name of the SSL/TLS certificate used for encrypted connections.
Filepath to the ssl private key used for encrypted connections.
File name of a PEM-encoded file with Diffie-Hellman parameters
for the SSL/TLS encryption. Alternatively you set it to
"@ffdhe8192" to use bundled parameters from RFC 7919.
ssl-ciphers option chooses the cipher suites to make available for use
This option is specified using OpenSSL cipher list notation.
It is recommended that you try your cipher string using ’openssl ciphers <string>’ before setting it here, to get a feel for which cipher suites you will get. After setting this option, it is recommend that you inspect your Murmur log to ensure that Murmur is using the cipher suites that you expected it to.
Note: Changing this option may impact the backwards compatibility of your Murmur server, and can remove the ability for older Mumble clients to be able to connect to it.
Must be a
<murmur-public-registration-configuration> record or
You can optionally register your server in the public server list that the
mumble client shows on startup.
You cannot register your server if you have set a
It might take a few hours until it shows up in the public list.
Optional alternative override for this configuration.
Configuration for public registration of a murmur service.
This is a display name for your server. Not to be confused with the hostname.
A password to identify your registration. Subsequent updates will need the same password. Don’t lose your password.
This should be a
https:// link to your web
By default your server will be listed by its IP address. If it is set your server will be linked by this host name instead.