Short introduction to WebRTC at the Amsterdam WebRTC Meetup, March 26, 2014

Organizers and hosts of the evening

Luis

Rianne Bart

Alex

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

Real Time Communicationbetween browsers

An short introduction toWebRTC

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

http://en.wiktionary.org/wiki/intellectual_property

http://en.wiktionary.org/wiki/right

http://en.wiktionary.org/wiki/patent

http://en.wiktionary.org/wiki/trade_secret

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.

http://iswebrtcreadyyet.com/



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

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

Get connected (1)

Webserver+ API’s

Mybrowser

Otherbrowser

1 2

3

5

4

Get connected (2)

1. User clicks button and connects to server2. Server sends signal to callee3. Callee accepts 4. Communication is established5. Audio, video chat transmission starts

Browser API’s for WebRTCBrowser 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

Mybrowser

Otherbrowser

Mybrowser

WebServer+ API’s

mic

webcam

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

Luckily, there ‘s help!Luckily, there ‘s help!

FLASH whenever you use IE or Safari

Demo’s GetUserMedia

?

Questions

?

Wrap up

What will it bring to the user?

Will WebRTC make the world

a happier place?

Without …

with WebRTC

Thanks to our sponsors

Thank you !

What ‘s next?What ‘s next?

We want moreWebRTC!

Where is moreWebRTC?

Ich bin ein Berliner …

… WebRTC Meetup

MondayMay 5, 2014

Join us at theBerlin

WebRTCMeetup

Short introduction to WebRTC at the Amsterdam WebRTC Meetup, March 26, 2014

Internet

Transcript of Short introduction to WebRTC at the Amsterdam WebRTC Meetup, March 26, 2014