Cisco Bug: CSCuj25617 - TMS should re-route non-immersive existing pending conferences
Jul 18, 2014
- Cisco TelePresence Management Server
Known Affected Releases
Symptom: When a meeting is booked via TMS or TMSXE without including a CTS endpoint the meeting is escalated to regular MCU such as 8510. When a meeting is booked via TMS or TMSXE that includes a CTS "immersive" endpoint the meeting is escalated to TelePresence Server, 8710. If the meeting was originally booked without CTS system is updated to include CTS system, routing does not change; however this use to be the case in TMS 14.1.1 and earlier. It is understand that on TMS 14.1.1 and earlier, the following feature needed to be enabled to allow routing to CTS systems by MCU: "Enable Cisco CTS Native Interop Call Routing" in Administrative Tool > Configuration > Conference Settings by setting to"Yes". Once set to yes, conferences can be saved with CTS and 8510. Also, now conferences do not escalate to 8710 when modified to include CTS "immersive" systems. In newer versions of TMS, 14.2.0 and later, the above feature, Enable Cisco CTS Native Interop Call Routing is enabled by default, permanently. This now breaks routing of conferences with CTS endpoints to 8710. For this enhancement, we would like one of the following 1. Revert this change, allowing this option to be manually selected and therefore allowing previous behavior. 2. Add a new check box under TMS Conference Settings to allow customer to choose whether CTS endpoint uses TelePresence Server or other MCU. 3. Although less desirable, an addition to Cisco form to help control this routing could work; but not for customer who do not deploy Cisco form. Conditions: Book a meeting with TMS or via TMSXE that does not included a CTS endpoint, registered to call manager Update that meeting to include CTS endpoint and the MCU used in routing does not change.
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