The information in this document is based on these software and hardware versions:
CMS version 3.0
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
Step 1. Sign in to the Webadmin Interface of the CMS.
Step 2. Navigate to Configuration > Cluster.
Note: Please keep in mind this menu is only displayed if the database cluster is already created.
Step 3. Over the section displayed, enter a unique name for that Callbridge and submit the change.
Note: The name configured must not contain any spaces, otherwise, clustering process fails.
Note: Peer link bit rate and participant limit parameters are optional and you can leave them blank.
Step 4. Repeat Step 1 to 3 for all the CMS servers with Callbridge service to be part of the Callbridge cluster.
Step 5. Navigate to Configuration > Cluster.
Step 6. On the table Clustered Call Bridges, enter the unique name of every Call Brdige part of the cluater.
Step 7. Enter the IP address of the corresponding Call Bridge on the field Address.
Note: The IP address for every callbridge must be the webadmin IP address with the webadmin port in case it is not the default 443.
Step 8. The Peer Link SIP Domain field can be blank as long as there are no Call control devices between your Call Bridges. If you specify a Peer Link SIP Domain, it is used when you call to a remote server.
Step 9. Select Add New for evey Call Bridge part of the cluster. The next image shows these Steps.
Step 10. Repeat Steps 5 to 9 for all the Call Bridges planned to be part of this cluster, as the image:
In order to verify all the CMS Call Bridges are properly joined to the cluster, access to the Webadmin interface of every peer and navigate to Configuration>Cluster, validate the status refers to itself as This Call Bridge for the specific server you validate.
For the rest of the peers listed, the status reported must be connection active, as shown in the image: