Cisco Unified MeetingPlace, Release 6.x -- Multiserver Meetings: Configuration Example

From DocWiki

Cisco Unified MeetingPlace, Release 6.x > Cisco Unified MeetingPlace Audio Server > Configuring > About Multiserver Meetings

Cisco Unified MeetingPlace, Release 6.x > Web Conferencing > Configuring > Configuring Web Conferencing for Multiserver Meetings

Multiserver meetings allow participants on different Cisco Unified MeetingPlace Audio Server systems to communicate with each other as if they were in the same meeting. When users schedule a multiserver meeting by using Cisco Unified MeetingPlace Web Conferencing, they designate one Audio Server system as the primary server responsible for connecting to other secondary Audio Server systems. Note the following limitations for multiserver meetings:

• Multiserver meetings do not span web servers. The web-conferencing portion of a multiserver meeting is scheduled on the web server associated with the primary Audio Server system.
• Video for multiserver meetings does not span multiple sites. Participants will always be able to hear video callers at other sites, but may not be able to see them.

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

See the following tasks:

• Gathering Server Information
• Creating Server Information Records in MeetingTime
• Configuring Cisco Unified MeetingPlace Web Servers for Multiserver Meetings

Contents 1 Gathering Server Information 1.1 Table: Table C-1 San Jose Cisco Unified MeetingPlace Audio Server Information 1.2 Table: Table C-2 New York Cisco Unified MeetingPlace Audio Server Information 1.3 Table: Table C-3 Boston Cisco Unified MeetingPlace Audio Server Information 2 Creating Server Information Records in MeetingTime 2.1 To Configure MeetingTime with Server Information Records 3 Configuring Cisco Unified MeetingPlace Web Servers for Multiserver Meetings 3.1 To Configure the Primary Web Server 3.2 To Configure the First Secondary Web Server 3.3 To Configure the Next Secondary Web Server

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. The following three tables are examples of server information records for the San Jose, New York, and Boston servers.

Table: 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: 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: Table C-3 Boston Cisco Unified MeetingPlace Audio Server Information

Field	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.

To Configure MeetingTime with Server Information Records

1. Log in to MeetingTime.
2. Configure the San Jose Cisco Unified MeetingPlace Audio Server system.
   1. Use MeetingTime to log in to the San Jose Cisco Unified MeetingPlace Audio Server system.
   2. Click Configure .
   3. Click Other MeetingPlace Server , then click the Query button on the right.
   4. Create three server records: one for San Jose, one for New York, and one for Boston based on the information you gathered in Table: San Jose Cisco Unified MeetingPlace Audio Server Information, Table: New York Cisco Unified MeetingPlace Audio Server Information, and Table: Boston Cisco Unified MeetingPlace Audio Server Information.
3. Configure the New York Cisco Unified MeetingPlace Audio Server system.
   1. Use MeetingTime to log in to the New York Cisco Unified MeetingPlace Audio Server system.
   2. Click Configure .
   3. Click Other MeetingPlace Server , then click the Query button on the right.
   4. Create two server records: one for San Jose and one for New York based on the information you gathered in Table: San Jose Cisco Unified MeetingPlace Audio Server Information and Table: New York Cisco Unified MeetingPlace Audio Server Information.
4. Configure the Boston Cisco Unified MeetingPlace Audio Server system.
   1. Use MeetingTime to log in to the Boston Cisco Unified MeetingPlace Audio Server system.
   2. Click Configure .
   3. Click Other MeetingPlace Server , then click the Query button on the right.
   4. Create two server records: one for San Jose and one for Boston based on the information you gathered in Table: San Jose Cisco Unified MeetingPlace Audio Server Information and Table: Boston Cisco Unified MeetingPlace Audio Server Information.

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.

To Configure the Primary Web Server

In this example, the primary web server is called "San Jose," and the secondary web servers are called "New York" and "Boston."

You must have a Cisco Unified MeetingPlace profile with System Manager privileges to do this procedure.

1. Sign in to Cisco Unified MeetingPlace Web Conferencing.
2. Click Admin , then click Web Server .
3. Configure the local web server:
   1. 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.
   2. For Web Server Name, change the entry from the NetBIO name to something more meaningful. This examples uses San Jose .
   3. Verify the value in the Hostname [Home Page] field. This value was set during installation; it should be the primary 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 .
   4. Click Submit .
4. Create additional web servers by entering or choosing appropriate values in the Web Server Name and Hostname fields.
   1. 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 .
   2. 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 .
5. Click the Back button to return to the main Administration page.
6. Configure the local site.
   1. From the main Administration page, click Site .
   2. 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.
   3. For Site Name, change the entry from the NetBIO name to something more meaningful. This example uses San Jose .
   4. Click Submit .
7. Create additional sites by entering or choosing appropriate values in the Site Name and External Web Server fields.
   1. 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 .
   2. To create the second remote web server in this example, for Site Name, enter Boston . For External Web Server, choose Boston , then click Submit .
8. Click the Back button to return to the main Administration page.
9. Configure a round-trip site route between two sites.
   1. From the main Administration page, click Site Route .
   2. 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.

To Configure the First Secondary Web Server

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

You must have a Cisco Unified MeetingPlace profile with System Manager privileges to do this procedure.

1. Sign in to Cisco Unified MeetingPlace Web Conferencing.
2. Click Admin , then click Web Server .
3. Configure the local web server:
   1. 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.
   2. For Web Server Name, change the entry from the NetBIO name to something more meaningful. This examples uses New York .
   3. Verify the value in the Hostname [Home Page] field. This value was set during installation; it should be the primary 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 .
   4. Click Submit .
4. Create additional web servers by entering or choosing appropriate values in the Web Server Name and Hostname fields.

   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 .

5. Click the Back button to return to the main Administration page.
6. Configure the local site.
   1. From the main Administration page, click Site .
   2. 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.
   3. For Site Name, change the entry from the NetBIO name to something more meaningful. This example uses New York .
   4. Click Submit .
7. Create additional sites by entering or choosing appropriate values in the Site Name and External Web Server fields.

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

8. Click the Back button to return to the main Administration page.
9. Configure a round-trip site route between two sites.
   1. From the main Administration page, click Site Route .
   2. 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.

To Configure the Next Secondary Web Server

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

You must have a Cisco Unified MeetingPlace profile with System Manager privileges to do this procedure.

1. Sign in to Cisco Unified MeetingPlace Web Conferencing.
2. Click Admin , then click Web Server .
3. Configure the local web server:
   1. 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.
   2. For Web Server Name, change the entry from the NetBIO name to something more meaningful. This examples uses Boston .
   3. Verify the value in the Hostname [Home Page] field. This value was set during installation; it should be the primary 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 .
   4. Click Submit .
4. Create additional web servers by entering or choosing appropriate values in the Web Server Name and Hostname fields.

   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 .

5. Click the Back button to return to the main Administration page.
6. Configure the local site.
   1. From the main Administration page, click Site .
   2. 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.
   3. For Site Name, change the entry from the NetBIO name to something more meaningful. This example uses Boston .
   4. Click Submit .
7. Create additional sites by entering or choosing appropriate values in the Site Name and External Web Server fields.

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

8. Click the Back button to return to the main Administration page.
9. Configure a round-trip site route between two sites.
   1. From the main Administration page, click Site Route .
   2. 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.