Cisco Cisco Unified MeetingPlace Web Conferencing Troubleshooting Guide

Complete these verification steps before you go onsite:

Review all applicable Field Notices and the Release Notes for Cisco MeetingPlace Web
Conferencing.

1. 

Confirm the Cisco MeetingPlace Web System Requirements outlined on pages three through four of
the Cisco MeetingPlace Web Conferencing System Manager's Guide are completed.

2. 

Confirm that there is connectivity between all of the applicable servers.

Confirm version compatibility with the Cisco MeetingPlace Web Conferencing System
Manager's Guide.

Note: You must consider what additional Cisco MeetingPlace software is installed on the
MeetingPlace Web machine and which software versions are used.

♦ 

3. 

Verify you have the proper license keys:

Conference Ports license (required for both audio and Web−only recordings)

♦ 

MeetingPlace Web Publisher license

♦ 

MeetingPlace Data Conferencing Option license (required for application share)

♦ 

MeetingNotes Data license (required for presentation and attachments)

♦ 

MeetingNotes Voice Option license (required to post meeting recordings through the Web)

♦ 

4. 

Make sure that you have a copy of the Cisco MeetingPlace Web Conferencing System Manager's
Guide and the software media (registered customers only) .

5. 

If you plan to upgrade, verify the available Cisco MeetingPlace Web machine meets all of the
hardware and software requirements of the new MeetingPlace Web version to which you plan to
upgrade.

6. 

If you plan to install a brand new Cisco MeetingPlace Web, verify that the new server meets all of the
hardware and software requirements of the version you plan to install.

7. 

For synchronized Voice and Web Recording, the Cisco MeetingPlace server software must be:

Version 4.3.0 or later for a Peripheral Component Interconnect (PCI) Server

♦ 

Version 5.02 or later for a Cisco MeetingPlace 8112 (M3) Server

♦ 

8. 

Confirm end user requirements are met per the Cisco MeetingPlace Web Conferencing System
Manager's Guide.

9. 

Confirm you have users from different locations, so that you can test the web site when complete.

10. 

Do you use NT Authenication or will it be implemented?

If your organization requires users to log in to the Windows domain before they access Cisco
MeetingPlace Web Conferencing, set up your web−conferencing server for Windows authentication.
This allows Release 5.3 to pass a users Windows login ID to the web−conferencing server for
verification.

When the web−conferencing server receives this information, the server compares the users
Windows login ID to the users Cisco MeetingPlace user ID. If the two IDs match, the user is
automatically logged into Cisco MeetingPlace Web Conferencing. For more information, refer to
pages 4−19 of the Administrator's Guide for Cisco MeetingPlace Web Conferencing Release 5.3.

11.