cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
138
Views
0
Helpful
0
Replies

Cisco TMS Failed to Alocate Meeting in CMS

ggomes63
Level 1
Level 1

Good Morning everyone,

We have a Cisco Unified on-prem Conferencing environment with the following components (all with latest releases):
CUCM - Endpoints registration and handling (both Cisco and Polycom conferencing kits - SIP)
CMS -  2+1(physical appliance) cluster with cms3 being associated with TMS
TMS - For creating meetings
CMM - For managing meetings

System is up and running and the usual workflow to create a VTC is the following:
User/admin creates a conference in TMS
1. User adds two main participants:
  -External participant - Used for remote web access
  -Master Conference Unit - cms03
2. User adds optional participants, e.g., remote sites on-prem VTC systems

For most of the time this works, sometimes remote VTC system fail to accept the first call to join the VTC, but it is because they are disconnected. Calling the assigned VTC number solves it.

The issue I bring here today, happens occasionally, with the following behavior:
Meeting created with three participantes, external one, MCU, Site-X Polycom HDX

When the time comes this is the event log:
1/30/2024 5:27:05 PM user1 Conference: Created
1/30/2024 5:27:05 PM user1 Instance: Created, start time 01/31/2024 08:30:00 +00:00
1/31/2024 8:15:04 AM network service network service Instance: Registered
1/31/2024 8:25:00 AM network service network service Instance: Display 4 minute message
1/31/2024 8:29:00 AM network service network service Instance: Display 1 minute message
1/31/2024 8:30:00 AM network service network service Instance: Started
1/31/2024 8:30:06 AM network service network service SITE-X Polycom HDX Instance: Meeting allocated on port: 1
1/31/2024 8:30:06 AM network service network service mcu-cms3 Instance: Allocation failed: Allocation of the CoSpace failed in CMS, Meeting cannot be allocated.
1/31/2024 8:30:06 AM network service network service mcu-cms3 Instance: Allocate failed, conference is not automatically connected
1/31/2024 8:30:06 AM network service network service mcu-cms3 Instance: Attempting automatic MCU failover. New conference main participant will be SITE-X Polycom HDX.
1/31/2024 8:30:06 AM network service network service Conference: Updated
1/31/2024 8:30:06 AM network service network service Conference: Participant removed: mcu-cms3
1/31/2024 8:30:06 AM network service network service mcu-cms3 Instance: SIP Dial => 480017@domain.local
1/31/2024 8:30:06 AM network service network service Instance: Updated
1/31/2024 8:30:11 AM network service network service Instance: Non-secure conference. Original value of the setting was 'if possible' and not all participants support encryption.
1/31/2024 8:30:11 AM network service network service SITE-X Polycom HDX Instance: Meeting allocated on port: 1
1/31/2024 8:30:11 AM network service network service Instance: Main system changed from mcu-cms3 to SITE-X Polycom HDX

Following this it seems the remote HDX becomes the MCU, and cms-03 leaves. After this joining the meeting is not posible.

I then recreated the same meeting without the HDX Polycom. After meeting started with sucess I add the HDX Polycom through CMM and everythings goes smoothly.

So my question, why is this happening sometimes. Can it be that when creating the meeting the posibility of a external VTC system being added as a particiant before the cms-mcu results in the meeting being allocated to that external system first, breaking the processing?

Best regards

0 Replies 0