Chapter 3 Installing Web Conferencing for a Segmented Meeting Access Configuration
About Segmented Meeting Access
Figure 3-1 Segmented Meeting Access-2 Server Configuration
1 |
LAN/WAN |
3
2
DMZInternet
4 | 121504 |
|
1 | Internal Cisco Unified MeetingPlace web | 2 | External Cisco Unified MeetingPlace web |
| server |
| server |
| This web server sits inside the private |
| This web server sits in a network segment, |
| corporate network. |
| such as a DMZ. |
|
|
|
|
3 | Internal user | 4 | External user |
| • Internal users enter internal meetings |
| • External users can enter external |
| through the internal web server. |
| meetings only. |
| • Internal users enter external meetings |
| • Users enter these meetings through the |
| through the external web server. |
| external web server. |
|
|
|
|
About the SMA-2S Configuration with SSL and Segmented DNS
If your Cisco Unified MeetingPlace Web Conferencing system has SSL configured on the external web server and a segmented DNS, the segmented DNS name cannot be the same as the SSL certificate name on the external or internal machine. See the following example for configuration guidelines.
Example
You have an
•The segmented DNS name is meetingplace.company.com.
•The SSL certificate name for the external machine is meetingplace1.company.com.
•The hostname for the external machine from the internal machine is meetingplace1.
•All URLs and
When users access http://meetingplace.company.com from the external network, the external machine will automatically redirect them to HTTPS plus whatever hostname is configured in the
Note If you force SSL on all users, both internal and external users will be forced to use SSL when they access the external web server.
Installation and Upgrade Guide for Cisco Unified MeetingPlace Web Conferencing Release 6.x
|
|
| |
|
|