Blogs

3CX V20 RC4 is the lastest release from the team at 3CX. It features a new Admin Console which replaces the legacy Management Console.

On top of performance improvements to the call manager (SIP server) which allows support for 50% more users on the same hardware, 3CX V20 also features Debian 12 as the underlying operating system. Debian 12 will provide the most up to date security patches until 2026.

New Admin Console

A significant feature of V20 is the brand-new management console, the 'Admin Console,' which is integrated into the 3CX web client. Users can seamlessly transition to the Admin Console within the 3CX web client without requiring a separate login or URL. This update streamlines the configuration process significantly.

By consolidating the web client and management console into a single link, we now have a simplified, easy-to-remember FQDN for both users and admins.

For instance:

In V18: https://[COMPANY NAME HERE].3cx.us/webclient/

In V20: https://[COMPANY NAME HERE].3cx.us/

With this user-friendly FQDN and the option for users to set their own password or utilize SSO, there is reduced dependence on the welcome email.

Department and Role Framework

A notable feature in V20 is the introduction of "Departments," comparable to Active Directory Organizational Units (OUs). Departments can be customized to include their own:

• Office hours
• Holidays
• Time zones
• Language
• Soon to include: Phonebook, CRM configuration & Blacklist
• Administrators, managers, and owners

Departments play a crucial role in the new security framework, offering administrators the ability to define permission settings through the use of departments and roles. For instance, you might establish a "Sales" department with a dedicated administrator responsible for user management and IVRs. By default, trunks are system-wide.

Security roles are allocated according to the groups to which a user is affiliated. Consequently, if a user is part of the default group that encompasses all users and is designated as a group admin, they acquire the authority to manage all users.

See our guide here on how to upgrade to V20 today!

---

Preflight Upgrade Requirements

Check if any of the known limitations apply to you below.

V20 Upgrade Requirements

• 2 Core, 2 GB. All 3CX's hosted by Voxtelesys come standard with a minimum of 2vCore and 4GB's of memory, so no worries here.
• Sufficient Disk Space needed. Ensure a minimum of 5 GB of free disk space.
• The source list must remain unaltered for a successful upgrade; any modifications will result in failure Remove any additional source lists. If you are utilizing Microsoft Azure, verify by checking "cat /etc/apt/sources.list.d/microsoft-prod.list."

Not Implemented Features and Roadmap

In an update 1 or final (TBD)

• Extension email must be unique and for now can be left empty. In the next update, leaving the email empty will disable Web Client access. You do not have to specify an email for each extension. So you can omit the email. This will automatically disable Web Client access (so it's also a security thing) This will be good for hotels, hospitals, schools etc everywhere where only a deskphone is required.
• V20 requires at least one user with the “System Owner” role assigned. This user should have a unique email address solely dedicated to their role and not utilized for any other extensions. If no System Owner is assigned, a tooltip message will appear, guiding you to set one.
• Import sheet will be expanded with group membership and role. We need some time to do this, it will be update 1 or 2.
• Multi Edit - we are aware of this and will address this in V20 but not now.
• You will need to make a ring group which will email all participants.

---

Roadmap Progression

This is the tentative timeline set forth by 3CX.

Hosted by Voxtelesys

• We will manage the upgrade process for you, ensuring that your system configuration is unaffected by any known limitations listed below.

Hosted by 3CX

• New trials and new customers will be deployed on V20
• Existing trials remain on V18
• Existing customers remain on V18 until January 2024 and will then be upgraded

On Premise

Customers will be able to choose between V18 and V20 for another two months at least.

• Linux customers can upgrade to V20 by clicking the Upgrade button whenever they are ready.
• Windows version of 3CX V20 should be available in January 2024.

Self Hosted

• The 3CX marketplace images for V20 are available with the final release.
• The V18 marketplace images for Google, Amazon AWS, Digital Ocean, and Vultr will remain available for customers to choose between V18 or V20 for at least two months.

SMB + FREE

• The multi-tenant version of 3CX will remain on V18 until February 2024.

Know limitations, not implemented features.

• Scheduled Reports

---

Preflight Checklist before Voxtelesys will upgrade your 3CX to V20

• Check 5GB of free disk space is available.
• Not using Dect/FXS Devices.
• Not using Hotdesking.
• DID's are setup in E164 format.
• WARN if using Custom Template, using STUN instead of SBC/Router phone.
• Not Bridging 3CXes.
• Not using Teams Direct Routing Integration.
• [email protected] Extension has the “System Owner” role assigned.
• WARN if using Call Flow Apps.

---

Sources:

• Quick Pit Stop with Release Candidate 4
• Update 9 - Paving the Way for V20
• V20 Version Upgrades - Top Reasons for Aborting
• Version 20 BETA - Phone Provisioning & 2FA
• New V20 Deployment Wizards + Amazon Lightsail
• V20 Roadmap: V20 - 3CX reloaded!
• Preview of 3CX Version 20
• Preparing for v20 Part 1 - Split DNS for 3CX
• Version 18 to Version 20 Update Tutorial
• Debian

Connect with Voxtelesys on Facebook, X, or LinkedIn.