3CX On Windows - V18 - Multiple NGINX Listeners

[tnelson]

All,

We did a default 3CX system install on port 5000, and 5001. Its working perfectly. Thank you. We have two questions:

1)We are however experts with NGINX, and we tried to add some more HTTP, and HTTPS listeners in the web config which were unique from IIS server which is running on port 80, and 443. For example we want nginx to listen to 8080, and 8443 as well. We made the appropriate corrections to nginx.conf which is on the server, and restarted nginx, and local clients on the PBX can access these ports, and run from 8080, and 8443 with no problem at all. Furthermore, We can run from a clean network on the other side of the planet to 5000, and 5001, and have both 8080, and 8443 open on the network firewall. But for some reason remote access to the additional ports are dropped by 3CX, almost as if the PBX is checking traffic to the application and dropping it based on incoming port. IE the NGINX webserver is running properly, and listening to the right ports.

Is 3CX installing some filter in Windows Firewall or doing something unusual at the application level? If so what other steps do we need to do accept traffic from CLASSA/B/C/INTERNET to ports 8080, and 8443 as well. These ports are not terminating to IIS, and are in fact running 3CX on the local machine.

2) In Versions 14, and 16 there were older Polycom and Cisco Phone templates on the console which are no longer on the console. Understand they may not be supportable no for the company, but is there anyway we can add them back to Version 18 just for us? We have never had any need to call support for these phones, and dont understand them being dropped. If I am not mistaken it uses to say No Longer Supported section or something like that.


Thanks in Advance... and Great Product!

Cheers
GLI

 

[tnelson]

//BTW THESE ARE THE DEFAULT STATEMENTS IN THE NGINX.CONF OUT OF THE BOX
listen 5001 ssl http2;
listen [::]:5001 ssl http2;
listen 5000;
listen [::]:5000;

//THESE ARE THE STATEMENTS WE ADDED
listen 8080;
listen [::]:8080;
listen 8443 ssl http2;
listen [::]:8443 ssl http2;

NGINX SERVICE IS LOADING NORMALLY, AND THESE PORTS LISTEN AND ARE ACCESSIBLE ON LOCAL WEB BROWSERS TO 127.0.0.1:8443, and 127.0.0.1:8080 ALONG WITH INTERNALNIC-IP:8080 AND INTERNALNIC-IP:8443.

 

[tnelson]

Or alternatively... for the meantime while we troubleshoot this wacky problem.... if anyone has a working IIS http proxy configuration you can share from https://www.acme.com to localhost:5001 or localhost:5000 with SSL offload...

 

[tnelson]

Well folks... this works...we had some gremlins in google cloud which cleared on a firewall reset.
Net Net... the default 3CX install goes to http port 5000, and https port 5001. On Windows Server, the Default IIS server listens to port 80, and 443.

There are at least five workable conditions to use additional ports:
a) You can configure NGINX to support 8080(ALT HTTP), and 8443(ALT HTTPS) which makes the platform addressible through MOST FIREWALLS but not all.
b) Or you can set up an IIS to NGINX/3CX proxy using 80/443 to proxy to 5000/5001.
c) Or you can shut IIS off and just run 3CX as an appliance, and give it more ports in the NGINX.CONF...adding 80,443, 8080, and 8443...
d) You can move to a vhost model and run NGINX as a Proxy to your 3CX server(s) or 3CX server instances.....
e) You can run VPN over the top and bypass your own firewall configurations for VPN connected clients on all ports. This has NGINX listening on a broad range of ports.

In any event the base install is a bit simplistic...but a we promise the ALT ports are very helpful to all.

Cheers - The Chickens.