mirror of
https://github.com/mumble-voip/mumble.git
synced 2026-03-03 00:46:56 -05:00
Question about Restricting Channel Visibility in Mumble #3092
Labels
No labels
GlobalShortcuts
Hacktoberfest
accessibility
acl
asio
audio
bonjour
bsd
bug
build
certificate
ci
client
code
documentation
external-bug
feature-request
gRPC
github
good first issue
help wanted
help-needed
ice
installer
linux
macOS
needs-ckeck-with-latest-version
needs-more-input
overlay
positional audio
priority/P0 - Blocker
priority/P1 - Critical
priority/P2 - Important
priority/P3 - Somewhat important
priority/P4 - Low
public-server-registration
qt
recording
release-management
server
stale-no-response
stale-support
support
task
test
theme
translation
triage
ui
windows
wontfix
x64
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/mumble-mumble-voip#3092
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Nablusi on GitHub (Jan 10, 2026).
The issue
I am currently integrating Mumble with ICE for a multi-company setup. I want to ensure that users from one company can only see their own company channel and cannot see channels of other companies.
Could you please let me know if there is a way to restrict channel visibility so that a user only sees the channels assigned to their company?
I don't want the users to see the root channel or any other channel except their company channel
Mumble version
1.4
Mumble component
Server
OS
Windows
Additional information
No response
@Krzmbrzl commented on GitHub (Jan 10, 2026):
There is no way to do that. If you want different sets of users to only see specific channels, I recommend using different servers in the first place.
Related: #3057
@Nablusi commented on GitHub (Jan 11, 2026):
@Krzmbrzl
I tried to create five servers, each with its own port.
Here are the Docker commands I ran, which I repeated for each server, changing the port accordingly
its creates two files
The issue is one server is running and the the other one is not
here is result
Can you help me figure out the issue? Like why is just one server is running
@Krzmbrzl commented on GitHub (Jan 11, 2026):
Are all servers using the same Ice endpoint (from the config file)? That could be the issue as only one of the serves will succeed to create the endpoint.
However, you don't have to spin up multiple server instances. You can use a single instance to host multiple virtual Mumble servers. You an use Ice to spin up and control more servers as needed
@Nablusi commented on GitHub (Jan 11, 2026):
@Krzmbrzl
The issue I’m facing is not with server creation, but with accessing or testing the other servers. I always end up entering only the first company’s server.
maybe I am missing something, if u could help with this issue
@Krzmbrzl commented on GitHub (Jan 11, 2026):
The individual servers will be served at consecutive ports (by default). So if the first virtual server is configured to bind to port
64738, the next virtual server should be on64739, then64740and so on. If one of those ports is already taken, the next port will be attempted. You can check the respective virtual server's log - it should contain a message telling you which port it has bound to (the port should also be queriable via Ice, I believe)@Nablusi commented on GitHub (Jan 12, 2026):
@Krzmbrzl
I believe that, in my case, the best approach is to build virtual servers for each company. I have already built a backend to support this architecture.
Assuming a scenario with 100 companies and approximately 1,000 active users, do you know how I can calculate the required resource consumption (CPU, memory, network, and storage)? Additionally, is there any official documentation that explains how to calculate these requirements theoretically?
@Krzmbrzl commented on GitHub (Jan 12, 2026):
No
My guess would be to use whatever a single server of that size needs and multiply it by 100. However, I don't think there is a general way to compute resource usage of a server (it depends hugely on how exactly you use the server).
That being said, I have doubts that hosting all 100 servers on a single machine (which is what you'd need to do if you wanted them all to be virtual servers of a single Mumble instance) with 1000 users each will work out great. If all users are speaking you have voice packets of ~100k people, which will be an enormous bandwidth (and processing) requirement…