Knowledgebase
Firewall Exceptions
Posted by Pete Cabral on 21 October 2013 11:45 AM

Firewall Exceptions

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.  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 block connectivity to our server and/or audio from passing through.  If you experience problems or need assistance on changing the settings of your firewall ,  please contact your IT staff.

 Please ensure that all IP addresses/DNS names are allowed access in and out of your firewall on the ports listed below.

Contact Support to obtain your specific PORT to plug into the table below. 

 

****Update****

Items in BLUE are new as of April 1, 2016 and all are required for continued use of ESChat. 

  

Description

Host Address

Type

Port

              Potential Client Firewall Issue

ESChat Provisioning server

provision.sla-ptt.com,

54.215.171.160

TCP 

80

&

443

The client displays a failure message after attempting to activate with its Activation Code. 

ESChat Enterprise server

aws-client.sla-ptt.com,

13.56.0.0/16
50.18.0.0/16
52.8.0.0/16
52.9.0.0/16
52.52.0.0/15
52.95.246.0/24
52.95.255.96/28
54.67.0.0/16
54.151.0.0/17
54.153.0.0/17
54.176.0.0/15
54.183.0.0/16
54.193.0.0/16
54.215.0.0/16
54.219.0.0/16
54.241.0.0/16
184.72.0.0/18
184.169.128.0/17
204.236.128.0/18

TCP

80

&

443

The client displays a failure message during registration.

ESChat Enterprise server ESChat Signaling port

54.219.138.108,

54.193.35.65, 52.8.165.33 

TCP

<port>

The client displays a failure message during provisioning, registration, or other operation. Such as a 'Failed to provision with ESChat system: Error Code 4' message.

ESChat Enterprise server ESChat Data port range

54.219.138.108,

54.193.35.65, 52.8.165.33 

UDP

<port thru port+8>

The client unsuccessfully sends or receives audio during a call.

Dispatch Client Mapping Tiles

download.sla-ptt.com,

54.215.171.160

TCP

80

Map portion of the Dispatch Client is black.

Client Mapping Tiles

maps.google.com 

(Google uses 12 different ip address for this, addition by DNS name is Required)

TCP

80

Map portion of the Dispatch Client is black.

Apple APNS (iOS Only)

17.0.0.0/8

TCP

80

&

5223

Apple devices don't recieve the Apple Push Notificatiions when connected to the network.

 

For help with this or any other questions, please start HERE with our Firewall Troubleshooting document, or contact Support.

(1 vote(s))
Helpful
Not helpful

Comments (0)