Clarification on upgrade to v20

[TheRambler]

Hi,

Apologies if this has been asked before, I've been searching but all I can find is either posts where people say the upgrade went smoothly aside from some small issues (Not related to softphones) or after the upgrade softphones couldn't connect but was due to them not having 443 opened on the firewall.

We have 443 opened on the firewall. I've done 2 upgrades so far and both instances the softphones (at least Windows (v20 MS Store version) and Android) can connect to the new v20 instance so far as they can make and receive calls but the extension status is grey and none of the tabs (Team, Contacts, Recents ect) load. If the apps are re-provisioned via the webclient they then connect no problem.

It seems related to the port change (5001/5000 > 443/80) because if I re-install the v20 server using the old ports (5001 & 5000), with no other changes, then both apps reconnect no problem.
Given the default ports pre v20 was 5000 and 5001 and in v20 are 443 and 80 I thought I'd see more reports about this or something in the FAQs for the v20 upgrade so being unable to find anything I can't help think I'm missing something? Or is everyone just installing v20 using the old http/s ports or suffering reprovisioning everyone's app?

Thank you

 

[NicholasP_3CX]

When you perform the upgrade to 3CX Version 20, you can keep the same ports.

Restoring from a backup, you will be asked which ports to use during the installation process.

When deploying a new system, you can open the setup config file and change the ports back to 5000 and 5001 if you wish.

 

[TheRambler]

Thanks Nicholas! So it is expected behaviour then that when migrating from a v18 system using the default ports 5001/5000 to a v20 system using default ports 443/80 that the apps will need to be reprovisioned?

It would be our preference to keep things default as much as possible to make things easier for support so if this is the case then we'll need to decide if we'd rather have a mix of 5001/5000 and 443/80 systems or would we rather take on the added labour of re-provisioning everyone's app (which would also involve resetting almost everyone's password cause what customers ever know their 3CX passsword? )

 

[NicholasP_3CX]

So it is expected behaviour then that when migrating from a v18 system using the default ports 5001/5000 to a v20 system using default ports 443/80 that the apps will need to be reprovisioned?

Of course it is expected. It is a different port at the end of the day. Try logging in to your bamking application and put port 5001 at the end. Its not gonna connect, no matter what you do.

This is expected as the devices are expecting their information on port 5001 but now 5001 isnt active so the devices just sit there doing bugger all.

It would be our preference to keep things default as much as possible to make things easier for support so if this is the case then we'll need to decide if we'd rather have a mix of 5001/5000 and 443/80 systems or would we rather take on the added labour of re-provisioning everyone's app

This is entirely up to you. There is nothing wrong with port 5001. However it has been noticed that some public networks (airports, hotels, exhibition centres) may be blocking non standard HTTPS ports, so if someone tries to connect to their PBX they would not be able to.

(which would also involve resetting almost everyone's password cause what customers ever know their 3CX passsword? )

No need, as long as they have access to the web client, (they may need to just modify their bookmarks on the web client) they can reset their own password, without the admin needing to intervene.



IP Phones on the other hand will need to be reprovisioned to the new provisioning URL. Option 66 might be your friend here.

 

[TheRambler]

I get it's a different port of course, but my bank isn't deciding it's changing the default port moving forward. If it did, I'm sure they would add a redirect on the old port or they'd get inundated with calls "I can't access my banking". I thought maybe something would have been implemented in v20 to still listen on the old ports and auto redirect/reprovision to the new ports.

Anyways I've discovered if I add the following to 3CX's nginx.conf file the apps reconnect
listen 5000;
listen [::]:5000;
listen 5001 ssl http2;
listen [::]:5001 ssl http2;

After the apps have been connected for just a couple of minutes I can then remove this addition and they remain connected, even after rebooting the devices and 3CX server so to ensure it's not just on some cached/established connection. This will save us a lot of time.

Probably not supported I appreciate, please don't give me the big stick