Resolving Firewall Issues on Session

  • Updated

 

For networking environments with firewall or proxy restrictions, use the following configuration recommendations to allow full functionality of Session:

Domains

Session uses a combination of primary/in-house and third-party services during normal use. The following domains should be included in a firewall allowlist:

*.session.com 
*.hopin.to
*.hopin.com
*.videoml.team
chat.stream-io-api.com
*.launchdarkly.com
*.segmentapis.com
*.datadoghq.eu
images.unsplash.com
cmp.osano.com

Ports

Minimum Requirements:

The minimum requirement is that TCP port 443 is open. Some firewall/proxy rules only allow for SSL traffic over port 443. You will need to make sure that non-web traffic can also pass over this port.

Better Experience:

In addition to the minimum requirements being met, we also recommend that TCP & UDP ports 3478 be open, which is the default port for the STUN and TURN network protocols. STUN and TURN are used for realtime voice/video and messaging and blocked connectivity may disrupt video and chat functionality. We recommend not to block this traffic.

Best Experience:

For the best possible user experience, UDP ports 1025 - 65535 should be open for users. Opening this port range allows for audio/video network routes that may otherwise be relayed, which can have an adverse effect on interactive performance.

Was this article helpful?