The document outlines the agenda for a WebRTC workshop on the ecosystem. The workshop will include introductions, an overview of WebRTC, standardization discussions, presentations on WebRTC archetypes and use cases, and details on implementation architectures. The implementation section will discuss developing WebRTC applications independently or with frameworks, SDKs, services, and API platforms.
Russian Call Girls in %(+971524965298 )# Call Girls in Dubai
Workshop web rtc implementation details
1. WebRTC Workshop
Open discussion on the ecosystem
September 2014
Tsahi Levent-Levi
2. About Me
•Too many years in the telecom industry. Mainly VoIP
•Developer, Product Manager, CTO
•Had my share of standardization and patents
•Write about WebRTC and other topics
•Published the WebRTC for Business People report
•Consulting
10/13/2014
2
Tsahi Levent-Levi
tsahil@bloggeek.me
@tsahil
3. WebRTC Workshop - Open discussion on the ecosystem
10/13/2014
3
13:00 Introductions Doug
13:10 What is (and isn't WebRTC) Tsahi
14:00 Standaradization, IETF and WebRTC Victor
14:45 Break
15:00 5 WebRTC Archetypes Tsahi
15:45 The WebRTC Use Cases/Deployments Doug
16:30 Implementation/Architecture Details Tsahi
17:15 Wrap-up Victor
4. Alternatives
10/13/2014
4
Level of dependency on 3rdpartiesLevel of required experience in VoIP & WebRTCSelfDevelopmentIntegrationof Open Source FrameworksIntegrationof CommercialSDKs & FrameworksEmployingSaaSWorkingwith anAPI Platform
14. Why Use a Framework?
•WebRTC is a moving target
–API changes
–Interoperability across browsers
•Simple, but not enough
•Solving the missing signaling issue
14
23. Why Use a Service?
•No maintenance involved
•Predictable pricing
•Focus on the use case (=time to market)
•Feature rich on operability
•Various offerings:
1.Signaling
2.NAT traversal
3.Media processing
23
24. Signaling: PubNub
•Global low latency network that added recently support for WebRTC
•Other options: Pusher, Firebase
24
25. NAT Traversal
•Offload the headache of deploying TURN servers
•Offer geographical spread of STUN/TURN
25
29. They Are Different
•Feature set
•Size
•Focus
•Stability
•Flexibility
•…
29
30. List What You Need
•Voice?
•Video?
•Multipoint?
–How many users?
–How many passive/active?
–What quality levels are acceptable?
•Recording?
•Connectivity to other networks?
•Collaboration?
•…
30
31. Parameters to Select By
•Focus
•Feature set
•Deployment options
•APIs & Documentation
•Support
•Self Service
•Business model
•Financial & Legal
31