This is an introduction on Janus and its WebRTC features to the ClueCon audience, with a few words on how it can be used to complement FreeSwitch in some interesting scenarios.

1. All roads lead to WebRTC:
an intro to Janus
Lorenzo Miniero
@elminiero
ClueCon – Chicago, IL, USA
August 6th 2019

2. Who am I?
Lorenzo Miniero
• Ph.D @ UniNA
• Chairman @ Meetecho
• First timer at ClueCon!
Contacts and info
• lorenzo@meetecho.com
• https://twitter.com/elminiero
• https://www.slideshare.net/LorenzoMiniero

3. Does ClueCon Weekly count?
https://www.youtube.com/watch?v=dzQhyw1jiaA

4. Does ClueCon Weekly count?
https://www.youtube.com/watch?v=bANmsBaYFN4

5. Before moving on, what’s Meetecho?
• Co-founded in 2009 as an academic spin-off
• University research efforts brought to the market
• Completely independent from the University
• Focus on real-time multimedia applications
• Strong perspective on standardization and open source
• Several activities
• Consulting services
• Commercial support and Janus licenses
• Streaming of live events (IETF, ACM, etc.)

6. Proudly brewed in sunny Napoli, Italy!

7. WebRTC reference architecture: P2P

8. WebRTC reference architecture: P2P

9. Involving a server/application as a peer

10. Involving a server/application as a peer

11. Enter Janus!
Janus
General purpose, open source WebRTC server
• https://github.com/meetecho/janus-gateway
• Demos and documentation: https://janus.conf.meetecho.com
• Community: https://groups.google.com/forum/#!forum/meetecho-janus

12. Modular architecture
• The core only implements the WebRTC stack
• JSEP/SDP, ICE, DTLS-SRTP, Data Channels, Simulcast, VP9-SVC, ...
• Plugins expose Janus API over different “transports”
• Currently HTTP / WebSockets / RabbitMQ / Unix Sockets / MQTT / Nanomsg
• “Application” logic implemented in plugins too
• Users attach to plugins via the Janus core
• The core handles the WebRTC stuff
• Plugins route/manipulate the media/data
• Plugins can be combined on client side as “bricks”
• Video SFU, Audio MCU, SIP gatewaying, broadcasting, etc.

13. Modular architecture
• The core only implements the WebRTC stack
• JSEP/SDP, ICE, DTLS-SRTP, Data Channels, Simulcast, VP9-SVC, ...
• Plugins expose Janus API over different “transports”
• Currently HTTP / WebSockets / RabbitMQ / Unix Sockets / MQTT / Nanomsg
• “Application” logic implemented in plugins too
• Users attach to plugins via the Janus core
• The core handles the WebRTC stuff
• Plugins route/manipulate the media/data
• Plugins can be combined on client side as “bricks”
• Video SFU, Audio MCU, SIP gatewaying, broadcasting, etc.

14. Modular architecture
• The core only implements the WebRTC stack
• JSEP/SDP, ICE, DTLS-SRTP, Data Channels, Simulcast, VP9-SVC, ...
• Plugins expose Janus API over different “transports”
• Currently HTTP / WebSockets / RabbitMQ / Unix Sockets / MQTT / Nanomsg
• “Application” logic implemented in plugins too
• Users attach to plugins via the Janus core
• The core handles the WebRTC stuff
• Plugins route/manipulate the media/data
• Plugins can be combined on client side as “bricks”
• Video SFU, Audio MCU, SIP gatewaying, broadcasting, etc.

15. Modular architecture
• The core only implements the WebRTC stack
• JSEP/SDP, ICE, DTLS-SRTP, Data Channels, Simulcast, VP9-SVC, ...
• Plugins expose Janus API over different “transports”
• Currently HTTP / WebSockets / RabbitMQ / Unix Sockets / MQTT / Nanomsg
• “Application” logic implemented in plugins too
• Users attach to plugins via the Janus core
• The core handles the WebRTC stuff
• Plugins route/manipulate the media/data
• Plugins can be combined on client side as “bricks”
• Video SFU, Audio MCU, SIP gatewaying, broadcasting, etc.

16. Extensible Architecture and API

17. Extensible Architecture and API

18. A quick look at plugins: SIP gateway
https://www.slideshare.net/LorenzoMiniero/janussip-opensips-2017
https://www.slideshare.net/LorenzoMiniero/janusasterisk-astricon-2017
https://www.slideshare.net/LorenzoMiniero/janussip-opensips-2019

19. A quick look at plugins: Audio MCU

20. A quick look at plugins: Video SFU

21. A quick look at plugins: Streaming

22. Beyond C: plugins in Lua or JavaScript!
https://www.slideshare.net/LorenzoMiniero/fosdem2018-janus-lua-plugin-presentation

23. Combining plugins: Webinar example

24. Combining plugins: SocialTV example

25. Combining plugins: the IETF use case!
https://www.slideshare.net/LorenzoMiniero/ietf-remote-participation-via-meetecho-webrtc-meetup-stockholm
https://www.vuc.me/2017/vuc640-ietf-remote-participation-with-lorenzo-miniero/

26. Streaming IETF meetings with Janus
https://ietf.org/meeting/remote-participation.html

27. Streaming IETF meetings with Janus
https://ietf.org/meeting/remote-participation.html

28. Streaming IETF meetings with Janus
https://ietf.org/meeting/remote-participation.html

29. Streaming IETF meetings with Janus
https://ietf.org/meeting/remote-participation.html

30. Streaming IETF meetings with Janus
https://ietf.org/meeting/remote-participation.html

31. Streaming IETF meetings with Janus
https://ietf.org/meeting/remote-participation.html

32. Streaming IETF meetings with Janus
https://ietf.org/meeting/remote-participation.html

33. Simulcasting & SVC
https://www.meetecho.com/blog/simulcast-janus-ssrc/

34. Data channels everywhere!
https://www.meetecho.com/blog/data-channels-broadcasting-with-janus/

35. RTP forwarding as another tool in your belt

36. RTP forwarding as another tool in your belt

37. A target scenario: broadcasting

38. A target scenario: broadcasting

39. Another scenario: remote AI/ML
https://fosdem.org/2019/schedule/event/janus_ml/

40. Another scenario: remote AI/ML
https://fosdem.org/2019/schedule/event/janus_ml/

41. Another scenario: remote AI/ML
https://fosdem.org/2019/schedule/event/janus_ml/

42. Yet another scenario: geographic access

43. Yet another scenario: geographic access

44. Monitoring: Event Handlers
https://www.slideshare.net/LorenzoMiniero/fosdem2017-janus-event-handlers
https://www.slideshare.net/LorenzoMiniero/janushomerhepic-opensips18

45. How do you scale all this?
https://www.slideshare.net/LorenzoMiniero/scaling-webrtc-applications-with-janus

46. Merging soon: multistream!
https://www.slideshare.net/LorenzoMiniero/multistream-in-janus-commcon-2019

47. Janus and Freeswitch
• Janus and Freeswitch actually complement each other nicely!
• Janus has an SFU, SIP-wise it’s an endpoint, etc.
• Freeswitch has an MCU, SIP-wise it’s a complete server, etc.
• Different ways they can talk to each other
• Via WebRTC directly (orchestration of Verto and Janus API)
• Via SIP or other legacy protocols (SIP or NoSIP plugin in Janus)
• Many already using them together
• e.g., https://www.slideshare.net/polysics/clue-con2017 (L. Pradovera)
Warning needed when using WebRTC, though!
• FreeSwitch doesn’t support BUNDLE, Janus requires it
• You’ll need separate PeerConnections if you want audio and video

48. Janus and Freeswitch
• Janus and Freeswitch actually complement each other nicely!
• Janus has an SFU, SIP-wise it’s an endpoint, etc.
• Freeswitch has an MCU, SIP-wise it’s a complete server, etc.
• Different ways they can talk to each other
• Via WebRTC directly (orchestration of Verto and Janus API)
• Via SIP or other legacy protocols (SIP or NoSIP plugin in Janus)
• Many already using them together
• e.g., https://www.slideshare.net/polysics/clue-con2017 (L. Pradovera)
Warning needed when using WebRTC, though!
• FreeSwitch doesn’t support BUNDLE, Janus requires it
• You’ll need separate PeerConnections if you want audio and video

49. Janus and Freeswitch
• Janus and Freeswitch actually complement each other nicely!
• Janus has an SFU, SIP-wise it’s an endpoint, etc.
• Freeswitch has an MCU, SIP-wise it’s a complete server, etc.
• Different ways they can talk to each other
• Via WebRTC directly (orchestration of Verto and Janus API)
• Via SIP or other legacy protocols (SIP or NoSIP plugin in Janus)
• Many already using them together
• e.g., https://www.slideshare.net/polysics/clue-con2017 (L. Pradovera)
Warning needed when using WebRTC, though!
• FreeSwitch doesn’t support BUNDLE, Janus requires it
• You’ll need separate PeerConnections if you want audio and video

50. Janus and Freeswitch
• Janus and Freeswitch actually complement each other nicely!
• Janus has an SFU, SIP-wise it’s an endpoint, etc.
• Freeswitch has an MCU, SIP-wise it’s a complete server, etc.
• Different ways they can talk to each other
• Via WebRTC directly (orchestration of Verto and Janus API)
• Via SIP or other legacy protocols (SIP or NoSIP plugin in Janus)
• Many already using them together
• e.g., https://www.slideshare.net/polysics/clue-con2017 (L. Pradovera)
Warning needed when using WebRTC, though!
• FreeSwitch doesn’t support BUNDLE, Janus requires it
• You’ll need separate PeerConnections if you want audio and video

51. Thanks! Questions? Comments?
Contacts
• https://twitter.com/elminiero
• https://twitter.com/meetecho
• https://www.meetecho.com

52. See you soon in Napoli!
September 23-25, 2019, Napoli — https://januscon.it

53. See you soon in Napoli!
September 23-25, 2019, Napoli — https://januscon.it

54. See you soon in Napoli!
September 23-25, 2019, Napoli — https://januscon.it

55. See you soon in Napoli!
September 23-25, 2019, Napoli — https://januscon.it

56. See you soon in Napoli!
September 23-25, 2019, Napoli — https://januscon.it