- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-10-2017 03:53 AM - edited 03-18-2019 01:05 PM
Hi guys,
Since the MCU is at the end-of-sales, I am looking for an equivalent device, so Cisco documentation seems to designate CMS as replacing, However, I would like to know whether:
- CMS includes built-in gatekeeper like in MCU ?
- CMS allows to join conference without using any gatekeeper registration ?
- CMS recording and streaming option allows me to dispense with the order of a specialized device like Cisco Telepresence Content Server TCS ?
Thank you in advance,
Sofiane
Solved! Go to Solution.
- Labels:
-
Room Endpoints
Accepted Solutions

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-10-2017 06:26 AM
There is no built-in gatekeeper like the MCU products, so endpoints must be registered to CUCM/VCS or third-party call control server.
Standalone endpoints can dial into CMS, for H323 calls, they should first go through an VCS/Expressway to interwork between H323-SIP.
TCS is EOS (eos-eol-notice-c51-738128), and the replacement is CMS. The recording option of CMS can record and stream conferences, however a streaming solution such as VBrick Rev is required to view the recordings and live streams as CMS doesn't have a built-in portal.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-10-2017 05:58 AM
Hi Sofiane,
The features related info is available in the datasheet, the call capacity of CMS based on platform is given below
able 2. Call Capacity on Supported Servers
Type of Call |
Cisco Meeting Server 1000* |
Cisco Meeting Server 2000** |
Full HD calls (1080p30) |
48 |
250 |
HD calls (720p30) |
96 |
500 |
SD calls (448p30) |
192 |
1000 |
Audio calls |
3000 |
3000 |
http://www.cisco.com/c/en/us/products/collateral/conferencing/meeting-server/datasheet-c78-737519.html
CMS can be deployed in different ways as per the config guides below
http://www.cisco.com/c/en/us/support/conferencing/meeting-server/products-installation-and-configuration-guides-list.html
Manish
- Do rate helpful posts -

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-10-2017 06:26 AM
There is no built-in gatekeeper like the MCU products, so endpoints must be registered to CUCM/VCS or third-party call control server.
Standalone endpoints can dial into CMS, for H323 calls, they should first go through an VCS/Expressway to interwork between H323-SIP.
TCS is EOS (eos-eol-notice-c51-738128), and the replacement is CMS. The recording option of CMS can record and stream conferences, however a streaming solution such as VBrick Rev is required to view the recordings and live streams as CMS doesn't have a built-in portal.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-10-2017 08:09 AM
Hi Patrick,
Thanks for your complete answer. However, since CMS does not support streaming I do not understand why in Cisco Meeting Server and Cisco Meeting App Data Sheet at "Ordering Information" section it is mentioned "3. Options such as branding or recording and streaming can be added." ?
Sofiane

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-10-2017 08:55 AM
CMS supports recording and streaming, streaming was introduced in CMS 2.1. CMS generates a flash stream, so it needs an external streaming server to distribute it so it can be viewed, such as VBrick Rev. Suggest you take a a look at the CMS Configuration Guides, they can help answer some of your questions, as well as how CMS is configured and operates.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-11-2017 01:39 AM
I understand now, thank you for assisting me.
Regards,
Sofiane
