I have one jvb in us-east and another in us-west, when I pass
function startConference() {
try {
const domain = url;
const options = {
roomName: id,
parentNode: document.getElementById('jitsi-container'),
configOverwrite: {
deploymentInfo: {
userRegion: "us-east"
}
}
};
const api = new window.JitsiMeetExternalAPI(domain, options);
...
on the client the JMS assigns the us-west one (or does not care), the call works fine though.
I take it we just need one block like this in nginx for X amount of JVb’s:
# colibri (JVB) websockets for additional JVBs
location ~ ^/colibri-ws/([0-9.]*)/(.*) {
proxy_pass http://$1:9090/colibri-ws/$1/$2$is_args$args;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
tcp_nodelay on;
}
videobridge {
http-servers {
public {
port = 9090
}
}
websockets {
server-id = "19.222.22.99"
enabled = true
domain = "meet.com:443"
tls = true
}
octo {
enabled=true
region="us-east"
relay-id="61054636-c546-4991-a203-8ab4bf22a9c0"
}
}
videobridge {
http-servers {
public {
port = 9090
}
}
websockets {
server-id = "53.193.47.175"
enabled = true
domain = "meet.com:443"
tls = true
}
octo {
enabled=true
region="us-west"
relay-id="df7ec86f-63d7-4da7-88e0-aa83840bb77e"
}
}
jicofo {
xmpp: {
client: {
client-proxy: focus.meet.com
}
trusted-domains: [ "recorder.meet.com" ]
}
bridge: {
brewery-jid: "JvbBrewery@internal.auth.meet.com"
selection-strategy: RegionBasedBridgeSelectionStrategy
}
authentication: {
enabled: true
type: XMPP
login-url: meet.com
enable-auto-login: false
}
}
