How are licenses used on a cluster of Call Bridges?


Prior to 3.0:

You need a license file for each individual Call Bridge—licenses can only be shared 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, ACU, Recording/Streaming.

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.

A single conference run across multiple Call Bridges in a cluster, will consume a single license. Weighted calls are a means of measuring the number of conferences across the cluster. Use the parameter weightedCallsActive on API object /system/multipartyLicensing. The sum of weighted calls across a cluster matches the number of conferences 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 licenses are required.

3.0 onwards:

Note: 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).

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.

Meeting Management with Smart Licensing tracks how many Call Bridges per cluster, thereby eliminating the need for the R-CMS-K9 activation license.

Last update:
08-Sep-2020
FAQ ID:
1333