Discussion related to the Meet UI, Meet features, Meet use cases, the meet.jit.si app, and basic usage of Jitsi products intended for end users. These discussions will tend to be less technical than those in Install & Config and Developers. Jitsi Meet is composed of several components which work together for delivering the best video conferences, as you are used to already. When it comes to deploying these to production, there are, of course, many. Jitsi Meet is a fully encrypted, 100% open source video conferencing solution that you can use all day, every day, for free — with no account needed. What else can you do with Jitsi Meet? Share your desktop, presentations, and more Invite users to a conference via a simple, custom URL. Jitsi Meet is a fully encrypted, 100% open source video conferencing solution that you can use all day, every day, for free — with no account needed. What else can you do with Jitsi Meet? Share your desktop, presentations, and more Invite users to a conference via a simple, custom URL. Jitsi Meet is translated to many languages thanks the our community’s help. In the past few weeks we have seen many contributions to our translations, both improving the existing ones and bringing in new languages. Thank you to everyone who contributed!
One-to-one calls should avoid going through the JVB for optimal performance and for optimal resource usage. This is why we've added the peer-to-peer mode where the two participants connect directly to each other. Unfortunately, a direct connection is not always possible between the participants. In those cases you can use a TURN server to relay the traffic (n.b. the JVB does much more than just relay the traffic, so this is not the same as using the JVB to 'relay' the traffic).
This document describes how to enable TURN server support in one-to-one calls in Jitsi Meet, even though it gives some hints how to configure prosody and coTURN, it assumes a properly configured TURN server, and a properly configured XMPP server.
One way to configure TURN support in meet with a static configuration. You can simply fill out the
p2p.stunServers option with appropriate values, e.g.:
This technique doesn't require any special configuration on the XMPP server, but it exposes the credentials to your TURN server and other people can use your bandwidth freely, so while it's simple to implement, it's not recommended.
This draft describes a proposed standard REST API for obtaining access to TURN services via ephemeral (i.e. time-limited) credentials. These credentials are vend by a web service over HTTP, and then supplied to and checked by a TURN server using the standard TURN protocol. The usage of ephemeral credentials ensures that access to the TURN server can be controlled even if the credentials can be discovered by the user.
Jitsi Meet can fetch the TURN credentials from the XMPP server via XEP-0215. You can enable this functionality by setting
p2p.useStunTurn: true in config.js. By properly configuring a common shared secret on your TURN server and your XMPP server, the XMPP server can deliver appropriate credentials and TURN urls to Jitsi Meet. coTURN natively supports shared secret authentication (--use-auth-secret-) and in prosody, you can use the mod_turncredentials module.
Use TURN server on port 443
By default, TURN server listens on standard ports udp 3478 and tcp 5349(for tls connections).There are certain corporate networks which allow only tcp connections using port 443(https) and to coverthis kind of scenarios it is useful to have TURN server listening on port 443 for tls connections.Here is how to run nginx and TURN server on the same machine sharing port, for this you will need a seconddns for your turn domain pointing to the same machine (as a reference below we will use
- You need to enable the multiplexing based on that new dns. You need to create a file in
/etc/nginx/modules-available. If you are placing the file in
/etc/nginx/modules-availableyou need to add a symlink in
/etc/nginx/modules-enabled.The file content should be:
Make sure you edit the file and replace
jitsi-meet.example.com it your domain of deployment,
turn-jitsi-meet.example.com with the DNS you will use for the TURN server and
__your_public_ip__ with your public ip of the deployment.If you have more virtualhost make sure you add them here and do the port change and for them(the next step).
- Then go to /etc/nginx/site-available/your-conf and change your virtual host to listen on 4444 instead of 443.
- Next you need to make sure Prosody is advertising the correct DNS and port for the TURN server. You should edit the line using port
5349and make it look like (change port and address):
- Now you need to make sure the TURN server (coturn) uses trusted certificates here is how to request those fromLet's Encrypt, make sure you set correct values for the domain and email:
- After restarting prosody (systemctl restart prosody) you are good to go!
Jitsi is a set of open-source projects that allows you to easily build and deploy secure videoconferencing solutions. We are best known for our Jitsi Meet video conferencing platform, meet.jit.si where we host a Jitsi Meet instance that the community can use for totally free video conferences , and the Jitsi Videobridge that powers all of our multi-party video capabilities.
The easiest way is to go to meet.jit.si or download one of the mobile apps (Android or iOS).
If you prefer, you can also setup your own Jitsi Meet instance or embed a meet.jit.si room into your own website. See the FAQs below for more information on those options.
Yes. Jitsi is 100% open source and freely available to use and develop with. We also host and run meet.jit.si as a free service.
We have a bunch, but the most popular ones are:
- Jitsi Meet – Secure, Simple and Scalable Video Conferences that you use as a standalone app or embed in your web application
- Jitsi Videobridge – the media server engine (aka Selective Forwarding Unit (SFU)) that powers all of Jitsi’s multi-party video conferences
- Jigasi – a gateway service that connects SIP telephony to a Jitsi Videobridge conference
- Jibri – a broadcaster and recorder used for saving video call recordings and streaming to YouTube Live
- Jidesha – a Chrome and Firefox extension for screensharing
You can see all of our projects on our github page – https://github.com/jitsi
Jitsi Meet includes many features and we are constantly adding more. Some of the main ones are:
- Auto-view the active speaker or click on any attendee to see their video
- Android and iOS apps
- Text chatting (web only)
- Lock a room with a password
- Screen sharing (if jidesha is setup, only required in Chrome)
- Streaming a conference to YouTube live (if Jibri is configured)
- Shared text document based on Etherpad
- Raise/Lower your hand for attention
- Participant talk-time statistics
- Push-to-talk mode
- Play a YouTube video to all attendees call
- Audio-only option
- Telephone dial-in to a conference (if Jigasi is setup)
- Dial-out to a telephone participant (if Jigasi is setup)
- Integration in other apps / websites
Jitsi Meet also includes statistics and integrations features and a callstats.io integration to help developers. Make sure to use meet.jit.si to see the latest features.
Yes. The easiest way to record is to live stream your conference to YouTube and access the recording there. You can try this now on meet.jit.si. Self-installed Jitsi Meet deployments will need to setup Jibri to do this.
Yes, Jitsi offers a telephony interface that allows users to dial into a conference or for placing dial-out reminder calls. You can try this on meet.jit.si. Self-installed Jitsi Meet deployments will need to setup and configure Jigasi with a SIP provider to connect to the phone network.
We are fortunate that our friends at 8×8 fully fund the project. 8×8 uses Jitsi technology in products like Virtual Office. The open source community and meet.jit.si service help to make Jitsi better, which makes 8×8 products better, which helps to further fund Jitsi. This virtuous cycle has worked well in the past and should continue to for many years to come.
Setting up Jitsi Meet is a simple experience for those that are familiar with Unix installations. For Debian-based systems, we recommend 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.
Yes, Jitsi Meet has an External API that can be used to embed an existing Jits Meet instance into any webpage with just a few lines of code. Many of Meet’s options can be changed via configuration file. Web developers can even actively control the conference with a variety of commands and events. You can do this with your own self-installed instance or run it from meet.jit.si – no server installation required. See here for more on the Jitsi Meet External API.
Yes, Jitsi Meet can be compiled as an SDK and embedded into Android and iOS apps. You can find instructions on how to do that here:
Jitsi Meet Apk
Neither the immediate Jitsi team or 8×8 provide commercial support for Jitsi. Jitsi does enjoy a large developer community with many development shops and individuals that provide support and commercial development services. If you need paid help, we recommend you do a search or post a request on our Community Forum in the paid-word category: https://community.jitsi.org/c/users/paid-work
Jitsi Meet Meeting Planen
Jitsi Desktop, formerly known as the SIP Communicator and briefly known as just “Jitsi”, is a VoIP and instant messaging application. This was the Jitsi team’s first project that originated way back in 2003.
Jitsi’s video conferencing capabilities evolved out of this original project. Jitsi Desktop is no longer actively maintained by the Jitsi team under 8×8; but it is still maintained, by the community.
Jitsi Meet Vs Meet
Install ssl in xampp. The Jitsi Community Forum is best place to go for all kinds of discussion on Jitsi projects.