CMS 2.3 node participantlimit

Mamdouh Elgamal — Mon, 18 Mar 2019 21:09:29 GMT

Hello,

I'm trying to understand Call bridge behavior when participant limit is reached.

given a call bridge group with 3 nodes, cb1,cb2,cb3 (all in the same cluster)

suppose i create a meeting in TMS and assign CMS resource + video endpoints. Meetings settings are set to have the bridge dial-in the endpoints

TMS reaches out to CB1 to create the meeting, but CB1's participantLimit has reached the max (i'm referring to participantLimit set @ /system/cluster object)

I'm seeing that cb1, just rejects the call:

add participant "xxxxx@zyx.com" request failed: call bridge unavailable

API provider: call control participant create failed (21)

shouldn't cb1 forward the call internally to cb2 ?

what is the expected behavior ?

The interesting thing, if i changed the meeting connection settings in TMS to have the device call the bridge number. The call connects on cb2, no issues.

EDIT:

i suppose this document answers my question..

https://www.cisco.com/c/en/us/support/docs/conferencing/meeting-server/212298-cisco-meeting-server-acano-tms-integ.html#anc9

but i't seems i need to route the call through CUCM if participant limit is reached on primary server.

topic CMS 2.3 node participantlimit in TelePresence and Video Infrastructure

CMS 2.3 node participantlimit