Cisco Meeting Server (CMS): Basic Configuration

Cisco Meeting Server (CMS): Basic Configuration

Hello, in this article you can find the basic configuration steps and how to enable web interface of Cisco Meeting Server (CMS).

There are 3 different interfaces for configuring Cisco Meeting Server: command line (CLI), GUI and API. The first CLI interface can be accessed via the server’s console or SSH (after the IP address is given). Now let’s start with the basic configuration steps, starting with the CLI interface and continue with switching to the GUI interface:

Cisco Meeting Server CLI Basic Configuration

When you connect to CMS via console, a login screen is displayed. You can log into CMS with default user admin and admin as password. After you log in, it asks you to change the password.

After passing this step, we can proceed to IP settings. By default, the CMS uses the IP which is received via DHCP, and if you want to configure CMS with a static IP address, you can use the following CLI command according to your own settings:

ipv4 a add 

In this command, a is the name of a interface, the IP address /24 is subnet mask and as you would expect is default gateway.

Once you set the IP address, you can now connect to the CMS over SSH.

You can change the hostname which is defined as acano by default by issuing this command:

hostname cms1

After this command, the CMS will ask you to reboot CMS in order to activate new hostname. You can reboot the CMS with the reboot command.

You need DNS and NTP servers for CMS to work properly. Considering that they are already up and running, enter the following DNS (.100) and NTP (.101) IP configurations:

ntp server add
dns add forwardzone .

You can noe continue with the configuration to activate the GUI.

WEB GUI Configuration

In order to use the web GUI, first you need a certificate for HTTPS connections. This certificate can be either a self-signed or a CA-signed certificate. For ease of operation, you can use the self-signed certificate by issuing this command:

pki selfsigned cms1

After that, specify the interface and HTTPS port for the web interface:

webadmin listen a 445

For the certificate (s) to be used, we specify the self-signed certificate created in the upper section and with the relevant key:

webadmin certs cms1.key cms1.crt

You can use the following command to route HTTP requests to HTTPS:

webadmin http-redirect enable

Then finally activate the web admin module:

webadmin enable

Now you can use the web interface with same CLI user.

You can also find these procedures in the video below:

Cisco Meeting Server (CMS) Basic Configuration

At this point, I must point out that you need to use either CLI, GUI and API interfaces to configure the different services of CMS. So this means that you can’t do everything from GUI or CLI only. I hope this situation will change with next releases.

Comments are closed.