Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Limitations
Cisco TelePresence Management Suite 13.2.1 Software Release Notes
Page 6 of 11
Identifier
Summary
CSCtr32413
When booking one or more endpoints and a Cisco TelePresence Content Server through the
booking API, the booking sometimes fails with this error: There are not enough resources on any
MCU to host your conference. Please go back and remove some of the participants, or lower the
conference bandwidth.
booking API, the booking sometimes fails with this error: There are not enough resources on any
MCU to host your conference. Please go back and remove some of the participants, or lower the
conference bandwidth.
CSCtr35038
When a participant is added to and then disconnected from a permanent conference created on a
Cisco TelePresence MCU, using Cisco TMS
Cisco TelePresence MCU, using Cisco TMS
Monitoring > Conference Control Center,
the
participant incorrectly remains as a pre-configured participant on the MCU.
CSCtr91647
Cisco TMS always adds a Cisco TelePresence MCU for point-to-point calls with C-series
endpoints if the IP bandwidth for the conference is set to more than 6000 Kbps. This occurs even
though the field External MCU Usage in Routing is set to Always except p2p (
endpoints if the IP bandwidth for the conference is set to more than 6000 Kbps. This occurs even
though the field External MCU Usage in Routing is set to Always except p2p (
Administrative
Tools > Configuration > Conference Settings > Advanced Conference Options
pane).
CSCts02650
Any communication with Cisco TelePresence MCUs/Cisco TelePresence Servers is slow when
they are set to use HTTPS and HTTP is turned off.
they are set to use HTTPS and HTTP is turned off.
CSCts02666
Administrative Tools > Activity Status >
select the description of an event
> Activity Log
displays incorrectly when Cisco TMS is installed on a non-English operating system.
CSCts02669
When editing a recurrent conference from TMS Scheduler, you are not asked whether you want
to edit this instance or all instances of the recurrence. Only the selected instance will be changed.
to edit this instance or all instances of the recurrence. Only the selected instance will be changed.
CSCts02678
Unable to change the call direction of an external IP video dial-in participant from
Monitoring >
Conference Control Center
.
CSCts02684
Alarms displayed in
Monitoring > Conference Control Center
do not display when the
conference is opened. Old alarms are not cleared correctly.
CSCts02729
Conferences booked with audio/video dial-in participants are displayed as ad-hoc calls in
Monitoring > Conference Control Center
.
CSCtt07448
The language setting for confirmation email messages does not correspond with the language set
for Cisco TMS users.
for Cisco TMS users.
Limitations
Cisco products
Equipment
Summary
Cisco TelePresence MCU
v4.3 or later
v4.3 or later
Cisco TelePresence MCU Software version 4.3 introduced new options for Content
mode: Passthrough, Hybrid, Transcoded, and Disabled.
This version of Cisco TMS cannot use the Passthrough or Hybrid content modes.
When scheduling a conference with a Cisco TelePresence MCU running software
version 4.3 or later, Cisco TMS uses Content status H239Enabled only. As a result,
Content mode for that conference will either be set to Transcoded or Disabled.
This will be resolved in a future Cisco TMS software release.
mode: Passthrough, Hybrid, Transcoded, and Disabled.
This version of Cisco TMS cannot use the Passthrough or Hybrid content modes.
When scheduling a conference with a Cisco TelePresence MCU running software
version 4.3 or later, Cisco TMS uses Content status H239Enabled only. As a result,
Content mode for that conference will either be set to Transcoded or Disabled.
This will be resolved in a future Cisco TMS software release.
Cisco Unified
Communication Manager-
provisioned systems
Communication Manager-
provisioned systems
When making an ad hoc call which involves a participant which is registered to a Cisco
Unified Communication Manager, the Cisco Unified CM-registered system could
appear twice in the
Unified Communication Manager, the Cisco Unified CM-registered system could
appear twice in the
Conference Call Centre
in Cisco TMS.