Preview Tool

Cisco Bug: CSCun85388 - Secure phone can't be registered after change 3rd CA signed certificates

Last Modified

May 07, 2014

Products (1)

  • Cisco Unified Mobile Communicator

Known Affected Releases


Description (partial)

The problem is that the customer has a requirement to use ONLY certificates from his own CA, and no self-signed certificates generated by CUCM. Normally, you generate a signing request from CUCM and have it signed by your CA. Then CUCM continues to issue its own certificates to phones and clients. Because CUCM's certificates are trusted by the CA it is usually good. 
In this case, the customer needs to install his own certificates on the clients and phones 
He has tested it successfully with his IP phones.But failed on jabber

Configure the 3rd CA signed certificate
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.