Introduction & Licensing - 3CX Virtual PBX Server
Zero Admin
With the new Dashboard
Bulletproof Security
With SSL certs and NGINX
Install on $150 Appliance
Intel MiniPC architecture
New, Intuitive Windows Client
More themes, more UC
More CRM Integrations
Scripting Interface to add your own
Improved Integrated Web Conferencing
iOS and Android apps included
Personal Click2Meet URLs

Introduction & Licensing

Installing 3CX Phone System as a Virtual PBX Server

3CX Phone System allows you to host up to 25 separate 3CX Phone System virtual PBX instances on one Windows Server 2012 machine. Each instance is entirely separate from the other and allows you to completely separate configurations and data between customers.

By hosting 25 Virtual PBX instances on one Windows Server machine, you can avoid having to license & manage individual Windows instances, saving greatly on licensing, management, operating system overhead and hardware costs.

Connect each instance to its own dedicated SIP trunk or Gateway port and keep call billing perfectly separated for each customer. The feature set of 3CX Phone System is almost identical whether you install it as a Virtual PBX in the cloud or as an on premise edition.

3CX Phone System allows you to easily deploy and manage 3CX Phone System Virtual PBXs:

Backup / Update all 3CX Phone System Virtual PBX instances

3CX offers a tool that is able to backup or update ALL instances on the machine and restore all instances on another machine if need be. Automate backup on a scheduled basis and restore all instances in case of hardware failure.

Full VMware and Hyper V compatibility

If you want to leverage your existing Vmware or Hyper V knowledge you can do so with 3CX Phone System. It has been verified and tested against the leading virtualization platforms and allows you to take full advantage of VMware and Hyper V management and redundancy features.

Easily configure a new 3CX Phone System Virtual PBX

Ability to quickly create a 3CX Phone System configuration using our wizard or from a web input form: Import users, configure trunks and push out to a new 3CX Phone System instance.

Allow companies to manage user settings with granular user access

Allow customers to manage their own extensions, but not Trunk, Gateway and other system configurations. Two additional user levels: Department manager, who can manage the extensions of his/her group, and System manager, who can manage all extensions. The System administrator level allows the customer full access to the system and can be disabled to avoid any misconfigurations by the customer.

Easy remote provisioning

3CX Phone System can easily provision remote IP Phones and 3CXPhone instances via the extended SBC which acts as an agent for provisioning requests. With the Session Border Controller you can send phones readily configured for true plug and play at the customer site.

Eliminate firewall and bandwidth issues with inbuilt Session Border Controller

3CX Phone System features the unique SBC, which allows all SIP traffic for the customer to be tunneled over a single port. Drastically simplify remote installs and eliminate firewall configuration issues. Furthermore, the intelligent 3CX SBC can detect calls being made between local extensions and avoid sending audio streams to the Virtual PBX – saving valuable bandwidth and dramatically improving audio quality.


Each 3CX Virtual PBX is licensed separately, depending on the requirements of the customer, i.e. number of simultaneous calls, whether customer requires PRO edition and so on. The actual platform - i.e. the installation of 25 instances, is provided FREE of charge. Licenses for 3CX Phone System are available in two types:

Perpetual licenses

Customers can buy a perpetual 3CX Phone System license that can be activated either in the cloud or on-premise. This is the most economical way to license 3CX Phone System.

Subscription licenses

Customers that prefer to pay per month or per year, can opt for time based subscription licenses. Time based licenses include maintenance but are more expensive in the long run. However they allow partners to license 3CX Phone System for short period of times and reduce the ‘risk’ when entering into contracts with customers.

You might also be interested in:

Ask a Question

Please only post questions in regards to the document you are currently reading.
Technical support or pre sales questions must be posted via the support or sales channels and such comments will be deleted. Thank you for understanding

Leave a Reply

  1. Brad

    So how does the cloud/SBC arrangement work with FXO/PRI gateways? Can you still route calls out local POTS or PRI in addition to sending them to the cloud PBX to be SIP trunked?

    June 30, 2015 at 7:21 pm Reply
    • Charalambos Eleftheriou

      Hi Brad, When you say Cloud Server if you mean the a full public (hosted) version then you can only use VoIP providers. If you a referring to the Cloud Server that you install locally on your network and host it for other companies then you can achieve call routing through gateways using Point to Point VPN Connections. 3CX SBC is fully supported on all versions.

      July 1, 2015 at 10:23 am
    • Brad

      So how is the v14 multi-tenant cloud version with SBC any different from a topology standpoint than v12 with regards to call routing?

      July 1, 2015 at 3:52 pm
    • Charalambos Eleftheriou

      Hi Brad, No change in regards to the operation of SBC. There will though be a release of a v14 of 3CX SBC for windows very soon. Also there is an updated procedure for the upgrading or installing the new version of SBC for Raspberry Pi available.

      July 1, 2015 at 4:03 pm
  2. Sorry, didn’t find any information regarding my question.
    Do we need to have different (25) IP addresses for various clients instances to access the system, register endpoints and make/receive calls?

    July 7, 2015 at 11:19 am Reply
    • Charalambos Eleftheriou

      Hi Oleg, You will only need one static public IP and one static internal ip. Then you will register an FQDN that resolves externally and internally. The FQDN will be the same for all instances and will be prepended with the name of the instance. So if your FQDN is: https: // then you configure an instance called “instance1” then to access that instance you will use: https: // Documentation will be available very soon. In the meantime see this guide on creating FQDN using Spilt DNS:

      July 7, 2015 at 11:45 am
  3. Brent

    Subscription licenses, do you have to reinstall the software each month? when the license is renewed or how does this work?

    September 27, 2016 at 4:58 am Reply
    • No – There is a check that is made over the internet. If the key is renewed, the product will understand. If license is not renewed or there is no internet connection, then it will deactivate.

      September 27, 2016 at 5:34 pm