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. In this case, you might have issues with your calls and video.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. If your network does not have any NAT, Jitsi cannot use the local coturn server to determine the IP it should advertise to the users. You will need to edit the file name field in the UI before pressing "Choose File" button when selecting the certificates. If your fqdn was, your filenames would need to be and. These can be entered in the installer UI. Example:įurther, for the jitsi_fqdn, you will need to provide. Should be a yaml list of server:port entries. stun_servers: Needed if you don't setup coturn using the installer.timezone: Europe/Paris # The timezone in TZ format. ![]() helm_override_values: # if needed, to override helm settings automatically set by the installer For Helm values that can be overriden, see For environment variables that can be passed in via Helm overrides, see.jvb_auth_password: # a secret internal password for jvb.jicofo_component_secret: # a secret internal password for jicofo component.jicofo_auth_password: # a secret internal password for jicofo auth.It must resolve to the public-facing IP of the VM. jitsi_fqdn: The access address to jitsi.Jitsiįrom the Installer's Integrations page, click "Install" under "Jitsi".įor the jitsi.yml presented by the installer, edit the file and ensure the following values are set: You will need to have these certificate files in place before running the installer. crt/.key PEM encoded certificate for this fqdn. Please find your ~/.element-enterprise-server/config directory and create a directory called ~/.element-enterprise-server/config/legacy/certs under which to put a. max_port: The maximum UDP Port used by coturn for relaying UDP Packets, in range 32769-65535įurther, for the coturn_fqdn, you will need to provide certificates for the installer outside of the GUI.min_port: The minimal UDP Port used by coturn for relaying UDP Packets, in range 32769-65535.shared_secret: A random value, you can generate it with pwgen 32.coturn_fqdn: The access address to coturn.Coturnįrom the Installer's Integrations page, click "Install" under "Coturn".įor the coturn.yml presented by the installer, edit the file and ensure the following values are set: You must not use host_aliases for these hosts to resolve to the private IP locally on your setup. The jitsi and coturn domain names must resolve to the VM access IP. You will also have to allow the following port range, depending on the settings you define in the installer (see below) : ![]() You will have to open the following ports to your microk8s host (or k8s cluster) to enable coturn and jitsi : Configure the Installer to install Jitsi and TURN Prerequisites Firewall
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |