3CX is pleased to announce a new release of 3CX Phone System 10, build 24018 – Service Pack 6.
To combat software piracy, we require all 3CX Phone Systems to be reactivated on their next start-up. This service pack will allow you to reactivate 3CX Phone System. Download this update by simply logging into the 3CX Windows Management Console and navigate to the 3CX Phone System Updates node.
IMPORTANT NOTIFICATION: Before upgrading 3CX Phone System 10 to Service Pack 6, make sure you have your 3CX license information handy. A reactivation of the license is required after performing this update as 3CX Phone System may fall back into FREE Mode. After the update, open the 3CX Management Console > Settings > Activate License and reactivate 3CX Phone System with your license Key.
New Features, Improvements and Bug Fixes
Fixed: 3CX Wallboard has now been updated to work with the latest version of Google Chrome.
Fixed: The 3CX Tunnel can now traverse more NAT networks & firewalls, reducing the number of one way audio connections (3CX SIP Proxy Manager must be updated if in use).
Fixed: Grandstream crash related to BLF Keys caused by a firmware update (Re-provision required)
Fixed: Message waiting indicator in Cisco SPA Phones fixed (Re-provision required)
Fixed: Removed 24 hour re-provision for Cisco SPA Phones. Cisco Phones will now check at 2AM in the morning.
Fixed: In some rare cases, queue calls coming via PSTN gateway could result in one way audio issues.
Fixed: Correct updating in ports, trunks and inbound rules pages when forwarded to extensions set to DEFLECT (302 diversion header).
Added: Ability to round up call costs to any specified value in minutes. The parameter is named “BILLFREQUENCY” and available in Settings > Advanced > custom parameter table.
Added: SIP phone provisioning templates for Yealink T32 and T38.
If you have the 3CX Hotel Module installed, you will need to update your installation from here.
If you have the 3CX VAD – (Voice Application Designer) installed, you will need to update your installation from here.
If you have 3CX Multitenant, it is required to take a backup of all tenants, uninstall, install the latest version and restore. To obtain 3CX Phone System Multi Tenant, please contact the 3CX Sales Team.
Users of 3CX Phone System 5, 6, 7, 8 and 9 are recommended to upgrade to 3CX Phone System 10. If you do not have Upgrade Insurance and wish to upgrade 3CX Phone System to version 10, click here.
Good action.
You should do this more often.
Thanks for the updates.
It seems to me, that the only reason for this SP is the Piracy-combat…
In either case, is the configuration preserved?
Thanks, Les.
And yes – the configuration is preserved. It will keep the last working configuration you had before.
To clarify… we did as the blog post states.
…we keyed in our May 2011 demo key and it failed and revoked the license. How quaint.
So…we re-registered on your web site, hopefully we get a new key via email to continue testing.
As for the proxy, we have nothing to fix from our side. You need to simply make an exception for 3cx.com.
Some companies use Proxy servers to establish a connection to the Internet. Fair enough.
3CX Phone System requires an Internet connection on port 443 (SSL) for the license activation. This is NOT going to change.
The Management console of 3CX Phone System cannot foresee proxy connections, and does not use the proxy settings from broswer so in this case you can try to instruct Windows to redirect the data traffic to the proxy server. Try this command in cmd
netsh winnt set proxy proxy-server=[IPADDRESS or PROXY NAME] bypass-list= *.3cx.com
Great function however:
Updating a Tentant went well, but after activating I do get a:
“Unexpected error: Failed to open registry key Licence: 66 System:0″
The licens I´m trying to activate is a NFR which expire in july 2012.
Will I be able to update another tentant with a bought licens?
Thanks
/Jesper
Take a backup of all tenants
Uninstall
Download the new multitenant installation
Restore backups
OR as a temp workaround open registry
HKLM\Software\3CX and create “PhoneSystem” (without quotes) key
For now make the registry edit however I suggest that for production purposes you download the latest multitenant and install the full installer because we made changes
Thanks for your quick reply
HKLM\Software\3CX does NOT exist, perhaps because I did the SP6 update:-|
I will have to uninstall, and make a new installation as you recomend.
/Jesper
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\3CX\PhoneSystem
Is it possible to create an activation by Phone(system) option.
so 3CX-PBX will connect by ‘phone’ to a telephony system of 3CX?
with kind regards,
and keep up the good work!
Jos Greeve
I alos went to update a tenant license NFR test and havethe same issuse as Jasper:
Updating a Tentant went well, but after activating I do get a:
“Unexpected error: Failed to open registry key Licence: 66 System:0″
We have an open support ticket.
Updating stand alone machines have gone with little or no issue other than on an IIS installation behind Windows 7 we lost IIS and had to reinitiate it via Control Panel on the local machine.
The blog is very good with the basic information. I know that we would like more detail particularly on what the updated phone templates are updated for on Grandstream and Cisco phones.
Thank you
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\3CX\PhoneSystem but this is a work around.
In real environments, you need to take a backup, uninstall and install MT INstallations because the previous version was a BETA install.
The error of the license should not happen on normal 3CX Phone System installations because phonesystem key is already there.
Re IIS – not a 3CX Problem.
Re grandstream and cisco I am going to update the blog post and put more information on it yes. Thanks for this
All up and working great now.
Thank you
In need of the Desktop Component MSI before proceeding to install. Is this available somewhere that I have not yet found? Thanks.
Craig
You are right, the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\3CX\PhoneSystem does exist.
However I did a uninstall and a re-install (thanks to your perfect working Backup system:-))
Is the 10.0.24018.2322 the newly announced “ready for operation” Cloud version?
/Jesper
I believe the requirement to update the sip proxy manager needed to be better thought out. Steps:
1. In our case, Service Pack 6 needs to be installed after hours.
2. Sip Proxy Manager needs to be updated and has to be done after hours to avoid a service interruption.
3. People who use a remote extension are not available after hours for me to be able to remotely connect to their computers and upate the SPM.
Does ths mean all remote extensions will not communicate with the PBX after SP6 has been applied via the SIP Proxy Manager until all Proxy Managers have been updated? If this is so, this causes an interruption in work flow because the people who use remote extensions will have to wait until I connect to each computer remotely and install the latest SIP Proxy Manager after applying Service Pack 6.
I suggest you come up with a better way to update the SIP Proxy Manager especially for future multi-tenant installations which seems to be the same as a remote extension.
Thank you – John @ Fox
SP6 needs to be installed after hours in any company that cannot afford downtime. This is a 5 minute procedure.
Same applies for sip proxy managers. This is a 1 minute procedure. Total tunnel downtime after an update would be 10 minutes.
It is required that the admin needs to access the remote offices and update the SPM. Configuration will remain the same and there are no questions asked at install time. You can install over the previous installation.
The older Sip Proxy manager is still compatible with SP6 so you do not need to install them both together.
In all fairness, there aren’t many Sip Proxy Manager updates released. In 1 year we had 2 updates only.
@Jesper – The latest version is the version that should be used yes.
It is no possibity to select and download the service pack. The 3CX1PSSB (8SC) license is regularly registered, service restarted, pc rebooted…
Sorry for the delay.
With Winforms (the Windows application), by browser is refused this type of operation (there is an explicit message shown by the interface itself in the browser).
@Nathan – I doubt this is related to the update. You can see from the change log and we changed nothing in this area. I think some settings were changed either in the outbound parameter tab of the VoIp Provider SiP trunk or maybe the provider changed something from their end. Some providers see this as CID spoofing.
What is the sip trunk you use?
If you want to check this go to the outbound parameters of the sip trunk and change the CID related fields to ORIGINATOR CALLER ID Example From Display Name -> ORIGINATOR CID. (NOT Outbound CID) If you have this already, make a wireshark capture and confirm that 3CX is actually sending the originator CID not the outbound CID of the line. If wireshark shows ok, then you need to go to the provider. If wireshark shows that in the From you have the outbound CID of the line, open a support ticket with 3CX Support.
I can assure you that this service pack contains EXACTLY what is specified in the change log above. Nothing more Nothing less.
an error message appeared “a previous version of 3cx phone system is installed on my computer”
X64 bit
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\3CX\PhoneSystem or
X86 bit
HKEY_LOCAL_MACHINE\SOFTWARE\3CX\PhoneSystem
if it stil does not install contact support
(Running on Windows Server 2008 R2)
That fixed it, thanks. I am not sure why this changed but if I load up a pre SP6 snapshot of the VM that setting was intact. As an aside it looks like a one off because I had this setting on 6 client deployments and I ran the update at all 6 locations the same night and had no problems. All of them are running near identical setups to ours accept for the NFR license. Not a game breaker, I just didn’t think to look there for some reason and that is my bad.
Hi Nick, it’s a regular, standalone installation diretly on the “PBX-PC”.
I don’t know why but, when I connected yesterday to verify the version on my customer 3CX PC, I attempted to select the SP6 another time…and this time the operation went straight…
As specified in the post I had to reactivate the license and all was OK
Upgraded to sp6, and now when I re-enter the licence key, 3cx is complaining that the key isn’t valid…., and the system is dropping back to the free version. Anyone else have this trouble?
Could someone at 3cx contact me to sort it out. I recommended 3cx for the company phone system, and the boss will be really pissed tomorrow if all he has is the free version……..
For the record, I personally bought the license, so I know its valid, and the free upgrade period has another couple of weeks to run.
While it may be possible I stuffed up, I have checked the key combination and re-entered several times :)
(I took a screenshot of the old key as well and it matches)
Regards,
Mat
Issue resolved. Operator error, not a 3cx issue. Thanks for the assistance of your team.
Regards,
Mat