Installation

To install the LiveSwitch Server, make sure your machine meets the server requirements.

The following diagram shows the LiveSwitch Server components that are necessary for your client app to run:

flowchart TB G(Gateway Cluster)-->R(Redis) G-->P(PostgreSQL) S-->G M(Media Server Cluster) C(Clients)--> M C-->S(SIP Connector) r0-->M M-->G r1-->r2 r1-->r3-->r2 r0-->G r0-->P1(PostgreSQL) r0-->RabbitMQ subgraph r0[Recording] r1(Monitor) r2(Mover Cluster) r3(Muxer Cluster) end classDef default fill: #D8EFF9,stroke:#86CBEE; classDef f1 fill:transparent,stroke:#AAADB4,stroke-width:2px; class r0 f1;

Components	Usage	Requirements
Redis	Stores ephemeral data	Required. Version 3.2.100 or newer Cluster mode is turned off. LiveSwitch doesn't support cluster mode and doesn't work properly if cluster mode is configured.
PostgreSQL	Stores configuration data and recording information	Required. Version 11 or newer
RabbitMQ	Passes messages among Recording Monitor, Recording Mover, and Recording Muxer	Version 3.8.11 or newer
Gateway	Connects the various parts of LiveSwitch	At least one Gateway
Media Server	Manages SFU and MCU sessions	At least one Media Server
SIP Connector	Allows LiveSwitch to connect to SIP endpoints	Optional
Recording Monitor	Manages recording database and runs migrations	Required if you enable recording management
Recording Mover	Moves recording files to cloud	Optional
Recording Muxer	Muxes recordings	Optional

Note

LiveSwitch v1.11 and older use Redis to store configuration data. LiveSwitch v1.12 and newer can use PostgreSQL instead of Redis to store configuration data. It's highly recommended that you use PostgreSQL instead to store configuration data. Using Redis to store configuration data is deprecated and is going to be removed in a future release.