I am having the problem described in this forum post. As the post explains, this can be resolved by either using HTTPS or by using the external webmeeting link.
Unfortunately, HTTPS is already being used and it is still not working. I have confirmed that the external Webmeeting link works, but it isn't very convenient to have users start the webmeeting from their extension in the default client and then have to join with the external link in another tab/window. Obviously with workarounds this is possible but I was wondering if anyone ran into this problem who was also using HTTPS already and what can be done to resolve this.
Per the link in the forum post, I've tested amending the target for the Google Chrome shortcut as suggested but did not have any success. The webclient URL is a custom one with a certificate from GoDaddy, but it seems that something about the FQDN with regards to HTTPS is not working properly. Has anyone else run into this problem? Thank you.
Unfortunately, HTTPS is already being used and it is still not working. I have confirmed that the external Webmeeting link works, but it isn't very convenient to have users start the webmeeting from their extension in the default client and then have to join with the external link in another tab/window. Obviously with workarounds this is possible but I was wondering if anyone ran into this problem who was also using HTTPS already and what can be done to resolve this.
Per the link in the forum post, I've tested amending the target for the Google Chrome shortcut as suggested but did not have any success. The webclient URL is a custom one with a certificate from GoDaddy, but it seems that something about the FQDN with regards to HTTPS is not working properly. Has anyone else run into this problem? Thank you.
