Cisco Bug: CSCup66989 - Orphan Meetings not migrated correctly leading to TMSXE Issue
Jun 26, 2015
- Cisco TelePresence Management Server
Known Affected Releases
Symptom: After upgrading from a version < 14.4, meetings listed in TMS as "Part of a series external to Cisco TMS" are not shown in the TMSXE linked resource calendars in Exchange. These types of meetings are known as 'Orphans' because they are instances of a series TMS does not know the full series. Cisco TMSBA (Cisco TMS booking API) clients when querying the suspect conference will find the conference is of recurrence type 'Default' but the Exceptions array is empty. For orphans, you expect to find the instances in the Exceptions array. Conditions: The meetings are Orphan conference instances that were booked before upgrading to 14.4 or 14.4.1. An example of an orphan is creating a recurring series that only includes users, no resource accounts. Then editing a specific instance of the series to add TMSXE enabled resource accounts to just that instance. These conferences will be labeled as "Part of a series external to Cisco TMS" when viewed in the Cisco TMS web interface The installation includes applications using the Cisco TMS Booking API (TMSBA) - such as the Cisco TMSXE Exchange integration. Installations that upgrade from <14.4 directly to 14.4.2 or newer will not experience this defect.
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