WebRTC vs VoIP: IIT-RTC Oct 2013
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

WebRTC vs VoIP: IIT-RTC Oct 2013

on

  • 1,885 views

Reid Stidolph's presentation at IIT-RTC Conference in Chicago. It contrasts WebRTC to VoIP as it is implemented today.

Reid Stidolph's presentation at IIT-RTC Conference in Chicago. It contrasts WebRTC to VoIP as it is implemented today.

Statistics

Views

Total Views
1,885
Views on SlideShare
1,544
Embed Views
341

Actions

Likes
3
Downloads
41
Comments
0

4 Embeds 341

http://getvoip.com 209
http://www.scoop.it 94
https://twitter.com 36
http://plus.url.google.com 2

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Intro <br /> Compare and contrast WebRTC, and VoIP as it’s deployed today. <br />
  • The VoIP universe as it exists today is very diverse and vibrant. <br /> VoIP began for many as IP networks began to prevail within the various galaxies <br /> In many cases, VoIP was introduced for cost savings replacement to telco <br /> VoIP saw fast growth in the early days in the Fixed line and business VoIP space…innovators like asterisk, vonage <br /> Some of the more rapid expansion, by telco standards, is taking place in the mobile and UC arena. <br /> It’s important to note that the network environments and requirements, the acronyms, the use of protocols…can all be very different <br />
  • Begins with a singularity in focus: the Web <br /> Rapid expansion <br /> Relatively few endpoint types, accessed by JavaScript <br /> Single largest install base of an interoperable RTC media stack <br /> Rapid expansion like this is bound to cause some disruption <br />
  • To understand where someone is going, you can look at where they’ve been <br /> To begin to contrast the two, we can first look at what the user interface to the two worlds has been <br />
  • These are harder to quantify and characterize <br /> Undercurrents like bigger network vs. bigger client highlight this <br /> While they are difficult to characterize, they manifest themselves in the technologies that align on one side or the other <br /> As the two worlds collide once again, it is helpful to have a pragmatic appreciation for what each does well, and maybe not so well <br />
  • Browser crashes, tab closes, or the network changes…what happens? <br />
  • That’s a look at just a couple of specific challenges for those looking to bring VoIP/Telco like qualities to WebRTC…and vice-versa. <br /> But there are major industry shifts taking place as a result of the gaps between VoIP, and the rapidly expanding WebRTC…things are happening to fill the void. <br /> An immediate push for existing, traditional RTC services to extend what they do to the web. <br /> This implies heavy requirements for elements with GW functionality <br /> SBCs make a good choice as they are already deployed in many RTC architectures to handle things like security and compliance…WebRTC IWF becomes super-set of this <br /> VoIP network architecture for a while has been moving toward virtualization, and becoming more web-like…this trend has likely seen acceleration as a result of WebRTC <br /> On the web side, deployments will need robust tools and techniques, beyond the scope of a simple GW, or static web server, to handle the advance call scenarios like rehydration and mobility <br /> Toolkits, toolkits, toolkits…those wanting rapid service creation and prototyping can do so with minimal investment <br /> Web based services could be subject to compliance obligations, forcing them to scale and handle media <br /> The tools of WebRTC will likely move outside of the “web” as well <br />
  • So that provides on contrast of WebRTC and VoIP as it’s deployed in enterprises and service providers today <br /> For you technologists, as these worlds expand, there is sure to be no shortages of unique, fun, technical challenges found where these universes collide and mesh. <br />

WebRTC vs VoIP: IIT-RTC Oct 2013 Presentation Transcript

  • 1. WebRTC vs. VoIP What’s New? What’s Different? reid.stidolph@oracle.com @reidstidolph reidstidolph@gmail.com http://www.linkedin.com/in/reidstidolph
  • 2. Overview Level-Set Similarities Technical Differences Architecture Differences Principle Differences Shifts in RTC
  • 3. Voice Over Internet Protocol ● “VoIP” a Broad term ● Grown to encompass multimedia, not just voice ● Diverse protocols ○ some well defined standards, some de-facto, some proprietary ● Used in a variety of networks ○ IPv4, IPv6, Public Internet, Private LANs, etc. SI P
  • 4. The VoIP Universe IM S UC IP i l e Vo Mob Fixed Line Con sum er s VoIP es Busin VoI P
  • 5. Web Real Time Communications ● Plugin-less RTC Media engine in the Browser ● Purpose built for the World Wide Web ● Collaborative W3C and IETF standardization ● RTC as a feature, not necessarily the service or application
  • 6. WebRTC Universe 1B devices Supported in 1Q14
  • 7. User Experience Legacy 100 Years of Telco Reliable, Secure, Resilient 20 Years of Web Rich, Dynamic, Innovative
  • 8. VoIP and WebRTC Similarities ● Transmission of communication data between Users in real-time ● Use RTP, SDP O/A ● G.711 ● Run over IP networks
  • 9. Technical Divide Signaling Transport Media Description Undefined SIP XMPP H.323 WebSock BUNDL E DTLS -S Media Transport Network ets R TP ux RTP-M C RT eb W Signaling Protocol VP8(?) H.264 AMR-WB Opus P HTT Vo IP Codecs T CP Traditional SDP MSID TURN Data Channels ICE STUN UDP TLS MSRP UDP IPv4 / IPv6 RTP Unique Tr ansport per Strea m SDES-SRTP
  • 10. Architecture DB DB AS WS AS WS AS WS WS LB-L LB-G VS Internet
  • 11. Principle Differences
  • 12. Identity Telco ID Web ID User-Centric Network-Centric Identity Management
  • 13. WebRTC Mobility and Resilience: More Needed Web App has no control over network changes • Rehydration - automatically reestablish handover App App Failure Reconnect App lost sessions • Restore call/session after browser refresh/crash • Network handoff • Device handoff
  • 14. Shifts in RTC: Create and Extend RTC Extension, WebRTC enabling existing comms WebRTC as a new edge access network Network evolutions toward NFV, Telco-OTT Security, Interoperability, Reliability App creation toolkits for rapid service creation, prototyping Media scaling, compliance Advance session handling
  • 15. Thank You! reid.stidolph@oracle.com @reidstidolph reidstidolph@gmail.com http://www.linkedin.com/in/reidstidolph