During setup, the EPC Setup Wizard will offer to automatically create Windows firewall exceptions for the ports used by the agent and Controller. If this option is disabled, or if a third-party firewall is in use, ensure that the required local and remote ports are open to allow the agent to function properly.
Notes
The source of all traffic is the Endpoint Client.
Many of these processes are bidirectional and require both inbound and outbound access.
EPC requires that certain ICMP functions be enabled on the Windows host which are typically blocked by the Windows Firewall. The EPC Setup Wizard automatically enables the minimal set of ICMP functionality required during Agent installation.
Controller Connection
To connect to the EPC controller, outbound traffic on TCP 443 will need to be enabled to the following IPs resolving to neccontroller.us.nectar.services:
52.204.230.133 |
34.231.219.110 |
50.17.99.212 |
Ports
Port Direction
Note that for Hubs, inbound traffic will need to be enabled for the following destinations:
UDP & TCP 5060/5061
UDP 29999
UDP 30000/50000
Regular EPC agents will not require inbound traffic for these destinations.
Destination | Protocol | Port Number(s) | Direction | Application |
|---|---|---|---|---|
Controller | TCP | 443 | Outbound | HTTP Management |
(Optional) Controller | TCP | 40006 | Outbound | HTTP Management |
(Optional) Internet | TCP/UDP | 53 | Outbound | DNS |
(Optional) DHCP Server | UDP | 67/68 | Outbound | DHCP client |
SIP Endpoint | UDP & TCP | 5060/5061* | Outbound | SIP signaling |
Peer Agent | UDP | 29999* | Outbound | P2P Testing |
Peer Endpoint | UDP | 30000-50000 | Outbound | Real-time media |
(Optional) Variable | ICMP | N/A | Outbound | Inbound ICMP messages (required for some network tests) |
* Default port number. A different port number can be assigned during setup/configuration of the Controller (see the Nectar EPC-Controller SSE Installation Guide or Nectar EPC-Controller MSE Installation Guide for details).