Guest

Cisco Unified MeetingPlace

Release Notes for Cisco MeetingPlace for IP Phone Release 4.2.5.5

  • Viewing Options

  • PDF (190.6 KB)
  • Feedback
Release Notes for Cisco MeetingPlace for Cisco IP Phone Release 4.2.5.5

Table Of Contents

Release Notes for Cisco MeetingPlace for Cisco IP Phone Release 4.2.5.5

Contents

Introduction

System Requirements

Software Requirements

Hardware Requirements

Cisco MeetingPlace Product Compatibility

Cisco MeetingPlace System

Cisco MeetingPlace Gateways

Cisco MeetingPlace Web

Cisco Security Agent

Installation Notes

Cisco CallManager

Cisco MeetingPlace for IP Phone Installation and Cisco CallManager Configuration

Cisco MeetingPlace for IP Phone Installation on a Separate Windows Server

Installing Cisco MeetingPlace for IP Phone on a Separate Windows Server

Cisco MeetingPlace M3 and PCI

Debug Mask Configuration for PCI Platforms

Known Issues

Related Documentation


Release Notes for Cisco MeetingPlace for Cisco IP Phone Release 4.2.5.5


August 5, 2007

This document describes all of the notable fixes, outstanding issues, and features and capabilities for Cisco MeetingPlace for Cisco IP Phone Release 4.2.5.5.


Note In this document, Cisco MeetingPlace for Cisco IP Phone Release 4.2.5.5 is called Release 4.2.5.5.


Contents

Introduction

System Requirements

Cisco MeetingPlace Product Compatibility

Installation Notes

Known Issues

Related Documentation

Introduction

Release 4.2.5 integrates with Cisco CallManager to host meetings for users through the Cisco IP Phone Model 7960.

Once installed and configured, Release 4.2.5.5 enables Cisco IP Phone 7960 users to perform the following tasks:

Schedule immediate or future Cisco MeetingPlace meetings

Attend Cisco MeetingPlace meetings directly

Find today or tomorrow's meetings

Delete meetings scheduled in the future

Request Cisco MeetingPlace to outdial

System Requirements


Note For additional multiserver requirements, see Chapter 3, "Telephony and LAN Planning" in the MeetingServer 5.0 Installation Planning Guide.


Software Requirements

The minimum software requirements for Release 4.2.5.5 are:

Cisco MeetingTime

MeetingTime 5.0 for MeetingServer Release 5.0.0.af

MeetingTime 4.3 for MeetingPlace Release 4.3.0.t

Cisco MeetingPlace IP Gateway software

Release 4.1.3.8 on PCI platforms

Release 4.2.7.6 on M3 platforms

M3 and PCI platforms

MeetingServer Release 5.0.0.af for M3

MeetingPlace Release 4.3.0.t for PCI

Cisco MeetingPlace for IP Phone:

MeetingPlace for IP Phone Release 4.2.5.5

Cisco MeetingPlace Web Conferencing

MeetingPlace Web Release 4.2.5.55

Hardware Requirements

The minimum hardware requirements for Release 4.2.5.5 are:

M3 Platform configured to support VoIP

PCI Platform configured to support VoIP

Windows server with the following minimum requirements:

450 MHz Pentium III

256 MB RAM, 4GB disk space

Windows 2000 with Service Pack 2 installed

Network Interface Card

CD-ROM drive

Microsoft Windows Networking Support

TCP/IP protocol

Cisco CallManager 3.13a with installed Cisco IP Phone 7960 firmware P00303010107


Note To check your Firmware version in Cisco CallManager Administration, choose Device menu > Firmware Load Information. Click the Device Defaults Configuration link to view the load information for your Cisco IP Phone 7960.


Cisco MeetingPlace Product Compatibility

Cisco MeetingPlace System

Release 4.2.5.5 is compatible with:

MeetingServer release 5.0 for M3

MeetingPlace release 4.3 for PCI


Note Release 4.2.5.5 does not support Networked MeetingPlace PCI configurations with Cisco MeetingPlace IP Gateway.


Cisco MeetingPlace Gateways

Cisco MeetingPlace Web Conferencing, Cisco MeetingPlace for IP Phone, Cisco MeetingPlace IP Gateway and the Cisco MeetingPlace for Outlook or E-mail Gateway can be installed on the same Windows 2000 Server with the M3 platform.

Cisco MeetingPlace IP Gateway must be installed on a separate Windows 2000 Server with the PCI platform.


Note If web authentication is configured, then Release 4.2.5.5 must be installed on separate Windows 2000 Server.


Release 4.2.5.5 is compatible with currently shipping gateways, as indicated in the following matrix:

Gateway
Compatible Version

Cisco MeetingPlace IP Gateway

4.1.3.8 (PCI), 4.2.7.6 (M3)

Cisco MeetingPlace Web Conferencing

4.2.5.55 (PCI)

Cisco MeetingPlace E-Mail Gateway

4.2.1.13

Cisco MeetingPlace for Outlook

4.2.5.8


Cisco MeetingPlace Web

Release 4.2.5.5 requires anonymous authentication. If MeetingPlace Web Release 4.2.5.x has been set up to use web authentication, Release 4.2.5.5 must be installed on a separate Windows server with a dedicated Cisco MeetingPlace Web Conferencing installed.

Additionally, if you log on to Release 4.2.5.5 while you are already logged onto a web conference, your web session may become stale. This will happen if Release 4.2.5.5 uses the same Cisco MeetingPlace Web Conferencing (Release 4.2.5) that is used for web conferencing. Your current voice and web conference will be uninterrupted, but you will have to log in again to the interface you want to use.

A workaround to this problem is to install the Cisco MeetingPlace Web Conferencing that is intended for web conferencing on a separate Windows server.

Cisco Security Agent

Release 4.2.5.5 is not compatible with Cisco Security Agent (CSA). We recommend that you do not install Cisco Security Agent on a gateway server where Release 4.2.5.5 is or will be installed.

If Cisco Security Agent is installed on an end-user system, users will see a security alert when they attempt to use the application-sharing feature. Users can choose to proceed with the feature and use application-sharing without difficulty.

Installation Notes

Cisco CallManager

Release 4.2.5.5 is made up of two main components: Cisco IP Phone pages and templates installed on a Windows 2000 server, and a Cisco MeetingPlace service that is configured on a Cisco CallManager server.

For the Call Me softkey on a Cisco IP Phone Model 7960 to outdial users for a current meeting, Cisco CallManager and Cisco IOS gateways must be configured according to a corporate dial plan. See your Cisco CallManager documentation for details.

Release 4.2.5.5 requires administrators to create Cisco CallManager accounts and associate Cisco IP Phones with the user accounts. Administrators also need to configure the Cisco MeetingPlace service and parameters through the Cisco CallManager Administration (ccmadmin) web pages. Once this service is configured, each user must log on to the Cisco IP Phone User Options (ccmuser) web site and subscribe to the Cisco MeetingPlace service.

Cisco MeetingPlace for IP Phone Installation and Cisco CallManager Configuration

Users wishing to access Cisco MeetingPlace through their Cisco IP Phone Model 7960 will need a Cisco CallManager account with an associated Cisco IP Phone, as well as a Cisco MeetingPlace user profile on the Cisco MeetingPlace server they wish to connect to. Each user must subscribe to configured Cisco MeetingPlace phone services. Use the information below to configure these services.

1. The batch file containing the Cisco MeetingPlace for IP Phone components needs to extract the Cisco IP Phone pages and templates to the same folder as Cisco MeetingPlace Web Conferencing if installed on the same Windows 2000 Server. If the Cisco IP Phone pages will be installed on a different Windows 2000 Server, then these pages must be extracted to the root directory of the web server (c:\Inetpub\wwwroot, by default).

2. Add the Cisco MeetingPlace service in Cisco CallManager Administration. The service URL should be http://7960_server/mpweb/scripts/7960mp.asp, where 7960_server is the Windows 2000 Server with the Cisco IP Phone pages.

3. Define the following service parameters for the Cisco MeetingPlace service in Cisco CallManager Administration:

ipphone

username

userpwd

4. Each user must subscribe to the Cisco MeetingPlace service from the Cisco IP Phone User Options (ccmuser) web pages.


Note For additional installation and configuration information, see the System Manager's Guide for Cisco MeetingPlace for Cisco IP Phone Release 4.2.5.


Cisco MeetingPlace for IP Phone Installation on a Separate Windows Server

If you experience performance issues, such as the Cisco IP Phone not responding while requesting information, Release 4.2.5.5 can be installed on a separate Windows server without Cisco MeetingPlace Web Conferencing.

Installing Cisco MeetingPlace for IP Phone on a Separate Windows Server


Step 1 Obtain the home directory of your web server's default web site.

Step 2 From Start > Programs > Administrative Tools, select Internet Services Manager (IIS).

Step 3 From the left panel, right-click on your web server's default web site and select Properties.

Step 4 Select the Home Directory tab.

The Local Path field displays the home directory of this web server's default web site—for example, c:\inetpub\wwwroot.

Step 5 Proceed with the Release 4.2.5.5 installation.

Step 6 When the WinZip Self-Extractor screen displays, enter the home directory obtained in the field provided.

or

Click the Browse button to browse to this directory.

Step 7 Click the Unzip button.

WinZip will create the \mpweb\scripts and \mpweb\template directories in home directory you specified.

WinZip will display a window when the files have been successfully unzipped.


Note You will also need to copy the template files from the \template directory on this Windows server to the Cisco MeetingPlace Web Conferencing server \template directory.


Step 8 Click OK to close this window; then, click the Close button to proceed with the installation.

Step 9 When prompted for your Cisco MeetingPlace Web Conferencing hostname, enter the name of the server where Cisco MeetingPlace Web Conferencing is installed in the field provided (the name of a separate server) and click OK.

Step 10 Follow the prompts to install the Cisco IP Services SDK.

Step 11 This installs the Cisco IP Phone Services ActiveX proxy.

Step 12 After the installation has completed, set the permissions for the mpweb/scripts directory in IIS by right-clicking in IIS on the mpweb/scripts directory and select Properties.

Step 13 The scripts Properties dialog box displays.

Step 14 Ensure that the Execute Permissions parameter is set to Scripts only and click OK.

Cisco MeetingPlace M3 and PCI

The translation table will have to be modified to send a call out either IP ports or T1 ports. This is dependent upon implementation of Cisco MeetingPlace and Cisco equipment.

Debug Mask Configuration for PCI Platforms

For PCI platforms to perform outdials, you must turn on the debug mask on the Cisco MeetingPlace IP Gateway. This can be done by using the registry editor and entering ffffffff (8 f characters) for the debug mask. The location of the debug Mask REG_DWORD is MY Computer\HKLM\SOFTWARE\Latitude\MeetingPlace IP Gateway\General.

Known Issues

The following is a list of known issues and open bugs as of time of Release 4.2.5.5:

Cisco SDK installer is blank when it tries to display current settings (CR16416)

The SDK installer doesn't display any text for the current settings field. Install Shield should display your settings in a window before it begins copying files to the hard drive.

IIS40Helper error message: automation error can't find specified path (CR16417)

The error message reads "Run-time error '-2147024893 (80070003)': Automation error The system cannot find the path specified." This message occurs following CR16416 (Cisco SDK installer is blank when it tries to display current settings).

Self-registration error occurs when trying to uninstall the Cisco SDK installer (CR16422)

The error message reads "One or more files did not properly self-register. The following files did not self-register: 1. C:\WINNT\oleaut32.dll Unspecified error."

Run-time error '-2147024896 (8007003)': occurs during install (CR16362)

The following error message occurs during the installation of the Cisco IP Services SDK. "Run-time error '-2147024893 (80070003)': Automation error The system cannot find the path specified."

Meeting ID field should not allow # and * entries (CR16482)

Meetings scheduled using # and * characters in the meeting ID field cannot be found through MeetingTime or MeetingPlace Web, and cannot be attended using the IP phone.

Related Documentation

For additional information about Cisco MeetingPlace products or about obtaining documentation or technical support, see the Guide to Cisco MeetingPlace Conferencing Documentation and Support at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/conf/mtgplace/roadmap.htm