Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Resolved issues in 14.1
Cisco TelePresence Management Suite 14.1.1 Software Release Notes
Page 8 of 21
Identifier
Description
to 64k bandwidth when trying to set other values in Microsoft Outlook.
CSCua77446
Resolved the issue where scheduling a participant template made all participant templates seem
scheduled in
scheduled in
Booking > New Conference >
Add Participants button >
Template
tab.
This issue occurred for systems not managed by Cisco TMS.
CSCua23453
Resolved the issue where a system appeared as available when it was already booked. This
happened when a new date had started in UTC, but not in Cisco TMS’s time zone.
happened when a new date had started in UTC, but not in Cisco TMS’s time zone.
CSCtx73847
Resolved the issue where if scheduling a OBTP conference in Cisco TMS involving one or more
"room" type systems, the Cisco TMS routing logic failed to set up the connection.
"room" type systems, the Cisco TMS routing logic failed to set up the connection.
CSCud07423
When deleting a conference from a recurrent series, it was possible for the user to click OK without
an option selected. Now the option Delete the selected occurrence will be preselected.
an option selected. Now the option Delete the selected occurrence will be preselected.
CSCtt27466
Resolved the issue where setting Set Conferences as Secure by Default to Yes in
Administrative Tools > Configuration > Conference Settings
, did not enable secure
conferencing in Cisco TMS Scheduler as default.
CSCud10011
Resolved the issue where after going to
Booking > New Conference
, clicking the Add
Participant button and adding an MCU to the conference, the
MCU
tab did not show the correct
status for the MCUs.
CSCub19010
Resolved the issue where scheduling a conference with endpoints running TC/TE software or MXP
endpoints when
endpoints when
Administrative Tools > Conference Settings > Conference Create Options >
Set Conferences as Secure by Default was set to If Possible or Yes, Cisco TMS could in certain
circumstances incorrectly change the configuration.
circumstances incorrectly change the configuration.
CSCuc88037
Resolved the issue where it was possible to remove the main participant (the host or the MCU) in
an ad hoc conference. This would disconnect the call.
an ad hoc conference. This would disconnect the call.
CSCtr32362
Resolved the issue where a conference booked at midnight in Cisco TMS could be replicated to
the previous day in Microsoft Exchange.
the previous day in Microsoft Exchange.
Systems Management
Identifier
Description
CSCuc65075
Removed the warning given by Cisco TMS when trying to add a Cisco VCS using the VCS’s IP
address. As provisioning has been improved with Cisco TMSPE, there is no longer a requirement
for this warning.
address. As provisioning has been improved with Cisco TMSPE, there is no longer a requirement
for this warning.
CSCtx12293
Resolved the issue where a system took longer to upgrade than Cisco TMS expected and
therefore Cisco TMS reported the upgrade as unsuccessful. This issue applied to systems running
TC and TE software version 6 or earlier.
therefore Cisco TMS reported the upgrade as unsuccessful. This issue applied to systems running
TC and TE software version 6 or earlier.
CSCud16380
Resolved the issue where if adding a system using SNMP, not all the system’s capabilities were
added by the first Force Refresh.
added by the first Force Refresh.
CSCud07392
Resolved the issue in
System Upgrade
where if Upgrade Mode Basic was selected, both .pkg
and .zip files were displayed. Adding a .zip file is not a valid option here.
CSCua25689
Resolved the issue where adding a Cisco TelePresence MCU with only HTTPS enabled failed.
CSCud21809
Resolved the issue where a Cisco TelePresence MCU on a dual stack network could be added