Cisco Meeting Server Deployment Notes

[Meddane]

To simplify explaining how to deploy the Meeting Server, deployments are described in terms of three models:

• Single combined Deployment — all Meeting Server components (Call Bridge, WebBridge 3, Database, Recorder, Uploader, Streamer and TURN server) are available, the CallBridge and Database are automatically enabled but the other components can be individually enabled depending upon the requirements of the deployment. All enabled components reside on a single host server.
• Single split Deployment — in this model the TURN server, Web Bridge 3, and MeetingApps are enabled on a Meeting Server located at the network edge in the DMZ, while the other components are enabled on another Meeting Server located in the internal (core) network.
• Scalablity and Resilience Deployment — covers deploying multiple Meeting Servers clustered together to provide greater scale and resilience in the deployment.

The Cisco Meeting Server 2000 only has the Call Bridge, Web Bridge 3, and database components. It is suited for deployment on an internal network, either as a single server or a cascade of multiple servers. The Cisco Meeting Server 2000 should not be deployed in a DMZ network. Instead if a deployment requires firewall traversal support for external Cisco Meeting Server web app users, then you will need to also deploy either:

• a Cisco Expressway-C in the internal network and an Expressway-E in the DMZ, or

• a separate Cisco Meeting Server 1000 or specification-based VM server deployed in the DMZ with the TURN server enabled.

The Cisco Meeting Server 1000 and specification-based VM servers have lower call capacitiesthan the Cisco Meeting Server 2000, but all components (Call Bridge, Web Bridge 3, Database, Recorder, Uploader, Streamer and TURN server) are available on each host server. The WebBridge 3, Recorder, Uploader, Streamer and TURN server require enabling before they are operational.

Cisco Expressway VS CMS Edge comparison for WebRTC

Cisco Expressway

• EXP as TURN & reverse HTTPS proxy

• WB3 needed in core even for external only participants

• SIP & web app participants both. Make sure you do the capacity planning well as the capacities are very different for SIP and webapp via Expressway

• Recommended for Small & Medium CMS deployments

• Small, Medium & Large Expressway OVA supported

• Only 1 EXP cluster (web app participants) supported per CMS

CMS Edge

• Same CMS software but with only TURN & WB3 services enabled

• WB3 not needed in core if external only participants

• web app participants only

• Needed for Large deployments, can also be used for Small & Medium

• Small & Large CMS Edge options

• CMS TURN or WB3 don’t need clusters to work. So can scale vertically till 10 TURN per CB/CBG

• Only Single NIC supported

• CMS 3.0 (& above) supports WB3

• Multiple web app join links cluster. Multiple EXP clusters can be used for SIP participants

• Single & Dual NIC supported

• EXP 12.6+ supports WB3

• Single web app join link