mediasoup-client 3.23.0 released with RTP extension control API

Announcements
1

mediasoup-client 3.23.0 comes with a new feature and a breaking change:

  • [BREAKING CHANGE] transport.produce(): Remove headerExtensionOptions.
  • DeviceOptions: Add forcedRtpExtensions option, which is an object whose keys are valid RtpHeaderExtensionUri strings and values are booleans indicating whether such a RTP extension should be enabled or disabled.
  • Currently it only works in latest Chrome, which is the only browser that supports the WebRTC RTP Extension Control API.

Usage example:

const mediasoupDevice = await mediasoupClient.Device.factory({
	forcedRtpExtensions: {
		'http://www.webrtc.org/experiments/rtp-hdrext/abs-capture-time': true
	},
});
2

So forcedRtpExtensions is not mandatory and mediasoup-client still works without it, right?

3

Correct.

BTW everything is always documented: mediasoup :: API