Exposing RTCPeerConnection for a given transport

[kevmo314]

Can the RTCPeerConnection for a given transport be exposed? It’s necessary to do things like use insertable streams to mutate the stream before sending it to mediasoup, but right now the API doesn’t seem to provide such an operation?

[ibc (Iñaki Baz Castillo)]

AFAIS you don’t need access to the PeerConnection at all. You can tell mediasoup-client to create the pc with those new constraints by passing them in additionalSettings:

• https://mediasoup.org/documentation/v3/mediasoup-client/api/#TransportOptions

And you already have access to the RTCRtpSender once a Producer is created:

• https://mediasoup.org/documentation/v3/mediasoup-client/api/#producer-rtpSender

Let me know if there is something else you need that is not exposed above. For now, marking this topic as resolved.

[ibc (Iñaki Baz Castillo)]

@kevmo314 can you confirm that this is ok?

[havfo (Håvar Aambø Fosstveit)]

It seems one would need access to the RTPReceiver as well, on the consumer side if one is to decode the streams.

[ibc (Iñaki Baz Castillo)]

Have you actually checked the full API exposed by mediasoup-client?

• https://mediasoup.org/documentation/v3/mediasoup-client/api/#consumer-rtpReceiver

[havfo (Håvar Aambø Fosstveit)]

Off course you have already thought about it, great work! I need to read more carefully