| 1 | # Mumble |
| 2 | |
| 3 | - Status: ??? |
| 4 | - Maintainers: ??? |
| 5 | - Features: ??? |
| 6 | |
| 7 | ## Configuration |
| 8 | |
| 9 | **Basic configuration example:** |
| 10 | |
| 11 | ```toml |
| 12 | [mumble.mymumble] |
| 13 | Server = "mumble.yourdomain.me:64738" |
| 14 | Nick = "matterbridge" |
| 15 | # Use `""` if the server doesn't have a password |
| 16 | Password = "serverpasswordhere" |
| 17 | # Uncomment for client certificates |
| 18 | #TLSClientCertificate="mumble.crt" |
| 19 | #TLSClientKey="mumble.key" |
| 20 | # Optional custom TLS certificate |
| 21 | TLSCACertificate=mumble-ca.crt |
| 22 | ``` |
| 23 | |
| 24 | ## FAQ |
| 25 | |
| 26 | ### How to generate a client certificate to reserve a nickname? |
| 27 | |
| 28 | Self-signed TLS client certificate + private key used to connect to |
| 29 | Mumble. This is required if you want to register the matterbridge |
| 30 | user on your Mumble server, so its nick becomes reserved. |
| 31 | You can generate a keypair using e.g. |
| 32 | |
| 33 | openssl req -x509 -newkey rsa:2048 -nodes -days 10000 \ |
| 34 | -keyout mumble.key -out mumble.crt |
| 35 | |
| 36 | To actually register the matterbridege user, connect to Mumble as an |
| 37 | admin, right click on the user and click "Register". |
| 38 | |
