The second machine, which will only host a standalone videobridge, will be named BRIDGE. In the following, we will denote the main machine on which Jitsi runs, as MAIN. Hence, we thought it would be valuable to take another, hopefully simple and understandable stab at explaining this task to the community. While there is a guide in the Jitsi Wiki and a video that explains how to do it, many people still struggle ( 1, 2) to get this set up successfully. The best approach is to deploy the second videobridge on a new instance to avoid running into CPU limitations on the main machine. Jitsi can then distribute the load and should be able to host more than 100 people in a meeting. One solution is to add a second videobridge to the Jitsi instance. The limiting factor appears to be the “videobridge”. When browsing the load capabilities of a single Jitsi instance, we found that the stock setup begins to experience some challenges at around 35 people and fails at around 70 people. The ChallengeĬynkra actively supports the local Zurich R User Group.įor one of their recent meetings, about 100 people RSVP’ed. There are many different ways to install and run Jitsi on a machine.Ī popular choice in the DevOps space is to use Docker via docker-compose, which was the method used in our scenario.Īt cynkra, while we have been running our own Jitsi instance quite happily for some months, there was a slightly challenging task coming up: hosting a virtual meeting for approximately 100 participants. sudo nano /etc/jitsi/meet/Īnonymousdomain: ' Meet is a self-hosted Free and Open-Source Software (FOSS) video conferencing solution.ĭuring the recent COVID-19 pandemic, the project became quite popular, and many companies decided to host their own Jitsi instance. You will never enter it into a browser or need to create a DNS record for it. hostname is only used internally by Jitsi Meet. The next configuration allows anonymous users to join conference rooms that were created by an authenticated user. #ldap_tls_cacert_file: /etc/ssl/certs/ca-certificates.crt # for tls change ldap_servers to ldaps:// Ldap_bind_dn: cn=Administrator,cn=Users,dc=foo,dc=bar Ldap_search_base: dc=my,dc=search,dc=base URL=XMPP:Ĭreate users manually prosodyctl register įor a few user is is ok to create them manually but for many users you need something like ldap: sudo apt install sasl2-bin libsasl2-modules-ldap lua-cyrussasl Sudo nano /etc/jitsi/jicofo/sip-communicator.properties With this configuration all users need to authenticate to use Jitsi. For a publicly accessible server this is not what we want. The default config allow any user to start meetings without authentication. The you need to NAT the ports 443 4443 10000 from externat ip to the server. nano /etc/jitsi/videobridge/sip-communicator.properties If the installation is behind NAT jitsi-videobridge should configure jitsi-videobridge in order for it to be accessible from outside. Sudo /usr/share/jitsi-meet/scripts/install-letsencrypt-cert.sh If you want to use letsencrypt select self-signed the install certboot and use jitsi’s script like this: sudo add-apt-repository ppa:certbot/certbot For this demo I will use the self-signed option. Then you will be shown a new dialog box that asks if you want Jitsi to create and use a self-signed TLS certificate or use an existing one. Sudo tee /etc/apt//jitsi-stable.list > /dev/nullĭuring the installation of jitsi-meet you will be prompted to enter the domain name. Sudo sh -c 'gpg -dearmor > /usr/share/keyrings/jitsi-keyring.gpg'Įcho 'deb stable/' | \ In this step, you will change the system’s hostname to match the domain name that you intend to use for your Jitsi Meet instance. Jitsi is state-of-the art video conferencing software that you can self-host or simply use at. In this post I will show you how you can install Jitsi meet on your server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |