Webmeeting FQDN incorrect

[Andy Walsh]

After upgrading to v15 SP4, I went through the usual set up, choose a FQDN and that is all fine. The 3CX license key is correctly bound to that FQDN and the 3CX Mng portal works and on the dashboard specifies the correct FQDN.

The problem is the webmeeting FQDN is different for some reason and I can't work out how to change it. As I say the main FQDN is correct and working.

Does anyone know how to change the WebMeeting FQDN.

Any help much appreciated.

 

[YiannisH_3CX]

The webmeeting FQDN is auto created and it's based on the FQDN you used to install the system. Therefore you cannot change the webmeeting FQDN without changing the FQDN you used to install the PBX

https://www.3cx.com/docs/fqdn-management-allocation/

 

[Andy Walsh]

Hi YiannisH,

Thanks for your reply. The FQDN during the install is correct but the webmeeting FQDN is a different domain. I have no idea how the main FQDN is different from the WebMeeting FQDN. I can send over a screenshot but I didn't want to post it on a public forum.

Thanks

Andy

 

[YiannisH_3CX]

Send me a private with the screenshot so i can tale a look.

Thanks

 

[North Cascade Group]

Did you ever get this fixed? I have the same problem I think.

We have our own domain and certificate which is pbx.mydomain.net, which shows up correctly as the FQDN on the dashboard, however, in the licensing portal, and on the dashboard under "webmeeting FQDN" it shows as pbx-mydomain-net.3cx.net

I can access the admin console just fine from pbx.mydomain.net, but the webmeeting stuff still redirects to the longer FQDN with the .3cx.net extension on it. Is that correct? Shouldn't my entire system (Admin console, Webmeeting) point to the same FQDN?

 

[YiannisH_3CX]

Hello @North Cascade Group

Please note that when creating a PBX a separate FQDN is formed for webmeeting. Please read through the following article that explains how the FQDNs are reformatted for webmeeting
https://www.3cx.com/docs/fqdn-management-allocation/