Scheduled TMS meetings dropout

Had a scheduled meeting booked last month in TMS for multiple Cisco endpoints and MCU cluster (cms) all hunky dory.

Come meeting time, none of the endpoints joined the meeting. Your call could not be found. Straight to PIR mode and root cause analysis. Bloody hell.

A change was performed 2 weeks back where a new node joined the cms call bridge with no issues but one. Tested adhoc/rendezvous/conference calls/TMS scheduled calls with no issues.

So that one issue was that CMM showed an error where the cms cluster was out of compliance. It didn’t affect meetings as I had 90 days to rectify it. Since we are running traditional licensing for now, Cisco TAC identified a missing lic file and once that was uploaded to the new node; the callbridge was restarted all good and cmm showed in compliance.

Now come meeting time. All 20 endpoints didn’t even bother to join the call. RTMT showed the numbers not even going beyond cucm. No link established with the cms cluster. Shit.

Now the fix was to readd the mcu in TMS. I want to know if that callbridge restart caused TMS to drop scheduled meetings because there is no way to know for sure what exactly caused this looking at logs and trying to replicate the problem.

Anyone have any ideas what could’ve caused this?