Cisco Bug: CSCun76724 - TMS uses wrong conference numeric ID when booking first conference after
Jul 09, 2014
- Cisco TelePresence Management Server
Known Affected Releases
Symptoms: When changing the DN range for a direct managed bridge in Cisco TMS, the old values are cached for a while. Conferences booked shortly after the change are still allocated using the old DN range. Conditions: The issue has been observed with Cisco TelePresence MCUs, but other bridge types could be affected as well.
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