Understanding OCTO

facsiaginsa · April 19, 2020, 12:36am

Hi, i want to try octo, but first i want to make sure that i understand the concept first. Any of you who already implement OCTO or know about it, please correct mme if i’m wrong. so my understanding is like this:

drawing 1:

So for octo to work we need the jitsi meet web with config.js (that will mark the user with region). All of the web connect to 1 (jicofo & prosody) server. we also need to configure jicofo bridge selection strategy. And the prosody is connected to jvb all across the region (and config the jvb region).

Is that sounds right?

Or we implement octo with multi (jico & prosody) server? for example like this:

drawing 2:

damencho · April 19, 2020, 2:03am

The second option is not supported. It is just bridges across regions as media is the critical traffic, signalling does not have problem with higher rtt.

facsiaginsa · April 19, 2020, 3:17am

Thx @damencho for confirming. I assume meet.jit.si using that first topology too right? Do you have failover mechanism for the jicofo & prosody server? Using haproxy or nginx maybe?

Oh one more question, If I want to use octo for dividing high number of participant in one room. Is that a good/bad idea? (We want to reduce the load in the videobridge)

Ex: 1 room with 80 people, we will divide them in “2 region”. 40 people each.

damencho · April 19, 2020, 3:41am

Yes.

Yes, multiple shards health monitored by haproxy.

damencho · April 19, 2020, 3:42am

Yep. That’s the way of doing big conferences.

facsiaginsa · April 19, 2020, 4:48am

Nice, thx! Will try octo configuration…

mudasirmirza · April 19, 2020, 8:59am

Hi,

Please if possible share your experience and if it is fine, can you also document how you configured OCTA

damencho · April 19, 2020, 4:58pm

github.com

jitsi/jitsi-videobridge/blob/master/doc/octo.md

# Setting up Octo (cascaded bridges)

## Jitsi Videobridge
Add these properties to `/etc/jitsi/videobridge/sip-communicator.properties` to
enable support for Octo:
```
org.jitsi.videobridge.octo.BIND_ADDRESS=10.0.0.1 # the address to bind to locally
org.jitsi.videobridge.octo.PUBLIC_ADDRESS=1.2.3.4 # the address to advertise (in case BIND_ADDRESS is not accessible)
org.jitsi.videobridge.octo.BIND_PORT=4096 # the port to bind to
org.jitsi.videobridge.REGION=region1 # the region that the jitsi-videbridge instance is in
```

You need to make sure that all of the bridges can communicate via the socket
addresses described in the properties above, and that the network is secure.

## Jicofo configuration
To enable the use of Octo in jicofo, you need to set the "selection strategy" by
setting this property in `/etc/jitsi/jicofo/sip-communicator.properties`:
```
org.jitsi.jicofo.BridgeSelector.BRIDGE_SELECTION_STRATEGY=RegionBasedBridgeSelectionStrategy

This file has been truncated. show original

tibinvpaul · May 31, 2020, 4:03pm

Hey @damencho - I have a follow up question regarding OCTO. Shall we configure OCTO on a single region setup to divide participants across multiple JVBs? If it is possible, how the streams will be distributed? Will it be handled automatically? Thanks.

facsiaginsa · June 2, 2020, 12:49pm

@tibinvpaul, for me, i configure them with different regions. If you want to make it just 1 region. Use intraRegionBridgeSelectionStrategy (not officially documented by jitsi team, but from reading the jicofo code, it can be done). Look here to know how the bridge is selected: https://github.com/jitsi/jicofo/blob/master/src/main/java/org/jitsi/jicofo/bridge/IntraRegionBridgeSelectionStrategy.java

boby21 · September 5, 2020, 1:41pm

its strange after setting octo, I am receiving a lot of connection timeout and connection lost? before octo everything was fine