Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
The
EnableCMSTrial registry key is disabled by default . To enable this feature, change the EnableCMSTrial registry key
value to
one.
CMS Profiles
Cisco TMS checks the callProfile and callLegProfile that are created by Cisco TMS on CMS, in every 24 hours. If the
profiles are deleted, Cisco TMS recreates the profiles and reassociates them with the cospaces that are created by Cisco
TMS. Administrators can perform a Force Refresh in the View Settings page to initiate the process manually without
waiting for 24 hours. System-level profiles are used for the period that the TMS-created profiles are deleted.
profiles are deleted, Cisco TMS recreates the profiles and reassociates them with the cospaces that are created by Cisco
TMS. Administrators can perform a Force Refresh in the View Settings page to initiate the process manually without
waiting for 24 hours. System-level profiles are used for the period that the TMS-created profiles are deleted.
Unsupported Features
The following features are not supported for CMS in Cisco TMS:
■
WebEx enabled conferences
■
Conference Control Center
You can however view CMS in the Edit Conference and Add Participants section for the conferences that are
scheduled on other bridges.
You can however view CMS in the Edit Conference and Add Participants section for the conferences that are
scheduled on other bridges.
■
ISDN Bandwidth and ISDN Restrict
■
Best Impression Routing
■
Least Cost Routing
■
Recording with TCS
The Feedback Log and Call Log tabs under Systems > Navigator > Select a CMS> Log have been removed for CMS.
The Enforce Management Settings has also been removed from Systems > Navigator > Select a CMS>Settings > Edit
Settings
Settings
Scheduling
After you upgrade to TMS 15.3, prescheduled meetings still behave in the same way the original booked meetings.Cisco
TMS does not force the meetings to run on CMS.
TMS does not force the meetings to run on CMS.
You can now select CMS as Preferred MCU Type in Routing from Administrative Tools > Configuration > Conference
Settings > Advanced.
Settings > Advanced.
When you add CMS as a participant and schedule a conference, the IP Bandwidth field in Booking > New Conference >
Advanced Settings is disabled. The highest bandwidth value 6144 kbps is selected. CMS does not have any bandwidth
restriction to host a conference.
Advanced Settings is disabled. The highest bandwidth value 6144 kbps is selected. CMS does not have any bandwidth
restriction to host a conference.
The following options can only be selected under Booking > New Conference > Advanced Settings, when you add CMS
and book a new conference:
and book a new conference:
■
Continuous Presence in Picture Mode.
■
Automatic Best Effort in Extend Mode.
■
If Possible in Secure.
When you add CMS as the main bridge and schedule a conference, the option to mute audio and video is disabled for
all the participants.
all the participants.
The conference and participants templates support for CMS is in-line with TelePresence Conductor.
Notes
■
After you upgrade to TMS 15.3, pre-scheduled meetings still behave in the same way the original booked
meetings. Cisco TMS does not force the meetings to run on CMS.
meetings. Cisco TMS does not force the meetings to run on CMS.
■
If the master database of CMS cluster goes down just before scheduled time, then the scheduled conference
might not be successfully initiated in CMS.
might not be successfully initiated in CMS.
5
Cisco TelePresence Management Suite Software Release Notes