Hello community,
we are currently testing a self-hosted jitsi instance.
The VM has the following hardware:
CPU: Intel Xeon E5-2650 (4 cores)
RAM: 8GB
OS: Ubuntu 18.04 LTS
Our Jitsi runs behind a NAT. The configuration was carried out according to these instructions.
# Jitsi Meet quick install
This guide helps you ___host your own Jitsi server___. If you want to have a video conference without setting up any infrastructure, use https://meet.jit.si instead.
This document describes the required steps for a quick Jitsi Meet installation on a Debian based GNU/Linux system. Debian 9 (Stretch) or later, and Ubuntu 18.04 (Bionic Beaver) or later are supported out-of-the-box.
On Ubuntu systems, Jitsi requires dependencies from Ubuntu's `universe` package repository. To ensure this is enabled, run `apt-add-repository universe` at the command-line.
_Note_: Many of the installation steps require elevated privileges. If you are logged in using a regular user account, you may need to temporarily increase your permissions (for example, by using `sudo` for individual commands).
## Basic Jitsi Meet install
### Set up the Fully Qualified Domain Name (FQDN) (optional)
If the machine used to host the Jitsi Meet instance has a FQDN (for example `meet.example.org`) already set up in DNS, `/etc/hostname` must contain this FQDN; if this is not the case yet, [change the hostname](https://wiki.debian.org/HowTo/ChangeHostname).
Then add the same FQDN in the `/etc/hosts` file, associating it with the loopback address:
127.0.0.1 localhost meet.example.org
This file has been truncated. show original
As long as there are only two participants in a room, everything runs perfectly. As soon as the third person joins, the performance drops rapidly and the participants often go black.
Any ideas?
Many thanks for help!
What do you have in /etc/jitsi/videobridge/sip-communicator.properties?
Hello,
thanks for reply. Here is our sip-communicator.properties
org.ice4j.ice.harvest.DISABLE_AWS_HARVESTER=true
org.ice4j.ice.harvest.STUN_MAPPING_HARVESTER_ADDRESSES=stun.l.google.com:19302 ,stun1.l.google.com:19302 ,stun2.l.google.com:19302
org.jitsi.videobridge.ENABLE_STATISTICS=true
org.jitsi.videobridge.STATISTICS_TRANSPORT=muc
org.jitsi.videobridge.xmpp.user.shard.HOSTNAME=(Our Public DNS-Name)
org.jitsi.videobridge.xmpp.user.shard.DOMAIN=auth.(Our Public DNS-Name)
org.jitsi.videobridge.xmpp.user.shard.USERNAME=jvb
org.jitsi.videobridge.xmpp.user.shard.PASSWORD=lwZNf2RB
org.jitsi.videobridge.xmpp.user.shard.MUC_JIDS=JvbBrewery@internal.auth.(Our Public DNS-Name)
org.jitsi.videobridge.xmpp.user.shard.MUC_NICKNAME=1f2c525b-d49d-42dc-ab92-1c9c9bc00b08
org.ice4j.ice.harvest.NAT_HARVESTER_LOCAL_ADDRESS=192.168.111.20
org.ice4j.ice.harvest.NAT_HARVESTER_PUBLIC_ADDRESS=X.X.X.X (Our Public IP)
Doesn’t it ramp up? You should give it 10-20 seconds to ramp-up after the third joins.
No. Even after 2 minutes the performance is bad and the participants often go black for a short time…
As soon as the third participant leaves the room, it runs smoothly again
2 participants go p2p, 3 goes through the bridge. Is the bandwidth to the server enough? Is the server bandwith enough?
We use a 100Mbps (Up+Down) fiber internet connection. The Server is connected to The Firewall via 1 Gbps LAN.
You could try adding:
org.jitsi.videobridge.NAT_HARVESTER_LOCAL_ADDRESS=192.168.111.20
org.jitsi.videobridge.NAT_HARVESTER_PUBLIC_ADDRESS=Your Public IP
to /etc/jitsi/videobridge/sip-communicator.properties
And then restart jitsi-videobridge2.
i added the lines but the problem persists
What firewall ports do you have open / what ports are you NATing?
We NAT the Ports 10000 (UDP) and 443 (TCP)