First, let me say that uMurmur is exactly what I have been looking for.
I didn't think I could run a voice chat server on my entry level NAS.
I want to outline some of the steps I have taken in case it saves some time for others.
My Synology model is the 212j and it is currently running DSM 4.0.2233
First, you should install the Mumble client on at least one machine.
Start the Package Center, click 'Settings' button then 'Package Sources' tab
Now, click on the 'Other Sources' tab and you will be able to install 'uMurmur'
Here's the first area where I think an improvement can be made.
I had expected to click on the uMurmur icon off the home menu and configure uMurmur.
Unfortunately, that is a hyperlink to start the client.
Here's how I was able to reconfigure the server:
First, I had to install the 'Configuration File Editor' package.
Save it to your local machine and then use the 'Install / Update' button from Package Center to install the package
Once installed, click on the 'Config File Editor' icon from the home menu.
Select 'Config File Editor' from the drop down menu and add this line to the bottom of that list:
/volume1/@appstore/umurmur/var/umurmur.conf,uMurmur
Click the Save button and then close the editor and re-open it.
Now you will see 'uMurmur' on the drop down list - when you select it, you will be able to edit the uMurmur configuration file
The first thing I tried was to add a password.
When I use the Mumble client and the SuperUser account, I enter that password and I am connect as an administrator.
The problem is, I can't for the life of me figure out what the admin can do that everyone else can't do.
After you save configuration changes, just restart the service from the Package Center.
Going to be setting up our channel list next.
Can anyone explain what the SuperUser is supposed to be able to do?
I understand we can't make permanent channels from the client.
I have also experienced disconnects where the client says the remote server disconnected.
The client tries to reconnect and then I get a message that the account is already in use.
This even happens on the LAN side. Any hints on that problem?
My last question is- how do I prevent just anybody from using my server?
I see a bunch of certificate security stuff, but no ACL or alternative way to authorize clients.