qualityRTC FAQ

Browse through some of the most frequently asked questions from other customers who are using qualityRTC.

  • What does “Bad DNS resolution” mean?

    In qualityRTC there’s a set of silent tests that can be added to an account. One such test is DNS resolution, which checks to see if the resolution mechanism used works well with the DNS server of the user. When you see the messa...

  • VIDEO BANDWIDTH shows low bitrate while BANDWIDTH SPEED shows high bitrates

    In the screen shot below, a user comes with a result in qualityRTC that shows low VIDEO BANDWIDTH bitrates while BANDWIDTH SPEED is showing high bitrates. Here is what we can glean out of the information: TURN CONNECTIVITY shows ...

  • How would bad routing look like on qualityRTC?

    One of the leading factors to quality issues with WebRTC is the distance between the user and your backend infrastructure. Even if there is a nearby server, there can be limiting factors such as the use of a VPN service by yo...

  • What network ports does qualityRTC use?

    For its own use, qualityRTC requires port 443 to be open and reachable. For anything that is WebRTC infrastructure specific, the required ports are similar to those of the service being tested. This is due to the fact that qualit...

  • TURN CONNECTIVITY sometimes succeeds and sometimes fails

    If you have a user running qualityRTC complaining that his sessions sometimes connect and sometimes doesn’t, and you get similar types of results in the TURN CONNECTIVITY tests of qualityRTC, then this might be due to a firew...

  • Invite Options JSON structure

    When generating a qualityRTC invite, you can have query parameters included such as region or account. You can also use these invites to add any additional fields you might need. This is something you can configure using the Opti...