Data center selected might not be optimal | We can see you are connecting from <USER-COUNTRY>, but the media server assigned to you is in <MEDIA-COUNTRY>. “Long distance” calls lead to lower call quality. This can be the case if you are using a VPN or if you configured your DNS server (to Cloudflare for example). Read the full article to learn more.
| Code: | 10002 |
| Type: | Error |
| Category: | Miscellaneous |
| Products: | qualityRTC |
| Message: | We can see you are connecting from <USER-COUNTRY>, but the media server assigned to you is in <MEDIA-COUNTRY>. “Long distance” calls lead to lower call quality. This can be the case if you are using a VPN or if you configured your DNS server (to Cloudflare for example). |
What is this about?
The service you are using works with multiple data centers across the globe. It tries to figure out the closest data center to use when you connect.
That decision making process is also known as geolocation, but it doesn’t always work well. When it doesn’t, we indicate it so you can know about this.
Potential risks
Connecting to a non-optimal data center means you are “spending” longer time over the public internet with the media packets. This translates into longer round trip times and sometimes also to higher packet loss percentages.
All in all, it can lead to poorer media quality than what you can achieve.
Suggested actions to take
- Sometimes, this has to do with the DNS server configuration used. Cloudflare (DNS 1.1.1.1) is known to cause issues from time to time with this for example. In such a case, switching a DNS provider on your device or just letting the ISP resolve DNS addresses might solve the problem
- It might be related to a use of a VPN on your end, forcing traffic to go to a specific data center
- Your account on the provider’s application might be configured to use a specific data center. Either by mistake or purposefully, as there might be other considerations at play here related to call routing