Guest

Cisco Unified MeetingPlace

MeetingPlace Server PCI Onsite Merge

Document ID: 60127

Updated: Jul 07, 2005

   Print

Introduction

Cisco MeetingPlace provides a fully integrated rich-media conferencing solution, including voice and web conferencing capabilities. Cisco MeetingPlace resides on network, behind the PIX Firewall on internal voice and data network, and offers unmatched security, reliability, scalability, application integration and cost efficiency.

This document outlines verification procedures to use before you go on site, before you start onsite work, and after you have completed any Cisco MeetingPlace Server PCI Merge onsite work.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on the Cisco MeetingPlace Audio Server (PCI).

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.

Items to Verify Before You Go on Site

Pre-Merge

Complete these steps:

  1. Have a laptop with a nine-pin null modem female-to-female cable to connect to the front service port on the front of the Cisco MeetingPlace server.

  2. Verify that the HyperTerminal on your laptop works.

  3. Have a copy of the MeetingPlace Server Merge Procedure and the Installation and Upgrade Guide for Cisco Unified MeetingPlace Audio Server 6.x available.

  4. Check all applicable Field Notices and Release Notes, and check the Release Notes for Cisco Unified MeetingPlace Audio Server Release 6.0 in order to verify software compatibility.

  5. If you plan to upgrade the Cisco MeetingPlace standalone server, make sure you have the necessary software.

  6. Have a copy of the Customer Engineer Guide.

  7. Have the superuser password of the day.

Network Server

Complete these steps:

  1. Verify you have the correct licenses needed to handle the increased capacity after you merge the Cisco MeetingPlace standalone server.

  2. Verify that the new T1 lines are ready.

  3. If you need to upgrade the Cisco MeetingPlace Networked System before the merge, refer to the Installation and Upgrade Guide for Cisco Unified MeetingPlace Audio Server 6.x and perform the activities described in that document.

Standalone Server

Complete these steps:

  1. If you upgrade the standalone server to the same Cisco MeetingPlace server version as on the Cisco MeetingPlace network server, refer to the Installation and Upgrade Guide for Cisco Unified MeetingPlace Audio Server 6.x and bring it along.

  2. If there are gateways attached to the standalone server, decide what to do with them in the Cisco MeetingPlace Networked System environment.

Items to Verify Before You Start Onsite Work

Pre-Merge Tasks

Complete these steps:

  1. Back up the databases on the Cisco MeetingPlace Networked System and standalone server.

  2. Capture and save your HyperTerminal session.

Items to Verify After Onsite Work

Post-Merge Tasks

Complete these steps:

  1. Check whether any Major or Minor alarms have been generated.

  2. Check the date and time set on the system.

  3. Use Cisco MeetingTime to log in.

Verify LAN Connectivity for Networked System

Complete these steps:

  1. From the Cisco MeetingPlace network server, issue the gwstatus and swstatus commands to verify that all software has a status of up and that all conference servers and the shadow server have a status of OK and a run level of UP.

  2. Remote login (rlogin) to each conference server and issue the swstatus command to verify that all software has been updated with the correct version and has a status of up.

  3. Remote login (rlogin) to the shadow server and issue the swstatus command to verify that all software has a status of up.

Verify Telephony on the Merged Cisco MeetingPlace Conference Servers

Complete these steps:

  1. From the Command-Line Interface (CLI), issue the spanstat -s command and verify that the T1 lines are up.

  2. From the CLI, issue the spanstat -all command and verify that all ports are idle.

  3. Issue the activity CLI command and choose option 4 to place a test call.

  4. Call in to Cisco MeetingPlace to verify that you can schedule and attend a meeting.

    1. Check that the "Welcome to MeetingPlace" greeting plays in the correct language.

    2. Log in as a profile user (for example, profile 0002 – technician).

    3. Schedule and attend an immediate meeting.

    4. Have at least two parties in a call, and verify that they can hear one another clearly.

  5. Check all in-session features (roll call, breakout session, outdial, and so forth) that are relevant to your customer.

    Note: Enter spanstat help in order to determine the character code definitions and sequences for the various types of connections.

Cisco MeetingTime Configuration for Merged Server

Verify that these Cisco MeetingTime settings are correct:

  • On the Configure tab:

    • Telephony access

    • System options (license keys)

    • Server configuration:

      • Conference ports

      • Floater ports

      • Overbook ports

      • Recording space

    • Other Cisco MeetingPlace servers

Verify Remote Access

Verify that you can use your modem line to dial in to the Cisco MeetingPlace network server (and the conference servers and shadow server, if applicable).

Note: Ensure that the Cisco Unified MeetingPlace Audio Server system resides on a network segment that is free from potential network problems, such as storms, loops, and collisions.

Related Information

Updated: Jul 07, 2005
Document ID: 60127