Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Known limitations
Known limitations
Cisco products
Equipment
Summary
TMS Phone books
It is not possible to preview provisioning source (phone book) if you have more than
100 groups. Cisco has not found any low risk fix for this and has decided to rewrite
this for the next main release of Cisco TMS. Customer with this problem is
encouraged to contact support.
100 groups. Cisco has not found any low risk fix for this and has decided to rewrite
this for the next main release of Cisco TMS. Customer with this problem is
encouraged to contact support.
Upgrade of provisioned
EX systems
EX systems
Cisco TMS is able to upgrade EX systems on version TC4.2 and higher, however
the upgrade is not possible with TC4.1 software.
the upgrade is not possible with TC4.1 software.
Cisco VCS X7.0
Cisco TMS13.1 will support X7.0 when it is released, however you will see that a
ticket will be produced in Cisco TMS if you have TMS Agent enabled, stating an
incompatibility between provisioning versions between VCS and Cisco TMS. The
ticket should be ignored there is not an issue.
ticket will be produced in Cisco TMS if you have TMS Agent enabled, stating an
incompatibility between provisioning versions between VCS and Cisco TMS. The
ticket should be ignored there is not an issue.
Upgrading to Cisco TMS
13.1
13.1
If replication is enabled when running the Cisco TMS 13.1 setup, the installer will
stop the installation and show a warning. Due to a weakness in how TMS 12.1/12.2
handled disabling of replication, the user is given the option to continue the
installation. Continue only if upgrading from TMS 12.1 or TMS 12.2 and disabling
replication has failed.
stop the installation and show a warning. Due to a weakness in how TMS 12.1/12.2
handled disabling of replication, the user is given the option to continue the
installation. Continue only if upgrading from TMS 12.1 or TMS 12.2 and disabling
replication has failed.
E20
Cisco TMS cannot guarantee that a scheduled E20 upgrade provisioned by the
TMSAgent is actually upgraded.
TMSAgent is actually upgraded.
MCU 4200 and 4500
series
Media MSEs
series
Media MSEs
Cisco TMS 13.1 assumes all MCUs/MSEs have at least 2.0 version software
installed. Using older software can cause problems in Cisco TMS.
installed. Using older software can cause problems in Cisco TMS.
Cisco TMS
Cisco VCS
Cisco VCS
Network latency and ‘distance’ between Cisco TMS and the Cisco VCS systems can
affect the ability to enable Cisco VCS clusters with provisioning on those Cisco VCS.
On a network with high latency and lower throughput, enabling a provisioning cluster
may lead to timeouts and potentially partial configurations of the TMS Agents. To
minimize this impact of network ”distance”, it is important to configure provisioning
clusters before populating the provisioning directory with users as described in the
affect the ability to enable Cisco VCS clusters with provisioning on those Cisco VCS.
On a network with high latency and lower throughput, enabling a provisioning cluster
may lead to timeouts and potentially partial configurations of the TMS Agents. To
minimize this impact of network ”distance”, it is important to configure provisioning
clusters before populating the provisioning directory with users as described in the
. However, if replication is being
re-enabled or a Cisco VCS or VCS cluster is being added to the solution in a
network with high latency, then the default timeout (one hour) can be increased by
adding the registry key tmsAgentReplicationSetupTimeout (in minutes) at the
following registry location on the Cisco TMS server:
HKEY_LOCAL_MACHINE\SOFTWARE\Tandberg\TANDBERG Management Suite.
network with high latency, then the default timeout (one hour) can be increased by
adding the registry key tmsAgentReplicationSetupTimeout (in minutes) at the
following registry location on the Cisco TMS server:
HKEY_LOCAL_MACHINE\SOFTWARE\Tandberg\TANDBERG Management Suite.
Cisco TMS, Provisioning
Directory
Directory
Provisioning Directory will not be available immediately after server restart as it
takes longer to start up than the rest of the Cisco TMS interface. If a user browses to
the Systems > Provisioning > Directory before the service has finished starting
up, an information message is shown to have the user check back shortly.
takes longer to start up than the rest of the Cisco TMS interface. If a user browses to
the Systems > Provisioning > Directory before the service has finished starting
up, an information message is shown to have the user check back shortly.
MCU
Participant drag and drop is not available for SIP participants on a Cisco
TelePresence MCU that were originally dial-out calls.
TelePresence MCU that were originally dial-out calls.
E20
Pre-registering of E20 endpoints in Cisco TMS that will be provisioned by the TMS
Agent is not supported at this time. This will be corrected in a future version of Cisco
TMS.
Agent is not supported at this time. This will be corrected in a future version of Cisco
TMS.
Cisco TMS, Provisioning
When TMS Agent Data Replication is enabled, if a server (such as Cisco TMS or
Cisco VCS) is out of the replication topology for more than 24 hours and then comes
online again, all changes that have happened on any other replication member
during that time will not be copied across to the server when it comes back online.
However, all new changes will be copied as normal. If necessary, missing entries
modified or added during the downtime can be recovered to the server by running
the “dsreplication initialize” from the command line on the server.
Cisco VCS) is out of the replication topology for more than 24 hours and then comes
online again, all changes that have happened on any other replication member
during that time will not be copied across to the server when it comes back online.
However, all new changes will be copied as normal. If necessary, missing entries
modified or added during the downtime can be recovered to the server by running
the “dsreplication initialize” from the command line on the server.
Cisco TMS, Provisioning
Information for the screen Directory, in Systems > Provisioning > Directory is not