A video & audio conferencing app for Nextcloud
- 💬 Chat Nextcloud Talk comes with a simple text chat, allowing you to share or upload files from your Nextcloud Files app or local device and mentioning other participants.
- 👥 Private, group, public and password protected calls! Invite someone, a whole group or send a public link to invite to a call.
- 💻 Screen sharing! Share your screen with participants of your call. You just need to use Firefox version 66 (or newer), latest Edge or Chrome 72 (or newer, also possible using Chrome 49 with this Chrome extension).
- 🚀 Integration with other Nextcloud apps like Files, Calendar, User status, Dashboard, Flow, Contacts and Deck, with more to come.
- 🎡 We’re not reinventing the wheel! Based on the great simpleWebRTC library.
- 🌉 Sync with other chat solutions With Matterbridge being integrated in Talk, you can easily sync a lot of other chat solutions to Nextcloud Talk and vice-versa.
More in the works for the coming versions.
If you have suggestions or problems, please open an issue or contribute directly 🤓
| Browser | Compatible |
|---|---|
| Firefox | ✔️ 52 or later |
| Chrome/Chromium | ✔️ 49 or later |
| Opera | ✔️ 72 or later |
| Safari | ✔️ 13 or later |
| Edge | 🎤 Speakers are not promoted 🏷 Name changes while a call is on-going are not reflected |
Nextcloud Talk is really easy to install. You just need to enable the app from the Nextcloud App Store and everything will work out of the box.
There are some scenarios (users behind strict firewalls / symmetric NATs) where a TURN server is needed. That's a bit more tricky to install. You can find instructions in our documentation and the team behind the Nextcloud VM has developed a script which takes care of everything for you (vm-talk.sh). The script is tested on the recent Ubuntu Server LTS. Please keep in mind that it's developed for the VM specifically and any issues should be reported in that repository, not here.
Here's a short video on how it's done.
Talk works peer to peer, that is, each participant sends an end-to-end encrypted stream to every other participant and receives one stream per other participant. Bandwidth usage grows with the number of participants.
A single video stream currently uses about 1 Mbit/sec and the total required bandwidth can be calculated as follows:
1 Mbit/s * (participants - 1)
This means that in a call with 5 participants, each has to send and receive about 4 Mbit/sec. Given the asymmetric nature of most typical broadband connections, it's sending video that quickly becomes the bottleneck. Moreover, decoding all those video streams puts a big strain on the system of each participant.
To limit and CPU bandwidth usage, participants can disable video. This will drop the bandwidth use to audio only, about 50 kbit/sec (about 1/20th of the bandwidth of video), eliminating most decoding work. When all participants are on a fast network, a call with 20 people without video could be doable.
Still a call creates a load on the participants' browsers (decoding streams) and on the server as it handles signaling. This, for example, also has consequences for devices that support calls. Mobile device browsers will sooner run out of compute capacity and cause issues to the call. While we continuously work to optimize Talk for performance, there is still work to be done so it is not unlikely that the bottleneck will be there for the time being. We very much welcome help in optimization of calls!
To make sure a call can sustain the largest number of participants, make sure that:
- each participant has a fast upload and download.
- each participant has a fast enough system. This means:
- on a desktop/laptop system, a browser like Firefox or Chrome should be used. The WebRTC implementation in other browsers is often sub-par. On a laptop, the power cord should be plugged in - this often results in better CPU performance.
- on mobile devices, the Android/iOS apps should be used because mobile browsers will run out of computing power quickly.
- all participant disables their video streams.
With this setup, 20 users should be possible in a typical setup.
Nextcloud offers a partner product, the Talk High Performance Back-end, which deals with this scalability issue by including a Selective Forwarding Unit (SFU). Each participant sends one stream to the SFU which distributes it under the participants. This typically scales to 30-50 or even more active participants. Furthermore, the HPB setup also allows calls with hundreds of passive participants. With this number of participants is only limited by the bandwidth of the SFU setup. This is ideal for one-to-many streaming like webinars or remote teaching lessons.
The HPB also takes care of signaling, decreasing the load of many calls on the Talk server and optional SIP integration so users can dial in to calls by phone.
If you need to use Talk in an enterprise environment, contact our sales team for access to the Talk High Performance Back-end. See our website for more details and pricing.
- 🗂️ Simply clone this repository into the
appsfolder of your Nextcloud development instance. - 📦 Run
make dev-setupto install the dependencies. - 🏗️ Run
make build-js. - 🔌 Then activate it through the apps management. 🎉
- 📘 To build the docs locally, install mkdocs locally:
apt install mkdocs mkdocs-bootstrap.
We are also available on our public Talk team conversation, if you want to join the discussion.
- Disable camera until reboot:
sudo modprobe -r uvcvideo - Re-enable camera:
sudo modprobe uvcvideo - Send fake-stream (audio and video) in Firefox:
- Open
about:config - Search for
fake - Toggle
media.navigator.streams.faketo true
- Open
The API documentation is available on nextcloud-talk.readthedocs.io/.
In the Talk app we have one branch per Nextcloud server version. stable* branches of the app should always work with the same branch of the Nextcloud server.
This is only off close to releases of the server, to allow easier finishing of features, so we don't have to backport them.
10.0.0- Numeric milestones are settled and waiting for their release or some final polishing💛 Next Minor (20)- The next minor milestone is for issues/PR that go into the next Dot-Release for the given Nextcloud version (in the example 20 - e.g. 10.0.1)💚 Next Major (21)- The next major milestone is for issues/PR that go into the next feature release for the new Major Nextcloud version (as there are Minors for 20, this would be 21)💔 Backlog- The backlog milestone is assigned to all remaining issues
You can always pick a task of any of the milestones and we will help you to get it into the assigned milestone or also an earlier one if time permits. It's just a matter of having an overview and better visibility what we think should be worked on, but it's not exclusive.
For more information please see the guidelines for contributing to this repository.