Junction is Finland’s biggest hackathon, it was organised to coincide with Slush, the biggest startup conference in the Nordics. Callstats.io took part at the Junction hackathon by sending Juho, our data scientist, to evangelize WebRTC APIs.

The year 2015 is the last time Web Summit will be organised in Dublin. We sent a one man team to Dublin for three days to speak with WebRTC-powered startups.

In this blog post we’ll go through how video is sent over the Internet and talk about various errors that might happen when sending video over a WebRTC connection and how they can be fixed.

Think of any communication product and you’ll notice that the generated traffic can be divided into three different categories: audio, video and other data. This is was one of the core reason for WebRTC to develop the data channel to send for any type of data, i.e., in addition to being able to transport audio and video over MediaStreamTracks.

This October, the Traction conference was hosted in San Francisco. Lasse, our Growth Hacker, represented callstats.io at the event to learn more about different methods to drive growth.

callstats.js v3.6 will officially add support for Microsoft Edge, which recently announced support for Object RTC (ORTC).

When a person (repeatedly) drops out and rejoins a conference due to network connectivity problems or media pipeline misconfigurations, it is called user churn. We started investigating churn more closely at callstats.io, developing some simple metrics to measure it within a conference.

At the 2015 Kranky Geek event in San Francisco, there was a sense of excitement within the WebRTC developer community. Especially, the upcoming enhancements to Chrome and Firefox, and that the event provided a platform to exchange notes on their deployment issues, etc.

WebRTC version 1.0 is almost here…

As some of you might have noticed we have been introducing many features to our dashboard in the last couple of months as well as changing the look and feel of the dashboard. To make the development work of the dashboard easier and faster we also looked at different options for a new front-end framework.

The callstats.js v3.4 will introduce a new feature that tracks the conference media quality of each participant as well as their connection status and periodically sends that information to the application in a callback function.

Varun Singh, callstats.io CEO, explains what we do and why it matters in a video interview with voipusersconference.org.

WebRTC is progressing rapidly; the main trend seems to be transitioning from peer-to-peer to conferences with centralized servers. This trend is mainly observed for conferences with more than 5 participants. Today, we are announcing a new API associateMstWithUserID() that maps each media stream track received by an endpoint to a remote userID.

To make sure WebRTC conferences can be offered at the best possible quality, the WebRTC standard includes a statistics API. The statistics can be retrieved with the getStats() API call.

A WebRTC session can fail because of many reasons and at various stages of setting up the session. We zoomed in on the WebRTC negotation phase in our development. Today we release a new API call reportError() that shows to our customers at which stage the conference failed to setup a connection.