cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
6898
Views
58
Helpful
18
Replies

CMS 2.2 ad hoc call not work

samhopealpha
Level 1
Level 1

Hi Everybody, 

I am going to create an adhoc conference with Internal CA

But CUCM still showing the CMS registration "unknown" state

By following the guide (section 4: Setting up escalated ad hoc calls)
https://www.cisco.com/c/dam/en/us/td/docs/conferencing/ciscoMeetingServer/Deployment_Guide/Version-2-2/Cisco-Meeting-Server-2-2-Deployments-with-CUCM.pdf


Version
CUCM 11.5
CMS 2.2.5
SX20 ce 8.3.2
mx800 ce 8.3.2
Cisco TelePresence DX70 ce 8.3.2

  • The endpoints are all updated to ce 8.3.2
  • Rendezvous call is tested successfully
  • The SIP trunk is TLS already between CUCM and CMS.

acano> webadmin
Enabled : true
TLS listening interface : a
TLS listening port : 443
Key file : webadmin.key
Certificate file : webadmin.crt
CA Bundle file : cacert.pem
HTTP redirect : Enabled
STATUS : webadmin running
acano> 
acano> 
acano> 
acano> callbridge 
Listening interfaces : a
Preferred interface : a
Key file : callbridge.key
Certificate file : callbridge.crt
Address : none
CA Bundle file : cacert.pem
acano>

In CUCM,

HTTP inferface info
Override sip trunk destination as http address: <Tried checked and unchecked>
username : <tried the username with admin role and API role>
HTTPS port: 443

Anybody know what's the problem why CMS cannot register to CUCM?

Thanks in advance


Sam

18 Replies 18

 

Issue got fixed and adhoc CFB is now registered after issue commands tls webadmin min-tls-version 1.0 & tls sip min-tls-version 1.0

 

I , i have the same problem and i already upgrade my cucm from 11.0 to 11.5.1.14900-11

 to  have Cisco Meeting server in conference bridge type , i have also upgraded my  cms to 2.2.3 , and my sip trunk (with or without TLS)  is up and i have meet me conferences , but i cant never have ad-hoc cfb registered to my cucm.

Can someone help?

I have same issue. CMS not registering as CFB on the CUCM.

 

CUCM Ver: 12

CMS ver : 2.4

 

Using Private CA to sign all the certificates, no certificate errors when using FQDN to access CMS from browser.

Secure SIP trunk working fine with calls.
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: