Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Limitations
Cisco TelePresence Management Suite Release Notes Software Release Notes (14.5)
Page 71 of 76
Limitations
Feature
Limitation
Time zone support
n
The Cisco TMS server time zone cannot be changed.
n
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.
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.
This limitation will be addressed in coming releases of TelePresence Conductor
and Cisco TMS.
and Cisco TMS.
See also
scheduling improvements [p.1]
TelePresence Conductor
scheduling
scheduling
Multiple TelePresence Conductor cluster nodes are not supported in Cisco TMS.
TelePresence Conductor
scheduling
scheduling
Cisco TMS scheduling with TelePresence Conductor does not currently support
WebEx Enabled TelePresence.
WebEx Enabled TelePresence.
Monitoring and reporting
n
Conferences using FindMe and Multiway may cause duplicates in
Conference
Control Center
and
Reporting
.
n
Conferences where participants have been put on hold or have been
transferred may cause duplicates in
transferred may cause duplicates in
Conference Control Center
and
Reporting
.
WebEx
n
Advanced recurrence patterns are not supported for WebEx Enabled
TelePresence.When booking from the
TelePresence.When booking from the
New Conference
page, select to include
WebEx before specifying the recurrence pattern, and only the supported
patterns will be made available for selection.
patterns will be made available for selection.
n
Deleting a recurrent meeting series while one instance is ongoing will delete
the meeting in Cisco TMS but not in WebEx. This is because WebEx does not
allow changes to ongoing meetings, this includes deletion.
the meeting in Cisco TMS but not in WebEx. This is because WebEx does not
allow changes to ongoing meetings, this includes deletion.
Collaboration Edge
Cisco TMS does not currently support devices that are behind Collaboration Edge.
Expressway
Cisco Expressway-C and Cisco Expressway-E will display in Cisco TMS with
system type TANDBERG VCS.
system type TANDBERG VCS.
System Type field
Some systems that previously contained TANDBERG in the system type may still
show up as TANDBERG in Cisco TMS. This is primarily based on Cisco TMS
reading the system type directly from the system’s API. In some cases, Cisco TMS
added the system type where one was not available through the API. Therefore,
the name may continue to show up with TANDBERG in the system type.
show up as TANDBERG in Cisco TMS. This is primarily based on Cisco TMS
reading the system type directly from the system’s API. In some cases, Cisco TMS
added the system type where one was not available through the API. Therefore,
the name may continue to show up with TANDBERG in the system type.
Scheduling meetings in
Cisco TMS
Cisco TMS
In some cases, Cisco TMS does not allow to book a recurrence meeting, if it
overlaps with a meeting that is scheduled for 24 hours or more.
overlaps with a meeting that is scheduled for 24 hours or more.
Bug toolkit identifier: CSCux64873.