VidyoConnect for WebRTC Server comes from the factory configured as a single Standalone server. It has a Media Server and a Session Manager. The role of the Media Server is to establish WebRTC calls to the browser application, communicate with the VidyoPortal, and establish calls to the VidyoRouter. The role of the Session Manager is to provide configuration for the cluster, monitor the Media Servers and distribute WebRTC calls to the best Media Server, and provide signaling and media proxying services.
Every cluster must have one or more Session Managers and one or more Media Servers. For very small deployments or lab setups, a single server can act as both the Session Manager and Media Server. A large deployment may have a single Session Manager (or two or three for High Availability) and many Media Servers.
Only Session Managers require public IP addresses. The public IP address may be directly configured on the Session Manager or may be a static NAT configured on a firewall. Media Servers do not need public IP addresses. The Session Managers and Media Servers must be able to reach each other.
The Media Server that is on the same server as the Session Manager also must be added to the list of Media Servers and configured in order to be used. In larger cluster configurations, it may make sense not to configure it.
Once VidyoConnect for WebRTC Server is added to a Cluster in a Media Server role, its Admin portal only provides a MAINTENANCE tab with controls for security, downloading logs, upgrading your system, and shutting down and rebooting the machine.
Once you add a server to the cluster as described in Adding Media Servers to the Cluster, the Session Manager requests heartbeat service from the Media Server. Once the Session Manager receives the heartbeat from the server, it makes the Media Server available for calls.
For High Availability, you may configure multiple Session Managers to use the same Media Server nodes. With a multiple Session Manager configuration you will need to have a single FQDN with DNS load balancing across the Session Managers. When building a cluster with Media Servers handling 50 or more simultaneous calls, it is recommended not to use the built-in Media Servers on the Session Manager servers in order to reserve resources for media proxying.