
3-2
Administrator’s Guide for Cisco MeetingPlace Video Integration Release 5.3
OL-6280-01
Chapter 3 Installing Cisco MeetingPlace Video Integration
Before You Install
•
Release 5.3 of the Cisco MeetingPlace system is up and running, including Cisco MeetingPlace
audio server and Cisco MeetingPlace Web Conferencing.
•
All video endpoints that your organization supports (H.323, SCCP, and ISDN) can successfully
participate in video conferences on the Cisco IPVC MCU. Endpoints must be able to join both by
dialing in and by having the Cisco IPVC MCU call the endpoint.
Verifying your Video-Conferencing License
Make sure your Cisco MeetingPlace system is licensed for Cisco MeetingPlace Video Integration.
The Cisco MeetingPlace MeetingTime utility is fully documented in the
Administrator’s Guide
for
Cisco MeetingPlace Audio Server Release 5.3.
Step 1
In MeetingTime, click the
Configure
tab, then click
System Options
.
Step 2
Click
Query.
Step 3
Click the
>
button until you see
Cisco MeetingPlace Video Integration
.
Step 4
Number of licenses
should be
1
. If it is
0
(zero) contact your Cisco technical support representative. See
the
Guide to Cisco Conferencing Documentation and Support
.
About Configuring the Cisco IPVC MCU to Use Cisco MeetingPlace
Before you configure the Cisco IPVC MCU for Cisco MeetingPlace Video Integration, make sure that
the Cisco IPVC MCU is working independently of Cisco MeetingPlace Video Integration and can host
and manage video conferences.
For detailed information about video-conferencing parameters, see the Cisco IPVC MCU
documentation, including the Release Notes:
Cisco IP/VC 3511 MCU and Cisco IP/VC 3540 MCU
Module Administrator Guide
, Version 3.2 and
Cisco IP/VC 3511 MCU and Cisco IP/VC 3540 MCU
Module Release Notes for Release 3.5
.
All H.323 resources on the Cisco IPVC MCU are dedicated to a single Cisco MeetingPlace service, and
Cisco MeetingPlace controls all H.323 resources on the Cisco IPVC MCU. However, conferences can
be created using SCCP (SKINNY protocol), and Cisco MeetingPlace does not control those conferences.
Cisco IPVC MCU resources will be shared between the Cisco MeetingPlace service and any SCCP
services.
The unique service prefix associated with the Cisco MeetingPlace service will be used to route callers
to the Cisco IPVC MCU and must not conflict with other routing patterns in the gatekeeper or
Cisco CallManager.
The following optional cards for the Cisco IPVC MCU are not supported:
•
Rate Matching card
•
Data Conferencing card
If your Cisco MeetingPlace audio server is configured to use only G.729, make sure the
Cisco IPVC MCU is configured to support G.729. A transcoder card may be needed. For information
about specifying an audio codec, see the online help for the Cisco IPVC MCU.