27/08/2015
Upgrade 3CX V12.5 to 3CX V14 - http://www.internetvoipphone.co.uk/blog/upgrade-3cx-v12-5-to-3cx-v14/
Having recently upgraded our 3CX V12.5 to 3CX V14, we'd like to share our experienceIt is important to note that you should fully update your existing 3CX 12.5 edition as there is a service pack that prepares V12.5 for the V14 upgradeIf you are using IIS and have a third party trusted certificate, it is also important that you export your SSL Certificate to a .pfx file (We'll come back to this later)As we have come to expect, this upgrade requires you to backup your existing 3CX installation, uninstall 3CX V12.5, install 3CX V14 and then restore from backupSome key points that you should note before proceeding:If you are planning to use IIS as your webserver, only ports 80 and 443 are available for provisioning. We were previously using 5000 and 5001 as we maintained these ports as our 3CX versions evolved. We were now going to have to change these to 80 and 443A full list of required ports for 3CX V14 can be found here, allowing you to reconfigure your firewall. Notice the RTP ports have changed from 9000-9199 to 9000-9500http://www.3cx.com/docs/3cx-phone-system-v14-ports/We needed to use IIS as we valued our trusted SSL certificate which provided callers using our WebRTC link on our website with confidence that this was a safe siteAs a result of our provisioning ports changing we had to reprovision all our phones, softphones, mobile apps following the upgrade. In addition we had to update the WebRTC URL on our website and change option 66 in our DHCP scope (For completeness)During the installation you will be asked whether you have a third party SSL certificate that you wish to use. This is the time to import you previously exported SSL certificate. We failed to do this the first time round. We fixed our SSL certificate in IIS but then found that many things within the console stopped working with validation errors. Our only work around was to backup, uninstall, reinstall and restore from backup only this time importing our SSL certificateIt is also worth noting that in previous 3CX installations you were asked whether you were installing a new system or restoring from a backup. 3CX V14 requires that you complete a new install of a new system as the Backup and Restore facility is now found within the main console (More on the improved capabilities of this facility later)Upon completion of the install, you need to access the Backup and Restore facility from within the 3CX main console and restore your previous configAt this point we reprovisioned all devices because we were now using ports 80 and 443 for provisioningIt is worth mentioning another little 'gotcha' that we came across. We mistakenly provided an an incorrect public IP address during install time. Easy to rectify we thought, as we changed the public IP address in the three different areas within 3CX, only to find that calls were being rejected by our SIP Trunk provider. It turned out that the change was not fully propogated throughout all the 3CX files and our old public IP was still being used. 3CX Support fixed the MediaServer file concerned and assured us that a service would resolve this issue moving forward. I hope so as I wouldn't want to uninstall/reinstall because I changed my internet connectionIn our attempts to troubleshoot the above problem, we noticed that Verbose Logging was no longer available under Server Activity Log (Now found under the Status menu). 3CX Support also suggested that this would be available as part of the first service packNow that we had a working 3CX V14 installation we could take a further look at some of the new enhancements of which there a plenty1. The 3CX mobile app now works exceptionally well with a significantly improved PUSH capability making this a very useful feature2. The backup facility can now be scheduled and stored offsite via an FTP server, although following this exact configuration the Backup and Restore app within the console becomes very unresponsive. But it works!3. Call Reports are now based within the console and can be customised, scheduled and delivered via email4. Automatic deletion of Voicemails and Recordings can be arranged through the use of quotas. This means that voice mails and recordings can be automatically purged once they have reached a certain age. Unfortunately, the maximum age you can define is 30 days which would not be long enough for many businessesThere are many other enhancements but these are the ones most interesting to us
