Your SlideShare is downloading. ×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

WebRTC Best Practices - WebRTC Paris 2013 - Chad Hart - Dialogic

1,015
views

Published on

Chad's presentation from the WebRTC Paris show covering interoperability issues, WebRTC gateway trends, WebRTC security models, server-side media processing, a video kiosk case study, and future …

Chad's presentation from the WebRTC Paris show covering interoperability issues, WebRTC gateway trends, WebRTC security models, server-side media processing, a video kiosk case study, and future WebRTC applications

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,015
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
30
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • \
  • Dialogic’sPowerMedia XMS provides widely needed capabilities in many applications. While WebRTC is designed to be primarily browser-to-browser, there is a growing number of user cases that require server side media support or that would be greatly enhanced by it.Dialogic’s key capabilities include:Multi-party mixing – traditional MCU-type functionality; mixing streams from various sources into one or more streams and relaying them to users to avoid the mesh overloading problems that occur if you keep everything peer-to-peerTranscoding – converting one codec to another. In the absence of a mandatory video codec today this is important for converting the VP8 codec supported in browsers to H.265 used in existing video conferencing systems and supported by battery saving smartphone hardware. Transcoding is also important to converting WebRTC’s audio codecs (G.711 or Opus) to codecs used in today’s mobile networks, landline, and enterprise environments. New codecs are introduced all the time, so this is a practical problem that will not go away any time soon.Interworking with existing telephony environments – including encryption, media plane, and signaling interworking with the 6B+ users who can be reached via a SIP-based networkRecording – Recording is critical in contact center environments for regulatory purposes. It is also a Stream processing – monitoring and manipulating a stream in real time, be it via a text overlay or inserting an add into the stream or doing manipulation of the video or utilizing avatars.Person-to-machine applications – while WebRTC was originally made for browser-to-browser communications, there are many person-to-machine applications that might not involve another person at all, like today’s IVRs, Text-to-Speech, speech recognition systems, or machine vision, analytics and more.
  • &
  • Latin American Airline Call centerMove to video kiosks in airports Cheaper than putting live agents Allows easy access to travelersLeverage existing contact center infrastructure Augments current capabilities Adds video calling to agents keeping existing ACD systems Provides audio & video to kiosksTarget: high value international travelers & touristsPhase II: Expand to tablets/mobileBusiness model: leverage existing agents & infrastructure; expand presence for more revenueEnd-to-end control of devicesMitigates interoperability issuesReduces security exposureLeverage existing infrastructureUse WebRTC to augment & extendMedia quality is difficult to control over the internetHD video not always necessaryFall back to voice
  • Latin American Airline Call centerMove to video kiosks in airports Cheaper than putting live agents Allows easy access to travelersLeverage existing contact center infrastructure Augments current capabilities Adds video calling to agents keeping existing ACD systems Provides audio & video to kiosksTarget: high value international travelers & touristsPhase II: Expand to tablets/mobileBusiness model: leverage existing agents & infrastructure; expand presence for more revenueEnd-to-end control of devicesMitigates interoperability issuesReduces security exposureLeverage existing infrastructureUse WebRTC to augment & extendMedia quality is difficult to control over the internetHD video not always necessaryFall back to voice
  • Transcript

    • 1. WebRTC Best Practices Chad Hart COMPANY CONFIDENTIAL © COPYRIGHT 2013 DIALOGIC INC. ALL RIGHTS RESERVED.
    • 2. Current & Emerging WebRTC Media Processing Needs Multi-party mixing Transcoding Interworking Recording Stream processing Person-to-machine PowerMedia™ XMS COMPANY CONFIDENTIAL © COPYRIGHT 2013 DIALOGIC INC. ALL RIGHTS RESERVED. 2
    • 3. API’s and Interfaces for Media Developers Telephony Developers Enterprise Developers Standard Media Server Interfaces Back-end Web Developers RESTful APIs PowerMedia™ XMS COMPANY CONFIDENTIAL © COPYRIGHT 2013 DIALOGIC INC. ALL RIGHTS RESERVED. 3
    • 4. We help with traditional media processing too Mixing/MCU Recording/Playback Call Progress Analysis Text-to-Speech Automatic Speech Recognition Whisper mode High Availability … COMPANY CONFIDENTIAL © COPYRIGHT 2013 DIALOGIC INC. ALL RIGHTS RESERVED. 4
    • 5. Agenda Interoperability & Interworking Gateways Real WebRTC networks Tough choices Case study - WebRTC solves real problems today What you should really be working on COMPANY CONFIDENTIAL © COPYRIGHT 2013 DIALOGIC INC. ALL RIGHTS RESERVED. 5
    • 6. Interoperability – Browser to Browser • • Instigators • • Version differences Vendor implementation timelines Homebuilt implementations New browser introductions (hopefully!) API’s Media COMPANY CONFIDENTIAL © COPYRIGHT 2013 DIALOGIC INC. ALL RIGHTS RESERVED. • Need: Medium • Difficulty: Low to High • Resolution: JS Shim, use Chrome • Need: Low • Difficulty: High • Resolution: use Chrome 6
    • 7. Interoperability – Browser to Phone • SIP complexity Instigators • Lack of standards to do this (of course they are coming) Signaling Media COMPANY CONFIDENTIAL © COPYRIGHT 2013 DIALOGIC INC. ALL RIGHTS RESERVED. 7 • Need: Low to High • Difficulty: Medium to High • Resolution: H2S Gateway, Telco SHIM APIs • Need: Low to High • Difficulty: Low to High • Resolution: Media GW, Transcoding
    • 8. “Legacy” Telephony Interworking Functions WebRTC Users Phone User Network HTTP-to-SIP (H2S) SRTP-DTLS UDP/TCP Media GW G.7XX/H.264 OPUS/VP8 Transcoder COMPANY CONFIDENTIAL © COPYRIGHT 2013 DIALOGIC INC. ALL RIGHTS RESERVED. RTP/SRTP-SDES 8 UDP
    • 9. Many Packaging Options HTTP-to-SIP (H2S) Media GW Transcoder HTTP-to-SIP (H2S) HTTP-to-SIP (H2S) Media GW Media GW Transcoder Transcoder COMPANY CONFIDENTIAL © COPYRIGHT 2013 DIALOGIC INC. ALL RIGHTS RESERVED. 9 HTTP-to-SIP (H2S) Media GW Transcoder
    • 10. Will One H2S Gateway be Sufficient? Application specific APIs work best SIP is not really that standard Retail Click-to-Call Enterprise Click-to-Call Residential Web Phone RCS Web Client HTTP-to-SIP (H2S) Developer API exposure RFC3261 SIP Enterprise SIP Remote Agent Remote Worker COMPANY CONFIDENTIAL © COPYRIGHT 2013 DIALOGIC INC. ALL RIGHTS RESERVED. IMS/RCS 10
    • 11. HTTP-to-SIP (H2S) Requirements are not Uniform WebRTC Users Phone User Network H2S H2S H2S Web Signaling H2S SIP Control Interfaces SRTP-DTLS UDP/TCP Media GW G.7XX/H.264 OPUS/VP8 Transcoder COMPANY CONFIDENTIAL © COPYRIGHT 2013 DIALOGIC INC. ALL RIGHTS RESERVED. RTP/SRTP-SDES 11 UDP
    • 12. Security Functions Firewalls API Management Session Border Control All Traffic APIs VoIP Traffic Identifier Address:Port API Key Phone #, URI Controls Bandwidth, Address, Ports API Calls VoIP Messages, Bandwidth, Ports Topology Hiding No N/A Yes Scope COMPANY CONFIDENTIAL © COPYRIGHT 2013 DIALOGIC INC. ALL RIGHTS RESERVED. 12
    • 13. Basic, Telco-Centric Model Javascript App Web server SIP/IMS Network SIP H2S Firewall COMPANY CONFIDENTIAL © COPYRIGHT 2013 DIALOGIC INC. ALL RIGHTS RESERVED. SIP WebMG 13 SBC RTP
    • 14. Mature, Web-Centric Model Web server Identity Server Internal REST APIs API Calls WSS server API Manager App Server STUN/ TURN Firewall COMPANY CONFIDENTIAL © COPYRIGHT 2013 DIALOGIC INC. ALL RIGHTS RESERVED. App Server H2S Server WebMG 14 SIP/IMS Network SIP
    • 15. Design Trade-offs Application Performance Client Performance COMPANY CONFIDENTIAL © COPYRIGHT 2013 DIALOGIC INC. ALL RIGHTS RESERVED. Server Performance 15
    • 16. When does media control matter? When there is limited bandwidth COMPANY CONFIDENTIAL © COPYRIGHT 2013 DIALOGIC INC. ALL RIGHTS RESERVED. When the user is paying per GB 16 When battery usage is a factor
    • 17. Case Study – the Airline 17 COMPANY CONFIDENTIAL © COPYRIGHT 2013 DIALOGIC INC. ALL RIGHTS RESERVED. 17
    • 18. Case Study – the Airline Lessons Learned: • Applications are viable today when you have end-to-end control • Leveraging existing infrastructure shortens time-to-market • Assume you will have poor connectivity • Be careful with the cloud 18 COMPANY CONFIDENTIAL © COPYRIGHT 2013 DIALOGIC INC. ALL RIGHTS RESERVED. 18
    • 19. What Smarter People Are Doing COMPANY CONFIDENTIAL © COPYRIGHT 2013 DIALOGIC INC. ALL RIGHTS RESERVED. 19
    • 20. Contact me Chad Hart linkedin.com/in/chadwallacehart chad.hart@dialogic.com @chadwallacehart COMPANY CONFIDENTIAL © COPYRIGHT 2013 DIALOGIC INC. ALL RIGHTS RESERVED. webrtcHacks.com @webrtcHacks 20