Check out our new WebRTC Network test page!
Media quality is affected by a number of factors, but is especially susceptible to end-user network environments. Understanding the network conditions for WebRTC calls can ensure higher media quality and predictability. To tackle this issue, we launched a new feature called pre-call test.
Our customer noticed that their RTTs were higher than expected. We went to work to understand what caused the high RTT values.
The main reason we use Kubernetes at callstats.io is simple: It lets us minimize the number of servers we run in our AWS ecosystem, naturally bringing about sizeable cost efficiencies. But we also make use of many features available in Kubernetes.
For many developers looking to dip their feet into WebRTC, one of the biggest questions is whether to use a software development kit (SDK). This is especially true when the intended purpose is strictly one-to-one, peer-to-peer (P2P) communication.
Our deep dive series into callstats.io REST API continues with a post on ICE gathering state changes. Read on and make the most out of your call diagnostics service.
We think of data collection and presentation at callstats.io as a pyramid, with individual call data at the bottom of the pyramid. As we go up the layers, the data gets aggregated in stages into a holistic view for your WebRTC App.
The new tab-based dashboard layout and improved filtering help understand specific conferences or users; ‘Conference details’ tab gets a makeover