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 28 of 89
n
Meeting Id Quantity—the number of meeting IDs to allow.
Other changes in this release:
n
Alias selection will now be done using a prioritized list specified by the administrator. Different
prioritizations can be defined for immersive and other aliases.
prioritizations can be defined for immersive and other aliases.
n
SIP and H.323 settings for scheduling have been added to the TelePresence Conductor
Edit Settings
tab.
Version XC2.2 is now supported and required. Support for XC1.2 is discontinued as of 14.3. Cisco TMS will
raise a ticket if a previous version of TelePresence Conductor is detected.
raise a ticket if a previous version of TelePresence Conductor is detected.
The recommended deployment model for XC2.2 is the back-to-back user agent (B2BUA), which is SIP-only.
TelePresence Conductor scheduling limitations
As the TelePresence Conductor scheduling solution has notable limitations at this time, we recommend
carefully considering these
carefully considering these
of TelePresence Conductor and Cisco TMS will address these limitations, and an updated deployment guide
for Cisco TMS with TelePresence Conductor will be made available at that time.
for Cisco TMS with TelePresence Conductor will be made available at that time.
Meeting ID quantity setting for TelePresence Server and MCU
The Meeting Id Quantity setting has also been implemented for TelePresence Server and MCU and is
available on the
available on the
Extended Settings
tab of each system.
Improved support for TelePresence Conductor-managed TelePresence Server and MCU
n
Cisco TMS will now use feedback from TelePresence Conductor for managed bridges and ignore any
feedback sent directly from those bridges.
feedback sent directly from those bridges.
n
Irrelevant settings and diagnostic tickets, and all extended settings for TelePresence Conductor-managed
bridges have been removed from Cisco TMS. Removed tickets are related to bandwidth, gatekeeper, and
SIP server registration.
bridges have been removed from Cisco TMS. Removed tickets are related to bandwidth, gatekeeper, and
SIP server registration.
n
Cisco TMS will now ignore the setting
Administrative Tools > Configuration > Conference Settings >
Advanced Conference Options >
Automatic MCU failover if set to If conference start or MCU polling
fails for conferences hosted by TelePresence Conductor.
Configurable length for auto-generated PINs
In
Administrative Tools > Configuration > Conference Settings
, a new setting has been introduced that
allows the administrator to specify the number of digits Cisco TMS will include when auto-generating
PIN codes for each conference created.
PIN codes for each conference created.
The name of the new field is Auto Generated Password Length. The setting is only applied when Auto
Generate Password on New Conferences is enabled.
Generate Password on New Conferences is enabled.
Notifications to all participants that a scheduled conference is ending
If a conference is hosted on a multipoint bridge, all conference participants can now receive in-video
notifications at configurable intervals; by default the notifications will be sent at 5 and 1 minutes before the
conference is scheduled to end.
notifications at configurable intervals; by default the notifications will be sent at 5 and 1 minutes before the
conference is scheduled to end.
Previously, in conferences hosted on a TelePresence MCU, TelePresence Server, or TelePresence
Conductor, only master participants that supported notifications sent directly from Cisco TMS would be
warned that the conference was ending.
Conductor, only master participants that supported notifications sent directly from Cisco TMS would be
warned that the conference was ending.