This document outlines the agenda for a WebRTC event, including presentations on building video conferencing applications, unlocking the telecom world with WebRTC, market solutions, and applications of WebRTC. The event will also provide a short introduction to WebRTC, covering its history and how it allows real-time communication directly in browsers without plugins through APIs for audio, video, and data channels. A demo of the GetUserMedia API will be shown.

2. Organizers and
hosts of the evening
Luis
Rianne
Bart
Alex

4. WebRTC presentations
-1- Welcome and introduction + demo GetUserMedia (Bart)
-2- Remote instructions (Fabian)
-3- Building a video-conferencing application (Jeroen)
PAUZE
-4- Unlocking and connecting the telecom world (Luis en Philippe)
-5- The market and WebRTC solutions providers (Alex)
-6- Where to apply WebRTC? (Bart, Alex)
-7- Wrap-up (Bart en Alex)
BORREL

5. Real Time Communication
between browsers
An short introduction to
WebRTC

6. Until now, some history
• Skype, MSN, Lync, video
conference systems, Unified
Communications (UC)
– Definition UC: From one interface/screen switching modes of
communication without changing screens or devices
• Proprietary owned implementations
– Manufactured exclusively by the owner of
intellectual property rights, as with a patent or trade secret.
• Expensive and not freely available
• Communication is server based

7. Initiative
• Promoted by Google Chrome team since 2009, the W3C
webRTC WG and the IETF RTCweb WG
• Specification / W3C Editor's Draft 21 March 2014
• WebRTC is open source project
• Manage multimedia communications
• Simple API’s in Javascript
• Multi platform and multi device
• WebRTC specs built into browsers (see http://
iswebrtcreadyyet.com/)
• Now (2014) many suppliers offer WebRTC solutions and
numbers are growing.

9. The promise of WebRTC
WebRTC:
• No plugins
• No downloads
• No App stores
• No patents
• No installations
Multi media RTC for:
• Audio
• Video
• Data
Using RTC any browser can call any other browser

10. One-click technology
On webpage in browser:
• Click here to talk to your customer support
• Click here to see your colleague
• Click here to join video conference

11. Get connected (1)
Web
server
+ API’s
My
browser
Other
browser
1 2
3
5
4

12. Get connected (2)
1. User clicks button and connects to server
2. Server sends signal to callee
3. Callee accepts
4. Communication is established
5. Audio, video chat transmission starts

13. Browser API’s for WebRTC
Browser supports WebRTC using API’s:
• GetUserMedia
– To access and control microphone and
camera hardware
– Must be allowed by user (opt-in)
• PeerConnection
– Establish connection and set up context like
security and codecs
• DataChannels
– Provide peer-to-peer connection
– “Data part of WebRTC”
API = Application Programming Interface
My
browser
Other
browser
My
browser
Web
Server
+ API’s
mic
webcam

14. Role of the Webserver
• WebRTC is a webservice  webserver needed
• Acts as the central control point
• Webserver handles button clicked by user to join
video conference
• Webserver is needed to establish the connection
between the browsers (peers)
• Webserver does not handle the data part of the
communication between the browsers

15. http://iswebrtcreadyyet.com/

16. Luckily, there ‘s help!
FLASH whenever you use IE or Safari

17. Demo’s GetUserMedia

18. ?
Questions
?

19. Wrap up

20. What will it bring to the user?
Will WebRTC make the world
a happier place?

21. Without …

22. with WebRTC

24. Thanks to our sponsors

25. Thank you !

26. What ‘s next?

27. We want more
WebRTC!
Where is more
WebRTC?

28. Ich bin ein
Berliner …
… WebRTC
Meetup

29. Monday
May 5, 2014
Join us at the
Berlin
WebRTC
Meetup