This document describes the single split deployment of Cisco Meeting Server (CMS), what is the scope and difference with single combined deployment.
Contributed by Jefferson Madriz and Octavio Miralrio, Cisco TAC Engineers.
There are no specific requirements for this document.
This document is not restricted to specific software and hardware versions.
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.
Note: Cisco Meeting Server version 3.0 does not support X-Series servers.
Note: Cisco Meeting Server 3.0 introduces a mandatory requirement to have Cisco Meeting Management (CMM) version 3.0 or later.
Note: All of the Meeting Servers in the deployment must run the same version of software.
In a split server deployment, the CMS services are splitted on different servers, Callbridge and Database remain in a Core CMS server, Webbridge and Traversal Using Relays around NAT (TURN) services are configured in an Edge CMS server. Keep in mind Uploader, Recorder and Streamer services, must be enabled on a separate server.
For Split deployment, external webRTC services must be provided by TURN server configured on CMS edge, in this scenario provide webRTC services via Expressway server is not supported, in order to use Expressway as the TURN server to provide webRTC services, it is required to use Single Convined deployment. The difference is that TURN services are provided by Expressway and webbridge is enabled on CMS core, as shown in the next image:
In the single split deployment, the TURN services are provided by CMS edge, and the webbridge services is configured in the CMS edge while the callbridge services is enabled on CMS core, as shown in the next image:
Caution: If you enabled Web Bridge 3 and web app you must use Expressway version X12.6 or later, earlier Expressway versions are not supported by Web Bridge 3.
In a typical CMS split deployment, services are divided in two different CMS servers, the Core and the Edge. The Edge server is the one that provide TURN services for Media, and it is recomended to use the webbridge in order to enable webRTC services internal and externally to the network, as shown in the image:
Configure the Cisco 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 bootstrapping, and configuration via its command line interface. For example, the MMP is used to enable the Web Bridge, Database and other components.
- The Application runs on the MMP platform. Administration of the application level (call and media management) can be done via the callbridge's Web Admin interface or through the Application Programming Interface (API) if you prefer. The API uses Hypertext 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 you need to configure multiple Call Bridges via the API and third party API tools, such as POSTMAN.
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 theConfigurationtab of the Meeting Server web interface, as shown in the image:
More details related to capacity and ports can be find on links below: