Firewall Setup

To ensure optimal performance when using VideoSDK, it's important to configure your network firewall (if any) to allow connection to VideoSDK servers.

Who This Applies To

If your organization uses a firewall for network security and it is not configured to allow connections to VideoSDK servers, you may encounter:

• Connection failures

• Disruptions during sessions

To avoid such problems, ensure your firewall allows the necessary traffic by implementing one of the recommended firewall policies outlined below.

Firewall Policies

Full Access Policy

The simplest policy is to allow connections from all subdomains of videosdk.live over both TCP and UDP across all ports.

This covers API, Signaling, Media, and TURN servers.

*.videosdk.live

Fine Grained Policies

If broader policies are not permitted, you can apply the following rules:

1. API Server

   TCP: Port 443

   api.videosdk.live

2. Signaling Server

   TCP: Port 443

   You have two configuration options:

   1. Wildcard Subdomain Access (Recommended) Allow all regional signaling subdomains:

      *.rm.videosdk.live

   2. Explicit Host Access If wildcards are not permitted, allow these domains explicitly:

      in1.rm.videosdk.live
      sg1.rm.videosdk.live
      us2.rm.videosdk.live
      eu1.rm.videosdk.live
      uae1.rm.videosdk.live
      aus1.rm.videosdk.live

3. Media Server

   If the Primary connection fails, Fallback connection will be used.

   Primary: UDP on Ports 40000 to 60000

   Fallback: TCP on Ports 40000 to 60000

   media.videosdk.live

4. Turn Server

   If the Primary connection fails, Fallback connection will be used.

   Primary: UDP & TCP on Port 3478

   Fallback: TCP on Port 443

   turn.videosdk.live