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 !
Please be aware:
The purpose of these forums is to allow community members collaborate and help each other. Questions posted here do not follow Polycom’s SLA guidelines. If you require assistance from Polycom technical support, please open a web service request or call us .
The above is necessary in order to track issue internally within Polycom.
You are welcome to post more questions or configuration or logs for other community members to look at but if your issue requires a fix via Polycom you must go via the official support structure.
Please remember, if you see a post that helped you , and it answers your question, please mark it as an "Accept as Solution".
This forum reply or post is based upon my personal experience and does not reflect the opinion or view of my employer. Polycom employee participation within this community is not mandatory and any post or FAQ article provided by myself is done either during my working hours or outside working hours, in my private time, and may be answered on weekends, bank holidays or personal holidays.