Re: Cisco CUCM 11.5 and Cisco CMS 2.6 Non video in Conf Ad Hoc

nikita kochetkov · ‎09-24-2019

Hello, there is CUCM-CMS- the problem is this:

CMS is registered in the CUCM but when I collect the Ad Hoc conference there is only an audio call.

Nick Halbert-Lillyman · ‎09-26-2019

When you create the ad-hoc conference, does it say "welcome to a Cisco meeting" ? If so, you know you're at least hitting CMS, in which case maybe check your location settings.
If not, you're probably using the audio bridge on CUCM. I can't see your endpoint config on there, but make sure As-hoc conferencing is set to "Use Media Resource Group List" instead of "Use endpoint". You can also manually set the MRGL on the endpoint page on CUCM.

Sandro Nardi · ‎09-30-2019

Totally agree with @Nick Halbert-Lillyman be sure you are hosted on CMS and not on CUCM
my 2 cents, you can enable the detailed API tracing from the admin interface and check what's happening in real time using the "logging" command during an SSH session on the CMS.
check for possible connection error or certificate error Rendezvous call might work without a correct certificate exchange ad-hoc require proper certificate exchange for the api user to comunicate with CMS.

nikita kochetkov · ‎09-30-2019

CMS API Logs

2019-09-30  13:06:21.426  Info     API trace 39513:  <hostId>abb4f5d7-93ab-43bf-9c3b-ff632531ce55</hostId>
2019-09-30  13:06:21.426  Info     API trace 39513:  <softwareVersion>2.6.1</softwareVersion>
2019-09-30  13:06:21.426  Info     API trace 39513:  <uptimeSeconds>603585</uptimeSeconds>
2019-09-30  13:06:21.426  Info     API trace 39513:  <cdrTime>2019-09-30T10:06:21Z</cdrTime>
2019-09-30  13:06:21.426  Info     API trace 39513:  <activated>true</activated>
2019-09-30  13:06:21.426  Info     API trace 39513:  <clusterEnabled>false</clusterEnabled>
2019-09-30  13:06:21.426  Info     API trace 39513:  <cdrCorrelatorIndex>99</cdrCorrelatorIndex>
2019-09-30  13:06:21.426  Info     API trace 39513:    [ ... ]
2019-09-30  13:06:21.426  Info     API trace 39513:  </status>
2019-09-30  13:06:21.480  Info     API trace 39514: GET for "/api/v1/system/status" (from 10.176.252.28)
2019-09-30  13:06:21.480  Info     API trace 39514: sending 200 response, size 614
2019-09-30  13:06:21.480  Info     API trace 39514:  <status>
2019-09-30  13:06:21.480  Info     API trace 39514:  <hostId>abb4f5d7-93ab-43bf-9c3b-ff632531ce55</hostId>
2019-09-30  13:06:21.480  Info     API trace 39514:  <softwareVersion>2.6.1</softwareVersion>
2019-09-30  13:06:21.480  Info     API trace 39514:  <uptimeSeconds>603585</uptimeSeconds>
2019-09-30  13:06:21.480  Info     API trace 39514:  <cdrTime>2019-09-30T10:06:21Z</cdrTime>
2019-09-30  13:06:21.480  Info     API trace 39514:  <activated>true</activated>
2019-09-30  13:06:21.480  Info     API trace 39514:  <clusterEnabled>false</clusterEnabled>
2019-09-30  13:06:21.481  Info     API trace 39514:  <cdrCorrelatorIndex>99</cdrCorrelatorIndex>
2019-09-30  13:06:21.481  Info     API trace 39514:    [ ... ]
2019-09-30  13:06:21.481  Info     API trace 39514:  </status>
2019-09-30  13:06:24.299  Info     API trace 39515: POST for "/api/v1/coSpaces" (from 127.0.0.1:46200)
2019-09-30  13:06:24.299  Info     API trace 39515: content data size 66, type "application/x-www-form-urlencoded":
2019-09-30  13:06:24.299  Info     API trace 39515:  name=1002001036040004&
2019-09-30  13:06:24.299  Info     API trace 39515:  uri=1002001036040004&
2019-09-30  13:06:24.299  Info     API trace 39515:  callId=1002001036040004
2019-09-30  13:06:24.299  Info     API trace 39515: sending 401 response, size 0
2019-09-30  13:06:24.299  Info     API trace 39515: WWW-Authenticate: Basic realm="Cisco Meeting Server"
2019-09-30  13:06:37.009  Info     API trace 39516: GET for "/api/v1/system/status" (from 127.0.0.1:46222)
2019-09-30  13:06:37.009  Info     API trace 39516: sending 401 response, size 0
2019-09-30  13:06:37.009  Info     API trace 39516: WWW-Authenticate: Basic realm="Cisco Meeting Server"
2019-09-30  13:06:39.667  Info     API trace 39517: GET for "/api/v1/system/status" (from 10.176.252.18)
2019-09-30  13:06:39.668  Info     API trace 39517: sending 200 response, size 614
2019-09-30  13:06:39.668  Info     API trace 39517:  <status>
2019-09-30  13:06:39.668  Info     API trace 39517:  <hostId>abb4f5d7-93ab-43bf-9c3b-ff632531ce55</hostId>
2019-09-30  13:06:39.668  Info     API trace 39517:  <softwareVersion>2.6.1</softwareVersion>
2019-09-30  13:06:39.668  Info     API trace 39517:  <uptimeSeconds>603603</uptimeSeconds>
2019-09-30  13:06:39.668  Info     API trace 39517:  <cdrTime>2019-09-30T10:06:39Z</cdrTime>
2019-09-30  13:06:39.668  Info     API trace 39517:  <activated>true</activated>
2019-09-30  13:06:39.668  Info     API trace 39517:  <clusterEnabled>false</clusterEnabled>
2019-09-30  13:06:39.668  Info     API trace 39517:  <cdrCorrelatorIndex>99</cdrCorrelatorIndex>
2019-09-30  13:06:39.668  Info     API trace 39517:    [ ... ]
2019-09-30  13:06:39.668  Info     API trace 39517:  </status>

As you can see from the log, the conference is going without CMS