Ports and Protocols Guide
- 08 Apr 2026
- 1 Minute to read
- Print
- DarkLight
- PDF
Ports and Protocols Guide
- Updated on 08 Apr 2026
- 1 Minute to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback!
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.
Ports
Destination | Protocol | Port Number(s) | Direction | Application |
|---|---|---|---|---|
Controller | TCP | 443 | Outbound | HTTP Management |
Controller | TCP | 40006 | Outbound | EPC Control Traffic |
Controller | TCP | 26022 | Outbound | Certificate Transfer |
Internet | TCP/UDP | 53 | Outbound | DNS |
DHCP Server | UDP | 67/68 | Outbound | DHCP client |
SIP Endpoint | UDP & TCP | 5060/5061* | Inbound/ Outbound | SIP signaling |
Peer Agent | UDP | 29999* | Inbound/ Outbound | P2P Testing |
Peer Endpoint | UDP | 30000-50000 | Inbound/ Outbound | Real-time media |
Variable | ICMP | N/A | Inbound/ 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).
Was this article helpful?