Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Resolved caveats
Reference ID
Summary
Diagnostics) “verify that all OpenDS database indexes are in a constant state” failed even
though there was not an issue with the indexes. This also produced a critical ticket (the check
is made on a weekly basis).
though there was not an issue with the indexes. This also produced a critical ticket (the check
is made on a weekly basis).
86888
Improved the error response when TMS Agent Diagnostic Verify that all OpenDS database
indexes are installed is run (Administrative Tools > TMS Agent Diagnostics). The
diagnostic will now fail with the message No contact with port 4444.
indexes are installed is run (Administrative Tools > TMS Agent Diagnostics). The
diagnostic will now fail with the message No contact with port 4444.
84717
Resolved issue where it was not possible to verify that the authentication was disabled on a
Cisco VCS with X6 software. The diagnostic was found under Administrative Tools> TMS
Agent Diagnostics > Select VCS.
Cisco VCS with X6 software. The diagnostic was found under Administrative Tools> TMS
Agent Diagnostics > Select VCS.
87398
Resolved issue where creating a new provisioning user with, for example the display name
Dave Jones, then change this user's display name to Fred Smith, you could find the user by
typing Dave, Jones or Fred, but NOT Smith.
Now the search will find Fred or Smith.
Dave Jones, then change this user's display name to Fred Smith, you could find the user by
typing Dave, Jones or Fred, but NOT Smith.
Now the search will find Fred or Smith.
87095
Resolved the issue where Device URI pattern
{username}.{device.model}.{device.connectivity['external'='home','in
{username}.{device.model}.{device.connectivity['external'='home','in
ternal'='']}@argon.lab
didn’t work as intended.
There is now the possibility to use special character ‘.’ in the change value expressions. The
expression is now:
{username}.{device.model}{device.connectivity['external'='.home','in
ternal'='']}@argon.lab
expression is now:
{username}.{device.model}{device.connectivity['external'='.home','in
ternal'='']}@argon.lab
85385
Resolved issue where it was not possible to override generic SIP server address with a
specific SIP server address (Systems > Provisioning > Directory > Configurations). The
result was that an invalid SIP server address could be set on Movi or an endpoint.
Example config:
SIP Server Address 10.xx.xx.30
SIP Server Address 10.xx.xx.31 e20
SIP Server Address vcscluster movi
specific SIP server address (Systems > Provisioning > Directory > Configurations). The
result was that an invalid SIP server address could be set on Movi or an endpoint.
Example config:
SIP Server Address 10.xx.xx.30
SIP Server Address 10.xx.xx.31 e20
SIP Server Address vcscluster movi
This should give vcscluster for any Movi version, but it gives 10.xx.xx.30.
See the Cisco TMS Provisioning Deployment Guide for recommendations.
See the Cisco TMS Provisioning Deployment Guide for recommendations.
86980
Resolved issue where going to Systems > Provisioning> Directory > click on Add
Configurations > clicking on the arrow next to the search icon should have given the option
to select a model to filter by. The error was that no models where listed.
Configurations > clicking on the arrow next to the search icon should have given the option
to select a model to filter by. The error was that no models where listed.
87973
Improved validation rules of phone numbers when importing users from Active Directory.
Cisco TMS now accepts regional codes between one and four digits in round brackets.
Cisco TMS now accepts regional codes between one and four digits in round brackets.
89478
Resolved issue where Cisco EX series systems were displayed as Cisco E20 systems in
Systems > System Upgrade.
Systems > System Upgrade.
114892
Resolved issue where provisioned systems did not get release keys automatically
downloaded.
downloaded.
114502
The Cisco TMS installer will no longer check if provisioning is disabled if upgrading from
Cisco TMS 12.6.2 or newer.
Cisco TMS 12.6.2 or newer.
113845
Resolved issue where a trailing space in the device URI pattern entered for the findme device
template caused high CPU usage on the Cisco TMS server.
template caused high CPU usage on the Cisco TMS server.
88551
Resolved issue where emails sent from the Systems > Provisioning >Directory section of
Cisco TMS did not fully support UTF-8. This resulted in some corrupted characters and
unreadable text in the email body.
Cisco TMS did not fully support UTF-8. This resulted in some corrupted characters and
unreadable text in the email body.
87973
Resolved error where only a 3 digit telephone prefix (area code) could be imported with user
information from AD. This is within the Systems > Provisioning > Directory section of Cisco
TMS. Now any prefix/area code of 1-4 digits will be accepted.
information from AD. This is within the Systems > Provisioning > Directory section of Cisco
TMS. Now any prefix/area code of 1-4 digits will be accepted.
Reporting