infrastructure

Archived

This repository has been archived on 2023-03-15. You can view files and clone it, but cannot push or open issues or pull requests.

History

Quentin Dufour 56cf9c1e55 Videobridge doc + debug		2021-01-31 18:03:55 +01:00
..
jicofo	Jicofo might work as intended!	2021-01-29 17:47:09 +01:00
jvb	Videobridge doc + debug	2021-01-31 18:03:55 +01:00
meet	Working on meet frontend	2021-01-30 12:06:14 +01:00
prosody	Working on meet frontend	2021-01-30 12:06:14 +01:00
docker-compose.yml	Videobridge doc + debug	2021-01-31 18:03:55 +01:00
README.md	Videobridge doc + debug	2021-01-31 18:03:55 +01:00

README.md

About Jitsi

Several server components:

prosody XMPP (ext)
jitsi videobridge aka JVB
jitsi conference focus aka jicofo aka focus
jitsi meet
octo
jigasi
jibri
etc.

Some libs:

libjitsi seems deprecated
jicoco contains some parent classes to handle Jitsi's Configuration
jitsi-utils contains the Logger definition for example
ice4j contains jitsi's implementation of WebRTC
etc.

Client components:

jitsi meet electron
jitsi android/ios
etc.

Conf

Base conf:

the following is used in videobridge.conf: jicoco/MucClientConfiguration

How the new configuration is read in jicoco: https://github.com/jitsi/jicoco/blob/master/jicoco-config/src/main/kotlin/org/jitsi/config/JitsiConfig.kt#L83-L91 They use this library: https://github.com/lightbend/config We are particularly interested by: https://github.com/lightbend/config#standard-behavior Using 'application.conf' with classpath does not seem to work. But, specifying the file path as -Dconfig.file=/etc/jitsi/jicofo.conf works!

Some parameters are also set independently of lightbend hocon config. They are seen in jicofo entrypoint: https://github.com/jitsi/jicofo/blob/master/src/main/java/org/jitsi/jicofo/Main.java Many of these parameters can be in fact read from the HOCON file except one: the --secret parameter or the JICOFO_SECRET env variable. But we can see this is a deprecated thing, it has been already removed from master: c9e5b50a8b For now (as per v5390) we will keep JICOFO_SECRET environment variable but will assume no other environment variable is set But maybe this value is deprecated: the check is still here but it is not used anymore?!

Generate certs with prosody

prosodyctl cert generate auth.jitsi
prosodyctl cert generate jitsi

An example prosody configuration file

https://github.com/jitsi/jitsi-meet/blob/master/doc/example-config-files/prosody.cfg.lua.example

but this one is not the one used by the debian postinst script instead, we should look at this one: https://github.com/jitsi/jitsi-meet/blob/master/doc/debian/jitsi-meet-prosody/prosody.cfg.lua-jvb.example

Jitsi can be configured to authenticated through tokens, the postinst file is here: https://github.com/jitsi/jitsi-meet/blob/master/debian/jitsi-meet-tokens.postinst

Remote debug

Add this parameter to the java process you want to debug (either jicofo or jvb). It must be added by modifying the entrypoint script, next to the respective Dockerfile of each container.

-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=*:5005

Be careful

jiti-videobridge (jvb) does not start to listen on ICE ports (both TCP and UDP) at boot. Instead, listening is triggered on the creation of the first conference (a 2 people P2P conference is enough). A nice entrypoint to check with your debugger is: