1c:I[869440,["/_next/static/chunks/75d2c4075a475375.js","/_next/static/chunks/d1235a80671f2edd.js","/_next/static/chunks/86d2156c58e5da3a.js","/_next/static/chunks/c7a67b723df8f377.js","/_next/static/chunks/e46e2fc92aeea261.js","/_next/static/chunks/38c06e352c6a5c07.js","/_next/static/chunks/d4ccca391b5cafb6.js","/_next/static/chunks/8a30997d5c2e7c97.js","/_next/static/chunks/200000012bb724cc.js","/_next/static/chunks/d5699eb51d77a346.js","/_next/static/chunks/390f80f98f6bf3ba.js"],"default"] 1d:T6d4,

VoIP calls don’t need anything special done to your firewall to make them work. This is because each side of the VoIP call is initiated from each side of the call.

The majority of firewalls will allow outbound traffic on any port (Lets call it a door from now on!) you wish. This is because the traffic is being initiated from within your network and the firewall knows you can be trusted.

Once it initiates traffic outbound on it’s chosen port to Yay.com it will keep that door open to Yay.com to continue to communicate with. It won’t be open to all, just to that conversation that your firewall and us are having at that time, whether that’s waiting for a phone call, receiving/making a phone call or the actual audio of that phone call.

In some very very rare cases, it it is of course possible that your firewall decides to close that door either midway through the conversation or right after it starts. It’s a highly unusual scenario and if a firewall is configured this way, it will be limiting to not just VoIP calls, but many other things over your data connection.

In most cases, the simplest way to resolve a limitation like this is apply a wildcard to your firewalls “white list” that says allow all/traffic to and from anything @yay.com

If you need any further help today, please don't hesitate to contact