I'm having a bit of problems building a 3 server (v 2.9) CMS callbridge cluster.
The DB cluster running in same three severs looks all good with all nodes In Sync.
I have configured the Callbridges following the Resilient Deployment Guide 2.2.
After adding all three servers in the Web page, I can see they all connected in the master server, however the other two only show "connection attempted" for the other two servers.
I've checked all certificates and restarted the Callbridge service and the servers themselves to no avail. I have also tried to use FQDN and IP address to point to the servers in the Clustered Callbridges section. No errors in the CMS logs.
Any clues as to what could be causing this problem?
Need to check the syslog, see my earlier reply, the event log in the web interface doesn't contain enough info for troubleshooting, but the syslog contains details about what's going on with CMS.
Shouldn't the port be for the webadmin rather than the MMP? That's what I've got on my working clustered deployment (https://<CMS-FQDN>:445)
I have the same problem, but I am seeing something strange:
I enter via web the firts cms> cluster, the result is connection attempted on the remote servers.
I enter via web the second and third CMS, the cluster page result is connection active in all The CMS.
Please help me
Is it possible to snapshot the cluster page here so we can see what you have configured? If you don't see a heartbeat or [this Call Bridge] on the page, it *might* be that the names are different. So under callbridge Identity, make sure that name and the unique name under Clustered Call Bridges are the exact same. Make sure no whitespaces etc to. Make sure its the same on all pages for each callbridge in the cluster. Seeing the page would be of help to if you can provide it.