Cisco CMS Ad-hoc conferencing with CUCM

Ad-hoc as a common type of meeting, you can easily and easily implement three-party or more party meetings, next will show how to use the CMS as meeting Bridge resources to implement Ad-hoc. This article uses CUCM11.5SU1 and CMS2.3.3 as the experimental case, please complete the corresponding configuration according to your own environment.

Attention
CUCM11.5 SU3 Previous version, using the TLS 1.0 version, cms2.3+ using the TLS1.2 version, if CUCM11.5 SU3 before the integration with cms2.3+, need to modify the CMS TLS version information, please refer to the command:
CMS Command:

TLS WebAdmin Min-tls-version 1.0
TLS SIP Min-tls-version 1.0

The following is the configuration process:

1. Certificate-related Configuration
2. CMS-related configuration
3. CUCM-related configuration
4. Test

1. Certificate-related Configuration
   CUCM and CMS implementations Ad-hoc must implement the mutual trust of the certificate and therefore require the following certificate request (CA or OpenSSL)
   (1) Required certificates for CUCM side:
   A. Download the root certificate from the CA or OpenSSL, as shown in the CA as an example:
   

   B. Upload the root certificate to Callmanger-trust
   Login Cucm>cisco Unified OS administration>security>certificate Management Click Upload certificate/certificate Chain, fill in the parameters, click Upload.
   Certificate purposerequired Field:callmanager-trust
   Description (friendly name): CUCM Trust ROOTCA from CA
   Upload File:rootca.cer (Find the corresponding ROOTCA according to your own name)
   

    C. CUCM申请callmanager证书并上传到Callmanager 1). 申请CSR,Generate Certificate Signing Request         Certificate PurposeRequired FieldRequired Field: CallManager        DistributionRequired Field:默认即可        Common NameRequired Field:默认即可Subject Alternate Names (SANs)         Parent Domain: cms.bv.lab(域名)         Key TypeRequired FieldRequired Field   RSA          Key LengthRequired Field: 默认即可（2048）         Hash AlgorithmRequired Field: 默认即可（SHA256）

   
   
   2). Download the generated CSR
   3). Generate a CER
   Login CA http://10.79.246.137/certsrv->Request A certificate->advanced certificate Request, click Submit
   
   4). Upload the certificate to CUCM CallManager
   Login Cucm>cisco Unified OS administration>security>certificate Management Click Upload certificate/certificate Chain, fill in the parameters, click Upload.
   

(2) CMS side certificate
A. Generate the CSR and download CAMA.CSR. CN: Domain name subjectaltname:cms all domain names and addresses in cluster

PKI CSR CMSA CN:cms.bv.lab Subjectaltname:cmsa.cms.bv.lab,cmsb.cms.bv.lab,cmsc.cms.bv.lab, 10.79.246.177,10.79.246.178,10.79.246.185
PKI list
User supplied certificates and keys:
Cmsa.key
CMSA.CSR
B. Generate CER
Login CA http://10.79.246.137/certsrv->Request a certificate->advanced certificate Request , click Submit
C. Upload root certificate and CMS certificate
PKI list
User supplied certificates and keys:
Cmsa.cer
Rootca.cer

2. CMS-related configuration
   A. Configure Callbridge
   cmsa> callbridge
   Listening interfaces:a
   Preferred interface:n One
   Key file:cmsa.key
   Certificate file:cmsa.cer
   Address:none
   CA Bundle file:rootca.cer
   B: Configuration Webadmi N
   cmsa> webadmin
   enabled:true
   TLS listening interface:a
   TLS listening port:8443
   Key file:cmsa.ke Y
   Certificate file:cmsa.cer
   CA Bundle file:rootca.cer
   HTTP redirect:disabled
   Status:webadmin runningC: Configuring incoming call
   

3. CUCM-related configuration
   A: Upload CMS webadmin certificate to Callmanager-trust
   B: Add Trunk
   C:SIP profile
   Use Fully qualified Domain Name in SIP requests required
   Conference Join Enabled Required
   Deliver Conference Bridge Identifier must be selected
   Enable options Ping to monitor destination status for trunks with Service Type "None (Default)" optional
   Allow Presentation sharing using BFCP optional
   Allow IX application Media selectable
   Allow multiple codecs in answer SDP optional
   D: Add Conference Bridge. HTTP Port is the port number for the CMS WebAdmin login (note:cucm11.5su3 The following versions, Conference Bridge type can only select "Cisco telepresene conductor", CUCM11.5SU3 above version can select "Cisco meeting Sertver")
   

Cisco CMS Ad-hoc conferencing with CUCM