WebRTC Standardization

View Github Repository Open presentation in a new window

sachanacar

See all presentation from sachanacar

WebRTC Standardization

0 0

webrtc-a-future-without-sip

:rocket: DeveloperWeek Presentation

On Github sachanacar / webrtc-a-future-without-sip

WebRTC vs. SIP

Sacha Nacar

Developer Community Manager @ Voxbone
@sachanacar
bit.ly/wwrs
ow.ly/IPSVJ
  • Presentation
  • Article

VOXBONE SIMPLIFIES COMMUNICATIONS

By bringing local voice services to the cloud.

  • Sell local phone numbers Worldwide
  • SIP endpoint
  • Calls routed Private backbone
  • WebRTC-SIP SDK

Preface, Butterfly Effect and Bike-shedding

Will WebRTC Replace SIP?

By Andrew Prokop

  • Why this title? Article
  • Does it really come down to WebRTC vs. SIP?
  • NOT EXHAUSTIVE!
  • net neutrality, data privacy, Internet of Things
  • BikeShedding, parkinson's law of triviality

Is WebRTC a Drink I Can SIP?

  • Why this title? Article
  • If first time you hear, I HAVE GOODIES at the end - FIND A BETTER PUN
  • Accronym - WebRTC - API, Browser-to-Browser, no plugin
  • Session Initiation Protocol, text-based protocol in Internet telephony (VoIP) for signaling and controlling multimedia sessions.

WebRTC vs. SIP?

WebRTC vs. SIP?

SIP vs. Protocol X

Browser vs. PSTN

  • SIP and WebRTC - Similar use cased - different in function
  • Put it this way: SIP doesn't need WebRTC, WebRTC doesn't need SIP - but needs a signalling protocol
  • Two different battles

Battle 1:

Will a signaling system prevail over SIP?

SIP Over WebSockets

JSON Over WebSockets

XMPP/Jingle

Data Channel

Maybe Not

  • WebRTC work in progress - no protocol specified signaling
  • Gap vs. Opportunity - heated debate
  • Signaling/signalling
  • SIP OVER WEBSOCKETS
  • standard in VoIP
  • convenient semantics for voip
  • not invented with WebRTC in mind - need custom stack or gateway
  • Carriers make infrastructures accessible over Websockets
  • Open source encoding: JSSIP, sipML5
  • SIP made more accessible to the web
  • JSON OVER WEBSOCKETS
  • subset of JavaScript - natively readable by web browsers
  • most intuitive, no processing or encoding
  • needs custom stack for external infrastructures (legacy telephony)
  • community - 3rd party frameworks (PubNub, Firebase)
  • Matrix.org - federating JSON signalling
  • XMPP, Data Channel
  • Why important? Standardization means locking and outcasting
  • Ease of integration + Support of community
  • Do we HAVE to standardize?
  • Decouplig developers vs. telcos

Battle 2: The Browser vs. The PSTN

  • Standardization isnt onyl battle
  • WebRTC can change way we communicate - eclipse PSTN
  • Both future will depend on factors

WebRTC Standardization

  • Signaling standardization is not only one
  • DOWN
  • Video Codec fierce war- VPn (google) vs. H26n (cisco)
  • DOWN
  • Browser acceptance of WebRTC
  • Overall interoperability will define whether better to use the phone or browser

WebRTC Going Mobile

  • Dial-tone to smartphone (computer)
  • WebRTC's future = what communicating will become (wearbles, IoT)
  • SPEED (LTE) + Low Cost Data plans
  • Carriers will be at center of WebRTC vs. PSTN battle

Identity Management

  • Dial-tone to smartphone (computer)
  • WebRTC's future = what communicating will become (wearbles, IoT)
  • SPEED (LTE) + Low Cost Data plans
  • Carriers will be at center of WebRTC vs. PSTN battle

Conclusions

  • Many other factors
  • Put it this way: SIP doesn't need WebRTC, WebRTC doesn't need SIP - but needs a signalling protocol
  • Two different battles

Thanks to:

Dan Burnett

Victor Pascual

Andrew Prokop

Torrey Searle

Vincent Morsiani

Robert Zemeckis

WebRTC - A Future Without SIP?