@@ -155,22 +155,16 @@ or in /etc/jitsi/videobridge/config
VIDEOBRIDGE_MAX_MEMORY=8192m
### on fairmeeting main server
Let bridges communicate with MUC https://git.fairkom.net/hosting/fairmeeting/issues/55
### Firewall
Previously we had to enter a bridge as component with its secret in `/etc/prosody/conf.avail/fairmeeting.net.cfg.lua`
```
Component "jvb-HOSTINGPARTNER-0.fairmeeting.net"
component_secret = "secret"
ufw allow 10000/udp
ufw allow 22/tcp
ufw enable
```
and then do
`service prosody restart`
`service jitsi-videobridge restart`
For statistics, check /var/log/jitsi/jicofo.log like https://youtu.be/LyGV4uW8km8?t=1269 for messages like `Video stream count for:`
### allow colibri web socket
...
...
@@ -201,3 +195,24 @@ videobridge {
```
Use jvb's IP address for server-id - this will allow proxy in /etc/nginx/sites-available/run.fairmeeting.net.conf to proxy the client via websocket directly to the IP of the bridge so that the bridge can ask directly the web browser on the health.
# Historical
The following tasks are deprecated when installing a videobridge:
### on fairmeeting main server
Let bridges communicate with MUC https://git.fairkom.net/hosting/fairmeeting/issues/55
Previously we had to enter a bridge as component with its secret in `/etc/prosody/conf.avail/fairmeeting.net.cfg.lua`
```
Component "jvb-HOSTINGPARTNER-0.fairmeeting.net"
component_secret = "secret"
```
and then do
`service prosody restart`
`service jitsi-videobridge restart`
For statistics, check /var/log/jitsi/jicofo.log like https://youtu.be/LyGV4uW8km8?t=1269 for messages like `Video stream count for:`