moved 3cx to cloud vm, sip phones won't stay registered?

[stechtn]

I've googled and keep finding info not quite related.

We have a grandstream dect. It worked perfect when the server was inside our firewall. Now that it's outside, we have to restart the dect every morning to get calls on it.

3cx apps on our phones have even had this issue. I'm forgetting something about firewall rules or something. I do see the firewall blocking some uninitiated packets coming from the phone system.. so i set an allow all rule for the IP of the phone system coming in on wan. That didn't solve the problem, just stopped it from getting logged in the firewall logs as blocked.

outside our network, using cellular data everything works fine for 3cx App softphones. So it's our firewall.

What could I be overlooking? Firewall is a derivative of PFSense. Yes, the firewall check on the server passed. Or is there a setting on the grandstream i need to set so it stays registered? I didn't see any keep alive settings.

3cx 16.0.9

 

[Alphabetic]

Hi - First things first: https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

Is the old location off completely?

have you got manual DNS set up?

 

[SteveITS]

Did you set up an SBC? Or are you using STUN? Either way there's probably some setup involved to configure local phones...

 

[stechtn]

Hi - First things first: https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

Is the old location off completely?

have you got manual DNS set up?

Old location is off.
Yes it's manual DNS.

 

[stechtn]

Did you set up an SBC? Or are you using STUN? Either way there's probably some setup involved to configure local phones...

STUN.

I made a change to the local IP phone to use STUN. Hopefully it's a permanent fix. Oddly one of our android phones with the 3cx app also has the issue, app has to be opened when on site to receive calls. Another extension, on a different phone, doesn't have the issue at all.

 

[ChrisC_3CX]

Since you moved this 3CX Instance to the cloud, all Deskphones should be configured as remote devices meaning that you should either use the 3CX SBC provisioning method or STUN. Local provisioning method is out of the question unless of course you have a site-to-site VPN implemented. I highly recommend recommend using the 3CX SBC as opposed to STUN, either way, do make sure to factory reset the phone before switching the provisioning method and then follow the corresponding guide to reprovision: https://www.3cx.com/sip-phones/

If you really must use STUN do have a look at the our STUN guide for information on how to properly configure the Deskphones in order to ensure normal functionality.

Regarding the android device, try completely uninstalling the app, re-install and then create a new test extension to provision to it. Check if the issue persists. If it does, it may very well have something to do with the device since you have other android devices that work fine in the same exact environment.