Cisco Bug: CSCul19347 - Port number information is dissimilar on conference bridge configuration
Apr 03, 2017
- Cisco TelePresence Conductor
Known Affected Releases
Symptom: Issue : Port number information is dissimilar on conference bridge configuration for CUCM AdHoc conference Description CUCM deployment guide for Telepresence conductor XC2.2 having the dissimilar port information on AdHoc Conference configuration. http://www.cisco.com/en/US/docs/telepresence/infrastructure/conductor/config_guide/Cisco_TelePresence_Conductor_with_Cisco_Unified_CM_Deployment_Guide_XC2-2.pdf HTTP port is given wrongly in the Task 27 or page No. 37 out of 66 Please refer the Document-1 Screenshot on attachment In the page No. 38 out of 66 is not matched with example configuration Please refer the Document-2 Screenshot on attachment Configuration table and Configuration screenshot are using dissimilar port informations in the CUCM AdHoc conference configuration guide. Expected behavior : If the conference bridge is having secure https port we should use 443, else we can use port No. 80 for http. Please find the below url for the same. http://www.cisco.com/en/US/docs/telepresence/infrastructure/conductor/config_guide/Cisco_TelePresence_Conductor_with_Cisco_Unified_CM_Deployment_Guide_XC2-2.pdf Version Details: Telepresence Conductor -> XC2.2.1 Conditions: Expected behavior : If the conference bridge is having secure https port we should use 443, else we can use port No. 80 for http.
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