This article covers:

KUDO Firewall rules

Using KUDO with a proxy

IP ranges

KUDO Firewall rules

Unless you are using a dedicated server (PaaS), where each server has its own IP address, the following domain names will need to be whitelisted:   

NOTE:

Unless you are specifically informed that you are using KUDO on Paas, then you are using the SaaS variant.

DOMAINS

• *.kudoway.com
• *.kudoway.eu 
• *.tokbox.com
• *.opentok.com

PORTS

• Open the UDP ports 1025 – 65535 ( for the best experience), this has a great impact on the quality of the session;
• Open the TCP port 443
• Open UDP Port 3478  (If you are using KUDO on a dedicated server [PaaS], then this can be blocked and enforced TCP instead of UDP).
• Make sure to open the UDP port 3478 for inbound and outbound traffic for:
  • *.opentok.com 
  • *.tokbox.com
    

HTTPS CERTIFICATE VERIFICATION

• oscp.godaddy.com
• crl.godaddy.com

Using KUDO with a proxy

If the only way to access the Internet from your network is through a proxy then it must be a transparent proxy or it must be configured in the browser for HTTPS connections.

WebRTC does not work with proxies requiring authentication.

IP ranges

Our servers can be reconfigured in real-time, so the IP range can change dynamically based on traffic conditions. We suggest whitelisting domain names instead of the below.

US Server
18.210.55.0
52.205.123.254
54.221.231.39
54.221.227.27

EU Server
18.184.190.85
52.29.212.117
35.156.104.68
35.157.48.210