Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Resolved iss ues
Cisco TelePresence Management Suite 13.1.2 Software Release Notes
Page 7 of 18
Identifier
Summary
CSCts98564
Resolved the issue where booking a recurring meeting that included an instance of the series
occurring in the past on the day the meeting was booked would book that instance of the series
as a meeting with no participants. The corrected behavior is all instances in the past are
removed, including those occurring on the day of booking. The occurrence of the requested
pattern in the future will be the first instance of the saved conference.
occurring in the past on the day the meeting was booked would book that instance of the series
as a meeting with no participants. The corrected behavior is all instances in the past are
removed, including those occurring on the day of booking. The occurrence of the requested
pattern in the future will be the first instance of the saved conference.
CSCts82318
Changed the error handling on retrieving conferences when there was inconsistent data on
which participant was the VC Master for the conference. The error is now logged and no
longer returns an exception to the Booking API. Prior to this change, if this error condition
existed in the customer’s TMS database, the Cisco TMSXE Synchronizer process could hang
during synchronization.
which participant was the VC Master for the conference. The error is now logged and no
longer returns an exception to the Booking API. Prior to this change, if this error condition
existed in the customer’s TMS database, the Cisco TMSXE Synchronizer process could hang
during synchronization.
General
Identifier
Summary
CSCtr80556
In Cisco TMS v13.1, the time zones for Russia were updated to account for the change in time
zone rules adopted in 2011. This change had an error that left all Russian time zones off by
one hour. This one hour offset is now fixed, and all Russian time zones are now handled
correctly in Cisco TMS.
zone rules adopted in 2011. This change had an error that left all Russian time zones off by
one hour. This one hour offset is now fixed, and all Russian time zones are now handled
correctly in Cisco TMS.
Reporting
Identifier
Summary
CSCts33831
Resolved issue introduced in Cisco TMS v13.1 where call detail records from a Cisco
TelePresence ISDN GW were no longer collected.
TelePresence ISDN GW were no longer collected.
CSCts82312
Resolved issue for scheduled calls involving an MCU introduced in Cisco TMS v13.1 where a
duplicate call log record for calls involving the MCU would be created when using a Cisco
TelePresence MCU running version 4.2 or newer.
duplicate call log record for calls involving the MCU would be created when using a Cisco
TelePresence MCU running version 4.2 or newer.
CSCtt00984
Resolved the issue where an error was displayed when exporting to Excel for a report created
in Reporting > Conferences > Scheduling Interface > Data tab.
in Reporting > Conferences > Scheduling Interface > Data tab.
Booking
Identifier
Summary
CSCtr67199
Cisco TMS v13.1 changed the way email addresses were validated to account for new top
level domains. This change introduced a problem during booking where email addresses over
a certain length/complexity could cause the booking process to stall for an extended time. This
issue has now been resolved.
level domains. This change introduced a problem during booking where email addresses over
a certain length/complexity could cause the booking process to stall for an extended time. This
issue has now been resolved.
CSCtr28070
Resolved the issue where a double booking was possible if editing a non-recurring meeting
into a recurring meeting while simultaneously removing occurrences of the new meeting that
conflicted with another recurring meeting.
into a recurring meeting while simultaneously removing occurrences of the new meeting that
conflicted with another recurring meeting.
CSCts38070
Resolve the issue where booking a recurrent meeting using the Monthly pattern while using the
setting ‘Last...’ (e.g. last Monday of e very Month) caused the start time for all instances of the
series except for the first instance to be midnight.
setting ‘Last...’ (e.g. last Monday of e very Month) caused the start time for all instances of the
series except for the first instance to be midnight.
119789
Resolved the issue with a scheduled One-Button-To-Push conference where if a participant
was set to call H.323 using IP Addresses, the One-Button-To-Push calendar on the calling
system would fail to connect the call.
was set to call H.323 using IP Addresses, the One-Button-To-Push calendar on the calling
system would fail to connect the call.
CSCts38075
Resolved the issue where changing the recurrence pattern of an existing series that results in
fewer instances of the meeting could result in some instances of the new meeting pattern being
deleted.
fewer instances of the meeting could result in some instances of the new meeting pattern being
deleted.
CSCtt00571
Resolved the issue with scheduled One-Button-To-Push conferences where it was not possible
to book a participant that could only be connected as dial-out from the conference (E.g. an
External Dial Out participant, phonebook entry, etc). The conference would be rejected with
No Route Possib le. This combination is now allowed and the Cisco TelePresence MCU will
to book a participant that could only be connected as dial-out from the conference (E.g. an
External Dial Out participant, phonebook entry, etc). The conference would be rejected with
No Route Possib le. This combination is now allowed and the Cisco TelePresence MCU will