Quickstart - Automatic Install | 3CX MCU Server
Introduction
This guide will take you through the requirements and steps of installing, using and troubleshooting the 3CX MCU meeting server.
Recommended VM Specifications
Select the appropriate VM size & environment for your meeting usage. A Debian 12 VM is required for the 3CX MCU installation.
- 25 License Seats: OS Debian 12 64 bit, CPU: 4 vCPU, Memory: 4 GB RAM, Storage: 50 GB, MCU Bandwidth: 50Mbps Down, 200Mbps Up
- 100 License Seats: OS Debian 12 64 bit, CPU: 8-16 vCPU, Memory: 8 GB RAM, Storage: 50 GB, MCU Bandwidth: 200Mbps Down, 500Mbps Up
- 250 License Seats: OS Debian 12 64 bit, CPU: 16-24 vCPU, Memory: 16 GB RAM, Storage: 50 GB, MCU Bandwidth: 500Mbps Down, 1Gbps Up
Firewall Configuration
- LetsEncrypt Certificate creation and renewal requires usage of port 80 TCP
- MCU requires usage of port 443 TCP and 48000-65535 UDP
- PBX must be able to reach wmr.3cx.net in order to download the MCU installation script & verify your DNS record.
TCP: 80, 443
UDP: 48000 - 65535
The PBX & MCU must be able to reach each other on their respective HTTPS ports.
Installing the MCU on Linux
Prepare your Linux machine:
- Ensure your Debian 12 is up to date.
apt update ; apt -y upgrade |
- On your Debian 12 command line perform the above command.:
To install the MCU:
- Go to your Admin Console > System > Conferencing > Video and select “Add Meeting Server”
- Click “Add Meeting Server” and wait for a response.
- You will be provided with instructions on how to install the MCU as well as a command to auto-install the MCU on your server.
- Copy the provided command, paste it and run it on your Debian 12 server’s command line as root.
- If all prerequisites are as expected, you should see the above installation wizard.
- When selecting option #1 “Use FQDN provided by 3CX and Let’s Encrypt SSL certificate”, the installer will automatically install the MCU, get you a 3CX provided DNS record and will generate a letsencrypt certificate for you based on that FQDN/DNS record.
- Once the installation is complete, if all prerequisites were correctly fulfilled, the MCU will be instantly online in your MCU monitor page in the PBX Admin > System > Conferencing > Video page.
- When selecting option #2 “Use custom FQDN and SSL certificates”, the installer will first request that you provide it with an FQDN that resolves to the current VM.
- If this step succeeds and the FQDN you provided matches the IP of the current VM, on your PBX, a temporary 3CX Provided FQDN is received as a placeholder for your final custom FQDN.
- The installer will then automatically install the MCU and provide you instructions on where to place your certificates.
- Once you place the certificates in the correct folder and restart the MCU, the FQDN on your PBX will change to the one you provided during the first steps of the installation and will appear “Green” indicating that it's online and ready to be used.
Uninstalling the MCU Package
Linux Meeting MCU - Uninstall & Install Procedure
- Find what version of the MCU and MCUManager you have installed by running this in your console:
dpkg - l | grep 3cx |
- Uninstall version e.g 20.0:
sudo apt-get remove 3cx-mcu20.0 (Where 20.0 replace with your version) |
sudo apt-get remove 3cx-mcumanager20.0 (Where 20.0 replace with your version) |
- Cleanup all unused components & dependencies installed alongside the MCU:
sudo apt-get autoremove |
See Also
- 3CX MCU & MCU Manager Troubleshooting
- The 3CX MCU Firewall Feature
- 3CX MCU Network Configurations
- 3CX MCU On-Premise Meeting Recordings
Last Updated
This document was last updated on 15 June 2024