Firewall Exceptions for On-Premise ESChat Deployments

This document is specific to on-premise ESChat deployments.

We require a 12 min TCP port registration timer and a 1 min UDP port registration timer.

The ESChat client requires specific network routes to communicate between the host device (such as a smartphone or computer running the client) and the remote servers.  We continue to push our architecture and deployment model forward to improve security and redundancy for our customers.  If you have firewall rules in place, the following tables current rules that are required to support our newest servers and our disaster recovery instances.  All ports are outbound only.  Please enter all information as listed in the tables. We do not control IP ranges required by third party providers. While most third party vendors will accept IP addresses, Google Maps requires the DNS (Domain Name System): https://maps.googleapis.com/

If your device has a firewall enabled or is on a network that operates behind a firewall, like many corporate wired and Wifi networks, it may be blocking connectivity to our server and/or audio from passing through.  If you experience problems or need assistance changing the settings of your firewall,  please contact your IT staff.

ESChat requires various ports to be opened for both outbound traffic and inbound response (as requested from the client) to the IP addresses listed below (8 including the Disaster Recovery addresses).  The signaling port and data port range are specific to each customer's build. 

Apple requires 2 ports be opened for outbound traffic to the IP range below for the APNS Push Notifications.

Google requires a port be opened for outbound traffic to the DNS names below.