Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
New features
Cisco TelePresence Management Suite Release Notes Software Release Notes (14.6.2)
Page 2 of 89
To book from the
New Conference
page, check Externally Hosted and provide a SIP URI in the Video
Address field.
Note that externally hosted conferences do not support adding the following features: WebEx, cascading,
Cisco TMS-managed bridges, dial-out participants, recording, or encryption.
Cisco TMS-managed bridges, dial-out participants, recording, or encryption.
Changes to the users that receive booking confirmation and cancellation emails
All users involved in booking a conference will now receive booking confirmation and error notification email
messages when the conference is booked, updated, or deleted. This includes the following:
messages when the conference is booked, updated, or deleted. This includes the following:
n
Conference creator: The user who books the conference.
n
Conference owner.
n
Any other user who has ever updated the conference.
Note that the service accounts used for Cisco TMSXE, Cisco TMSXN or Cisco TMSPE Smart Scheduler
will now receive a large number of emails, as they are involved in all bookings made through these interfaces.
If this becomes an issue, do one of the following:
will now receive a large number of emails, as they are involved in all bookings made through these interfaces.
If this becomes an issue, do one of the following:
n
Configure your mail server to archive and purge old emails for these accounts.
n
Change the service user's email address in Cisco TMS to noreply@example.org or similar.
Conference save performance improvements
Saving a conference is now significantly faster in large deployments.
The routing mechanism has been improved to optimize bridge selection during booking, by distributing
conferences more evenly across bridges in your deployment.
conferences more evenly across bridges in your deployment.
Cisco TMS will now randomly select a bridge if there are two or more that are identical (model, IP zone,
protocols, and so on), which minimizes delays when allocating and launching conferences.
protocols, and so on), which minimizes delays when allocating and launching conferences.
Previously Cisco TMS would always favor the same bridge if there were two or more that were identical.
Improved handling of changes to ongoing conferences
Adding or removing participants from ongoing conferences will never change the Main participant (conference
host).
host).
This could happen in previous releases when adding participants to ongoing conferences when using clients
such as Microsoft Outlook or Smart Scheduler. Ongoing conferences will no longer be disrupted or moved to
a different bridge.
such as Microsoft Outlook or Smart Scheduler. Ongoing conferences will no longer be disrupted or moved to
a different bridge.
Improved scheduling logging
All four of the scheduling log files now contain significantly more information about bridge selection. It is
generally no longer necessary to enable debug logging when troubleshooting bridge selection issues as all
relevant information is now displayed at the INFO log level.
generally no longer necessary to enable debug logging when troubleshooting bridge selection issues as all
relevant information is now displayed at the INFO log level.
Note that scheduling logs are disabled by default.
Enforcing upper limit of 5000 systems
Starting with Cisco TMS 14.6, adding more than 5000 systems licenses will generate a warning that using
more than 5000 systems is not supported. This warning will be displayed every time the
more than 5000 systems is not supported. This warning will be displayed every time the
General Settings
page is accessed.