* If Cisco Unified CallManager is not part of your network environment, the H.323/SIP Gateway can register itself directly to the H.323 gatekeeper. For instructions on configuring the H.323/SIP Gateway for use with an H.323 gatekeeper, see [[Cisco Unified MeetingPlace Release 6.1 -- Cisco Unified MeetingPlace H.323/SIP IP Gateway, Release 5.3|Cisco Unified MeetingPlace H.323/SIP IP Gateway, Release 5.3]]. If it is correctly configured, the H.323/SIP Gateway appears in the endpoint registration table in the gatekeeper.

+

* If Cisco Unified CallManager is not part of your network environment, the H.323/SIP Gateway can register itself directly to the H.323 gatekeeper. For instructions on configuring the H.323/SIP Gateway for use with an H.323 gatekeeper, see [[Cisco Unified MeetingPlace, Release 6.x -- Cisco Unified MeetingPlace H.323/SIP IP Gateway, Release 5.3|Cisco Unified MeetingPlace H.323/SIP IP Gateway, Release 5.3]]. If it is correctly configured, the H.323/SIP Gateway appears in the endpoint registration table in the gatekeeper.

: If your Cisco Unified MeetingPlace system includes more than one H.323/SIP Gateway, and if the gateways are connecting to a gatekeeper, the E.164 number of each H.323/SIP Gateway must be unique. (The E.164 numbers do not need to be unique if they connect to Cisco Unified CallManager.)

: If your Cisco Unified MeetingPlace system includes more than one H.323/SIP Gateway, and if the gateways are connecting to a gatekeeper, the E.164 number of each H.323/SIP Gateway must be unique. (The E.164 numbers do not need to be unique if they connect to Cisco Unified CallManager.)

Verifying That Component Systems Are Up and Running

Several component systems must be working independently before you prepare to install Cisco Unified MeetingPlace Video Integration.

Verify the following:

Release 6.1 of the Cisco Unified MeetingPlace system is up and running, including Cisco Unified MeetingPlace Audio Server and Cisco Unified MeetingPlace Web Conferencing.

All video endpoints that your organization supports (H.323, SCCP, and ISDN) can successfully participate in video conferences on the Cisco Unified Videoconferencing MCU. Endpoints must be able to join both by dialing in and by having the Cisco Unified Videoconferencing MCU call the endpoint.

Verifying Your Video-Conferencing License

Verify that your Cisco Unified MeetingPlace system is licensed for Video Integration.

To Verify Your Video-Conferencing License

In MeetingTime, click the Configure tab, then click System Options.

Click Query.

Click the > button until you see Cisco Unified MeetingPlace Video Integration.

The Number of Licenses should be set to 1. If it is set to 0 (zero) contact your Cisco technical support representative.

About Configuring the Cisco Unified Videoconferencing MCU to Use Cisco Unified MeetingPlace

Before you configure the Cisco Unified Videoconferencing MCU for Cisco Unified MeetingPlace Video Integration, verify that the Cisco Unified Videoconferencing MCU is working independently of Video Integration, and that it can host and manage video conferences.

All H.323 resources on the Cisco Unified Videoconferencing MCU are dedicated to the Cisco Unified MeetingPlace services, and Cisco Unified MeetingPlace controls all H.323 resources on the Cisco Unified Videoconferencing MCU. However, conferences can be created by using SCCP (Skinny protocol), and Cisco Unified MeetingPlace does not control those conferences. Cisco Unified Videoconferencing MCU resources will be shared between the Cisco Unified MeetingPlace service and any SCCP services.

The service prefixes associated with the Cisco Unified MeetingPlace service will be used to route callers to Video Administration for Cisco Unified MeetingPlace and must not conflict with other routing patterns in the gatekeeper or Cisco Unified CallManager.

The following optional cards for the Cisco Unified Videoconferencing MCU are not supported:

Rate Matching card

Data Conferencing card

If your Cisco Unified MeetingPlace Audio Server is configured to use G.729, verify that the Cisco Unified Videoconferencing MCU is configured to support G.729. If you are using Cisco Unified Videoconferencing 4.x, a transcoder card may be needed. For information about specifying an audio codec, see the Cisco Unified Videoconferencing MCU Help.

We do not recommend changing settings in the Cisco Unified Videoconferencing MCU after users have begun to schedule conferences via Cisco Unified MeetingPlace if such changes reduce the number of available video conferences or ports. Before changing the settings in the Cisco Unified Videoconferencing MCU, see the Changing Settings in Other Components.

To configure your Cisco Unified Videoconferencing MCU to provide video content for Cisco Unified MeetingPlace conferences, do the following tasks in the order shown:

Log in to the Cisco IP/VC Administrator of the Cisco Unified Videoconferencing MCU that you want the Cisco Unified MeetingPlace server to use.

Choose MCU > Protocols > H.323.

Check the Enable H323 Protocol field.

In the Gatekeeper Address field, enter the IP Address of the Video Administration server with Gatekeeper Port 1719

Click Advanced H.323 Settings

In the Advanced H.323 Settings dialog box, confirm that Ras Port is set to 2719, Signalling Port is set to 2720, Registration Refresh Rate is set to 300seconds, and MCU Registration Mode is set to "MCU" (default setting).

Click OK.

Note: SCCP protocol can be configured for use by Cisco Unified CallManager video telephony ad-hoc calls if desired but any SCCP ports configured will take away from H.323 ports for Cisco Unified MeetingPlace Video Integration use. Size the MCU appropriately for both H.323 and SCCP use. For details, refer to the applicable Administrator Guide for your Cisco Unified Videoconferencing MCU at http://www.cisco.com/en/US/products/hw/video/ps1870/prod_maintenance_guides_list.html.

Choose Settings > Advanced.

Set the following parameters on the Advanced page:

In the Conferences Can Be Created Using field, click Scheduler Only.

In the Participants Can Join the Conference Using field, click Invite and Dial-in.

In the Ad Hoc Conferences Terminate When field, click Last Participant Leaves.

In the External Conference Authorization Policy field, click None.

We recommend that you check Disconnect Participants on Communications (ICMP) Failure and click Audio Failure in the Disconnect On field.

To save these settings, click Upload.

Repeat Step 1 through Step 10 for each Cisco Unified Videoconferencing MCU that is to be used with Cisco Unified MeetingPlace.

To Set the Audio Indication Interval (Optional)

If video participants join a conference that has not yet started, they must wait in the waiting room. Do this procedure to play an announcement while participants wait.

Click MCU, then click Settings.

Click Advanced .

Click Command.

The Advanced Command dialog box appears.

In the Advanced Command dialog box, do the following:

In the Available commands window, click First Audio Announcement Interval (msec).

Your selection appears in the Command field.

In the Parameter field, enter the value in milliseconds that you want Cisco Unified 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.

Click Send, then click Close.

Repeat Step 1 through Step 4 for each Cisco Unified Videoconferencing MCU that is to be used with Cisco Unified MeetingPlace.

You must create at least one Cisco Unified Videoconferencing MCU service for Cisco Unified MeetingPlace. Before you create a service in the Cisco Unified Videoconferencing MCU, verify that the media processor (MP) that the Cisco Unified Videoconferencing MCU uses supports Cisco Unified MeetingPlace.

Table: Media Processors That Support Video in Cisco Unified MeetingPlace

Cisco Unified Videoconferencing Media Processor

Software Supporting Cisco Unified MeetingPlace

Local Cisco Unified Videoconferencing MCU media processor

Release 4.0 or later

Cisco Unified Videoconferencing EMP

Release 3.0.5 or later

Cisco Unified Videoconferencing Rate Matching module

Does not support Cisco Unified MeetingPlace

Data Conferencing Card

Does not support Cisco Unified MeetingPlace

You can use one of the preconfigured Cisco Unified MeetingPlace service templates or manually create a Cisco Unified MeetingPlace service. The procedures vary slightly depending on whether you are using Cisco Unified Videoconferencing MCU Release 4.x or Release 5.x. Follow the procedures for your version.

Using Preconfigured Service Templates

Cisco Unified Videoconferencing MCU Release 4.x includes three preconfigured services that are designed for Cisco Unified MeetingPlace. Cisco Unified Videoconferencing MCU Release 5.x includes one preconfigured service that is designed for Cisco Unified MeetingPlace.

Note: The Cisco Unified MeetingPlace service prefixes appear automatically on the IP/VC Administrator Services page for new Cisco Unified Videoconferencing MCUs. However, these services do not appear when you upgrade your Cisco Unified Videoconferencing MCU. To display these services, you can use the restore factory defaults option. However, in doing so, you will lose your current configuration.

To Install the Cisco Unified MeetingPlace Service Templates on an Existing Cisco Unified Videoconferencing MCU Installation and Erase Existing Services

Run the Cisco Unified Videoconferencing MCU installer.

At the first install screen, click Customize.

Check the MCU Config File check box.

Continue with the installation.

After installation, log in to the Cisco Unified Videoconferencing MCU as administrator.

Click MCU on the sidebar and click the Services tab.

In the Services tab, choose the applicable template. 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.

See the appropriate table for the default service codes included with your MCU:

In the Service Description field, enter the description for this service that you want to appear on the Create Conference page.

In the Media Types section, check Video and uncheck Data. (Cisco Unified MeetingPlace provides data collaboration in conferences, so you must disable data collaboration in the Cisco Unified Videoconferencing MCU if it is currently enabled.)

Specify the number of ports that you want the Cisco Unified Videoconferencing MCU to reserve for each conference as follows:

In the Reserved Number of Parties field, enter 2.

Note: One of these ports is reserved for the Cisco Unified 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.

In the Maximum Number of Parties field, enter the total number of Cisco Unified Videoconferencing MCU ports that are available for conferences.

When you set view parameters, use the Cisco Unified MeetingPlace service template as a model. The templates are described in the 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.

Click the Edit View icon.

The Edit View dialog box appears.

In the Use Processor field, click the type of media processor that you want this service to use.

Note: The MP and RM optiondoes not support Cisco Unified MeetingPlace.

Click MP to specify that the service uses only the local media processor to process video conference calls.

Select the Video Settings Schemes profile that you want to edit and click the Edit button.

The Edit Video Scheme dialog box appears.

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 Unified MeetingPlace (and in Cisco Unified CallManager, if your network uses Cisco Unified CallManager.)

Note: Endpoints that are not capable of supporting this bandwidth receive only the conference audio unless dynamic scheme is allowed.

To save these Video Scheme changes and to close this dialog box, click OK.

To save these conference-view parameters and to close the Edit View dialog box, click OK.

To Save Your Service

To save your service, click OK at the bottom of the Service page.

Creating a Service Manually for Cisco Unified Videoconferencing MCU Release 5.x Only

To create a Cisco Unified Videoconferencing MCU service for Cisco Unified MeetingPlace do the following procedures in the order presented:

In the Service Description field, enter the description for this service that you want to appear on the Create Conference page.

In the Service Type field, select Standard Rate Video or High Rate Video.

Note: High Definition Video is not supported with Cisco Unified MeetingPlaceVideo Integration.

In the Data Collaboration section, uncheck the three check boxes. (Cisco Unified MeetingPlace provides data collaboration in conferences, so you must disable data collaboration in the Cisco Unified Videoconferencing MCU if it is currently enabled.)

Specify the number of ports that you want the Cisco Unified Videoconferencing MCU to reserve for each conference as follows:

Click the Advanced Management and Security button.

The Management and Security dialog box appears.

Click the Port Reservation & Limits tab.

In the Number of Ports Guaranteed (Reserved) When a Conference Starts field, enter 2.

Note: One of these ports is reserved for the Cisco Unified MeetingPlace server.

Check the Allow Conference to Grow Over Guaranteed Value check box if you would like conferences to be allowed to grow on an ad hoc basis if resources are available.

When you set view parameters, use the Cisco Unified MeetingPlace service template as a model. The templates are described in the 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. Other views are optional. Do not create multiple identical views for a single service code. Each view should be unique.

Click the Advanced Video Settings button.

The Advanced Video Settings dialog box appears.

In the Support Image Size Up To field, click the largest video format that your endpoints will use.

To save these conference-view parameters and to close the Advanced Video Settings dialog box, click OK.

To Save Your Service

To save your service, click Upload at the bottom of the Service page.

How to Define a Custom Video Layout for a Service Code

In the Cisco Unified MeetingPlace web meeting room, we support only two video layouts: Continuous Presence and Speaker Only. Therefore, the service code must have only two layouts defined: one with multiple participants and one with only one participant. (Usually, the main layout has multiple participants and the custom layout has only one participant).

Assuming that the main layout is already defined to have multiple participants, you need to define a custom layout with one participant only. Follow these steps to define the custom layout:

Procedure

Click the Services tab.

Double-click the name of the service prefix for which you want to create a custom video layout.

The Automatic Service Definition page appears.

Ensure that the Support presentation view (H.239) checkbox is not checked.

Click Advanced Video Settings...

Ensure that the Enable 3G videophone layout checkbox is not checked.

Check "Enable custom layouts".

Click Settings.

The Custom Layout Settings page appears.

Under Custom layout 2, for Layout role, enter Custom layout. The system displays parameters for the new custom layout.

Configuring NTP on Cisco Unified Videoconferencing MCUs

Network Time Protocol (NTP) must be configured on all MCUs. Perform the following procedure on all MCUs:

To Configure NTP on Cisco Unified Videoconferencing MCUs

In the Cisco Unified Videoconferencing Administrator interface, on the sidebar, click Board.

Make sure the Basics tab is selected.

Next to the Date/Time field, click Change.

The Change Time dialog box appears.

Select the NTP enabled check box.

Select the Synchronize with NTP Server Address radio button and enter the IP address of a network server clock.

Click Upload.

Configuring the Cisco IOS H.323 Gatekeeper

The Cisco IOS H.323 Gatekeeper is a neighbor to the Video Administration server internal (ECS) gatekeeper, which was installed with the Video Administration software. All endpoints and Cisco Unified CallManager trunks should be registered to the Cisco IOS H.323 Gatekeeper. All MCUs and ISDN gateways should be registered to the Video Administration's internal (ECS) gatekeeper.

In order for calls to correctly route to the Video Administration ECS gatekeeper, and to the Cisco Unified Videoconferencing MCUs, add a remote zone to your Cisco IOS H.323 Gatekeeper and a route for each service prefix that is configured on the MCUs.

* Add this entry for each service prefix that is configured on the Cisco Unified Videoconferencing MCUs.

For more information about routing calls through a Cisco IOS H.323 Gatekeeper, see the Cisco IOS H.323 Configuration Guide.

Configuring Video Administration for Cisco Unified MeetingPlace

Video Administration for Cisco Unified MeetingPlace must be installed and configured before installing Cisco Unified MeetingPlace Video Integration. If you have not already done so, do the following tasks on the Video Administration server:

Configure Video Meeting Types. Video Meeting Types on the Video Administration server must be synchronized with Service Codes on the Cisco Unified Videoconferencing MCUs. Add video meeting types on the Video Administration server and then download them to the Cisco Unified Videoconferencing MCUs. Alternatively, you can configure the service codes on the Cisco Unified Videoconferencing MCUs first and then upload them to the Video Administration server. For details on configuring service codes on the Cisco Unified Videoconferencing MCUs, see the About Configuring the Cisco Unified Videoconferencing MCU to Use Cisco Unified MeetingPlace. For details on uploading or downloading meeting types on the Video Administration server, see the Meeting Types.

In order for the audio and video portions of a conference to release ports at the same time, you must configure the Early Mtg Start (min) parameter on the Audio Server to match the Early Meeting Start parameter on Video Administration. To find the Early Mtg Start (min) parameter on the Audio Server, see the To Confirm the Early Meeting Start Parameter on the Audio Server. To configure the Early Meeting Start parameter on the Video Administration server to match the one on the Audio Server, see the Video Administration Configuration Tool chapter.

To Modify the Translation Table

If your Cisco Unified MeetingPlace system supports IP phones only, you do not need to change the translation table on the Cisco Unified MeetingPlace Audio Server.

If your Audio Server is configured for both PSTN and IP interfaces, and your organization does not have a certified Cisco Unified MeetingPlace technician, contact Cisco Unified MeetingPlace Professional Services to modify the translation table on the Audio Server. For information, contact your Cisco technical support representative.

About Setting the Audio Codec Negotiation Priority

Sound quality and bandwidth use are determined partly by the audio codec that the Cisco Unified MeetingPlace and Cisco Unified Videoconferencing systems use. The video signal of the video endpoint and its audio channel must share available bandwidth. As a result, better picture quality may degrade audio quality or delay audio transmission.

The Cisco Unified 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 on the Audio Server by using the setipcodec command. Use the following guidelines:

To make more bandwidth available for video, assign G.729 the highest priority.

Note: If the Audio Server is configured to use only G.729, verify that the Cisco Unified Videoconferencing MCU is configured to support G.729. A transcoder card may be needed.

To Confirm the Early Meeting Start Parameter on the Audio Server

In order for the audio and video portions of a conference to release ports at the same time, you must configure the Early Mtg Start (min) parameter on the Audio Server to match the Early Meeting Start parameter on the Video Administration server.

Go to the MeetingTime Configure tab.

Under the Company Specific Information heading, select Scheduling Parameters.

Scroll down in the panel on the right to the Early Mtg Start (min) field under the Run-time Params heading.

To Configure Network Time Protocol (NTP) on the Audio Server

Configuring Cisco Unified MeetingPlace H.323/SIP Gateway

The Cisco Unified MeetingPlace H.323/SIP Gateway connects the Cisco Unified MeetingPlace system to the network. The H.323/SIP Gateway also initiates the call that connects the Cisco Unified MeetingPlace Audio Server with the Cisco Unified Videoconferencing MCU.

If the H.323/SIP Gateway is not already connected to your network, use the following information to configure all necessary components:

If your Cisco Unified MeetingPlace system currently supports Cisco IP telephony, you do not need to make further changes to the H.323/SIP Gateway.

If Cisco Unified CallManager is not part of your network environment, the H.323/SIP Gateway can register itself directly to the H.323 gatekeeper. For instructions on configuring the H.323/SIP Gateway for use with an H.323 gatekeeper, see Cisco Unified MeetingPlace H.323/SIP IP Gateway, Release 5.3. If it is correctly configured, the H.323/SIP Gateway appears in the endpoint registration table in the gatekeeper.

If your Cisco Unified MeetingPlace system includes more than one H.323/SIP Gateway, and if the gateways are connecting to a gatekeeper, the E.164 number of each H.323/SIP Gateway must be unique. (The E.164 numbers do not need to be unique if they connect to Cisco Unified CallManager.)

Configuring Load-Balancing Configurations for Video Conferencing

In Cisco Unified MeetingPlace deployments for large numbers of users, multiple Cisco Unified MeetingPlace Web Conferencing servers can be configured in clusters, and meetings are distributed among the servers in a cluster. However, you can activate Cisco Unified MeetingPlace Video Integration on only one of those 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 Video Integration activated on it. However, in order to ensure that ad-hoc video conferences can occur, configure 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 Video Integration activated on it.

If your Cisco Unified MeetingPlace system is configured for load balancing, set the system to allow ad-hoc video conferencing.

Note: Do the following procedure even if Video Integration is not installed on a server in a cluster that includes load balancing.

To Configure Load Balancing for Video Conferencing

Sign in to the Cisco Unified MeetingPlace Web Conferencing interface by using your system manager password.

Click Admin.

Click Site Properties.

On the Web Conferencing Administration page for your site, confirm that Allow Web Load Balancing in Ad Hoc Video Meetings is set to No.

How Load Balancing Works

If the server with Cisco Unified 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 Unified 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 Video Integration is activated.

If Cisco Unified MeetingPlace Audio Server is configured to use only G.729, make sure your Cisco Unified Videoconferencing MCU supports this protocol.

If an endpoint is correctly configured to work with the Cisco Unified Videoconferencing MCU and configured to optimize audio quality according to the documentation that came with the product, no additional configuration is required for Video Integration. To optimize sound quality, see the troubleshooting tips in the Problems During a Video Conference.

When the system includes Cisco Unified 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 from meeting notifications that is not applicable, or add special instructions or other information that your users can use to attend conferences that include video.

If your environment includes Cisco Unified CallManager, set up Cisco Unified CallManager to route calls between the components that are involved in integrating video conferencing with Cisco Unified MeetingPlace.

There are many ways to set up Cisco Unified CallManager to work with Cisco Unified MeetingPlace Video Integration. For example, you can use the guidelines in the Cisco IP Video Telephony Solution Reference Network Design to set up Cisco Unified 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 Unified CallManager for your network is beyond the scope of this document; see the documentation for Cisco Unified CallManager or contact your Cisco technical support representative.

The MeetingPlace service prefix you defined on the Cisco Unified Videoconferencing MCU, followed by an exclamation point (!).

Description

A name that describes this route pattern.

Cisco Unified CallManager 4.0: Gateway or Route/Hunt List

Cisco Unified 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.

4. Click Insert.

5. Repeat Step 2 through Step 4 for each service code you defined on the Cisco Unified Videoconferencing MCU.

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 Unified MeetingPlace conferences without compromising security, one or more Cisco Unified 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; see Installing Web Conferencing for a Segmented Meeting Access Configuration.

Cisco Unified MeetingPlace Video Integration must be activated on one and only one server on which Web Conferencing is installed:

If it is activated behind the firewall, only internal participants can attend video conferences.

If it is activated in the DMZ, external participants can also attend.

Use the following information to determine whether you will activate Video Integration behind the firewall or in the DMZ:

If you want to host video conferences in the DMZ, you must install Video Integration on all Web Conferencing servers inside and outside the corporate firewall so that scheduling of meetings can be done from any Web Conferencing server. Activate only one Web Conferencing server in the DMZ area to host video conferences.

If Video Integration is activated 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 Video Integration is activated in the DMZ, and if the Video Administration for Cisco Unified MeetingPlace server is installed behind the firewall, open TCP port 3336 and 8080 through the firewall to allow you to connect Video Integration to the Video Administration server. (If you are running in secure mode, open port 8443 instead of 8080).

If Video Integration is activated 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.

Gathering Installation Values

You need to know the following in order to install Cisco Unified MeetingPlace Video Integration:

Item

Value

Determine which Web Conferencing server will host video conferences.

To enable scheduling of video conferences, Cisco Unified MeetingPlace Video Integration must be installed on all Web Conferencing servers, but only one of the Web Conferencing servers can host video conferences.

IP address or host name of the Video Administration for Cisco Unified MeetingPlace server.

The E.164 number or numbers assigned to the Cisco Unified MeetingPlace H.323/SIP Gateway.

If more than one Cisco Unified MeetingPlace H.323/SIP Gateway is connected to the same Cisco Unified 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 (;).

The account user name and password on the Video Administration for Cisco Unified MeetingPlace server that Video Integration will use to control video conferences.

Verify that you have completed all prerequisite tasks documented in this chapter.

Verify that Cisco Unified MeetingPlace is not in use. The Video Integration installer will stop the Web Conferencing master service and all subordinate services.

Verify that the current version of Web Conferencing is installed on the server.

Verify that the Video Administration server and the Cisco Unified Videoconferencing MCUs are available on the network (reachable via IP addresses).

Insert the Cisco Unified MeetingPlace Video Integration CD.

Run the Cisco Unified MeetingPlace Video Integration Setup.exe and follow the prompts. Enter the values that you collected in the Gathering Installation Values. Check the Host Video Conferences check box on only one Web Conferencing server.

All Cisco Unified MeetingPlace services will restart automatically after the installation is complete. Click Refresh in the Services window to update the view.

To verify that your system is configured correctly, click the orange Cisco Unified MeetingPlace icon in the system tray at the bottom of the computer screen and choose Eventlog.

If the installation is configured properly, the following message appears:

Cisco Unified MeetingPlace Video Integration must be installed on every Cisco Unified MeetingPlace Web Conferencing server to allow for scheduling of video conferences from any Web Conferencing server.

Only one Video Integration can be activated to host video conferences.

For information on compatibility to other Cisco Unified MeetingPlace components, see the Compatibility Matrix.

We do not support upgrading to Release 6.0 by using Terminal Services.