Polycom CMA System 5.x.x XMPP Keystore Patch
About This Patch
After 00:00 on May 7, 2013, Polycom CMA Desktop clients could no longer log into their associated Polycom CMA systems.
The login process stopped at “Initializing Call Stack”.
This issue occurs for all versions of the Polycom CMA system and it occurs because the thirdparty “Openfire” XMPP component within in the CMA system uses a certificate that expired at 00:00 on May 7, 2013.
After this date and time, the CMA Desktop client refused to establish a TLS connection for XMPP services due to the invalid certificate.
This patch replaces the certificate “keystore” file on the Polycom CMA system with a new certificate file that has an expiration date extended to year 2024
Important Prerequisites and Configuration Considerations
Apply this patch to CMA v6.x.x systems only.
Do not install this patch on CMA v6.x.x systems.
If after installing this patch, you upgrade the CMA system software to a later v6.x.x version, you will be required to apply this patch again to that new version.
In order to ensure that you can upgrade your CMA system to a later v6.x.x version, this patch does not write patch information to the CMA system database.
Therefore, this patch does not appear in the Past Upgrades page.
You can download this XMPP patch and more Information => here <=
NOTE: Please ensure to check the release notes for all details !
------------------------------------------------
Notice: I am an HP Poly employee but all replies within the community are done as a volunteer outside of my day role. This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
If you need immediate and/or official assistance for former Poly\Plantronics\Polycom please open a service ticket through your support channels
For HP products please check HP Support.
Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN
