Server Docs for 1.2.x

This documentation is specific to LiveSwitch 1.3.x (and higher) server components. For information on LiveSwitch 1.2.x (and older) server components, see Legacy (1.2 and older).

Server Components

LiveSwitch Server consists of three server components:

  1. The Gateway - provides signaling functionality allowing your clients to make connections to Media Servers.
  2. The Media Server - provides WebRTC connections allowing your clients to stream media through SFU or MCU connections.
  3. The SIP Connector - provides interoperability with third-party SIP services.

Set up a development environment 

  • For development, you are required to set up at least one Gateway and one Media Server for your clients to get SFU or MCU connections. 

Set up a production environment

For production, you are recommended to set up the following:

  • At least two (load balanced) Gateway Servers for redundancy.
  • Depending on your peak concurrent usage, you may require a cluster of Media Servers to handle your media traffic.
  • If your use case requires SIP interoperability, you need a SIP Connector.

Server Requirements

The following specifications describe the hardware requirements for each LiveSwitch server component:



  • Allow inbound TCP traffic on port 8080 (default, configurable) for HTTP
  • Allow inbound TCP traffic on port 8443 (default, configurable) for HTTPS

Minimum Hardware

  • 2x CPU
  • 2GB RAM
  • Moderate network performance

Recommended Hardware

  • 4x CPU
  • 4GB RAM
  • High network performance

High Availability

  • 2+ gateways
  • Load balance the with high-availability guarantees

Media Server


  • For clustering, allow TCP traffic on port 8445. If 8445 is unavailable, Media servers try the next port incrementally until one is available. That is  8446, 8447, 8448, 8449, etc.
  • For client connections, allow inbound UDP traffic on ports 49152-65535 on public interfaces.


  • 4x CPU
  • 4GB RAM
  • High network performance

Recommended Hardware

  • 8x CPU
  • 8GB RAM
  • Highest network performance

High Availability

  • 2+ media servers

SIP Connector


  • For SIP requests, allow UDP and or TCP traffic on port 5060 on public interfaces.

Getting Started

See the Installation and Configuration guides to get your server environment up and running quickly. For more advanced issues, see Advanced Topics.