WebRTC Integration from Tim Panton

1,680 views
1,481 views

Published on

WebRTC Integration presentation from Tim Panton, given at WebRTC pre-conference workshop at Rich Communications.

Published in: Technology
0 Comments
5 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,680
On SlideShare
0
From Embeds
0
Number of Embeds
761
Actions
Shares
0
Downloads
50
Comments
0
Likes
5
Embeds 0
No embeds

No notes for slide

WebRTC Integration from Tim Panton

  1. 1. WEBRTC INTEGRATION OPTIONS Tim Panton, Westhawk Ltd – @steely_glint
  2. 2. Demo – call a mobile  Demo calls my mobile from a browser
  3. 3. Not everyone wants to interop      Games Dating sites Whiteboards OTT Mayday For these sites a home grown signaling protocol may be simplest/best. (highest value apps will be in this class)
  4. 4. Problem statement WebRTC      HTTP(S) transport RIA 2.0 media Encrypted Opus VP8 ? Carrier IMS      SIP RTP Cleartext Ulaw (729, amr?) H263/4
  5. 5. Gateway needed ? Unless and until those incompatibilities go away.
  6. 6. HTTP to SIP – SIP in the Browser     Use javascript to build SIP messages and protocol Wrap in HTTP (or Web-sockets) Send to webserver Webserver unwraps and forwards to IMS
  7. 7. SIP in the browser Browser JS SIP SIP in HTTP WebSocket Server UDP SIP IMS
  8. 8. Problems       You still have a gateway – albeit a thin one. You have javascript injecting SIP messages into IMS The SDP isn’t compatible The media isn’t compatible What is Early media in a browser ? You have your SIP credentials out on the internet.
  9. 9. SIP in the browser with SBC DMZ Browser JS SIP SIP in HTTP WebSocket Server UDP SIP SBC UDP SIP IMS
  10. 10. Remaining Problems    The media isn’t compatible What is Early media in a browser ? You have SIP credentials out on the internet.
  11. 11. SIP in the browser with SBC, Media Gateway and Registration proxy DMZ Browser JS SIP SIP in HTTP RIA 2.0 WebSocket Server UDP SIP Proxy Reg SBC Media GW UDP SIP IMS RTP ulaw
  12. 12. REST in the browser      Use web ‘RESTful’ commands Sent from the browser To a webRTC gateway Gateway generates the SIP IMS needs Gateway controls transcode resource
  13. 13. REST in the browser with Gateway DMZ Browser app REST/HTTP WebRTC gateway UDP SIP IMS
  14. 14. Problems      Need to map from web Identity to SIP Select a web identity provider webRTC gateways don’t scale (yet) No standard for REST messages Home rolled protocol (may have holes)
  15. 15. XMPP in the browser with SBC DMZ Browser app XMPP/BOSH/H TTP WebRTC gateway UDP SIP IMS
  16. 16. Problems Need to map from web Identity to SIP  Select a web identity provider  webRTC gateways don’t scale (yet)  More complex than necessary  Needless protocol mapping? However  BOSH is tested  XMPP well defined and federates 
  17. 17. Did we forget mobile? WebRTC isn’t mobile first yet.
  18. 18. WebRTC on Mobile      Browser isn’t a natural interface WebRTC codecs are heavy on battery No native App friendly API (yet) SIP (if used) not an efficient mobile protocol Audio hardware on android variable Both Chrome and firefox on Android support webRTC Expect to see RIA 2.0 with native APIs
  19. 19. Identity. DTLS can carry a certificate – but which one should be used?
  20. 20. Multiple identities on the web When I call from a webpage, which identity do I want to present?  E164 to the shop  Facebook Id to my fb friends  Anon to the game  Pseudo id to dating site Do I ever want to present facebook ID to G+ users?
  21. 21. Demo Phono using a Jira identity. (perhaps)

×