Enabling the Web Admin Service on Cisco Meeting Server using CLI.
Before it can be enabled, the Web Admin service must be configured with the correct certificate to use. The certificate should be signed by a Certification Authority.
To view the list of certificates generated before enabling the webadmin service, Type the command: pki list in the command line to view these certificates. for example:
To generate a CSR named 1cert use the following command:
pki csr 1cert CN:lab.local OU:CCNP O:Collaboration L:lab ST:local C:US subjectAltName:webbridge.lab.local,xmpp.lab.local,callbridge.lab.local,join.lab.local,webadmin.lab.local,cms-a.lab.local,cms-b.lab.local,*.lab.local
Submit the CSR to your CA and download the certificate, and copy it using WinSCP.
For the certificate to be used for webadmin, specify the certificate created previously called 1cert.cer with the relevant key 1cert.key and the CA’s certificate, called in my scenario Bundle-CA.
Type webadmin listen a 445 command, This command instructs Web Admin to listen on interface a port 445.
By default, Web Admin listens on the standard HTTPS port of 443. However, if you are planing to use WebRTC, it is best practice to enable the Web Bridge for conference users and want that service to be available on the default HTTPS port. To enable both services to co-exist, configure Web Admin to listen on port 445 and require administrators to use the url https://ip address of cms:445 to access the CMS’ s GUI.
Finally enable the webadmin service as shown below.
Use the webadmin command to verify that network and certificate values are configured correctly.
Now the CMS is accessible through the GUI using the port 445.
Access the Cisco Meeting Management GUI.
In the Settings at the right, go to License and select Smart Licensing option.
Navigate to License at the right, and click the Start Trial button at the left. Make sure the CMM has internet connectity to register for Trial Mode.
Add a CallBridge to CM
Click Servers to add a Callbridge to CMM. Click Add Call Bridge.
Add the following information:
a. Server Address: 10.1.5.50
b. Port: 445
c. Username: admin
d. Password: (your password)
e. Display name: CMS-A
Now you Cisco Meeting Server is ready for 90 days of trial.
I created an Incoming Call with the domain firstname.lastname@example.org.
I created a space named Demystify From Scratch Meeting with SIP User Part ccnp.
From an IP Phone registred into a CUCM call the URI email@example.com. I used a speed dial because the CIPC does not support URI dialing.
The IP Phone is connected to a Meeting named Demystify From Scratch Meeting and the CMM displays a Meeting with one participant.
Do not forgot a SIP Trunk on the Call Control CUCM to CMS and SIP Route Pattern with the Domain Routing collab.lab.local, point this SIP Route Pattern to the SIP Trunk, this SIP Route Pattern must match the Incoming Call created previously on the CMS.
Note: Do not forgot to write a comment below……..