Installation, Upgrade, and Migration Guide for Cisco Unified MeetingPlace Release 8.6
Upgrading to Cisco Unified MeetingPlace Release 8.6
Downloads: This chapterpdf (PDF - 340.0KB) The complete bookPDF (PDF - 5.68MB) | Feedback

Upgrading to Cisco Unified MeetingPlace Release 8.6

Table Of Contents

Upgrading to Cisco Unified MeetingPlace Release 8.6

About the Upgrade

New in Release 8.6

Upgrade Process

Cisco WebEx Site

Preserved Data

How To Prepare for an Upgrade

Best Practices for an Upgrade

How To Upgrade a Multinode System

Preparing to Upgrade a Multinode System

How to Upgrade the Application Server Software

About Upgrading the Application Server Software

Preparing to Upgrade the Application Server Software

Determining Which Procedure to Follow

Upgrading the Application Server by Using the Console

Upgrading the Application Server Remotely

Upgrading a Failover Deployment in an Audio System or a System with MeetingPlace Scheduling (Cisco Unified MeetingPlace 8.5.5)

Upgrading a Failover Deployment in an Audio-Only System or a System with MeetingPlace Scheduling (Cisco Unified MeetingPlace 8.5.4 and Earlier)

Completing the Application Server Software Upgrade

Stopping Maintenance Mode

Updating Email Notifications

How to Test the Application Server Software Upgrade

Troubleshooting the Application Server Software Upgrade

How to Upgrade the Web Server

Preparing to Upgrade the Web Server

Backing Up Data

Working With the Cisco Security Agent (CSA)

Uninstalling the Cisco Security Agent (CSA)

Upgrading the Web Server Software to Release 8.6

Reinstalling the Cisco Security Agent (CSA)

Reconfiguring the Application Server Connection in the Gateway SIM

How to Upgrade the Software for the Hardware Media Server

How to Upgrade Microsoft Outlook for Cisco Unified MeetingPlace

Using Windows Installer (MSI)

Using setup.exe

Troubleshooting Your Upgrade

Troubleshooting a Single Node System

Troubleshooting a Multinode System

Testing that the Upgraded System Works Correctly


Upgrading to Cisco Unified MeetingPlace Release 8.6


Release 8.6
Revised: 10/30/13

Complete the upgrade procedure in this module if you have an existing Cisco Unified MeetingPlace Release 8.5.5 system and want to upgrade to Release 8.6.


Note This upgrade module covers the upgrade of the following Release 8.6 components (Application Server, Web Server, Cisco WebEx Node for MCS, Hardware Media Server, and Microsoft Outlook plug-in). If your system includes any Cisco Unified MeetingPlace integration, then refer to the specific integration module for your release. See the Configuration Guide for Cisco Unified MeetingPlace Release 8.6.


This upgrade procedures comprises the following

About the Upgrade

How To Prepare for an Upgrade

How To Upgrade a Multinode System

How to Upgrade the Application Server Software

How to Upgrade the Web Server

How to Upgrade Microsoft Outlook for Cisco Unified MeetingPlace

Troubleshooting Your Upgrade

Testing that the Upgraded System Works Correctly

About the Upgrade

New in Release 8.6

Upgrade Process

Cisco WebEx Site

Preserved Data

New in Release 8.6

Cisco Unified MeetingPlace Release 8.6 supports the following:

Cisco Unified MeetingPlace plug-in support for Microsoft Outlook 2013 (32-bit and 64-bit editions) for audio-only deployments and migrated MeetingPlace-scheduling deployments only.

Microsoft Exchange 2013

Windows 8 Professsional (32-bit and 64-bit editions)

Cisco Unified Communications Manager Release 10

IBM Domino Server 8.5.3 (x86 and x64)

IBM Lotus Notes client 8.5.3 and template 8.5.3

VMware ESXi 5.1

In addition, Cisco Unified MeetingPlace Release 8.6 works with the following browsers:

Windows tested browsers:

Internet Explorer 10

Mozilla FireFox 22.

Google Chrome 28

Macintosh tested browser:

Apple Safari 5.1.7

For a complete list, see http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_release_notes_list.html.

Upgrade Process

Follow these steps to upgrade to Cisco Unified MeetingPlace Release 8.6 from Release 8.5.5.

Procedure

Step #
Step Description
Related Topics

Step 1 

(Deployments with MeetingPlace scheduling or audio only) Notify end users of the planned upgrade and system downtime.

Note Multinode systems do not experience downtime; just reduced capacity as nodes are individually upgraded.

 

Step 2 

Upgrade your existing Application Server data.

How to Upgrade the Application Server Software

Step 3 

As needed, upgrade the Release 8.5.5 Web Server software.

How to Upgrade the Web Server

Step 4 

The Cisco WebEx Node for MCS has not changed after Release 8.5.2.

If you are at Release 8.5.1, then upgrade the Cisco WebEx Node for MCS to Release 8.5.2 by reinstalling Release 8.5.2 on the same machine (you are overwriting the existing Cisco WebEx Node for MCS software with Release 8.5.2 software).

Note The Cisco WebEx Node for MCS is optional.

Note You may choose to install the Cisco WebEx Node on a virtual machine.

Step 5 

As needed, upgrade the Microsoft Outlook for Cisco Unified MeetingPlace integration.

How to Upgrade Microsoft Outlook for Cisco Unified MeetingPlace

Step 6 

Test that the upgraded system works correctly.

Testing that the Upgraded System Works Correctly

Step 7 

Inform end users that the system has been successfully upgraded.

 

Cisco WebEx Site

When you upgrade to Cisco Unified MeetingPlace Release 8.6, you must be using the Cisco WebEx T27L SP27 or later Release.

If you are using an earlier release, you must upgrade to the Cisco WebEx T27L SP27 Release. Notify the Cisco WebEx Client Success Manager (CSM) that you plan to upgrade to Cisco Unified MeetingPlace Release 8.6 and then ask the CSM to upgrade your release of Cisco WebEx. In order to avoid a delay in implementing your upgrade, we recommend that you schedule the Cisco WebEx upgrade as far in advance as possible of your Cisco Unified MeetingPlace upgrade.

Preserved Data

All the Release 8.5.5 data is retained when your upgrade to Release 8.6. Note the following:

If the Microsoft Exchange server is under the SSL certificate, then you must reapply the certificate on the Application Server, for notifications to work.

On the Web Server, all customization changes not made from the Administration Center (such as *.css files, and so on) are not preserved.

How To Prepare for an Upgrade

Best Practices for an Upgrade

How To Upgrade a Multinode System

Best Practices for an Upgrade

Be sure the usernames have the necessary access permissions to perform the various procedures in this module.

When upgrading the Cisco Unified MeetingPlace system remotely, be sure your LAN connection supports at least 1 Gb/s (gigabits per second).

We highly recommend creating both a backup and archive, in case you need to revert to your legacy system. Sign in to the Cisco Unified MeetingPlace Administration Center and select Maintenance > Backup and Archive.

Deployments that are MeetingPlace scheduling or Audio Only

We recommend that you schedule to start and finish the upgrade of your Cisco Unified MeetingPlace system during a time when there is low activity and not much meeting traffic; for example, over a weekend or a period of extended downtime.

Have a valid DNS service configuration. This is mandatory for correct operation of the Cisco Unified MeetingPlace system. The DNS server is expected to answer the ICMP echo request from the Application Server with ICMP echo reply in under 200 milliseconds.

You can test your DNS service by entering on the command-line interface, ping <DNS_IP_Address>. You should get a response in under 200 milliseconds.

How To Upgrade a Multinode System

In a multinode system, the nodes can be upgraded individually, one at a time. During the upgrade, the Cisco Unified MeetingPlace system continues to hold conferences, though at a reduced capacity. However, configuration changes are limited until the upgrade is complete.


Note Avoid any unusual operations (such as bulk import of users) during the upgrade. Perform these operations before, or after, an upgrade.


Preparing to Upgrade a Multinode System

Be sure all the nodes are up and running, before starting your upgrade.

Sign in to the Administration Center and select Topology Management. Make sure all servers are connected and their Operational Status is good (green).

Make sure the Primary Meeting Director node is the Active Meeting Director node.

We strongly recommend that you assign regional master nodes as Meeting Director nodes.

The procedure below assumes the Meeting Director nodes are regional master nodes, and not leaf nodes.

Confirm that a Secondary Meeting Director node has been assigned. If not, assign a node as the secondary Meeting Director node.

The system can continue to hold conferences while the primary Meeting Director is being upgraded. The Secondary Meeting Director takes over as the Active Meeting Director during this time.

Order of Multinode Upgrades


Note Cisco suggests you upgrade each node individually, one at a time. This enables the Cisco Unified MeetingPlace system to continue to hold conferences with the remaining nodes, at reduced capacity, during the upgrade. While you could upgrade nodes simultaneously, the likely result, depending on your system setup, is that the system will be down during the upgrade.


The overall process is to upgrade conferencing nodes first, followed by the Secondary Meeting Director, then the Primary Meeting Director.


Tip Schedule maintenance mode for each node, ahead of time, to avoid the sudden closing of existing meetings on that node.


Single Region Upgrade

Multi-Region Upgrade

Single Region Upgrade

For details, see Upgrading a Multinode System.

1. Upgrade all the leaf nodes, except the Secondary Meeting Director node.

2. Upgrade the Secondary Meeting Director node.


Note Be sure to finish the upgrade of the Secondary Meeting Director before starting the upgrade of the Primary Meeting Director.


3. Upgrade the Primary Meeting Director node.


Note Be sure to wait until the Operational Status is green for all the other nodes in your system. Then stop the maintenance mode for the upgraded Primary Meeting Director.


Multi-Region Upgrade

For details, see Upgrading a Multinode System.

1. Start your upgrade with any region that does not contain a Meeting Director node:

a. Upgrade all leaf nodes.

b. Upgrade the regional master node.

2. Upgrade the leaf nodes in the region with the Secondary Meeting Director.

3. Upgrade the leaf nodes in the region with the Primary Meeting Director.

4. Upgrade the Secondary Meeting Director.


Note Be sure to finish the upgrade of the Secondary Meeting Director before starting the upgrade of the Primary Meeting Director.


5. Upgrade the Primary Meeting Director.


Note Be sure to wait until the Operational Status is green for all the other nodes in your system. Then stop the maintenance mode for the upgraded Primary Meeting Director.


Upgrading a Multinode System

Procedure


Step 1 Put each node in maintenance mode before the upgrade. Sign in to the Administration Center. Select Maintenance > Maintenance Configuration, then Start Maintenance Mode Now.

When you put a node in maintenance mode, existing meetings hosted on that node are closed.

Step 2 Execute the upgrade binary. See How to Upgrade the Application Server Software.

After the upgrade is complete, and the node has rebooted, then check that all Cisco Unified MeetingPlace services are running in good state.

Step 3 Stop the maintenance mode for the upgraded node. Sign in to the Administration Center. Select Maintenance > Maintenance Configuration, then Stop Maintenance Mode Now.

Step 4 Repeat Step 1 to Step 4 to upgrade each node until all the nodes are upgraded, except for the Meeting Director nodes.

Step 5 Put the Secondary Meeting Director into maintenance mode and upgrade it (repeat Step 1 to Step 3).

During the upgrade, replication stops between the Primary and Secondary Meeting Director nodes.

Step 6 Stop the maintenance mode for the Secondary Meeting Director.


Tip Wait until the Secondary Meeting Director is upgraded and taken out of maintenance mode, then upgrade the Primary Meeting Director. Wait until you see this message at the Cisco Unified MeetingPlace Administration Center > Maintenance > Maintenance Configuration > Message: This node is not in maintenance mode. MeetingPlace application is running.


Step 7 Put the Primary Meeting Director into maintenance mode.

The Secondary Meeting Director becomes the active Meeting Director node.

Step 8 Complete Step 2 and 3 to upgrade the Primary Meeting Director.


Note Once the Primary Meeting Director is upgraded, replication starts with data synchronized from the Secondary Meeting Director (active node) to the Primary Meeting Director. Any data, including records of meetings that were started and completed, when the Secondary Meeting Director was upgraded, is lost. (The data was lost because it existed only on the Release 8.5 Primary Meeting Director, and was never synchronized with the Release 8.5.5 Secondary Meeting Director.)


Step 9 Wait until the Operational Status is green for all the other nodes in your system. Then stop the maintenance mode for the upgraded Primary Meeting Director.

The Primary Meeting Director becomes the active Meeting Director node.


Related Topics

"Configuring your Multinode Topology for Cisco Unified MeetingPlace" in the Configuration Guide for Cisco Unified MeetingPlace

How to Upgrade the Application Server Software

About Upgrading the Application Server Software

Preparing to Upgrade the Application Server Software

Determining Which Procedure to Follow

Upgrading the Application Server by Using the Console

Upgrading the Application Server Remotely

Upgrading a Failover Deployment in an Audio System or a System with MeetingPlace Scheduling (Cisco Unified MeetingPlace 8.5.5)

Upgrading a Failover Deployment in an Audio-Only System or a System with MeetingPlace Scheduling (Cisco Unified MeetingPlace 8.5.4 and Earlier)

Completing the Application Server Software Upgrade

How to Test the Application Server Software Upgrade

Troubleshooting the Application Server Software Upgrade

About Upgrading the Application Server Software

An upgrade keeps the database that holds the Hardware Media Server configuration information.

We support using Integrated Lights-Out (iLO) to install/upgrade the Application Server software. This standard only applies to the Cisco MCS 7845-H2. For information about installing, configuring, and using iLO, see http://h18000.www1.hp.com/products/servers/management/ilo/.

The upgrade program retains the same deployment that you currently have on your existing Cisco Unified MeetingPlace system.

Preparing to Upgrade the Application Server Software


Caution Do not run any other processes or tasks on your systems during an upgrade.


Note Be sure the Application Server node is in maintenance mode. Sign in to the Administration Center. Select Maintenance > Maintenance Configuration, then Start Maintenance Mode Now.


Do not uninstall the Application Server software before the upgrade.

The Cisco Unified MeetingPlace system must be running when you perform an upgrade. Do not turn off the Cisco Unified MeetingPlace services.

If you have automatic backups/archives enabled, then turn this off when you upgrade the Application Server software.

Make sure your system is functional before starting the upgrade (the Operational Status of each node is green)

Determining Which Procedure to Follow

Depending on the configuration of your Application Server, follow one of these steps:

If your Application Server is in a failover deployment and you want to continue MeetingPlace scheduling—follow the procedure in Upgrading a Failover Deployment in an Audio System or a System with MeetingPlace Scheduling (Cisco Unified MeetingPlace 8.5.5) or Upgrading a Failover Deployment in an Audio-Only System or a System with MeetingPlace Scheduling (Cisco Unified MeetingPlace 8.5.4 and Earlier). After the upgrade, reconfigure the system for database replication.

Otherwise, follow the procedure in either the Upgrading the Application Server by Using the Console or the Upgrading the Application Server Remotely.

Upgrading the Application Server by Using the Console

Before You Begin

Complete Determining Which Procedure to Follow.

Take the Audio Blade offline.


Note Be sure the Application Server node is in maintenance mode, or the upgrade program will terminate.


Procedure


Step 1 Go to Cisco.com and find the upgrade binary: http://www.cisco.com/cisco/software/navigator.html and select Products > Voice and Unified Communications > Unified Communications Applications > Conferencing > Cisco Unified MeetingPlace > Cisco Unified MeetingPlace 8.6 > Unified MeetingPlace Application Server. The naming convention will be similar to CUMP_AppServerUpgrade_<version>.bin, where <version> is the version number to which you are upgrading.

Step 2 Save the file to a convenient location.

Step 3 Enter md5sum CUMP_AppServerUpgrade_<version>.bin to determine the checksum of the file that you downloaded. Compare this value to the checksum value of the file that is posted on the download page on Cisco.com.

Step 4 Sign in to the Application Server command-line interface as the root user.

Step 5 Transfer the CUMP_AppServerUpgrade_<version>.bin file to the Application Server to the /tmp folder.

We recommend saving the file to the /partB directory, as it has a lot of free space. (You can do this by using the mv command: mv /tmp/CUMP_AppServerUpgrade_<version>.bin /partB.)

Step 6 Enter sh ./CUMP_AppServerUpgrade_<version>.bin to execute the file.

The upgrade program checks to see if there are any previous versions of the Application Server software installed. If there is at least one previous version, the upgrade program displays a message listing the previous version found on the system.


Note If the upgrade program does not find any previous versions of the Application Server software, the upgrade program displays an error message and you must quit the upgrade.


Step 7 Select Enter after reading the Introduction.

Step 8 Select Enter to confirm your existing system.

Step 9 Select Enter to confirm the pre-installation summary.

Values include the product name and the amount of disk space required and available for the installation target.

Step 10 Select Enter to start the upgrade.

The upgrade program upgrades all the required components associated with the Application Server software.

The upgrade program displays a message stating that the upgrade is complete.

Step 11 Select 1 to restart the system.

Step 12 As required, upgrade the other Application Server nodes in your multinode system.

Step 13 Synchronize the Hardware Media Server and meeting types.

Step 14 Put the Audio Blade back online.


Troubleshooting Tips

See Troubleshooting the Application Server Software Upgrade.

Related Topics

Changing the Online and Offline Status of an Audio Blade in the Changing Values for the Hardware Media Server module

Synchronizing Audio Blade Meeting Types with the Template Audio Blade in the Changing Values for the Hardware Media Server module

Application Commands for the Application Server in the "Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server" section of the Configuration Guide for Cisco Unified MeetingPlace

Upgrading the Application Server Remotely

When you upgrade the Application Server software remotely, the upgrade status is limited. We recommend that you upgrade the Application Server at the console if possible.

Restrictions

You must use the screen to perform a remote upgrade.

Before You Begin

Complete Determining Which Procedure to Follow.

Take the Audio Blade offline.

Procedure


Step 1 Go to Cisco.com and find the upgrade binary: http://www.cisco.com/cisco/software/navigator.html and select Products > Voice and Unified Communications > Unified Communications Applications > Conferencing > Cisco Unified MeetingPlace > Cisco Unified MeetingPlace 8.6 > Unified MeetingPlace Application Server. The naming convention will be similar to CUMP_AppServerUpgrade_<version>.bin, where <version> is the version number to which you are upgrading.

Step 2 Save the file to a convenient, local location.

Step 3 Enter md5sum CUMP_AppServerUpgrade_<version>.bin to determine the checksum of the file that you downloaded. Compare this value to the checksum value of the file that is posted on the download page on Cisco.com.

Step 4 Transfer the CUMP_AppServerUpgrade_<version>.bin file to the Cisco Unified MeetingPlace Application Server /tmp folder by using SCP file transfer.

We recommend saving the file to the /partB directory, as it has a lot of free space. (You can do this by using the mv command: mv /tmp/CUMP_AppServerUpgrade_<version>.bin /partB.)

Step 5 Using an SSH client, sign in as the user called mpxadmin.

Step 6 Enter screen -S mp_upgrade to create and attach to a screen named mp_upgrade.

Step 7 Change to the root user by entering su - and enter the root password.

Step 8 From the CLI, navigate to the directory where you saved the /partB/CUMP_AppServerUpgrade_<version>.bin file.

Step 9 Enter sh ./partB/CUMP_AppServerUpgrade_<version>.bin to execute the file.

The upgrade program checks to see if there are any previous versions of the Application Server software installed. If there is at least one previous version, the upgrade program displays a message listing the previous version found on the system.


Note If the upgrade program does not find any previous versions of the Application Server software, the upgrade program displays an error message and you must quit the upgrade.


Step 10 Select Enter after reading the Introduction.

Step 11 Select Enter to confirm your existing system.

Step 12 Select Enter to confirm the pre-installation summary.

Values include the product name and the amount of disk space required and available for the installation target.

Step 13 Select Enter to start the upgrade.

The upgrade program upgrades all the required components associated with the Application Server software.

The upgrade program displays a message stating that the upgrade is complete.

Step 14 Select 1 to restart the system.

Step 15 As required, upgrade the other Application Server nodes in your multinode system.

Step 16 Synchronize the Hardware Media Server and meeting types.

Step 17 Put the Audio Blade back online.


Troubleshooting

If the SSH remote session disconnects while you are upgrading the Application Server, follow these steps to reattach to the installation screen and continue the upgrade:

1. Using an SSH client, sign in as the user called mpxadmin.

2. Enter screen -ls to find out the full name of the screen created in the preceding procedure. The full name of the screen consists of an identifier followed by a dot and then the name that you used. For example, the full screen name might be 1665.mp_upgrade.

3. Enter screen -rD full_screen_name to reattach to the installation screen.

Related Topics

Changing the Online and Offline Status of an Audio Blade in the Changing Values for the Hardware Media Server module

Synchronizing Audio Blade Meeting Types with the Template Audio Blade in the Changing Values for the Hardware Media Server module

Application Commands for the Application Server in the "Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server" in the Configuration Guide for Cisco Unified MeetingPlace

Upgrading a Failover Deployment in an Audio System or a System with MeetingPlace Scheduling (Cisco Unified MeetingPlace 8.5.5)

Follow this procedure if you are upgrading a failover deployment with:

Cisco Unified MeetingPlace scheduling to a Release 8.6 system with Cisco Unified MeetingPlace scheduling

Audio-only system to a Release 8.6 audio-only system

Before You Begin

Complete About Upgrading the Application Server Software

Complete Preparing to Upgrade the Application Server Software

Complete Determining Which Procedure to Follow for the active Application Server.


Note The following nomenclature is used for clarity in the procedure below: we assume node 1 is the active Application Server in the existing system and node 2 is the standby Application Server. If this is not the case, then refer to your existing documentation and use the mp_replication status command to determine which server is node 1 and which server is node 2. The node number is indicated in the output in the Node column.


The overall procedure is described in the summary steps. The detailed procedure follows, with step-by-step instruction.

Summary Steps

1. Turn off and tear down replication between the active and standby Application Servers.

2. Convert the active server to single server mode and upgrade it to Release 8.6.

3. Convert the newly upgraded Release 8.6 Application Server to failover (standby) mode.

4. Convert the remaining legacy Application Server to active, then convert it to single server mode and upgrade it to Release 8.6.

5. Set up replication between the two Release 8.6 Application Servers.

Procedure


Step 1 Sign in to the Administration Center of Node 1. Use the eth0 IP address or hostname.

Step 2 Select System Configuration > Failover Configuration > Failover Deployment Setup.

Step 3 Select Set Standby to change Node 1 from Active mode to Standby mode.

The process of setting the node to Standby mode begins and progress report id displayed.

Step 4 After the process is complete, select Start System Restart.

Node 1 automatically restarts, enters failover standby mode, and redirects to eth0:0 hostname.

Step 5 Sign in to the Administration Center of Node 1.

The Failover Status page is displayed.

Step 6 Select Show Failover Status to ensure that Node 1 is in failover standby mode.

Step 7 Select System Configuration > Failover Configuration > Add Failover Node.

Step 8 Select Remove Failover Node.

The process of removing the failover node begins and a progress report is displayed. Replication between the two nodes is switched off and torn down.

Step 9 When the process of removing failover mode is finished, select Start System Restart.

Node 1 restarts.

Step 10 Sign in to the Administration Center of Node 1.

The Failover Status page is displayed.

Step 11 Select Show Failover Status to make sure that replication between Node 1 and Node 2 is torn down

Step 12 Select Maintenance > Backup and Archive to createa backup and archive and save the configuration data on Node 1.


Note We recommend that you create a backup and archive in case you need to revert to your legacy system. However, if you are using new hardware, a backup and archive is not necessary.


Step 13 Select System Configuration > Failover Configuration > Failover Deployment Setup.

Step 14 Select Set Single Server Deplyment Mode.

The Setting Single Deplyment mode process begins and a progress report is displayed.

Step 15 When the process is finished, select Start System Restart.

Node 1 restarts, enters single server active mode, and redirects to eth0 hostname.

Step 16 Sign in to the Administration Center of Node 1.

The Failover Status page is displayed.

Step 17 Select Show Failover Status to make sure that replication between Node 1 is in Single Server Active mode.

Step 18 Upgrade the Application Server on Node 1. See "How to Upgrade the Application Server Software" section.


Note We recommend that you validate the upgrade of the Application Server on Node 1. See "Testing that the Upgraded System Works Correctly" section.


Step 19 Sign in to the Administration Center of Node 1 using the eth0 IP address or hostname.

Step 20 Select System Configuration > Failover Configuration > Failover Deployment Setup.

Step 21 Configure the virtual network interface (eth0:0) with an IP address, hostname, subnet mask., and default gateway.

Step 22 Select Save.

Step 23 Select Set Failover Deployment Mode.

The setting failover deplyment mode process begins and a progress report is displayed.

Step 24 When the process is finished, select Start System Restart.

Node 1 restarts, enters failover standby mode, and redirects to eth0:0 hostname.

Step 25 Select System Configuration > Failover Configuration > Failover Deployment Setup.

Step 26 Select Set Single Server Deployment Mode.

The setting single server deplyment mode process begins and a progress report is displayed.

Step 27 When the process is finished, select Start System Restart.

Node 2 restarts, enters single server active mode, and redirects to eth0 hostname.

Step 28 Sign in to the Administration Center of Node 2.

The Failover Status page is displayed.

Step 29 Select Show Failover Status to make sure that replication between Node 2 is in Single Server Active mode.

Step 30 Upgrade the Application Server on node 2. See "How to Upgrade the Application Server Software" section.

Step 31 Sign in to the Administration Center of Node 2 using the eth0 IP address or hostname.

Step 32 Select System Configuration > Failover Configuration > Failover Deployment Setup.

Step 33 Configure the virtual network interface (eth0:0) with an IP address, hostname, subnet mask, and default gateway.

Step 34 Select Save.

Step 35 Select Set Failover Deployment Mode.

The setting failover deplyment mode process begins and a progress report is displayed.

Step 36 When the process is finished, select Start System Restart.

Node 2 restarts, enters failover standby mode, and redirects to eth0:0 hostname.

Step 37 Sign in to the Administration Center of Node 2.

The Failover Status page is displayed.

Step 38 Select Show Failover Status to make sure that Node 2 is in Failover Standby mode.

At this point, both Application Servers are in Standby mode.

Step 39 Sign in to the Administration Center of Node 1 using the eth0:0 IP address or hostname.

Step 40 Select System Configuration > Failover Configuration > Add Failover Node.

Step 41 Specify relevant parameters for Node 2: hostname (use the eth0:0 hostname), mpxadmin user password, mpxadmin user password confirmation and description.

Step 42 If you want to indicate data synchronization between the two Nodes, check Sync and, in the Hostname for sync field, specify the hostname of the source Node (use the eth0:0 hostname).

Step 43 Select Save.

Step 44 Select Add Failover Node.

The adding failover node process is started and a progress report is displayed. Replication is initialized between these two nodes.

Step 45 After the first part of the process finishes, select Continue With Replication.

The adding failover node process is continued and a progress report is displayed. Data synchronization is performed (if it was indicated in Step 27) and replication is switched on.

Step 46 After the process is complete, select Start System Restart.

Node 1 restarts.

Step 47 Sign in to the Administration Center of Node 1.

The Failover Status page is displayed. Select Show Replication Status to ensure that replication is established between Node 1 and Node 2.

Step 48 Select System Configuration > Failover Configuration > Failover Deployment Setup.

Step 49 Select Set Active to change Node 1 from standby mode to active mode.

The setting node to active mode process is started and a progress report is displayed.

Step 50 After the process is complete, select Start System Restart.

Node 1 restarts, enters failover active mode, and redirects to eth0 hostname.

Step 51 Sign in to the Administration Center of Node 1.

The Failover Status page is displayed. Select Show Failover Status to ensure that Node 1 is in failover active mode.

Node 1 is the active Application Server and node 2 is the standby Application Server.


Related Topics

Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server module

Backing Up, Archiving, and Restoring Data on the Application Server module

Upgrading the Application Server by Using the Console

Upgrading the Application Server Remotely

What To Do Next

Completing the Application Server Software Upgrade

"Configuring your Multinode Topology for Cisco Unified MeetingPlace" in the Configuration Guide for Cisco Unified MeetingPlace

Upgrading a Failover Deployment in an Audio-Only System or a System with MeetingPlace Scheduling (Cisco Unified MeetingPlace 8.5.4 and Earlier)

Follow this procedure if you are upgrading a failover deployment with:

Cisco Unified MeetingPlace scheduling to a Release 8.5.x system with Cisco Unified MeetingPlace scheduling

Audio-only system to a Release 8.5.x audio-only system

Before You Begin

Complete About Upgrading the Application Server Software

Complete Preparing to Upgrade the Application Server Software

Complete Determining Which Procedure to Follow for the active Application Server.


Note The following nomenclature is used for clarity in the procedure below: we assume node 1 is the active Application Server in the existing system and node 2 is the standby Application Server. If this is not the case, then refer to your existing documentation and use the mp_replication status command to determine which server is node 1 and which server is node 2. The node number is indicated in the output in the Node column.


The overall procedure is described in the summary steps. The detailed procedure follows, with step-by-step instruction.

Summary Steps

1. Turn off and tear down replication between the active and standby Application Servers.

2. Convert the active server to single server mode and upgrade it to Release 8.6.

3. Convert the newly upgraded Release 8.6 Application Server to failover (standby) mode.

4. Convert the remaining legacy Application Server to active, then convert it to single server mode and upgrade it to Release 8.6.

5. Set up replication between the two Release 8.6 Application Servers.

Procedure


Step 1 Sign in to the CLI of node 1 (active server) as the mpxadmin user. If you are signing in remotely, use the eth0:0 IP address or hostname.

Step 2 Enter su - to switch to the root user.

Step 3 Enter mp_replication status on node 1 (active server) to ensure that all database changes have been synchronized.

The system displays the queue column as zeroes.

Host Name

Host IP Address

Replication Type

Site

Node

State

Status

Queue

ServerA

<Server_A_IP>

Local

1

1

Active

Local

0

ServerB

<Server_B_IP>

Intra-Site

1

2

Active

Connected

0


Step 4 On node 1, switch off replication between the two Application Servers, where node_2_eth0:0 is the eth0:0 address for node 2. Enter mp_replication switchOFF [-v] on node 1.

Step 5 On node 1 (active server), tear down the replication setup with the remote Application Server, where node_2_eth0:0 is the eth0:0 address for node 2. Enter mp_replication teardown [-v] on node 1.

Step 6 Sign in to the Cisco Unified MeetingPlace Administration Center and select Maintenance > Backup and Archive. Create a backup and archive and save the configuration data on node 1 (active server).

We recommend creating a backup and archive in case you need to revert to your legacy system. If you are using new hardware, then disregard this step.

Step 7 Enter failoverUtil setDeployment singleServer to change the mode of node 1 to SingleServer.

Step 8 Upgrade the Application Server on node 1. See How to Upgrade the Application Server Software.


Note At this time, we strongly recommend you validate the upgrade of the Application Server on node 1. See Testing that the Upgraded System Works Correctly.


Step 9 Enter failoverUtil setDeployment failover on node 1 to change the mode of node 1 to failover.


Note This disables the eth0 interface of node 1, so that node 2 can become active.


Step 10 Sign in to the CLI of node 2. If you are signing in remotely, use the eth0:0 IP address or hostname.

Step 11 Enter su - to switch to the root user.

Step 12 Enter failoverUtil setServer active on node 2 to change its mode from standby to active.

Step 13 On node 2, tear down the replication setup with the remote Application Server, where node_1_eth0:0 is the eth0:0 address for node 1. Enter mp_replication teardown [-v] on node 2.

Step 14 Enter failoverUtil setDeployment singleServer on node 2 to change its mode to SingleServer.

Step 15 Upgrade the Application Server on node 2. See the How to Upgrade the Application Server Software.

Step 16 Enter failoverUtil setDeployment failover on node 2 to change its mode to failover (standby).

At this point, both Application Servers are in standby mode.

Step 17 Sign in to the CLI of node 2. If you are signing in remotely, use the eth0:0 IP address or hostname.

Step 18 Enter mp_replication init -n 2 -r <node1-eth0:0-hostname> [-v] to initialize database replication.

Step 19 Sign in to the CLI of node 1. If you are signing in remotely, use the eth0:0 IP address or hostname.

Step 20 Enter the following to initialize and start database replication:

mp_replication init -n 1 -r <node2-eth0:0-hostname> [-v]

mp_replication switchON

Step 21 Enter failoverUtil setServer active on node 1 to change its mode to active.

Node 1 is the active Application Server and node 2 is the standby Application Server.


Related Topics

Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server module

Backing Up, Archiving, and Restoring Data on the Application Server module

Upgrading the Application Server by Using the Console

Upgrading the Application Server Remotely

What To Do Next

Completing the Application Server Software Upgrade

"Configuring your Multinode Topology for Cisco Unified MeetingPlace" section in the Configuration Guide for Cisco Unified MeetingPlace

Completing the Application Server Software Upgrade

Stopping Maintenance Mode

Once the upgrade of each node is complete, sign in to the Administration Center. Select Maintenance > Maintenance Configuration, then Stop Maintenance Mode Now.

Updating Email Notifications

Only complete this section if you are upgrading a Cisco Unified MeetingPlace system with MeetingPlace scheduling. If you upgraded a Cisco Unified MeetingPlace system with WebEx scheduling, then go to How to Test the Application Server Software Upgrade.

See the "Customizing Email Notifications for Cisco Unified MeetingPlace on MeetingPlace-Scheduled and Audio-Only Deployments" in the Configuration Guide for Cisco Unified MeetingPlace"for complete information on customizing your email notification templates.

The upgrade program retains the SMTP/Exchange server configuration, when upgrading to Release 8.6.


Related Topics

SMTP Server Configuration Page in the "Administration Center Page References for Cisco Unified MeetingPlace" section of the Configuration Guide for Cisco Unified MeetingPlace

Exchange Server Configuration Page in the "Administration Center Page References for Cisco Unified MeetingPlace" section of the Configuration Guide for Cisco Unified MeetingPlace

How to Test the Application Server Software Upgrade

After upgrading the Application Server, perform these tests to ensure that the upgrade was successful.

Checking the System Status in the Installing the Application Server Software module

Testing the Basic Installation in the Installing the Application Server Software module

Troubleshooting the Application Server Software Installation in the Installing the Application Server Software module

Troubleshooting the Application Server Software Upgrade

Problem   You open a Web browser, enter the Cisco Unified MeetingPlace home page URL in the address field, but do not see the Cisco Unified MeetingPlace Administration Center sign in page.

Solution   Wait about 10 minutes for all the services to come up. Then, sign in to the Command-Line Interface of the Application Server and enter swstatus. If you see "GS GONE", then the GS module may have timed out. Reboot the Application Server. However, if you see "GS UP", then check your networking.

Error Message    There is not enough disk space to update the Application Server 
software.

Recommended Action    Contact Cisco TAC, who can help you identify and remove unnecessary files from the relevant partitions.

Problem   The upgrade installer does not have enough space in the / directory.

Explanation    You downloaded the upgrade binary onto your desktop, which stores it in the /home/user_name/Desktop directory. That directory uses the space from the / directory.

Solution   Remove the downloaded file from the /home/user_name/Desktop directory to free up space.

Error Message    There is not enough space to extract the upgrade installer file.

Recommended Action    Ensure that there are no large, extraneous files in the /opt partition.

Error Message    Cannot upgrade the Application Server software because there is no 
earlier version already installed on the server.

Explanation    You must have at least one previous version on your system before you can upgrade.

Recommended Action    Install the Application Server software.

Related Topics

Installing the Application Server Software module

Error Message    The installer has found an equal or newer version this update.

Explanation    You must have at least one older version of the Application Server software on your system before you can upgrade.

Recommended Action    Install a newer version of the Application Server software.

Related Topics

Installing the Application Server Software module

Error Message    Warning - Not enough memory. If you continue, system performance may 
be impacted. It is highly recommended that you exit the installation and install 
more memory.

Explanation    We recommend that the server that you upgrade have at least 4 GB of memory.

Recommended Action    Install more memory.

Related Topics

System Requirements for Cisco Unified MeetingPlace Release 8.6at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_device_support_tables_list.html

Problem   The upgrade program says that the database is corrupted.

Solution   Run the /etc/init.d/mpx_db status command to check the status of the database.

Related Topics

How to Upgrade the Application Server Software

How to Upgrade the Web Server


Note Do not complete this section if you have an existing deployment with WebEx scheduling and MeetingPlace-driven User Management.


To upgrade the Web Server, perform the following tasks in this order:

1. Read the upgrade prerequisites. See Preparing to Upgrade the Web Server.

2. Back up your Web Server data. See Backing Up Data.

3. As needed, uninstall the Cisco Security Agent. See Uninstalling the Cisco Security Agent (CSA).

4. Upgrade the Web Server to Release 8.6. See Upgrading the Web Server Software to Release 8.6.

5. As needed, reinstall the Cisco Security Agent. See Reinstalling the Cisco Security Agent (CSA).

Preparing to Upgrade the Web Server


Caution Do not run any other processes or tasks on your systems during an upgrade.

Upgrade the Application Server before you install the Web Server software.

Do not interrupt the installation during the automatic system shutdown or reboot.

If your system has multiple Web Servers, you must upgrade them all to the same version.

We recommend that you only upgrade the Web Server software after hours. To avoid losing recordings, do not upgrade the Web Server database if there are any meetings that are currently in session that have recordings or if any meetings with recordings have recently ended, because the system may not have posted the recording yet posted to the attachment and recording page.

We do not support upgrading the Cisco Unified MeetingPlace Web Server software by using Terminal Services

You cannot upgrade the Cisco Unified MeetingPlace Web Server when the Application Server is being rebooted. The Application Server must be running before you can upgrade the Web Server.

To ensure that the Application Server is running, sign in to the CLI as mpxadmin and enter swstatus. For more information about using the CLI, see the Configuration Guide for Configuration Guide for Cisco Unified MeetingPlace or the online help in the administrator interface.

Backing Up Data

You will need to have a manual backup created if you need to revert to the original release. For more information, see How to Back Up and Restore MPWEB SQL Database in the "Configuring the SQL Server for the Cisco Unified MeetingPlace Web Server" in the Configuration Guide for Cisco Unified MeetingPlace.

Working With the Cisco Security Agent (CSA)

If the Cisco Security Agent (CSA) is installed on your system, before you upgrade the web server, you must stop CSA and uninstall it. Following the Web Server upgrade, reinstall the version of CSA that is for Cisco Unified MeetingPlace Release 8.6.

Uninstalling the Cisco Security Agent (CSA)

Reinstalling the Cisco Security Agent (CSA)

Related Topics

Release Notes for Cisco Security Agent for Cisco Unified MeetingPlace at http://www.cisco.com/en/US/products/sw/secursw/ps5057/prod_release_notes_list.html.

Uninstalling the Cisco Security Agent (CSA)

Procedure


Step 1 Sign into the Web Server.

Step 2 Choose Start > Control Panel > Add or Remove Programs.

Step 3 Highlight Cisco Security Agent.

Step 4 Select Change/Remove.

Step 5 Follow the prompts to remove the program.

Step 6 Reboot the system.


Upgrading the Web Server Software to Release 8.6


Note If you want to upgrade your Release 8.5.5 Web Server to a Release 8.6 Web Server on a virtual machine, then you need to migrate your Web Server. For instructions on migrating your Web Server to Release 8.6, see How to Migrate the Web Server.


Procedure


Step 1 Exit any open applications.

Step 2 Insert the Cisco Unified MeetingPlace Web Server software DVD into the DVD-ROM drive.


Note If you are upgrading to Release 8.6, then obtain the Cisco Unified MeetingPlace Release 8.6 binaries from http://www.cisco.com/cisco/software/navigator.html. Select Products > Voice and Unified Communications > Unified Communications Applications > Conferencing > Cisco Unified MeetingPlace > Cisco Unified MeetingPlace 8.6.


Step 3 Double-click the CiscoUnifiedMeetingPlaceWebServer.exe file to begin the installation.

The system displays informational screens. The system stops the web master service and the Gateway SIM service.

Step 4 Select Next.

The system copies files. During the upgrade process, both the old and new Gateway SIM program icons are displayed in the Windows tray. The older icon is removed automatically.

Step 5 Select Finish when done.

The system finishes the Gateway SIM upgrade.

Step 6 Select OK when it is done.

The installation wizard continues to install the Cisco Unified MeetingPlace Web Server software.

Step 7 Select Next.

The system starts copying the files.

Step 8 Choose the option to restart the Web Server on the Web Server InstallShield Wizard Complete window.

Step 9 Select Finish.

The upgrade finishes with a single system reboot.

Step 10 Ensure that the Windows Time Service is up and running.


Related Topics

For information about configuring the Web Server to synchronize with an NTP server, see Configuring the Time for the Web Server in the "Configuring Time and Time Zones for Cisco Unified MeetingPlace" section of the Configuration Guide for Cisco Unified MeetingPlace

Reinstalling the Cisco Security Agent (CSA)

See Installing the Cisco Security Agent on the Web Server.

Troubleshooting

If you run into problems while installing the CSA, contact Cisco TAC. Examples of problems include if you are installing the CSA and the system aborts the installation or if the system does not let you reinstall or uninstall the CSA.

Reconfiguring the Application Server Connection in the Gateway SIM

Following the upgrade, the connection between the Application Server and the Web Server is preserved (but may take awhile). However, if the connection is broken, then complete the following procedure to redo the connection.


Note Complete this procedure only if the connection between the Application Server and the Web Server is broken.


Procedure


Step 1 Stop the web services and the Gateway SIM service, including the Replication Service and Agent Service.

Step 2 Open the Gateway SIM Agent.

a. Open the MeetingPlace Gateways Configuration utility.

b. Select the Gateway SIM tab.

Step 3 Delete this unit from the active Application Server.

a. Go to the lower-left pane of the Gateway SIM tab.

b. Select the name of the Application Server that you want to disconnect from.

c. Select Delete.

Step 4 Add this unit to a new Application Server.

a. Open the Gateway SIM Agent.

b. Select Add.

The MeetingPlace Server Entry window displays.

c. Enter the new configuration information as follows:

Parameter
Action

Server Name

Enter the hostname of the Release 8.6 Cisco Unified MeetingPlace Application Server.

Note If you use an IP address instead of a hostname for the Application Server, you will have to update the IP address on the Web Server whenever you change the IP address on the Application Server.

Shadow Server

Leave this field as is.

Client IP Address

Enter the IP address of the computer on which the Gateway SIM is installed.

Transfer Destination

Leave this field as is.

Link Encryption Disabled

Leave this box unchecked to maintain encrypted communications between the Gateway SIM and the Application Server.

Encryption uses a 56-bit DES algorithm with a secret key.


d. Select OK.

e. Select OK again.

Step 5 Restart the Gateway SIM service and the Cisco Unified MeetingPlace Web Master Service.

If other Web Servers share the database with this server, restart the services on those servers as well.


How to Upgrade the Software for the Hardware Media Server

There is no change in the software for the Hardware Media Server between Release 8.5.5 and 8.6.

How to Upgrade Microsoft Outlook for Cisco Unified MeetingPlace

After you complete the upgrade process, have your users upgrade the Cisco Unified MeetingPlace plug-in for Microsoft Outlook on their PCs.

You can either have your users install the Microsoft Outlook plug-in, or if your IT department uses an automated distribution tool to deploy other software updates and patches, then push the installation of the new plug-in to your users by using the same distribution tool.


Note Both setup.exe and MSI detects the Microsoft Outlook version installed on your computer and installs the appropriate plug-in.



Note As a best practice, ask your customers to uninstall the legacy Outlook plug-in first, before installing the new plug-in.



Note Choose only one deployment method (either MSI or setup.exe) to upgrade the Outlook plug-in.


Using Windows Installer (MSI)

Using setup.exe

Using Windows Installer (MSI)

Obtain the plug-in at http://<application-server>/outlook/public/setup.exe. By default, MSI installs the plug-in at $ProgramFiles\Cisco \MeetingPlace\MPOI\MP4OL.dll or MP4OL64.dll.

These are the MSI commands:

SERVERURL: Cisco Unified MeetingPlace server URL

ADMIN: Value of 1, when the plug-in is installed for all users. Value of 2, when the plug-in is installed for the current user. The default value is 1; to install the plug-in for all users.

LOADHIDDENIEWIN: Pass 1 to make MPOI load a hidden Internet Explorer window after Microsoft Outlook starts up. By default, Internet Explorer is not loaded after Microsoft Outlook starts up.


Note When using the Windows Installer (MSI). be sure to push out the new Outlook plug-in after you upgrade each Application Server.



Note After upgrading the plug-in, instruct your users to clear the cookies in Internet Explorer, and restart Microsoft Outlook, before using Cisco Unified MeetingPlace for Microsoft Outlook meetings. If the user does not clear the cookies, then the user name is garbled in the login window.


What To Do Next

(For deployments with MeetingPlace scheduling or audio-only deployments) In order to use the Microsoft Exchange Server (with SSL/TLS enabled) with back-end integration, complete the procedure in "Configuring Cisco Unified MeetingPlace to Support TLS Encryption" in the Configuration Guide for Cisco Unified MeetingPlace.

Using setup.exe

Procedure


Step 1 Obtain the executable file for the Microsoft Outlook plug-in. Specifying the hostname (FQDN) or IP address of the Application Server, go to

http://<application-server>/outlook/public/setup.exe

Step 2 After the setup.exe file is downloaded, complete these steps on the client PC:

a. Exit the Microsoft Outlook client software.

b. Uninstall the legacy plug-in. After uninstalling the legacy plug-in, make sure the calendar form changes back to IPM.Appointment.

If you prefer to uninstall the legacy plug-in automatically, then skip to Step c and run setup.exe. Running this command uninstalls the legacy plug-in and then installs the new plugin.

If you prefer to uninstall the legacy plug-in interactively through the CLI, then enter %windir%\system32\rundll32.exe advpack.dll,LaunchINFSection %windir%\INF\MPOUTL.INF,DefaultUninstall.ntx86.

If you prefer to uninstall the legacy plug-in silently through the CLI, then enter %windir%\system32\rundll32.exe advpack.dll,LaunchINFSection %windir%\INF\MPOUTL.INF,SilentUninstall.ntx86.

c. Install the new Microsoft Outlook 2010 plug-in. Run the setup.exe file. Use the -admin switch to install the client software and make the Cisco Unified MeetingPlace scheduling form available to any user who signs in to the specific computer. Specifically, select Start > Run, enter <pathname> setup.exe -admin.

By default, setup.exe installs the plug-in at $Program Files\Microsoft Office\Office12\ADDINS.

d. Select OK to install.

Step 3 After installation is complete, launch Microsoft Outlook.

Step 4 Verify that you can schedule meetings by selecting the MeetingPlace tab and filling out the scheduling form.

For details, select Help in the scheduling form.


Note After upgrading the plug-in, instruct your users to clear the cookies in Internet Explorer, and restart Microsoft Outlook, before using Cisco Unified MeetingPlace for Microsoft Outlook meetings. If the user does not clear the cookies, then the user name is garbled in the login window.


What To Do Next

In order to use the Microsoft Exchange Server (with SSL/TLS enabled) with back-end integration, complete the procedure in "Configuring Cisco Unified MeetingPlace to Support TLS Encryption" in the Configuration Guide for Cisco Unified MeetingPlace.

Troubleshooting Your Upgrade

Troubleshooting a Single Node System

Troubleshooting a Multinode System

Troubleshooting a Single Node System

If the upgrade fails, do a fresh install of Release 8.5.5, then run a restore to restore the database and other data (see "Restoring Data By Using the CLI on the Application Server" in the Configuration Guide for Cisco Unified MeetingPlace).

Troubleshooting a Multinode System

If an upgrade fails for one of your nodes in a multinode system, the complete the following procedure.

Procedure


Step 1 Complete the upgrade for all the other nodes in your multinode system. Sign in to the Administration Center and select Topology Management. Make sure all the other nodes (servers) are connected and their Operational Status is good (green).

Step 2 Remove the node that did not upgrade successfully (in this procedure, node A), from the multinode system (through Topology Management). If it is a regional master node with attached leaf nodes, then the leaf nodes also need to be removed.

Step 3 Complete a fresh install of the Application Server on node A. Restore its configuration and non-database data.


Note Do not restore archived data on this node. Otherwise, you will not be able to complete the next step.


Step 4 Add node A back to the multinode system. If it is a regional master node with attached leaf nodes, then also add back the leaf nodes.

Step 5 After its Operational Status is good (turns green), all common data is replicated to node A. However, you must still reconfigure the local configuration manually.


Related Topics

"Configuring your Multinode Topology for Cisco Unified MeetingPlace" in the Configuration Guide for Cisco Unified MeetingPlace

Testing that the Upgraded System Works Correctly

Verify the following after you upgrade and configure the entire Cisco Unified MeetingPlace system:

Scheduling

Ensure that you can schedule a meeting.

Ensure that the system sends an email notification for the meeting that you scheduled.

Ensure that you can join and attend the meeting via audio, video, and web.

Test that the dial in and dial out features work.

System Access

Ensure that you have access to all of the Administration Center pages, including Conference Manager. To access the Administration Center, go to a web browser and enter http://your-app-server

Recordings

Ensure that you can record a meeting.

Ensure that you can play back the meeting recording.