CMS 3.3 Scheduler to CallBridge C2W status down

[Meddane]

I configured correctly the scheduler with the appropriate certificates, but the scheduler status shows that the C2W connection to CallBridge is down, even if the C2W connection between the webbridge3 and CallBridge is Success.

I think the new component scheduler is still in beta feature?

[b.winter]

Hi,

do you see any errors in the logs?

E.g. when you do "syslog follow" on CLI?

[Meddane]

Yes, see below the syslog follow capture:

[b.winter]

In which format did you add the webbridge via the API?

It should be in the format "c2w://<fqdn | IP>:<Port>"

Are the FQDN's / IP, that we see in the logs in the certificate of the webbridge?

[b.winter]

For the FQDN's "join.lab.public", "meet.lab.public" and "join.lab.local" it looks like, they were added in the wrong format:

"https://<fqdn>",  instead of the format mentioned before "c2w://<fqdn>:<port>"

For the FQDN "hq-cms.lab.local" it could be a certificate problem: from the output "SSL problem"

Maybe you could turn on the "Webbridge connection tracing" in the GUI and get some more specific messages from there.