#Jitsi meet 8x8 how to#

// Enable unified plan implementation support on Chromium for p2p connection.// 3rd participant joins the conference will be moved back to the JVB.// through the JVB and use the peer to peer connection instead.If that succeeds the conference will stop sending data // establish a direct connection when there are exactly 2 participants.// Peer-To-Peer mode: used (if enabled) when there are just 2 participants.You should not see red in this situation.įor the second question, can you do the same test but disable the p2p in the call, so even for 2 participants to make sure the call goes through the bridge. Thanks a lot, we are really struggling with this for 1,5 year now. NB, we only use Jitsi for one-on-one calls (p2p or p2p-turn), so it doesn’t matter at all if we adjust any settings which have a negative impact on calls for more than 2 participants (like multicasting or whatever).

#Jitsi meet 8x8 how to#

The question is: why is the outgoing bitrate much lower then we have available (causing low quality video for about 50% of our clients) and do you have any advice how to improve this? However, when we close Jitsi and open Google Meet, the availableOutgoingBitrate is higher and is much more stable: The outgoing bitrate is going up and down and after a while we noticed that it seems to be linked to the availableOutgoingBitrate measured by Chrome: We did this test on, but 8x8.vc and our own server act the same. Same for the connection and video quality (LD): It is surprising that the outgoing bitrate is very low (65Kbps). The CPU usage during Jitsi meeting in Chrome of this client is about 25% and the internet upload speed is quite stable 2MB/s: We did some testing with two of our client’s PC’s via our own Jitsi server, 8x8.vc and and they all seem to have the same behavior. (other reasons are the higher availability and zero maintenance cost)

This is annoying and one of the reasons we want to switch to 8x8. Q2: In our (one-on-one always, doctor/client) calls we deal many times with bad quality, while the internet connection on both sides seems to be ok and no high CPU load. How is the poor quality indication defined in the API? Q1: Why is the connection indicator in my first post red, while all connection parameters seem to be ok? High bitrates, no package loss and (after some testing with e2eping enabled today) a low E2E-RTT. Sorry for the confusion, I tried to ask two questions at once: With LD/SD/HD I ment the indication in the top bar next to the session timer, I assume this corresponds with 180p/360p/720p of the incoming video.