Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Limitations
Cisco TelePresence Management Suite Release Notes Software Release Notes (14.4.1)
Page 56 of 61
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
n
TelePresence Conductor does not properly load balance multiple scheduled
meetings beginning at the same time across multiple MCUs or TelePresence
Servers in a bridge pool. This can lead to situations where one MCU or
TelePresence Server will fill up and calls will be rejected while others in the
same bridge pool are underutilized.
meetings beginning at the same time across multiple MCUs or TelePresence
Servers in a bridge pool. This can lead to situations where one MCU or
TelePresence Server will fill up and calls will be rejected while others in the
same bridge pool are underutilized.
l
As a workaround for MCUs, we recommend only adding identical capacity
MCUs to a bridge pool and configuring either a content, chairperson, or
cascade port on the Conference Template. Bug toolkit
identifier: CSCui42818.
MCUs to a bridge pool and configuring either a content, chairperson, or
cascade port on the Conference Template. Bug toolkit
identifier: CSCui42818.
l
As a workaround for TelePresence Server, we recommend only adding one
TelePresence Server to a bridge pool. Bug toolkit identifier: CSCui42822.
TelePresence Server to a bridge pool. Bug toolkit identifier: CSCui42822.
n
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.
The above limitations will be addressed in coming releases of TelePresence
Conductor and Cisco TMS.
Conductor 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.