[an error occurred while processing this directive]

Cisco WebEx Meetings Server

Release Notes for Cisco WebEx Meetings Server Release 2.0

 Feedback

Release Notes for Cisco WebEx Meetings Server

These release notes describe new features, requirements, restrictions, and caveats for all versions of Cisco WebEx Meetings Server Release 2.0. These release notes are updated for every maintenance release but not for patches or hot fixes. Note that each maintenance release includes the features, requirements, restrictions, and bug fixes of the previous releases unless mentioned otherwise. Before you install Cisco WebEx Meetings Server, we recommend that you review this document for information about issues that may affect your system.

To access the latest software upgrades for this product, go to the following URL: http:/​/​software.cisco.com/​download/​ then navigate to your product. From Products, select WebEx > Web Conferencing > Cisco WebEx Meetings Server > Cisco WebEx Meetings Server 2.0.

New and Changed Features for Cisco WebEx Meetings Server Release 2.0

This section describes features that are new or changed in this release.

For a complete list of system requirements, including supported hardware and operating systems, see the Cisco WebEx Meetings Server System Requirements Release 2.0 at http:/​/​www.cisco.com/​en/​US/​products/​ps12732/​prod_​installation_​guides_​list.html.

For information about all available features and benefits, see the data sheet for this release of Cisco WebEx Meetings Server at http:/​/​www.cisco.com/​en/​US/​prod/​collateral/​ps10352/​ps10362/​ps12732/​data_​sheet_​c78-717754.html.

System Improvements

  • Operating system upgrade: Cisco WebEx Meetings Server operating system is upgraded to CentOS 6.4
  • Support for NAS storage: Fiber Channel (FC), Network File System (NFS), or SCSI only

Hardware Support

This release now supports the Cisco UCS B420 server with the following specifications:
  • CPU: Intel® Xeon® Processor E5-4650
  • Speed: 2.7 GHz
  • Cores: 8
  • Sockets: 4
  • Total vCPU: 64

Large Meetings

This release supports large meetings that can accommodate up to a maximum of 250 users per meeting on 800 users systems and 2000 user systems. Large meetings require these systems to be configured in HA mode.

Mobile Support

This release supports Android devices that use Android 2.1 or later. It was tested with Android WebEx App 4.0, 4.1, and 4.5.

For iOS, this release was tested with iOS WebEx App 5.1.

Upgrade to the latest version of the WebEx App to benefit from the new features that were added in this release.

Operating System Support

This release now supports Microsoft Windows 8 operating system.

Tested Browsers

Release 2.0 has been tested to work with the following web browsers:

Windows
  • Internet Explorer: 8 - 10 (32-bit/64-bit)

    Note


    IE 11 was tested on Windows 7 SP1 only


  • Mozilla Firefox: 10 - 25
  • Google Chrome: 23 - 31
Mac
  • Apple Safari: 6
  • Mozilla Firefox: 10 - 25
  • Google Chrome: 23 - 31

Note


Because of Google and Mozilla policy changes, starting with Chrome 32* and Firefox 27*, users may need to manually enable the WebEx plug-in when using these browsers to join a WebEx meeting or play back a WebEx meeting recording. More information and instructions can be found in our Joining a WebEx Meeting on Chrome and Firefox FAQ.

*The exact versions of Chrome and Firefox that are impacted by this policy have not been finalized as of the publishing of this document.


WebEx Productivity Tools

WebEx Productivity Tools now supports the following:
  • Microsoft Outlook 2013
  • Lync 2010 (32-bit)
  • Lync 2013 (32-bit)
  • Microsoft Office Communicator 2007
  • Microsoft Office Communicator 2007 R2

Accessibility Improvements

Section 508 of the U.S. Rehabilitation Act defines requirements for product accessibility. Your Cisco WebEx Meetings Server website and meeting application provide keyboard accessibility and limited Screen Reader support on Windows. For Release 2.0, an audio option was added to the text-based CAPTCHA (the textual challenge users are required to respond to when signing up for a WebEx account or when recovering a password to identify them as actual persons).

End-User Experience Enhancements

  • Improved recurring meeting support: You can now modify or delete a single occurrence of a recurring meeting series from both the Cisco WebEx Meetings Server website and WebEx Productivity Tools. Invitees receive email notifications alerting them of the modifications and your Microsoft Outlook calendars remain in sync.
  • Recording improvements: An option now displays on the scheduling page for you to automatically set recording for your meetings. You can also choose to download recordings or the NBR player from the Recordings tab on the Cisco WebEx Meetings Server website.
  • Entry and exit tones: You can now configure what you want to hear, such as a beep or no sound at all, when users enter and exit your meetings.
  • Scheduled maintenance window alerts: Warnings indicate when you are attempting to schedule or reschedule a meeting during a scheduled maintenance window.
  • Video tutorial for first-time access: The system provides you with a video tutorial when you first access the Cisco WebEx Meetings Server website.

    Note


    The video tutorial is not displayed if the system is configured to display customized Help but without a valid link rather than the default Cisco WebEx online help.

Administrator Enhancements

  • Improved reports: Provides improvements to monthly summary reports (PDF) and customized reports (CSV).
  • Improved Maintenance Mode: The following configuration tasks no longer require that you put the system in Maintenance Mode:
    • Quality of service (these configuration fields were found on the Admin > Settings > Quality Of Service page in previous releases)
    • Mail server (these configuration fields were found on the Admin > System > Configuration > Servers > MailServer page in previous releases)
    • Call-in access numbers, caller ID, and display name (these configuration fields were found on the Admin > Settings > Audio page in previous releases)
  • Enhanced management of maintenance window: This release improves your ability to schedule, cancel, and update system maintenance windows. Users are prevented from scheduling meetings during a maintenance window and alerted when scheduled maintenance is currently taking place.
  • LDAP filter: Enables you to choose which users to import from the Cisco Unified Communications Manager (CUCM) directory to the Cisco WebEx Meetings Server (CWMS) directory using LDAP.
  • Improved Administrator dashboard: Provides a redesigned dashboard with a focus on meeting lists and meeting trends.

Supported Upgrade Paths

This release of Cisco WebEx Meetings Server supports upgrades from release 1.x to 2.0 keeping the following in mind:

  • An upgrade is defined as a replacement of the system to deploy major modifications that we made to the system.
  • An update is defined as an incremental modification of the system to deploy fixes and minor improvements, for example updating a system running version 1.0 to run version 1.1.
  • In both cases all of the data from the original system, except for logs and log captures, is transferred to the updated or upgraded system.
  • When upgrading, you cannot skip a FCS version of the software and go directly to a companion maintenance release (MR). You must upgrade to the most recent FCS version and then update the system to a MR version. For example, you can upgrade from release 1.0 to 2.0. If, however, you want to upgrade to release 2.0 MR, you must first upgrade from 1.0 to 2.0 then update to the 2.0 MR.

Limitations and Restrictions

Recording Limitations

You can create as many recordings as your storage server capacity will allow. Estimate the required storage server size for a typical five-year period using the following formula:

Estimated hours of meetings that you expect to be recorded per day * 50-100 MB per hour of recording * five years * 24 hours per day * 365 days per year

There are no per-user storage limitations. Recordings are stored indefinitely until you delete them. There is no feature that enables you to automatically delete recordings due to the possibility that this would enable users to accidentally delete important recordings. Once you mark a recording for deletion, the recording is actually kept on the storage server for up to six months, giving you time to archive recordings on other media.

For more information on recording limitations, refer to the "Network-Based Recording (NBR)-Recorded Video Resolutions and FPS" section of the Cisco WebEx Network Bandwidth white paper at http:/​/​www.cisco.com/​en/​US/​prod/​collateral/​ps10352/​ps10362/​ps10409/​white_​paper_​c11-691351.pdf.

Internet Reverse Proxy Might Be Removed From the Platform

The Admin virtual machine can send a remove message to the Internet Reverse Proxy server to remove it from the platform. This message is sent as clear text, is unauthenticated, and could lead to a denial of service.

Using IP tables or access control lists (ACLs), configure the firewall so that connections to port 64616 only come from the Admin virtual machine.

Productivity Tools

Incompatible Versions

Each release of Cisco WebEx Meetings Server supports a specific version of the Cisco WebEx Productivity Tools client. You can download the supported version of Productivity Tools from the Downloads link on your Cisco WebEx Meetings Server website. Using incompatible versions of these two applications, for example, Productivity Tools Release 2.0 with Cisco WebEx Meetings Server Release 1.5 or lower, results in the following issue:

When the user schedules a WebEx meeting, the meeting time displays incorrectly on the website. This issue applies for both single and recurring meetings.

Updating a Recurring Meeting Scheduled from Microsoft Outlook

This release has the following limitations when updating a single instance of a recurring meeting series that was scheduled from the Microsoft Outlook integration:

  • User does not see the "Add WebEx Meeting" option: User schedules a standard recurring meeting series from Outlook. When the user attempts to update a single instance of the series, the user does not see the option to add the WebEx component to the meeting. In this instance, we recommend that the user schedules a new meeting that includes the WebEx option, or change the entire recurring meeting series to include the WebEx component.
  • WebEx is not removed from meeting exceptions: User schedules a recurring meeting series. User edits one or more instances to indicate a different time or date, then cancels the recurring meeting series. In this instance, the meetings that were edited are not canceled in Outlook. However, the WebEx information that is retained with the meetings are no longer valid.
  • Canceled meetings still display on web page: User schedules a recurring meeting series from Microsoft Outlook. User deletes a meeting instance from the series, then adds WebEx to the recurring meeting series. In this instance, the meetings that were deleted from the original recurring meeting series will still display on the Cisco WebEx Meetings Server website.
  • Updates not reflected in meeting exceptions: User schedules a recurring meeting series from Microsoft Outlook. User edits a single instance of the meeting series by changing the meeting topic, list or attendees, or location. User then edits the meeting content in the entire recurring meeting series. In this instance, any updates made to the series are not reflected in the meetings that were updated separately.
  • WebEx component does not reflect future meeting time: User schedules a WebEx meeting from Microsoft Outlook. The meeting time passes. The user drags one instance of the series to a time in the past, then updates it to reflect a time in the future. In this instance, the WebEx component of the meeting remains the same. It cannot be updated to reflect a future time.

Important Notes

Hypervisor Support

Cisco WebEx Meetings Server runs on VMware virtual machines.
  • Both VMware vSphere and VMware vCenter are required to deploy Cisco WebEx Meetings Server. Using the vSphere client, you will deploy the Cisco WebEx Meetings Server OVA file on an ESXi host managed by vCenter.
  • You must purchase VMware vSphere 5.0, 5.0 Update 1, or 5.1 for use as the hypervisor platform for Cisco WebEx Meetings Server by completing one of the following:
    • Buy vSphere directly from Cisco on the GPL (Global Price List). Cisco is an approved VMware partner and distributor. This is convenient for those who "want everything from a single vendor".
    • Purchase vSphere directly from VMware, through enterprise agreements you have directly with VMware.
  • Cisco WebEx Meetings Server does not support other hypervisors.
  • For more information about hypervisor requirements, see the Cisco WebEx Meetings Server System Requirements at http:/​/​www.cisco.com/​en/​US/​products/​ps12732/​prod_​installation_​guides_​list.html.

Configuring Your High-Availability System

When you update a high-availability system, after you reboot the system and the reboot process appears to be complete, we recommend that you wait an additional 15 minutes before starting your add high-availability system procedure.

About Using Self-Signed Certificates

We strongly recommend using a publicly signed certificate instead of the provided self-signed certificate. Publicly signed certificates are trusted by users' browsers since trust for them is established using the list of Root Certificate Authority certificates installed on each user's computer.

When using self-signed certificates, some users might have difficulty joining meetings because browsers by default do not trust such certificates. Users are required to explicitly establish trust in this case before they can proceed to join a meeting on your site. Some users might not understand how to establish trust with such a certificate. Others might be prevented from doing so by administrative settings. Therefore, you should use publicly signed certificates whenever possible to provide the best user experience.

The User Guide provides a topic on this issue for end-users. Refer to the "Meeting Client Does Not Load" topic in the Troubleshooting chapter of the Cisco WebEx Meetings Server User Guide at http:/​/​www.cisco.com/​en/​US/​products/​ps12732/​products_​user_​guide_​list.html.

Expanding Your System

If you have VMware snapshots of your existing (pre-expansion) system, make sure your expanded system is up and running while removing or deleting your existing system. This prevents accidental removal of the hard disk 4 base VMDK file, which might be accessed by the expanded system.

Productivity Tools Upgrade Notice

If a previously deployed Productivity Tools package has a different version or build number from a newly deployed Productivity Tools package and the upgrade is not blocked, then your Productivity Tools client will notify you with an upgrade warning dialog box.

SNMP v2 Community Names

There is no default SNMP v2 community name entry in this release of Cisco WebEx Meetings Server. The system will remove the existing Cisco WebEx Meetings Server 1.0 default Community Name, "CWS-Public," after upgrading. Only user-added SNMP v2 community names are maintained.

Known Issues and Notices

Uninstalling Cisco WebEx Meetings Application

The following uninstall behavior is a known issue when you have both the on-premises and cloud versions of the Cisco WebEx Meetings Application installed on your local hard drive:

When you click atcliun.exe from the WebEx folder to uninstall the Cisco WebEx Meetings Application, both the on-premises and cloud versions of the application are removed. However, when you delete the application using the Control Panel, only the on-premises version of the application is deleted. For more information, see the "Uninstall Cisco WebEx Meetings Locally" topic in the Cisco WebEx Meetings Server Planning Guide at http:/​/​www.cisco.com/​en/​US/​products/​ps12732/​products_​installation_​and_​configuration_​guides_​list.html.

Apple iOS 6.x and SSO

There is a known issue with Apple iOS 6.x, where Single Sign-On (SSO) does not work for internal users of iPad/iPhone who are using the Safari 6 web browser. This is due to an Apple defect that is fixed in iOS 7. The Safari bug ID is 13484525.

Translated Documentation

Translated documentation for this release of Cisco WebEx Meetings Server will be published 4-6 weeks after the English-language release.

Keeping Your Hostname While Changing Your Virtual Machine IP Address

Never change the DNS entries for the hostnames that are configured in your deployment. You can change the hostname of a virtual machine that is part of your deployment. The corresponding IP address is picked up automatically from the DNS. If you want to change the IP address of a virtual machine and keep the same hostname, you must perform the following steps:

  1. Configure a temporary hostname in the DNS.
  2. Change the hostname of the virtual machine to the temporary hostname that you configured and take the system out of maintenance mode for the new hostname to take effect. Your original hostname is not part of the deployment after making this change.
  3. Change the IP address of the original hostname in the DNS to the new IP address.
  4. Change the temporary hostname of the virtual machine to the original hostname and take the system out of maintenance mode for the hostname to take effect. Now the original hostname with your new IP address is configured.

FQDN Text

When you deploy virtual machines from vCenter using the OVA file, make sure the virtual machine hostname does not contain uppercase characters or underscores. When changing the hostname at the Administration site also make sure the virtual machine hostname does not contain uppercase characters or underscores.

Dashboard Issue - Failure to Display Meetings That Have Started

There is a known issue in this release of Cisco WebEx Meetings Server in which the dashboard fails to represent certain meetings as having started. This occurs in the following scenario: A meeting is scheduled with the "Allow participants to join teleconference before host" setting enabled. A user joins the meeting by phone but does not join the web portion. The dashboard should indicate that this meeting has started and has one participant but it does not. This may cause users to schedule multiple meetings resulting in performance issues.

Audio Configuration

On your audio configuration settings, note that G.711 will yield better voice quality than G.729. Refer to "About Configuring Your Audio Settings" in the Cisco WebEx Meetings Server Administration Guide for more information.

IP Communicator 7.0.x Endpoints

IP communicator 7.0.x endpoints joining Cisco WebEx Meetings Server meetings might introduce audio quality issues (echo and other noises) to a conference if it is in unmuted state or the participant using this endpoint becomes an active speaker. To prevent this, make sure you fine tune the IP communicator environment (for example, the headset, microphone, and speaker) or use a different traditional phone.

Meetings Started with iOS Devices

Meetings that are started with iOS devices cannot be recorded.

Android Devices

There is a known issue for users of Android that if the host has enabled True Color Mode in his or her meeting client settings, desktop sharing will not display correctly on the Android device. You can make sure that True Color Mode is disabled by selecting Meeting > Options from your Cisco WebEx Meetings page.

Windows Internet Explorer Issue

There is a known issue when you view user documentation with the Windows Internet Explorer 8 or 9 browser. A javascript error may be displayed in the lower left corner of your window while you are paging through the documentation. If you click on this error message, a Windows Internet Explorer pop-up message appears. Select the Always show this message for webpage errors check box if you want to see this message when an error condition is encountered. Select Close and continue reading the documentation. This error does not affect documentation.

Caveats

Using Bug Search Tool

Known problems (bugs) are graded according to severity level. These release notes contain descriptions of the following:

  • Open customer-found bugs of severity 1 - 3
  • Resolved customer-found bugs of severity 1 - 5
  • Resolved Cisco-found bugs of significance

You can find details about listed bugs and search for other bugs by using the Cisco Bug Search Tool.

Before You Begin

To access Bug Search Tool, you need the following items:

  • Internet connection
  • Web browser
  • Cisco.com username and password
Procedure
    Step 1   To access the Bug Search Tool, go to https:/​/​tools.cisco.com/​bugsearch/​search.
    Step 2   Sign in with your Cisco.com username and password.
    Step 3   Enter the bug ID number in the “Search for” field, then press Enter.
    Tip    You can also navigate to a specific bug by entering https:/​/​tools.cisco.com/​bugsearch/​bug/​<BUGID> where <BUGID> is the ID of the bug that you are searching for (e.g., CSCab12345).

    What to Do Next

    For information about how to search for bugs, create saved searches, and create bug groups, select Help on the Bug Search Tool page.

    Open Caveats in Cisco WebEx Meetings Server Release 2.0

    The caveats listed in the following table describe unexpected behavior in this release of Cisco WebEx Meetings Server. Refer to Bug Search Tool for further details.

    Table 1 Open Caveats in Cisco WebEx Meetings Server Release 2.0 (Build 2.0.1.2)
    Identifier Severity Headline
    CSCum68885 2 Users unable to join meeting unless host starts meeting from Web
    CSCum66805 3 CWMS Log Collection results in heavy writes to SAN
    CSCul48912 3 SSLGW killed by NM - SMALL HA DMZ continuous load run
    CSCum85537 3 CWMS 1.x - Not all countries are listed when creating a CSR
    CSCum88800 3 LARGE DMZ:FIPS ON:Load issues for Video sharing using ext SiteURL
    CSCum77581 3 Some services after MM off not coming up in a timely manner

    Resolved Caveats in Cisco WebEx Meetings Server Release 2.0

    The caveats listed in the following table describe issues that were resolved in this release of Cisco WebEx Meetings Server. Refer to Bug Search Tool for further details.

    Table 2 Resolved Caveats in Cisco WebEx Meetings Server Release 2.0 (Build 2.0.1.2)
    Identifier Severity Headline
    CSCuj32654 1 SSLGW Session Connect Failed Due To Invalid Cookie JSESSIONID
    CSCuj40077 1 CWMS Audio quality issues caused by RTC tick drifting
    CSCul20389 1 Error running mctoolUpgrade(). Error code: 507
    CSCul81686 1 CWMS admin flooding /triage dir with logs
    CSCui36487 2 Add HA or Enable Public Access fails after Grow using 1.1.1.9 OVA file
    CSCuj41809 2 Select 'Server auth enabled', CWMS cannot connect mail server.
    CSCul30354 2 Replication stops after /db/ partition on secondary admin is filled up
    CSCul47327 2 Users get deactivated due to creation date and not inactivity
    CSCuh76157 2 documentation not mentioning ICMP echo is needed for deplmnt validation
    CSCuj85393 2 Gyromain core file
    CSCuj13973 2 RTP packet crashes MPE module in CWMS
    CSCuj99830 2 SSLGW crash on CWMS
    CSCui44039 2 attendee can't jbh if last meeting of Recurrence Meeting not initialized
    CSCul78127 2 Rediness Check for established connection fails if Internal IP's NAT'd
    CSCul94862 2 CWMS Update instructions must be corrected
    CSCul98172 2 Adding HA with host name that starts with number(s) to primary failed
    CSCuj71789 2 Intermittently users need to click more than once to join meetings
    CSCul82580 2 Audio Quality Issues when the users are in Mute via the phone Button
    CSCum58019 2 Database system audit table flooding
    CSCub69687 3 PT: Don't support update a single occurrence meeting with PT.
    CSCuh20090 3 Deactivate host account after x days occurs when disabled
    CSCuh95370 3 Please include XMLAPI/URLAPI log within infocap
    CSCui00212 3 Meeting report incorrect value
    CSCui09539 3 CWMS reporting - Web Sharing minutes greater than duration of the conf
    CSCui25358 3 Changing FQDN for VM gets hostname error
    CSCui64590 3 TAL Services LTD:SSLGW cookie should have HttpOnly and Secure flag set
    CSCui68457 3 TAL Services LTD: Please add the HttpOnly and Secure flag set(page)
    CSCui68472 3 TAL Services LTD: Need the patch to Slowloris attack.
    CSCui68483 3 TAL Services LTD: password entry fields should be tagged
    CSCuj06685 3 Unable to sync users from CUCM with a UserID of more then 32 bytes
    CSCuj10290 3 Gateway info cannot be changed properly with the current instruction
    CSCuj44067 3 Can't do user lookup in meeting client if start instant meeting via PT
    CSCuj47179 3 Session data is invalid in 'Meeting Report.csv'
    CSCuj49288 3 'Announce name' doesn't work in the meeting which created from PT.
    CSCuj51131 3 Error popup after successfully generating report
    CSCuj54342 3 Webex storage cannot be added
    CSCuj80593 3 SSO can't be configured after DR - wrong permission on file
    CSCuj85572 3 no escape character in handling Dyr Sync password
    CSCul09763 3 PT: Can't update old meetings after change SSO to LDAP enabled site.
    CSCul16741 3 Nigeria Country Code is missing
    CSCul25327 3 Unable to create password for Administrator user
    CSCul32847 3 Meeting Center version is incorrect in 1.5MR1
    CSCul35798 3 Cannot reschedule meetings in Productivity Tools without signing out
    CSCul63335 3 logo file permissions change upon updating.
    CSCul66228 3 Updating user account settings stuck in loading
    CSCul79267 3 CWMS 1.5 installation error when hostname with numeric charaters.
    CSCui45309 3 Documentation - All fields are required for user import
    CSCui56746 3 Meeting Center Plugin Failed to Install Due to Certificate Expiry
    CSCuj13084 3 Certificate domain is case sensitive
    CSCuj24760 3 idp sso initate log will always forward to meeting list page
    CSCul29941 3 Deployment fails with long hostname
    CSCul73428 3 Default device pool should no be used for CWMS and CUCM Integration
    CSCul17672 3 Document behavior when multiple accounts in CUCM use same email address
    CSCul50499 3 Meeting Trends graph not displayed with Chrome 31
    CSCuj43886 3 CWMS MeetingReport shows NA-NA Participants
    CSCuj47223 3 admin doesn't receive infocap email intermittenly
    CSCuj82149 3 Japanese Kanji charactors are garbled in CWMS Admin GUI.
    CSCul18766 3 VAD is enabled by default on version 1.5
    CSCuj26337 3 Primary admin status shows down on dashboard
    CSCul03486 3 Phanton meeting shown on the dashboard
    CSCul65872 3 Document licensing behavior for simultaneous meetings
    CSCui41472 3 1.5 EFT: ELM not accessible error
    CSCui55957 3 Include NBR logs in infocap.
    CSCul03355 3 Documentation RAID Configuration Requirements for Orion
    CSCul16462 3 When using Hebrew Meeting Number shows up zzzyyyxxx instead of xxxyyyzzz
    CSCui25181 3 Doc - OL scheduling w/ PT for alternate host generates two notifications
    CSCui29057 3 End user prompted to install atinst.exe each time
    CSCui45275 3 CSV headers should not be case sensitive for user import
    CSCui54153 3 Accounts created via SSO on being reactivated sends wrong email template
    CSCui86297 3 CWMS PT 2.80.500.179 won't allow for auto sign-in when using SSO
    CSCuj90993 3 CWMS - Passwords validation fails when using a + sign
    CSCul16439 3 Multiple invites when alternate host assigned.
    CSCul83197 3 Infocap is empty
    CSCul98122 3 CWMS is incorrectly consuming licenses for back to back meetings
    CSCul99819 3 Solr always write info level logs to catalina.out
    CSCum00024 3 Start/End time is diff between meeting and license last month report
    CSCum01810 3 IRP log genertion uses port 64700 from 1.5 site
    CSCum40250 3 Licenses counting: Implementation of "JBH and 15 minutes grace period"
    CSCum46358 3 ELM is inaccessible after upgrade until sync period has passed
    CSCum53311 3 Document Alternate Host does not receive meeting recording notification
    CSCum58985 3 CWMS Call In Feature Behavior
    CSCul63726 3 Improperly formatted
    CSCum35526 3 Puppet .yaml files are not automatically purged from the system
    CSCul87097 3 Video is not recorded from all participants in the meeting
    CSCum35787 3 Puppet reports consuming disk space
    CSCum58164 3 apache tomcat logs do not have timestamps
    CSCum58196 3 Apache tomcat logs not included in infocap
    CSCul81680 3 PT silent install force user to login each time after reboot
    CSCum16003 3 Document Directory Integration HOST/ADMIN user behavior
    CSCum18847 3 Document "Create Password" link expiration time
    CSCum57542 3 One end user can be in a meeting center meeting twice
    CSCul44073 4 Specific port range between internal media VMs and media center
    CSCug49001 4 SSO error codes listed with error messages
    CSCul36080 4 Deactivate host due to inactivity definition
    CSCul69923 4 CWMS SSO and LDAP synchronication docuemtation
    CSCuj56401 4 config procedure table contains wrong links
    CSCuh60854 4 Temporary license expiry warning even after permanent license uploaded
    CSCum75113 4 Can't create tracking code group name the same as predefined group name
    CSCuj71624 5 Incorrect national keyboard handling in the in-meeting Invite window
    CSCul30490 5 Add to email template edit documentation
    CSCum25722 5 CWMS VM responsible for sending out notification mail

    Obtaining Documentation and Submitting a Service Request

    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 http:/​/​www.cisco.com/​en/​US/​docs/​general/​whatsnew/​whatsnew.html.

    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.


    [an error occurred while processing this directive]