09-16-2021 03:41 PM
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?
09-20-2021 11:50 PM
Hi,
do you see any errors in the logs?
E.g. when you do "syslog follow" on CLI?
09-21-2021 03:35 AM
Yes, see below the syslog follow capture:
09-21-2021 04:30 AM - edited 09-21-2021 04:31 AM
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?
09-21-2021 04:58 AM
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.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide