Uncomment the entire constraints section and set ideal: 480, max: 480 RECOMMENDED: Limit number of video feeds forwarded ¶ sudo nano /etc/jitsi/meet/$(hostname -f)-config.jsįor example: set resolution: 480 (and uncomment if necessary) You may want to limit the maximum video resolution, to save up resources on both server and clients. Read more on this feature here RECOMMENDED: Limit video resolution ¶ Set enableLayerSuspension: true (and uncomment if necessary) You may want to suspend unused video layers until they are requested again, to save up resources on both server and clients. Set requireDisplayName: true (and uncomment if necessary) RECOMMENDED: enable Layer Suspension ¶ sudo nano /etc/jitsi/meet/$(hostname -f)-config.js You may want to force users to choose a display name, to easily identify who is talking. sudo nano /etc/jitsi/meet/$(hostname -f)-config.jsĮdit language code defaultLanguage: 'en' Force users to set a display name ¶ Users may still choose they preferred language in client settings. You may want to change default interface language, if you are located in a non-English speaking country. IMPORTANT NOTE: after saving your settings, always restart jitsi services to apply them: sudo service jicofo restart & sudo service jitsi-videobridge2 restart. Jitsi default settings may work well with conferences with only a few participants, but as the number of participants increases, some of them may experience problems and crashes (not due to Jitsi server but to bandwidth and hardware limitations on the client side): by default each client encode (and send to the server) multiple video stream layers and, at the same time, receive everyone else’s at an ideal resolution of 720p. It is just a WIP proposal, open to discussion, on how a Jitsi server can be quickly (and legally) deployed in order to host one’s own private videomeetings, based on authors’ practical experiences.
DISCLAIMER: this is not legal nor technical advice.
0 kommentar(er)
