This document describes how to enable and configure Call Bridge service on Cisco Meeting Server (CMS). The Call Bridge service exchanges audio and video streams so that participants can see and hear each other.
Contributed by Jefferson Madriz and Octavio Miralrio, Cisco TAC Engineers.
Cisco recommends that you have knowledge of these topics:
- Domain Name Service (DNS)
- CMS network configuration
- Certificate Signing Request (CSR)
- Secure Shell (SSH) client
- Secure File Transfer Protocol (SFTP) client
The information in this document is based on these software and hardware versions:
- CMS version 3.0
- Putty SSH client
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.
The Call Bridge is the component of the Cisco Meeting Server that bridges the conference connections, it enables multiple participants to join meetings hosted on the Cisco Meeting Server.
Step 1. Access to the CMS Command Line Interface (CLI) with SSH client of your preference.
Step 2. Configure the Call Bridge to listen on any available interface. The default interface is a. Run the next command:
callbridge listen a
Note: The Call Bridge must listen on a network interface that is not use for Network Address Translation (NAT’d) to another IP address.
Step 3. Assign the certificate, key, and bundle file to the Call Bridge service. Run the next command:
callbridge certs singleCert.key singleCert.cer cacert.cer
Note: In case you need to check the certificates stored on CMS server, run the next command: pki list.
Step 4. Run the command callbridge restart to restart the Call Bridge to apply the changes.
Step 5. Validate you get SUCCESS lines returned stating that the Call Bridge is correctly configured for network and certificate values.
Run the commad callbridge, and validate that interface and certificates are correct.