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?
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:
And you already have access to the RTCRtpSender once a Producer is created:
Let me know if there is something else you need that is not exposed above. For now, marking this topic as resolved.
@kevmo314 can you confirm that this is ok?
It seems one would need access to the RTPReceiver as well, on the consumer side if one is to decode the streams.
Have you actually checked the full API exposed by mediasoup-client? 
Off course you have already thought about it, great work! I need to read more carefully
1 Like