Cisco Cisco MeetingPlace Gateway SIM Anleitung Für Quick Setup

Seite von 766
Configuring Cisco Unified MeetingPlace Web Conferencing Security Features
How to Configure Secure Sockets Layer
4
 
Restrictions
Do not perform this procedure if the Web Server is not in a Domain Name Server (DNS).
Procedure
Step 1
Open your web browser and enter the URL of your Web Server.
  •
For internal Web Servers, the default URL structure is http://server, where server is the name of 
your internal Web Server.
  •
For external (DMZ) Web Servers running Release 7.0.1, the default URL structure is 
http://server/mpweb/admin/, where server is the name of your external Web Server. 
  •
For external Web Servers running Release 7.0.2 or later releases, you can only access the 
administration pages for the external (DMZ) server from the server box itself and only through 
port  8002. If you try to access the administration pages on the external (DMZ) server by using http:// 
server/mpweb/admin/, the system will display a 404 “Page Not Found” error. 
To access the administration pages for the external (DMZ) server, you must be on the web server 
box and enter the following URL: http://localhost:8002/mpweb/admin/ 
Note
If SSL is enabled on your system, you must still enter the URL with http and not https. 
The system automatically logs you in as the user called “technician” with technician privileges. 
Step 2
Sign in to the end-user web interface. 
Step 3
Select Admin if you are not already on the Cisco Unified MeetingPlace Web Administration page.
Step 4
Select Web Server.
Step 5
Scroll down to the “View” section of the page.
Step 6
Select the name of the Web Server that you want to configure. 
Information about this Web Server populates the “Edit” section of the page.
Step 7
For 
, enter the fully qualified domain name (FQDN) of the primary network 
interface on the Web Server.
Example: hostname.domain.com.
Note
This hostname must be different from that used for Hostname [Home Page]. It must be 
resolvable by its intended users. Depending on your hostname choice, the hostnames might not 
have been automatically registered with the DNS during the OS installation. We recommend that 
you check the DNS, both the forward and reverse lookup zones, and add entries manually if 
needed. 
Step 8
For 
, enter the FQDN of the secondary network interface on the Web 
Server.
Example: hostnamewc.domain.com.