Allow DatagramConnection (ie the RtcTransport web API) to send and receive real SRTP/SCTP When wire protocol is set to kDtlsSrtp, take RTP/RTCP packets passed to sendPackets and SRTP encrypt them in the same way as they would be in a full PeerConnection, without the goofy wrapping in faked RTP headers. Similarly decrypt received SRTP/SRTCP packets, decrypt them and pass up to the client with the original headers inc seq num, ssrc etc. For any other packets, just DTLS encrypt/decrypt, as in SrtpTransport. This allows users of DatagramConnection to be wire-compatible with a standard peerconnection. Bug: chromium:443019066 Change-Id: I3bc3597b84b14fb03f3e7b6668638df0a5d86ef3 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/421782 Commit-Queue: Tony Herre <herre@google.com> Reviewed-by: Harald Alvestrand <hta@webrtc.org> Cr-Commit-Position: refs/heads/main@{#46240}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.
See here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.