Table Of Contents
Release Notes for Cisco TelePresence Manager Release 1.8
First Published: Nov 2, 2011,OL-22228-02
This release note describes the open caveats and additional information for all releases associated with Cisco TelePresence Manager (CTS-Manager), Release 1.8.x.
Note CTS-Manager is supported only in an enterprise intranet environment. NAT deployment is not supported.
Hardware Support and Upgrade Path
Table 1 shows the servers supported by Cisco TelePresence Manager 1.8.
Table 2 shows the supported servers by version number and Cisco product ID.
Specification-based Hardware Support
Beginning with release 1.8, CTS-Manager now supports specification-based hardware using VMware.
For more information on supported hardware, refer to the following links:
For more information on VMware support, refer to the following links:
Software Upgrade Path
Upgrading from CTS-Manager 1.6 to 1.8 is supported, but requires an upgrade license. Versions 1.7 and later require device and feature licenses.
Upgrading from CTS-Manager 1.7 to 1.8 is supported and does not require an upgrade license or key, as long as customers have an installed device and feature license and a current support contract.
For more information, refer to "Existing Customers Upgrading to CTS-Manager 1.8" in the CTS-Manager 1.8 Administration and Installation Guide:
Cisco TelePresence Software Compatibility Matrix
For Cisco TelePresence software compatibility information, refer to the information located at the following URL:
Cisco TelePresence Manager Open-Source Software Licenses
License agreements for the open-source software used in Cisco TelePresence Manager are available at the following URL:
What New in this Release
This section describes new and changed information in Cisco TelePresence Manager beginning with release 1.8.5.
New in Release 1.8.5
•Fixes for the following bugs:
–CSCuc79048: CTS-Manager does not push a meeting to TelePresence Server (TS) if the meeting subject is empty.
–CSCuc93997: TS ports calculation incorrect in room declined/add scenario.
–CSCud23079: Wrong call-in number is displayed after scheduling a meeting where TS is the multipoint scheduling device.
–CSCuc98978: CTS-Manager overbooks MCU resources, exceeding the maximum segments/ports capacity limit.
New in Release 1.8.4
•Support for Microsoft Exchange 2010 SP2
•Fixes for the following bugs:
–CSCuc45654: Interop meeting not scheduled to use TelePresence Server (TS) if the Dial ID is reused from an earlier meeting on the same day.
–CSCub70207: CTS-Manager does not push a meeting to TS when the meeting subject is longer than 50 characters.
Note In release 1.8.4, the meeting subject is limited (truncated) to 50 characters for TS 2.2 and 80 characters for TS 2.3.
–CSCuc09833: CTS-Manager overschedules TS resources.
–CSCtq93187: Meeting name does not update in TS.
–CSCuc43405: TS Multipoint call-in number does not check range and meeting is not pushed to TS if dial plan is over 10 digits.
Note When adding a TelePresence Server in the Configure > Bridges and Servers window, it is required to use the same number of digits in the Multipoint Call-In Number Start and Multipoint Call-In Number End fields when either the start or end range is over 2147483647.
–CSCub12057: CTS-Manager does not push new TS meetings when the maximum number of conferences has been reached on TS.
•For detailed information about migrating meetings from CUVC or MXE to TelePresence Server, refer to the following section in the CTS-Manager 1.8 Administration and Installation Guide:
New in Release 1.8.3
•Fixes for the following bugs:
•Known Issues with Scheduling Meetings on TelePresence Server
The following issues should be noted prior to implementation of scheduling meetings on TelePresence Server:
–CSCub70207 - If the meeting subject field is over 50 characters, the meeting is not created.
–CSCuc09833 - CTS-Manager overschedules TS resources if the meeting is changed to add more ports.
–CSCub12057 - CTS-Manager won't schedule a meeting that uses TS if there are too many conf errors.
–CSCuc45654 - Interop meeting not scheduled to use TS if the dial ID has been reused from an earlier meeting on the same day.
–CSCuc43405 - TS multipoint call-in number does not check range and meeting is not pushed to the TS if the dial plan is over 10 digits.
Note There are no workarounds for these known issues. As a result, Cisco recommends for customers to postpone migration to TelePresence Server until these issues are fixed.
New in Release 1.8.2
•The Extend Multipoint Meetings feature is now available for multipoint meetings using TelePresence Server (TS), using the following options:
–`Allow all meeting organizers to extend meetings up to (minutes):'
The `Always Extend' setting is available, however the `Extend, if resources available' setting is not compatible with TS.
–`Allow these meeting organizers to extend meetings'
Note Meetings using TS are extended automatically. There is no message on the phone or control device asking the user if they want to extend the meeting.
•Fix for the following bug:
•The following is a known issue in release 1.8.2:
–Symptom: Only multipoint meetings scheduled to use CTMS are revalidated after changing Extend Multipoint Meetings settings, so any meetings scheduled to use TS will not be extended.
–Conditions: CTS-Manager is configured with 3 CTMSs and 2 TSs. Upgrade CTS-Manager to release 1.8.2 and change the Extend Multipoint Meetings setting from `Do not end meetings until they are ended by the participants' to `Allow all meeting organizers to extend meetings up to (minutes):30' and select `Always extend.'
–Workaround: If the meetings scheduled to use TS are modified (time change), they will be extended.
Note Meetings scheduled after upgrading to 1.8.2 will be extended.
New in Release 1.8.1
•Alert Management: When disk usage is close to or exceeds a user-configurable threshold, an alert email is sent. The email is sent to the email address configured in the Copy Outgoing Email To field on the Configure > Application Settings > Email tab.
CTS-Manager sends alert emails under the following circumstances:
–When the disk usage reaches 5% below the configured disk threshold percentage, CTS-Manager sends an email indicating the disk usage is approaching the threshold.
–When the disk usage exceeds the configured disk threshold percentage, CTS-Manager sends an email indicating the disk usage has exceeded the threshold.
–When the disk usage exceeds 90%, CTS-Manager sends an email indicating the disk usage has exceeded the critical level.
CTS-Manager resends the alert every 24 hours until the disk usage issue is resolved.
•Support for MX300 endpoint is introduced.
•Support for TX-series endpoints is introduced.
•Fixes for the following bugs:
New in Release 1.8
•WebEx Multisite: Provides the ability to expand the number of WebEx users managed by CTS-Manager by adding additional WebEx scheduling servers. WebEx scheduling servers are added in the Configure > Bridges and Servers window. Meeting organizers select the server to which they have been assigned in the Meeting Manager window, the first time the schedule a TelePresence Meeting with WebEx.
•User Delegate: Allows a meeting organizer to allow other users to manage their meetings. The delegate user(s) receive email notifications and have access to the same features as the meeting organizer, including the ability to access Meeting Manager to view meeting details, change meeting options and preferences.
•TelePresence Server Scheduling: Now supported for scheduling multipoint meetings. It supports interoperability with videoconferencing and the new TelePresence call-in number feature. A TelePresence Server is added in the Configure > Bridges and Servers window and configured in the Configure > Application Settings > Bridges and Servers tab.
Note Cisco recommends for customers to postpone migration to TelePresence Server until the known issues detailed in the 1.8.3 release are fixed (see above).
•UCS Server: The Cisco UCS C210 M2 server is now supported for CTS-Manager. It provides a high-performance solution for large-scale TelePresence environments and is ideally suited for clustered deployments.
Note Only a single CTS-Manager can be installed on a UCS server at one time. Except for the required VMware software, no other software can be installed on the UCS. This includes Cisco TelePresence Multipoint Switch (CTMS) and Cisco TelePresence Recording Server (CTRS).
•TelePresence Call-In Number: Introduced in version 1.8 of Cisco TelePresence Multipoint Switch (CTMS) and Cisco TelePresence Manager (CTS-Manager), the Cisco TelePresence Call-in Number feature enables a Meeting Organizer to allow users to join the meeting from Cisco TelePresence endpoints that are not scheduled in the meeting invitation. For more information, see TelePresence Call-In Number: http://www.cisco.com/en/US/docs/telepresence/cts_manager/1_8/call_in_number.html
Note Security with the TelePresence Call-In Number feature is not supported with CTMS. Any endpoint that joins a secure meeting using the TelePresence Call-In Number through CTMS will downgrade the meeting to non-secure.
•MX200, EX and C-series Endpoints: MX200, EX and C-series endpoints can now be scheduled in TelePresence meetings. Endpoints with TC5.0 or later software that are registered to a Unified CM version 8.6(1) or later are discovered automatically by CTS-Manager. Endpoints with TC5.0 or later registered to a VCS must be added manually in the Configure > Endpoints window. Endpoints with TC5.0 or later support One-Button-to-Push. Endpoints with TC4.x or earlier function as VC endpoints.
•Browser Security: Secures communication between the CTS-Manager web server and the browser through which you access the CTS-Manager Administrative UI. Browser security eliminates website security certificate warnings, which you receive if your web server is not secure. In CTS-Manager, you can set up either inter-device security, which is an existing feature, or browser security, which is introduced in CTS-Manager release 1.8. The deployment of both security features at the same time is not supported.
For more information on browser security, see the Cisco TelePresence Security Solutions: http://www.cisco.com/en/US/products/ps8332/products_installation_and_configuration_guides_list.html
•Intelligent link to Cisco Prime Collaboration Manager: Provides a real-time unified view of
Cisco TelePresence meetings and real-time troubleshooting to simplify video collaboration management.
•Administration web user interface settings remembered for each user: User layout options, like column sorting and filtering, are preserved for the next time a page is accessed or the user logs in.
•MXE Support Discontinued: In earlier versions of the CTS-Manager release notes, CTMS 1.8 and Media Experience Exchange (MXE) 5600 with limited interoperability was supported.
Based on recent testing, it has been determined that MXE 5600 interop with CTMS 1.8 or later is a solution Cisco can no longer recommend to customers. As a result, support for MXE 5600 is discontinued with CTS-Manager and CTMS 1.8 and 1.9.
Existing customers are encouraged to migrate to TelePresence Server for interop.
For options regarding MXE 5600, contact your Cisco account team or send an inquiry to Ravi Bansal via email: email@example.com.
•Clustering Support Discontinued
Cisco no longer provides support for the clustering feature originally introduced in this release.
For questions, contact Ron Lewis: firstname.lastname@example.org.
Fixes for the following bugs:
New in Release 1.7
This section describes new and changed information in Cisco TelePresence Manager beginning with Release 1.7.
•WebEx OneTouch - Meeting organizers can now add WebEx participants to their meeting. Meeting organizers can be assigned to one of three WebEx roles:
–WebEx Permitted User - can request WebEx for meetings on an individual basis
–WebEx Premium User - automatically has WebEx for all meetings
–Non-Permitted WebEx User - is not permitted to use WebEx with meetings
For complete details on how to configure WebEx for the Cisco TelePresence System, including CTS-Manager, refer to the "Cisco WebEx OneTouch Configuration Guide for the Cisco TelePresence System" at the following URL:
•Easy Video Conference Scheduling - Third party VC endpoints can now be configured as groupware resources in the same manner as CTS endpoints which allows meeting organizers to reserve VC rooms from their calendar application, along with CTS endpoints. Once a VC room is included in a scheduled TelePresence meeting, CTS-Manager automatically recognizes that it is a video conferencing interop meeting, reserves the necessary resources, generates the call in number and meeting number, and includes the call-in information for the VC participants in the meeting confirmation email.
•Meeting Extension- Flexible meeting extension features, including the new Meeting Extension Premium role that allows specific user groups to have the capability to extend meetings.
•Enforced License-based features:
–Room-based licenses - correspond to the number of CTS devices (rooms) used for TelePresence meetings, based on one license per room. License are available in groups of 10, 50 and 100 rooms.
–Feature-based licenses include:
•Scheduling API - supports organizations that need calendaring integration other than with MS Exchange or IBM Domino.
•Metrics Dashboard and Reporting API - Metrics dashboard gives administrators an overview of scheduled meetings, return on investment, and travel avoidance savings. The reporting API allows developers to gather both scheduled and ad hoc meeting information, plus survey answers to compute custom metrics dashboards to meet customers needs.
•For more information about these APIs, go to http://developer.cisco.com.
–When upgrading to CTS-Manager 1.7, you can get an upgrade license.
Note Upgrade License Procedure: Please refer to CSCti46839 for an important note about the process of getting an upgrade license.
•VC Rooms status and configuration - The Support > VC Rooms window displays status information for all video conferencing meeting rooms registered with CTS-Manager. The Configure > VC Rooms window allows you to add and view the status of video conferencing rooms in CTS-Manager.
•Graphic user interface for CTS-Manager updated to Cisco standard style.
•System Resources - The Troubleshoot > System Resources window provides tracking information for memory, disk usage, and Ethernet traffic in a graphical snapshot format.
•Not-A-TelePresence Meeting - Allows a meeting organizer who schedules a meeting with only one Telepresence room to select option of non-Telepresence meeting to prevent an error message.
•Microsoft Exchange 2010 with Windows Server 2008 and IBM Domino 8.5 support.
•HD-Interop with Media Experience Engine (MXE) - New gateway for inter-operation with non-CTS endpoints configured in the Configure > Application Settings > Bridges and Servers window.
•Remove Email Prefixes from the Pushed Meeting Subject - In the Configure > Application Settings > Email window, this feature allows email prefixes including "FW:, RE: and Updated:" can be removed from the subject line of TelePresence meeting emails. This feature is useful when a meeting organizer, participant or administrator wants to sort TelePresence meeting emails by subject in order to find an email related to a specific meeting.
•Cisco Unified Video Conferencing (CUVC) Gateway now supports high definition interoperation with non CTS endpoints using 720P or standard definition using CIF.
•Support for multiple CUVC Servers using CUVC-M solution for scalability.
•Group email by conversation in Microsoft Outlook - This feature allows you to group CTS-Manager emails by Outlook's group by Conversation feature. This feature groups emails according to their subject line making it easier for you to sort and find emails related to scheduled meetings.
New in Release 1.6.5
•Fixes for the following bugs:
New in Release 1.6.3
•Support for NTLMv2 authentication policy for Exchange 2007 EWS is now available in this release.
•Support for unlimited LDAP servers with Microsoft Exchange WebDAV and EWS environments.
New in Release 1.6.x
•Studio mode recording - allows an administrator to turn on global studio mode recording if all managed CTS endpoints are upgraded to the supported version. CTS is configured using the CTS UI, with a preferred recording server which would dial out to meetings, allowing the one button to push recording for the meeting
•Concierge changed to Live Desk
•Tentative Room Reservations - CTS-Manager now processes room reservations which are in tentative state. A tentative state implies meeting invite has been viewed by room/CTS-500 owner but not accepted yet. CTS-Manager would treat a tentative reservation as an accepted reservation
•Support for MS Exchange 2003/2007 deployments using Windows 2008 platform
•Enhancement Email Management - more support to email notifications on a global basis, admin can turn off or on email notifications
•Hardware MIB- new hardware MIBs are supported in 1.6 release
•Support for MS Exchange 2007 Web Services using FBA (Form Based Authentication)
•SD Interop supported with CIF; HD Interop with CUVC 7.0 supports 720p
•Support for multiple Unified CM Clusters - supports One Button To Push in Unified CM multi-cluster deployment. The ens user does not need to dial any special number to dial across the clusters in that CTS-Manager will formulate the numbers dialed by CTS end points to go across clusters based on Unified CM configurations.
•Support for multiple LDAP Domains/Forests in MS Exchange Deployments - CTS-Manager supports interacting with a maximum of 5 LDAP servers per deployment
•Optional First Time Setup using the Pre-Qualifier tool
CTS-Manager Release 1.8.x Caveat Reference
Table 4 summarizes caveats found in CTS-Manager Release 1.8
Caveats for CTS-Manager Release 1.8
Symptom: CTS-Manager accessible on revoked browser security certificate.
Condition: Install and apply browser security successfully. From CA, make the applied certificate revoked. Access CTS-Manager administrative web UI from Internet Explorer browser.
Workaround: Access CTS-Manager administrative web UI from a different browser.
Symptom: Wrong call-in number is displayed for a meeting in the Monitor > Meetings > Details page.
Conditions: Call-in number feature is enabled and then the meeting is scheduled with TS chosen as the multipoint scheduling device.
Symptom: Multipoint meetings display an insufficient multipoint resources error even though there are TS video ports available.
Conditions: In some cases where rooms are removed and then re-added, TS ports are overallocated.
Symptom: Meeting not pushed to TS but appears in the CTS-Manager Monitor > Meetings page and the confirmation email is sent to the meeting organizer.
Conditions: Meeting was created with no subject and scheduled to use TS as the multipoint scheduling device.
Workaround: Add a subject to the meeting.
Symptom: CTS-Manager overbooks MCU resources, exceeding the maximum segments/ports capacity limit.
Conditions: The rooms in the meeting were deleted/re-added to the database with the same email address.
Workaround: Manually migrate overbooked meetings to a different CTMS or TS, if available.
Symptom: Meetings are not pushed to TelePresence Server.
Conditions: Telepresence Server Multipoint Call-In Number range is outside of CTS-Manager's supported range of 1 to 2147483647.
Workaround: Modify the Unified CM dial plan to make the dial number within CTS-Manager's range.
Symptom: CTS-Manager overschedules TS resources.
Conditions: When four TS devices are configured in CTS-Manager 1.8.x.
Symptom: Some interop meetings are not pushed to TS if the Dial ID is the same as an existing meeting in a different time slot. This happens if the newly created meeting occurs before the existing meeting.
Workaround: Delete the existing meeting from the TS, then re-push the calendar to the TS by going to Support > Bridges and Servers, selecting the TS and clicking Update Schedule.
Symptom: Meeting is not pushed to TelePresence Server.
Conditions: When the total # of meetings within the calendar push window is more than 200 and the maximum number of conferences has been reached on TS.
Workaround: Go to Configure > Policies, select TS and click Edit. Reduce the number of days pushed to TS to a number of days that have fewer than 200 total meetings that use TS during that period of time.
Symptom: When Extend Multipoint Meetings settings are changed, 0 meetings are revalidated.
Conditions: TelePresence Server is selected as the primary scheduling device on the Application Settings > Bridges and Servers tab. Several multipoint meetings are scheduled.
Go to the Application Settings > Meeting Options tab, change `Allow these meeting organizers to extend meetings' from 30 to 60 and click Apply. The message "Total meetings to be revalidated are 0" appears.
Note The same symptom occurs when changing `Allow all meeting organizers to extend meetings up to (minutes):' settings or switching between these two settings.
Workaround: Go to Monitor > Meetings, select a future meeting and click Details. In the Meeting Manager window that opens, click the Summary tab to confirm that the settings have changed from 30 to 60 for each future meeting.
Symptom: Multipoint meeting is displayed as `With Error' and `Not enough resources' when it should switch from TS to CTMS when the TS doesn't have enough resources.
Conditions: CTS-Manager is configured with both CTMS and TS. The TS is configured as the primary scheduling device.
Schedule a multipoint meeting and select the `Provide call-in number for other participants' option. TelePresence Call-In Number is set to 13 segments.
Schedule another meeting for the same time slot and select the `Provide call-in number for other participants' option for this second meeting. CTS-Manger cannot schedule the second meeting because there are not enough resources for it.
Note The same symptom occurs when TelePresence Call-In Number is enabled for all meetings. The only difference is that only CTMS is displayed in the Monitor > Meetings page.
Symptom: No error 501212 Insufficient Resources emails for multipoint meetings is sent when CTS-Manager cannot book a meeting due to insufficient resources. The meeting organizer is not notified when a meeting is in error due to insufficient multipoint scheduling device resources after CTS-Manager first attempts resource allocation on CTMS, then TS, and then fails. If only CTMS servers are configured as multipoint scheduling devices, then 501212 emails are generated and sent successfully to the meeting organizer.
Conditions: Configure a CTMS as the primary scheduling device with a TS as the secondary scheduling device on CTS-Manager 1.8.x.
Workaround: None. The TS must be removed from CTS-Manager for 501212 Insufficient Resource emails to be sent, and/or only CTMS servers can be configured as multipoint scheduling devices. Using either of these workarounds, 501212 emails are sent to the meeting organizer informing them their meeting could not be booked due to insufficient resources.
Symptom: Meeting pushed to endpoint fails for a TelePresence meeting which includes WebEx.
Conditions: Meeting scheduled using WebEx Productivity Tools plug-in for Microsoft Outlook and the following possible conditions:
1. No toll-free call-in number is configured on the WebEx administration site.
2. A third-party teleconference service provider is selected for Conference Type in the WebEx Productivity Tools plug-in instead of Webex Audio.
Symptom: After software upgrade, Configure > Software Upgrade page still shows status of "Upgrading application software".
Conditions: Upgrade from 1.6.5 -1.8.x.
Workaround: Wait for the restart and refresh the Web browser or open a new browser session.
Symptom: CTS-Manager is unable to update the subject name of a booked meeting on TelePresence Server.
Conditions: This occurs if the meeting is already booked by CTS-Manager on TelePresence Server and only the Subject Name is changed.
Symptom: CTS-Manager does not push a meeting to Telepresence Server.
Conditions: Meeting subject longer than 50 characters.
Workaround: Scheduler must modify the meeting in Microsoft Outlook to shorten the meeting subject to less than 50 characters.
Symptom: The CTS-Manager administrative Web UI displays the wrong time for Europe/Moscow time zone.
Conditions: Time Zone is set to Europe/Moscow, after Russia ended DST.
Workaround: In the Preferences window, select Asia/Muscat (+4) and click Save.
Symptom: No resource to schedule meeting with a TelePresence Server (TS) in CTS-Manager and TS configuration.
Conditions: When calling a number on the TelePresence Server that is greater than the maximum setting of 2147483647.
Workaround: Call a number that is 2147483647 or lower.
Symptom: Null cluster ID is assigned to a newly added endpoint.
Conditions: When adding a new endpoint with CTS-Manager / IBM Domino integration.
Symptom: When the meeting organizer attempts to register their WebEx account with CTS-Manager by clicking the Register button in the WebEx page of the CTS-Manager Meeting Details, they are redirected back to the CTS-Manager Meeting Details page without being registered.
C.onditions: WebEx site is configured to use Single Sign On, but Single Log Out is not in use.
Workaround: Check the Single Log Out box in the WebEx site administration.
Symptom: Proxy settings for a WebEx site disappear.
Conditions: Another WebEx site was previously configured and deleted.
Workaround: Re-enter proxy settings and re-validate WebEx site.
Symptom: CTS-Manager failed to sync with Exchange due to out of memory in the database.
Conditions: Another WebEx site was previously configured and deleted.
Workaround: Restart the service
Symptom: CTS-Manager resends confirmation emails for all meetings.
Conditions: A presentation codec is added to or removed from the CTS endpoint configuration in Unified CM.
Symptom: Tip Enabled feature does not work for video conferencing endpoints
Conditions: Go to Configure > Endpoints page, click New, selecting the Video Conferencing endpoint type. select TIP Enabled, and click Save. Select the endpoint and click Edit. TIP-Enabled is displayed as "NO". Meeting scheduled using the endpoint will be an interop meeting instead of CTMS native meeting.
Symptom: API user authentication fails with the error "Code: 501601, Message: Unable to authenticate user. Check authentication parameters."
Conditions: Multiple LDAP configuration and the API user is not configured in any of the LDAP servers.
Symptom: Two Unified CMs appear after DNS is set in CTS-Manager. One appears with an Error status and the other appears with an OK status.
Conditions: CTS-Manager installed with DNS disabled. After installation, DNS is enabled in the Configure > System Settings window.
Workaround: None. System will function normally.
Symptom: "Provide a Call-In Number for Other Participants?" options set to Null in the Meeting Manager > Meeting Options tab.
Conditions: "Allow meeting organizers to send a call in number for unscheduled TelePresence endpoints to join" and "Meeting organizers must enable this feature for each individual meeting" are selected in the Configure > Application Settings > Bridges and Servers tab. Recurring meeting scheduled with three CTS endpoints and the first occurrence is in the past. Settings changed in Configure > Application Settings > Bridges and Servers tab to "A call in number is always included" and then the endpoints, time or date of the second meeting occurrence are changed.
Workaround: Disable and Re-enable TelePresence Call-In Number.
Symptom: CTS-Manager in cluster deployment has log levels set to Debug in the Troubleshoot > Log Files > Log Levels tab.
Conditions: After fresh install of CTS-Manager cluster, standalone CTS-Manager 1.8 is during first-time set up of primary application server of the cluster.
Workaround: Manually change the log levels to Error. Leaving log levels set to Debug a long period of time can performance issues.
Symptom: "Provide a Call-In Number for Other Participants?" options set to Null in the Meeting Manager > Meeting Options tab.
Conditions: "Allow meeting organizers to send a call in number for unscheduled TelePresence endpoints to join" and "Meeting organizers must enable this feature for each individual meeting" are selected in the Configure > Application Settings > Bridges and Servers tab. Recurring meeting scheduled with three CTS endpoints. Settings changed in Configure > Application Settings > Bridges and Servers tab to "A call in number is always included" and then an endpoint is deleted from the meeting.
Workaround: Disable and Re-enable TelePresence Call-In Number.
Symptom: "Finish" button does not appear after adding secondary application server in cluster. "In Process" message is displayed.
Conditions: Setting up CTS-Manager in cluster deployment.
Workaround: Make sure the secondary application server was added successfully by going to Configure > Cluster Management > Application Servers tab and making sure the added application server status is green. When it is green, the process is finished.
Symptom: Video Conference Call-In Number in the Meeting Details window is incorrect. Video Call-In Number shown on the endpoint phone/display device is also incorrect.
Conditions: TelePresence Server (TS) set as primary multipoint scheduling device. Meeting scheduled with VC rooms using TS.
Workaround: To get the correct number, refer to the Call-In Number for Video Conferencing Devices in the email confirmation.
Symptom: Call-in number for VC room and TelePresence Call-In number is changed.
Conditions: The time of a scheduled recurring meeting with VC and TelePresence call-in numbers is changed by one hour. 2 hours before and 2 hours after the meeting, no other meeting can have the same conference ID.
Symptom: Secure connection failed for EWS during first-time setup.
Conditions: During first-time setup of primary application server of a CTS-Manager cluster, change from normal to secure mode and uploaded valid certificates.
Workaround: If EWS fails during first-time setup, change to normal mode instead of secure mode and after FTS, upload valid certificates and change back to secure mode.
Symptom: "Provide a Call-In Number for Other Participants?" is not selected in the Meeting Manager window even though "Allow meeting organizers to send a call in number for unscheduled TelePresence endpoints to join" and "A call in number is always included" are selected in the Configure > Application Settings > Bridges and Servers window.
Conditions: "Allow meeting organizers to send a call in number for unscheduled TelePresence endpoints to join" and "Meeting organizers must enable this feature for each individual meeting" are selected in the Configure > Application Settings > Bridges and Servers window, then the meeting is scheduled. After that, "A call in number is always included" is selected in the Configure > Application settings > Bridges and Servers window.
Workaround: Set "Provide a Call in Number for Other Participants" manually on the Meeting Manager > Meeting Options tab.
CTS-Manager Release 1.7.x Caveat Reference
Table 4 summarizes caveats found in CTS-Manager Release 1.7
Caveats for CTS-Manager Release 1.7
Symptom: When booking a multipoint meeting from Outlook over 365+ days, CTS-Manager books the meeting with an error; the meeting organizer is sent an "Action Required" email stating the meeting cannot be booked due to insufficient multipoint resources.
Conditions: CTS-Manager 1.7.X / 1.8.X with EWS
Exchange 2007 EWS or Exchange 2010 SP1 EWS
Room calendars have BookingWindowInDays set to value over 365
During nightly maintenance, if the meeting falls within the multipoint scheduling device cache window, the meeting will then be assigned a multipoint scheduling device but no email is sent during nightly maintenance to inform the user the meeting is booked.
Symptom: Meeting migration fails with error "Unable to migrate meetings due to current/or future meetings on target MCU."
Conditions: Meetings from CTMSs were migrated off due to a scheduled power outage. All meetings on all CTMSs were migrated successfully. Once power was restored, meeting were migrated back All but 2 of these migrations were successful. On these two CTMSs, there are no meetings displayed. In CTS-Manager, the two CTMSs are displayed with Scheduled as 'No', but active and future scheduled meetings are in the CTS-Manager calendar.
Workaround: Workaround 1: Delete/update the future scheduled meetings on the calendar so that they are removed from the CTMS in question, and then try migration operation.
Workaround 2: Wait for the future scheduled meetings to go in to past state and then try migration operation.
Symptom: No error message appears when a meeting is migrated to a CTMS that does not have enough resources.
Conditions: Attempt to migrate a meeting to a CTMS that does not have enough resources.
Symptom: Symptom 1: Some rooms missing from meeting. Symptom 2: After Exchange maintenance task recurring exceptions are missing.
Conditions: After maintenance window
Workaround: Reacceptance of recurring meetings restores the missing instances. Root cause is that changes done in CTS-Manager to support Exchange 2007 SP2 and Exchange 2010 broke the handling of recurring exceptions (both for 2010 and 2007).
Symptom: A meeting scheduled in the Russia time zone displays as one hour off, due to Russia's recent change to no longer use daylight saving time (starting autumn 2011) while CTS-Manager still uses DST for Russia.
Conditions: CTS-Manager ver 1.7.3.
Workaround: Use Asia/Muscat date/time group for proper offset.
Symptom: Meeting extension option cannot be enabled.
Conditions: Meeting Extension Premium Users was enabled and later became disabled and grayed out.
Workaround: Restarting CTS-Manager enabled the meeting extension options.
Symptom: Endpoint licenses invalid after software upgrade.
Conditions: The software was upgraded from version 220.127.116.11-237 to version 18.104.22.168-3229.
Workaround: License must be reinstalled.
Symptom: Software upgrade can not switch to new version after upgrade.
Conditions: The software was upgraded when the "switch versions" option was selected.
Workaround: CTS-Manager must be switched manually after the software upgrade, by clicking the Switch Versions button in the Configure > Software Upgrade window.
Symptom: Dates are not upgraded in the Monitor > Metrics Dashboard, Monitor > TelePresence Utilization, Monitor > Meeting Benefits, and Monitor > VC Utilization windows if endpoints are removed.
Conditions: Endpoints are removed before the data for those rooms are stored in the database.
Workaround: Restart CTS-Manager.
Symptom: Switching the software version fails after software upgrade.
Conditions: Upgrade using Configure > Upgrade Software and select the option to switch to the new software after upgrade or after upgrade, manually switch to the new version.
Symptom: Recurring meeting with individual meeting instances that have been changed cause endpoint (room) sync failures. Multiple rooms (endpoints) fail to sync. After booking a P2P or MP recurring meeting and changing any instance by adding a room, the added room will then show a sync failure.
Conditions: After upgrading to 1.7.2 and after booking a P2P or MP recurring meeting and changing any instance by adding a room, the added room (endpoint) will then show a sync failure.
Workaround: Switch the CTS-Manager version back to 1.7.1 will allows rooms to sync successfully.
Symptom: Meeting status does not change to "In Progress" in the Monitor > Meetings window after meeting is started.
Conditions: Start meeting, log in to CTS-Manager administrative UI and go to Monitor > Meetings.
Symptom: Cannot log in as live desk user.
Conditions: group fqdn was added manually and OU has special characters.
Symptom: Recurring meetings run out conference IDs.
Conditions: When CUVC conference ID length is set to 1 and when 10 or more meetings are created in the same time slot, the last meetings may not be scheduled and throw a "resource not available" error.
Workaround: Move the meeting to a different time slot, it is more likely to get updated with a new and unique conference ID.
Symptom: Some CUVC interop meetings may fail to be updated with error "Cannot generate unique conference ID on the conferencing bridge..." in TelePresence Engine Component logs.
Conditions: When CUVC Conference ID length is set to 1 and about 9-10 meetings are created in the same or overlapping time slot, updating one of the meeting may throw error to generate unique conf Id in the TelePresence Engine Component logs.
Workaround: Move the meeting to a different time slot, it is more likely to get updated with a new and unique conference ID.
Symptom: No SNMP trap sent with power supply failure or disk failure.
Conditions: Power supply or disk failure
Symptom: Scheduled daily maintenance does not complete.
Conditions: Connection problem with Exchange server.
Symptom: Number to Dial is not displayed in Meeting Options tab of Meeting Manager.
Conditions: User schedules a meeting with one endpoint.
Workaround: Once logged in, user must click the Summary page to find the Number to Dial field to enter the dial number.
Symptom: No warning message appears asking user if they want to save changes and changes are saved in the Configure > Application Settings window.
Conditions: Change some setting on one of the Application Settings page
Click another tab or item in the left pane of the window to navigate away from the window.
Symptom: Information about configuring WebEx with proxy server is not found in documentation.
Symptom: utils network ipv6 host CLI command does not work.
Conditions: User enters opens CTS-Manager CLI and enters the command utils network ipv6 host.
Workaround: None. ipv6 is not supported for CTS-Manager 1.8. No ipv6-related commands are available.
Symptom: CTS-Manager sends no email alert notification when disk usage exceeds a threshold value and can run out of disk space.
Conditions: CTS-Manager has no email alerts for disk usage.
Symptom: When CTS-Manager has been configured in Microsoft Exchange Web Services mode, modifying the time of an individual occurrence of a recurring meeting could create a duplicate occurrence in CTS Manager.
Conditions: An occurrence of a recurring meeting is modified in the Exchange server to have a different start time of day.
Symptom: Using a web browser that can open with multiple tabs or windows can cause Webex user authentication to fail. Also, clicking the Preferences link in the meeting details window can cause an HTTP 500 error.
Conditions: CTS-Manager licensing schema does not support temporary licenses.
Symptom: When scheduling a meeting using the Scheduling API, the meeting does not get scheduled.
Conditions: Meeting was scheduled using RDATE.
Workaround: Schedule the meeting using RRULE.
Symptom: Test connection to Microsoft Exchange server fails in CTS-Manager PreQualification Assistant Tool and CTS-Manager.
Conditions: CTS-Manager admin password includes a percent (%) sign.
Workaround: Avoid creating a CTS-Manager admin password that includes a percent (%) sign.
Symptom: Clicking the WebEx button in Cisco TelePresence meeting confirmation email to go to the CTS-Manager login screen, meeting organizer cannot log in on first attempt and receives the following error: "Insufficient credential `Meeting Organizer'. Requires credential `SysAdmin, Administrator or Live Desk'."
Conditions: When the meeting organizer clicks the WebEx button in the confirmation email and tries to log in to CTS-Manager the first time.
Workaround: Refresh browser window.
Symptom: When trying to log in to CTS-Manager, user sees blank page or "Service Temporarily Unavailable" error message.
Conditions: CTS-Manager is under a heavy load of HTTP requests, which can occur when it is managing more than 100 CTS endpoint devices and more than 25 concurrent user logins.
Workaround: Wait for 30 minutes and log in again. If the problem persists after a couple of login attempts, contact Cisco TAC.
Symptom: Unable to download logs.
Conditions: When the time to build the log tar bundle is outside the range of 30 sec to 3 min. This is related to the total size of the logs, but is driven by time consumed to build the tar bundle.
Workaround: Downloading logs using CLI:
Log in to the CLI as the SysAdmin user and use the following command:
file get activelog ctis/adminui/logs/AdminUI.log
To get all of the logs, you must get all of the files using the above command on an SFTP server.
Symptom: When the WebEx reserve key pool is below watermark and you try to enable WebEx for a meeting, new WebEx meeting keys will be requested from WebEx. Due to a duplicate WebEx key returned from WebEx site, the WebEx enable operation fails. This happens very rarely.
Conditions: When you try to make a reserve API call to WebEx, a DB exception error occurs stating a unique constraint violation and WebEx is not successfully enabled.
Workaround: Wait five minutes and try to enable WebEx again. The new set of keys may not have a duplicate key and the operation will be successful.
Symptom: Insufficient CTMS resources to create meetings.
Conditions: Deleting an in-progress meeting from Microsoft Outlook or IBM Lotus Notes does not delete it from CTS-Manager.
Workaround: Provision the CTMS with enough segments or schedule a new meeting at a different time.
Further Problem Description: Because CTS-Manager doesn't delete in-progress meetings or free up resources used by them, a CTMS that is already scheduled at full capacity will still have insufficient resources for creating new meetings, even if an in-progress meeting is deleted to free up resources.
Symptom: Production License Registration page does not have a vertical scroll bar, so you can't click the Migration License link that is located at the bottom of the page.
1. Upgrade system from 1.6 or 1.5 to 1.7 and click the Get an Upgrade License.
2. Click the link http://cisco.com/go/license.
Product License Registration page appears, but without scroll bar and Register for Upgrade/Migrate License link is located at the bottom of this page so the user can't find it.
Workaround: Open a new browser window and do the following:
1. Go to http://cisco.com/go/license and log in. The Product License Registration page appears.
2. In the Migration License section at the bottom of the page, click Register for Upgrade/Migrate License. The Select Product page appears.
3. From the drop-down menu, select Cisco TelePresence Manager and click Goto Upgrade/Migration License Portal. The Upload Features page appears.
4. Copy and paste the MAC Address into the first field and the Upgrade Code into the next field and click the Agreement checkbox to accept the terms of the end-user license agreement.
If the upgrade code does not appear, please contact email@example.com.
5. Enter your contact information, making sure your email address is correct, and click Continue.
6. The license file will arrive via email in less than one hour.
7. Save the license file.
Note You can rename the file without special characters or spaces, but don't change the information in it.
8. In Cisco TelePresence Manager, go to the Configure > Licenses window, click the License Files tab and upload the license file.
Note If you don't receive the license file after one hour or have problems uploading the license file, contact the Cisco Technical Assistance Center (TAC). If the number of room licenses you receive does not match the total licenses you purchased, email firstname.lastname@example.org with information about your license and your proof of purchase, including your Cisco sales order number or purchase order number.
Symptom: After upgrading CTS-Manager to version 1.7, the IBM Domino VC rooms cannot be added to CTS-Manager.
Conditions: The issue appears when there is an upgrade to version 1.7.
Workaround: Upload the IBM Domino Certificate (TrustedCerts.class) again.
Symptom: No confirmation email is sent when migrating all meetings from one bridge or server to another.
Conditions: When migrating all meetings from one bridge or server to another.
Symptom: A meeting from one MXE to another MXE results in mismatch of meeting number and bridge number shown in Meetings > Meeting Details > Bridges and Servers window and the confirmation email sent by the CTS-Manager. VC Rooms can join only after CTS joins.
Conditions: Migrating a meeting from one MXE to another or both CTMS and MXE.
Workaround: Use the bridge number shown in the confirmation email to call in to the meeting and make sure CTS rooms join before VC rooms.
CTS-Manager Release 1.6.x Caveat Reference
Table 4 summarizes caveats found in CTS-Manager Release 1.4 to 1.6.5.
Caveats for CTS-Manager Release 1.6.5
Symptom: CTS-Manager assigns the same video access ID to two interop meetings that are less then 2 hours apart.
Symptom: Misleading help description in security status.
Conditions: Under MCU/capacity.
Symptom: CTS-Manager fails to authenticate with Unified CM.
Conditions: CTI Service is not running on the publisher node of the Unified CM cluster.
Workaround: Start the CTI Service on the publisher node of the Unified CM cluster.
Symptom: Video Conference Interop: Bridge Phone Number" in confirmation email and "Video Conference Access Number" in webui meeting details not consistent while they mean the same thing.
Symptom: Export schedule meeting -> showing wrong entry after view it via Excel.
Conditions: Seems only for a large amount of data.
Symptom: Question mark shows as status for some future scheduled meetings.
Conditions: Occurs when some future meetings are scheduled.
Symptom: Prequalification test for Microsoft Exchange EWS fails mailbox quota test.
Conditions: If the CTS-Manager user logon name is different from the LHS of the email ID and there is no matching email ID for the user.
Workaround: Add a secondary email ID that uses the CTS-Manager logon name as the LHS of the email ID appended with the SMTP domain.
Symptom: CTS-Manager shows room synchronization failure in Microsoft Exchange WebDAV mode. System log files show it is unable to perform room synchronization due to an unexpected meeting returned back from the Microsoft Exchange Server. This could manifest to another system where a meeting deleted from the room calendar does not get deleted from CTS-Manager.
Conditions: This occurs if the room calendar does not contain any scheduled meeting during a specific time period.
Workaround: Create a monthly recurring meeting that starts in the past and ends 6 or more months in the future.
Symptom: One or more recurring meeting instances, deleted from calendar are not deleted from the CTS-Manager database.
Conditions: This issue occurs if the recurring meeting has one or more instances modified (subject, room and/or time) and the whole recurring meeting series is deleted.
Workaround: The workaround is to create a future recurring meeting with the same set of rooms as the original meeting that was not deleted from the CTS-Manager database.
Symptom: CTS-Manager fails to communicate with Cisco Unified Communications Manager (Unified CM) displaying the following error message: "Failed to initialize the Trust Manager for CCM Adapter:java.io.IOException: stream does not represent a PKCS12 key store java.io.IOException: stream does not represent a PKCS12 key store".
Conditions: CTS-Manager upgrade from release 1.5 to release 1.6.
Symptom: When the system is loaded with a very large number of meetings, TelePresence Engine may fail to save the resource reservation records for some meetings in the database during first-time startup.
Conditions: This may happen when CTS-Manager is syncing a large number of meetings for the first time along with meeting deletions and modification at the same time.
Workaround: Maintenance cycle will fix this issue. Meeting modification specific meeting will fix this issue.
Symptom: The Intercompany Access Number in the confirmation email for an intercompany meeting has a period following the country code. This is not an E164 format.
Conditions: In order for CTS-Manager to evaluate the country code of origin separately from the E164 dial number, the user must provide the E164 number beginning with the country code followed by a "." and the local phone number. Example:123.123455555
Symptom: IMM not supported on MCS-78x5 server.
Conditions: Customer trying to use IMM interface to control the server since the data center is not physically accessible.
Symptom: Schedule meeting shows wrong entry after exporting and view it with Excel.
Conditions: Exporting large amount of data.
Symptom: CTS-Manager does not send an email Access Number Prefix is modified
Conditions: When Access Number is modified from a CUVC profile.
Workaround: Deallocate the CUVC, Wait for all the Interop meetings are processed, then change the Access Number Prefix and select Scheduled mode from the CUVC profile. Side effect of the workaround is not fully evaluated.
Caveats for CTS-Manager Release 1.6.4
Symptom: JBoss Enterprise Application Platform Status Servlet Request Information Disclosure and JBoss Web Console Cross-Site Scripting (CVE-2009-2405) - JBoss Enterprise vulnerabilities.
Conditions: Scan of CTS-Manager performed.
Symptom: CTS-Manager Pre-Qualification Assistant Tool doesn't work due to unsupported domain version.
Conditions: Using LDAP with CTS-Manager in an environment where the domain controller is running Windows 2008 R2 OS
Symptom: Clicking Scheduled Meeting Details opens a very small web browser window.
Conditions: When using the IP address of the CTS-Manager to launch the web UI.
e.g. https://<server ip address>
Workaround: Use the DNS name of CTS-Manager to launch the web UI.
e.g. https://<server name>
Symptom: Attempts to log in to CTS-Manager causes a SocketTimeoutException error. Out of memory is noticed in TE logs.
Workaround: Restart CTS-Manager.
Symptom: Microsoft Exchange calendar sync with more than 850 rooms, takes too long and needs to be optimized.
Conditions: Large database.
Symptom: Restarting CTS-Manager with more than 850 rooms crashes CTS-Manager.
Conditions: Large database.
Symptom: Discovery of more than 850 rooms takes more than 2.5 hours which is significantly more than the typical 30 minutes for this load.
Conditions: Codec devices version 1.6.4, 1.6.3, and possibly all 1.6.x.
Symptom: Adding rooms to and deleting rooms from a meeting in the calendar are incorrectly displayed in the Cisco TelePresence Manager UI.
Conditions: Modifying rooms in the calendar for a TelePresence meeting that is in progress.
Symptom: JDBC Server Externally Available.
Conditions: Informix JDBC server running that allows remote access to the Informix database if user knows the password.
Symptom: CTS-Manager doesn't support certain OS versions of LDAP/Exchange.
Conditions: OS 2008 R2.
Caveats for CTS-Manager Release 1.6.3
Symptom: In Microsoft Exchange EWS deployment, meeting deleted from room calendar is still showing in CTS-Manager.
Symptom: Scheduled multi-point meeting gets rejected due to insufficient MP resource.
Conditions: The scheduled meeting time overlaps with other existing meeting.
Symptom: Meeting is not downloaded to phone.
Conditions: Room is added to a meeting while in progress.
Symptom: Time zone information is shown with null value on Scheduled Meeting page.
Symptom: CTS-Manager throws error while uploading CAPF certificate.
Conditions: This problem happens when CTS-Manager was downgraded from 1.6.x version to 1.5.x version.
Symptom: Live Desk user cannot login to CTS-Manager.
Conditions: Live Desk user is part of a group in a peer domain or additional domain.
Workaround: Move the Live Desk user to local domain.
Symptom: Discovery remains in starting state.
Conditions: Add Cisco Unified Call Manager 8.0.x.
Symptom: Admin user created using set account cli command can not log in to CTS-Manager administrative web UI.
Conditions: Only when the user is assigned with certain password combinations and phrases which are restricted.
Caveats for CTS-Manager Release 1.6.2
Symptom: No meeting information in CTS-Manager after upgrading from 15.x to 1.6.x.
Conditions: Domino super user has LDAP DN format name.
Symptom: Whenever a meeting is created after March 28th (the day when the UK changes from GMT to BST and applies DST), the email notification sent from CTS-Manager displays the wrong time (one hour earlier).
The meeting in the OWA calendar as well as the meeting details of the CTS-Manager web UI (Support > Scheduled Meetings) both have the correct time.
It's only a cosmetic issue with the meeting notification received by the user. This, however, may confuse them.
Conditions: - Microsoft Outlook 2007 SP1, version: 08.01.0240.006
- CTS-Manager 22.214.171.124 (64)
- User scheduling the meeting is in EU/London time (GMT) timezone.
- Scheduled meeting time is during UK Daylight Saving Time (DST) (British Summer Time).
For GMT DST starts on Sunday, March 28, 2010 at 1:00 AM local standard time and ends on Sunday, October 31, 2010 at 2:00 AM local daylight time.
Symptom: DB restore to a different server can cause login failed with, "System is being maintained. Try again later," and never recover.
Conditions: DB didn't initialize successfully.
Workaround: Restart DB and restart server.
Symptom: Test connection fails for Exchange installed using EWS.
Conditions: Super user's AD domain and SMTP email domain are different. Only windows authentication is enabled in IIS for EWS.
Workaround: Use AD domain without the .com in the domain name field on Exchange page. Mailbox quota will say unable to get info though.
Symptom: Multi-forest LDAP support needs to be expanded.
Conditions: Can't add more than one LDAP server for Microsoft Exchange WebDAV and EWS.
Symptom: TelePresence endpoint doesn't show sync status even though everything is operating correctly.
Conditions: CTS-Manager deployed with IBM Domino and meetings were created when the Resource Reservation database was not using the Resource Reservation Template 7 and later.
Workaround: The Resource Reservation database must be created using the Resource Reservation Template 7 and later. This is a CTS-Manager requirement: http://www.cisco.com/en/US/partner/docs/telepresence/cts_manager/1_7/admin/ctm_instalIBM.html.
Caveats for CTS-Manager Release 1.6.1
Symptom: Adding a Cisco Unified CM server with a secure profile cause the Test Connection command to fail, displaying the following message: 'Unable to create provider null'.
Conditions: Unified CM server has no certificate.
Workaround: When adding a Cisco Unified CM server with a secure profile in CTS-Manager add a certificate for that Unified CM server.
Symptom: Cisco Unified CM publisher goes into error mode.
Conditions: Subscriber is deleted from the Cisco Unified CM and discovery is triggered on the publisher with CTI running on both publisher and subscriber.
Workaround: When removing one node from cluster, it's suggested to restart RisDC and AMC services on all nodes.
Symptom: After deleting a room some meetings in that room are not removed from the CTS-Manager database.
Conditions: CTS-Manager was down or had network connectivity problems when the room deletion occurred and lost its connection to the Microsoft Exchange server.
Symptom: CTS-Manager web UI login by Live Desk group members or the Admin group members unsuccessful.
Workaround: Unknown. System may recover by itself after some time.
Symptom: Test Connection with complex password will pass for a secure Unified CM, but will fail in the runtime of Discovery. Once the password is changed and if Discovery is kicked off, Discovery will be OK showing all the rooms, but the Unified CM server will show error status in UI.
Conditions: Secure Unified CM profile with complex password.
Workaround: Change the password to avoid complex characters do a Test Connection, save and restart CTS-Manager.
Symptom: When a user tries to convert an intercompany recurrent meeting from one type of intercompany to another type of intercompany, i.e., hosted type to hosting type (type maps on UI to ->Another company option to Our company option) or vice versa. The dialog to apply the settings provide user with both the options, i.e., apply to all the future instances and apply to this instance.
Conditions: Both of the options of intercompany, our company type and another company type are enabled globally in the enterprise and user is trying to convert the recurrent meeting from one type of intercompany to another.
Workaround: User must always choose in this type of conversion the option to apply all and not the option to apply to this instance.
Symptom: Pre-Qualification Assistant tool and CTS-Manager Retrieve mailbox quota information failed even with the quota set as recommended.
Conditions: This occurs if the userID and display name are the same for a user in Domino.
Workaround: None, other than ignoring this particular failure message.
Symptom: Insufficient JBOSS access controls may allow access to sensitive applets.
Conditions: JBoss provides access to various files and Java servlets. Some of these are reachable externally with no authentication required.
Caveats for CTS-Manager Release 1.6
Symptom: Backup to remote SFTP server failed.
Conditions: Remote SFTP run on SunOS nemesis 5.9 Generic_118558-27 sun4u sparc SUNW,Sun-Fire-V240.
Symptom: Security advisory on vulnerabilities on the TSL/SSL package.
Conditions: An industry-wide vulnerability exists in the TLS protocol that may potentially impact any Cisco product that uses any version of TLS /SSL. The vulnerability exists in how the protocol handles session re-negotiation and exposes users to a potential Man-in-the-middle attack.
Symptom: CTS-Manager does not determine the correct CTMS for a interop scheduled call.
Conditions: User schedules a non-interop meeting and later changes it to an interop meeting.
Symptom: Manual version switch fails after upgrade.
Conditions: Upgrade is done with "automatically switch version after upgrade" set to No. After upgrade is done, CTS-Manager is restarted before the version is switched.
Workaround: Upgrade again but do not restart before switching the version.
Symptom: Establishing secure IBM Domino connection does not work when a secure HTTP port is provided.
Conditions: Fresh installation.
- In the CTS-Manager Administration UI, select IBM Domino in the left navigation pane.
- Select secure bind method.
- Specify the port value to the normal DIIOP port configured in IBM Domino Server.
- This workaround requires normal DIIOP port to be enabled.
Symptom: Admin user not able to login... System reports that it is in maintenance mode.
Conditions: This occurs after db restore and if db did not recover.
Workaround: * It is fixed - It should not occur any more.
* In rare circumstances - if it occurs again, there is no work around.
Symptom: When looking at restore script log, it is observed that it is trying to delete a row from db matching a filename "07.23.10.tar.gz" or "CTSMan_db_backup....03-27-". For both of them, it is throwing errors.
Conditions: The reason is, db output is wrapping long filenames into two lines and hence, they are broken in any single line. They need to be concatenated to form valid filenames and only then, operation should be attempted.
Symptom: CTS-Manager/CTMS/CTRS won't create a default snmp "admin" user for fresh installation.
Conditions: All the customer created, modified snmp users and trap destinations will still be migrated. However, system created default "admin" user with default password, "snmppassword", unchanged won't be migrated to 1.6 or later releases.
Symptom: When a Scheduled Studio mode recording call is launched and ended, the meeting doesn't show in-progress/completed on CTS-Manager web UI. CTS-Manager currently doesn't support transitioning meeting states based on Inbound call notifications. CTS gets a inbound call notification from CTRS when a studio mode recording is launched.
Conditions: Happens with studio mode scheduled recording meetings only.
Symptom: A modified Single room recurring meeting instance does not show in CTS-Manager.
Conditions: This might happen if the changes are done within a few minutes of creating the meeting. Sometimes the Exchange doesn't send out event when an instance date is changed.
Workaround: Users can update the meeting instance to reflect the correct request.
Caveats for CTS-Manager Release 1.5.1
Symptom: SNMP trap will be delayed by 40 seconds if a power cord is removed from an HP server.
Conditions: Always - if you remove and plug power cord back in within less than 30 seconds, you may not receive a trap to indicate there was a power change.
Caveats for CTS-Manager Release 1.5
Symptom: CTS-Manager pop up is missing the radio button to click Yes/No when a meeting organizer logs into CTS-Manager from a Confirmation email and modifies a recurring meeting.
Conditions: When the browser computer's Display settings has the DPI setting set to "Custom settings" with a larger font size.
Workaround: Select "Normal size (96 DPI)" for Control Panel->Display->Settings->Advanced->General->DPI settings. Your computer will restart after changing the settings.
Supplemental End User License Agreement
This Supplemental End User License Agreement ("SEULA") contains additional terms and conditions for the Software product that is used with Cisco's TelePresence product, including features, functionality and solutions enabled in such Software (collectively, "Software Product") licensed under the End User License Agreement ("EULA") between you and Cisco (collectively, the "Agreement"). Capitalized terms used in this SEULA but not defined will have the meanings assigned to them in the EULA. To the extent that there is a conflict between the terms and conditions of the EULA and this SEULA, the terms and conditions of this SEULA will take precedence.
In addition to the limitations set forth in the EULA on your access and use of the Software Product, you agree to comply at all times with the terms and conditions provided in this SEULA. DOWNLOADING, INSTALLING, OR USING THE SOFTWARE PRODUCT CONSTITUTES ACCEPTANCE OF THE AGREEMENT, AND YOU ARE BINDING YOURSELF AND THE BUSINESS ENTITY THAT YOU REPRESENT (COLLECTIVELY, "CUSTOMER") TO THE AGREEMENT. IF YOU DO NOT AGREE TO ALL OF THE TERMS OF THE AGREEMENT, THEN CISCO IS UNWILLING TO LICENSE THE SOFTWARE PRODUCT TO YOU AND (A) YOU MAY NOT DOWNLOAD, INSTALL OR USE THE SOFTWARE PRODUCT, AND (B) YOU MAY RETURN THE SOFTWARE PRODUCT (INCLUDING ANY UNOPENED CD PACKAGE AND ANY WRITTEN MATERIALS) FOR A FULL REFUND, OR, IF THE SOFTWARE PRODUCT AND WRITTEN MATERIALS ARE SUPPLIED AS PART OF ANOTHER PRODUCT, YOU MAY RETURN THE ENTIRE PRODUCT FOR A FULL REFUND. YOUR RIGHT TO RETURN AND REFUND EXPIRES 30 DAYS AFTER PURCHASE FROM CISCO OR AN AUTHORIZED CISCO RESELLER, AND APPLIES ONLY IF YOU ARE THE ORIGINAL END USER PURCHASER.
These SEULA terms will apply to the following Software Products:
Product Name Function
Cisco TelePresence Multipoint Switch
Cisco TelePresence Manager
Cisco Unified Video Conferencing
Cisco Unified Video Conferencing Manager
For the purpose of this SEULA, we define the following terms:
"Authorized Service Provider" is a service provider that has an agreement with Cisco that explicitly authorizes support for the Restricted Features.
"Intra-company Use" is a use of the Software Product which occurs within the same company/entity and which traverses a service provider network for the purpose of interconnecting and communicating to endpoints within the same companies/entities.
"Inter-company Use" is a use of the Software Product which occurs between two or more companies/entities and which traverses a service provider network for the purpose of interconnecting and communicating to other companies/entities. A use may include functionality that is accessed before, during or after a Cisco TelePresence meeting. Inter-company Use also includes providing features of the Software Product in a commercially available service offering.
"Restricted Features" means one or more of the following features: (i) Inter-company Multipoint encryption; and (ii) Inter-company HD/SD Inter-Operability.
In addition to the Agreement, the following supplemental terms apply:
1. The Restricted Features are available or potentially enabled in this Software Product but may only be used for Intra-company Use. THE RESTRICTED FEATURES CANNOT BE USED FOR THE PURPOSES OF INTER-COMPANY USE UNLESS SUCH USE IS PERMITTED BY AN AUTHORIZED SERVICE PROVIDER. IF YOU WERE TO USE THE RESTRICTED FEATURES FOR INTER-COMPANY USE, YOUR USE OF THE RESTRICTED FEATURES PRIOR TO SUCH AUTHORIZATION WOULD CONSTITUTE A BREACH OF THE AGREEMENT. Unless your use is through an Authorized Service Provider, you are not authorized to use the Restricted Features for Inter-company Use until the Restricted Features have been noted as a generally available feature set in the updated release notes for the Software Product, as posted by Cisco on cisco.com. Notwithstanding the foregoing, your Intra-company Use of the Restricted Features shall not be restricted by this paragraph.
2. The CTS-Manager calendaring feature for scheduling TelePresence calls may only be used for Intra-company Use. The CTS-Manager calendaring feature may not be used with more than one calendaring application. Customers in a shared office space with multiple tenants using their own calendaring solution must deploy one CTS-Manager per tenant.
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
CCVP, the Cisco logo, and Welcome to the Human Network are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networkers, Networking Academy, Network Registrar, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0711R)
© 2010 Cisco Systems, Inc. All rights reserved.