Download the Mumble 1.2.19 installer from the Mumble website.
Run the Mumble installer
The default is to install only the client – select the option to install the Murmur server as well.
We will need to set the password that the LifeRing clients will use when connecting to the Murmur server. That involves editing the murmur.ini file – you may wish to set the Folder Options so that the extensions for known file types are not hidden. Showing hidden files is optional.
The murmur.ini file is located in C:\Program Files(x86)\Mumble. Scroll down to the serverpassword entry and type the password that clients will use when connecting to the Murmur server. This value will be entered in to the LifeRing server console. The LifeRing server will communicate the password to the LifeRing clients.
To accommodate multiple clients from one location, set autobanAttempts = 0.
To use some port other than the default 64738, edit the line:
to reflect the appropriate port for your system.
To control the bandwidth available to the clients, change the maximum bandwidth. The default is
To support clients having lower bandwidth, we recommend
On first launch, you will likely be prompted to allow Murmur to communicate through the firewall.
To view the console of the Murmur server, right click on the Murmur icon in the system tray. This gives you the option to Show Log or Quit Murmur.
This is what the initial log will look like – note the SuperUser password.
The password for the superuser is set but it is not terribly user-friendly and will be needed to configure the Murmur server, so you may wish to set it to something more user friendly. Right click on the Murmur icon in the task bar and Quit Murmur. In a command shell, (Run as Administrator if on a Windows Server machine) browse to the C:\Program Files(x86)\Mumble folder and type in the command
murmur.exe –ini murmur.ini –supw mumble4ptt
where the word in green is the password you expect to use. There will be a message that the password has been set. Then restart the Murmur server.
The Mumble client is used to configure the Access Control Lists on the Murmur server so that it will work with LifeRing. When you first open the Mumble client, it will want to configure the sound for that PC. This is unnecessary – simply Cancel out of the dialog.
Accept the default value for Certificate Management – Automatic certificate creation.
Run the client, then select the option to Add New server. Create an entry for the local server – here, we have used the name Local. Use the address 127.0.0.1 on port 64738 (or custom configured port), with username of superuser. Note that it has no option or a password.
The first time you connect, there will be an error message about the certificate. Accept the certificate.
Also, the first time you log in, there will be a message that you have entered a wrong password, then you will be prompted to enter a password. The superuser password is the one that you configured above – mumble4ptt in the example. After a successful login, if you view the Server entry, the password will have been added in.
Now you are ready to complete the steps in the MumbleACLTutorial document.
After the Access Control Levels have been set and the network configured, the last step is to enter the Murmur server information into LifeRing server so the clients can being using Mumble for PTT.
On the LifeRing server console, go to License > PTT Key. You will see the dialog shown below.
Select type of Mumble.
The PTT key is the IP and Port that the clients will be using to connect. Each octet is expressed in three digits. The IP shown in this example is 184.108.40.206. The port is 64738.
The admin name is not used by the Murmur server so can be left blank.
The password is the one that was created by editing the murmur.ini file.
This information is passed to each LifeRing client when they first log in to the LifeRing server. If any changes are made to these values while clients are logged on, the LifeRing server sends out an immediate update to each of the clients.
If the clients will be connecting to the Mumble server via an external IP address, then traffic on port 64738 will need to be passed through the firewall to the local IP of the Mumble server.