Table Of Contents
Installing Cisco MeetingPlace Video Integration
Before You Install
Making Sure Component Systems Are Up and Running
Verifying your Video-Conferencing License
About Configuring the Cisco IPVC MCU to Use Cisco MeetingPlace
Verifying that Video Endpoints Can Connect to the Cisco IPVC MCU
Creating a Cisco IPVC MCU User for Cisco MeetingPlace
Setting Cisco IPVC MCU Parameters Required to Support Cisco MeetingPlace
Creating a Service for Cisco MeetingPlace
Configuring the Cisco MeetingPlace Audio Server
Modifying the Translation Table
About Setting the Audio Codec Negotiation Priority
Configuring Cisco MeetingPlace H.323/SIP IP Gateway
Configuring Load-Balancing Configurations for Video Conferencing
About Installing and Configuring Video Endpoints
(Optional) Configuring Cisco MeetingPlace for Outlook
(Optional) Configuring Cisco MeetingPlace for Lotus Notes
Configuring Cisco CallManager
Gathering Configuration Values
Adding an H.323 Gatekeeper
Creating an H.225 Trunk for the Cisco IPVC MCU
Adding the Route Pattern to Route Calls to the Cisco IPVC MCU
Preparing to Install the Video Integration with DMZ Configurations
Gathering Installation Values
Installing Cisco MeetingPlace Video Integration
Uninstalling Cisco MeetingPlace Video Integration
Installing Cisco MeetingPlace Video Integration
Perform the following tasks to set up Cisco MeetingPlace Video Integration:
•
Before You Install
•Installing Cisco MeetingPlace Video Integration
•Uninstalling Cisco MeetingPlace Video Integration
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
•Verifying your Video-Conferencing License
•About Configuring the Cisco IPVC MCU to Use Cisco MeetingPlace
•Configuring the Cisco MeetingPlace Audio Server
•Configuring Cisco MeetingPlace H.323/SIP IP Gateway
•Configuring Load-Balancing Configurations for Video Conferencing
•About Installing and Configuring Video Endpoints
•(Optional) Configuring Cisco MeetingPlace for Outlook
•(Optional) Configuring Cisco MeetingPlace for Lotus Notes
•Configuring Cisco CallManager
•Preparing to Install the Video Integration with DMZ Configurations
•Gathering Installation Values
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 1 Make sure that the following are true:
•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.
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 1 Verify 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 2 Create a Cisco IPVC MCU user for Cisco MeetingPlace.
Step 3 Set 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 4 Create a Cisco IPVC MCU service for Cisco MeetingPlace.
Note You 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 1 Follow the instructions in the documentation for your Cisco IPVC MCU to have each video endpoint dial in to a video conference.
Step 2 Follow 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 1 Log in to the Cisco IP/VC Administrator of the Cisco IPVC MCU that you want Cisco MeetingPlace to use.
Step 2 Click Board or Device on the sidebar.
Step 3 Click the Users tab.
Step 4 Click the Add button.
The Add User dialog box appears.
Step 5 In 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 6 In the "Access level" field, click Administrator or Operator.
Step 7 In the Password field, enter the password that you want this user to have.
Step 8 In the "Confirm Password" field, enter the password that you want Cisco MeetingPlace to use.
Step 9 To disable the ability of this user to telnet into the Cisco IPVC MCU, uncheck Enable for Telnet / FTP.
Step 10 To 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 1 Log in to the Cisco IP/VC Administrator of the Cisco IPVC MCU that you want the Cisco MeetingPlace server to use.
Step 2 Choose MCU > Settings > Basics.
Step 3 In the MCU field, click MCU.
Step 4 In 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 5 Click the Conference Mgmt button.
Step 6 Set 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 7 Click the Advance button.
Step 8 We recommend that you check Disconnect participants on communications (ICMP) failure and click Audio failure in the "Disconnect on" field.
Step 9 To save these settings to memory, click Upload.
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:
Step 1 Click MCU, then click Settings.
Step 2 Click the Advanced button.
Step 3 Click the Commands button.
The Advanced Command dialog box appears.
Step 4 In the Advanced Command dialog box, do the following:
a. In the Available commands window, click Audio indication interval.
Your selection appears in the Command field.
b. In the Parameter field, enter the value in milliseconds that you want Cisco MeetingPlace to announce to video participants that they are in the waiting room and that the conference has not formally started.
Tip We recommend entering 1500 to establish an interval of 15 seconds.
c. Click Send, then click Close.
Creating a Service for Cisco MeetingPlace
You must create a Cisco IPVC MCU service for Cisco MeetingPlace. Before you create a service in the Cisco IPVC MCU make sure that the media processor (MP) that the Cisco IPVC MCU uses supports Cisco MeetingPlace.
Table 3-1 provides information about which Cisco IPVC media processors support Cisco MeetingPlace.
Table 3-1 Media Processors That Support Video in Cisco MeetingPlace, Release 5.3
Cisco IPVC Media Processor
|
Software Supporting Cisco MeetingPlace
|
Local Cisco IPVC MCU media processor
|
Release 3.5.24 or later releases
|
Cisco IPVC EMP
|
Release 2.0.11 or later releases
|
Cisco IPVC Rate Matching module
|
Does not support Cisco MeetingPlace
|
Data Conferencing Card
|
Does not support Cisco MeetingPlace.
|
You can use one of the preconfigured Cisco MeetingPlace service templates or manually create a Cisco MeetingPlace service.
Using Preconfigured Service Templates
Cisco IPVC MCU, Release 3.5.24 includes three preconfigured services that are designed for Cisco MeetingPlace.
Note The Cisco MeetingPlace service prefixes appear automatically on the IP/VC Administrator Services page for new Cisco IPVC MCUs. However, these services do not appear when you upgrade your Cisco IPVC MCU to Release 3.5.24. To display these services, you must use the restore factory defaults option. In doing so, you will lose your current configuration.
To install the Cisco MeetingPlace service templates on an existing Cisco IPVC MCU installation and erase existing services:
Step 1 Run the Cisco IPVC MCU installer.
Step 2 At the first install screen, click Customize.
Step 3 Check the MCU Config File check box.
Step 4 Continue with the installation.
Step 5 After installation, log in to the Cisco IPVC MCU as administrator.
Step 6 Click MCU on the sidebar and click the Services tab.
Step 7 In the Services tab, choose the appropriate template for your needs. Voice Activated allows participants to View Active Speaker, while Continuous Presence allows participants to View Multiple People. These settings are available to participants in the web-conferencing meeting room:
Service Prefix
|
Supported Views
|
Supported Endpoints
|
Processors Required
|
Format
|
Allow Dynamic Scheme
|
887
|
Voice Activated and Continuous Presence
|
H.323
|
MP
|
H.261
|
Unchecked
|
888
|
Voice Activated
|
SCCP, H.323
|
MP
|
H.263
|
Checked
|
889
|
Voice Activated and Continuous Presence
|
SCCP, H.323
|
MP and EMP
|
H.263
|
Checked for both views
|
Step 8 Review the remaining topics in About Configuring the Cisco IPVC MCU to Use Cisco MeetingPlace and make additional configurations as required for your needs.
Creating a Service Manually
To create a Cisco IPVC MCU service for Cisco MeetingPlace, do the following tasks:
•Setting the Core Service Parameters
•Setting Audio Indications
•Making Sure that a Conference Password Is Not Required
•Setting Conference View Parameters
•Setting Video Schemes Parameters
Setting the Core Service Parameters
Step 1 Click MCU on the sidebar and click the Services tab.
Step 2 Click the Add button.
The Select Service dialog box appears.
Step 3 To create a new service, click OK.
The Add Service dialog box appears.
Step 4 In the "Service prefix" field, enter the value that you want to use for the Cisco MeetingPlace service.
Step 5 Uncheck the SCCP Service check box. Users of SCCP endpoints can still attend Cisco MeetingPlace conferences.
Step 6 In the "Service description," enter the description for this service that you want to appear on the Create Conference page.
Step 7 In the "Media types" section, check Video.
Note Cisco MeetingPlace provides data collaboration in conferences. Disable data collaboration in the Cisco IPVC MCU if it is currently enabled.
Step 8 Specify the number of ports that you want the Cisco IPVC MCU to reserve for each conference as follows:
a. In the "Reserved number of parties" field, enter 2.
Note One of these ports is reserved for the Cisco MeetingPlace server.
Tip You can ascertain the maximum number of ports this service can support by entering 200 in the "Maximum number of parties" field and choosing OK at the bottom of the page. The error message that appears indicates the maximum number of ports the current configuration allows based on the video bandwidth value specified in the Conference Views section.
b. In the "Maximum number of parties" field, enter the total number of Cisco IPVC MCU ports that are available for conferences.
Setting Audio Indications
We recommend that you enable all audio-indication parameters.
Step 1 Click the Indications button.
The Indications Settings dialog box appears.
Step 2 Make sure that all parameters are checked.
Step 3 Click OK.
Making Sure that a Conference Password Is Not Required
Step 1 Click the Management button.
The Management Settings dialog box appears.
Step 2 Make sure that password-related parameters are unchecked.
Step 3 Click OK.
The Add Services dialog box appears.
Setting Conference View Parameters
When you set view parameters, use the Cisco MeetingPlace service template as a model. The templates are described in Using Preconfigured Service Templates. A Voice Activated view allows participants to View Active Speaker, while a Continuous Presence view allows participants to View Multiple People.
Note•One Voice Activated, 1-participant layout is required. A Continuous Presence view is optional, if your hardware supports it.
•Do not create multiple identical views for a single service code. Each view must be unique.
General Instructions for Setting View Parameters
Step 1 Click the edit view icon.
The Edit View dialog box appears.
Step 2 In the "Use Processor" field, click the type of media processor that you want this service to use.
Note The MP and RM option does not support Cisco MeetingPlace.
•Click MP to specify that the service only uses the local media processor to process video conference calls.
•Click EMP to specify that the service uses the Cisco IPVC Enhanced Media Processor (EMP) register with the Cisco IPVC MCU to process video conference calls.
•Click Auto to allow the Cisco IPVC MCU to choose the media processor the Cisco IPVC MCU will use to process a specific video conference.
Note See Cisco IP/VC 3511 MCU and Cisco IP/VC 3540 MCU Module Administrator Guide, Version 3.2 for information about registering a media processor with the Cisco IPVC MCU.
Step 3 In the "Video Picture Size" field, click the video format that you anticipate most endpoints will use.
Step 4 To enable the Cisco IPVC MCU to switch the video to the speaker who is speaking the loudest, check Enable voice activate.
Step 5 In the "Voice activate method" field, we recommend that you click All see one to have all participants see the current speaker.
Step 6 To disable automatic switching of nonspeaking participants, uncheck Enable auto-switch.
Step 7 To save these conference-view parameters and to close the Edit View dialog box, click OK.
Special Instructions for Accommodating SCCP Endpoints
Because SCCP endpoints require the H.263 format, special view settings are required. To set up views, use the table in Using Preconfigured Service Templates as a model for setting parameters, or use the appropriate procedure from this section.
If your users will attend via SCCP endpoints and your Cisco IPVC MCU has only an MP card, only the Voice Activated view can be used. In this case, all participants will be able to use only the View Active Speaker option available in the Cisco MeetingPlace meeting room. They will not be able to view multiple people simultaneously.
Creating a Single Voice Activated View
Step 1 The default view should have the correct parameter settings. Verify that the settings are as follows:
Parameter
|
Value
|
Initial Layout
|
1-participant layout
|
Max Layout
|
1-participant layout
|
Use Processor
|
MP
|
Format (in the Video Schemes Settings section)
|
H.263
|
Other parameters
|
As desired
|
Step 2 Click OK.
If your users will attend via SCCP endpoints and you have both an MP card and an EMP card, in order for participants to be able to use both the View Active Speaker and the View Multiple People options that are available in the Cisco MeetingPlace web-conferencing meeting room, both views are required. The View Active Speaker option corresponds to the Voice Activated view, and View Multiple People corresponds to the Continuous Presence view.
Creating Two Separate Views
Step 1 In the service, click the Views button to create the first view.
Step 2 Set the following parameters for this view:
Parameter
|
Value
|
Initial Layout
|
Desired multiple participant layout (for example, 4 participant)
|
Max Layout
|
Desired multiple participant layout (for example, 4 participant)
|
Use Processor
|
EMP
|
Format (in the Video Schemes Settings section)
|
H.263
|
Other parameters
|
As desired
|
Step 3 Click OK.
Step 4 Check the Display all conference views check box.
Step 5 Click Add View.
Step 6 Set the following parameters for the second view:
Parameter
|
Value
|
Initial Layout
|
1-participant layout
|
Max Layout
|
1-participant layout
|
Use Processor
|
MP
|
Format (in the Video Schemes Settings section)
|
H.263
|
Other parameters
|
As desired
|
Step 7 Click OK.
Setting Video Schemes Parameters
Step 1 Select the "Video Settings Schemes" profile that you want to edit and click the Edit button.
The Edit Video Scheme dialog box appears.
Step 2 In the "Max bit rate" field, click the maximum video bandwidth that you want this service to support. This number must be less than or equal to the bandwidth settings in Cisco MeetingPlace (and in Cisco CallManager, if your network uses Cisco CallManager.)
Note Endpoints that are not capable of supporting this bandwidth receive only the conference audio unless dynamic scheme is allowed.
Step 3 Check Allow dynamic scheme to enable the Cisco IPVC MCU to switch the conference video bandwidth to a lower value when a less capable endpoint joins the conference.
•In the "Min bit rate" field, click the lowest bandwidth that you want this parameter to support.
Step 4 To save these Video Scheme changes and to close this dialog box, click OK.
Step 5 To save these conference-view parameters and to close the Edit View dialog box, click OK.
Saving Your Service
To save your service, click OK at the bottom of the Service page.
Configuring the Cisco MeetingPlace Audio Server
Perform the following tasks before you install Cisco MeetingPlace Video Integration.
Modifying the Translation Table
Step 1 If your Cisco MeetingPlace system supports IP phones only, you do not need to change the translation table on the Cisco MeetingPlace audio server.
If your Cisco MeetingPlace audio server is configured for both PSTN and IP interfaces, and your organization does not have a certified Cisco MeetingPlace technician, contact Cisco MeetingPlace Professional Services to modify the translation table in Cisco MeetingPlace audio server. For information, contact your Cisco technical support representative. See the Guide to Cisco Conferencing Documentation and Support.
About Setting the Audio Codec Negotiation Priority
Sound quality and bandwidth use are determined partly by the audio codec that the Cisco MeetingPlace and Cisco IPVC systems use. The video endpoint's video signal and its audio channel must share available bandwidth. As a result, better picture quality may degrade audio quality or delay audio transmission.
The Cisco MeetingPlace audio server supports the G.711 and G.729a compression codecs. To allocate resources between audio and video to best meet your needs, specify a voice data compression protocol in Cisco MeetingPlace audio server using the setipcodec command. For instructions, see the Configuration Guide for Cisco MeetingPlace Audio Server Release 5.3. Use the following guideline:
•To make more bandwidth available for video, assign G.729 the highest priority.
•For better audio sound quality, assign G.711 the highest priority.
Supporting G.729
Step 1 If 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.
Configuring Cisco MeetingPlace H.323/SIP IP Gateway
The Cisco MeetingPlace H.323/SIP IP Gateway connects the Cisco MeetingPlace system to the network. Cisco MeetingPlace H.323/SIP IP Gateway also initiates the call that connects the Cisco MeetingPlace audio server with the Cisco IPVC MCU.
•If your MeetingPlace system currently supports Cisco IP telephony, you do not need to make further changes to the Cisco MeetingPlace H.323/SIP IP Gateway.
•If your network includes Cisco CallManager and you have not yet configured the Cisco MeetingPlace H.323/SIP IP Gateway and Cisco CallManager to route calls to each other, see instructions in the Administrator's Guide for Cisco MeetingPlace H.323/SIP IP Gateway Release 5.2.1.
•If Cisco CallManager is not part of your network environment, MeetingPlace H.323/SIP IP Gateway can register itself directly to the H.323 gatekeeper. For instructions on configuring the Cisco MeetingPlace H.323/SIP IP Gateway for use with an H.323 gatekeeper, see the Administrator's Guide for Cisco MeetingPlace H.323/SIP IP Gateway Release 5.2.1. If it is correctly configured, the H.323/SIP IP Gateway appears in the endpoint registration table in the gatekeeper.
If your Cisco MeetingPlace system includes more than one Cisco MeetingPlace H.323/SIP IP Gateway, and if the gateways are connecting to a gatekeeper, the E.164 number of each MeetingPlace H.323/SIP IP Gateway must be unique. (The E.164 numbers do not need to be unique if they connect to Cisco CallManager.)
Step 1 If the Cisco MeetingPlace H.323/SIP IP Gateway is not already connected to your network, use the information in this section to configure all necessary components.
Configuring Load-Balancing Configurations for Video Conferencing
In Cisco MeetingPlace deployments for large numbers of users, multiple Cisco MeetingPlace Web Conferencing servers can be configured in clusters, and meetings are distributed among the servers in a cluster. However, you can install Cisco MeetingPlace Video Integration on only one of those Cisco MeetingPlace Web Conferencing servers, and meetings that include video conferencing must be held on that server.
Meetings that are scheduled with video ports are automatically held on the server that has Cisco MeetingPlace Video Integration installed on it. However, in order to ensure that ad-hoc video conferences can occur, configure Cisco MeetingPlace Web Conferencing so that meetings that are scheduled by users whose profiles allow them to schedule video conferences are always hosted on the server that has Cisco MeetingPlace Video Integration installed on it.
If your Cisco MeetingPlace system is configured for load balancing, set the system to allow ad-hoc video conferencing.
Note Perform the following steps even if Cisco MeetingPlace Video Integration is not installed on a server in a cluster that includes load balancing.
Step 1 Sign in to the Cisco MeetingPlace Web Conferencing interface using your System Manager password.
Step 2 Click Admin.
Step 3 Click Site Properties.
Step 4 On the Cisco MeetingPlace Web Conferencing Administration page for your site, set Allow Web Load Balancing in Ad Hoc Video Meetings to No.
How Load Balancing Works
If the server with Cisco MeetingPlace Video Integration is not available at the start of a conference, the meeting rolls to another server after 5 times the Load Stats Poll Period value on the Cisco MeetingPlace Web Conferencing Site Administration page. The Load Stats Poll Period parameter defaults to 1 minute. In this situation, video conferencing is not possible, but data and voice conferencing are available as usual.
If you do not set this option to No, all web conferences will be load-balanced. Video conferencing will not be available to conferences that are held on web-conferencing servers other than the one on which Cisco MeetingPlace Video Integration is installed.
For general information about load-balancing configurations, see the Administrator's Guide for Cisco MeetingPlace Web Conferencing Release 5.3.
About Installing and Configuring Video Endpoints
Video endpoints are the hardware and software that capture, send, receive, and display video images and audio. They can be either of the following:
•Room-based video systems.
•Desktop video systems, for example, a digital camera that is attached to the computer or IP phone of an individual user, and software to display images on the computer screen.
Cisco MeetingPlace Video Integration supports all video endpoints that are supported by Cisco IPVC MCU version 3.5plus. SCCP video endpoints (such as Cisco VT Advantage) require Cisco CallManager. ISDN video endpoints require a Cisco IPVC PRI Gateway as part of the Cisco IPVC MCU configuration. All endpoints must be able to participate successfully in a video conference on the Cisco IPVC MCU independently of Cisco MeetingPlace Video Integration.
If Cisco MeetingPlace Audio Server is configured to use only G.729, make sure your Cisco IPVC MCU supports this protocol.
If an endpoint is correctly configured to work with the Cisco IPVC MCU and configured to optimize audio quality according to the documentation that came with the product, no additional configuration is required for Cisco MeetingPlace Video Integration. To optimize sound quality, see the tips in the troubleshooting section on Problems During a Video Conference, page 6-7.
To set up Cisco VT Advantage endpoints, see the Cisco VT Advantage Administration Guide.
Because SCCP endpoints do not support the H.261 protocol, they support View Multiple People mode only if the Cisco IPVC MCU has an EMP processor and you have configured views on the Cisco IPVC MCU to support Continuous Presence according to instructions in Setting Conference View Parameters.
(Optional) Configuring Cisco MeetingPlace for Outlook
If your Cisco MeetingPlace system includes Cisco MeetingPlace for Outlook, perform the tasks in this section. If not, skip this section.
Cisco MeetingPlace for Outlook generates meeting notifications that users receive when they are invited to a meeting. These notifications are generated from templates that you can optionally customize.
For complete information about customizing meeting notification templates, see the Administrator's Guide for Cisco MeetingPlace for Outlook Release 5.3.
When the system includes Cisco MeetingPlace Video Integration, three video-specific templates are used. By default, these templates include parameters for dial in numbers for IP and ISDN video endpoints. They also direct users to join the web conference first, then join the video or voice conference. (This is the preferred method. Users who join the video conference from within the web conference have full access to the video controls and features in the web-conferencing meeting room.)
You can remove information that is not applicable, or add special instructions or other information that your users can use to attend conferences that include video.
Step 1 Examine the three video-specific notification templates to determine whether they have by default the information that your video users need.
Step 2 If not, customize the video-related meeting notifications.
(Optional) Configuring Cisco MeetingPlace for Lotus Notes
If your Cisco MeetingPlace system includes Cisco MeetingPlace for Lotus Notes, perform the tasks in this section. If not, skip this section.
The following steps provide a general overview. For complete instructions, see the Administrator's Guide for Cisco MeetingPlace for Lotus Notes Release 5.3.
Step 1 Configure the video-related settings in the MeetingPlace Server Agent database (MPSA.nsf):
•MeetingPlace Functionality Settings
–Hide # of Video Callers Field
–Make Meetings Web Only
•MeetingPlace Scheduling Parameters
–# of Video Ports to Schedule
Configuring Cisco CallManager
If your environment does not include Cisco CallManager, skip this section and follow instructions in Configuring Cisco MeetingPlace H.323/SIP IP Gateway to route calls to and from Cisco MeetingPlace via the H.323 gatekeeper.
If your environment includes Cisco CallManager, set up Cisco CallManager to route calls between the components involved in integrating video conferencing with Cisco MeetingPlace.
There are many ways to set up Cisco CallManager to work with Cisco MeetingPlace Video Integration. For example, you can use the guidelines in the Cisco IP Video Telephony Solution Reference Network Design to set up Cisco CallManager to route all calls, or you can follow the example in this section to have the gatekeeper route H.323 calls. The best solution will depend on your network environment and requirements. Determining the best configuration of Cisco CallManager for your network is beyond the scope of this document; see the documentation for Cisco CallManager or contact your Cisco technical support representative. See the Guide to Cisco Conferencing Documentation and Support.
Note If your Cisco MeetingPlace H.323/SIP IP Gateway is not yet configured for use with Cisco CallManager, see the Administrator's Guide for Cisco MeetingPlace H.323/SIP IP Gateway, Release 5.2.1 for configuration instructions.
To set up Cisco CallManager if you use a gatekeeper to route calls, perform the following general steps:
Step 1 Create a gatekeeper device that points to the gatekeeper associated with the Cisco IPVC MCU.
Step 2 Create an H.225 (Gatekeeper Controlled) trunk for the Cisco IPVC MCU.
Step 3 Create a route pattern to route calls to the H.225 (Gatekeeper Controlled) trunk for the Cisco IPVC MCU.
Gathering Configuration Values
Step 1 Make a note of the following:
•The service code for Cisco MeetingPlace conferences that you specified in the Cisco IPVC MCU.
•The IP address or hostname of the Cisco IPVC MCU.
•The IP address or hostname of the H.323 gatekeeper.
Adding an H.323 Gatekeeper
Step 1 Launch and log in to the Cisco CallManager Administration interface.
Step 2 Choose Device > Gatekeeper.
Step 3 Click Add a New Gatekeeper.
Step 4 Enter options:
Field
|
Value
|
Host Name / IP Address
|
IP address of the gatekeeper that your Cisco IPVC MCU is registered to.
|
Description
|
A name that identifies this gatekeeper.
|
Enable Device
|
Check the check box.
|
Other options
|
Values as appropriate for your environment.
|
Step 5 Click Insert.
Creating an H.225 Trunk for the Cisco IPVC MCU
Step 1 From the Cisco CallManager Administration menu bar, choose Device > Trunk.
Step 2 Click Add a New Trunk.
Step 3 For Trunk Type, choose H.225 (Gatekeeper Controlled).
Step 4 Click Next.
Step 5 Enter options:
Field
|
Value
|
Device Name
|
The IP address of your Cisco IPVC MCU.
|
Description
|
A name that identifies this trunk.
|
Retry Video Call as Audio
|
Check the check box.
|
Wait for Far End H.245 Terminal Capability Set
|
Check the check box.
|
Gatekeeper Name
|
The IP address of the gatekeeper to which your Cisco IPVC MCU is registered.
|
Terminal Type
|
Gateway
|
Technology Prefix
|
The prefix or pattern that will route calls to Cisco CallManager.
|
Other parameters
|
Values as appropriate for your environment.
|
Step 6 Click Insert.
Step 7 Click OK.
Step 8 Click Reset Trunk.
Adding the Route Pattern to Route Calls to the Cisco IPVC MCU
Step 1 From the Cisco CallManager Administration menu bar, do one of the following:
•In Cisco CallManager 4.0, choose Route Plan > Route Pattern/Hunt Pilot.
•In Cisco CallManager 4.1, choose Route Plan > Route /Hunt > Route Pattern.
Step 2 Click Add a New Route Pattern/Hunt Pilot.
Step 3 Enter options:
Parameter
|
Value
|
Route Pattern/Hunt Pilot
|
The MeetingPlace service prefix you defined on the Cisco IPVC MCU, followed by an exclamation point (!).
|
Description
|
The MeetingPlace Service on the Cisco IPVC MCU, or a different name that describes this route pattern.
|
Cisco CallManager 4.0:
Gateway or Route/Hunt List
Cisco CallManager 4.1:
Gateway or Route List
|
The IP address or hostname of the H225 Trunk (Gatekeeper Controlled) that you created.
|
Provide Outside Dialtone
|
Uncheck this check box.
|
Other parameters.
|
Values as appropriate for your environment.
|
Step 4 Click Insert.
Preparing to Install the Video Integration with DMZ Configurations
A DMZ is an area on the corporate network that is outside the corporate firewall. In order to allow external participants to attend Cisco MeetingPlace conferences without compromising security, one or more Cisco MeetingPlace Web Conferencing servers are deployed behind the firewall, and one or more web-conferencing servers are deployed in a DMZ. These configurations are called "segmented meeting access" (SMA) configurations; they are described fully in the Administrator's Guide for Cisco MeetingPlace Web Conferencing Release 5.3.
Cisco MeetingPlace Video Integration must be installed on one and only one server on which Cisco MeetingPlace Web Conferencing is installed:
•If it is installed behind the firewall, only internal participants can attend video conferences.
•If it is installed in the DMZ, external participants can also attend.
Note•If Cisco MeetingPlace Video Integration is installed in the DMZ, meeting schedulers must allow Internet access for all conferences that will include video, even if only internal participants will attend. The web and video conferences will be held on the server in the DMZ.
•If Cisco MeetingPlace Video Integration is installed behind the firewall in a DMZ configuration, users cannot include video conferencing in a meeting that also includes web-conferencing participants who are outside the firewall.
•Additional caveats apply. See Important Information About DMZ Configurations and Video Conferencing, page 4-12.
Step 1 Use the information in this section to decide whether you will install Cisco MeetingPlace Video Integration behind the firewall or in the DMZ.
Step 2 If you will install Cisco MeetingPlace Video Integration in the DMZ, and if the Cisco IPVC MCU is installed behind the firewall, open TCP port 3336 through the firewall to allow you to connect Cisco MeetingPlace Video Integration to the Cisco IPVC MCU.
Gathering Installation Values
You need to know the following in order to install Cisco MeetingPlace Video Integration:
Item
|
Value
|
IP address or host name of the Cisco IPVC MCU.
|
----------------------------------------------------------
|
The unique, dedicated service prefix that identifies Cisco MeetingPlace conferences on the Cisco IPVC MCU. This number must not coincide with other routing patterns that are registered with Cisco CallManager or the H.323 gatekeeper.
|
----------------------------------------------------------
|
The operator or administrator account user name and password on the Cisco IPVC MCU that Cisco MeetingPlace Video Integration will use to control video conferences.
|
----------------------------------------------------------
----------------------------------------------------------
|
The E.164 number or numbers assigned to the Cisco MeetingPlace H.323/SIP IP Gateways.
If more than one Cisco MeetingPlace H.323/SIP IP Gateway is connected to the same Cisco MeetingPlace audio server, each IP Gateway must have a unique E.164 number. List up to five E.164 numbers, each separated by a semicolon (;).
|
----------------------------------------------------------
|
Installing Cisco MeetingPlace Video Integration
Step 1 Make sure you have completed all prerequisite tasks documented in this chapter.
Step 2 Make sure Cisco MeetingPlace is not in use. The Cisco MeetingPlace Video Integration installer will stop the Cisco MeetingPlace Web Conferencing master service and all subordinate services.
Step 3 Make sure Cisco MeetingPlace Web Conferencing Release 5.3 is installed on the server on which you will install Cisco MeetingPlace Video Integration.
Step 4 Make sure that the Cisco IPVC MCU is available on the network (reachable via its IP address).
Step 5 Run the Cisco MeetingPlace Video Integration Setup.exe and follow the prompts: Enter the values that you collected in Gathering Installation Values.
Step 6 All Cisco MeetingPlace services will restart automatically after the installation is complete. Click the refresh button in the Services window to update the view.
Step 7 To see if your system is configured correctly, click the orange Cisco MeetingPlace icon in the system tray at the bottom of the computer screen and choose Eventlog.
If the installation is configured properly, this message appears:
Cisco MeetingPlace Video Integration -> CConferenceTechnologyProvider::initialize() STATUS: Cisco MeetingPlace Video Integration READY to receive requests from MPAgent.
Step 8 Configure the following parameters:
Uninstalling Cisco MeetingPlace Video Integration
To uninstall Cisco MeetingPlace Video Integration, use Add/Remove Programs in the Control Panel, or run the installer again.
The uninstall process will automatically stop the Cisco MeetingPlace Web Conferencing service and other Cisco MeetingPlace services including the Cisco MeetingPlace Video Integration service.
If you plan to reinstall Cisco MeetingPlace Web Conferencing and Cisco MeetingPlace Video Integration, uninstall Cisco MeetingPlace Video Integration first; then uninstall Cisco MeetingPlace Web Conferencing.
All services will automatically start again when the uninstallation is complete.
Feedback
