This document describes, the definition and scope of Single combined deployment for Cisco Meeting Server (CMS) based on Cisco Unified Computing Server (UCS) technology or based Virtual Machine (VM) server.
Contributed by Jefferson Madriz and Octavio Miralrio, Cisco TAC Engineers.
Note: CMS software version 3.0 does not support X-Series servers.
Note: CMS software version 3.0 introduces a mandatory requirement to have Cisco Meeting Management (CMM) 3.0 or later.
CMS virtual server
Cisco recommends that you have knowledge of these topics:
CMS basic configuration
The information in this document is based on these software and hardware versions:
CMS virtual server version 3.0
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
In a single combined deployment, all services are supposed to be configured within the same server, excep for recorder, streamer and uploader, in the case of the CMS 2000, it is assumed the Traversal Using Relays around NAT (TURN) services are provided by Expressway server. Callbirdge, Webadmin and Webbridge reside on the same CMS server, as shown in the image:
Note: For test purposes, the recorder, streamer and uploader can be configured on the same CMS server, however, in a production environment, it is recomended to use different CMS servers for each service in order to avoide performance issues.
The CMS supports integration with on prem Cisco Unified Communication Manager (CUCM) and with on prem Webbridge and proxy Webbridge via Expressways, in the proxy Webbridge, the TURN services are managed by Expressway-E server, as shown in the image:
The CMS also spport integration with Skype for business on pem and Office 365 (O365), same as in the proxy Webbridge, the Expressway-E is used as TURN server, as shown in the image:
Note: If you deploy Webbridge 3 and web app you must use Expressway version X12.6 or later, earlier Expressway versions are not supported by Web Bridge 3.
Configure the Meeting Server.
There are two layers to the Cisco Meeting Server software: a Platform and an Application.
The Platform is configured through the Mainboard Management Processor (MMP). The MMP is used for low level bootstrap, and configuration via its Command Line Interface (CLI). For example, the MMP is used to enable the Webbridge, Database cluster and various other components.
The Application runs on the MMP platform. Administration of the application level like call and media management, can be done via the Callbridge's Webadmin interface or through the Application Programming Interface (API) if you prefer. The API uses Hipertext Transfer Protocol secure (HTTPS) as a transport mechanism and is designed to be scalable in order to manage the potentially very large numbers of active calls and spaces available in a deployment.
Note: Prior to version 2.9 software you need to configure multiple Callbridges via the API and third party API tools, such as Postman and only use the Webadmin interface for a single Callbridge.
To simplify the use of API without the need for third-party applications, version 2.9 introduced a user interface for the API that can be accessed via the Configuration tab of the Meeting Server web interface.
The next image shows the components that can be configured within the CMS and the basic integration with Expressway and Lync.
More docmuentation that covers Cisco Expressway-E as the edge device for Meeting Server, is available on links below: