Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Interoperability
Cisco TMS Release Notes (14.3.2)
Page 47 of 52
Feature
Limitation
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
In some situations, Cisco TMS is unable to add more than 30 dial-out
participants to TelePresence Conductor-scheduled meetings, while dial-in
participants are still able to join. Bug toolkit identifier: CSCui59829.
participants to TelePresence Conductor-scheduled meetings, while dial-in
participants are still able to join. Bug toolkit identifier: CSCui59829.
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.
Monitoring and reporting
n
Conferences using FindMe and Multiway may cause duplicates in
Conference
Control Center
and
Reporting
.
n
When making an ad hoc call which involves an endpoint which is registered to
Unified CM, the system may appear twice in
Unified CM, the system may appear twice in
Conference Control Center
.
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.
n
Customers using WebEx Productivity Tools with TelePresence must recycle the
application pool of the Cisco TMS Booking Service after upgrading to this
version of Cisco TMS and ensuring that Cisco TMS is fully functional. The issue
is addressed in a coming release of Cisco TMSXE. See defect ID CSCui03015
for further detail.
application pool of the Cisco TMS Booking Service after upgrading to this
version of Cisco TMS and ensuring that Cisco TMS is fully functional. The issue
is addressed in a coming release of Cisco TMSXE. See defect ID CSCui03015
for further detail.
Interoperability
Compatibility with existing integration products
Product
Version
Cisco TelePresence Management Suite Extension Booking API
API version 4 and later. The latest version
is 12.
is 12.