-
Notifications
You must be signed in to change notification settings - Fork 46
Back of the envelope calculations: mediasoup
Paulo Lanzarin edited this page May 2, 2022
·
16 revisions
- Set the correct IPv4 for mediasoup:
- Let $SERVER_IPv4 be your server's public IPv4
yq w -i /etc/bigbluebutton/bbb-webrtc-sfu/production.yml mediasoup.webrtc.listenIps[0].ip "0.0.0.0"
yq w -i /etc/bigbluebutton/bbb-webrtc-sfu/production.yml mediasoup.webrtc.listenIps[0].announcedIp $SERVER_IPv4
yq w -i /etc/bigbluebutton/bbb-webrtc-sfu/production.yml mediasoup.plainRtp.listenIp.ip "0.0.0.0"
yq w -i /etc/bigbluebutton/bbb-webrtc-sfu/production.yml mediasoup.plainRtp.listenIp.announcedIp $SERVER_IPv4
- If you wish to enable IPv6 in mediasoup (otherwise skip to step 3):
- Let $SERVER_IPv6 be your server's IPv6
yq w -i /etc/bigbluebutton/bbb-webrtc-sfu/production.yml mediasoup.webrtc.listenIps[1].ip $SERVER_IPv6
- Follow https://github.com/bigbluebutton/bigbluebutton/pull/13112 to control mediasoup usage per meeting (metadata) or server (settings.yml) and then
sudo bbb-conf --restart
- If you're going to use mediasoup server wide, we recommend running the following command as an optional optimization:
yq w -i /etc/bigbluebutton/bbb-html5.yml public.kurento.signalCandidates false
- If you're going to use mediasoup server wide, we recommend running the following command as an optional optimization:
Refer to the to the docs in the code repository.