From 6ce94ba33f749480a5dc2418a3e273ac132650ff Mon Sep 17 00:00:00 2001
From: Antonis Christofides <achristofides@admin.grnet.gr>
Date: Sun, 11 Jun 2023 20:04:01 +0300
Subject: [PATCH] Fix additional JVB broken after move to external Jitsi role
 (fixes #2733)

This contribution is provided by GRNET S.A. (grnet.gr).
---
 docs/configuring-playbook-jitsi.md | 10 ++++++++++
 group_vars/jitsi_jvb_servers       |  4 ++++
 2 files changed, 14 insertions(+)
 create mode 100644 group_vars/jitsi_jvb_servers

diff --git a/docs/configuring-playbook-jitsi.md b/docs/configuring-playbook-jitsi.md
index ddae16b03..d1353bb01 100644
--- a/docs/configuring-playbook-jitsi.md
+++ b/docs/configuring-playbook-jitsi.md
@@ -208,6 +208,16 @@ However, it can also be set the ip address of the matrix server. This can be use
 jitsi_xmpp_server: "192.168.0.1"
 ```
 
+For the JVB to be able ito contact the XMPP server, the latter must expose the XMPP port (5222).  By default, the Matrix server does not expose the
+port; only the XMPP container exposes it internally inside the host, which means that the first JVB (which runs on the Matrix server) can reach it but
+the additional JVB cannot. The port is exposed by setting `jitsi_prosody_container_jvb_host_bind_port` like this:
+
+```yaml
+jitsi_prosody_container_jvb_host_bind_port: 5222
+```
+
+(The default is empty; if it's set then docker forwards the port.)
+
 The nginx configuration will also need to be updated in order to deal with the additional JVB servers. This is achieved via its own configuration variable
 `matrix_nginx_proxy_proxy_jitsi_additional_jvbs`, which contains a dictionary of server ids to ip addresses.
 
diff --git a/group_vars/jitsi_jvb_servers b/group_vars/jitsi_jvb_servers
new file mode 100644
index 000000000..67815f7c0
--- /dev/null
+++ b/group_vars/jitsi_jvb_servers
@@ -0,0 +1,4 @@
+jitsi_architecture: "{{ matrix_architecture }}"
+jitsi_hostname: "{{ matrix_server_fqn_jitsi }}"
+jitsi_uid: "{{ matrix_user_uid }}"
+jitsi_gid: "{{ matrix_user_gid }}"