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 22 of 89
Endpoints that are scheduled in One Button To Push conferences that take place in the 72 hours after the
upgrade to 14.4 will have a mismatched start time as the buffer is removed from Cisco TMS but still exists on
the endpoint. (The calendar is pushed to the endpoint by Cisco TMS 72 hours before the conference starts.)
upgrade to 14.4 will have a mismatched start time as the buffer is removed from Cisco TMS but still exists on
the endpoint. (The calendar is pushed to the endpoint by Cisco TMS 72 hours before the conference starts.)
To force an updated calendar to an endpoint, reboot it.
WebEx option key requirement removed
Enabling WebEx in Cisco TMS no longer requires an option key.
Removed
Discover Non-SNMP Systems
In
Systems > Navigator > Add Systems > Advanced Settings
, the option to Discover Non-SNMP
Systems has been removed, as Cisco TMS now discovers HTTP/HTTPS systems by default, if
SNMP times out.
SNMP times out.
The setting
Administrative Tools > Configuration > Network Settings >
Telnet/HTTP Connection
Timeout is used when adding systems using HTTP/HTTPS.
TelePresence Conductor scheduling improvements
In
Systems > Navigator >
select a TelePresence Conductor, the
Aliases
tab has been renamed to
TelePresence Conductor
and contains two new tabs:
Aliases
and
Service Preferences
.
Improved TelePresence Conductor scheduling implementation:
n
The Database Scanner service regularly updates Cisco TMS with the capacity of the TelePresence
Conductor. This also happens on Force Refresh.
Conductor. This also happens on Force Refresh.
n
There is now a notification if a TelePresence Conductor is running out of capacity.
n
The alias Priority number range now includes 0 in line with the TelePresence Conductor range of 0-65535.
The default value is now 0, previously it was 1.
The default value is now 0, previously it was 1.
n
The
Aliases
tab has been redesigned.
n
Only XC2.3 is supported with 14.4. Customers running XC2.2 must carry out these tasks in the following
order:
order:
a. Upgrade Cisco TMS to 14.4.
b. Upgrade the TelePresence Conductor to version 2.3.
c. In
b. Upgrade the TelePresence Conductor to version 2.3.
c. In
Systems > Navigator >
select the TelePresence Conductor
> Settings > Edit Settings >
TMS
Scheduling Settings
, ensure that Allow Booking is checked and that the dialing settings are
configured appropriately.
d. Run
Conference Diagnostics
in Cisco TMS to identify and fix any conferences affected by the
upgrades.
n
The order in which a preferred bridge is chosen when routing has now changed as follows:
a. TelePresence Server
b. TelePresence MCU
c. TelePresence Conductor
b. TelePresence MCU
c. TelePresence Conductor
n
Improved multi-screen system resource count.
n
Added option to regenerate alias, if a conference is edited and the original alias is no longer available.
Previously the conference had to be rebooked from scratch to find a new available alias.
Previously the conference had to be rebooked from scratch to find a new available alias.
n
Ability to disable aliases so they can be 'retired' by deselecting the Allow Booking setting.
n
If an alias in Cisco TMS does not exist on TelePresence Conductor, a ticket will now display. This is
helpful if somehow an alias was edited or deleted on TelePresence Conductor.
helpful if somehow an alias was edited or deleted on TelePresence Conductor.