Closed spprod35 closed 3 years ago
Update after a few hours of testing :
I integrated the following commits from the docker-jitsi-meet repository: 465816b4ebf2babf1b9e6daf007301c1fd17552e d747bfbe6b72dd86789f61a97372b94c2c19677f 130eb551a7666a9a143343e4ac7e707e3d6c6c02
They have not yet been released in the latest images. The above commits allow the integration of websocket easily. I made several configmaps while waiting for a release.
The errors for websockets are no longer there. However, there remain the E2E errors and the video quality which remains at a minimum
Can try setting on web-configmap.yaml
maxBitratesVideo: {
low: 200000,
standard: 500000,
high: 800000
},
and uncomment this then modify
// minHeightForQualityLvl: {
// 360: 'standard,
// 720: 'high'
// }
// },
I have tried this, to no avail. I was able to find a topic saying to deactivate the simulcast. I did this to no avail a few days ago.
However, I noticed today, that there were 2 occurrences for "disableSimulcast". I had not changed the correct value ...
Define "config.disableSimulcast = true;" at the end of the "web-configmap.yaml" file so that the HD quality returns while jitsi fixes the bug.
Hello
I failed to activate the websocket with kubernetes and this configuration. In addition I encounter this error on the client side:
This has the effect of blocking the quality to a minimum (320x240)
Do you have an idea ?
Thanks