Dear experts, This is a curious question. While webrtc RTPTranceiver supports the sendrecv why Mediasoup creates 2 separately as sendonly and receiveonly? Won’t it be good if we have a single connection to server and that ports are free and possibly the CPU and memory is optimized on server? Any r…

Sorry about that, it was a bit confusing the question and my answer as well. You’d be fine running single transports for piping remotely/locally, the transport can consume/produce as many streams as you’d like, you just would differentiate them by consumer/producer ID. The CPU/Bandwidth will foreve…

single WebrtcTransport with multiple producers and consumers

mediasoup libraries

snnz (Sergey Nozhenko) April 13, 2022, 6:15pm 2

Take a look at this topic: What are the design limitations leading to separate send/receive transports on the client and can we lift them?

Topic		Replies	Views
Reasons for having separate transports for producing and consuming media mediasoup libraries	2	442	December 2, 2019
Fundamentals Question mediasoup libraries	7	197	June 3, 2021
PipeTransport Clarification mediasoup libraries	8	694	November 9, 2022
Downside of using one transport for only one producer/consumer? mediasoup libraries	16	429	March 29, 2023
Application architecture: Transports, Producers, and Consumers mediasoup libraries	2	249	December 2, 2021

single WebrtcTransport with multiple producers and consumers

Related Topics