![]() On MAIN, in docker logs jitsi_jicofo_1, an entry should appear denoting that a new videobridge was successfully connected. The videobridge should successfully connect to. Run docker-compose up and observe what happens. env are the same as on MAIN, otherwise the authentication will fail. Make sure that JVB_AUTH_USER and JVB_AUTH_PASSWORD in. The videobridge will later connect to all services on MAIN. In docker-compose.yml, remove all services besides jvb. To the prosody section in docker-compose.yml and ensuring that the port is opened in the firewall ( ufw allow 5222). To be able to connect to the XMPP server (managed by prosody) on MAIN from BRIDGE (details in point 4 below), port 5222 needs to be exported to the public. An installation on the host system will also work.Īt this point we assume that you already have installed Jitsi with SSL support at a fictitious domain. The first step is to create a working installation on MAIN, following the official docker guide from the Jitsi developers. The second machine, which will only host a standalone videobridge, will be named BRIDGE. In the following we will denote the main machine which Jitsi runs on 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 about it, many people struggle ( 1, 2) to get this set up successfully. The best approach to do this 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 is said to be the “videobridge”. When browsing the load capabilities of a single Jitsi instance, one finds that the stock setup gets into trouble starting at around 35 people and will go down 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. While at cynkra 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. 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. Jitsi 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. ![]()
0 Comments
Leave a Reply. |