Table Of Contents
Release Notes for Cisco MeetingPlace for Cisco IP Phone Release 4.2.5.5
Cisco MeetingPlace Product Compatibility
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
Debug Mask Configuration for PCI Platforms
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
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:
•
•
•
•
•
System Requirements
Note
Software Requirements
The minimum software requirements for Release 4.2.5.5 are:
Cisco MeetingTime
•
•
Cisco MeetingPlace IP Gateway software
•
•
M3 and PCI platforms
•
•
Cisco MeetingPlace for IP Phone:
•
Cisco MeetingPlace Web Conferencing
•
Hardware Requirements
The minimum hardware requirements for Release 4.2.5.5 are:
•
•
•
–
–
–
–
–
–
–
•
Note
Cisco MeetingPlace Product Compatibility
Cisco MeetingPlace System
Release 4.2.5.5 is compatible with:
•
•
Note
Cisco MeetingPlace Gateways
•
•
Note
Release 4.2.5.5 is compatible with currently shipping gateways, as indicated in the following matrix:
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.
2.
3.
•
•
•
4.
Note
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
Step 2
Step 3
Step 4
The Local Path field displays the home directory of this web server's default web site—for example, c:\inetpub\wwwroot.
Step 5
Step 6
or
Click the Browse button to browse to this directory.
Step 7
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
Step 8
Step 9
Step 10
Step 11
Step 12
Step 13
Step 14
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:
•
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.
•
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).
•
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."
•
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."
•
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
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Guest
