Whitelisting (Virtual event)

This article describes what can be whitelisted to guarantee a good connection with LetsGetDigital.

DNS Whitelisting

If possible it's best to whitelist based on domain names. The following domains should have access:

*.letsgetdigital.io *.daily.co turn.aquila-eu.wbcnf.net

turn.aquila-eu.wbcnf.net is a specific server for Samba used in case certain ports are blocked.

Samba explanation

The server tries to proxy media traffic over UDP or TCP on ports 80 or 443. If media traffic cannot be carried over the direct connection to those UDP ranges on the media server - the front end tries each port/protocol to see if it can carry media traffic that way.

TURN is only used as a last resort, so it either allows the media server UDP range OR allows UDP/443 (preferred) to the TURN server.

For more information see (select the 'Ports' tab):

Testing the TURN server

You can test in Windows by playing with the in-built firewall.

  • Create a rule - Block UDP out - ports: 1000-65535 ( don't enable it )

  • Join a session and broadcast

  • Enable the rule - note your audio and video freezes

  • Refresh browser - note your audio and video works again

If you really want to prove TURN is being used to carry traffic, you can also inspect chrome://webrtc-internals/

Select the legacy API to get the stats from there, and find 'Conn-0-1-0) googCandicatePair' The find 'googleLocalCandidateType'

REF: https://developer.mozilla.org/en-US/docs/Web/API/RTCIceCandidateType

With the UDP outgoing ports blocked, this changes to relay meaning the TURN server is proxying the media traffic. Without these ports blocked - you will likely see stun or prflx candidate show there.

Used ports




Default SSL connection


For signalling and media tunnelling, where necessary

40000 - 65534

For direct peer-to-peer media connections

Daily.co explanation

Daily uses a variety of domains, IP addresses, ports, and protocols to connect calls. If you're trying to make calls to and from a network behind a corporate firewall, or through a VPN, you'll need to make sure you can access the following domains:

  • *.daily.co if possible. If not, you'll need to be able to reach these domains in addition to your account's subdomain.daily.co:

    • [b.daily.co](<http://b.daily.co>) and [c.daily.co](<http://c.daily.co>) for javascript, images, sounds, and fonts

    • [gs.daily.co](<http://gs.daily.co>) for room status updates

  • *.wss.daily.co for SFU media connections. The first hostname will usually resemble an AWS IP, such as ip-172-31-10-133-ec2.wss.daily.co.

  • prod-ks.pluot.blue (a Daily-owned server used for ICE negotiation)

  • *.twilio.com (STUN server/TURN relay for coordinating peer-to-peer calls)

  • *.xirsys.com (STUN server/TURN relay for coordinating peer-to-peer calls)

Additionally, you'll want to make sure you can access *.daily.co on port 443, as it's used for a variety of fallback connection types.

For more information see:

IP Whitelisting

Let's Get Digital can possibly use the following IPs.

Note: This list contains a very large set of IP addresses. We have a big range of IP addresses because all the services are behind a DDOS-protection layer. Publishing or sharing the IP-addresses



IPv 2400:cb00::/32 2606:4700::/32 2803:f800::/32 2405:b500::/32 2405:8100::/32 2a06:98c0::/29 2c0f:f248::/32


Media servers

Last updated

Contact support

Mail us