![\"\"](\"https:\/\/trueconf.com\/blog\/wp-content\/uploads\/2021\/10\/2021-10-26_110209.png\" "\\"\\"")
<\/a><\/p>\nWarning!<\/p>\n
Please note that Jitsi Meet cannot be used as a full-fledged video conferencing platform. It is a free solution designed to demonstrate capabilities of 8×8’s cloud-based service. Jitsi developers do not plan to add enterprise-grade capabilities into their product, while the implementation of such essential business features as Active Directory\/LDAP integration, NAT traversal, SIP support, conference recording, etc. requires installation and setup of additional plugins and software packages. Additionally, Jitsi does not provide a number of basic features, such as meeting scheduling (all Jitsi meetings are in fact virtual rooms).<\/p>\n
Finally, Jitsi Meet installation and maintenance requires advanced programming and Linux admin skills.<\/p>\n<\/div>\n
Compare Jitsi with TrueConf Server on-premises video collaboration platform<\/a><\/p>\n Do you want to deploy Jitsi Meet? You’ve come to the right place! Read this guide to learn how to install and set it up.<\/p>\n The following packages are required for Jitsi Meet installation:<\/p>\n Below you can find the list of ports that you will need to open in your operating system or forward to an external network:<\/p>\n Jitsi Meet can be deployed on Debian\/Ubuntu and openSUSE. For example, in this article we will install Jitsi Meet on Debian 10<\/b>.<\/p>\n Jicofo<\/b> is an XMPP component. It’s a process responsible for connecting client apps to video meetings. During conferences, it can send invitations, perform load balancing when using multiple XMPP servers, etc. Jicofo has its own HTTP API Jitsi Videobridge<\/b> is a key component of the system. When transmitting video and audio between the participants, it acts as an intermediary, which means it performs RTP\/RTCP termination and sets the bitrate limits in both directions for each client. Jitsi Videobridge contains its own HTTP API ( Based on the Simulcast<\/a> architecture, Jitsi Videobridge is not responsible for transcoding and consumes relatively few CPU resources.However, Simulcast significantly increases the client-side load as compared to other architectures.<\/p>\n Several video bridges can be connected to the Jitsi videoconferencing system with each new conference assigned to one of them.<\/p>\n Jigasi<\/b> – external extension designed for participating in Jitsi conferences via SIP telephony (a separate extension required).<\/p>\n Jibri<\/b> is a set of tools for recording and\/or streaming a meeting hosted on Jitsi Meet. It works by launching a Chrome instance rendered in a virtual framebuffer and capturing and encoding the output with ffmpeg. It is intended to be run on a separate machine (or a virtual machine), with no other apps using the video or audio devices. One Jibri supports only one recording at the same time.<\/p>\n Prosody<\/b> is a cross-platform XMPP server written in Lua.<\/p>\n 2. Install the required packages:<\/p>\n For correct operation of Jitsi Meet, the system host name should correspond with the domain name which will be used for your Jitsi Meet instance.<\/p>\n 3. Add the same domain name to the \/etc\/hosts \u00a0file:<\/p>\n where x.x.x.x.x<\/strong> is the public IP address of your server.<\/p>\n To connect users to your Jitsi Meet server instance you need to configure the firewall by opening the required ports with ufw. To do this, please run the commands below in the following sequence:<\/p>\n Check the status of the firewall with this command:<\/p>\n If these ports are open, you will see the following output:<\/p>\n 2. Add a link to to a stable repository:<\/p>\n Before the installation process, get a list of available packages from the Jitsi repository:<\/p>\n Install Jitsi Meet:<\/p>\n You will also be prompted to enter the host name of your Jitsi Meet instance. If you have a domain, you can use your domain name, for example myjitsi.example.org. Alternatively, you can enter the IP address of your computer (if it is static).<\/p>\n This host name will be used to configure the virtual host within Jitsi Meet, as well as to connect users to conferences.<\/p>\n You can generate a self-signed SSL certificate, or reject this option if you already have a commercial certificate and you are going to use it instead.<\/p>\n By default, Jitsi Meet is set up so that any user can connect to your server and create a conference. However, you can change this scenario and allow only authorized users to create conferences. In this case, when creating a new room Jitsi Meet will ask for username and password. In order to do it, you will need to edit the configuration files.<\/p>\n In the following examples the variable 2. Find the line This will limit the access of anonymous users to your platform and introduce mandatory authentication by username and password.<\/p>\n 3. Add the following section in the end of the file:<\/p>\n This allows anonymous users to join a conference created by an authenticated user on the server. The guest should know the unique conference address and password (if it is set).<\/p>\n 4. Open another file This data is necessary to indicate to Jitsi Meet which internal hostname should be used for unauthenticated guests.<\/p>\n After that, specify the domain that will be used to run Jicofo in the component settings. For conference facilities, Jicofo will only use registered domains.<\/p>\n To complete the configuration changes, add the following line to the file<\/p>\n Use the prosodyctl utility to create users:<\/p>\n Restart the systemd services to apply changes:<\/p>\n When creating a room in Jitsi Meet, you will now need to enter your username and password.<\/p>\nSystem requirements<\/h2>\n
\n
\n
sudo -V<\/code> command and install it using apt install sudo<\/code> as a root<\/b> user. If you would like to add a user with the username \u00a0user<\/code> to the sudo<\/code> group, use sudo usermod -a -G sudo user<\/code>.<\/div>\nJitsi Meet basic modules<\/h2>\n
\/about\/health<\/code> that allows checking Jicofo’s status.<\/p>\n\/colibri\/debug<\/code>) for monitoring.<\/p>\n<\/a>Step 1: Installing Additional Packages<\/h2>\n\n
sudo apt update<\/pre>\n
\n
sudo apt install apt-transport-https gnupg2 nginx-full curl ufw -y<\/pre>\n
<\/a><\/strong><\/p>\nStep 2: Setting up a domain name<\/h2>\n
\n
myjitsi.example.org<\/code>.<\/li>\nsudo hostnamectl set-hostname myjitsi.example.org<\/pre>\n
<\/a><\/strong><\/p>\n127.0.0.1 localhost\r\n\r\nx.x.x.x myjitsi.example.org<\/pre>\n
Step 3: Configuring the firewall<\/h2>\n
sudo ufw allow 80\/tcp\r\n\r\nsudo ufw allow 443\/tcp\r\n\r\nsudo ufw allow 10000\/udp\r\n\r\nsudo ufw allow 22\/tcp\r\n\r\nsudo ufw enable<\/pre>\n
sudo ufw status verbose<\/pre>\n
Status: active\r\n\r\nTo \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 Action\u00a0 \u00a0 \u00a0 From\r\n\r\n-- \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 ------\u00a0 \u00a0 \u00a0 ----\r\n\r\n22\/tcp \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 ALLOW \u00a0 \u00a0 \u00a0 Anywhere\r\n\r\n80\/tcp \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 ALLOW \u00a0 \u00a0 \u00a0 Anywhere\r\n\r\n443\/tcp\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 ALLOW \u00a0 \u00a0 \u00a0 Anywhere\r\n\r\n10000\/udp\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 ALLOW \u00a0 \u00a0 \u00a0 Anywhere\r\n\r\n22\/tcp (v6)\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 ALLOW \u00a0 \u00a0 \u00a0 Anywhere (v6)\r\n\r\n80\/tcp (v6)\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 ALLOW \u00a0 \u00a0 \u00a0 Anywhere (v6)\r\n\r\n443\/tcp (v6) \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 ALLOW \u00a0 \u00a0 \u00a0 Anywhere (v6)\r\n\r\n10000\/udp (v6) \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 ALLOW \u00a0 \u00a0 \u00a0 Anywhere (v6)<\/pre>\n
Step 4: Adding the Jitsi package to the repository list<\/h2>\n
\n
curl https:\/\/download.jitsi.org\/jitsi-key.gpg.key | sudo sh -c 'gpg --dearmor > \/usr\/share\/keyrings\/jitsi-keyring.gpg'<\/pre>\n
echo 'deb [signed-by=\/usr\/share\/keyrings\/jitsi-keyring.gpg] https:\/\/download.jitsi.org stable\/' | sudo tee \/etc\/apt\/sources.list.d\/jitsi-stable.list > \/dev\/null<\/pre>\n
Step 5: Installing Jitsi Meet<\/h2>\n
sudo apt update<\/pre>\n
apt install jitsi-meet<\/pre>\n
<\/a><\/strong><\/p>\n<\/a><\/strong><\/p>\nStep 6: User authentication<\/h2>\n
your_hostname<\/code> will be used instead of the domain name.<\/p>\nActivate mandatory authentication<\/h3>\n
\n
\/etc\/prosody\/conf.avail\/[your_hostname].cfg.lua<\/code><\/li>\n<\/ol>\nauthentication = \"anonymous\"<\/code> \u00a0\u00a0in the VirtualHost \"[your_hostname]\"<\/code> block and replace it with the following line:<\/p>\nauthentication = \"internal_hashed\"<\/pre>\n
...\r\n\r\nVirtualHost \"guest.your_hostname\"\r\n\r\n\u00a0\u00a0\u00a0\u00a0authentication = \"anonymous\"\r\n\r\n\u00a0\u00a0\u00a0\u00a0c2s_require_encryption = false<\/pre>\n
etc\/jitsi\/meet\/your_hostname-config.js<\/code> in a text editor and uncomment the line \/\/ anonymousdomain: 'guest.example.com'<\/code>, replace \u00a0guest.example.com<\/code> with your real Jitsi Meet hostname.<\/p>\n\/etc\/jitsi\/jicofo\/sip-communicator.properties\r\n\r\norg.jitsi.jicofo.auth.URL=XMPP:your_hostname<\/pre>\n
Creating user accounts<\/h3>\n
sudo prosodyctl register <username> your_hostname <password><\/pre>\n
sudo systemctl restart jitsi-videobridge2 prosody jicofo<\/pre>\n