Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
New features
Cisco TelePresence Management Suite Release Notes Software Release Notes (14.5)
Page 13 of 76
Other improvements in this release:
n
Updated icons and descriptions; the icon will now indicate whether TelePresence Server is in a rack.
n
TelePresence Server version 2.2 or later is now required. Make sure to upgrade TelePresence Server
before upgrading Cisco TMS to 14.3.
before upgrading Cisco TMS to 14.3.
n
Added support for Cisco TelePresence Server on Virtual Machine.
n
When adding TelePresence Server to Cisco TMS, Use Lobby Screen for Conferences is now set to On.
n
Now reconnecting calls through TelePresence Server after any disconnection, including for WebEx video.
Improvements to TelePresence Conductor support
To better accommodate the dial plan restrictions of each organization, the numeric variable part of the
TelePresence Conductor aliases used by Cisco TMS has been made configurable for the administrator.
TelePresence Conductor aliases used by Cisco TMS has been made configurable for the administrator.
The new settings are found by going to
Systems > Navigator
, selecting TelePresence Conductor and going
to the
Extended Settings
tab:
n
First Meeting Id—the number to start at when creating numeric IDs.
n
Meeting Id Step—how much to increase the numeric ID by with each ID generated.
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.