Cisco Cisco Unified MeetingPlace Web Conferencing Guida Alla Risoluzione Dei Problemi

Complete these steps:

Verify connectivity between all of the applicable servers:

Ping the Cisco MeetingPlace servers IP address.

a. 

Ping the Cisco MeetingPlace servers hostname.

b. 

1. 

Verify that the gateway server does not communicate with the Cisco MeetingPlace server network
through a Network Address Translation (NAT) scheme. NAT is not supported.

2. 

Complete these steps:

Schedule a meeting.

1. 

Attend the meeting.

2. 

Verify audio recording and conversion, if applicable.

3. 

Join the Web Conference.

4. 

Share a document.

5. 

Enable collaboration.

6. 

Test the slide show function.

7. 

Locate a past meeting that has attachments or recordings. Verify that these attachments are still visible
after the upgrade.

8. 

Complete these steps:

Open a browser and type http://localhost to see if the default Internet Information Services (IIS) page
is displayed.

1. 

Verify the account you are logged into has administrator rights.

2. 

Verify IIS works with these steps:

From another PC on the network, open a browser and try to connect to the gateway machine
with the URL the new Cisco MeetingPlace Web eventually uses.

a. 

From another PC on the network, open a browser and try to connect to the gateway machine
with this machine's IP address.

b. 

3. 

If the Cisco MeetingPlace Web machine uses the Secure Socket Layer (SSL) protocol, do not install
the SSL Certificate or configure IIS to use or force an HTTPS connection in advance. You must
install Cisco MeetingPlace Web before you install and configure SSL.

4. 

A Cisco Media Convergence Server (MCS), or the exact equivalent from HP or IBM, that is dedicated
to Cisco MeetingPlace applications is required. The number of MCSs that you require depends on the
number of voice and web−conferencing user licenses (ports) needed on your Cisco MeetingPlace
system.

•