forked from hacc/haccfiles
stuebinm
41d82ae436
we decided to: - get rid of unused packages - simpify the directory layout since we only have one host anyways - move our docs (such as they are) in-tree
40 lines
1.3 KiB
Markdown
40 lines
1.3 KiB
Markdown
+++
|
|
title = "mumble"
|
|
taxonomies.categories = [ "mumble" ]
|
|
+++
|
|
|
|
|
|
[offical Docmuentation](https://wiki.mumble.info/wiki/Main_Page)
|
|
|
|
Mumble's server is called murmur, but the naming is inconsistent. Sometimes
|
|
it's also just called mumble server.
|
|
|
|
# Usage
|
|
|
|
## registration
|
|
Users need to be registered to join any other channel than public.
|
|
An already registered user has to register them with the server.
|
|
1. right click on the username
|
|
2. choose register in the menu. Done.
|
|
|
|
## restricted channels
|
|
Every channel in the hacc category except for plenum can only be accessed by
|
|
members of the hacc group.
|
|
|
|
## adding users to a group
|
|
Only admins can edit groups, and only registered users can be added to groups.
|
|
1. right click on the Root channel
|
|
2. select Edit...
|
|
2. In Groups select $groupname
|
|
3. make the change you want to make
|
|
4. click "OK"
|
|
|
|
# Config details
|
|
- the server is not registered with mumble & not on the public server list
|
|
- the bitrate is set to 128kb/s; otherwise the client would complain that the
|
|
server bitrate is less then the configured (default) in its local settings
|
|
|
|
# Hacks
|
|
- murmur needs a TLS cert, which we get via the ACME module
|
|
- there's a funny group setup so that hopefully murmurd can read the cert
|
|
- this seems to work fine now, but was some source of trouble in the past
|