Cisco Cisco Unified MeetingPlace Web Conferencing 문제 해결 가이드

Complete these steps:

Ping and NSLOOKUP (if open) the fully qualified domain name (FQDN) or IP address of the internal
Web server from another internal PC.

Ping meetingplace.company.com (replace with the correct hostname of the server)

♦ 

NSLOOKUP meetingplace.company.com (replace with the correct hostname of the server)

♦ 

Note: To use NSLOOKUP, open a DOS prompt (go to Start > Run, enter cmd and click OK), then
enter NSLOOKUP meetingplace.company.com (replace with the correct hostname of the server).

1. 

Ping and NSLOOKUP (if open) the FQDN or IP address of the DMZ Web server from an external
PC.

2. 

Ping and NSLOOKUP (if open) the FQDN or IP address of the DMZ Web server from another
internal PC.

3. 

Ping and NSLOOKUP (if open) the FQDN or IP address of the MeetingPlace server from the DMZ
Web server.

4. 

Telnet on port 5003 from the DMZ Web server to the Cisco MeetingPlace server. Follow these steps
to confirm that the port is open:

Go to Start > Run and enter the telnet servername 5003 command, where servername is the
name or IP address of the MeetingPlace server, and click OK.

a. 

If you see a series of nonsensical characters (for example, :¶e,;4/v \?V \?ÿ¢), port 5003 is
open.

b. 

Enter Ctrl−] (Control, right bracket) to exit.

c. 

If you get a failed connection, as shown here, then port 5003 is not open:

Could not open connection to the host, on port 5003: Connection

                                failed

d. 

5. 

What are the most common types of scheduled meetings?

Note:  If the scheduled meetings are mostly internal, set the group default Display Meeting to Everyone
feature to No. If they are mostly public meetings, then set Display Meeting to Everyone to Yes.

Complete these steps (these steps vary based on whether they apply to a one− or two−server deployment):

Verify the hardware and software requirements for the servers.

Makes sure that the hardware on the gateway machine meets all of the appropriate requirements. The
machine that hosts more conferences must have the faster, better hardware.

1. 

For SMA−1S deployment, follow the steps for implementation in Table 5−1, and for Segmented
Meeting Access for 2 Server Deployment, refer to Table 5−2 in the Administrators Guide for Cisco
MeetingPlace Web Conferencing Release 5.3.

2.