3CX Phone System Service Pack 5

We are pleased to announce a new update for 3CX Phone System 12. Service Pack 5 is now available for download directly from the 3CX Phone System Management Console. Special focus was made on User interface improvements to the 3CXPhone clients for Windows, iOS, Android.


  • Improved help documentation
  • Numerous improvements and fixes to 3CXWebmeeting module. Now Webmeeting is enabled by default for all installations
  • 3CXPhone crash on startup fixed
  • Fixed export call reports to CSV format
  • When Queue notification emails are delivered, CallID is sent in the email notification. Can be very useful for troubleshooting purposes
  • Added amount of time caller has been waiting in the queue to the email notification
  • Presence in iOS Client was not working when 3CX Server is Cloud Server
  • New 3CX Grey theme in 3CXPhone for Windows
  • Fixed stuck call notification in 3CX TAPI Server. Complete uninstall and re-install of 3CXCRM is required
  • Fix in Cisco SPA Phone Template for Cloud Server not able to get the logo provisioned correctly.
  • Fixed creation of Portal Admin Web

Change Log/Build History

You can see a complete list of changes by clicking on the following links:
3CX Phone System
3CXPhone for Windows
3CX Phone for Android
3CX Phone for iOS

Installing 3CX Phone System 12 Service Pack 5

Access the 3CX Management Console, click on 3CX Service Packs / Updates and download SP5.


Download 3CXPhone for Android and iPhone

Documentation and Links

We welcome your feedback and comments in the 3CX Forums and on our Facebook Page.

Liked this article?

Get notified of new articles
or share
You might also be interested in:
  1. Sean M. Harrison

    Any chance for the new polycom VVX (400 or 410) series being supported? I know you guys don’t like the polycoms… but… Really like these phones. : ) any chance?

    May 5, 2014 at 5:15 pm
    • Connex communication

      Yes please add polycom vvx support
      our clients are waiting for these phones a long time

      May 6, 2014 at 3:55 pm
    • Andy Moses

      Yes we would like the VVX series Polycom phones added to version 12. Polycom is a big player and it helps sell 3CX to a larger client when they recognize the Polycom name.

      May 7, 2014 at 4:21 am
    • @Andy – Yes no problem – you have a template for these phones? Send it to us and we will test it.

      May 7, 2014 at 10:51 am
    • Andy Moses

      The one thing customers hate is the fact the conference hangs up if you mis-dial the pin. It should allow them to retry. I tell my clients not to use the conference and most have switched to a web solution.

      2. Please allow us to select the outside internet IP address for all phones when provisioning. We don’t use stun nor do we use the 3CX SBC. We go direct from the phone to the 3CX outside IP address directly. We let the routers application layer gateway handle the NAT translation. Currently we have to modify the phones config files directly. This is not a user friendly method.

      May 7, 2014 at 4:30 am
    • @Andy – Open in features. We do this for protection.
      You can select the Public interface for provisioning. Go to phone provisioning and there you have public Provisioning address. Configure the Phones to work in STUN remote extension mode and this will put the public provisioning url in the configuration files. No need to modify templates directly.

      May 7, 2014 at 10:49 am
  2. Orlin Shopov

    3CX Phone for Windows SP5 is crashing if not able to detect sound card / device on computer on which is installed. 3CX Phone V12 SP4 was working normally.

    May 7, 2014 at 12:21 am
    • @Orlin – You must have something seriously wrong on your environment. Try on another machine and let us know. Install desktop experience if you want to troubleshoot.

      May 7, 2014 at 10:46 am
    • Orlin Shopov

      It’s reproducable on any machine without sound card like server (there are still reasons you may need this setup to work !) or most important, on machine on which sound card is not recognized by 3CX Phone V12 SP5, but recognized by other softphones (e.g. Skype). Something changed from SP4.

      May 7, 2014 at 11:10 am
    • @Orlin – We are going to investigate this.

      May 9, 2014 at 9:07 am
  3. Orlin Shopov

    TAPI driver is not working correctly after uninstalling and installing CRM plugin (SP5). Simple check with Windows built-in dialer fails. Used to work in SP4 and previous CRM module.

    May 7, 2014 at 1:11 am
    • @Orlin – It works 100%. You have some old tapi service provider installed. Happens with a Driver.
      Confirm that phone and modems is cleared
      Delete the file from System 32 3CXTapiSrvProv.tsp
      INstall again
      And try again

      May 7, 2014 at 10:44 am
    • Orlin Shopov

      This way it’s working

      May 7, 2014 at 11:06 am
  4. Richard McKeethen

    A short while ago, I received an email notification regarding the availability of a service pack 4A update on our 3CX V11 system. The note in the 3CX console mentions something about the Heartbleed vulnerability bug *not* being fixed with this update. Specifically, the update states, “Not able to protect V11 against Heartbleed vulnerability.” I click the link for more information, but it takes me to the Service Pack 4 update for V11, from last year, with no mention of Service Pack 4A, nor anything about why 3CX can’t or won’t address the vulnerability for customers using V11. That’s obviously a huge concern for me. What’s going on here?

    May 7, 2014 at 4:03 am
    • @Richard – In the Notes of the service pack it says Heartbleed fix – A blog post for this is coming on the way. Not sure what you are saying here. All you need to do is update to 4A. v11 is 1.5 years old… that link takes you to the previous blog post by mistake. We will make a blog post soon.

      May 7, 2014 at 10:40 am
  5. Craig

    Faxes to 3cx Fax Server stopped working after installing SP5.

    May 7, 2014 at 8:37 pm
    • Ben McDevitt

      How does fax work for you with 3CX? I was going to switch us over but I was told it is un-reliable.

      May 14, 2014 at 6:51 pm
    • It works absolutely reliable if you use a supported gateway or VoIP provider!

      May 19, 2014 at 11:12 am
  6. Dave

    Any chance this service pack addressed the issue where a call recording fails to terminate and you end up with a 4GB+ file. I have this happen at least once a month. Just annoying.

    May 9, 2014 at 7:50 am
    • @Dave – I think you have a stuck call that remains in the system being recorded. Then after the hardcoded limit of 3 hours, the call drops. This is why your call rec stops at around 4Gb. This is something that happens and needs to be investigated. However the time it takes to nail this is very time consuming. Is it always the same call / scenario?

      May 9, 2014 at 9:07 am
  7. Andy Moses

    I am repling to Nicky…

    From Nicky–>@Andy – Open in features. We do this for protection.
    You can select the Public interface for provisioning. Go to phone provisioning and there you have public Provisioning address. Configure the Phones to work in STUN remote extension mode and this will put the public provisioning url in the configuration files. No need to modify templates directly.

    Nicky, you cannot choose the public IP for the Polycom phone template. You can only choose local lan. Maybe you guys dont realize this as you can pick internet (Proxy) for other phone types. Please fix.

    Second. I have been selling 3CX for many years and have opened feature requests on the issue with the conference hagning up on the first failed PIN attempt. I have had many converstions with 3CX on this as my customers hate the 3CX conference as their customers are frustrated when they cannot join the confernce and wonder why it just hangs up on them. My only solution is to point them to a much more user friendly conferencing solution. Its too bad this has to be considered a feature. I dont know any other conferencing solution that just hangs up after the incorrect pin is entered.



    July 25, 2014 at 10:32 pm
    • @Andy
      Polycom phones are not designed to work as remote extensions. This is why we restrict Polycom phones to be used in the local lan.

      About the conference, this is a known issue. We will discuss this again internally.

      July 26, 2014 at 12:38 pm