The setup consists of multiple Jitsi videobridges which can be added and removed on demand as well as one control server which does the loadbalancing decisions.

Each server has at least 8vCPUs, 16GB RAM and 10GB disc space. But the most important thing is bandwidth so a 1Gbit/s link is necessary for smooth operation.

The more CPUs you have the better, also you need good network hardware as you can expect many pps.

We did some presentations about the setup you can find them at SlideShare.

If you want to ask us questions join our chat!

We installed the first instance as described on https://jitsi.org/downloads and stopped the videobridge there, because the first server should only act as a control server. If you only host a single instance skip the step of disabling the videobridge. Just set the settings, restart and be done.

Disable the videobridge:

# systemctl stop jitsi-videobridge.service
# systemctl mask jitsi-videobridge.service

Disable unnecessary and broken features on the control server: /etc/jitsi/meet/meet.ffmuc.net-config.js

defaultLanguage: 'de',
disableThirdPartyRequests: true,
p2p: { enabled: false },
enableLipSync: false

Jitsi instances balance based on metrics published by the videobridges to jicofo. To allow the videobridges to publish those metrics we need to change some settings in the prosody settings.

In the Admin section you need to add all the bridges. /etc/prosody/prosody.cfg.lua

admins = {
        "jvb1.meet.ffmuc.net",
        "jvb2.meet.ffmuc.net",
        "jvb3.meet.ffmuc.net"
}

As we want to scale beyond 1024 connections we also switch to epoll in prosody.cfg.lua.

-- for better scaling
-- https://prosody.im/doc/network_backend
network_backend = "epoll"

And as we want external videobridges we need to listen on the external interface and not just localhost:

component_interface = "0.0.0.0";

And you also need to assign a component to each videobridge in your site config. /etc/prosody/conf.d/meet.ffmuc.net.cfg.lua

Component "jvb1.meet.ffmuc.net"
    component_secret = "pass"
Component "jvb2.meet.ffmuc.net"
    component_secret = "pass"
Component "jvb3.meet.ffmuc.net"
    component_secret = "pass"

On those servers only the jitsi-videobridge needs to be installed. There is no need for any other jitsi component.

First you need to change /etc/jitsi/videobridge/config to fit your install.

# Jitsi Videobridge settings

# sets the XMPP domain (default: none)
JVB_HOSTNAME=meet.ffmuc.net

# sets the hostname of the XMPP server (default: domain if set, localhost otherwise)
JVB_HOST=meet.ffmuc.net

# sets the port of the XMPP server (default: 5275)
JVB_PORT=5347

# sets the shared secret used to authenticate to the XMPP server
JVB_SECRET=pass

# extra options to pass to the JVB daemon
JVB_OPTS="--subdomain=jvb1 --apis=rest,xmpp"


# adds java system props that are passed to jvb (default are for home and logging config file)
JAVA_SYS_PROPS="-Dnet.java.sip.communicator.SC_HOME_DIR_LOCATION=/etc/jitsi -Dnet.java.sip.communicator.SC_HOME_DIR_NAME=videobridge -Dnet.java.sip.communicator.SC_LOG_DIR_LOCATION=/var/log/jitsi -Djava.util.logging.config.file=/etc/jitsi/videobridge/logging.properties --add-opens jdk.management/com.sun.management.internal=ALL-UNNAMED"

Then we need to adjust the sip-communicator settings:

/etc/jitsi/videobridge/sip-communicator.properties

org.jitsi.videobridge.AUTHORIZED_SOURCE_REGEXP=focus@auth.meet.ffmuc.net/.*
org.jitsi.videobridge.ENABLE_STATISTICS=true
org.jitsi.videobridge.STATISTICS_INTERVAL=1000
org.jitsi.videobridge.STATISTICS_TRANSPORT=muc,colibri,pubsub
org.jitsi.videobridge.PUBSUB_SERVICE=meet.ffmuc.net
org.jitsi.videobridge.PUBSUB_NODE=sharedStatsNode

We use telegraf to poll the statistics of the videobridges. We just use the exec section of Telegraf, to get the data.

Example: Our grafana dashboard

/etc/telegraf/telegraf.conf

[[inputs.exec]]
   commands = [
     "curl localhost:8080/colibri/stats",
   ]
   name_suffix = "_meet"
   data_format = "json"