Solved Update to v16 from v15.5 now FQDN on iOS app and Android doesn't work

[lloydrose]

On the weekend I upgraded from v15.5 to v16 on a fresh Server 2016 install running in a VM. I gave the server the same name on the domain as the old one which was renamed, same IP's as the old VM also and it has 3 network cards. 1 for Data, 1 for internal phones and 1 for SIP. Installed 3cx v16 and imported from backup. We have a public class C IP space so all of our servers can have public facing IP addresses however I prefer if we can get the FQDN name working for the external PBX ip on the mobile app. When we add it in, the phone registers however we get no voice in either direction to another phone number. But when we change it to the local IP of the PBX it works. Any suggestions? I would have thought this would have been a smoother install since we kept everything the same and did a restore from backup.

Any help would be appreciated.

Lloyd

 

[AWS2P]

do you use tunnel 5090 Port? is it open on firewall?

is the firewall checker passes green ?

If you dial *777 echo voice test, do you hear you back ?

 

[lloydrose]

When I have the FQDN in as the external PBX the echo test does not work on LTE. With the IP address in there it does.

 

[NickD_3CX]

When I have the FQDN in as the external PBX the echo test does not work on LTE. With the IP address in there it does.

This may be a silly question, but just in case. When you turned on LTE, did you make sure WiFi is turned off.
I have a suspicion that over WiFi this will not work because the firewall may be dropping loop-back traffic.

Another idea, in my opinion a very good one generally, to create a split DNS setup, so whoever connects via the internal network, the internal DNS Servers will return the corresponding Internal IP, whereas all Public DNS Servers will return the Public IP.

One last question, in the Extension Settings --> Phone Provisioning tab, with the "3CX App" selected in the drop-down, what Network Interface have you selected, the Public IP, the FQDN, or one of the other 2 Private IPs of the other 2 NICs?

 

[lloydrose]

Wifi was turned off and just LTE tested. We have our own external DNS which points to the PBX IP. Both internal and external can be the same. Our internal phones are on a separtate VLAN which talks to the PBX on another network. We have 0 issues internally. Also internally on our WiFi the FQDN works on the 3CX app. Its only when your out of the office that the FQDN does not work and we have to use the IP of the PBX. When I go to the drop-down the network interface I have selected is the IP and not the FQDN.

 

[NickD_3CX]

When I go to the drop-down the network interface I have selected is the IP and not the FQDN.

Could you try switching this to the FQDN? Once you do launch the App and go to Settings --> Accounts, then Manage Account (on the account in question). Once you do this could you share what is in the "Local PBX" and "External PBX" fields?
also try to make a call over LTE again and see what behaviour you see.

 

[lloydrose]

I changed it on my extension to the FQDN. I went back in the app and it didn't change but I suspect I would have to re-provision it? I am using an iPhone so I can manually change the internal and external to whatever I want. Android does not have the option for this however. When I changed it to the FQDN on my extension and changed it on my phone, I still get no voice on the *777 and the key presses also give nothing.

 

[NickD_3CX]

I changed it on my extension to the FQDN. I went back in the app and it didn't change but I suspect I would have to re-provision it? I am using an iPhone so I can manually change the internal and external to whatever I want. Android does not have the option for this however. When I changed it to the FQDN on my extension and changed it on my phone, I still get no voice on the *777 and the key presses also give nothing.

Yes, my bad, you would need to reprovision it for the changes to occur
If you want, create a new extension on your system, disable external calls, etc, send a Welcome Email to yourself to get the Config File and then send that to me.
I can't think of something, but I could try remotely from my location and maybe come up with some other idea what this is happening.

 

[lloydrose]

Hi Nick,

This did fix the issue after I properly reprovisioned the phone. Thanks!