How to Configure Webbridge 3 on CMS

Introduction

This document describes how to configure and enable Web Bridge service on Cisco Meeting Server (CMS) version 3.0.

Contributed by Jefferson Madriz and Octavio Miralrio, Cisco TAC Engineers.

Prerequisites

Requirements

Cisco recommends that you have knowledge of these topics:

• Domain Name System (DNS)
• CMS general configuration
• Certificate Signing Request (CSR)
• Secure Shell (SSH) client

Components Used

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.

Configuration

Step 1. Assign the interface to Web Bridge. 

Note: The Web Bridge 3 and Call Bridge to Web Bridge (c2w) configuration use the fullchain certificate files. They do not use the server certificate file as with previous Cisco Meeting Server conventions.

1. Access the CMS Command Line Interface (CLI) with your preferred SSH client.
2. Configure Web Bridge 3 to listen on Interface a and port 443.

webbridge3 https listen a:443

3. Configure Web Bridge 3 service with the certificate key and full chain certificate file generated.

webbridge3 https certs singleCert.key mxcbundle.crt

4. The Web Bridge 3 supports Hypertext Transfer Protocol Secure (HTTPS) redirection. Use this command to enable it, if desired:

webbridge3 http-redirect enable

Step 2. Configure the c2w connection.

1. Configure the Call Bridge to Web Bridge 3 (c2w) connection to listen on Interface a and port 9999.

webbridge3 c2w listen a:9999

2. Configure the c2w interface to use the server certificate, private key and full chain certificate file generated.

webbridge3 c2w certs singleCert.key mxcbundle.pem

3. Configure the c2w interface to trust the Call Bridge certificate, use the full chain certificate file generated.

webbridge3 c2w trust mxcbundle.pem

4. Enable the Web Bridge 3 service.

webbridge3 enable

5. Validate that the outputs are SUCCESS messages as shown in the image:

Step 3. Define Web Bridge 3 in Call Bridge.

The Call Bridge must be told where to connect to Web Bridge and how to verify the certificate that the c2w interface presents. This requires both Mainboard Management Processor (MMP) and Application Programing Interface (API) configuration.

1. Configure the Call Bridge to trust the c2w interface of Web Bridge 3, use the full chain certificate file assigned to the c2w interface of Web Bridge 3.

callbridge trust c2w mxcbundle.pem

2. Create an API object on /api/v1/webBridges. 
3. Log in to the Meeting Server Web Admin interface and select Configuration > API:
4. In the Filter input box, type webBridges to filter the list view.

5. Select the arrow next to webBridges.
6. Select Create new to create a new webBridge object.

7. Enter the url field, use the format c2w://:9999 with the FQDN value used on the CMS certificate, as shown in the image:

8. From the Web Admin interface, select Configuration > General.
9. On Web Bridge URI setting, configure the HTTPS URL for your Meeting Server.

10. Select Submit to save the changes.

Verify

1. Open an SSH session to the CMS.
2. Run the command webbridge3 to display the configuration.

3. From the Web Admin interface, select Status > General and validate that there are no alarms in Fault Conditions.