Varun Singh, callstats.io CEO, gave a presentation at Enterprise Connect 2016. He talked about how WebRTC is being used and what are the analytics behind it.
3. callstats.io
First cloud-based monitoring service for WebRTC
• 40 paying customers
• +80 developers accounts
Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb3
4. Very Simple API
• 3 lines of code —> 5 minutes.
1. include <script>
2. initialize() —> needs registration keys
3. addNewFabric(pc, …) —> call started
• optionally: send user events: audio muted/unmuted, video paused/
resumed, call terminated, call held.
• optionally: collect and send user feedback
http://www.callstats.io/api/4
5. It is not all about throughput*
• … it is about latency or delay!
*)capacity
bandwidth
speed
audio only call
6. Disruptions
Disruption: loss of connectivity when
network interfaces change, low
available capacity,or high delay
The light grey vertical lines show disruption, highlighted by the red bounding boxes.
6
7. Disruptions and user behaviour
User Behaviour: The user tries
to correct for the disruption by
turning on and off video
7
17. Lessons Learnt
• ask for audio and video device permissions
separately
• deploy TURN servers with UDP and TCP support
• detect crashes and re-setup connections
• media pipelines sometimes crash
• screen sharing plugin crashes
18. Summary (1/2)
• Browsers: Chrome dominates WebRTC
• OSes: Windows and Mac are pretty even
• Participants: ~3 participants in a call on average
• Relays: ~20% sessions need a TURN server
18
19. Summary (2/2)
• Setup time: 80% sessions setup in <5s
• Call Setup Failures: ~10% of calls fail to setup
• Reason for failure: 85% due to NAT/FW
• Call Drop: 20% calls fail after setup
• Churn: 25% of sessions have a participant rejoining
19