Solved PUSH and call in mobile app does not work after clean installation of 3CX V20

[Oleksii]

Hello!

We have a 3CX in our cloud with own FQDN and 5000 5001 ports for connectivity.
It was PBX version 18 that we upgraded to version 20.

Now it was necessary to change the FQDN and we need keep http and https ports 5000 5001.

I tried different methods of reinstalling with restoring from a backup of settings.

Today I gave up, and installed version 20 from the beginning.

Here are 2 problems:

During the installation v20, i cannot change http and https port.
For us, this is critical, the way standard ports are occupied by other services.

To specify the ports, I did the following:

1. Install clean v20 from Debian iso image
2. Specify the configuration file that generated 3CX Portal.
3. Specify the certificate file for the my FQDN
4. Backed up this configuration
5. Recreated the virtual machine and restored the PBX from the backup created in step 4.

Then I set up internal phones, trunks and IVR.

But, unfortunately, PUSH notifications on mobile phones did not work.

I read that you need to contact technical support to link the serial number to the new FQDN

Perhaps I did something in the wrong sequence?
How to fix PUSH on mobile phones after clean installation?

If I open the application on my phone and try to dial this number, then the call also does not come.

 

[bitn2]

In the configuration file you can change the ports... After the installation just restore your backup. The push doesnt work becaus your phone still use the port 5001 and not 443 as you installed your pbx.

 

[Oleksii]

In the configuration file you can change the ports... After the installation just restore your backup. The push doesnt work becaus your phone still use the port 5001 and not 443 as you installed your pbx.

Thank you!
I didn't think to fix the configuration file and changed the ports using the restore procedure.

I think the problem was my attempts to change the FQDN for this PBX.
I have already changed it once in the backup file to change the FQDN. And I also didn't have PUSH working on the new FQDN.

At the same time, there was a new one on the portal and I unloaded the configuration without resetting the FQDN value.

I think that the PBX does the setup/registration of PUSH at the beginning when the configuration is empty.

In this case, I did according to the instructions: unlinked the FQDN on the portal. Then I made a configuration file, specifying the new FQDN on the portal.
After that, I set up the forward and reverse zones for the new domain name on the internal DNS server (Hairpin NAT did not help)
I re-installed the PBX (when setting up IP parameters, 3CX found a new domain name in the reverse zone).
Well, I performed all the other settings.
Now everything works.