Unless you’ve been living under a rock for the last 2 years, you’ve heard of WebRTC. But unless you’re at the bleeding edge of technology within your organization, you likely don’t know a lot about the details of WebRTC, either from the technology or the business-case side. This Workshop, led by one of the world’s recognized authorities on the WebRTC industry, will help you get your bearings on this important subject. The first portion of the Workshop will give you a basic technology tutorial: What is WebRTC, how is it implemented, and what are the current challenges? This will be aimed at familiarizing you with the main concepts of WebRTC, and why it has become such a hot topic. The second portion of the workshop will help you understand the promise that WebRTC holds for the industry as a whole: The developer ecosystem that is arising around WebRTC; the early successes that implementers are having, and how WebRTC is likely to affect the enterprise. You’ll come away from this Workshop with an action plan to take back to your organization, to prepare your enterprise for the impact of WebRTC and to take full advantage of it. The Workshop will be presented by Tsahi Levent-Levi, one of the industry’s most recognized and best-read analysts for the WebRTC space. Tsahi tracks and shapes the WebRTC debate on his own website, Blog.geek.me, as well as on No Jitter and other venues. He is uniquely positioned to offer valuable insights on how WebRTC will impact your organization, and how you can prepare for it.

1. Fundamentals of WebRTC
for the Enterprise
Tsahi Levent-Levi
BlogGeek.Me
@tsahil

2. The NEXT slide is
THE MOST IMPORTANT ONE
you’ll see today
The rest? Just filler for this 3 hours session

3. TheBusyBrain
WebRTC is a Technology
not a Solution

4. Where are we Headed?
1. What is (and isn’t) WebRTC
2. Anatomy, VoIP & WebRTC
3. Where Enterprise Meets WebRTC
4. The WebRTC Ecosystem
remember: a Technology. Not a Solution

5. WHAT IS (AND ISN’T) WEBRTC

6. WebRTC offers real time communication natively
from a web browser
WebRTC is a media engine with JavaScript APIs

7. How Are Calls Made With WebRTC?
1
2
3
4
5

8. Isn’t it Just Like… SIP
???

9. Yes, but without any Signaling

10. So What?
No Plugins No Downloads No Installations No App Store
No SignalingFree (as in BSD) No Patents No Media Eng.

11. What Does it Provide?
• Real-time
• Voice, video and data
• Browser based
• No plugins
• Secured
• Interoperable (between browsers)

12. Why All the Fuss?

13. I heard Internet Explorer doesn’t support it

14. Where?
1.2
Billion
Enabled devices
14

15. Told you Internet Explorer is missing
This will never fly!

16. How Do We Solve Browser Support?
• Ignore
– Offer the service on supporting browsers only
– Videodesk.com isn’t showing the capabilities
– popexperts blocks such browsers from access to the actual service
• Plugin
– Build a plugin for non-supporting browsers
– AddLive and Weemo do that
• Downgrade to “Flash”
– Use Flash where WebRTC doesn’t work
– Apidaze took that approach
• Don’t use WebRTC at all

17. Someone told me mobile is eating up PCs
Why do I need WebRTC there?

18. Mobile and WebRTC

19. Our Routes to Mobile
1. Ignore mobile
Who needs it anyway?
2. Only run on supported browsers
Works well for ad-hoc support/sales use cases
3. Port and pack as an app
Everyone and his wife does that today…

20. A Story of Mobile & WebRTC
Hello Santa offers live one-on-one video calls with
Santa Claus. Calls can be placed on iPhone, iPad,
or any computer with an Internet connection. After
each call the customers gets a Video Souvenir, a
recording of the video call that they can keep for
themselves, or share on Facebook and Twitter.

21. How did this whole thing started?

22. Google Went Shopping
Date Assets Customers Google’s Target
On2 Feb 2010 VPx video codecs Adobe WebM
GIPS May 2010 iLBC, iSAC voice codecs
Voice Engine
Video Engine
Skype, Google,
Yahoo, Avaya, …
WebRTC

23. WebRTC’s History

24. What didn’t we cover?
Codec wars (and big money)
Patent litigation (and bigger money)
ORTC, CU-RTC-Web (and delay tactics)
Lots more

25. ANATOMY, VOIP & WEBRTC

26. The Anatomy of a VoIP Solution
Infrastructure
Signaling
Media Processing
Codecs
Source:

27. Bounderies of WebRTC
Infrastructure
Signaling
Media Processing
Codecs
Source:

28. Who took my signaling?

29. Signaling options in WebRTC
Technique Who is it for? Why?
SIP over WebSockets VoIP diehards It connects to their “existing” backend
XMPP/Jingle XMPP fanatics Because it does XMPP
WebSockets Fashionista WebSockets is the latest and greatest in
client-server web communications
XHR / Comet Ubiquity seekers Because WebSockets isn’t supported
everywhere
Data Channel Thrill seekers WebRTC’s data channel is an unexplored
territory that can be used for signaling

30. WebRTC’s Protocol Stack
High Performance Browser Networking / Ilya Grigorik

31. Transport
• Media transport based on SRTP
• No RTP at all
• “Latest and greatest” of RTP got mandated
– AVPF
– Multiplexing
– Etc.

32. Media
• No Mandatory to Implement (MTI) video codec. Yet…
Codec Use Specification
G.711 Narrow band, selected for
PSTN and VoIP interworking
RFC 3551
Opus New flexible audio codec.
Narrow to wideband
support; Support for
Speech & Music
RFC 6716
DTMF Telephone events RFC 4733
VP8 Google’s open source
codec
RFC 6386
H.264 Video codec (MPEG-LA
licensing)
RFC 6184

33. NAT Traversal
• “Almost” like SIP
– STUN – Enables announcing your public IP addresses during the
negotiation phase of a session
– TURN – Relays all media via a TURN server that is visible to all parties in
the session
– ICE – Decide on the best solution to send media (direct, STUN or TURN)
• Trickle ICE – Speed up the process of the ICE protocol by
parallelizing its handling of candidates
– New specification, implemented in WebRTC
– Slowly trickling into SIP and XMPP

34. Security isn’t Optional
Implement
Service
Check Impact of
Encryption
Deploy
Service
Implement
Security
Implement
Security
Buy Certificate for
HTTPS domain
Deploy
Service
Traditional VoIP WebRTC

35. SIP versus WebRTC
Protocol WebRTC SIP
Market Websites and web apps
Voice and IMS
deployments
Media SRTP RTP or SRTP
NAT traversal STUN, TURN, ICE STUN, TURN, ICE
Media negotiation SDP SDP
Voice codecs G.711, Opus
G.711, G.7xx, AMR-xx,
Speex, SILK, Opus, …
Video codecs VP8 H.263, H.264
API Java Script Unspecified

36. APIs or Interoperability?
Software
Professionals
Academia
Hobbyists &
Enthusiasts
Mobile
Developers
Device
Manufacturers
Infrastructure
Vendors
WebRTC Traditional VoIP

37. A Change in Mindset
Brain: How are going to get the Earth to lose weight?
Pinky: I know! We can get everyone to go on a diet!
Brain: Diets don't work.
Pinky: Not even if you call them 'A Whole New Way of Eating?‘
Brain: No.

38. WHERE ENTERPRISE MEETS
WEBRTC

39. The Innovator’s Dilema
Time
Product
Performance
Low end
High end

40. The Innovator’s Dilema
Time
Product
Performance
Low end
High end
WebRTC’s points
of disruption:

41. 3 Enterprise Domains
• Contact Center
• Unified Communications
• CEBP

42. Contact Center

43. The Contact Center: A Tale of Two Vendors

44. The Contact Center: A Tale of Two Vendors

45. Who will be left standing?
CRM vendor or Telephony vendor?

46. Contact Center
Related “Use Cases”
4

47. Inbound Calling: “External”
• Reduce friction
• Add context
• Click-2-Call example:

48. Inbound Calling: “Internal”
• Enable agents to receive calls inside the browser
• Route calls using Java Script…
• Tighter integration between CRM and VoIP
• Different approaches:

49. Outbound Calling
• Simplicity
• Maintaining CRM records

50. Amazon Mayday
• One way video
• Bidirectional voice
• Screen sharing
• Remote control
• 15 seconds average wait time
• From a company that:
– Had no real-time support to speak about
– Controls the end-to-end experience

51. Unified Communications

52. “
What Unified Comms?
Checking the calendar for this week I see that I have
11 UC meetings enabled on four different UC
platforms – only one of which my employer
supports directly.
Joseph Williams
UC Strategies: http://bit.ly/1dplIAo

53. The World is Fragmenting Further
BYOD OTT

54. Meantime in the Consumer World…
0 200 400 600 800
Telefonica
America Movil
Vodefone
Singtel
China Mobile
Viber
WeChat
Skype
Line
Whatsapp
Millions of users

55. What Roles can WebRTC Play in UC?
1. Put WebRTC in the MCU
– Any video call from WebRTC into the enterprise goes through the MCU
– Takes up ports, and doesn’t realize the power of WebRTC
2. Put WebRTC in the SBC
– A gateway of sorts, but with “improved” security
– Still not using the power of WebRTC
– Also – WebRTC doesn’t have any real use for an SBC
3. Use a Gateway for WebRTC
1. Works, but still – not using the power of WebRTC

56. Why not Reverse the Picture?
• Place WebRTC at the heart of the network
• Place SIP and H.323 at the edges instead
• Can this bring back control of UC to the enterprise?

57. The Google Elephant Anyone?

58. CEBP
(context enabled business processes)

59. Any Future in Voice?
Source: STL PartnersEU5: UK, France, Germany, Spain and Italy
EU5 Mobile Services revenue already down 10%
from 2009 peak

60. Which Call Costs More?

61. There is $$$ to be made in context

62. A Few Examples

63. Context Requires APIs
& WebRTC is… an API

64. THE WEBRTC ECOSYSTEM

65. Vendor Types in the Ecosystem
2nd Market
Vendors
Tooling
WebRTC
Core
Repurpose

66. Browser Vendors
• Google & Mozilla
• But also Vidyo
– Contributed SVC to the
WebRTC ecosystem
• & Cisco…
– OpenH264 for WebRTC
• Microsoft & Apple missing
– How does it affect WebRTC’s
future?
– How does it affect IE & Safari
market share?
2nd Market
Vendors
Tooling
WebRTC
Core
Repurpose

67. Tooling
• Providing infrastructure and
“shortcuts” for developers
• WebRTC API vendors: Tropo,
AddLive, TokBox, Priologic,
OpenClove, …
• Services vendors: XirSys,
PubNub, …
• Infrastructure vendors:
GENBAND, Dialogic, …
• SDK vendors: Digium,
Eyeball Networks, …
2nd Market
Vendors
Tooling
WebRTC
Core
Repurpose

68. Vendors
• Providing services
based on WebRTC
• Develop either directly
on top of WebRTC or via
tooling vendors
• Target the end users via
a multitude of use
cases
2nd Market
Vendors
Tooling
WebRTC
Core
Repurpose

69. 2nd Market
• Vendors adopting other
vendor’s end user
solutions
• TNW Academy’s story
2nd Market
Vendors
Tooling
WebRTC
Core
Repurpose

70. Repurposing WebRTC
• Reusing WebRTC’s
components to fit in
other places, treating it
as a pure media engine
• Vonage – going mobile
with an OTT app
• M5T – Client SDK for
developers
2nd Market
Vendors
Tooling
WebRTC
Core
Repurpose

71. Where are
we Now?

72. Shifts in the Ecosystem
Customer-facing
Services
Tooling
Vendors

73. Use Cases
(& business models)

74. Top Use Cases
0
20
40
60
80
100
120
140
160
Mar ‘14

75. Business Models in “Search Mode”
Subscription Unknown Device
selling
Project
based
Pay as you
go
None Freemium Licensing Revenue
sharing
Support
Mar ‘14

76. What was it you wanted us to remember?

77. TheBusyBrain
WebRTC is a Technology
not a Solution

78. THANK YOU
Tsahi Levent-Levi
tsahil@bloggeek.me
@tsahil