Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 526-4100
Text Part Number: OL-6280-01
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL
STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
CCSP, the Cisco Square Bridge logo, Cisco Unity, Follow Me Browsing, FormShare, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work,
Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco,
the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation,
Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net
Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing,
ProConnect, RateMUX, Registrar, ScriptShare, SlideCast, SMARTnet, StrataView Plus, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient,
TransPath, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship
between Cisco and any other company. (0406R)
Administrator’s Guide for Cisco MeetingPlace Video Integration Release 5.3
1Introducing Cisco MeetingPlace Video Integration Release 5.31-1
Audience1-1
Scope1-1
Naming Conventions Used in This Guide1-2
Overview of Cisco MeetingPlace Video Integration1-2
Features and Benefits of Cisco MeetingPlace Video Integration1-3
Additional References1-4
2Cisco MeetingPlace Video Integration Components and Process2-1
Overview of Components2-1
Supported Cisco MeetingPlace System Configurations2-4
About the Cisco MeetingPlace Video-Conferencing Process2-4
How Video Conferences Are Scheduled2-5
How Video Conferences Start2-6
How Video Conferences Run2-8
About Displaying the Status and Options of Video Participants in the Meeting Room2-8
How Cisco MeetingPlace Video Integration Tracks Port Availability2-8
How Video Conferences End 2-9
CHAPTER
OL-6280-01
3Installing Cisco MeetingPlace Video Integration3-1
Before You Install 3-1
Making Sure Component Systems Are Up and Running3-1
Verifying your Video-Conferencing License 3-2
About Configuring the Cisco IPVC MCU to Use Cisco MeetingPlace3-2
Configuring the Cisco MeetingPlace Audio Server3-11
Configuring Cisco MeetingPlace H.323/SIP IP Gateway3-12
Configuring Load-Balancing Configurations for Video Conferencing3-12
About Installing and Configuring Video Endpoints3-13
(Optional) Configuring Cisco MeetingPlace for Outlook3-14
(Optional) Configuring Cisco MeetingPlace for Lotus Notes3-14
Configuring Cisco CallManager3-14
Preparing to Install the Video Integration with DMZ Configurations3-17
Gathering Installation Values3-18
Installing Cisco MeetingPlace Video Integration3-18
Administrator’s Guide for Cisco MeetingPlace Video Integration Release 5.3
i
Contents
Uninstalling Cisco MeetingPlace Video Integration3-19
CHAPTER
CHAPTER
4Configuring and Managing Cisco MeetingPlace Video Integration4-1
About the Cisco MeetingPlace MeetingTime Software Application4-1
About Video-Conferencing Access Information4-1
About Changing System Configuration Settings4-2
Changing Values Entered During Installation of Cisco MeetingPlace Video Integration4-3
Changing Settings in Other Components4-3
About Managing Video-Conferencing Resources4-4
About Configuring Port Parameters4-7
About Managing User Profiles for Video Use4-10
Important Information About DMZ Configurations and Video Conferencing4-12
About Video-Conferencing Bandwidth4-12
Specifying User and Group Profile Information4-13
About Video-Conferencing Statistics 4-13
Viewing Video-Conferencing Statistics4-14
5Using Cisco MeetingPlace Video Conferencing5-1
Supported Meeting Types5-1
About Setting Up End Users for Video Conferencing in Cisco MeetingPlace5-2
About Scheduling Video Conferences5-3
Who Can Schedule Video Conferences5-3
When Video Conferences Can Be Scheduled5-3
How Users Schedule Video Conferences5-3
About Rescheduling Video Conferences 5-4
About Attending Cisco MeetingPlace Video Conferences5-4
How Users Join A Cisco MeetingPlace Video Conference5-5
Video Features and Functions in the Meeting Room During the Conference 5-7
About Modifying the Video Transmission5-8
About Modifying the Video Transmission of Other Participants5-9
About Recording a Video-Conferencing Session5-9
About Entering a Breakout Session5-9
About Participating in Lecture Style Meetings5-9
About Extending a Video Conference5-10
About Leaving a Video Conference5-10
About Ending a Video Conference5-10
Information for End Users5-10
Administrator’s Guide for Cisco MeetingPlace Video Integration Release 5.3
ii
OL-6280-01
Contents
CHAPTER
I
NDEX
6Troubleshooting 6-1
Viewing the Eventlog6-1
Setting the Level of Logging Detail6-1
General Troubleshooting Guidelines6-2
Problems Configuring and Initiating Cisco MeetingPlace Video Integration6-2
Problems Scheduling a Video Conference6-5
Problems Joining a Video Conference 6-5
Problems During a Video Conference6-7
OL-6280-01
Administrator’s Guide for Cisco MeetingPlace Video Integration Release 5.3
iii
Contents
iv
Administrator’s Guide for Cisco MeetingPlace Video Integration Release 5.3
OL-6280-01
CHAPTER
Introducing
Cisco MeetingPlace Video Integration
Release 5.3
Administrator’s Guide for Cisco MeetingPlace Video Integration Release 5.3 describes
Cisco MeetingPlace Video Integration.
This chapter contains the following topics:
• Audience, page 1-1
• Scope, page 1-1
• Naming Conventions Used in This Guide, page 1-2
• Overview of Cisco MeetingPlace Video Integration, page 1-2
• Features and Benefits of Cisco MeetingPlace Video Integration, page 1-3
1
Audience
Scope
• Additional References, page 1-4
This guide is intended for Cisco MeetingPlace system administrators who are familiar with the following
products, which are prerequisites for Cisco MeetingPlace Video Integration:
• Cisco MeetingPlace 8100 Series servers and the Cisco MeetingPlace MeetingTime software
application
• Cisco MeetingPlace Web Conferencing
• Other Cisco MeetingPlace integration products that are part of the Cisco MeetingPlace system
• Cisco CallManager (if your environment includes this product)
• Cisco IPVC MCU 3.5plus and its required components
This guide describes how to install, configure, manage, and troubleshoot the
Cisco MeetingPlace Video Integration. This guide does not describe in detail how to set up
Cisco MeetingPlace audio and web conferencing, nor does it describe how to set up or configure the
Cisco IPVC MCU or any of its components, including H.323 gatekeepers, video endpoints, or gateways.
OL-6280-01
Administrator’s Guide for Cisco MeetingPlace Video Integration Release 5.3
1-1
Chapter 1 Introducing Cisco MeetingPlace Video Integration Release 5.3
Naming Conventions Used in This Guide
This guide also does not describe in detail how to configure Cisco CallManager. Cisco IPVC video
conferencing, Cisco CallManager, and Cisco MeetingPlace audio and web-conferencing systems must
be up and running before you install Cisco MeetingPlace Video Integration.
For information on any of the preceding systems, see the documents listed in Additional References,
page 1-4.
Naming Conventions Used in This Guide
The following products and components appear frequently in this guide.
Official Name Abbreviation
Cisco MeetingPlace 8100 Series server with
Cisco MeetingPlace Audio Server Release 5.3
software
Cisco MeetingPlace for Lotus Notes Release 5.3Cisco MeetingPlace for Lotus Notes
Cisco MeetingPlace for Outlook Release 5.3 Cisco MeetingPlace for Outlook
Cisco IPVC MCU 3.5plusCisco IPVC MCU
Cisco MeetingPlace audio server
Cisco MeetingPlace Web Conferencing
Overview of Cisco MeetingPlace Video Integration
Cisco MeetingPlace Video Integration is a separately-licensed add-on to Cisco MeetingPlace
conferencing that integrates the voice and web-conferencing capabilities of Cisco MeetingPlace with the
video-conferencing functionality provided by the Cisco IPVC Multipoint Control Unit (MCU). Voice,
web, and video conference participants interact seamlessly in a single rich-media conference.
The visual channel of the video-conferencing medium is handled entirely by the Cisco IPVC MCU and
runs parallel to the voice and web conference. All media (video, voice, and data) are linked but
independent, so that each stream maintains its full feature set and functional richness.
The following steps provide a simplified overview of how the Cisco MeetingPlace Video Integration
solution works (in a system that includes e-mail notifications):
1. You set up user profiles in Cisco MeetingPlace that control who can schedule video conferences.
2. Users whose profile authorizes them to schedule video conferences submit a single
Cisco MeetingPlace form to schedule a meeting that includes video, voice, and web-conferencing
functionality. Users can require passwords, or specify that only profiled or invited users can attend.
3. Cisco MeetingPlace keeps track of available conferencing resources, including resources available
on the Cisco MeetingPlace audio server and video resources on the Cisco IPVC MCU. If there are
sufficient resources on both systems to accommodate a scheduler’s request, Cisco MeetingPlace
schedules the meeting and sends notifications to the invitees. These notifications include the
information participants need in order to access all conference media.
1-2
Administrator’s Guide for Cisco MeetingPlace Video Integration Release 5.3
OL-6280-01
Chapter 1 Introducing Cisco MeetingPlace Video Integration Release 5.3
4. At the scheduled meeting time, invitees use the information in the meeting notification to join each
aspect of the conference: the Cisco MeetingPlace web and voice conferences and the video
conference hosted on the Cisco IPVC MCU. Video participants attend the video aspect of the
conference via a room-based video system or via IP video cameras on their desktop, such as
Cisco VT Advantage. Participants can join the different media using any of several methods.
5. Cisco MeetingPlace initiates the voice conference on the Cisco MeetingPlace system and the video
conference on the Cisco IPVC MCU, and establishes the link that joins the audio of the video
conference with the audio of the voice conference.
6. After participants are in the integrated conference, audio-only and video participants can converse
seamlessly with each other. Video participants can control their audio and video transmission and
display from within the Cisco MeetingPlace web-conferencing meeting room.
7. If the conference needs to continue past the time it was scheduled to end, Cisco MeetingPlace
evaluates whether conferencing resources are available on both the Cisco MeetingPlace audio server
and on the Cisco IPVC MCU, then determines whether the conference can be extended.
Video conferences can also be added to an existing Cisco MeetingPlace conference on an ad-hoc basis,
if resources are available.
For details about the end user experience and process for using Cisco MeetingPlace Video Integration,
see Chapter 5, “Using Cisco MeetingPlace Video Conferencing” and Chapter 2,
“Cisco MeetingPlace Video Integration Components and Process.”
Features and Benefits of Cisco MeetingPlace Video Integration
Features and Benefits of Cisco MeetingPlace Video Integration
Cisco MeetingPlace Video Integration offers the following features:
• Enhances meeting effectiveness by bringing together multiple media to create a rich-media
conferencing environment.
• Offers a solution that integrates readily into existing networks and IP infrastructure.
• Includes tools to manage video-conferencing resources for optimal availability.
• Simplifies the processes of scheduling, distributing notifications, attending, and participating in
multiple media for end users.
• Leverages the existing video-conferencing capability of the Cisco IPVC MCU and networking and
telephony infrastructure, such as Cisco CallManager, to provide a complete and unified multipoint
conferencing solution for Cisco customers.
• Extends important resource management tools from Cisco MeetingPlace to the Cisco IPVC MCU,
allowing you to plan, allocate, and measure resource use, and thus to maximize the utility of
video-conferencing resources.
• Resource management features include the following:
–
The ability to schedule video-conferencing resources in advance. Cisco MeetingPlace manages
the scheduling of video-conferencing resources on the Cisco IPVC MCU, which does not have
built-in scheduling functionality.
–
Floater and overbook ports to optimize port availability and minimize waste of conference ports.
This increases the availability of conference ports for ad-hoc video conferences.
–
User profiles to limit use of conferencing resources to designated meeting schedulers and
groups.
OL-6280-01
–
Statistics on video usage that are included in standard Cisco MeetingPlace reports, so you can
easily evaluate needs and manage all resources.
Administrator’s Guide for Cisco MeetingPlace Video Integration Release 5.3
1-3
Additional References
• Ease-of-use features that simplify the rich-media conferencing process for users include the
following:
–
Unified scheduling, which allows users to coordinate all conferencing resources from a single
point. Scheduling is done through familiar desktop applications such as Microsoft Outlook,
Lotus Notes, or a web browser.
–
Notifications for each meeting that include the links and instructions to access all conference
media for that meeting.
–
Users can initiate or join a video conference on an ad-hoc basis, as long as video-conferencing
resources are available.
–
Preference information in user profiles, which automates parts of the attend process.
–
Video controls in the Cisco MeetingPlace web-conferencing meeting room, which allow users
to control all aspects of their conferencing experience from a single interface.
Additional References
Cisco MeetingPlace products
Guide to Cisco Conferencing Documentation and Support
Chapter 1 Introducing Cisco MeetingPlace Video Integration Release 5.3
Administrator’s Guide for Cisco MeetingPlace Video Integration Release 5.3
1-5
Additional References
Chapter 1 Introducing Cisco MeetingPlace Video Integration Release 5.3
1-6
Administrator’s Guide for Cisco MeetingPlace Video Integration Release 5.3
OL-6280-01
Cisco MeetingPlace Video Integration
Components and Process
This chapter describes the components that are required for the Cisco MeetingPlace Video Integration
solution:
• Overview of Components, page 2-1
• Supported Cisco MeetingPlace System Configurations, page 2-4
• About the Cisco MeetingPlace Video-Conferencing Process, page 2-4
Overview of Components
The components shown in Figure 2-1 and described in Tab l e 2-1 work together to provide video
conferences that are integrated with Cisco MeetingPlace voice and web conferences.
In the Cisco MeetingPlace Video Integration solution, Cisco MeetingPlace components provide audio
conferencing and web conferencing data collaboration, and the Cisco IPVC MCU and its associated
components provide video conferencing. Cisco MeetingPlace Video Integration integrates the two
solutions to provide integrated voice, data, and video conferencing.
CHAPTER
2
OL-6280-01
Administrator’s Guide for Cisco MeetingPlace Video Integration Release 5.3
2-1
Overview of Components
Figure 2-1
Cisco
MeetingPlace
audio server
Chapter 2 Cisco MeetingPlace Video Integration Components and Process
Cisco
IP/VC MCU
RTP
XML
Cisco MeetingPlace
Web Conferencing
Cisco MeetingPlace
Video Integration
Cisco MeetingPlace
for Outlook (optional)
MM
Cisco MeetingPlace
H.323/SIP IP Gateway
PSTN
Phone
Table 2-1Components Needed to Integrate Video Conferencing in Cisco MeetingPlace
IP
Cisco
IP Phone
Cisco
CallManager
M
M
SCCP
video
endpoint
M
IP
Cisco
VT Advantage
video endpoint
Cisco
IOS H.323
Gatekeeper
H.320
video
endpoint
Cisco
IP/VC
PRI
Gateway
H.323
video
endpoint
H.323
video
endpoint
92342
2-2
ComponentFunctions
Cisco MeetingPlace
audio server
• Handles the audio conference.
• Schedules the video conference port resources for the Cisco IPVC MCU.
• Sets the parameters that are interpreted by
Cisco MeetingPlace Video Integration, which uses these parameters to
control conference resources.
Cisco MeetingPlace
H.323/SIP IP
Gateways
• Allows the Cisco MeetingPlace system to communicate with IP telephony
devices.
• Connects the Cisco MeetingPlace audio server to the network and to
Cisco CallManager or the H.323 gatekeeper.
• Establishes the link between the Cisco MeetingPlace audio server and the
Cisco IPVC MCU to enable video and audio participants to hear and speak
to each other.
Administrator’s Guide for Cisco MeetingPlace Video Integration Release 5.3
OL-6280-01
Chapter 2 Cisco MeetingPlace Video Integration Components and Process
Table 2-1Components Needed to Integrate Video Conferencing in Cisco MeetingPlace (continued)
ComponentFunctions
Cisco MeetingPlace
Web Conferencing
• Displays a user interface to schedule and attend meetings.
• Displays video participant status.
• Provides the web-conferencing meeting room from which users can join
and control video conferences.
• Includes components that enable the Cisco MeetingPlace audio server to
communicate with Cisco MeetingPlace Video Integration.
Cisco MeetingPlace
for Outlook
(Optional)
Cisco MeetingPlace
for Lotus Notes
• Presents a convenient scheduling interface to end users.
• Provides meeting notifications that offer users two ways to “click to attend”
video, voice, and web conferences.
• Schedule and attend Cisco MeetingPlace meetings that include video
directly from the Lotus Notes environment.
(Optional)
Cisco IPVC MCU
• Processes the video streams to provide the video capability of the system.
Overview of Components
H.323 gatekeeper
Cisco IPVC PRI
Gateway (Optional)
Cisco MeetingPlace
Video Integration
• Communicates with the video endpoints.
• Routes calls between the video endpoints and the Cisco IPVC MCU, based
on the number dialed.
• Handles the IP protocol signaling.
• Enables H.320 video endpoints to participate in video conferences on the
Cisco IPVC MCU.
• Monitors the configuration of the Cisco IPVC MCU and passes current
status to the Cisco MeetingPlace audio server.
• Authorizes the Cisco IPVC MCU to create and initiate video conferences.
• Initiates the creation of the audio channel between the Cisco IPVC MCU
and the Cisco MeetingPlace audio server.
• Passes information between the Cisco MeetingPlace audio server and the
Cisco IPVC MCU.
• Coordinates capacity by transmitting meeting scheduling, initiation, and
termination information between the various components.
• Controls the behavior of the Cisco IPVC MCU based on meeting type and
requests placed via the Cisco MeetingPlace web-conferencing meeting
room.
• Controls entry of participants into video conferences, based on the number
of video ports scheduled on the Cisco MeetingPlace audio server for the
conference, plus available video floater and video overbook ports, if any.
• Tells the Cisco IPVC MCU when to terminate conferences.
OL-6280-01
• Keeps track of information for all conference participants in the
Cisco IPVC MCU and their corresponding participant IDs assigned by the
Cisco MeetingPlace audio server.
• Monitors the link between the Cisco MeetingPlace audio server and the
Cisco IPVC MCU and supports recovery if the connection is lost.
Administrator’s Guide for Cisco MeetingPlace Video Integration Release 5.3
2-3
Chapter 2 Cisco MeetingPlace Video Integration Components and Process
Supported Cisco MeetingPlace System Configurations
Table 2-1Components Needed to Integrate Video Conferencing in Cisco MeetingPlace (continued)
ComponentFunctions
Video endpoints
Cisco CallManager
(Optional)
• Capture and transmit video images and audio from each user or location.
• Receive and display video images and audio from other video-conference
participants to the user or location.
On networks configured with Cisco CallManager:
• Allows SCCP endpoints to participate in Cisco MeetingPlace conferences.
• Routes traffic.
Supported Cisco MeetingPlace System Configurations
Supported Cisco MeetingPlace system configurations include the following. Complete system
requirements and a Cisco MeetingPlace version compatibility matrix are in the Release Note for
Cisco MeetingPlace Video Integration Release 5.3:
• One Cisco MeetingPlace 8100 series server.
• One or more Cisco MeetingPlace H.323/SIP IP Gateway servers.
• Cisco MeetingPlace Web Conferencing servers in any configuration that is supported in
Release 5.3. However, Cisco MeetingPlace Video Integration can be installed only on a single
Cisco MeetingPlace web-conferencing server.
• Cisco MeetingPlace Video Integration installed on a Cisco MeetingPlace web-conferencing server.
If your system has a DMZ configuration, see Preparing to Install the Video Integration with DMZ
Configurations, page 3-17 for important considerations before installing
Cisco MeetingPlace Video Integration. A DMZ configuration includes one or more servers in a
DMZ outside the corporate firewall.
The following additional components are also supported:
• One Cisco IPVC MCU with all components including an H.323 gatekeeper.
• (Optional) Cisco CallManager.
About the Cisco MeetingPlace Video-Conferencing Process
2-4
The process of creating, running, and terminating an integrated video, audio, and web conference is
described in this section.
Participants who are using audio-only devices connect to the Cisco MeetingPlace audio server.
Participants with video equipment connect to the Cisco IPVC MCU, which processes both the video and
the audio channel of the video endpoints. Cisco MeetingPlace Video Integration mixes the audio streams
from both systems to allow all participants to hear and speak to each other. Figure 2-2 shows this process.
Administrator’s Guide for Cisco MeetingPlace Video Integration Release 5.3
OL-6280-01
Chapter 2 Cisco MeetingPlace Video Integration Components and Process
Figure 2-2
Cisco
IP Phone
Cisco
IP Phone
Cisco
IP Phone
IP
IP
IP
1
MeetingPlace
audio server
6
Cisco
About the Cisco MeetingPlace Video-Conferencing Process
Video
endpoint
Cisco
IP/VC
MCU
2
5
3
Video
endpoint
Video
endpoint
4
Video
endpoint
92341
1The audio of the telephone participants is
processed by the Cisco MeetingPlace audio
server.
2The audio channels from telephone
participants are sent to join the audio on the
Cisco IPVC MCU.
3Video participants hear the audio from
telephone participants.
How Video Conferences Are Scheduled
A user fills in a standard Cisco MeetingPlace conference scheduling form in Microsoft Outlook, Lotus
Notes, Cisco MeetingPlace Web Conferencing, or MeetingTime; then the user submits that form to
Cisco MeetingPlace audio server. If the user has indicated that the conference will include video
participants, the Cisco MeetingPlace audio server verifies that resources are available, and if so,
schedules the requested number of video ports and (depending on system configuration) notifies
invitees.
About the Minimum Number of Video Ports Scheduled
In order to prevent more video conferences from being scheduled than the Cisco IPVC MCU can support
at one time, Cisco MeetingPlace may schedule more video ports than the meeting scheduler specifies for
a conference. The minimum number of ports that Cisco MeetingPlace schedules for each conference is
determined by the formula [(Total number of video conference ports - Number of video floater ports +
Number of video overbook ports)/ Total number of video conferences available]. If a user does not
schedule fewer ports than the number of ports resulting from this calculation, Cisco MeetingPlace
schedules the number of ports that the scheduler specifies. Floater and overbook ports are defined in
About Configuring Port Parameters, page 4-7.
4The audio and video channels of the video
endpoints are processed by the
Cisco IPVC MCU.
5The audio channels of the video endpoints are
sent to join the audio in Cisco MeetingPlace
audio conferencing.
6Telephone participants hear the audio from
video endpoints.
OL-6280-01
Administrator’s Guide for Cisco MeetingPlace Video Integration Release 5.3
2-5
About the Cisco MeetingPlace Video-Conferencing Process
How Video Conferences Start
The Cisco IPVC MCU is configured to allow Cisco MeetingPlace Video Integration to control all H.323
video-conferencing resources and meeting operations on the Cisco IPVC MCU, including initiating
meetings. Cisco MeetingPlace does not control SCCP resources on the Cisco IPVC MCU.
Before a video conference can be started on the Cisco IPVC MCU, a Cisco MeetingPlace meeting must
exist on the Cisco MeetingPlace audio server. However, the meeting does not need to be scheduled in
advance; it can be scheduled as an immediate or reservationless meeting, as long as video ports and video
conferences are available at the time of the request.
The first Cisco MeetingPlace conference participant who joins the video conference initiates the creation
of the video conference on the Cisco IPVC MCU. Cisco MeetingPlace Video Integration verifies that
the conference is currently in session or within the guard times of the existing meeting, then tells the
Cisco IPVC MCU to immediately create a video conference with the Meeting ID.
The Meeting ID for the video conference includes the MeetingPlace service prefix that identifies
Cisco MeetingPlace conferences on the Cisco IPVC MCU, plus the standard Cisco MeetingPlace
Meeting ID for that conference. This Meeting ID is used by the gatekeeper or Cisco CallManager to
route incoming calls for this conference over the network to the Cisco IPVC MCU.
Conferences cannot be created by dialing in to the Cisco IPVC MCU unless the meeting has been
scheduled on Cisco MeetingPlace audio server. If a participant dials in to the Cisco IPVC MCU to start
a conference, the Cisco IPVC MCU sends information about the new video conference to
Cisco MeetingPlace Video Integration. If the conference has not been scheduled in Cisco MeetingPlace,
is not currently in session, or is outside the guard times of a scheduled meeting,
Cisco MeetingPlace Video Integration tells the Cisco IPVC MCU not to create the conference.
Chapter 2 Cisco MeetingPlace Video Integration Components and Process
How the Link Between the Cisco IPVC MCU and the Cisco MeetingPlace Audio Server Is
Established
When the first video participant joins an authorized video conference, either by outdialing from the
Cisco MeetingPlace Web Conferencing meeting room or by dialing in to the Cisco IPVC MCU,
Cisco MeetingPlace creates the link that connects the audio channel of the video conference and the
audio channel of the Cisco MeetingPlace audio server.
To initiate this link, Cisco MeetingPlace Video Integration tells the Cisco MeetingPlace audio server to
outdial to the Cisco IPVC MCU; the call is routed through the
Cisco MeetingPlace H.323/SIP IP Gateway to Cisco CallManager or to the H.323 gatekeeper, either of
which has been configured to route the call to the Cisco IPVC MCU. Either the gatekeeper or the
Cisco IPVC MCU can route the call to the correct conference. The routing pattern (outdialed number)
for this transaction is composed of the service prefix that identifies Cisco MeetingPlace conferences on
the Cisco IPVC MCU (and also is unique among the routing patterns configured on the gatekeeper and
CallManager) plus the Cisco MeetingPlace Meeting ID of the conference.
Cisco MeetingPlace Video Integration tries three times to establish this link.
After the link is established, the entire audio channel of the video conference on the Cisco IPVC MCU
becomes a participant in the Cisco MeetingPlace audio conference and vice versa.
NoteThe video link appears as a named participant in the in-session tab in MeetingTime, but not in the
Cisco MeetingPlace web-conferencing meeting room. It also is included in some reports, but not all. See
About Video-Conferencing Statistics, page 4-13.
2-6
Administrator’s Guide for Cisco MeetingPlace Video Integration Release 5.3
OL-6280-01
Chapter 2 Cisco MeetingPlace Video Integration Components and Process
About the Cisco MeetingPlace Video-Conferencing Process
After the link is established, all further communication between the Cisco IPVC MCU and the
Cisco MeetingPlace audio server is handled through the Cisco MeetingPlace Video Integration
component, which communicates with the Cisco MeetingPlace audio server through MPAgent.
MPAgent is a component of Cisco MeetingPlace Web Conferencing, which is a prerequisite to
installation of Cisco MeetingPlace Video Integration. Cisco MeetingPlace Video Integration
communicates with the Cisco IPVC MCU using proprietary XML messaging.
If the link between Cisco MeetingPlace and the Cisco IPVC MCU is disconnected,
Cisco MeetingPlace Video Integration attempts to reestablish it three times, checking every minute, or
when another participant joins the conference.
How Video Conference Participants Join Meetings
There are several ways additional participants can join the video conference. The process of adding
participants to the conference depends on how they enter the meeting.
If a Participant Joins a Scheduled Video Conference by Outdialing From the Cisco MeetingPlace Web Conferencing Meeting
Room
When a participant clicks Connect from within Cisco MeetingPlace Web Conferencing, or in a calendar
entry in Cisco MeetingPlace for Lotus Notes, or in the MeetingPlace tab of a meeting notification in
Cisco MeetingPlace for Outlook, Cisco MeetingPlace Video Integration sends a message to the
Cisco IPVC MCU to outdial to the endpoint of the participant. When the participant has successfully
joined the video conference, the Cisco IPVC MCU notifies Cisco MeetingPlace Video Integration, and
the status of the participant is recorded in the participant list that is displayed in the meeting room of
Cisco MeetingPlace Web Conferencing.
If a Participant Joins a Scheduled Video Conference by Dialing in to the Cisco IPVC MCU
Participants dial in to the conference from their video endpoint by using the number provided in the
Connect dialog box in the Cisco MeetingPlace web-conferencing meeting room. This number is the
service prefix on the Cisco IPVC MCU that identifies Cisco MeetingPlace conferences, plus the
Cisco MeetingPlace Meeting ID. Cisco CallManager or the gatekeeper routes all incoming H.323 calls
that begin with the specified service prefix to the Cisco IPVC MCU, which routes each call to the correct
video conference based on the Cisco MeetingPlace meeting ID number portion of the number that was
dialed.
When participants attempt to join the video conference by dialing in from their video endpoint, the
Cisco IPVC MCU accepts the call only if the conference is not restricted to profiled or invited users and
does not require a password. (This is because the Cisco IPVC MCU cannot authenticate dial-in
participants.) If the participant is granted access, the Cisco IPVC MCU checks with
Cisco MeetingPlace Video Integration to see if the meeting is in session and within the guard times. If
so, the Cisco IPVC MCU admits the participant to the video conference and notifies
Cisco MeetingPlace Video Integration that the participant has joined the conference.
Cisco MeetingPlace Video Integration notifies Cisco MeetingPlace Web Conferencing and the
Cisco MeetingPlace audio server of the status of the participant.
If a Participant Joins a Video Conference on an Ad-Hoc Basis
If all scheduled video-conferencing ports for a meeting that is already in progress are already in use and
an additional participant attempts to join the video conference, the user may be able to join on an ad-hoc
basis. In this case, the Cisco IPVC MCU polls Cisco MeetingPlace Video Integration to see if
video-conferencing ports are available, and if they are, the Cisco IPVC MCU allows the participant to
join the conference.
OL-6280-01
Administrator’s Guide for Cisco MeetingPlace Video Integration Release 5.3
2-7
About the Cisco MeetingPlace Video-Conferencing Process
How Video Conferences Run
About the Video Images
The visual stream to and from the video endpoints is entirely processed by the Cisco IPVC MCU. After
the call is connected, the media stream is routed from the video endpoint, through the Cisco IPVC MCU
for processing into a unified video stream, and back to the video endpoints for display to the users.
However, users control the status of the transmission (for example, started, paused, or terminated) from
within the Cisco MeetingPlace web-conferencing meeting room. See About Displaying the Status and
Options of Video Participants in the Meeting Room, page 2-8.
About the Audio Channel
The audio streams of the Cisco IPVC MCU and Cisco MeetingPlace are mixed to allow audio and
video-conferencing participants to hear and speak to each other. The audio channel from each video
endpoint is routed to the Cisco IPVC MCU, then passed through the video link to the
Cisco MeetingPlace audio server, where it is mixed with the audio from audio-only endpoints and sent
back to all users, to form a seamless audio experience for participants on both video and audio-only
endpoints.
Chapter 2 Cisco MeetingPlace Video Integration Components and Process
About Displaying the Status and Options of Video Participants in the Meeting
Room
When the Cisco IPVC MCU admits a participant to a video conference, the Cisco IPVC MCU notifies
Cisco MeetingPlace Video Integration, which notifies Cisco MeetingPlace Web Conferencing.
Cisco MeetingPlace Web Conferencing identifies the participant as a video participant in the participant
list in the Cisco MeetingPlace web-conferencing meeting room. The participant name displayed comes
from the participant’s profile or guest information if they outdialed from Cisco MeetingPlace, and from
the gatekeeper if they dialed in to the video conference. When a participant mutes, pauses, changes the
view of, or terminates their video connection, Cisco MeetingPlace Web Conferencing registers this
change in the meeting room user interface and passes the request to
Cisco MeetingPlace Video Integration, which passes the request to the Cisco IPVC MCU where it is
performed. If the user terminates the connection by hanging up the video endpoint, the
Cisco IPVC MCU notifies Cisco MeetingPlace Video Integration, which then notifies
Cisco MeetingPlace Web Conferencing so that the status of that participant can be updated.
When a video participant speaks, the Now Speaking display shows “Video Participant.”
How Cisco MeetingPlace Video Integration Tracks Port Availability
The number of available ports and conferences is determined by the Cisco IPVC MCU.
Cisco MeetingPlace Video Integration polls the Cisco IPVC MCU every 30 minutes for this information
and passes it to the Cisco MeetingPlace audio server, which displays it in MeetingTime.
Cisco MeetingPlace Video Integration uses this information to regulate the creation of and entry to video
conferences.
2-8
Administrator’s Guide for Cisco MeetingPlace Video Integration Release 5.3
OL-6280-01
Chapter 2 Cisco MeetingPlace Video Integration Components and Process
How Video Conferences End
The video conference on the Cisco IPVC MCU ends when the Cisco MeetingPlace conference ends,
according to the standard rules for ending conferences on the Cisco MeetingPlace audio server. At this
time, Cisco MeetingPlace Video Integration tells the Cisco IPVC MCU to terminate the video
conference.
About the Cisco MeetingPlace Video-Conferencing Process
OL-6280-01
Administrator’s Guide for Cisco MeetingPlace Video Integration Release 5.3
2-9
About the Cisco MeetingPlace Video-Conferencing Process
Chapter 2 Cisco MeetingPlace Video Integration Components and Process
2-10
Administrator’s Guide for Cisco MeetingPlace Video Integration Release 5.3
OL-6280-01
Installing Cisco MeetingPlace Video Integration
Perform the following tasks to set up Cisco MeetingPlace Video Integration:
• Before You Install, page 3-1
• Installing Cisco MeetingPlace Video Integration, page 3-18
• Uninstalling Cisco MeetingPlace Video Integration, page 3-19
Before You Install
Complete the following tasks in order before you run the Cisco MeetingPlace Video Integration
installer:
• Making Sure Component Systems Are Up and Running, page 3-1
• Verifying your Video-Conferencing License, page 3-2
CHAPTER
3
• About Configuring the Cisco IPVC MCU to Use Cisco MeetingPlace, page 3-2
• Configuring the Cisco MeetingPlace Audio Server, page 3-11
• Configuring Cisco MeetingPlace H.323/SIP IP Gateway, page 3-12
• Configuring Load-Balancing Configurations for Video Conferencing, page 3-12
• About Installing and Configuring Video Endpoints, page 3-13
• (Optional) Configuring Cisco MeetingPlace for Outlook, page 3-14
• (Optional) Configuring Cisco MeetingPlace for Lotus Notes, page 3-14
• Configuring Cisco CallManager, page 3-14
• Preparing to Install the Video Integration with DMZ Configurations, page 3-17
• Gathering Installation Values, page 3-18
Making Sure Component Systems Are Up and Running
Several component systems must be working independently before you prepare to install
Cisco MeetingPlace Video Integration.
Step 1Make sure that the following are true:
OL-6280-01
Administrator’s Guide for Cisco MeetingPlace Video Integration Release 5.3
3-1
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 1In MeetingTime, click the Configure tab, then click System Options.
Step 2Click Query.
Step 3Click the > button until you see Cisco MeetingPlace Video Integration.
Chapter 3 Installing Cisco MeetingPlace Video Integration
Step 4Number 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.
3-2
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.
Administrator’s Guide for Cisco MeetingPlace Video Integration Release 5.3
OL-6280-01
Chapter 3 Installing Cisco MeetingPlace Video Integration
We do not recommend changing settings in the Cisco IPVC MCU after users have begun to schedule
conferences via Cisco MeetingPlace if such changes reduce the number of available video conferences
or ports. Before changing the settings in the Cisco IPVC MCU, see Changing Settings in Other
Components, page 4-3.
To configure your Cisco IPVC MCU to provide video content for Cisco MeetingPlace conferences, you
must do the following in this order:
Step 1Verify that all video endpoints can connect to a conference on the Cisco IPVC MCU, and that the
Cisco IPVC MCU can call out to all video endpoints.
Step 2Create a Cisco IPVC MCU user for Cisco MeetingPlace.
Step 3Set Cisco IPVC MCU management parameters that are required to support Cisco MeetingPlace:
–
Reserve ports for Cisco MeetingPlace conferences.
–
Specify that only authorized users can use the Cisco IPVC MCU to create video conferences.
In this case, only Cisco MeetingPlace will be authorized to create video conferences.
–
Enable the Cisco IPVC MCU to generate an announcement for the Cisco MeetingPlace Waiting
Room.
Step 4Create a Cisco IPVC MCU service for Cisco MeetingPlace.
Before You Install
NoteYou cannot stack embedded Cisco IPVC media processors to use with Cisco MeetingPlace.
Verifying that Video Endpoints Can Connect to the Cisco IPVC MCU
Endpoints must be able to join video conferences on the Cisco IPVC MCU before
Cisco MeetingPlace Video Integration can run.
If you have questions about routing calls through the gatekeeper and you use a Cisco IOS H.323
Gatekeeper, see the Cisco IOS H.323 Configuration Guide.
Step 1Follow the instructions in the documentation for your Cisco IPVC MCU to have each video endpoint dial
in to a video conference.
Step 2Follow the instructions in the documentation for your Cisco IPVC MCU to have the Cisco IPVC MCU
call each video endpoint.
Creating a Cisco IPVC MCU User for Cisco MeetingPlace
Create a username and password that Cisco MeetingPlace Video Integration will use to log in to the
Cisco IPVC MCU.
Step 1Log in to the Cisco IP/VC Administrator of the Cisco IPVC MCU that you want Cisco MeetingPlace to
use.
OL-6280-01
Step 2Click Board or Device on the sidebar.
Step 3Click the Users tab.
Administrator’s Guide for Cisco MeetingPlace Video Integration Release 5.3
3-3
Chapter 3 Installing Cisco MeetingPlace Video Integration
Before You Install
Step 4Click the Add button.
The Add User dialog box appears.
Step 5In the “User name” field, enter the name that you want the Cisco MeetingPlace Web Conferencing
server to use to log in to the Cisco IPVC MCU.
Step 6In the “Access level” field, click Administrator or Operator.
Step 7In the Password field, enter the password that you want this user to have.
Step 8In the “Confirm Password” field, enter the password that you want Cisco MeetingPlace to use.
Step 9To disable the ability of this user to telnet into the Cisco IPVC MCU, uncheck Enable for Telnet / FTP.
Step 10To save this user profile, click Upload.
Setting Cisco IPVC MCU Parameters Required to Support Cisco MeetingPlace
To use your Cisco IPVC MCU with Cisco MeetingPlace, you must configure certain Cisco IPVC MCU
parameters to provide video for Cisco MeetingPlace conferences.
For more information about configuring the Cisco IPVC MCU for operation, see Cisco IP/VC 3511 MCU and Cisco IP/VC 3540 MCU Module Administrator Guide, Version 3.2.
Step 1Log in to the Cisco IP/VC Administrator of the Cisco IPVC MCU that you want the Cisco MeetingPlace
server to use.
Step 2Choose MCU > Settings > Basics.
Step 3In the MCU field, click MCU.
Step 4In the “Number of SCCP ports” field, select a value for the number of ports that you want
Cisco CallManager to use that leaves ports available for Cisco MeetingPlace.
For example, for a 60-port Cisco IPVC MCU select 0, 15, 30, or 45.
Step 5Click the Conference Mgmt button.
Step 6Set the following parameters in the Conference Mgmt page:
a. In the “External conference authorization policy” field, click Authorize.
b. In the “Allow conference creation using” field, click Scheduler, Web, Control API and dial-in.
c. In the “Allow conference joining using” field, click Invite and dial-in.
d. In the “Dial-in conference terminates when” field, click Last participant leaves.
Step 7Click the Advance button.
Step 8We recommend that you check Disconnect participants on communications (ICMP) failure and click
Audio failure in the “Disconnect on” field.
Step 9To save these settings to memory, click Upload.
3-4
Setting the Audio Indication Interval (Optional)
If video participants join a conference that has not yet started, they must wait in the waiting room. To
play an announcement while participants wait, set the following parameter:
Administrator’s Guide for Cisco MeetingPlace Video Integration Release 5.3
OL-6280-01
Loading...
+ 58 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.