Contents
- Release Notes for Cisco WebEx Meetings Server
- Finding Documentation
- System Requirements
- Deployment Notes
- Supported Firmware
- Software Updates and Patches
- Limitations and Restrictions
- Recording Limitations
- Localization
- Important Notes
- Hypervisor Support
- System Behavior upon Component Failure
- Configuring Your High-Availability System
- Caveats
- Using Bug Toolkit
- Open Caveats for Cisco WebEx Meetings Server 1.0 Patch 1
- Open Caveats for Cisco WebEx Meetings Server 1.0 Not Resolved in Patch 1
- Resolved Caveats for Cisco WebEx Meetings Server 1.0 Patch 1
- Known Issues and Notices
- Documentation Errata
- Importing, Exporting, and Deactivating Users
- Installing New Licenses
- Localization
- Meeting Trend Time Display
- Meeting Issues Email Procedure
- Viewing Your Resource History
- Generating and Viewing Reports
- Troubleshooting
- Obtaining Documentation and Submitting a Service Request
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. This version of the release notes describes Cisco WebEx Meetings Server version 1.0 (Build 1.0.1.6.A) and version 1.0 Patch 1 (Build 1.0.1.157.A). These release notes are updated for every maintenance release but not for patches or hot fixes. 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 all versions of Cisco WebEx Meetings Server, go to the following URL:
- Finding Documentation
- System Requirements
- Deployment Notes
- Limitations and Restrictions
- Important Notes
- Caveats
- Known Issues and Notices
- Documentation Errata
- Troubleshooting
- Obtaining Documentation and Submitting a Service Request
Finding Documentation
Provide the following URL to your users:
www.cisco.com/en/US/products/ps12732/tsd_products_support_series_home.html
System Requirements
Refer to Cisco WebEx Meetings Server System Requirements, Release 1.0 at http://www.cisco.com/en/US/docs/collaboration/CWMS/b_System_Requirements.pdf.
Deployment Notes
Consider the following when deploying your Cisco WebEx Meetings Server system:
- Make sure the network connection between your VMware vCenter and vSphere client is on a stable connection with at least a 1 GB link and low latency.
- If your VMware vSphere client is installed on your laptop and you are working remotely, upload the Cisco WebEx Meetings Server OVA file onto a local network segment.
- Since the speed of your network determines how long the deployment process takes, we recommend that you have at least a 1 GB network. For 250- and 800-user systems we recommend a 10 GB network.
- Cisco WebEx Meetings Server is designed for a single data center. Please make sure the network latency on your network is as low as possible.
Software Updates and Patches
We strongly recommend that you upgrade to the Cisco WebEx Meetings Server 1.0 patch before using this product. The patch improves the product's stability, provides access to all features, and resolves several issues that are present in version 1.0. See "Resolved Caveats" for the full list of issues that the patch resolves. The Cisco WebEx Meetings Server patch is available at the following URL:Limitations and Restrictions
Recording Limitations
Your storage server is configured to store approximately six months of recordings. Periodically, you should archive any recordings to other media if your organization requires that you keep recordings for more than six months.
Your system performs two tasks to maintain recording space:When a user deletes a recording, it is no longer available from the user interface but it is maintained in storage for six months. Therefore, you can still access the storage server to copy, back up, or use the recording files for six months after they have set for deletion by the user.
Each meeting recording is approximately 50–100 MB and with 1 TB of space allocated for recording storage, your system should have room for six months of recordings with standard usage. However, if the recordings on your system consume over 75 percent of the allocated space after three months, the system automatically deletes the first 10 files that have been set for deletion by the user.
For example, if a user deletes two files today, and then five files tomorrow, and then nine files the day after tomorrow, and then storage usage surpasses the 75% limit after 3 months, the system deletes the first two files today, the next five files tomorrow, and then the first three files deleted the day after tomorrow.
Important Notes
System Behavior upon Component Failure
When specific media and platform components running on a virtual machine go down, these components are automatically restarted by the system. Affected meetings fail over to other available resources in the same or another virtual machine in the system (for other than a standalone 50 user system).
HA Systems
With the deployment of a HA system (added to the primary system), Cisco WebEx Meetings Server will recover for these components when there is a single component failure:
- A single service on one virtual machine.
- A virtual machine.
- A single physical server or blade, which hosts up to two virtual machines (as long as the virtual machine layout conforms to the specifications listed in the Cisco WebEx Meetings Server System Requirements and the Cisco WebEx Meetings Server Planning Guide).
- A single network link, assuming the network is provisioned in a fully redundant manner.
- A single CUCM node, assuming CUCM is provisioned in a redundant manner.
Following the single component failure, the Cisco WebEx Meetings Server system behaves as follows:
- For a period of up to three minutes, application sharing, audio voice connection using computer and video may be interrupted. The Cisco WebEx Meetings Server allows three minutes for the failure to be detected and to reconnect all the affected meeting clients automatically. Users should not need to close their clients and rejoin their meeting.
- Some failures may cause teleconferencing audio connections to drop. If that happens, users will need to reconnect manually. Reconnection should succeed within a two-minute window.
- For some failures, not all clients and meetings may be affected. Meeting connections are normally redistributed across multiple virtual machines and hosts.
Additional Information For a 2000 User System
A 2000 user system provides some high availability functionality without the addition of a HA system. For a 2000 user system without high availability:
- Loss of any one of the Web or Media virtual machines results in a still functioning system, but with impaired capacity.
- However, loss of the Admin virtual machine renders the system unusable.
For a 2000 user system with high availability:
- Loss of any one virtual machine (Admin, Media, or Web) does not affect the system behavior; the system continues to function with full capacity. Loss of any one physical server (hosting the primary virtual machines [Admin and Media or Web and Media] or the HA virtual machines [Admin and Media or Web]) still results in a running system with full capacity.
- When the failed virtual machine is restarted, it rejoins the system and the system will return to a normal working state.
- When a Media virtual machine fails, meetings hosted on that server are briefly interrupted, but the meeting fails over to an alternate Media virtual machine. Users must manually rejoin the desktop audio and video sessions.
- When a Web virtual machine fails, existing web sessions hosted on that virtual machine also fail. Users must sign in to the WebEx site again and establish a new browser session that will be hosted on an alternate Web virtual machine.
- When an Admin virtual machine fails, any existing administrator sessions also fail. Administrators must sign in again to the Administration site and establish a new browser session that will be hosted on the alternate Admin virtual machine. Also, there may be a brief interruption to any existing administrator or end user meeting sessions.
Caveats
- Using Bug Toolkit
- Open Caveats for Cisco WebEx Meetings Server 1.0 Patch 1
- Open Caveats for Cisco WebEx Meetings Server 1.0 Not Resolved in Patch 1
- Resolved Caveats for Cisco WebEx Meetings Server 1.0 Patch 1
Using Bug Toolkit
ProcedureKnown problems (bugs) are graded according to severity level. These release notes contain descriptions of the following:
- All severity level 1 or 2 bugs.
- Significant severity level 3 bugs.
- All customer-found bugs except severity level 6 enhancement requests.
- All severity level 1 or 2 bugs.
You can search for problems by using the Cisco Software Bug Toolkit.
Step 1
To access the Bug Toolkit, go to http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs.
Step 2
Sign in with your Cisco.com user ID and password.
Step 3
To look for information about a specific problem, enter the bug ID number in the “Search for Bug ID” field, then click Go.
What to Do Next
For information about how to search for bugs, create saved searches, and create bug groups, select Help on the Bug Toolkit page.
Open Caveats for Cisco WebEx Meetings Server 1.0 Patch 1
The caveats listed on the following table describes unexpected behavior in the latest Cisco WebEx Meetings Server release. Bugs are listed in order of severity.
Table 1 Open Caveats in Cisco WebEx Meetings Server 1.0 Patch 1 Identifier
Component
Severity
Headline
severe
audio
Cisco WebEx Meetings Server EFT: Poor audio quality.
severe
mc-client-com-pt
PT: Can't login PT on some sites.
severe
admin-sys-config
Lower case site and admin urls before saving (easy).
severe
platform-install
System stuck in Maintenance Mode after add HA in Patch 1.0.1.153.
moderate
admin-sys-config
Upgrade: restored certificates are removed during Deployment FTE.
moderate
mc-client
Cisco WebEx Meetings Server EFT: PT schedules a 48-hour meeting.
moderate
admin-log
Handle abnormally large log files.
moderate
platform-integ
Hostnames, URLs, VIPs changes not properly propagated throughout system.
moderate
sslgw-general
PT: PT can't login when FIPS is ON,TLS 1.2 is used and allow GLA search.
moderate
admin-meetingmon
Data on meeting trend can't be automatically updated.
moderate
documentation
We covered more errors in a simple error message.
moderate
admin-sys-config
Add HA xu build to primary non-xu build, no error description.
moderate
platform-integ
After Update, Admin shows old version, take system off Maintenance stuck.
moderate
mc-web-enduser
Jabber: Lose meeting password if join meeting from meeting reminder.
moderate
admin-systemmon
Download log link to cover non-Admin node on failed deployment.
moderate
mmp-platform
Core files found after add DMZ or HA and after update.
moderate
mc-client-com-inst
Google Chrome gets into a hung loop and fails to load MC.
moderate
admin-sys-config
SSL cert invalid after expansion, but warning msg did not appear after reboot.
moderate
platform-integ
Existing root ssh session retained after depoyment FTE.
moderate
admin-sys-config
Eventbus VM status flapping UP DOWN due to upper lower case in hostname.
moderate
admin-log
Reduce the log collection wait time from 45 minutes.
moderate
admin-sys-config
Add DMZ, got Internal Server Error HTTP request/maintenanceLock/lock.
moderate
admin-sys-config
Cisco WebEx Meetings Server EFT: Resource History shows incorrect time.
moderate
admin-sys-config
Cisco WebEx Meetings Server EFT: QoS markers not found in wireshark trace.
moderate
admin-sys-config
No Email Server Validation in the initial config sequence.
moderate
platform-integ
Remove DMZ, UI alerts saveVipError() in HTTP request.
moderate
licensing
After DR license page doesn't load if overage/expiry occurred before DR.
moderate
List of invites is not available after meeting has started.
moderate
platform-install
Hostnames and URLs should be lower case in the system.
moderate
sslgw-forwarding
50-user system: Primary DMZ VM cannot be upgraded to ISO 137.
moderate
platform-install
Auto deployment fails in certain VMWare setups.
moderate
platform-integ
Change VM IP by changing DNS, exit MM stuck at rebooting.
moderate
platform-integ
Add DMZ to system, UI alerted saveVipError() in HTTP request.
moderate
mmp-platform
All clients leave audio session after joining audio session when cb failover.
moderate
mc-web-enduser
Password tip is disappear and submit button is disabled.
moderate
admin-meetingmon
Contents in usage/problematic email is not correct.
moderate
admin-sys-config
NAS does not get added when not in MM. Ok when in MM.
moderate
Email: When reply recording mail "recipient" won't get right address.
moderate
admin-sys-config
HA Upgrade link doesn't work if extra space at beginning or end of FQDN.
moderate
mc-web-enduser
Scheduling future meetings within 30 minutes does not change button.
moderate
platform-integ
Cleanup supervisor.log.
moderate
admin-sys-config
Glitch error when accessing the Admin Web page.
moderate
xmlapi
Click meeting URL jumped to another meeting info page.
moderate
admin-sys-config
DR completes but no indication on admin until new admin session opened.
moderate
db-core
Update is longer than 30 minutes sometimes, need to reduce DB backup time
Open Caveats for Cisco WebEx Meetings Server 1.0 Not Resolved in Patch 1
The caveats listed on the following table describes unexpected behavior in the latest Cisco WebEx Meetings Server release. This list of caveats covers defects that were not fixed in Patch 1. Bugs are listed in order of severity.
Table 2 Open Caveats in Cisco WebEx Meetings Server 1.0 Not Resolved in Patch 1 Identifier
Component
Severity
Headline
mc-client-com-pt
severe
Cisco WebEx Meetings Server EFT: Productivity Tools warns of redirection with SSO configured.
admin-sys-config
moderate
SSL cert invalid after expansion, but warning msg did not appear after reboot.
admin-sys-config
moderate
Upgrade: Restored certificates are removed during Deployment FTE.
admin-sys-config
moderate
No email server validation in the initial configuration sequence.
licensing
moderate
After disaster recovery, license page does not load if overage/expiry occurred before disaster recovery.
mc-client-com-inst
moderate
Google Chrome gets into a hung loop and fails to load MC.
platform-install
moderate
Reenable maintenance lock for add DMZ, upgrade, update, expand.
platform-install
moderate
Hostnames and URLs should be lowercase in the system.
platform-install
moderate
Auto deployment fails in certain VMWare setups.
platform-integ
moderate
Add DMZ to system, UI alerted saveVipError() in HTTP request.
platform-integ
moderate
Existing root SSH session retained after depoyment FTE.
platform-integ
moderate
Change virtual machine IP address by changing DNS, exit maintenance mode stuck at rebooting.
Resolved Caveats for Cisco WebEx Meetings Server 1.0 Patch 1
The caveats listed on the table below describe issues that were resolved in this Cisco WebEx Meetings Server 1.0 Patch 1 release. The caveats in this table are also open caveats for Cisco WebEx Meetings Server 1.0.
Table 3 Resolved Caveats in Cisco WebEx Meetings Server Identifier
Component
Severity
Headline
db-core
severe
Database deadlock encountered during disaster recovery on 2000-user systems.
admin-sys-config
severe
Could not access new Administration site URL after changing URLs and VIPs.
platform-install
severe
1.0.1.1: Add NAS during disaster recovery fails with exception error.
platform-integ
severe
Not in Cisco WebEx Meetings Server 1.0: OVA 20002 : Cannot manual deploy with IRP.
sso
severe
SSO login fails after a restore DB action from back up.
mc-web-enduser
severe
Firefox16 cannot start a meeting.
admin-log
severe
Meeting log capture needs to include leading zeros in log capture file name.
mc-web-enduser
severe
Inactive users get deactivated after upgrading system to 1.0.1.152.A.
mc-web-enduser
severe
rKey parameter of playback page is vulnerable to cross-site Scripting.
platform-install
severe
If an extra space is added at the end of a system name then add high availability will fail.
db-core
severe
Expansion failed due to error in database restore.
mc-client
severe
Meeting cannot be started on 1.0.1.112 Patch1 after upgrade.
admin-sys-config
severe
UI doesn't show correct status on failed high availability addition.
mc-client
severe
Cannot launch meeting on latest beta Chrome on Mac.
admin-meetingmon
severe
Alpha: constant warnings about Meetings experiencing issues.
ha
severe
After disaster recovery, taking system out of maintenance mode is blocked.
platform-integ
severe
Puppet does not sync files right if hostname has mixed case.
platform-integ
severe
After major upgrade or expansion default login must be deactivated.
eventbus
severe
On some nodes, change in VIP and URL may result in eventbus going down.
db-core
severe
Administration site cannot start as database authentication fails.
platform-install
severe
Cleanup distribution required for security.
platform-install
severe
System stuck in maintenance mode after add high availability in Patch 1.0.1.153.
mc-web-enduser
severe
Inactive users get deactivated after upgrading system to 1.0.1.152.A.
admin-sys-config
severe
Add HA stuck on 1.0.1.6 build when using IE.
mc-web-enduser
moderate
Activation email link cannot load iOS application.
mc-client-com-pt
moderate
L10N-PT: Some strings incorrectly translated.
platform-install
moderate
Major upgrade FTE reported calibration network failure on 250-user system.
mc-web-com-waf
moderate
Australia and Mexico are missing from the country list under Company Information.
mc-web-enduser
moderate
User signs out and then signs in and page does not work.
moderate
Email: When reply recording mail "recipient" will not retrieve the correct address.
moderate
Email: Recurrent meeting cannot receive reminder mail after two reminders have been successfully sent and received.
sslgw-dmz
moderate
Alpha: FCS Build - Can no longer access Alpha using iOS Devices.
mmp-platform
moderate
Wbxmcc,mcs and msc core files on micro standalone.
mc-web-enduser
moderate
Version information service reveals internal IP addresses.
mc-web-enduser
moderate
National Flag for some countries should follow meeting client.
platform-install
moderate
Delays encountered during addition of high availability.
admin-sys-config
moderate
Validate authenticity token when checking previous passwords.
eventbus
moderate
Missing the resubscription.
admin-sys-config
moderate
In a certain maintenance mode case, FIPS button in admin not updated if disabled or enabled.
db-core
moderate
Rebuilding of unusable indexes after call for their checking.
admin-sys-config
moderate
Cannot upload certificate with both wildcard and SAN.
admin-systemmon
moderate
Keeps restarting while in maintenance mode.
platform-integ
moderate
During Add DMZ, early checks are not reported.
mc-client-com-p
moderate
Productivity Tools: The message is not right for Productivity Tools when they are started automatically.
platform-install
moderate
Update high availability skipped pre-checks.
admin-sys-config
moderate
Certificates disappear in administration if bad pkcs12 is uploaded.
db-core
moderate
Update the set of files to be restored for license during upgrade and expansion.
platform-integ
moderate
Cannot ssh into redundant IRP using remote support created before adding high availability.
sslgw-general
moderate
Client prompts "Due to a connection issue, you cannot..."
admin-systemmon
moderate
NM ---- snmpd fills up wbxmonxpm.out logs.
admin-sys-config
moderate
Upload chain with missing intermediate certificate replaces existing certificate.
mc-client
moderate
Mac client VoIP user VOIP change to unmuted status after CB failover.
eventbus
moderate
Cisco WebEx Meetings Server EventBus: No events received after network disconnection.
platform-install
moderate
Auto with DMZ: Invalid FQDN can be entered.
mc-web-enduser
moderate
Recurrent meeting cannot be searched in set recurrence range.
ha
moderate
DMZ SSL stays DOWN.
mc-web-enduser
moderate
Some country names are missing on end user and admin page.
db-core
moderate
Prevent disaster recovery on high availability system.
mc-client-com-pt
moderate
Add "Switch Site" clear guidance to Productivity Tools help document.
admin-sys-config
moderate
L18N DE, add high availability UI blank due to Java error.
admin-sys-config
moderate
High availability add/remove: Incorrect showing of progressing indicator.
licensing-elm
moderate
LicenseHA:Grace period will be broken when failback to Pri bf elm sync.
platform-integ
moderate
Remove DMZ, UI alerts saveVipError() in HTTP request.
platform-install
moderate
High-availability system administrator status is down after update.
admin-sys-config
moderate
Glitch error when accessing the Administration site.
licensing
minor
Should enable system once user installs overage licenses.
admin-sys-config
moderate
Internet Explorer 8 - Cannot Download CSR.
platform-install
moderate
Private key listed in supervisor.log during upload.
admin-sys-config
moderate
Remote support account expiration date on admin is incorrect.
db-core
moderate
Add high availability: fails with Database-106 with no message.
admin-reporting
moderate
Cannot generate peak day and hour data and end page in report.
eureka-server
moderate
WBXms and WBXApp, and WBXwmswc version in patch1 is wrong, not updatable.
telephony
moderate
KPML user call back always fails.
licensing
minor
Should enable system once user installs overage licenses.
ha
minor
High-availability system restarts Event Bus too early
admin-sys-config
minor
Cannot sign in to the Administration site if the administrator's password includes the string, "pass."
admin-sys-config
minor
Remote support account: Date too far in the future.
platform-install
minor
Add two DMZ lower versions to system, no message alerts for mismatching versions.
admin-systemmon
minor
The labels in Network History should be aligned.
admin-sys-config
minor
Time zone list is not localized for some languages.
admin-sys-config
minor
Confusing certificate message after a minor upgrade.
mmp-platform
minor
MCS/MCC generate core file after kill -15/TERM wbxmcs.
admin-sys-config
minor
L10N ALL - message about invalid certificate after virtual machines added to system.
platform-install
minor
Remote support account does not work after update.
documentation
minor
WBX*INPROGRESSMEETING table is missing data when a meeting ends at a specific time.
admin-sys-config
minor
Remember me expiration time not controlled by server side logic - admin.
platform-integ
minor
Remove Public Access UI page - siteUrl variable not replaced by value.
admin-sys-config
minor
Goes to sign-in page after session timeout if user signs in with "remember me" checked.
admin-meetingmon
minor
There should not be a spare problematic meeting alarm/clear email.
platform-install
minor
Start with -XU then minor update; version no longer shows -XU.
admin-sys-config
minor
Certificate error message after major upgrade on Administration site.
admin-meetingmon
minor
Meeting trend cannot be automatically refreshed.
licensing
minor
After disaster recovery, the license page should not show restored license from the primary system.
admin-sys-config
cosmetic
Email: Spelling mistake in high-availability system mail.
admin-sys-config
cosmetic
Typo in Remove HA, OVA 1977.
platform-integ
enhancement
Support tarball checksum validation.
Known Issues and Notices
Keeping Your Hostname While Changing Your Virtual 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:
- Configure a temporary hostname in the DNS.
- 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.
- Change the IP address of the original hostname in the DNS to the new IP address.
- 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.
Support Information
The end-user online help contains inaccurate browser support information. Refer to the System Requirements for the correct information.
Dashboard Issues
On the Meeting Status page under Monthly Reports, when you display data for the last month, the text under the graph incorrectly indicates that "Problems were experienced in x% of meetings in the last three months." It should read "Problems were experienced in x% of meetings in the last month."
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 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 unmated 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.
Documentation Errata
- Importing, Exporting, and Deactivating Users
- Installing New Licenses
- Localization
- Meeting Trend Time Display
- Meeting Issues Email Procedure
- Viewing Your Resource History
- Generating and Viewing Reports
Importing, Exporting, and Deactivating Users
This section describes errata in the online help pertaining to importing, exporting, and deactivating users. Refer to "User Management" in the online help and the Administration Guide for the affected sections."About Comma- and Tab-Delimited Files" and "Setting Import File Field Values" Sections
The "About Comma- and Tab-Delimited Files" and "Setting Import File Field Values" online help topics are subtopics of "Deactivating Users." However, both topics are pertinent to all import and export user tasks, not just deactivating users.
The USERID Field in Comma- and Tab-Delimited Files
The topic "About Comma- and Tab-Delimited Files" says that the USERID field "must be left blank" when importing. This is true if you are creating new users, but it is incorrect if you are making changes to existing users.
Deactivating Users by Using the Import Feature
The section, "Deactivating Users," does not state that you can use the import feature to deactivate users. To deactivate users by using import, you must first export to a .csv file. This gets you the USERID field, which the system uses to identify the records you will change when you perform your import. You must build your import .csv file including the following changes:
- Change the ACTIVE column to N for the users you want to deactivate.
- Remove the records for the users that you do not want to change.
Perform your import. If you do not perform these steps, your import will fail for the changed users with the error "email address already exists."
Installing New Licenses
Actions that Require New Licenses
The following system-altering actions require that you install new licenses. For more information on installing licenses, refer to "Managing Licenses" in the Administration Guide.
- Expansion—Refer to "Expanding Your System to a Larger System Size" in the Administration Guide for more information.
- Upgrade—Refer to "Upgrading the System" in the Administration Guide for more information.
- Disaster Recovery—Refer to "Using the Disaster Recovery Feature" in the Administration Guide for more information.
Meeting Trend Time Display
The description of Meeting Trend data is not accurate. Refer to "Using Your Dashboard" in the online help and the Administration Guide for the affected sections.Meeting Trend Data
The description of the Meeting Trends graph includes the following statement:
"Meeting trend data is based on Greenwich Mean Time (GMT) and is therefore not accurately displayed over a 24-hour period. For example, if your system hosts 200 meetings during a given day, the database records the occurrence of those meetings based on GMT and not local time."
This is true for the one-month and six-month views but the one-day and one-week view data are based on the user's time zone.
Meeting Issues Email Procedure
ProcedureWhen you receive an email indicating that there are issues with meetings, perform the following steps to determine the cause.
Generating and Viewing Reports
When your system is newly deployed or recently upgraded, there is no data available for any of the reports except the Customized Details Report until the end of the first month. In that case, the Download links and all the other reports described in this section are not available until after the end of the first month. Refer to "Generating and Viewing Reports" in the online help and Administration Guide for more information.Troubleshooting
See the Cisco WebEx Meetings Server Troubleshooting Guide at http://www.cisco.com/en/US/docs/collaboration/CWMS/b_troubleshootingGuide.pdf.
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.