Dealing with video conferences with many users, trying to setup your own Meerkat/Periscope, or just want to get WebRTC’s various codecs to work together? You’re going to need to do some media processing - Emil from Jitsi, an open source WebRTC media server, will walk you through the why & how. - Emil Ivov - Atlassian

4. we love WebRTC
because it is p2p

5. better security
lower latency
less hassle
lower cost
BS METERTHEY SAY P2P HAS:
90% BS
25%
75%
25%

6. CONFERE
RECORDING
TALKING TO PHONES
BROADCASTING
RECORD
QUICK CON
NAT TRAVER

7. THE MCUTHE SFU P2P ME

8. THE MCUTHE SFU P2P ME
MI
X

9. THE MCUTHE SFU P2P ME
MI
X
C
ALL ABOUT THE
PERF
A L L A B O U T
INTEROP
ALL ABOUT … NO
SURE

10. THE SFU
ALL ABOUT
THE PERF

11. 20%
1000 video
streams550
Megabitshttps://jitsi.org/videobridge/
performance

12. WORK FOR A
MOBILE?
an MCU only
sends 1 stream
SFU needs tons of bandw
… from a participant perspec
ULD AN SFU EV

13. SIM &
SVC
in a

14. s i m u l c a

15. SVC: SCALABLE

16. SVC: SCALABLE

17. SVC: SCALABLE

18. SVC: SCALABLE

19. SVC: SCALABLE

20. SPACIAL

21. TEMPORA

22. simulcast in
chromeo=- 3407482598521328076 2 IN IP4 127.0.0.1
s=-
t=0 0
a=group:BUNDLE audio video data
...
m=audio 9 RTP/SAVPF 111 103 104 9 0 8 106 105 13 126
...
m=video 9 RTP/SAVPF 100 116 117 96
...
createOf
fer

23. simulcast in
chromeo=- 3407482598521328076 2 IN IP4 127.0.0.1
s=-
t=0 0
...
m=audio 9 RTP/SAVPF 111 103 104 9 0 8 106 105 13 126
...
m=video 9 RTP/SAVPF 100 116 117 96
a=ssrc-group:SIM 3535700627 3169665807 0902838992
a=ssrc:3535700627 cname:localCname
a=ssrc:3535700627 msid:DN4NQ 0a1622a6a67d
a=ssrc:3169665807 cname:localCname
a=ssrc:3169665807 msid:DN4NQ 0a1622a6a67d
a=ssrc:0902838992 cname:localCname
a=ssrc:0902838992 msid:DN4NQ 0a1622a6a67d
setLocalDes
cription
simulc
ast

24. simulcast:
raison d'être
360p
720p
1080p
ndpoint generated bandwidth estimations
draft-alvestrand-rmcat-congestaft-alvestrand-rmcat-remb

25. simulcast:
raison d'être
360p
720p
1080p
ndpoint generated bandwidth estimations
draft-alvestrand-rmcat-congestaft-alvestrand-rmcat-remb

26. 1080p
simulcast:
raison d'être
360p
720p
1080p
ndpoint generated bandwidth estimations
draft-alvestrand-rmcat-congestaft-alvestrand-rmcat-remb

27. 1080p
fiber or cable
simulcast:
raison d'être
360p
720p
1080p
ndpoint generated bandwidth estimations
draft-alvestrand-rmcat-congestaft-alvestrand-rmcat-remb

28. Wi-Fi
720p
simulcast:
raison d'être
360p
720p
1080p
ndpoint generated bandwidth estimations
draft-alvestrand-rmcat-congestaft-alvestrand-rmcat-remb

29. 3g
360p
simulcast:
raison d'être
360p
720p
1080p
ndpoint generated bandwidth estimations
draft-alvestrand-rmcat-congestaft-alvestrand-rmcat-remb

30. 3g
360p
fiber or cable
simulcast:
raison d'être
360p
720p
1080p
ndpoint generated bandwidth estimations
draft-alvestrand-rmcat-congestaft-alvestrand-rmcat-remb

31. 3g
360p
Wi-Fi
simulcast:
raison d'être
360p
720p
ndpoint generated bandwidth estimations
draft-alvestrand-rmcat-congestaft-alvestrand-rmcat-remb

32. 360p
3g
360p
3g

33. noyes no

34. noyes no

35. soonyes soon

36. How about the W3C and
IETF ?
(to be filled in on Thursday)

37. 20%
CPU
1000 video
streams550
Megabit
s