- #MUMBLE SERVER HOSTING CODE#
- #MUMBLE SERVER HOSTING PASSWORD#
- #MUMBLE SERVER HOSTING LICENSE#
- #MUMBLE SERVER HOSTING FREE#
- #MUMBLE SERVER HOSTING WINDOWS#
If you are a commercial provider, please comment in the discussion section (even if you agree, it helps to know we're on the right track), or add new sections. I'll note down what I can imagine commercial hosting providers would like to see implemented in Murmur before they start offering it as a service. Requirements for Murmur for adoption by commercial providers Note that if you just use our binaries from sourceforge, you don't need to worry about any of this. The owners of these packages and patents have all kindly granted Mumble a license, but that only covers open source distribution.
#MUMBLE SERVER HOSTING LICENSE#
You will also need commercial licenses for the packages Mumble uses, namely Qt and Ice, as well as a patent license for OCB.
#MUMBLE SERVER HOSTING CODE#
If you want to repackage and rebrand the client without also distributing its source code, the Mumble source code is BSD licensed, which allows you to do this. You are selling a service, not a program.
#MUMBLE SERVER HOSTING FREE#
Murmur and Mumble is BSD and GPL licensed, which means that much like the Linux kernel, you are free to use it in commercial hosting without royalties. Note that these are absolute worst-case scenarios, and the average bandwidth use is around 20-30 kbit/s during speech, multiplied by the number of listeners it is only possibly in a real world scenario for at most two people to be talking at the same time and still understand what they are saying.Īs one data point you can take a look at silencerru's post about the resource usage for a ~800 user server in the forum. If all 10 users speak at once, each stream has to be replicated 9 times, for a total of 63kbit/s*9*10=5.67 Mbit/s. In other words, a server with 10 users and 1 user speaking will need to replicate the datastream 9 times, for a total of 63*9=567kbit/s outgoing bandwidth. However, this is the max bandwidth, and the recommended bandwidth (that has a very unnoticeable quality reduction for normal speech) is 63kbit/s.
Mumble uses CELT, and using the highest quality and lowest latency, the peak bandwidth is 134kbit/s per speaker per listener (with IP and UDP overhead). We do see quite a few context switches though, so quality network cards and infrastructure capable of handling high packet load are recommended on servers hosting a big number of clients. Since only minimal processing, as required for cryptography and "visibility checks" between users, is done serverside, we were not able to push even 1% of actual CPU usage with 4 users on a Xeon 3.4Ghz.
#MUMBLE SERVER HOSTING WINDOWS#
Our internal testserver runs on Linux, and a binary version for Windows is included in the mumble installer.īased on data from our testserver, murmur will use about 40 MB of virtual memory, of which about 4 MB are resident in physical memory. At the moment, that is "most" UNIXes, Windows and MacOSX. Murmur runs on any operating system where Qt can compile.
Server page live updates with users in server as well as server timer expiration You mayĪlso extend the server duration up to 3 times!Ĭlicking direct link opens Mumble and connects to server
The server page also lists users in room and displays the expiration countdown.
#MUMBLE SERVER HOSTING PASSWORD#
Set a password Password protected servers are required as servers are reused.Ĭonnection Details Share the connection details, or use the copy feature to copy/paste the credentialsĭirectly.
0 kommentar(er)
