b39e5968bf
* fix(SDP): Add missing msid for p2p sources.
* fix(TPC): Don't convert plan-b<->unified-plan SDPs for p2p.
* squash: Implement review comments.
* fix(JingleSessionPC): Do not try to re-use inactive mid for new remote ssrcs. The direction was marked as 'inactive' only on Firefox as Safari had audio issues when an inactive mid is re-used. Chrome (in unified-plan) needs the direction of the mid in remote desc to be set to 'inactive' for a 'removetrack' to be fired on the associated media stream whenever a remote source is removed.
* fix(SDP): Drop SSRCs whenever the transceiver direction is 'inactive' or 'recvonly'. This is needed only for JVB connections. Add unit tests for LocalSdpMunger.
* fix: Ignore startAudioMuted/startVideoMuted for p2p. The tracks will not be added when the call switches from jvb to p2p for an endpoint that joins muted by focus.
* fix(RTC): Do not suppress the source updates on Firefox. If the msid attribute is missing, then remove the ssrc from the transformed description so that a source-remove is signaled to Jicofo. This happens when the direction of the transceiver (or m-line) is set to 'inactive' or 'recvonly' on Firefox. Not signaling these source updates creates issues with remote track handling on the other endpoints in the call.
* fix(RTC): Set transceiver direction after RTCRtpSender#replaceTrack. This fixes the issue where TRACK_REMOVED event is not fired when a remote track is removed from the peerconnection. Fixes https://github.com/jitsi/lib-jitsi-meet/issues/1612 and https://github.com/jitsi/jitsi-meet/issues/8482.
|
||
---|---|---|
.github | ||
android | ||
connection_optimization | ||
css | ||
debian | ||
doc | ||
flow-typed/npm | ||
fonts | ||
images | ||
ios | ||
lang | ||
modules | ||
patches | ||
react | ||
resources | ||
service/UI | ||
sounds | ||
static | ||
twa | ||
.buckconfig | ||
.editorconfig | ||
.eslintignore | ||
.eslintrc.js | ||
.flowconfig | ||
.gitattributes | ||
.gitignore | ||
.npmrc | ||
.travis.yml | ||
.watchmanconfig | ||
CONTRIBUTING.md | ||
LICENSE | ||
Makefile | ||
README.md | ||
SECURITY.md | ||
analytics-ga.js | ||
app.js | ||
babel.config.js | ||
base.html | ||
body.html | ||
conference.js | ||
config.js | ||
connection.js | ||
favicon.ico | ||
head.html | ||
index.android.js | ||
index.html | ||
index.ios.js | ||
interface_config.js | ||
logging_config.js | ||
manifest.json | ||
metro.config.js | ||
package-lock.json | ||
package.json | ||
plugin.head.html | ||
pwa-worker.js | ||
title.html | ||
webpack.config.js |
README.md
Jitsi Meet - Secure, Simple and Scalable Video Conferences
Jitsi Meet is an open-source (Apache) WebRTC JavaScript application that uses Jitsi Videobridge to provide high quality, secure and scalable video conferences. Jitsi Meet in action can be seen at here at the session #482 of the VoIP Users Conference.
The Jitsi Meet client runs in your browser, without installing anything on your computer. You can try it out at https://meet.jit.si.
Jitsi Meet allows for very efficient collaboration. Users can stream their desktop or only some windows. It also supports shared document editing with Etherpad.
NOTE: If you are looking for Jitsi as a Service (JaaS) please start here.
Installation
On the client side, no installation is necessary. You just point your browser to the URL of your deployment. This section is about installing a Jitsi Meet suite on your server and hosting your own conferencing service.
Installing Jitsi Meet is a simple experience. For Debian-based system, following the quick install document, which uses the package system. You can also see a demonstration of the process in this tutorial video.
For other systems, or if you wish to install all components manually, see the detailed manual installation instructions.
Installation with Docker is also available. Please see the instruction.
Download
Latest stable release |
---|
You can download Debian/Ubuntu binaries:
You can download source archives (produced by make source-package
):
Mobile apps
You can also sign up for our open beta testing here:
Release notes
Release notes for Jitsi Meet are maintained on this repository.
Development
For web development see here, and for mobile see here.
Contributing
If you are looking to contribute to Jitsi Meet, first of all, thank you! Please see our guidelines for contributing.
Embedding in external applications
Jitsi Meet provides a very flexible way of embedding in external applications by using the Jitsi Meet API.
Security
The security section here was starting to feel a bit too succinct for the complexity of the topic, so we created a post that covers the topic much more broadly here: https://jitsi.org/security
The section on end-to-end encryption in that document is likely going to be one of the key points of interest: https://jitsi.org/security/#e2ee
Security issues
For information on reporting security vulnerabilities in Jitsi Meet, see SECURITY.md.
Acknowledgements
Jitsi Meet started out as a sample conferencing application using Jitsi Videobridge. It was originally developed by ESTOS' developer Philipp Hancke who then contributed it to the community where development continues with joint forces!