This is a maintenance release addressing an issue with duplicate external primary keys, affecting customers
using Cisco TMS Booking API (Cisco TMSBA) clients such as Cisco TMSXE and Cisco TMSXN. This issue
was found in Cisco TMS versions 14.4 and 14.4.1 and causes problems replicating bookings from Cisco TMS
to Microsoft Exchange or IBM Domino.

Technical description of external primary key issue: CSCup76424

In Cisco TMS 14.4 and 14.4.1, Cisco TMS assumes that every conference has a unique ExternalPrimaryKey
value. Under certain conditions, earlier versions of Cisco TMS allowed multiple meetings to share the same
key, and the 14.4 and 14.4.1 upgrade scripts failed to de-duplicate these keys.

Cisco TMSBA clients such as Cisco TMSXE use the ExternalPrimaryKey to retrieve conferences from Cisco
TMS, always expecting to get the same conference when a specific ExternalPrimaryKey is provided to Cisco
TMSBA. If conference A and conference B have the same ExternalPrimaryKey value in the tmsng database,
Cisco TMSBA could return data belonging to conference A when Cisco TMSXE asks for conference B, and
vice versa. If this happens to Cisco TMSXE, the Cisco TMSXE replicator could permanently delete data from
Microsoft Exchange based upon incorrect data returned from Cisco TMSBA.

Versions of Cisco TMS prior to 14.4 do not rely upon the ExternalPrimaryKey being unique, and are not at risk
of data corruption unless upgraded to 14.4 or 14.4.1.

D14991 17c

Page 1 of 65