Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Feature
Limitation
Cisco TMSPE fails to
communicate with Cisco
TMS
communicate with Cisco
TMS
Cisco TMSPE fails to communicate with Cisco TMS when the new security mode is set
to
to
High in Cisco TMS 15.3.
This limitation will be addressed in forthcoming releases of Cisco TMSPE.
TelePresence Conductor
Clustering
Clustering
■
There will be no failover support for aliases if the primary TelePresence
Conductor is down. If the administrator has changed some aliases in the peer
TelePresence Conductor when the primary TelePresence Conductor is down,
the peer TelePresence Conductor's aliases cannot be updated in TMS until the
primary node is active.
Conductor is down. If the administrator has changed some aliases in the peer
TelePresence Conductor when the primary TelePresence Conductor is down,
the peer TelePresence Conductor's aliases cannot be updated in TMS until the
primary node is active.
■
In this release only the feedback from the primary TelePresence Conductor will
be processed by Cisco TMS. This means that adhoc resolving may have
impact, when the primary TelePresence Conductor is down.
be processed by Cisco TMS. This means that adhoc resolving may have
impact, when the primary TelePresence Conductor is down.
■
In this release there is no support for clustered TelePresence Conductor in
scheduling, routing and load balancing.
scheduling, routing and load balancing.
Phone Book on IX Endpoint
Cisco TMS is unable to detect the software version when you add an IX endpoint.
The Phone Book tab for IX endpoint under Systems > Navigator is configurable only for
version 8.2. IX endpoint cannot fetch phone book data from Cisco TMS when you add
any older version below 8.2.
version 8.2. IX endpoint cannot fetch phone book data from Cisco TMS when you add
any older version below 8.2.
You must add an IX version 8.2 to configure phone book and then use it from the
endpoint.
endpoint.
Virtual machine loses
network connectivity
intermittently for the
following product versions:
network connectivity
intermittently for the
following product versions:
■
VMware ESXi 5.0.x
■
VMware ESXi 5.1.x
■
VMware ESXi 5.5.x
■
VMware ESXi 6.0.x
Windows 2012 virtual machines that use E1000/E1000e driver, experience loss of
network connectivity. This issue would occur in the following environments:
network connectivity. This issue would occur in the following environments:
■
The virtual machine is Windows 2012 or Windows 2012 R2.
■
The virtual machine is using E1000 or E1000E driver.
A work around for this issue is to use VMXNET3 instead of E1000 or E1000e driver.
For more information see the following article:
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.
with a meeting that is scheduled for 24 hours or more.
Bug toolkit identifier: CSCux64873.
CMS Meeting End
notification
notification
Cisco TMS does not push meeting end notifications to CMS as CMS does not support
it. However, TMS managed endpoints will continue to receive notifications from TMS for
CMS hosted conferences.
it. However, TMS managed endpoints will continue to receive notifications from TMS for
CMS hosted conferences.
CMS status
Cisco TMS does not display
No Response from Main System log in Conference Event
Log when a CMS goes down during an ongoing conference.
Interoperability
The interoperability test results for this product are posted to
, where you can also find
interoperability test results for other Cisco TelePresence products.
9
Cisco TelePresence Management Suite Software Release Notes