I thought I put this in the original email but it looks like I didn't. The complete version I hit this bug in is 10.5.2.11900-3 (SU1). As Dennis mentioned, it is listed as a resolved caveat in 10.5.2.10000-5 (SU2). http://www.cisco.com/web/software/282074295/125179/cucm-readme-1052su2-Rev2.pdf
Thanks, -R From: [email protected] Date: Sun, 19 Jul 2015 03:29:39 +0000 Subject: Re: [cisco-voip] 10.5.2 Certificate bug To: [email protected]; [email protected]; [email protected] More like, another reason not to run base versions, especially when there's two major service updates available. On Fri, Jul 17, 2015 at 4:50 PM Heim, Dennis <[email protected]> wrote: Looks like another reason to move to 10.5(2)SU2A. Dennis Heim | Emerging Technology Architect (Collaboration) World Wide Technology, Inc. | +1 314-212-1814 “There is a fine line between Wrong and Visionary. Unfortunately, you have to be a visionary to see it." – Sheldon Cooper Click here to join me in my Collaboration Meeting Room From: cisco-voip [mailto:[email protected]] On Behalf Of Ryan Huff Sent: Friday, July 17, 2015 4:10 PM To: [email protected] Subject: [cisco-voip] 10.5.2 Certificate bug So this bug cost me 2 hours last night .. one of the more ridiculous ones I have seen in awhile. 10.5.2; the Subject Alternative Name in the CSR can't be the same as the CN (although that is how most CA's will generate). The work around? Add a space character at the end of the CN when you generate the CSR and then the call manage magically puts the CN in the SAN field of the CSR ..... W.T.F https://tools.cisco.com/bugsearch/bug/CSCus47235 _______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
