Cisco Unified MeetingPlace

Document ID: 60138

Contents

Introduction
Prerequisites
      Requirements
      Components Used
      Conventions
Explanation of the Purge Parameter
NetPro Discussion Forums - Featured Conversations
Related Information

Introduction

Each Cisco MeetingPlace Web server has its own purge parameter called "Purge meetings held before these many days." In a DMZ-C architecture, two Cisco MeetingPlace Web servers work together as a single system. One Cisco MeetingPlace Web server is installed internally, behind the corporate firewall, and is accessible only to internal users. The second Cisco MeetingPlace Web server is installed as an external server (with the ability to attend meetings only), and is relocated outside of the corporate firewall in a DMZ zone. This document explains:

• Purge behavior on the internal server and on the DMZ server.

• File access and retrieval behavior on the internal server and on the DMZ server.

• The importance of consistency between the purge values on the internal server and the DMZ server.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on Cisco MeetingPlace Web (all versions).

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

For more information on document conventions, refer to the Cisco Technical Tips Conventions.

Explanation of the Purge Parameter

Each Cisco MeetingPlace Web server (internal or DMZ) has its own purge parameter: "Purge meetings held before these many days."

If, for example, you set your internal Cisco MeetingPlace Web purge to 60 days, all attachments are kept for 60 days on the internal server. After 60 days, they are deleted from the server. If you set your DMZ server purge to 30 days, then all attachments are kept for 30 days on the DMZ server. After 30 days, they are deleted from the server.

The behavior users see when they try to review past meetings is different when they enter from the DMZ server than when they enter from the internal server:

• When you enter (access the Cisco MeetingPlace Web home page of) the internal server between 0 and 60 days from the time the meeting ended, Cisco MeetingPlace Web tells you this is a past meeting, and displays all the meeting details. You can retrieve attachments.

• When you enter the DMZ server less than one day after the meeting ended, Cisco MeetingPlace Web tells you this is a past meeting, and displays all the meeting details. You can retrieve attachments.

• When you enter the DMZ server between one and 30 days from the time the meeting ended, Cisco MeetingPlace Web tells you "this meeting does not exist or is too early to attend."

Even though the attachments cannot be accessed on the DMZ server after the first day, it is very important to keep the purge window the same on both the internal server and the DMZ server. In this example, the internal server purge window is set to 60 days and the purge window on the DMZ server has been set to 30 days. This type of setting is not recommended.

When you enter the internal Cisco MeetingPlace Web server to review a past meeting between 0 and 60 days, every attachment retrieved except for the Web Recording (synchronized data conferencing [DC] and audio recording) comes directly from the internal server itself. The Web Recording, if the meeting was public, exists only on the DMZ server.

This example makes clear the significance of consistency between the purge parameter settings on both the internal Cisco MeetingPlace Web server and the DMZ Cisco MeetingPlace Web server. In the example, when you enter the internal server and try to retrieve the Web Recording any time between 30 and 60 days, the internal server must go to the DMZ server to retrieve and play back the Web Recording file. However, because the DMZ server is set to purge after 30 days, the synchronized Web Recording file has already been purged. In other words, when you click on the Web Recording, you receive a message that states that the recording is not available. Because of this potential problem, you should use the same setting for the purge parameter on both the internal Cisco MeetingPlace Web server and the DMZ Cisco MeetingPlace Web server.

NetPro Discussion Forums - Featured Conversations

Related Information

• Voice Technology Support
• Voice and IP Communications Product Support
• Recommended Reading: Troubleshooting Cisco IP Telephony
• Technical Support - Cisco Systems