content: screen sharing streams (audio and video).audio: audio (listen only, microphone) streams.Default values for all media types are 0 (no dedicated workers). The semantics of auto, cores and Number are the same as in the mediasoup.workers configuration. The configuration is an object of the following format: Otherwise, they will use the shared pool. If a dedicated pool is set, streams of its media type will always land on it. This configuration controls the number of mediasoup workers to be used by specific media types. To set the number of workers to cores: yq w -i /etc/bigbluebutton/bbb-webrtc-sfu/production.yml mediasoup.workers "cores".The default and fallback values are auto.\: overrides the number of workers with a fixed value."cores": creates workers up to the host's core count (as provided by os.cpus().length).This configuration controls the number of mediasoup workers intended for general use (media type agnostic, shared pool). There are a couple of configurations of interest here: mediasoup.workers To control the number of mediasoup workers, bbb-webrtc-sfu's override configuration file (located in /etc/bigbluebutton/bbb-webrtc-sfu/production.yml) should be used. How can I control the number of mediasoup workers? Is single-core performance still important with mediasoup? It should be removed as a dependency as soon as this issue is addressed. Why is Kurento still around? īecause Kurento is still used for stream recording. Regardless of that: mediasoup is the default in 2.5 and should always be used unless default settings were explicitly changed. Look for the remote description (SDP) see if it contains mediasoup-client in the SDP header. For example: open one of those, share a camera. The most direct and precise way to figure out whether mediasoup is being used is checking about:webrtc (Firefox) or chrome://webrtc-internals. How do I know if mediasoup is being used? It's not on by default because bigbluebutton does not come with a TURN server by default, and that's what versioned-in-code setting presumes. Why isn't forceRelayOnFirefox enabled by default? You can also track BigBlueButton's issue for updates on additional workarounds. This is a Firefox bug, so the best place to get an overview on progress and what the issue is about is Mozilla's issue. Where can I track progress on a definitive solution or better workaround? It's generally a small subset of Firefox users, but that can vary depending on the user base. However, the issue doesn't manifest itself on all Firefox installations as it is dependent on how the end user's network topology is organized. Short (non) answer: that's difficult to measure.Įvery Firefox installation is prone to the lack of ICE-lite spec compliance. How often does this Firefox issue happens? To achieve that, set the configuration to true in /etc/bigbluebutton/bbb-html5.yml. This issue can be worked around by forcing TURN usage in Firefox user agents. That's usually the symptom of a known Firefox issue where it doesn't comply with ICE-lite implementations (and mediasoup is one). I'm having troubles seeing webcams or screen sharing in Firefox
Mozilla firefox install interrupted how to#
See Updating mediasoup for instructions and examples on how to do so. To configure IPv6, bbb-webrtc-sfu's override configuration file (located in /etc/bigbluebutton/bbb-webrtc-sfu/production.yml) should be used. Mediasoup (bbb-webrtc-sfu) does not come with a IPv6 enabled by default when installed either via packages or bbb-install. Nonetheless, we recommend double-checking the instructions in Updating mediasoup. If installed via bbb-install, then IPv4 is generally correct, but IPv6 might be absent. When installed via packages, mediasoup IPs are normally misconfigured. Bbb-webrtc-sfu and mediasoup Webcams/screen sharing aren't working Ĭertify that appropriate external addresses have been set for mediasoup.
0 kommentar(er)
