Cisco Bug: CSCus71112 - Conductor/CUCM secure communication requires VIP address to be SAN
Mar 29, 2017
- Cisco TelePresence Conductor
Known Affected Releases
Symptom: When deploying Conductor with CUCM and adding Conductor as a secure conference bridge, you must point CUCM to the ad-hoc VIP address on Conductor. For Conductor to register successfully over HTTPS with CUCM it is required that the VIP IP address or DNS name be added to the Conductor Server Certificate SAN list. This is not mentioned in the documentation and it is assumed the customer would know to do this and can lead to confusion. Should update the Conductor/UCM deployment guide to better clarify this. Conditions: Conductor deployed with CUCM as a secure conference bridge resource for ad-hoc calls.
Related Community Discussions
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)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases