Solved Web Meetings Create with Local IP, Instead Of FQDN - 3CX V18 App

[Jim.Lloyd]

I recently switched from the client browser extension to the Windows App for the v18 client. I quickly found that the presenter/host URL creates with the internal IP address, instead of the external (FQDN) address. The internal URL is invalid for joining a meeting. If I am on an external IP address, I connect with the FQDN and get a URL with the FQDN. The web browser doesn't do this, and consistently creates the external URL.

Is there a setting I can modify? I tried removing and re-adding the App, but I didn't manually clear any saved setting files and ended up with the same thing. If I mess with 'config.json' I am not sure if I will just break the 3CX App (i.e. - modify "PBXLocalAddr" to match "PBXPublicAddr"). But, why wouldn't the 3CX App know to do this?

I appreciate any assistance with this. Thanks, in advance!

 

[VasilisV_3CX]

Hi @Jim.Lloyd,

EDIT: There are two ways to connect to the PBX. You can connect via the Internal IP or the FQDN. Which ever way you connect (say for instance via the local IP), is the way the WebMeeting invite will display. If you log in with the FQDN, it will display the joining link as the FQDN/joininglink.

 

[Jim.Lloyd]

that is what I am asking... How do I get the App to log in with the FQDN when I am on the internal network? It dynamically goes to the local IP when I am on the internal network, but switches to the FQDN if I am on an external network. Hence, my question about editing the .json file... which seems 'messy'.

 

[VasilisV_3CX]

Hi @Jim.Lloyd,

The correct way to handle this would be by ensuring you have Split DNS working on your network.

However you can edit the Extension >> Phone Provisioning >> 3CX App >> Set it as the FQDN instead of IP.

 

[Jim.Lloyd]

Thank you, VasilisV! That is what I was missing, and my issue is resolved >)

I don't have physical phones in this configuration... all soft phones & the app. So, "Extension >> Phone Provisioning >> 3CX App >> Set it as the FQDN instead of IP" worked for me.

 

[VasilisV_3CX]

Great to hear this resolved the issue for you @Jim.Lloyd! Feel free to open a new thread if you require any further assistance or information.