Performance optimization / Jitsi with separate videobridges, rather poor quality

Install & Config
#1

We have set up a Jitsi-Meet system on debian 10 VMs.
The setup consists of a Jicofo / Coturn /Prosody server / Videobridge (jitsi-main) and 2 additional video bridge VMs (jitsi-jvb1 / jitsi-jvb2).
The VMs run as KVM on a Proxmox VE host.

All in all, after a long test phase, the system now seems to work quite properly.
However, we are still experiencing some problems.
The stability of the connections, as well as the general performance is very fluctuating and changes even during a meeting.
A participant who initially experiences fantastic results suddenly gets a bad connection for no apparent reason (red indicator) and then suddenly starts to stall or is out of sync.
And this even though he uses a laptop with chrome and a 100Mbit line.
We believe that there must be a few tricks left to do this much better, but we don’t know where to look anymore.
That’s why we are hoping for you…Please help us if you know something.

Here’s some of our config files (all from the main jitsi vm), let me know, if you need more:

/etc/prosody/prosody.cfg.lua
/etc/prosody/conf.avail/vc.foo.bar.cfg.lua
/etc/jitsi/meet/vc.foo.bar-config.js
/etc/jitsi/jicofo/config
/etc/jitsi/jicofo/sip-communicator.properties
/etc/jitsi/videobridge/config
/etc/jitsi/videobridge/sip-communicator.properties
/etc/sysctl.conf

Thanks a lot for your help, really looking forward to your comments
Sascha

prosody.cfg.lua.txt (10.2 KB) vc.foo.bar.cfg.lua.txt (2.9 KB) vc.foo.bar-config.js.txt (18.0 KB) jicofo-config.txt (987 Bytes) jicofo-sip-communicator.properties.txt (200 Bytes) videobridge-config.txt (782 Bytes) videobridge-sip-communicator.properties.txt (731 Bytes) sysctl.conf.txt (461 Bytes)

#2

As a start, can you change sysctl settings to match these: https://github.com/jitsi/jitsi-videobridge/blob/master/config/20-jvb-udp-buffers.conf
And see how it goes. Overall you should be using just jvb2, we can talk about and fix stuff in it. Jvb1 will not be debuged as it will not get any updates and there is no point of wasting time on it.

#3

Hi,
thanks, i changed sysctl on all nodes accordingly.
We will try to update to jvb2 during the easter days presumably, will let you know.

cheers
Sascha

#4

Hi,
well the changes to sysctl don’t seem to have improved the situation very much.
So now i would like to upgrade to jvb2.
As we experienced a bit of trouble doing so in the past, is there any “easy walkthrough of upgrading jvb1 to jvb2” including the separate videobridges, we could follow?
thanks
Sascha

#5

ok folks.
got jvb2 running on all three nodes.
But unfortunately we still have serious connection issues.
Actually it even looks like perfomance is worse than with jvb1.
Allthough attendees have a very fast and stable connection, Jitsi gives them a red or yellow connection icon, from time to time. Video / audio are far from in sync most of the time.

Would really appreciate some hints if you have any.
Tell me which config files you would like to see, and i will be very keen to provide them.

thanks
Sascha

#6

Hey bridge team @bbaldino @Boris_Grozev @Jonathan_Lennox any ideas?

#7

Ok, here are the configuration files as they are currently activated on the main jitsi vm.

/etc/prosody/prosody.cfg.lua
/etc/prosody/conf.avail/vc.foo.bar.cfg.lua
/etc/jitsi/meet/vc.foo.bar-config.js
/etc/jitsi/jicofo/config
/etc/jitsi/jicofo/sip-communicator.properties
/etc/jitsi/videobridge/config
/etc/jitsi/videobridge/sip-communicator.properties
/etc/sysctl.conf

looking forward to hear your remarks and ideas,
thanks a ton
Sascha

prosody.cfg.lua.txt (10.2 KB) vc.foo.bar.cfg.lua.txt (2.9 KB) vc.foo.bar-config.js.txt (18.0 KB) jicofo-config.txt (987 Bytes) jicofo-sip-communicator.properties.txt (200 Bytes) videobridge-config.txt (782 Bytes) videobridge-sip-communicator.properties.txt (877 Bytes) sysctl.conf.txt (511 Bytes)

#8

Unfortunately it is getting even worse here now.

We now have the problem of participants not seeing all attendees when logging into a meeting room.
The new attendee only sees one other user, but without video / audio, while two other users do see and hear each other in that room.
After a couple of login retires (up to 15 times) the connection with 3 users will be established and works.
So basically meetings with more than 2 users are not really possible atm.
We have strange Jigasi errors in our jicofo log, allthough jigasi is not even installed, don’t know if that is relevant:

org.jitsi.jicofo.jigasi.TranscriberManager.log() Error finding room for null

also some of these warnings:

org.jitsi.protocol.xmpp.AbstractOperationSetJingle.processJingleIQ().368 unsupported action session-terminate

videobridge warnings in the logs:

2020-04-15 11:15:46.993 WARNUNG: [48] [confId=411a6c4494d2e4f1 epId=d9f08cdd gid=ff0c16 stats_id=Morton-8gw conf_name=systemschmiede ssrc=1539892212] RetransmissionRequester$StreamPacketRequester.packetReceived#120: 1539892212 large jump in sequence numbers detected (highest received was 18395, current is 18735, jump of 339), not requesting retransmissions
2020-04-15 11:15:56.470 WARNUNG: [483] [confId=411a6c4494d2e4f1 epId=90c404fd gid=ff0c16 stats_id=Deondre-R8m conf_name=systemschmiede] AbstractEndpointMessageTransport.onClientEndpointMessage#219: Unable to find endpoint a42c424c to send EndpointMessage
2020-04-15 11:16:13.799 WARNUNG: [474] [confId=c0be16ad77d736cf gid=ff44c9 stats_id=Orie-ot0 componentId=1 conf_name=test ufrag=7h8ne1e5uhu49o name=stream-f0f3fe25 epId=f0f3fe25 local_ufrag=7h8ne1e5uhu49o] MergingDatagramSocket.doRemove#349: Removing the active socket. Won’t be able to send until a new one is elected.
2020-04-15 11:16:14.491 WARNUNG: [48] [confId=411a6c4494d2e4f1 epId=a42c424c gid=ff0c16 stats_id=Morton-8gw conf_name=systemschmiede ssrc=2923133453] RetransmissionRequester$StreamPacketRequester.packetReceived#120: 2923133453 large jump in sequence numbers detected (highest received was 24986, current is 25104, jump of 117), not requesting retransmissions
2020-04-15 11:16:14.494 WARNUNG: [51] [confId=411a6c4494d2e4f1 epId=a42c424c gid=ff0c16 stats_id=Morton-8gw conf_name=systemschmiede ssrc=3608345909] RetransmissionRequester$StreamPacketRequester.packetReceived#120: 3608345909 large jump in sequence numbers detected (highest received was 16673, current is 17014, jump of 340), not requesting retransmissions
2020-04-15 11:17:04.397 WARNUNG: [486] [confId=411a6c4494d2e4f1 gid=ff0c16 stats_id=Genoveva-UQz componentId=1 conf_name=systemschmiede ufrag=e9qdo1e5uhunqo name=stream-24fb9ec3 epId=24fb9ec3 local_ufrag=e9qdo1e5uhunqo] MergingDatagramSocket.doRemove#349: Removing the active socket. Won’t be able to send until a new one is elected.
2020-04-15 11:17:41.341 WARNUNG: [483] [confId=411a6c4494d2e4f1 epId=90c404fd gid=ff0c16 stats_id=Deondre-R8m conf_name=systemschmiede] AbstractEndpointMessageTransport.onClientEndpointMessage#219: Unable to find endpoint 12dc01ba to send EndpointMessage
2020-04-15 11:17:41.438 WARNUNG: [483] [confId=411a6c4494d2e4f1 epId=a42c424c gid=ff0c16 stats_id=Morton-8gw conf_name=systemschmiede] AbstractEndpointMessageTransport.onClientEndpointMessage#219: Unable to find endpoint 12dc01ba to send EndpointMessage
2020-04-15 11:18:41.138 WARNUNG: [414] [confId=411a6c4494d2e4f1 epId=a42c424c gid=ff0c16 stats_id=Morton-8gw conf_name=systemschmiede] AbstractEndpointMessageTransport.onClientEndpointMessage#219: Unable to find endpoint 439c8385 to send EndpointMessage
2020-04-15 11:19:54.053 WARNUNG: [414] [confId=411a6c4494d2e4f1 epId=a42c424c gid=ff0c16 stats_id=Morton-8gw conf_name=systemschmiede] AbstractEndpointMessageTransport.onClientEndpointMessage#219: Unable to find endpoint 4a3756e4 to send EndpointMessage
2020-04-15 11:20:22.073 WARNUNG: [504] [confId=411a6c4494d2e4f1 epId=a42c424c gid=ff0c16 stats_id=Morton-8gw conf_name=systemschmiede] AbstractEndpointMessageTransport.onClientEndpointMessage#219: Unable to find endpoint c7acb724 to send EndpointMessage
2020-04-15 11:20:51.080 WARNUNG: [495] [confId=411a6c4494d2e4f1 gid=ff0c16 stats_id=Deondre-R8m componentId=1 conf_name=systemschmiede ufrag=aav711e5uhuvrc name=stream-90c404fd epId=90c404fd local_ufrag=aav711e5uhuvrc] MergingDatagramSocket.doRemove#349: Removing the active socket. Won’t be able to send until a new one is elected.
2020-04-15 11:21:01.902 WARNUNG: [510] [confId=411a6c4494d2e4f1 epId=c7acb724 gid=ff0c16 stats_id=Wilburn-LVq conf_name=systemschmiede] AbstractEndpointMessageTransport.onClientEndpointMessage#219: Unable to find endpoint 8e8eeb04 to send EndpointMessage
2020-04-15 11:21:01.906 WARNUNG: [462] [confId=411a6c4494d2e4f1 epId=a42c424c gid=ff0c16 stats_id=Morton-8gw conf_name=systemschmiede] AbstractEndpointMessageTransport.onClientEndpointMessage#219: Unable to find endpoint 8e8eeb04 to send EndpointMessage
2020-04-15 11:21:11.574 WARNUNG: [462] [confId=411a6c4494d2e4f1 epId=c7acb724 gid=ff0c16 stats_id=Wilburn-LVq conf_name=systemschmiede] AbstractEndpointMessageTransport.onClientEndpointMessage#219: Unable to find endpoint 5589ee06 to send EndpointMessage
2020-04-15 11:21:11.598 WARNUNG: [510] [confId=411a6c4494d2e4f1 epId=a42c424c gid=ff0c16 stats_id=Morton-8gw conf_name=systemschmiede] AbstractEndpointMessageTransport.onClientEndpointMessage#219: Unable to find endpoint 5589ee06 to send EndpointMessage
2020-04-15 11:21:21.265 WARNUNG: [462] [confId=411a6c4494d2e4f1 epId=c7acb724 gid=ff0c16 stats_id=Wilburn-LVq conf_name=systemschmiede] AbstractEndpointMessageTransport.onClientEndpointMessage#219: Unable to find endpoint cda273f4 to send EndpointMessage
2020-04-15 11:21:21.273 WARNUNG: [510] [confId=411a6c4494d2e4f1 epId=a42c424c gid=ff0c16 stats_id=Morton-8gw conf_name=systemschmiede] AbstractEndpointMessageTransport.onClientEndpointMessage#219: Unable to find endpoint cda273f4 to send EndpointMessage
2020-04-15 11:23:44.175 WARNUNG: [48] [confId=411a6c4494d2e4f1 epId=c7acb724 gid=ff0c16 stats_id=Wilburn-LVq conf_name=systemschmiede ssrc=81850607] RetransmissionRequester$StreamPacketRequester.packetReceived#120: 81850607 large jump in sequence numbers detected (highest received was 14660, current is 14840, jump of 179), not requesting retransmissions
2020-04-15 11:27:04.349 WARNUNG: [48] [confId=411a6c4494d2e4f1 epId=a42c424c gid=ff0c16 stats_id=Morton-8gw conf_name=systemschmiede] SendSideBandwidthEstimation.getRttMs#587: RTT suspiciously high (1113ms), capping to 1000ms.
2020-04-15 11:30:23.608 WARNUNG: [498] [confId=411a6c4494d2e4f1 gid=ff0c16 stats_id=Morton-8gw componentId=1 conf_name=systemschmiede ufrag=56ur51e5uhv85i name=stream-a42c424c epId=a42c424c local_ufrag=56ur51e5uhv85i] MergingDatagramSocket.doRemove#349: Removing the active socket. Won’t be able to send until a new one is elected.
2020-04-15 11:30:24.920 WARNUNG: [506] [confId=411a6c4494d2e4f1 gid=ff0c16 stats_id=Wilburn-LVq componentId=1 conf_name=systemschmiede ufrag=69l5n1e5ui7bd3 name=stream-c7acb724 epId=c7acb724 local_ufrag=69l5n1e5ui7bd3] MergingDatagramSocket.doRemove#349: Removing the active socket. Won’t be able to send until a new one is elected.

and the SEVERE entries in that log:

2020-04-15 10:43:23.483 SCHWERWIEGEND: [287] [confId=a60d3378fb9a9d4f epId=6e074ec5 gid=ff2887 stats_id=Sydney-xFt conf_name=testmitkathrin] DataChannelStack.onIncomingDataChannelPacket#81: Could not find data channel for sid 1
2020-04-15 10:44:11.821 SCHWERWIEGEND: [237] [confId=a60d3378fb9a9d4f epId=c3ce7c4d gid=ff2887 stats_id=Sydney-xFt conf_name=testmitkathrin] DataChannelStack.onIncomingDataChannelPacket#81: Could not find data channel for sid 1
2020-04-15 10:44:11.821 SCHWERWIEGEND: [237] [confId=a60d3378fb9a9d4f epId=c3ce7c4d gid=ff2887 stats_id=Sydney-xFt conf_name=testmitkathrin] DataChannelStack.onIncomingDataChannelPacket#81: Could not find data channel for sid 1
2020-04-15 10:44:30.189 SCHWERWIEGEND: [297] [confId=a60d3378fb9a9d4f epId=16109808 gid=ff2887 stats_id=Sydney-xFt conf_name=testmitkathrin] DataChannelStack.onIncomingDataChannelPacket#81: Could not find data channel for sid 1
2020-04-15 10:44:30.189 SCHWERWIEGEND: [297] [confId=a60d3378fb9a9d4f epId=16109808 gid=ff2887 stats_id=Sydney-xFt conf_name=testmitkathrin] DataChannelStack.onIncomingDataChannelPacket#81: Could not find data channel for sid 1
2020-04-15 10:45:50.273 SCHWERWIEGEND: [303] [confId=68264c7bf81228ac epId=9c62e98a gid=ff2887 stats_id=Sydney-xFt conf_name=testmitkathrin] DataChannelStack.onIncomingDataChannelPacket#81: Could not find data channel for sid 1
2020-04-15 10:45:50.273 SCHWERWIEGEND: [303] [confId=68264c7bf81228ac epId=9c62e98a gid=ff2887 stats_id=Sydney-xFt conf_name=testmitkathrin] DataChannelStack.onIncomingDataChannelPacket#81: Could not find data channel for sid 1
2020-04-15 10:45:50.273 SCHWERWIEGEND: [303] [confId=68264c7bf81228ac epId=9c62e98a gid=ff2887 stats_id=Sydney-xFt conf_name=testmitkathrin] DataChannelStack.onIncomingDataChannelPacket#81: Could not find data channel for sid 1
2020-04-15 10:55:20.658 SCHWERWIEGEND: [377] [confId=e3b52b40f83bc3d7 epId=013c729e gid=ff1246 stats_id=Raheem-rQb conf_name=vioklittemi] DataChannelStack.onIncomingDataChannelPacket#81: Could not find data channel for sid 1
2020-04-15 10:55:20.658 SCHWERWIEGEND: [377] [confId=e3b52b40f83bc3d7 epId=013c729e gid=ff1246 stats_id=Raheem-rQb conf_name=vioklittemi] DataChannelStack.onIncomingDataChannelPacket#81: Could not find data channel for sid 1
2020-04-15 11:15:41.274 SCHWERWIEGEND: [462] [confId=411a6c4494d2e4f1 epId=24fb9ec3 gid=ff0c16 stats_id=Genoveva-UQz conf_name=systemschmiede] DataChannelStack.onIncomingDataChannelPacket#81: Could not find data channel for sid 1
2020-04-15 11:15:51.057 SCHWERWIEGEND: [449] [confId=411a6c4494d2e4f1 epId=90c404fd gid=ff0c16 stats_id=Deondre-R8m conf_name=systemschmiede] DataChannelStack.onIncomingDataChannelPacket#81: Could not find data channel for sid 1
2020-04-15 11:15:58.251 SCHWERWIEGEND: [490] [confId=411a6c4494d2e4f1 epId=a42c424c gid=ff0c16 stats_id=Morton-8gw conf_name=systemschmiede] DataChannelStack.onIncomingDataChannelPacket#81: Could not find data channel for sid 1
2020-04-15 11:15:58.251 SCHWERWIEGEND: [496] [confId=411a6c4494d2e4f1 epId=a42c424c gid=ff0c16 stats_id=Morton-8gw conf_name=systemschmiede] DataChannelStack.onIncomingDataChannelPacket#81: Could not find data channel for sid 1
2020-04-15 11:15:58.251 SCHWERWIEGEND: [491] [confId=411a6c4494d2e4f1 epId=a42c424c gid=ff0c16 stats_id=Morton-8gw conf_name=systemschmiede] DataChannelStack.onIncomingDataChannelPacket#81: Could not find data channel for sid 1

please help me…i don’t really know what to do right now.
thanks
Sascha

#9

My users are helped a-lot by disable measuring audio levels and rendering of the blue “i am talking dots”
disableAudioLevels: true,

This setting along reduces CPU load on slower client computers 70% and will improve audio performance.
A lot of the errors you see in the server log originate from overloaded client computers.

2 Likes
#10

hi xranby,
thanks, will try that instantly!
but can this setting really trigger the “more than 2 users have difficulties to meet in one room” problem?
Any additional hints highly appreciated!

thanks
Sascha

#11

edited the file as xranby said.
New attempt:
1 notebook with good WiFi (Chrome)
1 mobile (Samsung S10) with H connection

jvb warnings

2020-04-15 12:31:52.847 WARNUNG: [138] [confId=94237543d55d9e51 epId=bf3df464 gid=ffc4e5 stats_id=Katlynn-GMp conf_name=systemschmiede] TransportCcEngine.tccReceived#157: TCC packet contained received sequence numbers: 1752-1753. Couldn't find packet detail for the seq nums: 1752-1753. Latest seqNum was 14931, size is 1000. Latest RTT is 43243,308436 ms.
2020-04-15 12:31:52.893 WARNUNG: [138] [confId=94237543d55d9e51 epId=bf3df464 gid=ffc4e5 stats_id=Katlynn-GMp conf_name=systemschmiede] TransportCcEngine.tccReceived#157: TCC packet contained received sequence numbers: 1754-1755. Couldn't find packet detail for the seq nums: 1754-1755. Latest seqNum was 14940, size is 1000. Latest RTT is 43243,308436 ms.
2020-04-15 12:31:52.941 WARNUNG: [137] [confId=94237543d55d9e51 epId=bf3df464 gid=ffc4e5 stats_id=Katlynn-GMp conf_name=systemschmiede] TransportCcEngine.tccReceived#157: TCC packet contained received sequence numbers: 1756-1757. Couldn't find packet detail for the seq nums: 1756-1757. Latest seqNum was 14949, size is 1000. Latest RTT is 43243,308436 ms.
2020-04-15 12:31:52.999 WARNUNG: [138] [confId=94237543d55d9e51 epId=bf3df464 gid=ffc4e5 stats_id=Katlynn-GMp conf_name=systemschmiede] TransportCcEngine.tccReceived#157: TCC packet contained received sequence numbers: 1758-1759. Couldn't find packet detail for the seq nums: 1758-1759. Latest seqNum was 14962, size is 1000. Latest RTT is 43243,308436 ms.
2020-04-15 12:31:53.051 WARNUNG: [138] [confId=94237543d55d9e51 epId=bf3df464 gid=ffc4e5 stats_id=Katlynn-GMp conf_name=systemschmiede] TransportCcEngine.tccReceived#157: TCC packet contained received sequence numbers: 1760-1761. Couldn't find packet detail for the seq nums: 1760-1761. Latest seqNum was 14965, size is 1000. Latest RTT is 43243,308436 ms.
2020-04-15 12:31:53.091 WARNUNG: [137] [confId=94237543d55d9e51 epId=bf3df464 gid=ffc4e5 stats_id=Katlynn-GMp conf_name=systemschmiede] TransportCcEngine.tccReceived#157: TCC packet contained received sequence numbers: 1762-1763. Couldn't find packet detail for the seq nums: 1762-1763. Latest seqNum was 14969, size is 1000. Latest RTT is 43243,308436 ms.
2020-04-15 12:31:53.171 WARNUNG: [138] [confId=94237543d55d9e51 epId=bf3df464 gid=ffc4e5 stats_id=Katlynn-GMp conf_name=systemschmiede] TransportCcEngine.tccReceived#157: TCC packet contained received sequence numbers: 1764-1765. Couldn't find packet detail for the seq nums: 1764-1765. Latest seqNum was 14991, size is 1000. Latest RTT is 43243,308436 ms.
2020-04-15 12:31:53.211 WARNUNG: [137] [confId=94237543d55d9e51 epId=bf3df464 gid=ffc4e5 stats_id=Katlynn-GMp conf_name=systemschmiede] TransportCcEngine.tccReceived#157: TCC packet contained received sequence numbers: 1766-1767. Couldn't find packet detail for the seq nums: 1766-1767. Latest seqNum was 15005, size is 1000. Latest RTT is 43243,308436 ms.
2020-04-15 12:31:53.260 WARNUNG: [138] [confId=94237543d55d9e51 epId=bf3df464 gid=ffc4e5 stats_id=Katlynn-GMp conf_name=systemschmiede] TransportCcEngine.tccReceived#157: TCC packet contained received sequence numbers: 1768-1769. Couldn't find packet detail for the seq nums: 1768-1769. Latest seqNum was 15017, size is 1000. Latest RTT is 43243,308436 ms.
2020-04-15 12:31:53.427 WARNUNG: [138] [confId=94237543d55d9e51 epId=bf3df464 gid=ffc4e5 stats_id=Katlynn-GMp conf_name=systemschmiede] TransportCcEngine.tccReceived#157: TCC packet contained received sequence numbers: 1770-1774. Couldn't find packet detail for the seq nums: 1770-1774. Latest seqNum was 15105, size is 1000. Latest RTT is 43243,308436 ms.
2020-04-15 12:31:53.495 WARNUNG: [137] [confId=94237543d55d9e51 epId=bf3df464 gid=ffc4e5 stats_id=Katlynn-GMp conf_name=systemschmiede] TransportCcEngine.tccReceived#157: TCC packet contained received sequence numbers: 1775-1777. Couldn't find packet detail for the seq nums: 1775-1777. Latest seqNum was 15129, size is 1000. Latest RTT is 43243,308436 ms.
2020-04-15 12:31:53.519 WARNUNG: [137] [confId=94237543d55d9e51 epId=bf3df464 gid=ffc4e5 stats_id=Katlynn-GMp conf_name=systemschmiede] TransportCcEngine.tccReceived#157: TCC packet contained received sequence numbers: 1778. Couldn't find packet detail for the seq nums: 1778. Latest seqNum was 15157, size is 1000. Latest RTT is 43243,308436 ms.
2020-04-15 12:31:53.548 WARNUNG: [137] [confId=94237543d55d9e51 epId=bf3df464 gid=ffc4e5 stats_id=Katlynn-GMp conf_name=systemschmiede] TransportCcEngine.tccReceived#157: TCC packet contained received sequence numbers: 1779-1780. Couldn't find packet detail for the seq nums: 1779-1780. Latest seqNum was 15167, size is 1000. Latest RTT is 43243,308436 ms.
2020-04-15 12:31:53.603 WARNUNG: [138] [confId=94237543d55d9e51 epId=bf3df464 gid=ffc4e5 stats_id=Katlynn-GMp conf_name=systemschmiede] TransportCcEngine.tccReceived#157: TCC packet contained received sequence numbers: 1781-1782. Couldn't find packet detail for the seq nums: 1781-1782. Latest seqNum was 15179, size is 1000. Latest RTT is 43243,308436 ms.
2020-04-15 12:31:53.643 WARNUNG: [138] [confId=94237543d55d9e51 epId=bf3df464 gid=ffc4e5 stats_id=Katlynn-GMp conf_name=systemschmiede] TransportCcEngine.tccReceived#157: TCC packet contained received sequence numbers: 1783-1785. Couldn't find packet detail for the seq nums: 1783-1785. Latest seqNum was 15197, size is 1000. Latest RTT is 43243,308436 ms.

And i can see two users on my mobile, and only one user on my notebook…
I just don’t get it.

#12

ok, i can confirm, that video / sound / performance seem to be much better now, after disabling audiolevels.
However, we seem to have a split brain scenario here, where, startiing with 3 users, everybody has a different view.
For example:
first user sees / hears everyone
second user sees / hears himself and one other
third user sees 3 users but only hears one

What can that be?
Obviously this is a show stopper at the moment…

thanks again
Sascha

2 Likes
#13

Can you post the jicofo log , and the logs from all three video bridges?

sounds like a bug in the OCTO bridge synchronization.
without OCTO all users in one room should use one videobridge.
with OCTO users should be split up using all videobridges.

#14

Do the “split brain scenario” appear if only ONE bridge is active?

#15

yes, we stopped the other two, and we still had these problems

#16

can you try disable p2p mode so that all communication uses the bridge?
p2p: {
enabled: false,
}

#17

here’s the log files.
https://dropmefiles.com/94FvF
Sorry…wasn’t able to upload it in any other way…

thanks
Sascha

#18

i suppose you would like to read the logfiles before i edit p2p to false?

#19

I looked at the jicofo log WARNUNG’s and odd information.

  1. Not merging A/V streams from A to B
    Jicofo 2020-04-15 09:59:40.625 INFORMATION: [48] org.jitsi.jicofo.LipSyncHack.log() Not merging A/V streams from rmsrabel@conference.vc.foo.bar/144f655e to rmsrabel@conference.vc.foo.bar/b05eea8b
    Jicofo 2020-04-15 09:59:40.625 INFORMATION: [48] org.jitsi.jicofo.LipSyncHack.log() Not merging A/V streams from rmsrabel@conference.vc.foo.bar/53430fc4 to rmsrabel@conference.vc.foo.bar/b05eea8b

  2. it looks that all three videobridges uses the same login i think this is an error *

  3. missing pub-sub configuration, i think this is a requirement when using external videobridges *
    Jicofo 2020-04-15 09:48:50.448 WARNUNG: [30] org.jitsi.jicofo.bridge.BridgeSelector.log() No pub-sub node mapped for jvbbrewery@internal.auth.vc.foo.bar/7a882c9b-b169-49ac-bc0c-c3df680efdd4

I do not know if 0. is an issue.

I base my two remarks 1. and 2. on how to setup more than one videobridge and configure pubsub using this video tutorial:

#20

I think muc is now replacing pubsub (when using jvb2), and we consider it correct to use the same login for all videobridges.

Are we wrong?

thanks
Sascha