Firewall Exceptions for Singapore Cloud
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 out architecture and deployment model forward to improve security and redundancy for our customers. If you currently have firewall rules in place, the following tables outline existing and new 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 name:
If your device has a firewall enabled or is on a network that operates behind a firewall, such as 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.
The document is specific to AWS Australian cloud deployments.
We require a 12 min TCP port registration timer and a 1 min UDP port registration timer.
ESChat requires various ports to be opened for both outbound traffic and inbound response (as requested from the client) to the IP addresses. The signaling port and data port range are specific to each customer's build.
ESChat requires various ports to be opened for outbound traffic to the IP addresses as listed below.
| Description | IP Addresses | Port(s) | Type |
| ESChat Provisioning Server |
Primary: 54.215.171.160 54.219.138.108 52.61.94.106 3.31.151.6 3.31.160.231 18.252.168.182 18.253.93.42 18.254.200.140 Disaster Recovery: 35.153.48.78 |
80 & 443 | TCP |
| ESChat Signaling Port |
13.213.227.185 13.213.178.154
|
To determine your signaling port, go to the Administrative Portal and view your customer profile. You'll see your TCP Signaling Port.
(Example: 7400 TCP) |
TCP |
| ESChat Data Ports |
13. 213.227.185 13.213.176.154 3.0.136.244 |
4201-4264 | UDP |
AWS requires two ports to be opened for outbound traffic to various IP ranges due to the Network Load Balancer (NLB)
Find more documentation on AWS IP Ranges here: http://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html
A real time JSON file that lists all AWS IP ranges by region and availability zone here: https://ip-ranges.amazonaws.com/ip-ranges/json
| Description | IP Addresses | Port(s) | Type |
|
ESChat Web Portal |
52.76.89.45 52.221.155.163 122.248.215.27 |
80 & 43 | TC |
Apple requires two ports be opened for outbound traffic to the IP range below for the APNS Push Notifications.
| Description | IP Range | Port(s) | Type |
| Apple APNS (iOS Only) | 17.0.0.0/8 | 80 & 5223 | TCP |
Google requires a port be opened for outbound traffic to the DNS names below.
| Description | DNS Name | Port | Type |
| Client Mapping Tiles |
maps.googleapis.com fonts.gstatic.com |
80 & 443 | TCP |