You can view the
Traversal and Non Traversal license usage for all VCS clusters, and individual
VCS servers in a cluster, and standalone VCS server(s).
Click on a particular
cluster name to see the VCS servers in that cluster. You can view Traversal and
Non Traversal license usage, Registration usage (number of endpoints, MCUs etc
registered with the VCS), and cluster to which the VCS server belongs to.
None to see the data for standalone VCS server(s).
Mouse over the
Traversal Usage, Non Traversal Usage and Registered Usage columns in the
dashlet to view the number of licenses available, number of licenses used and
number of licenses not used.
This dashlet does not
auto refresh. You have to refresh the dashlet to get current data.
For VCS version 7.0
and later, any traversal or non-traversal call licenses that have been
installed on a cluster peer are available for use by any peer in the cluster.
For versions earlier than 7.0 licenses are not shared across the cluster; each
peer can only use the licenses that are installed in it.
The number of
licenses that can be installed on any one individual peer is limited to the
maximum capacity of each VCS unit, as follows:
- 500 non-traversal calls
- 100 traversal calls
- 2,500 registrations
licenses are not shared across a cluster. If a cluster peer becomes
unavailable, the shareable licenses installed on that peer will remain
available to the rest of the cluster peers for two weeks from the time the
cluster lost contact with the peer. This will maintain the overall license
capacity of the cluster - however, each peer is still limited by its physical
capacity as listed above. After this two week period, the licenses associated
with the unavailable peer are removed from the cluster. To maintain the same
capacity for your cluster, you should ensure that either the problem with the
peer is resolved or new option keys are installed on another peer in the