- 1 Introduction
- 2 Distribution-specific Murmur
- 3 Basic configuration
- 4 Running Murmur as a regular user
- 5 Administration
- 6 Alternative Murmur implementations
Murmur is the server component for Mumble. This article is meant to give you the necessary information to configure and run your own server. If you need a step-by-step guide to help you set up a Murmur server, read this.
If you find anything incorrect or missing in this article feel free to add it yourself.
By default, murmur is configured to run from a regular user account, and on Windows and OSX this is the only way it works. However, on distributions with prepackaged murmur (Debian/Ubuntu), murmur is configured to run as a sytem service, just like your webserver, mailserver and whatever else you've got running. This "global" installation is a ready, turn-key solution, most of the information here does not apply to you. Most packages also include the 'murmur-user-wrapper' script, which does all of the below for you if you want to run as a regular user (including starting DBus).
So, on these systems, you can still run murmur manually, but you will then not benefit from the extensive care that has gone into preparing those packages.
If you need to register users or change the settings of a virtual server, read the section on Advanced Configuration.
The default settings for a murmur server are configured in murmur.ini. Here you can configure the welcome text, port number and other settings. However, these are just default settings and can be overwritten via the Ice RPC without changing the .ini; if you're running multiple virtual servers, each virtual server has it's own configuration, which is maintained internally by Murmur (see below).
The default port for a Murmur server is UDP and TCP 64738. Have a look at URLs to see how to publish links to your server.
Adding an authenticated user can be done through various means. Unless you need automated registration of users or authentication against an external database using the functionality built into the client is the easiest method. If you need more control you can use Ice or DBus.
Setting the SuperUser password
Until you've set a password for the SuperUser, the account will be disabled. You don't need the SuperUser account to run a simple server, but you do need it if you want to give your regular user account any privileges. To set the password on Linux run
murmurd -supw <password>
This will set the password and return immediately. To run the server remove this parameter. If you are on a debian based system, you may also run
sudo dpkg-reconfigure mumble-server
If you're on Windows, then you set the password by running
"C:\Program Files\Mumble\murmur.exe" -supw <password>
Running Murmur as a regular user
If you are on Win32, you can simply start murmur.exe from the command line, or even easier just start it from the Start Menu.
For full functionality, murmur requires either a working DBus daemon or Ice being enabled. We recommend using the Ice interface, as DBus is considered deprecated and while it is not planned to remove it anytime soon it will not receive any new functionality.
Running the daemon
To run murmur, simply type
For debugging, you might want to add -fg -v to the command line, which will stop the program from running in the background and.
By default murmur opens it's configuration file, database file and logfile in your current directory. The configuration file can be overridden with the -ini parameter, and the database and logfile can be set form the ini file.
This section contains different ways of administrating a murmur Server.
Note: Most of these interfaces are created and maintained by third parties and the Mumble developers have no influence on the stability and/or security of these projects.
There are several browser based interfaces which can be used to administrate the Murmur server. If you need something very basic or want to create your own interface you should take a look at Murmurs script folder which contains some basic web-interface examples which use Ice or DBus. Additionally the following table contains a collection of more elaborate Web-Interfaces:
|Mumble PHP Interface||PHP||No||Yes||Yes||No||User and Admin functionality||
|MAP - Mumb1e Admin Plugin||PHP||Yes||No||Yes||No||Webinterface to manage Server User, Plugin User and Servers; useful for Server hosting|||
|MurmurCP||ASP.NET + ICE||No||Yes||Yes||No||Multiple Virtual Servers, Registration, Server Status, Forgot Password|||
|Mumble-Django||Python + Django||Yes||Yes||Yes||Yes||Channel viewer, admin panel, multiserver, registration, textures|||
|Simpleregister||PHP||No||Yes||Yes||No||Extended script from the sample folder|||
|Mumble Admin Ice PHP||PHP||No||Yes||Yes||No||Admin functionality|||
|Murmur Admin Console||Windows||Yes||No||Add, edit and delete players over SSH|||
|MurmurCL||multi-platform||No||Yes||Commandline interface written in Python||win32 exe / python source|
|mice||multi-platform||No||Yes||Helper script written in Python|||
|mmctl||Python||Yes||No||1.1.8||Easy to use script for managing servers and adding users locally|||
Manual configuration using DBus
If you are not able to use an additional application for administrating Murmur there is still the possibility of manually communicating with the server using DBus. You can find detailed information on this in our DBus article.
Alternative Murmur implementations
The Mumble team appreciates and supports the implementation of the Mumble protocol. Unlike other proprietary applications everyone is free to write his own Mumble server software and add it to this list.
uMurmur is a minimalistic Murmur implementation without dependency on QT-core. It lacks features of Murmur but aims at working well on embedded devices like routers. It currently supports 1.1.x Mumble clients. Read more at the uMurmur project page.