Follow

Firewall & Browser Requirements

Overview
Glia works automatically within most corporate firewalls. However, there are some specific firewall requirements for particular components of the platform.

 

1. General Firewall Requirements

Glia primarily uses port 80 and 443 with TCP / HTTP / HTTPS traffic.

Please ensure that *.salemove.com (Global) OR *.salemove.eu (Europe) domain is allowed.

In general, Glia opens a persistent socket connection from the browser to Glia Infrastructure. The socket connection relies on TCP via HTTPS/WSS. Please make sure that TCP packets are not blocked for HTTPS/WSS and that the connections are not terminated prematurely by the Firewall. 

Moreover, while having an A/V conversation, If you are hearing lagging or you think your firewall may be blocking or slowing down the audio/video stream, please make sure turn.salemove.com, turn2.salemove.com, turn3.salemove.com on port 80 and 443 with UDP & TCP / HTTPS traffic is allowed.

Please take into account your region.

Region DOM identifier Configuration
Global .com

turn.salemove.com

turn2.salemove.com

turn3.salemove.com

Europe .eu

turn.salemove.eu

turn2.salemove.eu

turn3.salemove.eu

Enabling UDP traffic is the preferred recommendation for lower latency. If UDP is not an option Glia works well using only TCP, however, there is a penalty on speed.

Known firewalls that you must allow traffic through: ZyXEL

 

2. Telephony Specific Firewall Requirements

Glia also has an option to use Twilio for the operator facing telephony parts of our system. Twilio's firewall requirements are described here. You can test your firewall for Twilio using the below links: 

Note:

When using Twilio, you need to Whitelist ALL of Twilio's IP address ranges and ports on your firewall for SIP signaling and RTP media traffic. More information about Twilio IP address whitelisting can be found here.

Customers can opt out of using Twilio for the operator facing system allowing all the audio to come through their normal phone system.

 

3. Firewall Blocks

If you have site blocks, for Glia to work properly, please allow the following:

Region DOM identifier Configuration
Global .com

*.salemove.com

*.twilio.com

Europe .eu

*.salemove.eu

*.twilio.com

 

4. Content Security Policy

If your site uses Content Security Policy, then for Glia to work properly, please add the following configuration based on your region:

Region DOM identifier Configuration
Global .com

connect-src 'self' wss://*.salemove.com https://*.salemove.com

Europe .eu connect-src 'self' wss://*.salemove.eu https://*.salemove.eu

 

Please note that poorly set up Content Security Policy can result in CORS errors in the operator application console logs. For example CORS policy: No 'Access-Control-Allow-Origin' error.

site.url has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Described error in web browser Developer's tool console:

Screen_Shot_2019-04-05_at_11.06.05.png

5. Ad blocking

Occasionally Glia scripts are not allowed by some specific browser extension for Ads blocking  (e.g. Ublock). If an Ad Block extension is blocking Glia scripts on the page then simply disable the extension on that site by clicking on the Ad Block extension icon, the browser will display the extension settings, from those settings click on disable. After you have disabled the extension refresh the page.

 

Troubleshooting Network Issues

If you are having problems related to the network you can utilize Chrome's network monitoring tools to generate a report of the network traffic which can be later used by Glia to help in the troubleshooting process.

If you are experiencing issues on the operator side (app.salemove.com), please follow the below steps:

  1. Log out of Glia and close Chrome
  2. Open Chrome and go to chrome://net-export/
  3. Click "Start Logging to Disk"
  4. Choose a folder in which you want this file to be saved
  5. Open a new tab and go to app.salemove.com, log in and make sure the issue occurs
  6. Go back to the chrome://net-export/ tab
  7. Click “Stop Logging”
  8. Send the file to your Glia contacts

If you are experiencing issues on the visitor side, please follow the below steps:

  1. Log out of Glia and close Chrome
  2. Open Chrome and go to chrome://net-export/
  3. Click "Start Logging to Disk"
  4. Choose a folder in which you want this file to be saved
  5. Open a new tab and go to your site where Glia is installed and make sure you can recreate the issue
  6. Go back to the chrome://net-export/ tab
  7. Click “Stop Logging”
  8. Send the file to your Glia point-of-contact
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments