Chapter 3 Installing Cisco Unified MeetingPlace Web Conferencing for a Segmented Meeting Access Configuration
About Segmented Meeting Access
1 | Cisco Unified MeetingPlace Audio Server | 2 | Internal DNS server. | |
| system. |
|
| |
|
|
|
| |
3 | Cisco Unified MeetingPlace web server. | 4 | Internal user. | |
| Note | The web server must have two IP |
| • Internal users enter internal meetings |
|
| addresses. |
| through the internal website. |
|
|
|
| • Internal users entering an external |
|
|
|
| meeting are redirected to their meeting |
|
|
|
| from the internal website. |
|
|
|
| |
5 | External user. |
|
| |
| • External users access external meetings |
|
| |
|
| through the external website. |
|
|
| • External users do not have access to |
|
| |
|
| internal meetings. |
|
|
|
|
|
|
|
About the SMA-2S Configuration
Note For system requirements, see the “Segmented Meeting Access - 2 Server Requirements” section of the of the Release Notes for your release of Cisco Unified MeetingPlace Web Conferencing. New installations of Cisco Unified MeetingPlace Web Conferencing Release 5.3 require a Cisco MCS.
In the Segmented Meeting
While internal users have access to the
The
Note We highly recommend that you configure external web servers to use Secure Sockets Layer (SSL). This provides optimum security and resolves proxy server issues that can prevent users from joining a web conference. For more information, see Chapter 6 in the Configuration Guide for Cisco
Unified MeetingPlace Web Conferencing Release 5.3.
Installation and Upgrade Guide for Cisco Unified MeetingPlace Web Conferencing Release 5.3
|
| ||
|
|