Cisco Meeting Server 3 0 Installation Guide For Virtualized Deployments

Cisco Meeting Server
Cisco Meeting Server 3.0

Installation Guide for Cisco Meeting Server 1000 and
Virtualized Deployments
December 09, 2020
Cisco Systems, Inc. www.cisco.com

Contents
Change History 5
1 Introduction 6
1.1 Overview of virtualized platforms 7
1.2 How to use this Guide 7
1.3 Differences in specific MMP commands 10
1.4 Differences in components enabled on the different platforms 10
2 Installation 12
2.1 Before You Start 12
2.1.1 About the Cisco Meeting Server software 12
2.1.2 Host requirements for the Cisco Meeting Server as a VM deployment 12
2.2 Installing via VMware on a specification-based server 15
2.3 Deploying Meeting Server from the OVA file with ESXi 6.5 Web Client 15
2.4 Installing and initial configuration of Cisco Meeting Server 1000 19
2.4.1 Before You Start 19
2.4.2 Task 1 — Unpacking and initial startup 19
2.4.3 Task 2 — Configuring VMware Network Management 21
2.4.4 Task 3 — Configuring the VMware Instance using vSphere client 23
2.4.5 Task 4 — Retrieving and activating VMware Licenses 24
2.4.6 Task 5 — Accessing the Cisco Meeting Server 1000 Console 25
3 Configuration 26
3.1 Creating your own Cisco Meeting Server Administrator Account 26
3.2 Setting up the Network Interface for IPv4 26
3.3 Adding Additional Network Interface(s) 28
3.4 Configuring the Call Bridge 28
3.5 Configuring the Web Admin Interface 29
3.5.1 Creating the certificate for the Web Admin Interface 29
3.5.2 Configuring the Web Admin Interface for HTTPS Access 31
4 Getting and Entering a License File 32

4.1 Transferring the license file to the Cisco Meeting Server 32
4.2 After transferring the license file 33
Appendix A Technical specifications for Cisco Meeting Server 1000 34

A.1 Physical specifications: 34
Cisco Meeting Server 3.0 : Virtualized Deployments 2

A.2 Environmental specifications 34
A.3 Electrical specifications 34
A.4 Video and audio specifications: 34
Appendix B Cisco licensing 36

B.1 Smart Licensing 36
B.2 Smart Account and Virtual Account information 37
B.3 How Smart licenses work in Meeting Server — overview 37
B.4 Expired license feature enforcement actions 39
B.5 How to retrieve licensing information (Smart Licensing) 40
B.6 Cisco Meeting Server licensing 40
B.6.1 Personal Multiparty plus licensing 42
B.6.2 Shared Multiparty plus licensing 42
B.7 Smart Licensing registration process 42
B.8 Obtaining Cisco user licenses using the traditional licensing method 43
B.9 Assigning Personal Multiparty licenses to users 44
B.9.1 To determine whether a specific user has a license: 44
B.10 How Cisco Multiparty licenses are assigned 45
B.11 Determining Cisco Multiparty licensing usage 45
B.12 Calculating SMP Plus license usage 46
B.13 Retrieving license usage snapshots from a Meeting Server 47
B.14 License reporting 47
Appendix C Branding 48
Appendix D Sizing a VM 49
D.1 Call Bridge VM 50
D.2 Edge VM 51
D.3 Database VM 52
D.4 Recorder and Streamer VM 52
D.4.1 VM sizing for the new internal SIP recorder component 52
D.4.2 VM sizing for the new internal SIP streamer component 53
Appendix E Additional information on VMWare 54

E.1 VMWare 54
Appendix F Creating a certificate signed by a local Certificate Authority 56
Cisco Legal Information 60

Cisco Trademark 61

Change History
Change History
Date Change Summary
December 09, 2020 Minor correction.
October 30, 2020 ESXi information updated.
October 06, 2020 Minor corrections.
September 09, 2020 Minor correction.
September 02, 2020 Minor edit to clarify VM minimum requirement to 4 vCPU cores for Record-
er/Streamer.
August 10, 2020 Updated for version 3.0.

Removed references to X-Series servers.
April 01, 2020 Broken links fixed.
November 27, 2019 400v/410v references removed.
November 13, 2019 Updated for version 2.8, ESXi support changes.
July 16, 2019 Corrected documentation error, reinserted Installation chapter
May 30, 2019 Minor documentation correction
April 26, 2019 Updated the supported versions of VMware ESXi
April 09, 2019 Miscellaneous corrections.
April 02, 2019 Information added for deploying Meeting Server from the OVA file with ESXi
6.5 Web Client.
Miscellaneous corrections.
January 28, 2019 Cisco Meeting Server 1000 using Cisco UCS C220 M5 Rack Server
supersedes the M4 variant. (From November 2018).
November 29, 2018 Miscellaneous corrections.
September 24, 2018 Removed Hyper-V section and references.
December 20, 2017 Added support for ESXi 6.5 and ESXi 6.0 Update 3 from Cisco Meeting Server
version 2.3.
November 27, 2017 Added Cisco Meeting Server 1000 additional installation detail. Removed
AWS references.

1 Introduction
1 Introduction
The Cisco Meeting Server is a scalable software platform for voice, video and web content,
which integrates with a wide variety of third-party kit from Microsoft, Avaya and other vendors.
With the Cisco Meeting Server, people connect regardless of location, device, or technology.
The Cisco Meeting Server software runs as a virtualized deployment using VMware ESXi 6.x
with virtual hardware vmx-1x loaded onto the following platforms:
l Cisco Meeting Server 1000 (a preconfigured Cisco UCS C220 rack server. From early
2019, the M5 variant superseded the M4 variant.)
l specification-based VM platforms.
The table below indicates the ESXi versions supported by the current versions of Cisco Meeting
Server software.
Table 1: ESXi version support
Cisco Meeting Server version ESXi version
3.0 ESXi 7.0b with Virtual Hardware version 17

ESXi 6.7 Update 3
ESXi 6.5 Update 2
ESXi 6.0 Update 3
2.9 ESXi 7.0b with Virtual Hardware version 17

ESXi 6.7 Update 3
ESXi 6.5 Update 2
ESXi 6.0 Update 3
2.8 ESXi 6.7

ESXi 6.5 Update 2
ESXi 6.0 Update 3
Note: From version 2.4, Cisco Meeting Server software no longer supports Microsoft Hyper-V
virtualized deployments.
Customers often use virtualized deployments of the Cisco Meeting Server as the edge server in
a split deployment and in scalable deployments.
The functionality, and user experience for participants, is identical across all platforms running
the same software version. However, deployments are not interchangeable between the
virtualized deployments and physical deployments (Cisco Meeting Server 2000). For example,
it is not possible to create a backup from a virtualized deployment and roll it back on a Cisco
Meeting Server 2000 or vice versa.

1 Introduction
Note: Meeting Server 3.0 introduces a mandatory requirement to have Cisco Meeting
Management 3.0 (or later). Meeting Management handles the product registration and
interaction with your Smart Account (if set up) for Smart Licensing support.
1.1 Overview of virtualized platforms
CAUTION: Irrespective of which virtualized platform is running the Cisco Meeting Server
software, ensure the platform is up to date with the latest patches. Failure to maintain the
platform may compromise the security of your Cisco Meeting Server.
Cisco Meeting Server 1000: ships with VMWare ESXi version 6.x and Cisco Meeting Server pre-
installed. However, this may not be the latest version of Cisco Meeting Server software
available. Follow the instructions in this guide to configure the Cisco Meeting Server 1000 and
apply the license. Once the Cisco Meeting Server is operational, check the version of software
installed using the MMP command version. The latest software is available here. To upgrade
the software installed on the Cisco Meeting Server 1000, follow the instructions in the release
notes for that software version.
Note: If your Meeting Server ships with ESXi 6.x — the default Cisco UCS ESXi 6.x credentials for
the Cisco Meeting Server 1000 are: login as root with a password of password. If your Meeting
Server ships with ESXi 7.x — the default Cisco UCS ESXi 7.x credentials for the Cisco Meeting
Server 1000 are: login as root with a password of c!SCo123.
You are advised to change this login admin account. Be aware that when you change the
password, Cisco UCS ESXi will require a complex password.
specification-based VM platforms: if you are upgrading the server from a previous virtualized
Cisco Meeting Server installation, then follow the instructions in the Cisco Meeting Server
release notes. If this is a new installation, then follow this guide to create a VM and install the
Cisco Meeting Server software.
1.2 How to use this Guide

This guide covers the installation of the Cisco Meeting Server 1000 and specification-based VM
deployments.
The Cisco Meeting Server 1000 is shipped with the software pre-installed. Go to Section 2.4
before going to Chapter 3 of this guide to start configuring the Cisco Meeting Server 1000.
Note: The Cisco Meeting Server 1000 has different settings to the specification-based VM
server, the settings are pre-configured, do not change the settings.

1 Introduction
If you are installing a specification-based VM deployment, then go to Chapter 2, before going

to Chapter 3 to configure the VM. Note that Chapter 2 is written for experienced VMware
administrators.
After configuring the Cisco Meeting Server and applying the license, use the Planning and
Preparation Deployment Guide to guide you on deciding the appropriate deployment, and then
follow the deployment and certificate guides that are most relevant to your targeted
deployment, see Figure 1. These documents can be found on cisco.com.

1 Introduction
Figure 1: Cisco Meeting Server installation and deployment documentation

1 Introduction
Note: The address ranges we use in Cisco user documentation are those defined in RFC 5737
which are explicitly reserved for documentation purposes. IP addresses in Meeting Server user
documentation should be replaced with correct IP addresses routable in your network, unless
otherwise stated.
1.3 Differences in specific MMP commands

The MMP Command Reference details the full set of MMP commands. There are a few
differences running a Cisco Meeting Server 2000 compared to a virtualized Cisco Meeting
Server.
on Cisco Meeting Server 1000

and virtualized Cisco Meeting
Command on Cisco Meeting Server 2000 Server
shutdown Not available through MMP. Use Do not use the vSphere power but-
Cisco UCS Manager to power ton. Use the shutdown com-
down blade servers before remov- mand instead.
ing power.
health Not available through MMP. Use Not available

Cisco UCS Manager.
serial Returns serial number of server. Not available
dns Do not specify an interface. Do not specify an interface.

For example For example
dns add forwardzone dns add forwardzone

<domain-name> <server <domain-name> <server
ip> ip>
user evict Available from version 2.9 Available
1.4 Differences in components enabled on the different platforms

The table below list the components available on the different Cisco Meeting Server platforms.
If a component is not available on a platform, then the MMP and API commands specific to the
component will not be available. For instance, the MMP and API commands for the TURN Server
are not available on the Cisco Meeting Server 2000.

Component on Cisco Meeting Server 2000 Server
Call Bridge Available Available

1 Introduction

Component on Cisco Meeting Server 2000 Server
Web Bridge 3 Available Available
Database Available Available
TURN server Not available Available
Recorder Not available Available
Uploader Not available Available
Streamer Not available Available
SNMP MIB Not currently available Available

2 Installation
2 Installation
This chapter applies to deployments on specification-based VM platforms and Cisco Meeting
Server 1000. Follow Section 2.2 to deploy a VMware host. Follow Section 2.4 to deploy a
Cisco Meeting Server 1000.
2.1 Before You Start
2.1.1 About the Cisco Meeting Server software

The Cisco Meeting Server software is provided as an .ova file for VMware users. This is a
template that sets up a new VM with a single network interface and a virtual disk containing the
Cisco Meeting Server application.
After installation a fully functioning Cisco Meeting Server is available, which can be run as:
n a complete solution with all components enabled on a single server (single combined server
deployment model),
n a split deployment with some components enabled on a Core server deployed on the internal
network, and other components enabled on an Edge server deployed in the DMZ (single split
server deployment model),
n a scalable and resilient deployment with multiple Call Bridges and databases, clustered
together to support growth in usage and minimize downtime.
The same .ova file is used to install all deployments.

To upgrade the Cisco Meeting Server software follow the procedure in the release notes
published for the software version.
2.1.2 Host requirements for the Cisco Meeting Server as a VM deployment

The Cisco Meeting Server runs on a broad range of standard Cisco servers as a VM
deployment. Refer to this link for VM configuration requirements and UCS tested reference
configurations for different deployments.
The Cisco Meeting Server also runs on third party servers including systems from Dell and HP
containing both Intel and AMD processors. Small form factor and ruggedized systems such as
Klas VoyagerVM and DTECH LABS M3-SE-SVR2 are also supported. The software can be
deployed on VMware ESXi as well as cloud services.

2 Installation
Table 2: Host requirements for the Cisco Meeting Server running on third party servers
Minimum Recommended
Server manufacturer Any Any
Processor type Intel Nehalem Intel Xeon 2600 v2 or newer

microarchitecture
AMD Bulldozer
microarchitecture
Processor frequency 2.0GHz 2.5Ghz
RAM 1GB per core* 1GB per core*
Storage 100GB 100GB
Hypervisor Latest update of Latest update of VMware ESXi 6.7 with virtual hardware vmx-
VMware ESXi 6.0 14
with virtual hardware
vmx-11 Note: Refer to the VMware documentation for further
information.
* additional memory should be available on the system for use by the hypervisor and any other VMs on the host.
Note: Meeting Server supports single and dual socket servers only.
Note: Both ESXi 6.5 and ESX 6.0 Update 3 provide a tool to enable you to disable TLS1.0 and
TLS 1.1 from communicating with ESXi.
Table 3: Recommended Core VM configurations
720p30 call legs CPU configuration RAM configuration Example systems
50 Dual Intel E5-2680v2 32 GB (8x4GB) Cisco UCS C220 M3

Dell R620
HP DL380p Gen8
40 Dual Intel E5-2650v2 32 GB (8x4GB) Cisco UCS C220 M3

Dell R620
HP DL380p Gen8
25 Single Intel E5-2680v2 16 GB (4x4GB) Cisco UCS C220 M3

Dell R620
HP DL380p Gen8

2 Installation
720p30 call legs CPU configuration RAM configuration Example systems
15 Single Intel E5-2640v2 8 GB (4x2GB) Cisco UCS C220 M3

Dell R620
HP DL380p Gen8
In addition:
n All memory channels should be populated to maximize available memory bandwidth. There
are no special requirements for NUMA systems.
n Out-of-band management systems should not be configured to share a network port with
the VM. Internal testing has shown that they can cause bursts of packet loss and degraded
voice and video quality. Out-of-band management should either be configured to use a
dedicated network port or disabled.
n Where available, hyperthreading should be enabled on the host, without this there is capacity
reduction of up to 30%.
n When comparing AMD and Intel processors, the number of AMD “Modules” (a pair of “cores”
sharing resources) should be compared to Intel “cores” (which execute a pair of
“hyperthreads”). In internal testing we have found that AMD processors provide 60-70%
capacity of an equivalent Intel processor. For this reason Intel processors are recommended
for production deployments.
n The CPUs used by the Cisco Meeting Server must be dedicated for its use. This is achieved
by:
o only running a single VM on the host, or
o pinning of all VMs on the host to specific cores and giving the Cisco Meeting Server sole
use of the assigned cores, and in addition, leaving a physical core with no VMs pinned to it
for the Hypervisor.
o following the co-residency requirements for Unified Communication in a Virtualized
Environment. Click on Cisco Meeting Server below the Meeting heading.
n If a VMWare Hypervisor with EVC mode enabled is used, the EVC must be set to one of the
following modes or higher:
“B1”/AMD Opteron™ Generation 4
“L2”/Intel® Nehalem generation (formerly Intel® Xeon Core™ i7)
EVC modes which enforce compatibility with older CPUs than those listed above, are not
supported as they will disable SSE 4.2; SSE4.2 is required.
n An activation key for the Call Bridge is required for media calls. To obtain the activation key,
you need the MAC address of your virtual server. See Chapter 4 and Appendix B for
information on licensing.

2 Installation
2.2 Installing via VMware on a specification-based server
Note: For every release of the Cisco Meeting Server for virtualized deployments, there will be an
.ova file for a new deployment, and an upgrade image (.img) for upgrading to the latest release.
For a new installation follow this section; for an upgrade follow the release notes.
l If a VMWare Hypervisor with EVC mode enabled is used, the EVC must be set to one of the
l An activation key for the Call Bridge is required for media calls. To obtain the activation
key, you need the MAC address of your virtual server. See Chapter 4 and Appendix B for
information on licensing.
2.3 Deploying Meeting Server from the OVA file with ESXi 6.5 Web Client
Note: For every release of the Cisco Meeting Server for virtualized deployments, there will be an
.ova file for a new deployment, and an upgrade image (.img) for upgrading to the latest release.
For a new installation follow this section; for an upgrade follow the release notes.
1. Download the .ova file from the Cisco web site.

2. In the vSphere Client go to the host in the Navigator tab on the left and select
Create/Register VM.
3. For Select creation type, select Deploy a virtual machine from an OVF or OVA file and click
Next.

2 Installation
4. Enter the desired name for the virtual machine and browse or drop the .ova file (downloaded
in step 1) to select it.
5. Follow the wizard instructions. The settings that must be selected are:
a. Select the datastore to store the VM configuration and disk files.
b. Select the network mapping you would like the VM to be connected to.
c. Set Disk provisioning to Thick.
d. Ensure Power On After Deployment is not selected.
e. Click Finish.

2 Installation
Note: Depending on how your virtual host is set up, some of the wizard settings may not
be displayed or may not be selectable.
6. Once completed, the new Cisco Meeting Server VM should now be listed in your Virtual
Machines.
7. Select the Cisco Meeting Server VM from your list of VMs.
8. From the Actions button, select Edit Settings….
a. Edit VM settings and choose CPUs. Set Number of CPUs to the desired number (where 4
is the minimum). See the deployment guide for scaling details. For more information on
VM configuration requirements, see
https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_
system/virtualization/virtualization-cisco-meeting-server.html and Appendix D.
b. Set Number of Cores per Socket to one of the following:
l On a dual processor host with hyperthreading, set Number of Cores per Socket to the
number of logical cores minus 2.
l On a dual processor host without hyperthreading, set Number of Cores per Socket to
the number of logical cores minus 1.
l On a single processor host, set Number of Cores per Socket to the number of logical
cores.
We recommend that you configure the number of sockets to mirror underlying
hardware.

2 Installation
Note: The number of logical cores can be found on the vSphere Web Client, by clicking
Manage > Settings > Processors. For more information, see:
https://docs.vmware.com/en/VMware-
vSphere/6.5/com.vmware.vsphere.resmgmt.doc/GUID-E09F36DF-E31F-417D-
9865-06E351D8AF15.html
c. Ensure the RAM is set to a minimum of 4GB and the disk space is set to 100GB.
9. Click Power on.
10. Click the Console tab and open the browser console (or remote console if VMware Remote
Console is installed).

2 Installation
11. Log in with the user name “admin” and the password “admin”. You will be asked to change
the admin password. You are now logged into the MMP. Go on to Chapter 3.
2.4 Installing and initial configuration of Cisco Meeting Server 1000
2.4.1 Before You Start

You need the following to complete your installation:
l PAK license number
l VMware license activation codes or customer-supplied VMware license keys
l Internet and email access to complete the license retrieval steps
l A Windows computer running vSphere Client 6.0 or the permisssions to install vSphere
client on the computer
l A console, either:
l A monitor with a VGA connector and USB keyboard
or
l A PC with a serial adaptor, Cisco serial cable, and terminal program, and network
connection with Internet Explorer or Firefox with JAVA installed and enabled
2.4.2 Task 1 — Unpacking and initial startup

1. Unpack the Meeting Server, power cords, console adaptor, and rack kit.
2. Position the Meeting Server or optionally rackmount — see the Cisco UCS C220 M5
Installation Guide or Cisco UCS C220 M4 Installation Guide, as appropriate for your
deployment.
3. Connect the Ethernet cables to the Ethernet1 port on the rear of the Meeting Server and
connect to the Ethernet network.
4. Connect the power cords to each power supply and connect to power.

2 Installation
5. Press the power button on the front of the Meeting Server. It will automatically stop and
restart itself more than once after initial power on.
6. Connect a console to the Meeting Server to continue. You can use either a monitor and
keyboard, or use a virtual console over a network connection. Select from the following
options:
2.4.2.1 Console Option 1 — Monitor and keyboard

1. Attach a monitor with a VGA connection to the VGA port on the rear of the Meeting
Server, or to the console port on the front.
2. Connect a keyboard to the USB ports located on the rear of the Meeting Server, or to the
console port on the front.
The Meeting Server will automatically boot to the VMware console screen when startup is
complete and should be visible on the monitor.
2.4.2.2 Console Option 2 — Virtual console over network

Use this method if no monitor and keyboard are available to connect to the Meeting Server:
1. Connect your computer's serial port to the RJ-45 port on the rear of the Meeting Server
labeled 10101 using the standard blue Cisco RJ-45 to DB-9 Null Serial cable provided
with routers and switches.
2. Open your terminal program, select the COM port for your serial port/adaptor and set the
terminal settings to 115200 baud, No Parity, 8 data bits, 1 stop bit.
3. Connect a second Ethernet LAN port to the RJ-45 port on the rear of the Meeting Server
labeled M1. If you only have the resources for one network connection, remove the LAN
connected to Ethernet1 and use it for the M1 port temporarily to enable the virtual
console, and move it back to Ethernet1 after configuration. The M1 port must be
connected and configured with a valid IP address to use the virtual console.
4. Ensure Meeting Server has its power supplies connected. If not, ensure it has been
plugged in for several minutes to allow the CIMC management interface to startup.
Meeting Server does not have to be powered on for CIMC to function, but must be
connected to power. (There is no external indicator for CIMC status.)
5. In your terminal program, press Escape and the 9 keys simultaneously to switch the port to
CIMC. A username prompt displays.
6. Enter the default username and password (username: admin, password: password).
7. The first time you login, you will be prompted to change the password to one of your
choice. Complete the prompts to set a new password.
8. Once logged in, at the command prompt enter the command scope cimc — the
command prompt changes to reflect that you are now in the CIMC menu.

2 Installation
9. Enter the command show network detail to show the current configuration of the
management Ethernet interface, including the current IP address the server has aquired via
DHCP (if available on the network). Make a note of the IPv4 address shown (if DHCP is
available).
10. If DHCP is not available and you need to set a static IP, use the following commands,
changing the sample values to ones appropriate for your network. (These commands
assume you are already in the CIMC scope.)
scope network
set dns-use-dhcp no
set dhcp-enabled no
set v4-addr 10.1.2.3
set v4-netmask 255.255.255.0
set v4-gateway 10.1.2.1
commit
11. Enter show network detail to confirm your changes. Once complete, enter the
command exit twice to log out of the CIMC.
12. Switch to your PC's browser, and browse to the IP address you configured or obtained
from the CIMC serial interface. Dismiss the certificate security warnings and a Cisco
landing page with username and password fields will display.
13. Login with the username of admin and the password you set when first connecting to the
CIMC.
14. When the Server Summary page loads, click the Launch KVM Console link under Actions.
The JAVA virtual console application loads. Depending on your Operating System and
browser you may get security warnings and dialogs to acknowledge and accept. Continue
until the application loads—it will show the monitor image as if you were directly connected
to the server. If the server is powered off, it will show a larger green window saying No
Signal.
15. If the server is powered off, from the Power menu, select Power On to start the server.
After a few minutes it should boot to the VMware console screen.
You can now use the virtual console the same as if you were connected using a local monitor
and keyboard.
2.4.3 Task 2 — Configuring VMware Network Management

You must have console access to the server via monitor or virtual console to complete the
following steps.
Ensure the server is powered on and the VMware console screen displays, offering press F2 to
configure or F12 to shutdown.

2 Installation
1. Press F2 to configure the server. The default username is root and the default password
is dependent up the version of ESXi installed, i.e. if your Meeting Server 1000 ships with
ESXi 6.x the default password is password, if it ships with ESXi 7.x the default password
is c!SCo123.
2. We recommend you change the default password:
a. From the menu options, use the arrow and Enter keys to select Configure Password.
b. Follow the prompts and set a password to use for the VMware root account.
Note: VMware has high password complexity requirements— use a strong password
including special characters, mixed case, and alpha and numeric characters.
3. From the menu options, use the arrow and Enter keys and select Configure Management
Network and then IPv4 Configuration.
4. Select the option for the network configuration you will use (DHCP or Static IP
assignment) and configure the IPv4 Address, Mask, and Gateway as appropriate for your
network.
REMINDER: This IP address is for the VMware Hypervisior, not the Meeting Server
application. The address used must be unique from the Meeting Server application.
5. (Optional) If you will access the Hypervisor management via a different VLAN from the
Meeting Server application, configure the VLAN that the Management Interface should
associate with.
6. Press Escape to return to the main menu, and Escape again to log out.
The VMware management IP address displays in the bottom left of the screen.
2.4.3.1 Useful information if you are using the virtual console

l CIMC is a powerful out-of-band management interface for the Meeting Server and is
recommended for use when the Meeting Server is installed in a rack or computer room.
This management interface is not used by VMware or the Meeting Server application, so if
you want to keep it connected, you must secure a dedicated LAN connection for the M1
Ethernet port. (NIC sharing options are also available in the Cisco UCS Server
documentation.)
l If you are using the virtual console with only one network connection and had been
temporarily using it for the M1 interface:
a. You will not need the virtual console anymore to complete the install. Disconnect the
Ethernet cable from the M1 interface of the server and reconnect it to the Ethernet1
port.
b. If you are using DHCP for the VMware management interface, you will need to restart
the server to obtain a new IP address after connecting the Ethernet cable. To restart,
press the power button on the front of the server briefly and the server will initiate an

2 Installation
automatic shutdown (this takes several minutes). After it powers off, power it back
on using the power button. Because you disconnected the network that the virtual
console was using, you will not be able to see the IP address the server obtained. To
find the IP address, contact your DHCP administrator to find which IP address the
server was assigned. The MAC address of the Ethernet1 interface can be found on
the pull-out tab located on the front of the Cisco Meeting Server 1000.
You should now have Ethernet connected to the Ethernet1 port on the rear of the server and
know the IP address in use by the VMware management network.
2.4.4 Task 3 — Configuring the VMware Instance using vSphere client

Now you connect to the VMware instance and complete the Hypervisor's initial configuration.
1. If you do not have vSphere 6.0 or 6.5 client installed and need to install it, follow these
steps:
a. Download from the local VMware instance:
i. Using your Internet Browser, browse to your new server's IP, for example,
http://IPaddress
ii. Click the link for Browse database in this host's inventory
iii. Enter the username root and password you configured in the VMware
network management setup.
iv. Navigate to datastore1\OVA-ISO\VMware\ and click the VMware-viclient...
link to download the client installer.
v. Once downloaded, locate the file and run the program to install the vSphere
client.
2. Open vSphere client and in the connection window, enter the IP for your VMware instance,
the username root and the password created during the VMware network management
configuration. Click Login to connect to the server.
3. An SSL certificate warning appears when connecting to the server, click Ignore to
continue. Upon connecting, you will also get a VMware evaluation notice, click OK.
2.4.4.1 Configuring VMware NTP

Configure the Hypervisor to have a valid NTP source so its logs will be accurate:
1. In the vSphere client, connect to the Meeting Server, and click on the Meeting Server in the
left panel to select it.
2. In the right-hand panel, click the Configuration tab, and under Software, click Time
Configuration.
3. In the resulting page, click the Properties link (in the top right corner).

2 Installation
4. In the Properties window, check the NTP Client Enabled checkbox and click the Options
button.
5. Click NTP Settings from the list and click the Add button to add the NTP source(s) you
wish to use.
6. Select General from the list.
7. Change the Service to Start and Stop with the host.
8. Click Start to start the service.
9. Click OK twice to close the time configuration pages.
2.4.5 Task 4 — Retrieving and activating VMware Licenses

If you ordered VMware licenses from Cisco, the licenses will be delivered as Activation Codes in
separate packaging or emails from Cisco. You require two 1-CPU licenses per Cisco Meeting
Server1000. These activation codes must be converted to license keys using the VMware public
website. You need internet and email access to complete this task.
2.4.5.1 Activate VMware activation keys

1. Use an internet browser (we recommend a browser other than Google Chrome for this
task), go to https://www.vmware.com/oem/code.do?Name=CISCO-RESELL-AC
2. Login with a VMware account. If you do not have one, complete the steps provided on the
webpage to create a new VMware profile.
3. Once logged in, enter the activation codes following your organization's policy on
assigning software activation codes. After completing the steps, VMware will email the
license codes to you.
4. Once the licenses have been added to your VMware account, the two single CPU licenses
must be combined into a single, dual CPU license. This is achieved on the myVMware
portal. These steps are covered in detail on the VMware KB article:
https://kb.vmware.com/s/article/2006973.
TIP: You may have issues combining licenses immediately after adding them into your
VMware profile. If this happens, wait 5-10 minutes and try again. If you continue to have
issues, contact VMware licensing support to assist with combining the licenses.
5. Once you have the new combined license key, open the vSphere client, connect to the
Meeting Server if you are not already, and click on the Meeting Server in the tree in the left
panel.
6. In the right panel, select the Configuration tab, then under Software, click on Licensed
Features.
7. Current evaluation details display, click on the Edit link at the top right corner of the page.

2 Installation
8. In the resulting window, select Assign a new key to this host and click the Enter button to
enter your license key.
9. Click OK close the dialog window.
Hypervisor basic setup is now complete.
2.4.6 Task 5 — Accessing the Cisco Meeting Server 1000 Console

The Meeting Server instance itself can be accessed by connecting to its own IP address, or via
the vSphere client console function.
1. Open the vSphere client and log into your Meeting Server's IP address with the username
of root and the password you configured previously.
2. Select the Meeting Server from the left-hand panel, and use the plus sign (+) to expand
the tree. A virtual machine named Cisco Meeting Server will be present and a green arrow
to indicate it is powered on.
3. If your network has DHCP, to find the current Meeting Server IP address, click on the
Summary tab while the Cisco Meeting Server VM is highlighted. The IP address the
Meeting Server has obtained will be shown under the General section. You can ssh to that
IP to continue the configuration of the Meeting Server software.
4. If your network does not have DHCP, you will have to assign an IP address to the VM using
the virtual machine console in the vSphere client and the Meeting Server MMP commands
ipv4 or ipv6 as described in Chapter 3 (or see the MMP Command Line Reference
Guide).
5. To access the console, click on the Console tab in the vSphere client when the Meeting
Server VM is selected. If the screen is blank, click within the window and press the Enter
key. A login prompt displays.
TIP: To regain mouse control outside the console window, press the Control and Alt keys
together.
6. Log in with the user name “admin” and the password “admin”. You will be asked to change
the admin password.
CAUTION: Passwords expire after 6 months.
The rest of the configuration process follows that described in Chapter 3.

3 Configuration
3 Configuration
3.1 Creating your own Cisco Meeting Server Administrator Account

For security purposes, you are advised to create your own administrator accounts as username
“admin” is not very secure. In addition, it is good practice to have two admin accounts in case
you lose the password for one account, if you do, then you can still log in with the other account
and reset the lost password.
Use the MMP command user add <name> admin, see the MMP Command Reference Guide
for details. You will be prompted for a password which you must enter twice. Login with the
new account, you will be asked to change the password.
CAUTION: Passwords expire after 6 months.
After creating your new admin accounts delete the default “admin” account.
Note: Any MMP user account at the admin level can also be used to log into the Web Admin
Interface of the Call Bridge. You cannot create users through the Web Admin Interface.
3.2 Setting up the Network Interface for IPv4
Note: Although these steps are for IPv4, there are equivalent commands for IPv6. See the MMP
Command Reference for a full description.
In the Cisco Meeting Server virtualized deployment, there is only one network interface initially,
interface “a”, but up to 4 are supported (see the next section). The MMP runs on interface a in
the virtual deployment.
1. To set network interface speed, duplex and auto-negotiation parameters use the iface
MMP command e.g. to display the current configuration on the "a" interface, in the MMP
type:
iface a
a. Set the network interface speed (Mbps), duplex and auto negotiation parameters
using the command iface (a|b|c|d) <speed> (full|on|off). For example,
set the interface to 1GE, full duplex:
iface a 1000 full
b. Switch auto negotiation on or off using the command iface a autoneg
<on|off>. For example:

3 Configuration
iface a autoneg on
Note: We recommend that the network interface is set to auto negotiation "on" unless
you have a specific reason not to.
2. The “a” interface is initially configured to use DHCP. To view the existing configuration, type:
ipv4 a
a. If you are using DHCP IP assignment, no further IP configuration is needed, go to step 3.
b. If you are using Static IP assignment:
Use the ipv4 add command to add a static IP address to the interface with a specified
subnet mask and default gateway.
For example, to add address 10.1.2.4 with prefix length 16 (netmask 255.255.0.0) with
gateway 10.1.1.1 to the interface, type:
ipv4 a add 10.1.2.4/16 10.1.1.1
To remove the IPv4 address, type:
ipv4 a del <address>
3. Set DNS Configuration
Meeting Server requires DNS lookups for many of its activities including looking up SRV
records and is required for a simplified deployment. We recommend you point Meeting
Server to the default DNS resolver for your network using a period "." for the forwardzone
value.
a. To output the dns configuration, type:
dns
b. To set the application DNS server use the command:
dns add forwardzone <domain name> <server IP>
Note: A forward zone is a pair consisting of a domain name and a server address: if a
name is below the given domain name in the DNS hierarchy, then the DNS resolver can
query the given server. Multiple servers can be given for any particular domain name to
provide load balancing and fail over. A common usage will be to specify "." as the
domain name i.e. the root of the DNS hierarchy which matches every domain name.
for example:
dns add forwardzone . 10.1.1.33
c. If you need to delete a DNS entry use the command:
dns del forwardzone <domain name> <server IP>

3 Configuration
for example:
dns del forwardzone . 10.1.1.33
3.3 Adding Additional Network Interface(s)

The Cisco Meeting Server virtualized deployments support up to four interfaces (a, b, c and d).
If required, you can add a second network interface on VMWare. However, any two interfaces of
the Cisco Meeting Server must not be put into the same subnet.
1. In the vSphere Client, locate your VM in the Hosts and Clusters list
2. Select Edit Virtual Machine Settings.
3. Add a Network Adapter with type VMXNET3.
Note: If you select an Ethernet Adaptor which is not VMXNET3, then you may experience
network connection problems, and may invalidate your license.
Note: For more information on adding or modifying Ethernet Adapters, refer to the VMware
web page Adding and Modifying Virtual Network Adapters.
4. After adding the new adapter, enable the interface for use on the MMP with the command
ipv4 b enable, for example.
5. Reboot the VM so the addresses and gateway can be added manually or automatically
picked up by DHCP (if enabled for that interface).
3.4 Configuring the Call Bridge

The Call Bridge needs a key and certificate pair that is used to establish TLS connections with
SIP Call Control devices and with the Lync Front End (FE) server. If you are using Lync, this
certificate will need to be trusted by the Lync FE server.
The command callbridge listen <interface> allows you to configure a listening interface
(chosen from A, B, C or D). By default the Call Bridge listens on no interfaces.
1. Create and upload the certificate as described in the Certificate Guidelines.
2. Sign into the MMP and configure the Call Bridge to listen on interface A.
callbridge listen a
Note: the Call Bridge must be listening on a network interface that is not NAT’d to another IP
address. This is because the Call Bridge is required to convey the same IP that is configured
on the interface in SIP messages when talking to a remote site.

3 Configuration
3. Configure the Call Bridge to use the certificates by using the following command so that a
TLS connection can be established between the Lync FE server and the Call Bridge, for
example:
callbridge certs callbridge.key callbridge.crt
The full command and using a certificate bundle as provided by your CA, is described in the
Certificate Guidelines.
4. Restart the Call Bridge interface to apply the changes.
callbridge restart
3.5 Configuring the Web Admin Interface

The Web Admin Interface acts as the interface to the Call Bridge; the API of the Cisco Meeting
Server is routed through this web interface.
Configuring the Web Admin Interface involves creating a private key/certificate pair, see Section
3.5.1, and uploading the private key/certificate pair to the MMP, see Section 3.5.2.
Once the Web Admin Interface is enabled you can use either the API or the Web Admin to
configure the Call Bridge.
3.5.1 Creating the certificate for the Web Admin Interface

The Web Admin Interface is only accessible through HTTPS, you need to create a security
certificate and install it on the Cisco Meeting Server. Follow the steps described in the
Certificate Guidelines for a production environment — this section shows how to test with a self-
signed certificate in a lab environment.
Note: You need a certificate uploaded for the Web Admin Interface even if you configure the Call
Bridge through the API rather than the Web Admin Interface.
The information below assumes that you trust Cisco to meet requirements for the generation of
private key material. If you prefer, you can generate the private key and the certificate externally
using a public Certificate Authority (CA), and then load the externally generated key/certificate
pair onto the MMP of the Cisco Meeting Server using SFTP. After obtaining the signed
certificate, go to Section 3.5.2.
Note: If testing your Cisco Meeting Server in a lab environment, you can generate a key and a
self-signed certificate on the server. To create a self-signed certificate and private key, log in to
the MMP and use the command:
pki selfsigned <key/cert basename>
where <key/cert basename> identifies the key and certificate which will be generated e.g. "pki

3 Configuration
selfsigned webadmin" creates webadmin.key and webadmin.crt (which is self-signed). Self-

signed certificates are not recommended for use in production deployments.
The steps below explain how to generate a private key and the associated Certificate Signing
Request using the MMP command pki csr , and export them for signing by a CA.
1. Log in to the MMP and generate the private key and certificate signing request (CSR):
pki csr <key/cert basename> [<attribute>:<value>]
where:
<key/cert basename> is a string identifying the new key and CSR (e.g. "webadmin" results
in "webadmin.key" and "webadmin.csr" files)
and the allowed, but optional attributes are as follows and must be separated by a colon:
l CN: the commonName which should be on the certificate. Use the FQDN defined in DNS
A record as the Common Name. Failure to do this will result in browser certificate errors.
l OU: Organizational Unit
l O: Organization
l L: Locality
l ST: State
l C: Country
l emailAddress
Use quotes for values that are more than one word long, for example:
pki csr example CN:example.com "OU:Accounts UK" "O:My Company"
2. Send the CSR to one of the following:
l To a Certificate Authority (CA), such as Verisign who will verify the identity of the
requestor and issue a signed certificate.
l To a local or organizational Certificate Authority, such as an Active Directory server with
the Active Directory Certificate Services Role installed, see Appendix F.
Note: Before transferring the signed certificate and the private key to the Cisco Meeting Server,
check the certificate file. If the CA has issued you a chain of certificates, you will need to extract
the certificate from the chain. Open the certificate file and copy the specific certificate text
including the BEGIN CERTIFICATE and END CERTIFICATE lines and paste into a text file. Save the
file as your certificate with a .crt, .cer or .pem extension. Copy and paste the remaining
certificate chain into a separate file, naming it clearly so you recognize it as an intermediate
certificate chain and using the same extension ( .crt, .cer or .pem). The intermediate certificate
chain needs to be in sequence, with the certificate of the CA that issued the chain first, and the
certificate of the root CA as the last in the chain.

3 Configuration
3.5.2 Configuring the Web Admin Interface for HTTPS Access
Note: The deployment automatically sets up the Web Admin Interface to use port 443 on
interface A. However, the Web Bridge also uses TCP port 443. If both the Web Admin Interface
and the Web Bridge use the same interface, then you need to change the port for the Web
Admin Interface to a non-standard port such as 445, use the MMP command webadmin
listen <interface> <port>.
1. Establish an SSH connection to the MMP and sign in.

2. Use SFTP to upload the private key/certificate pair and certificate bundle (optional) for the
Web Admin Interface.
3. Disable the Web Admin Interface before assigning the certificate.
webadmin disable
4. Assign the private key/certificate pair you uploaded in step 2, using the command:
webadmin certs <keyfile> <certificatefile> [<cert-bundle>]
where keyfile and certificatefile are the filenames of the matching private key and
certificate. If your CA provides a certificate bundle then also include the bundle as a separate
file to the certificate. For example:
webadmin certs webadmin.key webadmin.crt webadminbundle.crt
5. Restart the Web Admin Interface.
webadmin restart
6. Enable the Web Admin Interface.
webadmin enable
For example:
webadmin certs webadmin.key webadmin.crt
webadmin listen b 443
webadmin restart
webadmin enable
Test that you can access the Web Admin Interface, i.e. enter your equivalent of https://cms-
server.mycompany.com (or the IP address) in your browser and login using the MMP user
account you created earlier.
Note: From version 3.0 you can use Trial Mode for a 90 day full featured period without licenses.
In this instance, the Web Admin interface will display "This CMS is currently unlicensed" during
this period. For information on Smart licensing and how licensing works in 3.0 see Appendix B.

4 Getting and Entering a License File

Note: This section only applies if you are using the traditional licensing method. For information
on Smart licensing and how licensing works in 3.0 see Appendix B.
All virtualized deployments of the Cisco Meeting Server require a license file; the license file is for
the MAC address of your virtual server.
B.6 describes the Cisco Licensing available to purchase for the Cisco Meeting Server. After
purchasing the licensing, follow this chapter to apply the license to the Cisco Meeting Server
only if you are using the traditional licensing method.
4.1 Transferring the license file to the Cisco Meeting Server

This section assumes that you have already purchased the licenses that will be required for your
Meeting Server from your Cisco Partner and you have received your PAK code(s).
Follow these steps to register the PAK code with the MAC address of your Meeting Server using
the Cisco License Registration Portal.
1. Obtain the MAC address of your Meeting Server by logging in to the MMP of your server,
and enter the MMP command: iface a
Note: This is the MAC address of your VM, not the MAC address of the server platform that
the VM is installed on.
2. Open the Cisco License Registration Portal and register the PAK code(s) and the MAC
address of your Meeting Server(s).
3. If your PAK does not have an R-CMS-K9 activation license, you will need this PAK in addition
to your feature licenses.
4. The license portal will email a zipped copy of the license file. Extract the zip file and rename
the resulting xxxxx.lic file to cms.lic.
5. Using your SFTP client, log into Meeting Server and copy the cms.lic file to the Meeting
Server file system.
6. Restart the Call Bridge(s) using the MMP command callbridge restart
7. After restarting the Call Bridge(s), check the license status by entering the MMP command
license
The activated features and expirations will be displayed.

4.2 After transferring the license file

To apply the license you need to restart the Call Bridge. However, you must have configured the
Call Bridge certificates and a port on which the Call Bridge listens, before you can do this.
Note: From version 3.0 you can use Trial Mode for a 90 day full featured period without licenses.
In this instance, the Web Admin interface will display "This CMS is currently unlicensed" during
this period. For information on Smart licensing and how licensing works in 3.0 see Appendix B.
Note: If you are deploying multiple servers (single combined or split Core or Edge servers) that
you will cluster, see the Scalability & Resilience Deployment Guide Appendix entitled Sharing
Call Bridge licenses within a cluster for more information if you are using the traditional licensing
method. Otherwise, refer to the Smart Licensing section as you can now license multiple
clusters with one set of Meeting Server licenses in your Smart Account and you no longer need
to load the license file onto each individual Meeting Server instance as was the case prior to 3.0.
You are now ready to configure the Cisco Meeting Server. See the appropriate guide for your
deployment found here:
n Single Combined Server Deployment Guide if you are deploying on a single host server
n Single Split Server Deployment Guide if you are deploying on a split Core/Edge deployment
n Scalability & Resilience Guide if you are deploying multiple servers (single combined or split
Core or Edge servers) that you will cluster.
Remember to use the shutdown command rather than using the vSphere power button when
you want to shut down the Cisco Meeting Server.

Appendix A Technical specifications for Cisco Meeting Server 1000
Appendix A Technical specifications for Cisco

Meeting Server 1000
A.1 Physical specifications:

Chassis: Cisco UCS C220 M5 Rack Server or Cisco UCS C220 M4 Rack Server
Weight: 18+ kg (40 lbs)
Size: 1RU high
Rack requirements: 19" standard rack
A.2 Environmental specifications

Operating temperature: 5 to 35°C (41-95°F)
Operating humidity: 5 to 93% non-condensing
A.3 Electrical specifications

See Power Supply Specifications in the appropriate Cisco UCS C220 Server Installation and
Service Guide.
A.4 Video and audio specifications:

This table provides a comparison of the call capacities across the platforms hosting Cisco
Meeting Server software.
Table 4: Call capacities across Meeting Server platforms
Cisco Meeting Cisco Meeting Cisco Meeting

Type of calls Server 1000 M4 Server 1000 M5 Server 2000
Full HD calls 24 24 175

1080p60 video
720p30 content

1080p30 video
1080p30/4K7 content

Appendix A Technical specifications for Cisco Meeting Server 1000
Cisco Meeting Cisco Meeting Cisco Meeting

Type of calls Server 1000 M4 Server 1000 M5 Server 2000

1080p30 video
720p30 content
HD calls 96 96 700
720p30 video
720p5 content
SD calls 192 192 1000

448p30 video
720p5 content
Audio calls (G.711) 1700 2200 3000

Appendix B Cisco licensing

You will need licenses for the Cisco Meeting Server. From version 3.0 Meeting Server supports
Smart Licensing as well as the traditional method of licensing for existing users. This section
covers both methods and contains license information common to both methods. Where
information is specific to either Smart or traditional licensing, this is highlighted.
B.1 Smart Licensing

Version 3.0 introduces support for Smart Licensing on Cisco Meeting Server using Cisco
Meeting Management version 3.0 (or later). This transition to the software licensing model, i.e.
moving from traditional Product Activation Key (PAK) licenses to Smart Licensing, improves the
user experience of license purchasing, registration and software administration. It also aligns
Meeting Server with other Cisco products' approach to software licensing and utilizes Cisco
Smart Account — a central repository where you can view, store, and manage licenses across
your entire organization.
All new license purchases still receive a PAK code — retain for reference — as all licenses will be
available in the Smart Account that Meeting Management will sync to.
For further information and to create a Smart Account, go to: https://software.cisco.com and
choose Smart Licensing.
Note: The term "overage" is used to describe a situation where license usage is higher than the
entitlement.
The Meeting Server licensing changes and behaviors in 3.0 are:

l Cisco Meeting Management version 3.0 (or later) is mandatory in version 3.0 — Meeting
Management reads the Meeting Server license file, and can handle the product
registration and interaction with your Smart Account (if set up).
l You can now license multiple clusters with one set of Meeting Server licenses in your
Smart Account and you no longer need to load the license file onto each individual
Meeting Server instance as was the case prior to 3.0.
l Meeting Management with Smart Licensing tracks how many Call Bridges per cluster,
thereby eliminating the need for the R-CMS-K9 activation license.
l For a new deployment with no existing licenses:
l Newly purchased licenses may be Smart-enabled by default and require a Smart
Account — once you have entered the license details into Meeting Management, it
will validate the license details against those held in the Smart Account.
l For an existing deployment with a local license file on each Call Bridge:

l You can upgrade to 3.0 without a Smart Account, and Meeting Management will
read the existing license file(s) as per the traditional licensing method.
l You can move to a Smart Account using the Cisco Smart Software Manager
(CSSM) portal and choose the option to convert your existing licenses to Smart.
l SMP and PMP license usage is combined to decide if a day is counted as overage (if either
license is over, the whole day is regarded as usage higher than the entitlement). For other
feature licenses (for example, recording or custom layout), they are assessed separately
and enabled with entitlement via Meeting Management (assuming the license exists in
your Smart account).
Note: As Meeting Management is required for all 3.0 deployments, for larger customer
deployments, Meeting Management can be deployed in new licensing-only mode without
active meeting management.
For information on purchasing and assigning licenses using the traditional licensing method, see
Section B.8 and Section B.9.
B.2 Smart Account and Virtual Account information

Smart Accounts can contain Virtual Accounts which allow you to organize your licenses by any
designation of your choice, for example, by department. Here are some important points to
note when using a Smart Virtual Account with Meeting Server and Meeting Management:
l Each Meeting Server cluster(s) to a single Meeting Management should be linked to a
user-defined Smart Virtual Account.
l Each Virtual Account can only connect with a single Meeting Management server that is
configured to handle Smart Licensing.
l Only configure a single Meeting Management to Smart — we recommend you do not
configure a second redundant Meeting Management for Smart Licensing as double
counting of license usage will occur.
l PMP, SMP and Recording/Streaming licenses can be shared across multiple clusters with
a single Meeting Management instance and Smart Licensing in a single Virtual Account.
l ACU licensing is not available with the Meeting Management licensing dashboard —
ACUs are not supported in 3.0 and later.
B.3 How Smart licenses work in Meeting Server — overview
Note: For full details on using Cisco Meeting Management to administer Smart Licensing, see
the Meeting Management 3.0 Administrator Guide.

Meeting Management is mandatory for licensing to work on Meeting Server 3.0 and later.
Version 3.0 introduces a new trust and interaction between Meeting Server and Meeting
Management to support the new licensing using Smart or for existing customers use of installed
licensing files — it's this trusted link that enables Meeting Management to license Meeting Server.
A high level work flow for implementing Smart Licensing is as follows:
1. Register your Meeting Management to Smart Licensing Virtual Account.
2. When a Meeting Server first starts up it will have no license status values defined.
Note: You can use Trial Mode for a 90 day full featured period without licenses.
3. When Meeting Server first connects to a Meeting Management instance set up to

administer Smart Licensing, it checks to see if the Meeting Server has previously had a
license applied. If not, it will set the license expiry date to 90 days in the future.
The expiry date for a license is shown in Meeting Management and also returned in the
clusterLicensing API, as shown in Section .
Note: The expiry date for any feature license will only ever be up to a maximum of 90 days
in the future.
4. Meeting Management collates Meeting Server licensing usage for the cluster and reports
to your Smart Account on a daily basis to check that it has the licenses required to ensure
the Meeting Server is in compliance. The Smart Account responds to Meeting
Management to indicate if the Meeting Server is compliant or not. Meeting Management
then sets the expiry dates as appropriate as follows:
a. If the Meeting Management identifies that a license exists and is below entitlement
for a particular feature, the expiry date will be extended to 90 days in the future.
Note: If Meeting Server doesn't connect to Meeting Management and send usage
data for a period of 90 days then the Meeting Server's license won't get refreshed
and will therefore expire. For information on the enforcement actions when a license
expires, see Section B.4.
If a license usage is higher than the entitlement, or a license is not found, then enforcement
occurs as follows.
b. If Meeting Management identifies that less than 15 out of the last 90 days are non-
compliant, it will allow this and reset the Meeting Server expiry date to 90 days in the
future from that point. The admin will get a visual warning to notify "Insufficient
licenses".
c. If Meeting Management identifies that more than 15 of the last 90 days are non-

compliant, the first level of enforcement (Alarm 1) will occur, i.e. out of compliance
notifications on the Meeting Management interface.
d. If overage continues, Meeting Management does not reset the 90 day clock, it gives
you a countdown in xx days in which to add new licenses otherwise Alarm levels 2
and 3 will be enabled for all participants joining a meeting as shown in Appendix B.
Appendix B shows the enforcement flow from initial start up in trial mode on the left-hand side
through to overage enforcement as shown on the right-hand side.
Figure 2: Cisco Meeting Server and Cisco Meeting Management Smart Licensing enforcement flow
B.4 Expired license feature enforcement actions

Previously, Meeting Server would evaluate its license file on restart only. From 3.0 the current
status of whether a feature is licensed or not can change dynamically, for example, because a
feature license expires (previously this would not have been evident until a restart), or there has
been an API change. Meeting Management will calculate enforcement actions with Smart
Licensing or traditional license file mode.
Note: You can use the Smart Licensing portal to enable email notifications for "insufficient
licenses".
When a license feature has expired the actions described in Table 5 will occur.

Table 5: Expired license enforcement actions
Feature Action
callBridge When expired: a visual text message displays on screen lasting 30 seconds and an
audio prompt plays on joining a meeting for all participants/all meetings. (Alarm level
2)
callBridgeNoEncryption When expired more than 90 days ago or no license present: the same as before but
the visual message is permanent. The audio prompt plays "Your deployment is out of
licensing compliance, please contact your administrator". (Alarm level 3)
PMP/SMP
Note: you only need callBridge or callBridgeNoEncryption to prevent the above
action.
customizations When expired or not present, customization features will not be active during a meet-
ing.
recording When expired or not present you will not be able to start a new recording (regardless
of whether it is a 3rd party recorder or not).
This license represents recording and streaming so the same restrictions also apply to
streaming.
To turn off Alarms 2 and 3, simply add more licenses to your Smart Account.
B.5 How to retrieve licensing information (Smart Licensing)

To retrieve licensing information for a cluster using the Meeting Server Web Admin interface:
1. Log in to the Meeting Server Web Admin interface and select Configuration > API:
2. From the list of API objects, tap the ► after /api/v1/clusterLicensing
3. The current license status for the cluster is displayed as shown in this example:
Figure 3: clusterLicensing API — license status
B.6 Cisco Meeting Server licensing

The following features require a license:

n Call Bridge
n Call Bridge No Encryption
n Customizations (for custom layouts)
n Recording or Streaming
In addition to feature licenses, user licenses also need to be purchased, there are 2 different
types of user licenses:
n PMP Plus,
n SMP Plus,
Note: You can use Trial Mode for a 90 day full featured period without licenses.
For information on user licensing, see Section B.9.
Note: You have the choice of purchasing an activation key with SIP media encryption enabled or
SIP media encryption disabled (unencrypted SIP media) for the Cisco Meeting Server 1000,
Cisco Meeting Server and the VM software image. For more information on the unencrypted
SIP media mode and activation key see your Deployment Guide.
Note: This note only applies if you are using the traditional licensing method. You need a license
file for each individual Call Bridge, however, you can share licenses amongst servers in the same
cluster. Each license file should have all of the required features that you purchased for that
cluster; such as PMP Plus, SMP Plus, Recording/Streaming, and activation LIC-CMS-K9.
If a license is only installed on one Call Bridge in the cluster then the feature(s) will only work for
calls on that Call Bridge. The feature will fail for calls on other Call Bridges in the cluster, unless
you share the license with the other Call Bridges. Note that each Call Bridge in the cluster
requires its own license file.
You can determine the number of distinct calls across a cluster of Call Bridges using the
parameter weightedCallsActive on API object /system/multipartyLicensing. The sum of
weighted calls across a cluster matches the number of distinct calls on the cluster. For example,
if CMS1 shows 3 callsActive and 2 weightedCallsActive, and CMS2 shows 2
callsActive and 1 weightedCallsActive, then there are 3 conferences in total on the cluster
and 3 PMP Plus/SMP Plus licenses are required.
For more information, see the Appendix “Sharing Call Bridge licenses within a cluster”.

B.6.1 Personal Multiparty plus licensing

Personal Multiparty Plus (PMP Plus) provides a named host license assigned to each specific
user who frequently hosts video meetings. This can be purchased through Cisco UWL Meeting
or Flex Meetings (which includes PMP Plus). Personal Multiparty Plus is an all-in-one licensing
offer for video conferencing. It allows users to host conferences of any size (within the limits of
the Cisco Meeting Server hardware deployed). Anyone can join a meeting from any endpoint,
and the license supports up to full HD 1080p60 quality video, audio, and content sharing.
Note: Using Unified Communications Manager, the initiator of an Ad Hoc conference can be
identified and if they have been assigned a PMP Plus license then that is used for the conference.
Note: To determine the number of active calls using the PMP Plus licence of an individual, use
the parameter callsActive on API object
/system/multipartyLicensing/activePersonalLicenses. We generally allow 2 calls to be
active allowing for one starting and other finishing. If the call is on a cluster of Call Bridges then
use the parameter weightedCallsActive on API object
/system/multipartyLicensing/activePersonalLicenses for each Call Bridge in the cluster.
The sum of weightedCallsActive across the cluster matches the number of distinct calls on
the cluster using the individual’s PMP Plus license. If a PMP Plus licence is exceeded, then SMP
Plus licences are assigned, see Section B.10.
B.6.2 Shared Multiparty plus licensing

Shared Multiparty Plus (SMP Plus) provides a concurrent license that is shared by multiple users
who host video meetings infrequently. Shared Multiparty Plus enables all employees who do not
have PMP Plus host license to access video conferencing. It is ideal for customers that have
room systems deployed that are shared among many employees. All users with PMP Plus or
using SMP Plus licenses have the same great experience, they can host a meeting with their
space, initiate an ad-hoc meeting or schedule a future one. Each shared host license supports
one concurrent video meeting of any size (within the limits of the hardware deployed).
Note: To determine the number of SMP Plus licences required, use the parameter
callsWithoutPersonalLicense on API object /system/multipartyLicensing. If the calls are
on a cluster of Call Bridges then use the parameter weightedCallsWithoutPersonalLicense
on API object /system/multipartyLicensing for each Call Bridge in the cluster. The sum of
weightedCallsWithoutPersonalLicense across the cluster matches the number of distinct
calls on the cluster which require an SMP Plus license.
B.7 Smart Licensing registration process

To enable Smart Licensing:

1. Sign in to Cisco Smart Software Manager (CSSM) portal and choose Virtual Account with
Meeting Server Licenses.
2. Generate a registration token.
3. Copy the token to your clipboard.
4. Open the instance of Meeting Management that you want to use for license reporting.
5. Go to the Settings page, Licensing tab.
6. Click Change.
7. Choose Smart Licensing and Save.
8. Click Register.
9. Paste the registration token (this allows Meeting Management to connect to the Smart
Licensing portal).
10. Click Register.
11. When you have registered, check how many licenses you have in your Virtual Account.
12. In Meeting Management, go to the Licenses page.
13. Enter the license information for the licenses you have in your Virtual Account.
If any licenses are not shown in your Virtual Account, use the Convert Licenses tab, search
by PAK to find them, then choose Convert Licenses as shown in Figure 4. (If you can't find
a license(s), open a case by sending an email to [email protected].)
Figure 4: License conversion for Smart Licensing
B.8 Obtaining Cisco user licenses using the traditional licensing method
This section assumes that you have already purchased the licenses that will be required for your
Meeting Server from your Cisco Partner and you have received your PAK code(s).

Follow these steps to register the PAK code with the MAC address of your Meeting Server using
the Cisco License Registration Portal.
1. Obtain the MAC address of your Meeting Server by logging in to the MMP of your server,
and enter the MMP command: iface a
Note: This is the MAC address of your VM, not the MAC address of the server platform that
the VM is installed on.
2. Open the Cisco License Registration Portal and register the PAK code(s) and the MAC
address of your Meeting Server(s).
3. If your PAK does not have an R-CMS-K9 activation license, you will need this PAK in addition
to your feature licenses.
4. The license portal will email a zipped copy of the license file. Extract the zip file and rename
the resulting xxxxx.lic file to cms.lic.
5. Using your SFTP client, log into Meeting Server and copy the cms.lic file to the Meeting
Server file system.
6. Restart the Call Bridge(s) using the MMP command callbridge restart
7. After restarting the Call Bridge(s), check the license status by entering the MMP command
license
The activated features and expirations will be displayed.
B.9 Assigning Personal Multiparty licenses to users

This process requires that users are imported from a single LDAP source. See the "Provisioning
— Import users" chapter in the Meeting Management 3.0 Administrator Guide for full details.
B.9.1 To determine whether a specific user has a license:

1. From the list of API objects, tap the ► after /users
a. Select the object id of the specific user
b. Identify the object id of the userProfile associated with this user
2. From the list of API objects, tap the ► /userProfiles
a. Select the object id of the specific userProfile
b. Find the setting for parameter hasLicence. If set to true then the user identified in
step 1 is associated with a Cisco Multiparty user license. If set to false the user is NOT
associated with a Cisco Multiparty user license.

Note: If the userProfile is deleted, then the userProfile is unset for the ldapSource and
the imported users.
B.10 How Cisco Multiparty licenses are assigned

When a meeting starts in a space, a Cisco license is assigned to the space. Which license is
assigned by the Cisco Meeting Server is determined by the following rules:
n if the space owner is defined and corresponds to a Meeting Server imported LDAP user with
an assigned Cisco PMP Plus license, the license of that owner is assigned irrespective of
whether the person is active in the conference, if not, then
n if the meeting was created via ad hoc escalation from Cisco Unified Communications
Manager, then Cisco Unified Communications Manager provides the GUID of the user
escalating the meeting. If that GUID corresponds to a Meeting Server imported LDAP user
with an assigned Cisco PMP Plus license, the license of that user is assigned, if not, then
n if the meeting was scheduled via Cisco TMS version 15.6 or newer, then TMS will provide the
owner of the meeting. If that user corresponds to a Meeting Server imported LDAP user by
user ID/email address with an assigned Cisco PMP Plus license, the license of that user is
assigned to the meeting, if not then,
n a Cisco SMP Plus license is assigned.
B.11 Determining Cisco Multiparty licensing usage

We recommend you use Meeting Management to view your Multiparty licensing usage.
However, the API can be used.
Table 6 below lists the API objects and parameters that can be used to determine the
consumption of Multiparty licenses.

Table 6: Objects and parameters related to Multiparty license usage
API object Parameter (s) Use to ......
/system/licensing personal, determine whether components of the

shared Cisco Meeting Server have a Multiparty
license and are activated. Values are:
noLicense, activated, grace, expired.
Also provides date of expiry and
number limit.
/system/multipartyLicensing personalLicenseLimit, indicates the number of licenses avail-

sharedLicenseLimit, able and in use
personalLicenses,
callsWithoutPersonalLicense,
weightedCallsWithoutPersonalLicense
/sys- callsActive, indicates the number of active calls

tem/multipartyLicensing/ weightedCallsActive that are using a Personal Multiparty
activePersonalLicenses Plus user license,
/userProfiles hasLicense indicates whether or not a user is

associated with a Cisco Multiparty user
license
For more information on these additional object and fields to support Cisco Multiparty licensing,
refer to the Cisco Meeting Server API Reference Guide.
B.12 Calculating SMP Plus license usage

For the following specific scenarios, the SMP Plus license consumed for a meeting is reduced to
1/6th of a full SMP Plus license:
n an audio-only conference where no attendees are using video,
n a Lync gateway call unless the Meeting Server is recording or streaming, at which point it is
considered a full conference and a full SMP Plus license is consumed,
n a point to point call involving a web app and a SIP endpoint, or two web apps, unless the
Meeting Server is recording or streaming, at which point it is considered a full conference and
a full SMP Plus license is consumed.
A full SMP Plus license is consumed for any audio-video conference instantiated from a space
with the owner property undefined, owned by an imported LDAP user without a PMP Plus
license, or owned by an imported LDAP user whose PMP Plus license has already been
consumed, this is irrespective of the number of participants.

Note: A point to point call is defined as:

n having no permanent space on the Meeting Server,
n two or less participants, including the recorder or streamer
n no participants hosted on the Lync AVMCU,
This includes Lync Gateway calls as well as other types of calls: point-to-point web app to web
app, web app to SIP and SIP to SIP.
B.13 Retrieving license usage snapshots from a Meeting Server

An administrator can retrieve license usage from the Meeting Server. These cannot be accessed
though the Web Admin Interface, instead use an API tool such as POSTMAN:
Use GET on /system/MPLicenseUsage/knownHosts to retrieve host ids of the Meeting Servers
in the deployment. Supply an offset and limit if required to retrieve host ids other than those on
the first page of the list.
Use GET on /system/MPLicenseUsage to retrieve license usage from the Call Bridge of the
Meeting Server with the specified host id. Supply a start and end time for the snapshot. Provides
information on number of personal licenses in use, number of shared licenses in use which are
audio only, point to point, or neither audio or point to point, number of calls being recorded and
number of streamed calls.
Note: Note: personal and shared licenses are normalized over the number of Call Bridges that
the call spans.
B.14 License reporting

Meeting Management has license reporting/usage information for the last 90 days, and Cisco
Smart Software Manager also contains license reporting information. The usage of recording
licenses indicates the number of conferences recording concurrently, similarly the streaming
license usage indicates the number of conferences streaming concurrently.

Appendix C Branding
Appendix C Branding
Some aspects of the participant experience of meetings hosted on Meeting Servers can be
branded, they include :
n the web app sign-in background image, sign-in logo, text below sign-in logo, icon, and the
text on the browser tab,
n IVR messages,
n SIP and Lync participant's splash screen images and all audio prompts/messages,
n text on the meeting invitation.
If you apply a single brand with only a single set of resources specified (one web app sign-in
page, one set of voice prompts, one invitation text), then these resources are used for all
spaces, IVRs and Web Bridges in the deployment. Multiple brandings allow different resources
to be used for different spaces, IVRs and Web Bridges. Resources can be assigned at the
system, tenant, space or IVR level using the API.
See the Customization Guidelines for more information on branding.

Appendix D Sizing a VM
The Cisco Meeting Server is designed for maximum flexibility, it is highly scalable and allows the
“mix and matching” of Cisco Meeting Server 2000, Cisco Meeting Server 1000 and VM
deployments. For example, using VMs as edge servers and Cisco Meeting Server 2000 and
Cisco Meeting Server 1000 at the core for a highly scalable distributed architecture, or placing
all components within a VM deployment on a single standardized server.
Maximum flexibility is also carried through into the wide range of standard servers and
specifications the Cisco Meeting Server software can run on. Appendix E provides details for
one of the most popular virtualization technologies: VMware. The Cisco Meeting Server
software also runs effectively on an array of more specialized servers, for example for
applications requiring portable and rugged form factors.
The whole Cisco Meeting Server or individual components of the Cisco Meeting Server can be
run in a virtual machine (VM) deployment. For instance:
l for the purposes of testing the deployment, all of the components can run on a single VM
see Figure 5.
Note: In production networks, the Recorder and Streamer components should be enabled
on a different Meeting Server to the server hosting the conferences.
l a single VM can run the Web Bridge as an edge component with the TURN server,
connected to a Cisco Meeting Server 2000 or Cisco Meeting Server 1000 sitting in the
core network running the Call Bridge, and another VM running the other core components.
Note: If the Cisco Expressway is used at the edge of the network, then the TURN server
component on the VM does not require enabling, and the Web Bridge should reside on the
Meeting Server with the Call Bridge hosting the conferences.
l one VM running edge components, connecting to a second VM running the Call Bridge
and database, and a third VM running other core components.
Figure 5 illustrates the Cisco Meeting Server software components enabled on one server.
Figure 6 illustrates the Cisco Meeting Server software components deployed across an edge
server and core servers.

Figure 5: Cisco Meeting Server software components enabled on one server
Figure 6: Cisco Meeting Server software components with the TURN server and Web Bridge 3 at the
edge
When a VM is configured to run one or more Cisco Meeting Server components, Cisco
recommends that the entire host is dedicated to the VM. This provides best performance for
real time media applications and ensures high quality end user experience. The sizing of VMs
depends on the components being used.
D.1 Call Bridge VM

The Call Bridge carries out the media transcoding for the Cisco Meeting Server. This
component has the highest requirements of any of the components.

Each physical core of an Intel Xeon 2600 series (or later) CPU, running at 2.5GHz, is capable of
approximately 2.5 720p30 H.264 call legs when hyperthreading is enabled. Capacity scales
linearly with number of CPU cores and frequency, so a two socket E5-2680v2 system, which
has 20 physical cores, can handle 50 concurrent 720p30 H.264 call legs.
The VM should be configured to use all but one of the host physical cores. When hyperthreading
is enabled the number of available logical cores is double the number of physical cores, so in the
dual E5-2680v2 system above, there are 40 virtual CPUs, of which 38 should be allocated to
the VM. We recommend that you configure the number of sockets to mirror underlying
hardware.
Figure 7: Virtual CPU core allocation for a dual E5-2680v2 host
Over subscription of the host, either by incorrectly setting the number of Cisco Meeting Server
VM virtual CPUs or by contention for CPU resources amongst VMs, causes scheduling delays
and results in degraded media quality. The recommendation to assign the number of vCPUs in
excess of the number of physical cores is an overcommitment of the CPU resource. This CPU
over commitment does lead to a distortion in the VM CPU utilization statistics and a higher CPU
Ready time. CPU commitment is a workload specific consideration and therefore may conflict
with more generic advice. This vCPU commitment is intentional for Cisco Meeting Server and is
a result of empirical testing to extract peek performance from a host. A Cisco Meeting Server
VM, correctly configured according to the recommendations above, will degrade gracefully by
dropping frame rate and/or resolution if pushed over capacity.
1GB RAM for each underlying physical CPU core should be allocated to the VM with a minimum
allocation of 4GB of RAM. For the system above, the VM should be configured with 19GB
corresponding to the 19 physical CPU cores in use.
D.2 Edge VM
The requirements for other components are lower, and a VM can be used in a split core-edge
deployment to provide edge functionality, for example TURN server on an edge VM. This edge

VM can be coupled with a core VM .

A VM providing edge services to a single Core VM should be configured with a minimum of 4
vCPUs and 4 GB RAM.
D.3 Database VM
Note: This section is applicable only if you choose to use one or more external databases.
The host server for a database has modest CPU requirements, but requires large storage and
memory. We do not mandate a qualified VM host but recommend:
n Four vCPUs, 8GB RAM and 100GB data store
(The OVF will be set to these parameters so that they are the defaults post-deployment)
n Sandy Bridge (or later) class Intel processors (e.g. E5-2670 or E5-2680 v2)
n The data store should reside on either a high IO per second SAN or local SSD storage
n The data must reside on the same vdisk as the OS
The Cisco UCS C220 which is currently used as the host for the Cisco Meeting Server 1000
could be used, but the VM database would only use a small percentage of the server’s
resources. Using this server, other VMs could be also hosted on the same server as the VM
database, if desired.
D.4 Recorder and Streamer VM
Note: The new internal SIP recorder and streamer service cannot be used as an External
recording or streaming service as the services rely on specific SIP header parameters passed by
the Meeting Server Call Bridge. When calls from any other source that is not Meeting Server Call
Bridge connect, the recorder/streamer will reject the call as it won't locate the specific SIP
headers expected.
D.4.1 VM sizing for the new internal SIP recorder component

The recommended deployment for production usage of the recorder is to run it on a dedicated
VM with a minimum of 4 vCPU cores and 4GB of RAM. The following table provides an idea of
performance and resource usage for each of the recording types.

Table 7: Internal SIP recorder performance and resource usage
Recording Set- Recordings per RAM required per Disk budget per Maximum concurrent
ting vCPU recording hour recording
720p 2 0.5GB 1GB 40
1080p 1 1GB 2GB 20
audio 16 100MB 150MB 100
Key point to note (applies to new internal recorder component only):

l Performance scales linearly adding vCPUs up to the number of host physical cores.
D.4.2 VM sizing for the new internal SIP streamer component

The recommended deployment for production usage of the streamer is to run it on a dedicated
VM with a minimum of 4 vCPU cores and 4GB of RAM. The following table gives an idea of 3
recommended minimum specifications and the number of streams they can handle.
Table 8: Internal SIP streamer recommended specifications
Number of Number of 720p Number of 1080p Number of audio-only

vCPUs RAM streams streams streams
4 4GB 50 37 100
4 8GB 100 75 200
8 8GB 200 150 200
Key points to note (applies to new internal streamer component only):

l Number of vCPUs should not oversubscribe the number of physical cores.
l Maximum number of 720p streams supported is 200 regardless of adding more vCPUs.
l Maximum number of 1080p streams supported is 150 regardless of adding more vCPUs.
l Maximum number of audio-only streams supported is 200 regardless of adding more
vCPUs.

Appendix E Additional information on VMWare
E.1 VMWare
Core VMs should be configured to use the entire host. This ensures that a CPU core is available
for the ESXi kernel to perform management and network operations.
As part of internal testing we regular benchmark a variety of CPU and server configurations.
During these tests synthetic calls are added over time, gradually increasing the demands on the
VM and pushing it over capacity. Several internal statistics are monitored to ensure quality of
user experience. In addition, ESXi statistics are monitored and diagnostic logs are collected.
Although not recommended, it is possible to run other VMs alongside the Cisco Meeting Server
VM as long as CPU isolation domains are created to prevent contention. This technique is
known as “anti-pinning”, and involves explicitly pinning every VM to a subset of the cores. The
Cisco Meeting Server VM must be the only VM pinned to its cores, and all other VMs need to be
explicitly pinned to other cores.
For example, if a 20 core dual E5-2680v2 host is available, but only 25 concurrent 720p30 call
legs are required, then anti-pinning can be used. Using the 2.5 calls/core ratio, 10 physical
cores are required to provide this capacity. 10 cores can be used for other tasks.
With hyperthreading enabled, 40 logical cores are available and ESXi labels these logical cores
by index 0-39. The Cisco Meeting Server VM should be allocated 20 virtual CPUs and
configured with scheduling affinity 0-19. All other VMs running on the host must be explicitly
configured with affinity 20-39 to create the pair of isolation domains. It may also be necessary
to leave a physical core with no VMs pinned to it for the ESXi Hypervisor.
Figure 8: VM isolation domains created by pinning
VMXNet3 virtual network adapters are preferred as they require lower overhead than other
adaptor types. All virtual network adapters should be the same type.

VMware vMotion and High Availability (HA) technologies are fully supported. VMware Fault
Tolerance (FT) is not supported as it is limited to single virtual core VMs. High level tools such as
VMware vCenter Operations Manager are fully supported.
Note: If a VMWare hypervisor with EVC mode enabled is used, the EVC must be set to one of the

Appendix F Creating a certificate signed by a local Certificate Authority
Appendix F Creating a certificate signed by a local

Certificate Authority
This appendix covers the steps for signing the CSR using a local CA such as Microsoft Active
Directory server with the Active Directory Certificate Services Role installed.
1. Transfer the file to the CA.
2. Issue the following command in the command line management shell on the CA server
replacing the path and CSR name with your information:
certreq -submit -attrib "CertificateTemplate:WebServer"
C:\Users\Administrator\Desktop\webadmin.csr
3. After entering the command, a CA selection list is displayed similar to that below. Select the
correct CA and click OK.
4. Do one of the following:

l If your Windows account has permissions to issue certificates, you are prompted to
save the resulting certificate, for example as webadmin.crt. Go on to step c below.
l If you do not see a prompt to issue the resulting certificate, but instead see a message
on the command prompt window that the 'Certificate request is pending: taken under
submission', and listing the Request ID as follows. Note the RequestID and then follow
the steps below before going on to step c below.

5. Using the Server Manager page on the CA, locate the Pending Requests folder under the CA
Role.
6. Right-click on the pending request that matches the Request ID given in CMD window and
select All Tasks > Issue.
7. The resulting signed certificate is in the Issued Certificates folder. Double-click on the
certificate to open it and open the Details tab (see right).

8. Click Copy to File which starts the Certificate Export Wizard.

9. Select Base-64 encoded X.509 (.CER) and click Next.
10. Browse to the location in which to save the certificate, enter a name such as webadmin and
click Next.

11. Rename the resulting certificate to webadmin.crt.
Now transfer the certificate (e.g. webadmin.crt) and private key to the MMP of the Cisco
Meeting Server using SFTP, see Section 3.5.2.
CAUTION: If you are using a CA with the Web Enrolment feature installed, you may copy the CSR
text including the BEGIN CERTIFICATE REQUEST and END CERTIFICATE REQUEST lines to
submit. After the certificate has been issued, copy only the certificate and not the Certificate
Chain. Be sure to include all text including the BEGIN CERTIFICATE and END CERTIFICATE lines
and paste into a text file. Then save the file as your certificate with a .pem, .cer or .crt extension.

Cisco Legal Information
Cisco Legal Information

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE
SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND
RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE
PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE
FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT
ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE
INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE
SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE
FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program
developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version
of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University
of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND
SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE
ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED,
INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING,
USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL,
CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST
PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE
THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY
OF SUCH DAMAGES.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended
to be actual addresses and phone numbers. Any examples, command display output, network
topology diagrams, and other figures included in the document are shown for illustrative
purposes only. Any use of actual IP addresses or phone numbers in illustrative content is
unintentional and coincidental.
All printed copies and duplicate soft copies of this document are considered uncontrolled. See
the current online version for the latest version.
Cisco has more than 200 offices worldwide. Addresses and phone numbers are listed on the
Cisco website at www.cisco.com/go/offices.
© 2016-2020 Cisco Systems, Inc. All rights reserved.

Cisco Trademark
Cisco Trademark
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates
in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL:
www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their
respective owners. The use of the word partner does not imply a partnership relationship
between Cisco and any other company. (1721R)

Cisco Meeting Server 3 0 Installation Guide For Virtualized Deployments

Uploaded by

Copyright:

Available Formats

Cisco Meeting Server 3 0 Installation Guide For Virtualized Deployments

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cisco Meeting Server 3 0 Installation Guide For Virtualized Deployments

Uploaded by

Copyright:

Available Formats

Cisco Meeting Server

Cisco Meeting Server 3.0

December 09, 2020

Cisco Systems, Inc. www.cisco.com

4 Getting and Entering a License File 32

Appendix A Technical specifications for Cisco Meeting Server 1000 34

Cisco Meeting Server 3.0 : Virtualized Deployments 2

Appendix B Cisco licensing 36

Appendix E Additional information on VMWare 54

Appendix F Creating a certificate signed by a local Certificate Authority 56

Cisco Legal Information 60

Cisco Meeting Server 3.0 : Virtualized Deployments 3

Cisco Meeting Server 3.0 : Virtualized Deployments 4

December 09, 2020 Minor correction.

October 30, 2020 ESXi information updated.

October 06, 2020 Minor corrections.

September 09, 2020 Minor correction.

August 10, 2020 Updated for version 3.0.

April 01, 2020 Broken links fixed.

November 27, 2019 400v/410v references removed.

July 16, 2019 Corrected documentation error, reinserted Installation chapter

May 30, 2019 Minor documentation correction

April 26, 2019 Updated the supported versions of VMware ESXi

April 09, 2019 Miscellaneous corrections.

November 29, 2018 Miscellaneous corrections.

September 24, 2018 Removed Hyper-V section and references.

Cisco Meeting Server 3.0 : Virtualized Deployments 5

Table 1: ESXi version support

Cisco Meeting Server version ESXi version

3.0 ESXi 7.0b with Virtual Hardware version 17

2.9 ESXi 7.0b with Virtual Hardware version 17

2.8 ESXi 6.7

Cisco Meeting Server 3.0 : Virtualized Deployments 6

1.1 Overview of virtualized platforms

1.2 How to use this Guide

Cisco Meeting Server 3.0 : Virtualized Deployments 7

If you are installing a specification-based VM deployment, then go to Chapter 2, before going

Cisco Meeting Server 3.0 : Virtualized Deployments 8

Figure 1: Cisco Meeting Server installation and deployment documentation

Cisco Meeting Server 3.0 : Virtualized Deployments 9

1.3 Differences in specific MMP commands

on Cisco Meeting Server 1000

health Not available through MMP. Use Not available

serial Returns serial number of server. Not available

dns Do not specify an interface. Do not specify an interface.

dns add forwardzone dns add forwardzone

user evict Available from version 2.9 Available

1.4 Differences in components enabled on the different platforms

on Cisco Meeting Server 1000

Call Bridge Available Available

Cisco Meeting Server 3.0 : Virtualized Deployments 10

on Cisco Meeting Server 1000

Web Bridge 3 Available Available

Database Available Available

TURN server Not available Available

Recorder Not available Available

Uploader Not available Available

Streamer Not available Available

SNMP MIB Not currently available Available