WebRTC Workshop 2013 given at the IMS World Forum


Published on

WebRTC Workshop given at the IMS World Forum

Published in: Technology, Business

WebRTC Workshop 2013 given at the IMS World Forum

  1. 1. WebRTC WorkshopThe HTML5 Real-Time WebApril 22nd 2013Pre-conference Workshop for the IMS World ForumAlan Quaylealan@alanquayle.comwww.alanquayle.com/blogJose de Castrojdecastro@voxeolabs.comwww.voxeolabs.com4/21/2013 © 2013 Alan Quayle Business and Service Development 1
  2. 2. Objectives• Bring together deep technical and deep business thought leadership onWebRTC with Jose de Castro, Alan Quayle, and many of the audience toproviding attendees with a unique independent workshop.• Provide a deep-dive quantified analysis of the WebRTC status, enablingattendees to understand what is likely to emerge over the next 18months to 2 years, in this complex rapidly emerging ecosystem andwhat it will mean to their business.• Provide attendees with a series of WebRTC demonstrations, to sharetheir experiences on implementing WebRTC, and provide amplenetworking opportunities at the end of the workshop to discuss andconsolidate what has been learned through the day.4/21/2013 © 2013 Alan Quayle Business and Service Development 2
  3. 3. Structure (1 of 6)• Registration• 09:30 - Introduction to WebRTC and Initial Market Reviewo What is it and what it is not,o Cutting through the mis-information and hypeo Non-technical introductiono Web browser implementation statuso Taxonomy of suppliers / service providerso Codecs and devices - is certification necessary?o What is Googles aim?• 10:30 Standardization deep diveo Standardization processo Current statuso Battles and likely outcomeso IETF and RTCWEB documents
  4. 4. Structure (2 of 6)• 11:30Technology deep diveo Peer connect APIo Setting up local media and media flowo Protocolso WebRTC triangle / trapezoido SIP, Jingle and the PSTN.• 13:00-14:00 Lunch• 14:00 What WebRTC means to Service Providers and IMS:o Extending enhanced communications services to web browserso Impact on OTT (Over The Top) and existing voice, messaging, video and VASo Impact of device complianceo Customer experiences and behaviorso Revenue, churn and relevance impacts• 14:30 What WebRTC means to enterprises:o Impact on Unified Communication and the Contact Centero Impact on companys websiteo Security and operational issueso Potential cost savings and innovations
  5. 5. Structure (3 of 6) DEMO TIME 15:00-17:00+• Demo Time will be divided into 2 sessions, its aim is to be informaland provide ample networking opportunities for attendees toconsolidate their learning from the workshop:• Demo presentation to the group: each demo will be 5 minutes long,and 5 minutes for questions; and• Demo one-on-one: attendees can chat one-on-one with the demopresenters, notionally 30 minutes but can run on into discussions atthe bar through the evening.
  6. 6. Structure (4 of 6) DEMO TIME 15:00-17:00• Zingaya (Call button for websites)o Embed a Call button into the website. Visitors can click that button and the call isforwarded to the website operators preferred land-line or mobile phone. All that isrequired is a website; all the visitors need is a browser and microphone.• Voxeo Labs (Ameche (new IMS/Web services), Tropo (leading call control API),Phono (Web comms innovation)). They will demo Phono’s three types ofidentity:o Anonymous Identity: user lands on web site and is able to call directly into the contactcentero Web Identity: use your web identity (twitter, foursquare, etc) to call each other.o Telco Identity: Phono sessions can attach to the telco network and assume the realidentity (phone number) of the subscriber, allowing calls to be routed to both the mobileand the browser simultaneously.• Telestaxo Provides a complete stack from the client-side with Javascript JAIN SIP JS and WebRTCas well as the server side with our SIP Over WebSockets. The demo will be a WebRTCvideo conferencing and IM.
  7. 7. Structure (5 of 6) DEMO TIME 15:00-17:00• Solaiemes WebRTC to Rich Communication Suite demoo Demonstration of RCS messaging and WebRTC to access to mediacomponents of devices to revamp the value of PSTN (and also mobile) lines.Shows how Unified Communications could be built just a mash-up ofstandards and APIs.• Quobiso Their approach to WebRTC is based on QoffeeSIP, a complete open sourceJavascript SIP stack that can be used in a website to exploit all the multimediacapabilities of WebRTC technology. Thanks to QoffeeSIP they have developeda corporate WebRTC webphone that can interop with different networkdevices; this webphone is going to be released at IMS World Forum event.• Huawei leading NEPo WebRTC / RCS insurance application demo
  8. 8. Structure (6 of 6) DEMO TIME 15:00-17:00• Drum by NetDev (conference calls and online meetings)o Allows providers of fixed, mobile and next generation VoIP services to deliver audioconferencing as a direct, branded service. Hosted within your IP network on yourservers, Drum audio conferencing is a standalone software solution with an integratedmedia server.• Bistri (Social Video)o Video chat with fun video effects, take screenshots of calls, share them with friends orsocial networks. Bistri runs in the browser, so theres no need to install additionalsoftware or plugins.• apidaze.ioo Is a cloud communications API for developers with tools for building web or mobilecommunication services, with a special focus on WebRTC. The demo will show how aweb developer can easily use the regular WebRTC API to place calls to external numbersand audio conference rooms accessible from the PSTN too, using a simple rawWebSocket connection that carries JSON text.
  9. 9. Introduction to WebRTC andInitial Market Review
  10. 10. What The Geeks SayOpen, Nothing ProprietaryNo Plugs-InsMulti Platform / Device
  11. 11. Real-time stuff for yourbrowser with no plug-ins
  12. 12. M2M and Telematics
  13. 13. Surveillance& Monitoring
  14. 14. Lots &Lots &Lots ofDevices
  15. 15. Embedding CommunicationsEverywhere!
  16. 16. Codec WarsOpus,VP8G.711,AMR-WB,EVS,H.264
  17. 17. Browser GetUserMedia PeerConnection DataChannelChrome Yes Yes Q2 ‘13Chrome for mobile Yes (March ‘13) Yes (March ‘13) Q2 ‘13Firefox (desktop) Yes Yes Yes (first one)Firefox (mobile) Yes Yes Yes (first one)Opera Yes H2 ‘13 2014Opera Mini H2 ‘13 2014 2014IE (desktop) Chrome Frame /2014Chrome Frame /2014Chrome Frame /2014IE (mobile) 2014/2015 2014/2015 2014/2015Safari (desktop) 2014/2015 2014/2015 2014/2015Safari (mobile) 2014/2015 2014/2015 2014/2015WebRTC is NOT Everywhere
  18. 18. Lies, Damned Lies, and Statistics
  19. 19. Regardless IE Matters
  20. 20. Mobile is Even More ComplexNative browser Natively in OS 2nd browser 3rd party SDK
  21. 21. BusinessTechnology
  22. 22. BusinessTechnologyLatencyEfficiencyResiliencePerformanceImplementation ComplexitySupporting DevicesEcosystem SupportCustomer NeedsInteroperabilityUse CasesIPR
  23. 23. 30“Given the ability to deliver a royalty-freeplatform with no compromises on quality, wesee no reason to include mandatory royalty-bearing codecs.”“H.264 support is a requirement in some regulatoryframeworks, such as emergency services. AMR narrow-bandis playing a key role in mobile telephony and has a hugefootprint.”“G.711 is universal, unencumbered, and widely implemented.A mandate for Opus will limit initial RTCWeb clients to usesoftware-based codecs”“We would like to recommend AMR-WB andEVS, since we expect them to be available inmobile chipsets.”
  24. 24. Optional Codec Diversity will Reign
  25. 25. Codec Wars• G711a/u (RFC 3551): supported by all the devices. Needs to use a lot ofbandwidth.• DTMF tones (RFC 4733, updates RFC 2833): needed for interactions withseveral systems (for instance IVRs).• Opus (RFC 6716): bitrate variable, low latency and high quality for human voiceand music. Specially designed for real time communications.• In order to interact with VoIP systems, in several scenarios, it will needtranscoding or interworking of DTMFs (RFC 4733-> INFO, RFC 4733-> in-band,etc).• Can’t we just have both G.711 AND Opus? YES!!!!Regardless Transcoding Will be Needed
  26. 26. And With Transcoding Comes33DelayThird PartiesPacket LossQuality LossCost
  27. 27. H.264H.265VP8VP9Can’t we just have both H.264/5 AND VP8/9?Video Battle is Getting Nowhere
  28. 28. There’s No Approval Process
  29. 29. In The Limit Which Browser Gives you the BestExperience?
  30. 30. Device base supporting WebRTCCopyright Disruptive Analysis Ltd2013Feb 2013MillionSource: Disruptive Analysis WebRTC Strategy Report, Feb 2013Definitions & methodology in report - See disruptivewireless.blogspot.com for details05001000150020002500300035004000TabletsSmartphonesPCs
  31. 31. The WebRTC Train has left the stationand it isn’t going to wait for Telecom
  32. 32. WebRTC is a car without wheels!
  33. 33. WebRTC Triangle• Both browsers running the same web application from web server• Peer Connection media session is established between them• Signaling is not standardized, could be SIP, Jingle, proprietary.Uses HTTP or WebSockets for transportWeb Server(Application)Browser M(Running HTML5 Applicationfrom Web Server)Browser L(Running HTML5 Applicationfrom Web Server)Peer Connection (Audio, Video, and/or Data)40Intro to WebRTC February 2013The wheels!
  34. 34. The Beauty and Value of WebRTC iswhen we mash it up with other stuff
  35. 35. Keep Calm andDo SOMETHING(Just NOT THROUGHTHE GSMA or TMF)HMS Government Advisory
  36. 36. Standardization Deep Dive(c) 2012 Alan Quayle Business and Service Development
  37. 37. Technology Deep Dive(c) 2012 Alan Quayle Business and Service Development
  38. 38. What WebRTC Means to ServiceProviders(c) 2012 Alan Quayle Business and Service Development
  39. 39. NetHead CustHeadOur Industry’s Multiple Identity Disorder
  40. 40. A Telcos Two Unique Assets
  41. 41. Impact of WebRTC?• Voice becomes just like all your other communications: organized into yourpreferred social or office tools.• It will be important for the IMS/RCS world to inter-operate with theWebRTC world, currently these browsers will be a closed book to IMS. ForRCS to become pervasive, it cannot remain trapped in phones that haveimplemented the IMS/RCS client.• For all the OTT (Over The Top) applications, they can now use their"directory service" i.e. your list of contacts also using their service to enableViber / Skype / Whatsapp everywhere. On your PC, smartphone, tablet, TV;and they can offer chargeable services without Apple taking 30%.• As long as youre data connected, communications is in the cloud, peopleneed only break out to PSTN when the other person is not data connected,or the call quality is too low due to their internet connection. PSTNbecomes the communications path of last resort!
  42. 42. Impact of WebRTC?• The companys website now becomes its call center front end. A weblogbecomes your personal communications assistant.o Lots of start-ups in this space• Communication service aggregators save customers running multiple clientson their phone, that would run in the cloud and be controlled from thebrowser.• Click to call doesnt require an operators voice network, just access to theinternet.• Communications becomes like using any application on a smartphone,users can add features, capabilities, people throughout a call, e.g. N-waycalling finally becomes simple and obvious with a simple point and swipe.• Directory services become critical sources of value in connecting all thedifferent IDs: telephone numbers, SIP IDs (IDentifier), web session IDs,other OTT IDs, etc.
  43. 43. Impact of WebRTC?• VAS (Value Added Services) leaves telco. Any web developer can create value andsolve problems for customers, it the customer who will decide, and those developerswho fail fastest win the innovation race.• Advertising finally enters the communications space, opening up business modelinnovation.• New CRM (Customer Relationship Management) methods: click from email, fromwebpage, from app, from TV. The ability to communicate becomes embedded inmost transactions.• QoS (Quality of Service) remains an issue, but for the people using Vonage and Skypeover the years will attest, QoS is rarely an issue.• Your phone number is no longer relevant anymore. Its a gateway to the past.Customers will only know the PSTN is involved because of the poor audio quality(G.711) – BUT it is the customers only unique ID that they own.• Gaming becomes interesting as all the devices become controllers using gesturecontrols as well as the more traditional methods for network-based games.
  44. 44. Other Telco Impacts• Impact of WebRTC on IP Messagingo No need to for a messaging client to be downloadedo Unified communications across voice, video and datao Integrated experience across the web and communications client• Opportunitieso Integrated chargingo Bundle APIs: WebRTC, RCS API, payment API, Call Control APIso QoS for those willing to pay (those running their business on your network)• QoS API? NO! keep that for YOUR SERVICESo Extend network services over the webo Enhance enterprise Unified Communication offerso Enhance OTT? Why they’re competitors!o Gateway for the WebRTC codec messo Web phone for existing customers
  45. 45. Key Points• Voice traffic is going to be through the web• Browsers are the new endpoints• A website of a company can be the call center• An individual’s website (Facebook Page) their communicationsassistant• Security, identity and privacy are very importanto Telephone number is not important unless operators pull their finger out!• New business opportunities abound
  46. 46. DO Communicationsbetter thaN thecompetitionELSE BE AN ISPHMS Government Advisory
  47. 47. What WebRTC Means to Enterprises(c) 2012 Alan Quayle Business and Service Development
  48. 48. WebRTC and the Enterprise• Enterprise is both excited and confusedabout WebRTCo Lower communication costso Lower IT costs as fewer clients to maintain?o Better home and mobile comms that areintegrated with corporate systemso New customer communications options• Confusion arises fromo How to integrateo What needs to changeo How does it work with legacy devices likedesktop videophones, mobile clients, desktopphones, Microsoft Lync, Cisco UC, etc.o What about our corporate firewall, what aboutour SBC?
  49. 49. What Enterprises are Saying in Interviews on WebRTC“WebRTC can lower our communications costs by 30%”“WebRTC will finally give us a workable video communication solutionacross all employees”“WebRTC can make our contact center integrated into all channels, e.g.Web and Mobile, improving customer service.”“WebRTC can improve collaboration both internally and with ourpartners as it just works between browsers.”“WebRTC appears to be not part of the Telco’s offer, it is OTT.”“WebRTC is confusing, it doesn’t work in most browsers.”“WebRTC looks like a lot of hype, will it go the same was as VoIP?”“WebRTC’s security, private, and ability to get hacked remain unclear”“WebRTC will be killed by Microsoft!”
  50. 50. IT’s Technical Concerns• Open standards makes it easier to hack• Clientless, plugin-less browser audio and video for real-time communications means we’re not dependent onbrowser software suppliers• Open-source codec• ICE/STUN NAT transversal does not work all the time• SRTP (Secure Real-time Transport Protocol) –configuration and SSL certification issues• No rules on signaling protocol – security issues?• Multiplex RTP and RTCP on single port – managementissues?• Multiplex audio and video on a single port – managementissues?
  51. 51. Understanding Old-IT• Hardware endpoints with hard to upgrade software• Few soft clients tied to the PBX• Limited codec support, generally H.26x for video• No experience with ICE, STUN, and STRP• RTCP shall be on the RTP port +1• Audio and Video are managed separately• Look how long BYOD is taking• Skype blocked, Facebook blocked,• WebRTC blocked!!!!!!
  52. 52. Typical Large Enterprise DeploymentSBCRouterDesktop NetworkTelepresence Network
  53. 53. IT Generation GapMultiplexedMediaSTUN / ICEVP8RTP/RTCPSeparatedNO STUN /ICE!!!!H.26x
  54. 54. The Solution:A Gateway• Signaling Gatewayo SIP stack in JavaScript?o Break to SIP at the Gateway• De-ICEo Validate SDP ICE candidates• De-Multiplex Media• STUN Binding Handlingo Response to STUN bindings onRTP channelso Validate• Transcoding
  55. 55. Use Cases• Social Media and CRM Integration• Video Conferencing to any device• Inbound Click to call a New channel• Can be deploy by outsourcers• Calls in internal directories
  56. 56. In Summary• Enterprise is interested in WebRTC BUT…• Some Enterprises change even slower than Telcos….• If Telco’s don’t help them, they will go to other service providers• Gateway as a Serviceo Signaling Conversiono Media Interworking
  57. 57. Keep Calm andDo SOMETHING(Just NOT THROUGHTHE GSMA or TMF)HMS Government Advisory
  58. 58. http://webrtcbook.com65Intro to WebRTC February 2013
  59. 59. What WebRTC Means to Enterprises(c) 2012 Alan Quayle Business and Service DevelopmentDEMOTIME