Thank you so much for your help. I finally got to build a WebRTC connection using
mediasoup. But is there any reason why you designed a user to create separate
recvTransport for producing and consuming respectively?
If a WebRTC transport represents a network path negotiated by both, a WebRTC endpoint and mediasoup, I feel like it could be more efficient to have a single transport handle both producing and consuming.