01-03-2019 07:49 AM
Hi,
After setting up and configurating CMM according to the documentation Cisco has provided, I've been noticing how there is a delay between an actual set up of a new call in the Cisco Meeting Server until it is displayed in the CMM. After a couple of tests i've concluded that the delay is about 4 min and 30 seconds long before the meeting is displayed in CMM.
The CMS recieves the correct CDR information from CMM. However, this warning keeps popping up in the CMS event log:
CDR events; in connecting state for 60 seconds, abort and restart connection.
Anyone got any ideas?
Best regards, Mathias
01-06-2020 05:49 AM
mathias.bolin1 , have you had any resolution to this issue? I'm having the same problem but in our case we are using VQ Conference Manager and running CMS 2.5.1.
12-20-2020 08:02 PM - edited 12-20-2020 08:03 PM
Good day.
We have the same problem.
CDR events; in connecting state for 60 seconds, abort and restart connection for xxxxx.xxxxx.xxx/meetings/cdr/1/?token=xxxxx
So far, CMS and CMM 3.0.1 have not been able to solve it
12-20-2020 11:07 PM
12-20-2020 11:18 PM
There is a connection.
05-01-2021 04:35 AM
Did you resolve this?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide