3CX change of Port Numbers in v12.5

[maharshi_raval]

Hi,
After the announcement at http://www.3cx.com/blog/docs/new-port-numbers/ going forward with version 12.5 3CX will use ports 80 and 443 for certain features and not 5000 and 5001. Can someone give me a clear idea on if it will affect any functionality on the 3CX Phone apps for Android and IPhone that are being used in Tunnel Mode from outside the LAN. ? #

Any help is much appreciated. Thanks in Advance for you time.

Kind Regards,
M Raval

 

[tsukraw]

They changed the official release of 12.5
During the install you have the option to stick with 5000/5001 or change it to 80/443

If you chance it to 80/443 you will need to update your provisioning URL in DHCP if you are using option 66 for internal stuff.

From outside you will need to adjust your firewall to allow the connection through to 3CX and you might have to send out a new welcome email for the client to update to the new ports.

I've installed v12.5 a couple times now and been running the RC and beta builds. I personally don't see a reason to change ports and on all but 1 install kept it 5000/5001 just to make life easier.

Reading your question i see i didnt fully answer it. I havent seen any negitive effects in keeping 5000/5001 all the functionality seems to work just fine.

 

[jesnofear]

I am glad to see the ports changing to standard ports. One question I have though, can the auto provisioning URL's be changed from http to https. Given that the provisioning can occur over the WAN, sending raw text over any port is a bad idea, especially since it contains a extension and password, it makes it easier to hijack your voip system.

 

[ian.watts]

I was at least able to form the URL for my own extension's provisioning file in my web browser remotely.. and added the https:// instead.. still comes up.
So.. it does at least provide the file via HTTPS. Getting the option to use HTTPS would seem to make sense here, yes.
Sadly, my template uses the vars which result in all the entries being HTTP at present.. and I'd rather not go manual on my templates to make it HTTPS-ready.

That being said, I don't personally tend to provision outside the LAN in general.. but it can certainly be a convenience for the mobile devices and perhaps the occasional remote worker/office.