3CX Phone System v12.5 Beta – Important Change – New Port Numbers

With the release of 3CX Phone System v12.5 Beta, changes have been made to the port numbers making the deployment of 3CX Phone System much simpler. For a correct operation of 3CX Phone System, administrators should forward the correct new port numbers and make the following changes:

HTTP and HTTPS Port Changes

The ports previously used for HTTP and HTTPS were port 5000 for HTTP and port 5001 for HTTPS. This change affects Phone Provisioning URLs, access to all websites (Management Console and Reporter), and Presence in 3CX Bridges. The new ports are:

  • Port 5000 becomes port 80 for HTTP.
  • Port 5001 becomes port 443 for HTTPS.

The Phone Provisioning URLs need to be updated by simply removing port 5000 from the URL. For example:

  • The provisioning link in V12: http://example.3cx.com:5000/provisioning/{randomfoldername}

Becomes:

  • The provisioning link in V12.5: http://example.3cx.com/provisioning/{randomfoldername}

Since the Provisioning link has been modified, 3CXPhone Clients need to be re-provisioned otherwise they will not be able to connect to 3CX Web Presence Servers. To avoid these issues, access the 3CX Management console, click the Extensions node, select all the extensions in the list and click “Send Welcome Email” button.

3CX Bridge Presence URL

From the management console:

  1. Expand the “Bridges” node.
  2. Click on each bridge which has 3CX Presence enabled and navigate to the “3CX Presence” tab.
  3. In the “Receive Presence Information” sectionremove port :5000 or :5001 from the URL.

For example:

  • http://example.3cx.com:5000/MyPhone/MPWebService.asmx

Becomes

  • http://example.3cx.com/MyPhone/MPWebService.asmx

Media Server Ports

The port ranges for Media (voice and video) have changed. Administrators need to edit their firewall rules and forward the following range of ports: 9000-9199 UDP Only (Total of 200 ports) .
Ports 9000-9099 will be used to transmit media for SIP VoIP Calls, whilst ports 9100-9199 are used to transmit media for WebRTC VoIP Calls.

HTTPS Certificates

From Version 12.5 and higher, any certificates generated at installation time can be backed up and restored using the 3CX Backup and Restore tool. This way administrators can ensure that client certificates remain the same.

x86 Installations

3CX Phone System can only be installed on x64 based Windows Operating Systems. Support for x86 has dropped.

Winforms Removed

The 3CX Winforms Management Console has been removed from the 3CX Phone System installation. This is deprecated. 3CX Management Console is Web Based only from now on.

Liked this article?


Get notified of new articles
or share
You might also be interested in:
  1. Installing 3CX V12.5 on Win 7 Pro conflicts with IIS on port 80 & 443.
    3CX installation package insists on installing Abyss and ends prematurely.

    October 21, 2014 at 10:41 am
    • Andreas Christodoulou

      Hi Orlin

      Operating systems like Windows 7 and 8 , only Abyss can be used as a Web Server.The restriction is configured because IIS versions installed on workstation operating systems can only serve up to 10 simultaneous HTTP Request

      October 21, 2014 at 12:40 pm
    • Orlin Shopov

      Hi Andreas,

      the question was how to cope with IIS, if already installed on Win 7/8 ?
      The cons about IIS are not the focus.

      Regards

      October 21, 2014 at 2:51 pm
  2. Paul Sayers

    Does this now means if the client is using port 443 for another service .i.e Exchange OWA, they require two static wan IP’s now.

    This means extra costs for our clients if this is the case, why the change and can we overwrite the port numbers.

    October 21, 2014 at 1:44 pm
    • @Paul – We have blocked the installation of 3CX Phone System if Exchange is present. Exchange is too integrated with Windows and IIS. You need to have either one or the other on separate machines. It is absolutely acceptable to have Exchange on a dedicated machine…

      October 21, 2014 at 4:26 pm
    • Stan Guinn

      Nicky, you reply doesn’t really answer the question. If the customer’s site has Exchange on a different server, the router can only route 443 to one server and it would need to be Exchange. So how does 3CX get access to port 443 if it is already being routed somewhere else? Or can the 443 requirement be changed somewhere in the 3CX settings?

      October 21, 2014 at 5:32 pm
    • @ Stan – Yes you can simply go in the IIS and change the binding to a different port.. Then go in registry and add the port there.

      October 21, 2014 at 7:02 pm
    • Paul Sayers

      I think you are missing my point,

      If you have incoming traffic internet traffic on port 443 on one wan IP address, already which is going to the exchange server for owa for example.

      With your changes, you can not have external traffic for 443 going to two different internal IP address unless your have two external IP addresses.

      I know that the costs are around 5 per month extra, but it will also involve setup changes to the internal hardware which the client has to pay

      Can you change the ports for 80 and 443.

      October 21, 2014 at 5:44 pm
    • @Paul Sayers – for now evaluate the BETA as it is because this part is not yet finished. The port can be changed and we can make a guide on the changes that need to be made for IIS and Abyss..

      October 21, 2014 at 7:47 pm
    • Stan Guinn

      I cannot just install it and test it. My port 80 is already committed to a web server and my port 443 is already committed to my Exchange server.

      October 22, 2014 at 12:31 am
    • @Stan – Then do not use this build. We understand that 80 and 443 are used for other services. We are working so that the final build will have these HTTP and HTTPS ports configurable to your wishes..

      October 22, 2014 at 10:15 am
  3. Tucker Sukraw

    Am i missing something? I dont seem to find a download link?

    October 21, 2014 at 3:55 pm
  4. Cloud Server 12.0 doesn’t require port 5000 or 5001. I assume this change only applies to the stand-alone version. Are there any other port changes that would effect Cloud Server?

    October 21, 2014 at 4:34 pm
  5. Barry

    I have to agree with Paul here. Haven’t 3CX on standard web ports makes installation more difficult, not less.

    October 21, 2014 at 6:47 pm
    • @Barry – I think it makes 3CX installation much easier… Why not put exchange on a different port – You will immediately see how difficult that gets…
      Not having your users to remember the port 5000 or in the Webrtc links etc, is much easier.

      October 21, 2014 at 7:04 pm
    • I have to completely disagree with you and 3cx on this. If I have 25 users accessing a website or OWA I am not going to change the ports that they have been using for years so that one or two people can access the 3CX interface without having to remember to add :5000. 3CX should not default to commonly used ports that are already in use at 95% of my customers locations. Your going to get a ton of push back from this. Also my 3CX boxes already get brute forced enough, putting the web interface on 80/443 is only going to increase security risks.

      October 29, 2014 at 9:39 pm
  6. George Bardissi

    Iphone and android apps can dial but presence shows disconnected

    October 22, 2014 at 2:38 am
    • Hi George
      You have to re-send the Welcome eMail to the phones – in this way, the old 5000/5001 port will be updated accordingly with the new 80/443.

      October 22, 2014 at 8:48 am
    • @George – this is because the Web ports have been changed – what was working on 5000 now works on 80 and what was working on 5001 for HTTPS now is working on 443…

      October 22, 2014 at 10:15 am
    • George Bardissi

      Confirmed 80 and 443 are open

      Resent welcome email

      No change

      3cx phone for windows works as expected remotely

      iPhone and android same result on disconnected status but on hook and can dial

      October 22, 2014 at 12:35 pm
    • Hi George,
      Please open a support ticket so this can be investigated further.

      October 22, 2014 at 1:39 pm
  7. Vance Harris

    200 ports is not going to cut it for a 128 seat or above system?

    October 22, 2014 at 2:11 pm
    • @Vance – No it will not be enough.. But we have to choose moderate and acceptable defaults because we have other license types not only the 128.
      The default range we chose covers it for 4 8 16 32 64 license limits. 128 and 256 are hich level enterprise and require require advanced configuration.

      October 22, 2014 at 4:50 pm
  8. Geoff Musselbrook

    Hi
    I understand how changing the ports for new installations is a good thing, however we will now have to change every extension on every 3cx we have ever installed, this will be a nightmare. Is the final release likely to have an option to not use the new port numbers, most of our customers are not capable of reprovisioning themselves and we also have very complex firewalls in place which will not allow port 80 and 443 access.

    I presume that the tennant system will be ok, as it uses the domain name rahter than port 5000, is that correct.
    Geoff.

    October 22, 2014 at 4:52 pm
    • @geoff – Yes the final release is going to have the ability to configure the port you want. So when your clients upgrade they can select the default ports of 5000 and 5001
      We are at the moment deciding what the default values should be…

      October 22, 2014 at 5:53 pm
    • Hi
      Still not sure if we can use this release on the tennant system. If I installe it will it kill all the rtennant or just the one I am upgrading?

      I would like to try it on just the main tennant account first.
      Geoff.

      October 28, 2014 at 7:48 pm
  9. Hi
    Is there a way to test in multitenat?
    same rules for ports?

    regards

    October 23, 2014 at 12:04 am
  10. We do not like this change in port numbers. This causes major issues with exchange 2013 web access and/or small business server. We have hundreds of installations that work this way and thus will not be workable. The fact 3cx has worked on different ports made it more flexible as well as better for qos tuning. This needs to be seriously rethought.

    October 29, 2014 at 4:05 pm
  11. Chuck Rich

    We have quite a few installations that we are managing. Every time there is a major shift like this that effects every phone and/or every computer running MyPhone then 3CX Phone, whichever the case may be, it causes a good bit of stress on the customer and us to have to rework everything which is not always as easy as just auto-provisioning the phones. This makes the case for renewing their software maintenance and upgrading a tougher sell. I’m certainly in favor of new features and functions but it should build on what’s already been established, not tear down what’s there and rebuild it again. Just my two cents…

    October 29, 2014 at 4:10 pm
  12. Scott Buchanan

    We use 3CX running Abyss on Server 2012 R2 Essentials, to simply potentials conflict the the server IIS for Remote Anywhere. This will conflict. Did I say conflict?

    October 29, 2014 at 4:20 pm
  13. Ronnie Barreto

    3cx Might feel that changing the ports to standard http & https port s a good thing, but Please take into account security, other web servers on the same ip, and legacy support. I feel that the increased visibility of the management console being on a standardized web port will increase hacking. Yes I know that 3cx employs anti-hacking abilities, but that doesn’t mean all 3cx installations will use strong passwords will get hacked. Many 3cx admins will get mad when their bill goes up 1000% by being hacked and sip extensions are created for fraudulent use. I know asterisk is apples to oranges but I wont even allow admin capabilities of any asterisk to public networks in fear of hacking. I don’t necessarily want to make access to management consoles easy.

    As said others it’s nice to pop in a new phone system without having port conflicts and figuring out were to put it. If you give the ability to change clients will be no different ports and managing can become a hassle. Standardization and consistency throughout your product versions show stability as well as ease of management.

    October 29, 2014 at 6:36 pm
    • @Ronnie – thank you for your feedback. As I said in previous comments, we are making the final release port configurable.. So you can choose whether to use default ports or whether to customize the ports for HTTP And HTTPS

      October 29, 2014 at 7:10 pm
  14. Laurent

    HTTP and HTTPS Port Changes:
    50 3cx Phones installed in a Customer service…. we need to re-provision all the softphones!!!!! (because don’t think users will do it by themself if you send them an E-mail).
    Before v12, I was in love of 3cx… but since v12, 3cx developpers are in an other planet.
    3cx making 64 sim calls licenses and more, but you don’t know how work a big company or a Customers service… 3cx phone is definitly not anymore dedicated for Customers services.
    Why changing ports!!!!! it’s just to lost time!!!!!
    Why the 3cxPhone in v12 lost so many functionalities compare v11!!!!!!!!
    I never seen a new software version with less options!!!!

    I’m definitly so unhappy of 3cx!

    October 31, 2014 at 10:42 pm
    • Laurent

      where are all these previous functionalities:
      – setup more than 1 extension in 3cx phone (all deskphones have this kind of functionalities and v11 was able to do it)
      – sidebar (in v11, it was possible to setup some shorcuts extensions; internal or externals numbers)
      – select the volume (speaker, microphone, ring) independently each other
      – configuration of sound devices used bu 3cx phone
      – …

      November 1, 2014 at 12:11 am
    • @Laurent – 3CXPhone is still available for download. You can use that for multiple accounts
      Sidebar – This is not clear.
      This is available in audio options
      Available in audio options.

      November 3, 2014 at 1:17 pm
  15. Nick

    Hi 3CX Team,

    I would like you to seriously reconsider making the default ports 443 and 80 for the release. 5000 and 5001 has been working well, and causes little or no conflicts. Any good admin can setup 3CX using these ports.

    Making the default 443 and 80 will simply cause you larger support issues, and I for one cannot see good reason to make this change from a technical point of view!?

    Make the default during install what it is… if people want to put on 443 and 80, let them, but leave everything well enough alone.

    This reminds me of the last time the change of ports was made… V8? then it was a pain as well!

    Thanks for listening.

    Nick

    November 11, 2014 at 2:51 am
  16. Scott Buchanan

    How do we work around remote access for Server 2012 Essentials R2?

    November 18, 2014 at 5:33 pm
    • @Scott – Unclear question – What do you mean Remote access? RDP?
      Contact Microsoft or search in their tech blogs..

      November 18, 2014 at 9:13 pm