View Code? Open in Web Editor NEW

Cutting Edge WebRTC Video Conferencing

License: ISC License

Makefile 0.52% C++ 47.44% JavaScript 9.26% Python 0.20% Dockerfile 0.02% TypeScript 5.84% HTML 0.04% Rust 24.08% C 0.18% Shell 0.31% Roff 1.79% Meson 0.38% Perl 9.94%

mediasoup's Introduction

mediasoup v3

Website and Documentation

mediasoup.org

Support Forum

mediasoup.discourse.group

Design Goals

mediasoup and its client side libraries are designed to accomplish with the following goals:

Be a SFU (Selective Forwarding Unit).
Support both WebRTC and plain RTP input and output.
Be a Node.js module/Rust crate in server side.
Be a tiny JavaScript and C++ libraries in client side.
Be minimalist: just handle the media layer.
Be signaling agnostic: do not mandate any signaling protocol.
Be super low level API.
Support all existing WebRTC endpoints.
Enable integration with well known multimedia libraries/tools.

Architecture

Use Cases

mediasoup and its client side libraries provide a super low level API. They are intended to enable different use cases and scenarios, without any constraint or assumption. Some of these use cases are:

Group video chat applications.
One-to-many (or few-to-many) broadcasting applications in real-time.
RTP streaming.

Features

ECMAScript 6/Idiomatic Rust low level API.
Multi-stream: multiple audio/video streams over a single ICE + DTLS transport.
IPv6 ready.
ICE / DTLS / RTP / RTCP over UDP and TCP.
Simulcast and SVC support.
Congestion control.
Sender and receiver bandwidth estimation with spatial/temporal layers distribution algorithm.
Data message exchange (via WebRTC DataChannels, SCTP over plain UDP, and direct termination in Node.js/Rust).
Extremely powerful (media worker thread/subprocess coded in C++ on top of libuv).