Configuring a Private MCU/Video Conference Server

Introduction

This document describes the steps required to switch between 3CX Cloud Video Conference to an On-premise Video Conferencing Server.

Setting Up a Video Conferencing Server

  1. Go to “System” > “Conferencing” > enable “Private Video Conferencing Server”.
  2. Add a Meeting Server and wait for a couple of minutes. A dialog configuration will be shown.

Configuration Guide Dialog

  1. Prepare a clean and newly installed Debian 12 Linux machine, with the following ports open, (TCP 80 443 and UDP 48000-65535) inbound and outbound.

3CX WebMeeting MCU Installation

  1. Copy and Paste the command directly to the terminal and run it. You will need to choose whether to use a 3CX FQDN or a Custom FQDN.

Page Showing Status of Meetings

  1. Wait for the installation to complete and once successful your Video Conferencing Server will appear connected in the Status of Meetings page.

Current Meetings Section

  1. When you schedule your next WebMeeting, you will see the “Current Meetings” section which includes Video Conference statistics.

Hardware Specs

Debian 12 64-bit VM: 4-24 vCPU, 4-16 GB RAM, 50 GB storage, 50-500 Mbps down/200 Mbps-1 Gbps up depending on your usage. More detailed documentation and info will be out at a later date.

ACL/Firewall

Each on-premise installation environment is different, therefore, it is your responsibility to define the appropriate ACL/firewall rules that will not allow the 3CX host to reach sensitive subnets/endpoints within your network. This must be handled on the networking layer in gateways and firewalls and in the forefront of 3CX On-premise Video Conferencing Server, to prevent pivoting our infrastructure in the case of a compromise.

Last Updated

This document was last updated on 4 September 2024

https://www.3cx.com/docs/video-conference-server/