Release Note
MeetingPlace IP Gateway 4.2.7.6
|
Document
Type |
Release Note |
|
Latitude
Document Number |
0050-0046-01 |
|
Author(s) |
AK |
|
Revision
Date |
2/23/2001 |
|
Print Date |
7/20/2004 |
|
Disposition |
RELEASE |
|
Revision |
A0 |
0050-0046-01 Revision
History
|
Date |
Author |
State |
Rev |
ECN |
Reason for Change |
|
02/20/02 |
AK |
Draft |
1.1 |
|
Initial draft |
|
03/11/02 |
AK |
Update |
1.2 |
|
Team Review |
|
03/12/02 |
AK |
GA |
A0 |
0423 |
General Availability of MeetingPlace IP Gateway 4.2.7.6 |
Table of Contents
1. Overview................................................................................................................................... 4
2. Hardware Compatibility............................................................................................................. 4
3. Software Compatibility.............................................................................................................. 5
3.1 MeetingPlace System......................................................................................................... 5
3.2 MeetingPlace Gateways..................................................................................................... 5
3.2.1.... MeetingPlace
Web................................................................................................. 5
3.3 Cisco CallManager............................................................................................................. 5
3.4 Microsoft NetMeeting.......................................................................................................... 5
4. New Features............................................................................................................................ 6
4.1 Increased Capacity............................................................................................................. 6
5. Configuration Considerations.................................................................................................... 7
5.1 CallManager Configuration................................................................................................... 7
5.2 MeetingServer 5.0 Configuration........................................................................................... 7
Appendix A....................................................................................................................................... 8
A.1 Known Issues.................................................................................................................... 8
This document describes on a high level the issues customers
should be aware of when installing/using MeetingPlace IP (release 4.2.7). MeetingPlace IP is a combination of software and
hardware located on a MeetingPlace conference server, and call control software
known as the MeetingPlace IP Gateway located on a Windows server. MeetingPlace
IP, which is installed onto your existing network, easily integrates with Cisco
CallManager to host meetings for users through Cisco IP and standard PSTN
phones, as well as H.323 devices like Microsoft NetMeeting.
MeetingPlace IP can support up to 384 IP
connections, or an interdependent combination of simultaneous IP and PSTN connections
in a single MeetingPlace meeting.
This product does not
support EISA or PCI hardware platforms.
The minimum hardware requirements for MeetingPlace IP (release 4.2.7) are:
· MeetingPlace M3 conference server with one Smart Blade and one IP Access Blade.
Each IP Access Blade
can handle 48 IP connections. Each T1 Smart Blade can handle 96 PSTN
connections. Physically, IP Access Blades and T1 Smart Blades are identical
cards. Their functionality is based on their configuration.
Note: Since IP Access Blades do not provide conferencing capability, IP telephony requires the pairing of an IP Access Blade with a Smart Blade. Multiple IP connections (over 48 ports) will require one Smart Blade for every two IP Access Blades.
· Cisco CallManager 3.1.x
Note: CallManager 3.0.x supports up to 250 IP connections. You must upgrade to 3.1.x for the full complement of 384 IP connections.
· 11 IP address for a “Fully Loaded” VoIP M3 system
- 1 for the Windows NT or 2000 server running MeetingPlace IP Gateway
- 1 IP address for the system card on the M3 server
- Total of 8 IP addresses for all the IP Access Blades configured for MeetingServer 5.0 (one IP address per IP Access Blade)
Note: For optimal voice quality, it is strongly recommended that all IP Access Blade connections be 100Base-TX.
It is recommended that the latest software or firmware versions be installed.
· MeetingServer 5.0 and MeetingTime 5.0 on an M3 platform
MeetingPlace IP is compatible with currently shipping gateways as indicated in the following matrix. MeetingPlace IP can be installed on the same machine as MeetingPlace Web plus one notification gateway, or as a standalone.
|
Gateway |
Compatible Versions |
|
MeetingPlace Web |
4.2.5 |
|
MeetingPlace E-Mail Gateway |
4.2.1 |
|
MeetingPlace for Outlook |
4.2.5 |
Note: A Windows NT or 2000 server running MeetingPlace IP Gateway has higher requirements than a Windows server running other Gateways.
To enable Web Conferencing on the same Windows NT server as the MeetingPlace IP Gateway, the Windows NT server will have to be configured to bind two different IP addresses to the same LAN interface card. For more information, please refer to the System Manager’s Guide.
MeetingPlace IP can be installed on either the same system as MeetingPlace Web or on a standalone system. If installing on the same system as MeetingPlace Web, you must configure an extra IP address to be obtained by MeetingPlace Web.
MeetingPlace IP has been validated with Cisco CallManager version 3.0.x and above, and 7960 phone sets.
MeetingPlace IP has been validated with Microsoft NetMeeting 3.0.
Please refer to the MeetingPlace IP Gateway System Manager’s Guide (SMG) for full feature descriptions.
MeetingPlace IP Gateway now supports up to 384
Voice over IP (VoIP) user licenses. This is an increase from 24 user licenses
in release 4.1.3.
The following are cursory configuration checklists. Refer to the System Manager’s Guide for detailed instructions on CallManager configuration.
Please add the following in CallManager:
· H.323 gateway (NT or 2000 Server running IP Gateway Software)
· Route pattern (e.g., 5000)
· Point the route pattern to the H.323 gateway you just configured.
Note: CallManager 3.1.x can handle 500
H.323 connections per H.323 gateway.
Note: It is strongly recommended that you upgrade to CallManager 3.1.x. Load testing has revealed that only 250 IP connections can be made with CallManager 3.0.x. CallManager 3.1.x can handle 384 IP connections.
Please use the blade command interactively. MeetingServer 5.0 can be configured as a mixed environment or a pure IP or pure PSTN environment. Each IP Access Blade requires an IP address and handles 48 IP connections. Each T1 Smart Blade can handle 96 PSTN connections. A maximum VoIP configuration contains 384 IP ports and requires a total of nine IP addresses. A maximum PSTN configuration contains 1152 PSTN ports and requires only one IP address.
Note: For detailed information on how to configure Smart Blades, refer to the MeetingServer 5.0 Customer Engineer Guide.
|
CR16144 |
If CallManager loses LAN connectivity MP doesn’t release ports After 24 hours, hung IP ports will be released if they are not part of a continuous meeting. Restarting the IP Gateway will release all hung IP ports. |
|
CR16149 |
Unplugging and replugging IP ethernet cable, link doesn't always come back up You may want to do this kind of operation while the system
is not running. Also, once the system is rebooted with the cable plugged in,
the link always comes up normally. This is also caused if the switch is down
and/or the cable is physically removed. |
|
CR16159 |
Port Utilization
doesn't report IP ports |
|
CR15410 |
IP ports aren't
listed in MeetingTime but are listed in MeetingPlace |
|
CR15780 |
IRC not responding,
rtpRecvDirect deadlock |
|
CR16186 |
Echo effect Improper use of Plantronic headset on 7960 IP phone, or setting the volume on the 7960 phone to maximum, can cause echo effect. |
|
CR16281 |
Poor voice quality
on NetMeeting. This is a limitation of NetMeeting. |