Windows Upgrade from v18 to v20 - Web ports changed from 5001 to 443 on restore

[randybell]

I did a v18 to v20 upgrade on an on-premise PBX a couple nights ago.

The web ports changed from 5001 to 443 on restore. I didn't intend this to happen, but am fine with this.

I am told that this is not even possible when doing a restore. Did I miss something? I would prefer to start migrating 5001 over to 443 with other on-prem winPBX installs.

 

[SteveITS]

443 is the default during an install but can be changed in the .xml file before uploading it.

So if one just uninstalls + installs, the port will change. Phones, etc. need to be reconnected though.

 

[randybell]

right, but I am doing install restoring from backup. I didn't manually change anything, wondering now when I go to do the same on other v20 install using restores how that port can be changed.

 

[SteveITS]

It’s tied to the install, and not part of the backup. Hence not part of the restore.

 

[TheodorosG_3CX]

The https port is not included in the backup as you always have the option to use the default 443 or another port upon installation.
You need to always check the steps in the installation before confirming.

 

[randybell]

related to this re-install on self hosted installs. The provision links are not updating on most phones. First I noticed on SnomD715/D735 but the same issue with Yealink T46s/48s/52s

Any suggestions on resolving this on bulk? So far I have to either log into the phones directly and update the provision link manually or factory reset (as long as they can grab RPS access, they will reprovision). It's about 100 phones in 5 offices

 

[Guillaume Bourgeois]

If you manage the router in front of the 3CX, set up Port Forwarding to redirect traffic intended for TCP port 5001 to TCP port 443.

Reprovision your phones, remove Port Forwarding.

 

[randybell]

If you manage the router in front of the 3CX, set up Port Forwarding to redirect traffic intended for TCP port 5001 to TCP port 443.

Reprovision your phones, remove Port Forwarding.

Excellent suggestion and will work for some of the phones on remote locations, but not for the bulk of them on the LAN that still point to the IP address not dns

 

[Guillaume Bourgeois]

The good news is that the phones are still functional (They can make and receive calls) and you'll have plenty of time to go through each one to make modifications. I did 200 the other day; it took me about 30 minutes of focused work. It's not very time-consuming.

Your main challenge is with remote phones, those that you cannot connect to because they are not on your local network.

 

[randybell]

The good news is that the phones are still functional (They can make and receive calls) and you'll have plenty of time to go through each one to make modifications. I did 200 the other day; it took me about 30 minutes of focused work. It's not very time-consuming.

Your main challenge is with remote phones, those that you cannot connect to because they are not on your local network.

Remote phones are find since they are pointing at DNS so at the firewall. a redirect does the job

What I have done on my local LAN phones (the bulk of them) was do a redirect on the on-premises 3cx PBX, In my case Windows system

the connectadress being my 3cx PBX LAN IP

netsh interface portproxy add v4tov4 listenaddress=0.0.0.0 listenport=5000 connectaddress=mylocalpbxIP connectport=80

This has done the trick. So far so good, one site seems to havell all deskphones communicating with the 3cx PBX local and updating the provisioning URL.

 

[Guillaume Bourgeois]

Remote phones are find since they are pointing at DNS so at the firewall a redirect does the job

What I have done on my local LAN phones (the bulk of them) was do a redirect on the on-premises 3cx PBX, In my case Windows

connectadress being my l3cx PBX LAN IP

netsh interface portproxy add v4tov4 listenaddress=0.0.0.0 listenport=5000 connectaddress=mylocalpbxIP connectport=80

This has done the trick. So far so good, one site seems to havell all deskphones communicating with the 3cx PBX local and updating the provisioning URL.

That's a good idea; I hadn't thought of that ! You're not crazy, not at all !
Don't forget to remove it when you're done to avoid leaving active rules.

I'm adding this to my "tricks" basket. I hope you won't charge me $$ too much for this.