Add a new cluster of Cisco Meeting Server nodes to be connected to your Mividas Core installation.

To add a new Cisco Meeting Server cluster, start by navigating to Mividas Core > Admin > Video meeting bridges. In the upper right of the screen click the ( ) icon which will show you a list of available options, select Cisco Meeting Server to proceed.

This section is for you who want to create a new cluster, CMS nodes can also be connected to existing clusters which are done via the video meeting bridge dashboard. Read more about this in the Video meeting bridges documentation.

Cisco Meeting Server cluster onboarding

After selecting to create a new Cisco Meeting Server cluster from the video meeting bridges view you will be redirected to the onboarding for creating a new cluster. The first step is to specify settings for the cluster described below:

  • Description – The cluster description is used for identifying the cluster in the interface.
  • Type – The type of cluster to create, be sure “CMS Cluster” is selected.

Cluster settings

  • Primary SIP domain – The SIP domain to use eg. with meeting invitations.
  • WebRTC/Web access hostname – WebRTC hostname to use eg. with meeting invitations.
  • IVR phone number – IVR phone number to use eg. with meeting invitations.

Standard number series

  • Static rooms numbers – Number intervals to use for when static virtual meeting rooms are created.
  • Scheduled rooms numbers – Number intervals to use for when scheduled virtual meeting rooms are created.

Additional cluster settings

After adding a new cluster additional advanced settings will be available when editing the cluster settings. Read the Editing clusters documentation for further information.

Adding a Cisco Meeting Server

The next step is to add your Cisco Meeting Servers nodes to your newly created cluster. You can also add CMS nodes that do not contain an active call bridge, e.g. CMS database server, CMS edge, and CMS Webbridge.

  • Description – A short description for the new Cisco Meeting Server node.
  • IP address – The IP address for the node.
  • Ev. separate IP/host for API calls – Choose if you want network separation for all API calls, so that traffic will go through a separate hostname if you want to add firewall rules or the like.
  • DNS Name – The Cisco Meeting Server’s DNS name.
  • Username and password – Specify the username and password in order for Mividas Core to be able to connect to the CMS node.
  • Synchronize tenants from CMS – If checked Mividas Core will synchronize available tenants from the CMS node.
  • Set CDR receiver for statistics – Option for retrieving call statistics from the connected CDR receiver.
Print page

On this page