Refer to the exhibit. When troubleshooting an internal Jabber login problem, there is a pop-up about a certificate error, and then the login fails The FQDN of Cisco UCM is cucm.ex.com. and the FODN…

Question

Exhibit

Options

• ASign the Cisco Untried IM and Presence server certificate with trusted a trusted
• BImport the certificate of cucm.ex.com into the Trusted Certificate Authorities on the PC running
• CImport the Cisco UCM CallManager certificate into the Trusted Certificate Authorities on the PC
• DSign the Cisco UCM CallManager certificate with a trusted certificate authority.
• ESign the Cisco UCM tomcat certificate with a trusted certificate authority.

• A
  5% (2)
• B
  11% (4)
• C
  82% (31)
• D
  3% (1)

Explanation

Jabber uses two key certificate interactions with CUCM: (1) The Tomcat certificate secures HTTPS/web service connections used during Jabber's login and service discovery - signing it with a trusted CA (Answer E) ensures the PC trusts it automatically. (2) The CallManager certificate is used for secure SIP/TFTP communication - importing it into the PC's Trusted Certificate Authorities store (Answer C) resolves trust errors for that certificate. Answer A addresses IM&P, not the root cause described. Answer B imports the cucm.ex.com certificate generically, which is less precise than importing the specific CallManager cert. Answer D signing the CallManager cert may help but is less directly actionable than C+E for the described scenario.

No community discussion yet for this question.