Cisco Systems Unified MeetingPlace Web Conferencing 사용자 설명서

In the OS Image field, verify the operating system version. 

Click OK to close the MCS Version Utility. 

If there is a problem with a Windows service or the web server loses its connection, go to the 
drive:\Program Files\Cisco Systems\MPWeb\datasvc directory and run Dcdiags.bat as soon as possible 
to generate a server log. All diagnostic information is stored in the Cisco Systems\MPWeb\Diagnostics 
directory. 

Zip these files, and send them to your Cisco support representative for additional assistance.

The web server must be able to connect to itself by using the hostname you configured on the Web Server 
administrative page. This is also the hostname used by end users to connect to this web server. 

Connection problems are most likely caused by firewall-related configurations. 

The following procedure uses hostname.domain.com as an example. Replace hostname.domain.com 
with your web server’s actual FQDN.

From the web server, use a web browser to connect to http://hostname.domain.com. 

If you receive an error message, add the following line to the C:\WINNT\System32\drivers\etc\hosts file: 

Try to connect to http://hostname.domain.com again. 

If users are not able to access the full meeting room after upgrading the Audio Server from a previous 
release, it is possible that the Full Web Conferencing Ports setting on the Audio Server is incorrect. 
Perform the following procedure to configure the Full Web Conferencing Ports setting to match the 
number of web conferencing licenses available on your Audio Server.

Start MeetingTime and log in to the Cisco Unified MeetingPlace Audio Server.

Click Administration > Configure.

Click Server Configuration, then click Query. 

Click the value for Full Web Conferencing Ports and enter the number of web conferencing licenses 
purchased.