3CX Cloud Server Release Candidate

We’re proud to announce our new 3CX Cloud Server! 3CX Cloud server replaces the old Multi tenant version of 3CX Phone System 11. 3CX Cloud Server not only runs 3CX Phone System v12 rather then v11, but has been greatly improved to allow 3CX partners to host 3CX Phone System as a hosted PBX for customers:

  • A central console to manage all tenants from a single windows application40
  • Easy deployment of IP Phones for customers
  • Secure provisioning via HTTPS
  • Far less ports per tenant, making firewall configuration much easier
  • The management console is now available via port 80/443 and only the URL changes per customer
  • 3CX Session Border Controller – available for Windows or Raspberry Linux – to avoid any firewall issues at the customers site as well as make plug and play provisioning of phones possible.
  • Central backup tool to back and restore ALL tenants in one go
  • Central Service Update tool to apply updates to ALL tenants in one go
  • Full VMware and Hyper V compatibility for redundancy
  • 3CX Cloud Server product information here. 


You can download 3CX Cloud Server here. Read the Installation and Configuration manual here.
Download 3CX Session Border Controller for Windows here.
3CX Session Border Controller for Raspberry Pi should be downloaded via the repository using apt-get. For more details consult the manual.


Liked this article?

Get notified of new articles
or share
You might also be interested in:
  1. Ash Alom

    Hi. I have just deployed 3CX cloud server RC recently. Have managed to get the 1st tenant working fine who is operating on Cisco spa 405g handsets. However I’m having issues with 2nd tenant who also owns Cisco handsets but the spa 525g model. Am I right in saying we need to deploy SBC on the client side to allow the Cisco hansets to work correctly. Is there a workaround to this as deploying SBC is not feasible with certain remote agents.

    February 24, 2014 at 5:29 pm
    • @Ash – unfortunately there is no workaround. What you can do is contact cisco because they have a VIA issue which comes into play when the server the phone is connecting to is NOT LISTENING on the standard SIP Port ie 5060. This is why everything works on the first tenant.
      We are still checking to see if we can make a workaround in the config but it is not looking so good at the moment….

      February 24, 2014 at 6:27 pm
  2. Steve Gosnay

    Hi there, Is a there a licencing restriction on the number of tenants at all?

    February 25, 2014 at 12:57 am
    • Steve Gosnay

      Forget this comment – my browser was slow to update the comments and it has already been answered.

      February 25, 2014 at 1:00 am