Viewing profile — ibc

Yeah please, let the author know your preferred programming language so he'll rewrite the whole software.

Yep, I know. However the effort required to make and maintain DEB/RPM packages for different architectures (mediasoup has a C++ component) is huge.

DataChannels are transmitted over the same UDP/ICE "connection" that is used to transmit audio and video packets. So if you plan to send real-time data (for example: real-time subt…

mediasoup is not an application, is a Node.js library. It's yet nother NPM dependency in your Node.js application. No reason to have a DEB package.

mediasoup (server side, so the Node + C++ component you mean) does not implement "RTCPeerConnection". That's just needed for browsers. In mediasoup we don't use SDP but specific RT…

Yes, you can use WebRTC DataChannels for sending custom text/binary data on top of a ICE+DTLS connection. BTW mediasoup supports DataChannels. Any question or comment about mediaso…

I thought that this news was about mediasoup, not about generic WebRTC questions.

PornHub uses mediasoup for live cams.

It's a Node library, yes.

mediasoup (in server side) is a Node.js library or a NPM dependency that you integrate into your Node.js app. Of course it comes with tons of C++ lines but, from the point of view …

Yep, two active developers but being just a set of libraries it's good enough. We also get nice contributions (C++ fixes and optimizations) via PR in GitHub. And we use mediasoup i…

Jitsi is a full application (web app, backend servers) with a specific use case: meetings (similar to Zoom or Google Meet). mediasouop is not an application but a set of server and…

10 users? the cheapest one.

In WebRTC spec (although not super mandatory but the current way to go), the client no longer signals its sending SSRCs into the SDP but a MID and optional RID values (if simulcast…

This is RTP not WebSocket or HTTP. Media servers need a separate port for each RTP communication. A hack could be done to make all WebRTC endpoints to use a single port in mediasou…

Why is that so important? As I said, choosing a specific port is not enough. This is not TLS. An aggressive firewall may drop those TCP connections because there is no TLS data on …

Majority of RTP media server listen into a separate port for each connection. That's how RTP typically works. This is not TCP connections.

> is like sending information at several resolutions and each peer selecting the best one. Well, no. This is not about sending all video layers to all receivers and let them choose…

Not at all.

Again, thanks for the SPAM. And you are wrong. RTP video cannot be sent that way because each receiver must also send back feedback to the sender. RTP protocol is more complex than…

You cannot select a specific listening port for a specific transport, because each WebRTC transport requires, at least, a different listening port in the server: https://mediasoup.…

Thanks for the SPAM. Let's talk about whatever you wish to say.

I thought this news was about mediasoup, not about WebRTC in general. Said that I agree that your scenario is valid without any media server.

We do support TCP ICE candidates for long time: https://mediasoup.org/documentation/v3/mediasoup/api/#WebRtc... > TCP candidate so a TURN server isn't needed at all? This is not tr…

The demo is just a demo. mediasoup is a low level library (no UX into mediasoup). The online demo backend does not have any TURN server. It's obviously recommended to deploy a TURN…