Does anyone here admin a Mumble server? looking for advice

[ashin]

We are trying out Mumble compared to Vent, and so far I see pro's and con's.

But really to compare them I need to get the permissions set up and all that stuff. I am finding this very confusing in Mumble. I see it has access tokens, which basically make it work like Vent if I understand it - password protected channels, right?

But then you can set up a more robust permission system more like Teamspeak, where users are in groups and that determines their permissions in various channels. This is the part that is totally throwing me off. I found the documentation on the sourceforge site to be .. well, not enough for me. :P

Basically this is how I want my voice server to work:

1. Anybody with the info can log in and use the public guest channels.

2. Only guild members can access other channels. (Should I just have them require ppl to be registered, and then do manual registration?)

3. Only senior members and officers can drag players from guest chans into member chans.

4. Only officers can access the officers lounge.

5. Only chapter leads can do admin things to the server (new chans, etc.)

What I don't want to do is create a huge amount of work manually assigning every person to groups. So I feel I need some more automatic way at least for base member access. Manually assigning the more senior ranks is fine.

Thanks for any advice! I'm desperate to escape Vent but I need to find the right solution.

[Senusret]

We are trying out Mumble compared to Vent, and so far I see pro's and con's.

But really to compare them I need to get the permissions set up and all that stuff. I am finding this very confusing in Mumble. I see it has access tokens, which basically make it work like Vent if I understand it - password protected channels, right?

But then you can set up a more robust permission system more like Teamspeak, where users are in groups and that determines their permissions in various channels. This is the part that is totally throwing me off. I found the documentation on the sourceforge site to be .. well, not enough for me. :P

Basically this is how I want my voice server to work:

1. Anybody with the info can log in and use the public guest channels.

2. Only guild members can access other channels. (Should I just have them require ppl to be registered, and then do manual registration?)

3. Only senior members and officers can drag players from guest chans into member chans.

4. Only officers can access the officers lounge.

5. Only chapter leads can do admin things to the server (new chans, etc.)

What I don't want to do is create a huge amount of work manually assigning every person to groups. So I feel I need some more automatic way at least for base member access. Manually assigning the more senior ranks is fine.

Thanks for any advice! I'm desperate to escape Vent but I need to find the right solution.

You have to set up groups by right clicking the top most channel or the default channel and chosing Edit . Create groups like Guild Members, Guild Officers etc.... People have to be logged in and registered users to be placed into the groups once the groups are set up you can then set permission on each channel so only the members of the groups you want can enter those channels.

My experience with Mumble is that it's has about 1-2 second less delay then Vent over all which when calling things out for raids can make a big difference.

Once you get it figured out you will never want to use Vent again. Hang in there.

[Deleted]

Moving to the computer section.

[Deleted]

Aye, Senusret has it down. I don't believe you can automatically add people to the 'member' group - unless you want to have a public channel, that needs a logon only, then the guild channel that requires an access token (for guildies), then make your more senior positions user groups.

I think that'd do what you're after.

[Senusret]

This will help scroll down to the ACL section and read it. Remove the spaces I can't post links yet.

http: //mumble.sourceforge.net / Murmurguide

[ashin]

Okay well that would explain one mystery - so you're only allowed to move someone to a group if they are connected to the server at the time?

What I was thinking for my main member group was just to have that be Registered users. So if you haven't registered, public access only. If you register, then you are a Member. So I would have to turn off letting users automatically self register.

Can you make it so registration requires inputting a password? Otherwise how does it work if users can't self-register?

---------- Post added 2011-08-10 at 08:46 AM ----------

This will help scroll down to the ACL section and read it. Remove the spaces I can't post links yet.
http: //mumble.sourceforge.net / Murmurguide

Actually that was much more clear than the main documentation on ACL's. I think I'm understanding it better now, thanks.

Do you think given my situation I should just use a token for member access? I was kind of trying to avoid them since it seems clumsier to change passwords periodically, etc.

---------- Post added 2011-08-10 at 08:49 AM ----------

Random additional question - where is the permission for whether someone can set a priority speaker or not?