Guest

Preview Tool

Cisco Bug: CSCur46416 - Certificate CSR Should Not Check Case Sensitivity in SAN

Last Modified

Nov 27, 2020

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

10.5(1.10000.7)

Description (partial)

Symptom:
"CSR SAN and Certificate SAN does not match" error

Conditions:
Generating a multiserver CSR and have upper and lower case hostnames defined in the cluster

Related Community Discussions

SIP TLS Trunk between CUCM 10.5 and VCS X7.2 do not accept the certificate
Hi, here is the scenario: there is a cluster of two VCS C running X7.2 with MS-Lync integration already running with B2BUA. Certificates already deployed for both VCSs and CA certificate uploaded to both. A new CUCM 10.5.1 was installed for TX deployments and a SIP trunk was established with success. Unencrypted calls can be completed at both directions. No certificates was generated at this CUCM. Now, this customer tried to set up a TLS between CUCM and VCS C: - SIP security profile as indicated ...
Latest activity: Dec 31, 2014
Bug details contain sensitive information and therefore require a Cisco.com 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.