Cisco Bug: CSCuj62186 - Recording alias saved in scheduled conference is not always unique
Nov 27, 2020
- Cisco TelePresence Management Server
Known Affected Releases
Symptom: Overlapping TMS scheduled recorded conferences are merged into one TCS recording after those conferences are ended. In a normal scenario, when a TMS scheduled conference is saved with a selected recording alias, TMS will transform the actual recording alias number into a long number (i.e. '4602' -> '46727644133559'). In an abnormal scenario, when a TMS scheduled conference is saved with a selected recording alias, TMS did not transform the actual recording alias number into a long number. For example, before and after the conference is saved, connection setting page shows the recording alias number as '4602'. Conditions: This issue only occurs when H323 gatekeeper registration mode in TCS is configured as gateway mode. This issue is intermittent. Found in TMS 13.2.2/14.2.2.
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