Official Mumble VoIP Forums

Linking Channels for partial Listen Ability

How to do...
Hello world!

I am trying to set a mumble server up and I am having a bit of trouble getting my ACLs / Linked channels to work the way I'd like them too.

I'd like the channels to look something like this:
* Root Channel
L Red Team
L Blue Team

Where people in the Root channel can talk and listen to both Red and Blue team, but Red and Blue team can't hear each other. The links I've been doing seem to make them all listen to each other. I've seen tutorials for similar things but I can't seem to apply them to my use case.

Ideally I wouldn't need to assign groups to specific users manually, as there will be users coming in and out and they won't be registered.

Thanks for your help!
Link red and blue to the parent channel (so all three are linked), and then in the red and blue channels edit the ACL: Add a

Code: Select all

@sub,1
group, and deny speak.

The @sub group can be used to specify ACL rules for channels of a common parent, in this case 1 above the channels in question.

See also the @sub description at https://wiki.mumble.info/wiki/ACL_and_G ... 0sub_group
kissaki wrote:
Sat Jul 14, 2018 6:41 pm
Link red and blue to the parent channel (so all three are linked), and then in the red and blue channels edit the ACL: Add a

Code: Select all

@sub,1
group, and deny speak.

The @sub group can be used to specify ACL rules for channels of a common parent, in this case 1 above the channels in question.

See also the @sub description at https://wiki.mumble.info/wiki/ACL_and_G ... 0sub_group
Hi again Kissaki! Thank you for the reply!

I followed your steps but I'm still having some troubles where I can still hear both teams. I setup the ACLs like this for Red and Blue: https://i.imgur.com/DojCnQ7.png. I must be doing something wrong, but between the wiki and my googling I can't for the life of me figure out what it is.
Reading the page I linked:
First of all, this ACL will be evaluated in the context of the defining channel, since the group starts with ~.
So I guess you'll have to make it a @~sub instead of @sub.

I'm a little confused of how it is interpreted without it though.