Upgrade V18 to V20

[Alle CTEC]

https://www.3cx.com/blog/releases/v20-upgrade-checklist-faq/

I refer to the checklist in question. It does not mention the configuration of the phones. I configure the split DNS and it works fine for me but the phone previously pointed to an IP address and not an FQDN. Have I checked that the control panels that have already updated to 9 build 31 still have phones pointing to the control panel with an IP address? They then automatically switch to fqdn via provisioning. Should the firmware be updated to the latest release before updating? Example Legacy applications stop working? If I have voicegateways configured with an IP address and not an FQDN, do they need to be reconfigured? DECT systems? will they work without problems? Are there any limitations on updates to be made?

The firewall part must be modified so that 5001 automatically migrates to 443

Thank you in advance

 

[SteveITS]

The 3CX web server port only changes if you reinstall 3CX and choose a different port...it does not change by just having 3CX upgrade itself.

"The firmware" being phone firmware? I usually upgrade phone firmware after a 3CX upgrade, but the one I've upgraded so far did not have any phone firmware updates to install.

The requirement to use the FQDN is to use HTTPS with a valid certificate, on the phones, web client, etc. I don't know about other hardware.

 

[Alle CTEC]

ok but do the phones that currently point to an IP automatically switch to FQDN?

Is it okay to switch phones to fqdn before updating? Does the update migrate them?

Is there nothing you need to do for DECT extensions?

Personally I noticed that when generating the template of a patton fxs the template pointed to an fqdn and not an ip address.

Example Legacy applications continue to work? Desktop Apps?
To use the CTI mode, I think only the PWA is available, right?

 

[SteveITS]

All our clients we have set up are all self-hosted so were using it all along. So I do not know of the change process, just that it is required. So I would think/hope so. AFAIK using the LAN IP was to allow a direct HTTP connection, and 3CX wants to use HTTPS now. So I would expect the FQDN to work as long as split DNS or NAT reflection is working. Might be safer to change them before the upgrade?

re: applications, they should use the FQDN. The Desktop App will work in v20 if it was set up (or if you figure out how to install and configure it) but may stop at some point. The new Store app will control phones: https://www.3cx.com/blog/press-releases/softphone-beta-csta/.

 

[Alle CTEC]

We didn't understand each other. Do Snom Fanvil Yealink phones that point to an IP address such as 192.168.1.x switch by themselves to points such as 3cxpbx.my3cx.it?

For the application I read in the app store it is a sip client that does not support CTI mode that only works with the pwa.

Anyway, what about this lack of certainty, could it get blocked? I thought I understood that everything had to switch to fqdn but the provisioning of phones and devices is not mentioned.

I ask you one last question if I reinstall the control panel changing the port from 5001 to 443 do I have to reconfigure all the pwa?

Thanks

 

[bitn2]

We didn't understand each other. Do Snom Fanvil Yealink phones that point to an IP address such as 192.168.1.x switch by themselves to points such as 3cxpbx.my3cx.it?

Yes, they will pull the new config.

 

[Alle CTEC]

Ok thank you very much, regarding the dect phones instead, are there no changes to be made?

The pwa applications instead for example if I used port 5001 and I take advantage of it to recreate the exchange on 443 from 0 by importing the backup, do the pwa need to be reinstalled?

Thank you very much

 

[SweetAction]

Ok thank you very much, regarding the dect phones instead, are there no changes to be made?

The pwa applications instead for example if I used port 5001 and I take advantage of it to recreate the exchange on 443 from 0 by importing the backup, do the pwa need to be reinstalled?

Thank you very much

The PWA will need to be reinstalled if you change the FQDN or Port.

 

[SteveITS]

Also AFAIK the phones can't update their config if the server port changes.

 

[Alle CTEC]

I updated to V20, first I checked that the phones were already pointing to fqdn and not IP address. I followed the check list, then I configured the call destinations and working hours by setting them from the group in the admin panel /weblcient/ I updated to V20, the only device I had to reconfigure was the Patton voice gateway which was working but uneditable.

Good