Main view of Mumble
|
|
Original author(s) | Thorvald Natvig |
---|---|
Developer(s) | Various |
Initial release | 2005 |
Stable release |
1.2.19 / January 27, 2017
|
Repository | github |
Written in | C++ |
Operating system | Android, iOS, Linux, macOS, Microsoft Windows |
Platform | Qt |
Type | VoIP client and server |
License | New BSD license |
Website |
Mumble is a voice over IP (VoIP) application primarily designed for use by gamers and is similar to programs such as TeamSpeak.
Mumble uses a client–server architecture which allows users to talk to each other via the same server. It has a very simple administrative interface and features high sound quality and low latency. All communication is encrypted to ensure user privacy.
Mumble is free and open-source software, is cross-platform, and is released under the terms of the new BSD license.
A Mumble server (called Murmur) has a root channel and a hierarchical tree of channels beneath it. Users can temporarily connect channels to create larger virtual channels. This is useful during larger events where a small group of users may be chatting in a channel, but are linked to a common channel with other users to hear announcements. It also matches team-based first-person shooter (FPS) games. Each channel has an associated set of groups and access control lists which control user permissions. The system supports many usage scenarios, at the cost of added configuration complexity.
Mumble uses the low-latency audio codec Opus as of version 1.2.4, the codec that succeeds the previous defaults Speex and CELT. This and the rest of Mumble's design allow for low-latency communication, meaning a shorter delay between when something is said on one end and when it's heard on the other. Mumble also incorporates echo cancellation to reduce echo when using speakers or poor quality sound hardware.
Mumble connects to a server via a TLS control channel, with the audio travelling via UDP encrypted with AES in OCB mode. As of 1.2.9 Mumble now prefers ECDHE + AES-GCM cipher suites if possible, providing Perfect Forward Secrecy. While password authentication for users is supported, since 1.2.0 it is typically eschewed in favor of strong authentication in the form of public key certificates.