aiortc

https://github.com/jlaine/aiortc may be a better option than janus. It's a much simpler to use implementation and is python. quick summary of the acronyms... STUN/TURN/ICE are all related to NAT traversal (ie. when you are behind a router or firewall of some kind and your computer's IP is different from your public IP). The reason you need this is because UDP is not connection-based like TCP. So STUN is a service that helps your computer find its public IP. ICE is a protocol for finding and reporting peer candidates (after they've learned their public IPs via STUN) so they can establish a peer-to-peer connection. TURN is when you reflect the connection off a public server instead of establishing a peer-to-peer connection. SDP is session description...basically information on what media formats and other things each client will accept

If you want real-time data-transmission (for chat, audio or video), what about WebRTC? It's primarily intended to be used in browsers, but there's nothing theoretically preventing you from just using a Python library (e.g. https://github.com/jlaine/aiortc ) that implements the protocols if you wanted.

There have been a few libraries popup that tie libnice + OpenSSL + libsrtp + usrsctp together, it is nice that the stack is all there. Just have to jump through lots of hoops :) The creation of them also seems to be accelerating! I think the P2P excitement has helped a lot. * https://github.com/xhs/librtcdc (This was the first non-chrome one afaik) * https://github.com/chadnickbok/librtcdcpp * https://github.com/jlaine/aiortc * https://github.com/rawrtc/rawrtc * https://github.com/pions/webrtc * https://github.com/nodertc * https://gstreamer.freedesktop.org/data/doc/gstreamer/head/gs... There are also a few that aren't public, I haven't used them directly though. Only by talking to other devs.

There are several examples available from the project's github repo: https://github.com/jlaine/aiortc/tree/master/examples I personally like the "server" and "apprtc" demos as you can easily talk to a browser. They illustrate slightly different things: - "apprtc" relies on a third-party signaling service, and shows you how you can play media from a file / record it to a file, or generate video frame-by-frame. - "server" shows you how you can combine media and signaling into a single Python-based server, and how you can apply image processing on the fly to the received video.

Duly noted, I've opened an issue to track this: https://github.com/jlaine/aiortc/issues/76 aiortc's RTCPeerConnection indeed uses RTCRtpSender.send to apply parameters. This is directly inspired by ORTC: http://draft.ortc.org/#dom-rtcrtpsender-send