Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
an available bridge for booking. Conductor cluster behavior remains unchanged - calls may drop and have to dial back
into their meetings, and some services may be temporarily unavailable during the cluster’s recovery from a node failure.
Cisco TMSPE and its associated functions do not failover. Three-node Conductor clusters are not supported for this
feature.
into their meetings, and some services may be temporarily unavailable during the cluster’s recovery from a node failure.
Cisco TMSPE and its associated functions do not failover. Three-node Conductor clusters are not supported for this
feature.
Resolved and Open Issues
Follow the link below to find up-to-date information about the resolved and open issues in this release:
You need to refresh your browser after you log in to the Cisco Bug Search Tool.
Limitations
Feature
Limitation
Time zone support
■
The Cisco TMS server time zone cannot be changed.
■
International time zone amendments such as changes to DST dates or time
zone regions are automatically updated on the Cisco TMS server and in Cisco
TMS through Microsoft Windows Updates. The same is not true of endpoints
running Cisco TelePresence TE or TC software—they have a manual pre-
defined list of time zones, so any changes to DST dates or time zone regions
will not be reflected. This can lead to time zone mismatch errors on direct-
managed endpoints. Scheduling will not be affected, but Cisco TMS could fail to
read/write time zone data.
zone regions are automatically updated on the Cisco TMS server and in Cisco
TMS through Microsoft Windows Updates. The same is not true of endpoints
running Cisco TelePresence TE or TC software—they have a manual pre-
defined list of time zones, so any changes to DST dates or time zone regions
will not be reflected. This can lead to time zone mismatch errors on direct-
managed endpoints. Scheduling will not be affected, but Cisco TMS could fail to
read/write time zone data.
TelePresence Conductor
scheduling
scheduling
TelePresence Conductor waits up to 30 seconds before releasing resources between
meetings. This may cause denial of inbound and outbound calls for back-to-back
meetings and utilization spikes when participants repeatedly leave and join a meeting.
Bug toolkit identifier: CSCuf34880.
meetings. This may cause denial of inbound and outbound calls for back-to-back
meetings and utilization spikes when participants repeatedly leave and join a meeting.
Bug toolkit identifier: CSCuf34880.
This limitation will be addressed in coming releases of TelePresence Conductor and
Cisco TMS.
Cisco TMS.
TelePresence Conductor
scheduling
scheduling
Multiple TelePresence Conductor cluster nodes can be added in Cisco TMS but only
primary TelePresence Conductor can be used for scheduling.
primary TelePresence Conductor can be used for scheduling.
TelePresence Conductor
scheduling
scheduling
Scheduling Cisco TMSPE-generated Collaboration Meeting Rooms is not supported.
TSP Audio and meeting
extension
extension
If two meetings are allocated the same TSP audio number by WebEx, Cisco TMS has
no awareness of this when deciding whether to extend the meeting. This could lead to
two conferences containing the same audio participants.
no awareness of this when deciding whether to extend the meeting. This could lead to
two conferences containing the same audio participants.
4
Cisco TelePresence Management Suite Software Release Notes