Voice traffic on an organization’s local area network is similar to data traffic in that it is transmitted as packets over different devices. The main difference between data and voice traffic is that data traffic has the ability to resend information if it initially gets lost in transit. Voice traffic, on the other hand, cannot resend information because the packets must be received in order as a continuous stream for the information to make sense. As such, the way voice packets are treated in your network will have a significant effect on your call quality.
We recommend configuring your network such that voice traffic has a higher priority than data traffic. (See graphic below). This will ensure that issues related to voice packets are minimized and that your calls have optimal audio quality without having a noticeable effect on your data traffic. Traffic prioritization can be configured in a variety of ways, but we suggest prioritizing packets based on the IP addresses listed below. Please reach out to your organization’s network / IT team to determine the best way to set up traffic prioritization. If you do not have an IT team you can reach out to your internet provider to see if prioritization can be configured on your network.
If you want to prioritize voice traffic on your local area network, you can set up QoS rules using the following media server IP addresses. Doing so is optional, although we do recommend it.
|Region||Location||Media Server IP Address Range||CIDR notation|
|North America||USA (Virginia)||220.127.116.11 - 18.104.22.168||22.214.171.124/23|
|126.96.36.199 - 188.8.131.52||184.108.40.206/23|
US West Coast (Oregon) November 20, 2019
|220.127.116.11 - 18.104.22.168||22.214.171.124/24|
|South America||Brazil||126.96.36.199 - 188.8.131.52||184.108.40.206/26|
|220.127.116.11 - 18.104.22.168||22.214.171.124/24|
|Europe||Germany||126.96.36.199 - 188.8.131.52||184.108.40.206/25|
|220.127.116.11 - 18.104.22.168||22.214.171.124/24|
|Ireland||126.96.36.199 - 188.8.131.52||184.108.40.206/26|
|220.127.116.11 - 18.104.22.168||22.214.171.124/24|
|Asia||Japan||126.96.36.199 - 188.8.131.52||184.108.40.206/26|
|220.127.116.11 - 18.104.22.168||22.214.171.124/24|
|Singapore||126.96.36.199 - 188.8.131.52||184.108.40.206/26|
|220.127.116.11 - 18.104.22.168||22.214.171.124/24|
|Oceania||Australia||126.96.36.199 - 188.8.131.52||184.108.40.206/26|
|220.127.116.11 - 18.104.22.168||22.214.171.124/24|
We recommend you set up all of them, regardless of your location. Our service uses Global low-latency (GLL) routing to select the data center with the lowest latency. GLL region selection reduces audio latency in call scenarios where two or more parties are being connected in a region other than the United States. Using GLL, conference audio latency will be reduced in cases where two or more parties are physically close to one another, but far from the United States. For example, a call from Sydney to Sydney will see the greatest benefit from global low-latency as the difference from a locally routed media path and a media path that routes through the United States is the greatest. A conference call where all participants are dialing in from European countries which is mixed in Ireland will have lower audio latency for all parties versus the same conference mixed in the United States.Ports used: TCP 443, 3478 , 5349; UDP: 10000-20000
Additionally, Talkdesk enables DSCP by default in compatible browsers (currently Google Chrome) and the Callbar application. Capable browsers and Callbar will tag WebRTC media packets, enabling differentiated handling on a LAN, so that real-time media can be prioritized above other network traffic. These will be tagged as Expedited Forwarding (46).
If you are using a Windows OS, please check the article Implementing QoS on Windows Environments.
For more information about setting up Talkdesk, please check the article System Requirements and Network Settings.