Introduction

Typically, UCX server is deployed behind a router that implements NAT/PAT between the UCX server and the Internet.  In order to provide external access to servers on the local network, the router allows you to configure port forwarding (based on the manufacturer of your router, different names can be used for this feature - for example Virtual Server Setup).

This document focuses on the steps necessary to enable support for UCX telephony functionality, including accessing the Web Based Configuration Utility for remote management from the internet across the customer router.  Other UCX functionality may require configuration of the customer router to ensure proper communication can be established. The documentation describing that functionality includes the specific router configuration required, such as UCX Remote Access, Software Update, and External CDR.

Port Forwarding to Allow Remote Management

In order to enable access to the Web-based Configuration Utility of your UCX system from the public network, you should configure your router to forward the following ports to the IP address of your UCX Server (by default 192.168.1.200):

With this rule enabled, you can access the UCX Web-based Configuration Utility using the address https://<public IP address of your router>.

Alternatively, a "special" port number could be used for external access to the HTTPS port on UCX. For example, the router could be configured to send all traffic received on port 8000 to the internal IP address of UCX and port 443. Users would then access the system using the address: https://<public IP address of your router>:8000.

When configuring your router, the goal should be to open as few ports as possible.  Hence we recommend you to use only the Secure Web Server rule above.  Nevertheless, if you really want to access the UCX Web-based Configuration Utility also using the address http://<public IP address of your router>, you could also create the following port forwarding rule:

Port Forwarding for SIP Trunks

In order for the UCX system to properly establish voice path for SIP trunks calls in all possible scenarios, it is necessary to enable port forwarding of RTP ports to the UCX server.  The RTP port range (by default 10000 to 13999) must be forwarded to the IP address of your UCX Server (by default 192.168.1.200):

Port Forwarding for Remote XSTIM Phones 

In order to allow XSTIM based phones (E-MetroTel Infinity,Nortel/Avaya IP) to access your UCX Server from the public network, you should configure your router to forward the following ports to the IP address of your UCX Server (by default 192.168.1.200):

* If you use a non-default port number for XStim signaling (configured in the XSTIM settings in XSTIM Settings page), use the actual port number for the first rule in the table above.
 

Port Forwarding for Remote InfinityOne Clients

In order to allow InfinityOne softphones (Desktop, Browser or Mobile) to access your InfinityOne Server from the public network, you should configure your router to forward the following ports to the IP address of your InfinityOne Server (by default 192.168.1.200):

* If you use a non-default port number for the Site URL Port Number (configured in InfinityOne Installation Wizard or the InfinityOne Administration/General/Network settings), use the actual port number for the first rule in the table above.

Port Forwarding for Remote UCX MGCP Phones 

In order to allow MGCP phones (typically Panasonic IP phones) to access your UCX Server from the public network, you should configure your router to forward the following ports to the IP address of your UCX Server (by default 192.168.1.200):

In order to allow remote SIP phones to access your UCX Server from the public network, you should configure your router to forward the following ports to the IP address of your UCX Server (by default 192.168.1.200):

* If you use a non-default port number for SIP signaling (configured in SIP Settings page), use the actual port number for the first rule in the table above. For AWS systems, check the value pre-populated in the SIP Settings page under Bind Port.