Pervasive Video with WebRTC Technology Praveen Chintala, Practice Architect BRKCOL-2556

Size: px

Start display at page:

Download "Pervasive Video with WebRTC Technology Praveen Chintala, Practice Architect BRKCOL-2556"

Denis Patrick
6 years ago
Views:

2 Pervasive Video with WebRTC Technology Praveen Chintala, Practice Architect BRKCOL-2556

3 Agenda What is WebRTC? WebRTC Evolution Architecture Standards WebRTC Browser Support Transition To Cloud & Security Interoperability with Enterprise Communications Platforms WebRTC Solutions WebRTC Use Cases & Demo Open Dialog, Polling & Q&A

4 WebRTC, Video Transition & Market Trends

5 What is WebRTC What is WebRTC: WebRTC is an API definition being drafted by the World Wide Web Consortium (W3C) It is a free, open project that enables web browsers with Real-Time Communications (RTC) capabilities via simple JavaScript APIs What is the merit of WebRTC: WebRTC enables applications such as voice calling, video chat and P2P file sharing inside the browsers without plugins (or separate clients)

6 Interactive Voice and Video in your Bowser Today... Sales Department

7 But Proprietary no interoperability Requires 3rd party plugins Difficult to deploy (permissions, etc...) Not available on all platforms, Mobile - ios & Android Needs to be Updated Native Browsers cannot support media (Voice & Video) Viruses / malware / industrial spying

Video Transition - Market Trends Dramatic increase

Movement from proprietary to standards-based

and B2C video collaboration From To Collaboration

Any-to-any (multi-vendor) real-time systems with

mobile) Shift from Closed / Private delivery to

of both scripted and usergenerated content From

8 Video Transition - Market Trends Dramatic increase in video conferencing offerings and adoption Movement from proprietary to standards-based delivery Move from intra-company to inter-company and B2C video collaboration From To Collaboration Video SP Video Both Proprietary video conferencing Any-to-any (multi-vendor) real-time systems with dedicated infrastructure video collaboration From on-prem to cloud/hosted delivery models Proliferation of video enabled devices (highly mobile) Shift from Closed / Private delivery to over-thetop IP-based Distribution Huge availability of both scripted and usergenerated content From Broadcast video delivered linearly to in-home TV To Over-the-top live and video ondemand to any device

tools and systems that need it Internet of Things Enable more

9 Industry Transition Dev Op s Driving a need for rapid deployment Embedded communications Put communications in the tools and systems that need it Internet of Things Enable more thing to people communications

does look as good Not as fast Can not access some local hardware Limited multi-media Transition Browsers Adding More Support Audio & video (streaming & real

10 The Browser Vs. Thick App War Desktop Environment Browser Based Applications Pros Cross Platform Rapid deployment Yesterday Cons Require network connectivity UI not as rich UI does look as good Not as fast Can not access some local hardware Limited multi-media Transition Browsers Adding More Support Audio & video (streaming & real time) Offline storage and local databases 2D & 3D Graphics Background apps, threads Screen toast notifications Asynchronous notifications Cross application security Better UI and font control Browser Support Access to Host Resource Geolocation Address book Microphone and Camera SMS, MMS, Drag & Drop

11 WebRTC Evolution

12 Evolution of Bowser Based Framework HTTP (Pre AJAX) Original Web, One Page request returns one page (e.g. Geocities) Browser Server AJAX (2004) Page Can Update without refreshing (e.g. Gmail) Web Socket (2008) Page Can Establish bi-directional communication (e.g. Trellol) Graphic by Jimmy Lee / jimmylee.info Browser WebRTC (2012) Page to Page Communications Browser Browser Server Server Browser

13 Browsers Used to lack UC/Video Capabilities Plugins and native apps fill these gaps Softphone engine Real-time voice codecs Real-time video codecs Real-time data/content sharing Call signaling Media encryption Ability to send media to other endpoints Capabilities Notifications Firewall traversal negotiation Peripheral controls System activity detection Drive to remove plugins has accelerated, WebRTC is quickly becoming the default alternative

14 UC/Video Is Not Broadly Deployable Today in Browsers. Plugins or native apps that browsers can launch are required

15 And Mobile Browsers Are Not Extensible Native mobile apps are required

Browsers Drop Plug-ins Support Chrome and Firefox leading the charge Google Chrome and Mozilla Firefox will drop plugin s support in the near future To give people more control over their browser,

org/futurereleases/ 2013/09/24/plugin-activation-in-firefox/ Today s browsers are speedier, safer, and more capable than their ancestors.

16 Browsers Drop Plug-ins Support Chrome and Firefox leading the charge Google Chrome and Mozilla Firefox will drop plugin s support in the near future To give people more control over their browser, Firefox will no longer activate most plugins by default /09/24/plugin-activation-in-firefox/ Today s browsers are speedier, safer, and more capable than their ancestors. Meanwhile, NPAPI s 90s-era architecture has become a leading cause of hangs, crashes, security incidents, and code complexity. Because of this, Chrome will be phasing out NPAPI support over the coming year. To avoid disruption to users, Google Chrome will support whitelist the most popular plugin s

17 Browsers Workarounds for Plugins Chrome and Firefox Support Select Whitelist Plugins To avoid disruption to users: Google Chrome will support most popular plug-ins Firefox also allows workaround for whitelist plugins

18 HTML5 Overview Actually, HTML5 & Friends Standards Finalizing in Parallel with Implementations SEMANTICS <!DOCTYPE html> <audio> <section> MathML <footer> <header> <video> <time> <output> OFFLINE / STORAGE Application Cache IndexedDB localstorage STYLING border-radius border-image backgrounds CSS3 columns shadows transitions animations MEDIA & GRAPHICS WebRTC RTCWeb <audio> WebGL PERFORMANCE <video> <canvas> SVG XMLHttpRequest Web Workers Web Sockets window.history INTEGRATION Drag & Drop Touch Events Geolocation Full Screen

Key Features Media Streams Get User Media:

Control Encryption Bandwidth Management Data

19 Key Features Media Streams Get User Media: for capturing video and audio from webcam and microphone WebRTC can carry a media source containing one or more synchronized Media Stream Tracks Media should be converted to URL to be played by HTML5 Peer Connection High quality peer to peer audio/video calls (Peer-to-Peer) Codec Control Encryption Bandwidth Management Data Channels Point-to-Point Application Data Transfer (not supported in any browser)

20 What Does this mean? It means standalone audio-video chat clients (e.g., Skype) can be replaced with browser based clients No need to install any more application. Browsers will do the job Once Data Channel feature is also implemented by browsers remote desktop, file transfer, gaming, real time text chat, and many other apps would become possible just from within the browser

21 What else become possible? Combining with other web technologies will open new doors WebGL and HTML5 combined with WebRTC can make an entirely new web experience Example: Applying video effects on live streaming video All these will be possible at very low cost

22 WebRTC Architecture

communication components Cross platform Ease of Development Ease of Deployment Distribution = URL

23 Why This is Interesting? No VoIP expertise needed Enables huge web developer population New applications Mashable communication components Cross platform Ease of Development Ease of Deployment Distribution = URL Datacenter, not individual devices Low maintenance Rapid updates Click to access Any device Reduced need for plugins/native apps Extends business comm. systems Massive Adoption Ease of Access

Cisco Product Strategy for HTML5 / WebRTC

support of WebRTC within 1-2 years Offer

broadly adopted browser standards Architect

capabilities as they become broadly available

24 Cisco Product Strategy for HTML5 / WebRTC Standards-based, interoperable browser support of WebRTC within 1-2 years Offer compelling products today, using existing broadly adopted browser standards Architect new products for emerging browser capabilities, e.g. WebRTC Plan support for emerging browser capabilities as they become broadly available Complement with native platform capabilities if necessary Progressive adoption by customers & partners over time

25 Interactive Voice, Video, Data in Web Browsers A Journey Browsers Vendor A Browser with Web App X Apps Standards Native, Zero Plugin Codecs Vendor B Browser with Web App X

26 Notable Challenges Media traversal through firewalls, NAT Securing browsers and media Validating identity of person calling Optimizing real-time traffic performance

27 Browser Architecture High-level Browser-to-Browser Real-time Communications Voice, Video via SRTP (DTLS) Identity Provider Web App X via HTTP/HTTPS (e.g. HTML, CSS, JavaScript) Web Server

28 WebRTC Architecture Key Components Your Web Apps.. Web Server Web API (Edited by W3C WG) WebRTC Voice Engine isac /ilbc Codec NetEQ for Voice Echo Canceler / Noise Reduction WebRTC C++ API (Peer Connection) Session management / Abstract signaling (Session) Video Engine VP8 / H.264 Codec Video Jitter Buffer Image enhancement Transport Engine SRTPc Multiplexing P2P STUN+ TURN+ICE B R O W S E R Audio Capture/Render Video Capture Network I/O

29 What are the gaps WebRTC limitations Session Initiation is not a part of WebRTC. Checking for the presence is not part of WebRTC Session initiation and Presence should be taken care by the application that embeds WebRTC WebRTC is peer-to-peer architecture; no support for One or Many-to-Many (multicast, broadcast) Third party libraries provide signaling capabilities Cafex Fusion Client SDK provides a framework for developers to embed real-time communications easily within business applications across mobile and browser platforms with no added client or plugin

30 WebRTC Connection Establishment Client 1 Caller Server Client 2 Calling 1 Providing Signaling Channel 2 Connect to Server 2 Connect to Server 3 Setup PeerConnection 4 Send OFFER To Server 5 Distribute Signaling to Other Client 6 Accept Signaling: OFFER 10 Accept Signaling: ANSWER 9 Distribute Signaling to Other Client 7 Setup PeerConnection 8 Send ANSWER to server 11 Send OK to Server 12 Distribute Signaling to Other Client 13 Stream Establishment

31 WebRTC Identity Browser is configured with identity provider(s) for the user User logs on to identity provider Browser gets assertion from identity provider that binds the DTLS fingerprint to identity Calling JavaScript passes assertion to farend Bob s browser verifies the assertion with identity provider and check DTLS fingerprint matches Oauth /OpenID Connect/facebook (Identity Provider) 3 JS App Alice Browser Calling Website DTLS/SRTP Media 4 3 JS App Bob Browser

32 WebRTC Security SRTP RTP/SRTP are most commonly used in Voice & Video over IP implementations Sequence numbers, synchronization etc.. Only Payload is Encrypted DTLS DTLS handshake between endpoints to negotiate encryption keys Self-signed Certificates (no traditional PKI) NAT/Firewall Traversal STUN (Session Traversal Utilities for NAT) TURN (Traversal Using Relays around NAT) ICE (Interactive Connectivity Establishment)

33 Browser Architecture Closer Look at Enhancements for Real-time Communications Camera, Microphone, Access Media Control APIs Codecs Offer/Answer Signaling Controller Audio/Video Engine RTP Stack DTLS/SRTP Transport Data SCTP/DTLS Other Browser APIs ICE Engine Access to mic, camera Audio, video codecs srtp for interactive media, lip sync, etc SRTP media encryption using DTLS keying ICE for NAT/firewall traversal Web App (HTML, CSS, JavaScript) SCTP/DTLS for real-time data, e.g. games SDP-based offer/answer negotiation = enhancement to browser = app using new browser APIs

34 WebRTC How Does it Work? Browser to Non Browser Endpoint Web Server WebRTC SIP SIP Call Agent Javascript HTTP SIP SRTP Browser

35 WebRTC Mutipoint Very High-level Real-time Multipoint Architecture (Subject to Change) Multiple Browsers Enterprise Endpoints Voice, Video via SRTP MUTI-POINT CONF UNIT or TRANSCODER Web App via HTTP/HTTPS (e.g. HTML, CSS, JavaScript) Web Server GW to SIP SIP SIP SIP Proxy

36 WebRTC Standards

37 Good Progress on Technology Agreement Significant Progress made this year by standard bodies CONVERGING Audio Codecs.. G.711, Opus Signaling: SDP-based offer/answer using JavaScript Firewall/NAT Traversal ICE, STUN, TURN Media Encryption: DTLS-keyed SRTP Media Consent: ICE/STUN/TURN Identity: Identity Provider Model QoS DiffServ Code Point markings to enhance WiFi, residential GWs, LTE links Both Video Codec(s) VP8 Vs H.264 are supported, IETF Decision Made! TBD Cisco Announced FreeOpenH264 Project Mozilla Announced Firefox will use OpenH264 Congestion Control Goals = Minmize latency, Quick Reaction, Consistent data flow Screen/Application Sharing Recording Simulcast Video Trickle ICE Port reduction with Bundle Partial Offer / Answer

38 Standards Efforts Cisco Playing Key Role RTCWeb Working Group Primary effort in IETF Cullen Jennings of Cisco is co-chair Defining how browsers communicate with others largely re-using existing protocols Notable documents draft-ietf-rtcweb-audio draft-ietf-rtcweb-jsep draft-ietf-rtcweb-qos draft-ietf-rtcweb-security-arch draft-ietf-rtcweb-data-channel draft-ietf-rtcweb-overview draft-ietf-rtcweb-rtp-usage draft-ietf-rtcweb-use-cases-and-requirements WebRTC Working Group Primary effort in W3C Cullen Jennings of Cisco co-authors draft Keith Griffin of Cisco is co-author for the data/screen sharing draft Defining how Web applications access browser real-time communications, i.e. API s Notable documents WebRTC 1.0: Real-time Communication Between Browsers Media Capture and Streams Media Capture Scenarios

Open Source H.264 to Enable WebRTC Adoption Cisco and Firefox make a H.264 Video endpoint calls a Firefox browser via WebRTC-Enabled Cisco Spark http://blogs.cisco.

39 Open Source H.264 to Enable WebRTC Adoption Cisco and Firefox make a H.264 Video endpoint calls a Firefox browser via WebRTC-Enabled Cisco Spark y-first-h-264-video-endpoint-calls-firefoxvia-webrtc-enabled-project-squared Google Chrome is considering how to add support for H.264 in its browser Additional information available at: Spark:

40 Browser Support for WebRTC

41 Browser Evolution

42 Browser Support of HTML5 Steadily Increasing Trend Across Browsers

HTML 5 Tests How Well Does your browser support HTML 5

[30] 501 [26] 494 [18] 408 [10] 345 Firefox [32] 475

Internet Explorer [DG] 378 [11] 376 [10] 335 [9] 128 [8]

392 Safari [8.0] 429 [7.0] 397 [6.0] 380 [5.1] 305 [5.

maximum score of 555 Older browser versions of the HTML5

43 HTML 5 Tests How Well Does your browser support HTML 5 Upcoming Current Older Chrome [37] 512 [35] 507 [32] 505 [30] 501 [26] 494 [18] 408 [10] 345 Firefox [32] 475 [31] 577 [30] 467 [28] 448 [26] 446 [24] 436 [17] 397 Internet Explorer [DG] 378 [11] 376 [10] 335 [9] 128 [8] 43 [7] 27 Opera [24] 504 [22] 498 [20] 496 [16] 494 [ Safari [8.0] 429 [7.0] 397 [6.0] 380 [5.1] 305 [5.0] 246 Browser passes all tests it could receive a maximum score of 555 Older browser versions of the HTML5 only evaluated against fewer tests - resulted in lower maximum score

44 Browser Implementations of WebRTC Many Versions Coming to Market Google Chrome Initial desktop implementation in Chrome 23 Stable & later Initial mobile implementation in Chrome 26 for Android Beta H.264 support in ChromeOS 39/40 for Chrome Book Actively contributing to standards efforts, & open source, e.g. WebRTC.org Mozilla Firefox OpenH.264 is supported in Firefox 33 Actively working on open source implementation & contributing to standards efforts Microsoft Internet Explorer MS announce WebRTC support through ORTC API, contributing and improving the ORTC API for WebRTC standards efforts Conflicting statements about WebRTC 1.1. Apple Safari Maintaining strict secrecy

Microsoft Security and Patch Support Beginning January 12, 2016, only current version of Internet Explorer available for a supported operating system will receive technical support and security

45 Microsoft Security and Patch Support Beginning January 12, 2016, only current version of Internet Explorer available for a supported operating system will receive technical support and security updates. =PN&alpha=internet+explorer Microsoft announces support for WebRTC technlogy and will be supporting the ORTC API in Internet Explorer. Spartan Bowser will most likely be the future MS browser

46 Transition To Cloud & Security

47 Cloud Data Huge amount of data in the cloud including WebRTC further adds.. Large amounts of collection by governments and less legal entities Continuous stream of financial losses

48 Don t Panic

49 Multi User Security with Content Privacy (new-way) Endpoint transmitter encrypts and authenticates content Multi-point server verifies authentication, modifies RTP header and re-authenticates Key used for media encryption is not known to server Endpoint receiver authenticates packet and decrypt media B C Header Enclosed Payload Header Verify Authentication Header Enclosed Payload Header RTP Processing Header Enclosed Payload Header A

50 WebRTC, Privacy, TOR and VPN WebRTC API allows a webpage to get your IP addresses This includes, public, private, and multi-homed Needed to provide these to the other side to send peer to peer traffic Web servers have always got your public address Running a split tunnel VPN, it reveals both external interfaces User in Canada VPN into the US so you look american to netflix, a netflix web client might be able to figure out that one of your public IPs is in Canada and one is in the US Using a VPN to hide your location, don t use a split tunnel Many enterprises have a policy against using split VPN

51 Interoperability with Enterprise Communications

Does the business endpoint support ICE? Can the business endpoint speak G.

52 Key Interoperability Considerations How standards-compliant are signaling implementations in the gateway & business system? Does the business endpoint support ICE? Can the business endpoint speak G.711 or Opus for voice? Can the business endpoint speak VP8 or H.264? Does the business endpoint support DTLS SRTP?

53 Potential Interoperability Solutions? Enterprise Communications Vendors Build gateway capabilities into their systems Build native support into their systems Integration Vendors Build gateway capabilities into their products Service Providers Offer native capabilities that interoperate with their services Offer gateway services Cloud Services Offer gateway services

54 WebRTC Solution

Future WebEx Browser Meeting Experience Subject To Change HTML5 & Web RTC based WebEx Client Join fast into your meeting No install or plug-in Currently in Internal

55 Future WebEx Browser Meeting Experience Subject To Change HTML5 & Web RTC based WebEx Client Join fast into your meeting No install or plug-in Currently in Internal Beta only Key Capability: For Attendees only VoIP on WebRTC (Chrome, Firefox) Video on WebRTC (Firefox, Chromebook Future) Participant List Hybrid Audio View & Share Chat

Jabber Guest Fundamentals Precursor to WebRTC Consumer Experience Session ID BRKUCC 2086 Customer

com/community/technol ogy/collaboration/usergroups Real-Time Expert Help Video Chat Guest User

Enterprise DMZ Cisco Expressway E (OR VCS E) X8.

56 Jabber Guest Fundamentals Precursor to WebRTC Consumer Experience Session ID BRKUCC 2086 Customer Connection Program ogy/collaboration/usergroups Real-Time Expert Help Video Chat Guest User Experience Desktop browser Mobile application SDK (mobile app or Web-based) Required Components Enterprise DMZ Cisco Expressway E (OR VCS E) X8.2 or later Enterprise Network Jabber Guest virtual machine Cisco Expressway C (or VCS C) x8.2 or later Cisco Unified Communications Manager 8.6 or later and registered endpoints Optional: MCU/Telepresence/Contact Center

Precursor WebRTC - Jabber Guest Call Flow Home Internet DMZ

2+ Jabber Guest Cisco UCM HTTPS-based call control (ROAP)

call control based on URL For mobile, uses Cisco app from

57 Precursor WebRTC - Jabber Guest Call Flow Home Internet DMZ Enterprise Expressway/VCS Edge X8.2+ Expressway/VCS Core X8.2+ Jabber Guest Cisco UCM HTTPS-based call control (ROAP) SIP RTP/SRTP STUN/TURN Jabber Guest Serves up Javascript call control based on URL For mobile, uses Cisco app from app store or integrates SDK into third-party app For laptop browsers, initiates H.264 add-on install as needed (Cisco or 3rd-party Web app) Converts HTTPS call request to SIP INVITE

58 Firefox Hello Firefox Hello, simple and easiest way to connect for free over video with anyone, anywhere Share a link and have remote party join a video call from Firefox browser

59 Remote Expert Mobile Plugin less Approach with Minimal Transcoding REM Internet Media H.264 Broker H.264 Internet VP8 REM Media Broker VP8 Zero transcoding H.264 endpoints Google Chrome Google Chrome & VP8 only browsers Internet VP8 VP8 REM Media Broker H.264 VP8 to H.264 transcoding VP8 to H.264 transcoding H.264 endpoints Mobile Advisor supports both H.264 and VP8. As a result, no transcoding occurs when a smartphone or a tablet app connects to an H.264 end point Mobile apps powered by RE Mobile switch between codecs to minimize transcoding Supports VP8 to H.264 Transcoding for WebRTC compliant browsers Guarantees compatibility between WebRTC endpoints and immersive, desktop and traditional video end points

60 webrtc2sip Web Browser Java Scripts SIP Stack SIP Webrtc2sip gateway allows your web browser to make and receive calls from/to any SIP-legacy network or PSTN. webrtc2sip SIP Proxy RTCWeb Breaker PSTN SDP Stack Media Media Coder WebRTC Click-to-Call IMS/LTE/ SIP webrtc2sip is a smart and powerful gateway using RTCWeb and SIP to turn your browser into a phone with audio, video and SMS capabilities The gateway contains four modules: SIP Proxy RTCWeb Breaker Media Coder Click-to-Call. The gateway allows your web browser to make and receive calls from/to any SIP-legacy network or PSTN. - They have sample demos you can explore

Carrier Support for WebRTC ATT launches commercial support for WebRTC Via it s AT&T enhanced WebRTC API AT&T Enhanced WebRTC API is available to developer through an open beta program Valuable tool

61 Carrier Support for WebRTC ATT launches commercial support for WebRTC Via it s AT&T enhanced WebRTC API AT&T Enhanced WebRTC API is available to developer through an open beta program Valuable tool for developers and customers; will spur growth by eliminating a key barrier to adoption Caller ID for WebRTC communications: It can use end user's AT&T mobile number for calls placed from WebRTC-enabled browsers. Enables end users to move or transfer a call starting on a PC, MAC or tablet to a smartphone. AT&T Becomes First U.S. Carrier To Launch Commercial Support For WebRTC

require users to install anything Developed by three college student as part their Summer Program PeerCDN is

62 PeerCDN New Kind of CDN using WebRTC Web Browsers can serve contents to other browsers instead of the server Help with speed and scalability, dramatically reduces bandwidth costs Pure JavaScript -lightweight, and doesn't require users to install anything Developed by three college student as part their Summer Program PeerCDN is now part of Yahoo! Browser shares static resources (images and file downloads) over a peer-to-peer network Web Server

63 WebRTC Use Cases - Demos

64 Key Use Cases Voice & Video Enterprise Contact Centers Telco-OTT Unified Communications Conferencing Kiosks Social Communication Entertainment Education Apps IMS Extension

65 Get a feel for WebRTC

Reference Read the specifications: http://w3c.github.io/webrtc-pc/ http://w3c.github.io/mediacapture-main/ http://tools.

com/ many more books coming out this year Join the community mailing lists of ISOC supported standards

66 Reference Read the specifications: WebRTC Books : many more books coming out this year Join the community mailing lists of ISOC supported standards organizations W3C: Send with "subscribe" to public-webrtc-request@w3.org IETF:

67 WebRTC Advantages In Closing.. Accessed through JavaScript API Does not require plugins, downloads or installs Multiple browsers Platform agnostics Video Convergence Accelerate Internet of Everything initiative Cisco is Committed to WebRTC technology Cisco is driving standards & adopting WebRTC in our solutions

68 Polling Open Dialog & Q&A What type of browsers version are using in your organization? Are you limited to Internet Explorer, are you open to other browser vendors? What kind s of pressure are you getting from your organization to deploy WebRTC? Are you needing to deploy applications that have no plugins? What are your end customer asking you? What other platform support would you require for WebRTC? Anything else on your mind regarding WebRTC How can Cisco help to drive WebRTC adoption in your environment...

Cisco Customer Connection Program Connect with Cisco & Peers Influence Collaboration product direction Access to early adopter & beta trials Contribute to advisory groups Monthly technical & roadmap

69 Cisco Customer Connection Program Connect with Cisco & Peers Influence Collaboration product direction Access to early adopter & beta trials Contribute to advisory groups Monthly technical & roadmap briefings Exclusive perks at Cisco Live Collaboration Cloud Fusion: Vision & Architecture (speaker: Jonathan Rosenberg, VP/CTO CTG) 5 NDA Roadmap Sessions + Microsoft Interop Q&A Open Forum with Product Management Reserved seats at Work Human Innovation Talk (Wed. 3:30 4:30) Visit the Customer Connection Program - Collaboration zone in the Cisco Campus Join the Customer Connection program Explore the Collaboration community New CCP members get a thank-you gift 17,000+ Members

Complete Your Online Session Evaluation Give us your feedback to be entered into a Daily Survey Drawing. A daily winner will receive a $750 Amazon gift card.

70 Complete Your Online Session Evaluation Give us your feedback to be entered into a Daily Survey Drawing. A daily winner will receive a $750 Amazon gift card. Complete your session surveys though the Cisco Live mobile app or your computer on Cisco Live Connect. Don t forget: Cisco Live sessions will be available for viewing on-demand after the event at CiscoLive.com/Online

71 Continue Your Education Demos in the Cisco campus Walk-in Self-Paced Labs Table Topics Meet the Engineer 1:1 meetings Related sessions

72 Thank you

WebRTC: The Journey From Browser Plugins to Thin Client Communications

WebRTC: The Journey From Browser Plugins to Thin Client Communications Keith Griffin Ph.D Principal Engineer Office of CTO Collaboration Technology Group BRKCOL-2556 Agenda Introduction Our Journey to