Cisco Bug: CSCum98292 - TMS unnecessarily uses same MCU number in back-to-back meetings
Mar 11, 2015
- Cisco TelePresence Management Server
Known Affected Releases
13.2.2 14.1.1 14GoldTop
Symptoms: Cisco TMS unnecessarily assigns the same DN to back-to-back scheduled meetings hosted on a conference bridge. Conditions: The issue is usually seen when the conference bridge is in heavy use, and scheduled usage is close to maximum capacity. Using the same DN for consecutive meetings will not break any meeting functionality, but should be avoided in case someone dials in to a conference early. They could then end up in someone else's conference. Workarounds: No workaround is available in Cisco TMS <= 14.3.2. Cisco TMS's logic for assigning DNs to scheduled conferences has been significantly improved in version 14.4. Note that the problem may still occur, but affected customers are still encouraged to upgrade.
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