Configuration Guide for Cisco Unified MeetingPlace Web Conferencing Release 5.3.
Configuring Multiserver Meetings

Table Of Contents

Configuring Multiserver Meetings

Requirements

Overview

Example

Gathering Server Information

Creating Server Information Records in MeetingTime

Configuring Cisco Unified MeetingPlace Web Servers for Multiserver Meetings

Troubleshooting

Manually Refreshing a Site


Configuring Multiserver Meetings


Detailed information about how to configure a multiserver meeting on the Cisco Unified MeetingPlace Audio Server system is described in the "About Multiserver Meetings" section of the Administrator Guide for Cisco Unified MeetingPlace Audio Server Release 5.3. This section describes how to complete a multiserver meeting configuration by using a concrete example.

Topics in this section include:

Requirements

Overview

Example

Troubleshooting

Requirements

Before configuring multiserver meetings, make sure that your Cisco Unified MeetingPlace systems meet the following requirements.

Make sure that user profiles are the same across all systems. Users cannot schedule multiserver meetings if their profiles on all affected servers do not match.

Make sure that all Cisco Unified MeetingPlace system parameters that control scheduling behavior are the same across all systems. For example, if you set "Allow Vanity ID" to Yes on one system, make sure that you set "Allow Vanity ID" to Yes on all other Cisco Unified MeetingPlace systems affected by your multiserver meeting configuration.


Note After a meeting is scheduled on the primary server, the secondary server receives a request to schedule a meeting with the same meeting ID. However, if "Allow vanity ID" is set to No on the secondary server, a blank meeting ID request is sent to the secondary server so that the secondary server can auto-generate a meeting ID and successfully schedule the meeting.


Overview

The multiserver meeting feature requires configuration of both the Cisco Unified MeetingPlace Audio Server system and Cisco Unified MeetingPlace Web Conferencing. Configuration is therefore completed in both MeetingTime and the Cisco Unified MeetingPlace Web Conferencing online administrative interface.

Multiserver meeting configuration is composed of the following tasks:

1. Create server information records for the Cisco Unified MeetingPlace Audio Server systems involved in multiserver meetings. This task is completed in MeetingTime.

Detailed information about this task is provided in the "Creating Server Information Records for Cisco Unified MeetingPlace Servers" section of the Administrator Guide for Cisco Unified MeetingPlace Audio Server Release 5.3.

2. Configure the web server, site, and site routes for the web servers involved in multiserver meetings. These tasks are completed in the Cisco Unified MeetingPlace Web Conferencing online administrative interface.

Example

The following example uses three Cisco Unified MeetingPlace systems: San Jose, New York, and Boston. Each Cisco Unified MeetingPlace system is composed of a Cisco Unified MeetingPlace Audio Server system and a corresponding Cisco Unified MeetingPlace web server. In this example, San Jose is chosen as the primary Cisco Unified MeetingPlace system. Both New York and Boston are chosen as secondary Cisco Unified MeetingPlace systems.

This provides us with the following multiserver meeting scenarios:

Between New York and San Jose, either one can act as the primary Cisco Unified MeetingPlace Audio Server system while the other acts as the secondary server.

Between Boston and San Jose, either one can act as the primary Cisco Unified MeetingPlace Audio Server system while the other acts as the secondary server.

New York and Boston are not configured for multiserver meetings in a primary-secondary relationship.

This example consists of the following tasks:

Gathering Server Information

Creating Server Information Records in MeetingTime

Configuring Cisco Unified MeetingPlace Web Servers for Multiserver Meetings

Gathering Server Information

Before two Cisco Unified MeetingPlace servers can connect, each server must have information about the other server entered into its database. Just as profiles identify Cisco Unified MeetingPlace users, each server must have a Server Information record to identify it to the other servers. Table C-1, Table C-2, and Table C-3 are examples of server information records for the San Jose, New York, and Boston servers.

Table C-1 San Jose Cisco Unified MeetingPlace Audio Server Information

Field
Server Information

Name

San Jose

ID number

1000

Phone number

408-123-1234

Ethernet address

0001af00aa00

Web Publisher Location

http://172.27.15.156

Data conference active?

Yes

Server number

0


Table C-2 New York Cisco Unified MeetingPlace Audio Server Information

Field
Database Record #1

Name

New York

ID number

2000

Phone number

212-123-1234

Ethernet address

0001af00aa11

Web Publisher Location

http://172.27.15.154

Data conference active?

Yes

Server number

0


Table C-3 Boston Cisco Unified MeetingPlaceAudio Server Information

MeetingTime Parameter
Database Record #1

Name

Boston

ID number

3000

Phone number

617-123-1234

Ethernet address

0001af00aa22

Web Publisher Location

http://172.27.15.155

Data conference active?

Yes

Server number

00


Creating Server Information Records in MeetingTime

In this example, San Jose is the primary Cisco Unified MeetingPlace Audio Server system. New York and Boston are secondary Cisco Unified MeetingPlace Audio Server systems.

Before You Begin

Gather information about the San Jose, New York, and Boston servers.

Procedure


Step 1 Log in to MeetingTime.

Step 2 Configure the San Jose Cisco Unified MeetingPlace Audio Server system.

a. Use MeetingTime to log in to the San Jose Cisco Unified MeetingPlace Audio Server system.

b. Click Configure.

c. Click Other MeetingPlace Server; then, click the Query button on the right.

d. Create three server records: one for San Jose, one for New York, and one for Boston based on the information you gathered in Table C-1, Table C-2, and Table C-3.

Step 3 Configure the New York Cisco Unified MeetingPlace Audio Server system.

a. Use MeetingTime to log in to the New York Cisco Unified MeetingPlace Audio Server system.

b. Click Configure.

c. Click Other MeetingPlace Server; then, click the Query button on the right.

d. Create two server records: one for San Jose and one for New York based on the information you gathered in Table C-1 and Table C-2.

Step 4 Configure the Boston Cisco Unified MeetingPlace Audio Server system.

a. Use MeetingTime to log in to the Boston Cisco Unified MeetingPlace Audio Server system.

b. Click Configure.

c. Click Other MeetingPlace Server; then, click the Query button on the right.

d. Create two server records: one for San Jose and one for Boston based on the information you gathered in Table C-1 and Table C-3.


Configuring Cisco Unified MeetingPlace Web Servers for Multiserver Meetings

Complete the following to configure a Cisco Unified MeetingPlace web server to participate in a multiserver meeting:

Configure the local web server

Create and configure additional web servers that will participate in multiserver meetings

Configure the local site

Create and configure additional sites that will represent other Cisco Unified MeetingPlace systems

Create site route between sites

In this example, we configure three web servers: San Jose, New York, and Boston.

Configuring the Primary Web Server

This section describes how to configure the primary web server so that users can schedule multiserver meetings. In this example, the primary web server is called "San Jose" and secondary web servers are called "New York" and "Boston".

Before You Begin

You must have a Cisco Unified MeetingPlace profile with System Manager privileges.

Procedure


Step 1 Sign in to Cisco Unified MeetingPlace Web Conferencing.

Step 2 Click Admin; then, Web Server.

Step 3 Configure the local web server:

a. From the "View" section of the page, click the name of the local web server.

Information about this server populates the "Edit" section of the page.

b. For Web Server Name, change the entry from the NetBIO name to something more meaningful. This examples uses San Jose.

c. For Hostname, enter the IP address or FQDN of the web server. This entry must be resolvable from the network of your intended users. This example uses the IP address 172.27.15.156.

d. Click Submit.

Step 4 Create additional web servers by entering or choosing appropriate values in the Web Server Name and Hostname fields.

a. To create the first remote web server in this example, for Web Server Name, enter New York. For Hostname, enter 172.27.15.154; then, click Submit.

b. To create the second remote web server in this example, for Web Server Name, enter Boston. For Hostname, enter 172.27.15.155; then, click Submit.

Step 5 Click the Back button to return to the main Administration page.

Step 6 Configure the local site.

a. From the main Administration page, click Site.

b. From the "View" section of the page, click the name of the local site.

Information about this site populates the "Edit" section of the page.

c. For Site Name, change the entry from the NetBIO name to something more meaningful. This example uses San Jose.

d. Click Submit.

Step 7 Create additional sites by entering or choosing appropriate values in the Site Name and External Web Server fields.

a. To create the first remote site in this example, for Site Name, enter New York. For External Web Server, choose New York; then, click Submit.

b. To create the second remote web server in this example, for Site Name, enter Boston. For External Web Server, choose Boston; then, click Submit.

Step 8 Click the Back button to return to the main Administration page.

Step 9 Configure a round-trip site route between two sites.

a. From the main Administration page, click Site Route.

b. From the "Add" section, choose sites for From: and To: and then click Add.

In this example, we create four site routes: from San Jose to New York, from New York to San Jose, from San Jose to Boston, from Boston to San Jose.


Configuring the First Secondary Web Server

This example uses New York as a secondary web server in this multiserver meeting configuration.

Before You Begin

You must have a Cisco Unified MeetingPlace profile with System Manager privileges.

Procedure


Step 1 Sign in to Cisco Unified MeetingPlace Web Conferencing.

Step 2 Click Admin; then, Web Server.

Step 3 Configure the local web server:

a. From the "View" section of the page, click the name of the local web server.

Information about this server populates the "Edit" section of the page.

b. For Web Server Name, change the entry from the NetBIO name to something more meaningful. This examples uses New York.

c. For Hostname, enter the IP address or FQDN of the web server. This entry must be resolvable from the network of your intended users. This example uses the IP address 172.27.15.154.

d. Click Submit.

Step 4 Create additional web servers by entering or choosing appropriate values in the Web Server Name and Hostname fields.

a. To create the remote web server in this example, for Web Server Name, enter San Jose. For Hostname, enter 172.27.15.156; then, click Submit.

Step 5 Click the Back button to return to the main Administration page.

Step 6 Configure the local site.

a. From the main Administration page, click Site.

b. From the "View" section of the page, click the name of the local site.

Information about this site populates the "Edit" section of the page.

c. For Site Name, change the entry from the NetBIO name to something more meaningful. This example uses New York.

d. Click Submit.

Step 7 Create additional sites by entering or choosing appropriate values in the Site Name and External Web Server fields.

a. To create the remote site in this example, for Site Name, enter San Jose. For External Web Server, choose San Jose; then, click Submit.

Step 8 Click the Back button to return to the main Administration page.

Step 9 Configure a round-trip site route between two sites.

a. From the main Administration page, click Site Route.

b. From the "Add" section, choose sites for From: and To: and then click Add.

In this example, we create two site routes: from New York to San Jose, from San Jose to New York.


Configuring the Next Secondary Web Server

This example uses Boston as another secondary web server in this multiserver meeting configuration.

Before You Begin

You must have a Cisco Unified MeetingPlace profile with System Manager privileges.

Procedure


Step 1 Sign in to Cisco Unified MeetingPlace Web Conferencing.

Step 2 Click Admin; then, Web Server.

Step 3 Configure the local web server:

a. From the "View" section of the page, click the name of the local web server.

Information about this server populates the "Edit" section of the page.

b. For Web Server Name, change the entry from the NetBIO name to something more meaningful. This examples uses Boston.

c. For Hostname, enter the IP address or FQDN of the web server. This entry must be resolvable from the network of your intended users. This example uses the IP address 172.27.15.155.

d. Click Submit.

Step 4 Create additional web servers by entering or choosing appropriate values in the Web Server Name and Hostname fields.

a. To create the remote web server in this example, for Web Server Name, enter San Jose. For Hostname, enter 172.27.15.156; then, click Submit.

Step 5 Click the Back button to return to the main Administration page.

Step 6 Configure the local site.

a. From the main Administration page, click Site.

b. From the "View" section of the page, click the name of the local site.

Information about this site populates the "Edit" section of the page.

c. For Site Name, change the entry from the NetBIO name to something more meaningful. This example uses Boston.

d. Click Submit.

Step 7 Create additional sites by entering or choosing appropriate values in the Site Name and External Web Server fields.

a. To create the remote site in this example, for Site Name, enter San Jose. For External Web Server, choose San Jose; then, click Submit.

Step 8 Click the Back button to return to the main Administration page.

Step 9 Configure a round-trip site route between two sites.

a. From the main Administration page, click Site Route.

b. From the "Add" section, choose sites for From: and To: and then click Add.

In this example, we create two site routes: from Boston to San Jose, from San Jose to Boston.


Troubleshooting

Q. I do not see the "Multi-Server Meeting" radio button in the scheduling page.

A. Your profile may not have the correct setting to allow you to schedule multiserver meetings. Use MeetingTime to check the "Call call other server?" profile setting located in the "Outdial Meeting Defaults" section.

Q. How do I change the displayed server name of a particular site that appears under the Add section of the Invited Servers page? For example, a secondary server is listed as Name = chamberlain and Site = New York.

A. The information displayed under the Add section comes from the Cisco Unified MeetingPlace Audio Server system that is connected to your current web server. In this example, we are on the San Jose web server, so you need to go to the San Jose Cisco Unified MeetingPlace Audio Server system to correct this problem.

Use MeetingTime to log in to the San Jose Cisco Unified MeetingPlace audio server. Under the "Other MeetingPlace Server" section, change the name "chamberlain". Manually trigger a site refresh to have the updated information propagate the database of the web server and subsequently display in the Cisco Unified MeetingPlace Web Conferencing user interface. For instructions, see the "Manually Refreshing a Site" section.

Q. Why does the name of my secondary server appear differently in two separate areas of the Invited Servers page? For example, my secondary server appears with the correct name (i.e., Boston) in the "Add" section of the page. However, after I invite the server it appears in the "View" section of the page as mp-vc-01.

A. The information displayed in the "View" section comes from the actual Cisco Unified MeetingPlace audio server. In this example, the name "mp-vc-01" comes from the settings configured on the Boston Cisco Unified MeetingPlace audio server.

Use MeetingTime to log in to the Boston Cisco Unified MeetingPlace audio server. Under the "Other MeetingPlace Server" section, change the name "mp-vc-01". Manually trigger a site refresh to have the updated information propagate the database of the web server and subsequently display in the Cisco Unified MeetingPlace Web Conferencing user interface. For instructions, see the "Manually Refreshing a Site" section.

Q. I added a new site called "London" in the Site administrative page. However, when I go to the Site Routes administrative page, "London" is not available in the Site drop-down list.

A. The database has not been updated. Force an update by completing the task described in the "Manually Refreshing a Site" section.

Manually Refreshing a Site

Before You Begin

You must have a Cisco Unified MeetingPlace profile with System Manager privileges.

Procedure


Step 1 Sign in to Cisco Unified MeetingPlace Web Conferencing.

Step 2 Click Admin; then, Site.

Step 3 From the "View" section of the page, click the name of a site so that information about this site populates the "Edit" section of the page.

Step 4 Without changing anything, click Submit.

Step 5 Repeat Step 3 and Step 4 for all other sites.