- 14 Jul 2025
- 2 Minutes to read
- Print
- DarkLight
- PDF
Master Ports and Protocols Guide
- Updated on 14 Jul 2025
- 2 Minutes to read
- Print
- DarkLight
- PDF
This document will serve as a master guide to all Ports and Protocols configurations. For additional assistance, please contact support@nectarcorp.com
DXP Connection
Nectar Diagnostics can be configured to connect to the Digital Experience Platform using an HTTPS connection using port 443.
The port is configurable but should be allowed to default to 443.
The connection can be configured to be made through an HTTP proxy with or without proxy credentials.
This connection is used to export session data.
UC Diagnostics-Vendor-Specific APIs
The following APIs are supported and enabled using the CLI:
API | Protocol | Ports |
Skype for Business SDN | HTTP HTTPS | Configurable |
Ribbon Edge SBC | TCP TLS | Configurable |
Ribbon Core SBC | TCP IPSEC | 5000/5001 |
Audiocodes Mediant SBC | TCP TLS | 2748/2749 |
Cisco CUCM | CTI | Configurable |
Oracle SBC | TCP TLS | Configurable |
Voice Quality Collector | UDP/TCP | Configurable |
Genesys Engage | TCP TLS | Configurable |
Cisco Cube Syslog | TCP IPSEC | Configurable |
Cisco Cube RADIUS | UDP IPSEC | Configurable |
Avaya Session Manager Syslog | TCP | Configurable |
Avaya SBC Syslog | TCP | Configurable |
Avaya SBC RADIUS | UDP | Configurable |
Foundation APM
Destination | Foundation APM to Destination | Destination to Foundation APM | Notes |
Active Directory/LDAP | TCP:389/636 | External Authentication | |
CIP | TCP:443 | ||
DNS | UDP:53 | ||
NTP Server | UDP:123 | Internal or External | |
Perspective Agents | TCP:443 | ||
SMTP Server | TCP:25 | ||
Advanced Diagnostics-M | TCP:443 | ||
User PC | TCP:80/443 | ||
N10 Cloud Correlation Engine | TCP:443 | ||
N10 RIG Agent | TCP:1527 | When separate boxes |
Advanced Diagnostics-M
Destination | Advanced Diagnostics- M to Destination | Destination to Advanced Diagnostics-M | Notes |
DNS | TCP:53 | ||
NTP | TCP:123 | ||
Advanced Diagnostics-A | TCP:22/9006/9008 | ||
Advanced Diagnostics-P | TCP:22/9006/9008/9010 | ||
Foundation APM Server | TCP:20/21/80/443 UDP:162 | ||
User PC | TCP:20/21/22/443 |
Advanced Diagnostics-P
Destination | Advanced Diagnostics- P to Destination | Destination to Advanced Diagnostics-P | Notes |
L3 Network Devices | UDP:161 | Optional for route table updates | |
Advanced Diagnostics-A | TCP:9006/9008 | ||
User PC | TCP:22 | ||
NTP | TCP:123 | ||
DNS | TCP:53 |
Advanced Diagnostics-A
Destination | Advanced Diagnostics- A to Destination | Destination to Advanced Diagnostics-A | Notes |
User PC | TCP:22 | ||
NTP | TCP:123 |
Advanced Diagnostics-Vendor-Specific APIs
Destination | Notes |
Audiocodes SBC API Cisco CUCM CTI Genesys GSIPs/TLIB API Plantronics Headset API RTCP-XR (RFC-6035) Sonus 1k/2k or 5k API | These APIs and ports are configurable. Review these integrations with your Nectar Engineering Team. |
Endpoint Client
Each Endpoint Client (EPC) and Endpoint Hub (EPH) connect to the centralized controller and establish a secure TCP control connection.
Source | Destination | Protocol | Traffic Direction | Remarks |
---|---|---|---|---|
EPC | Controller | TCP 443 | Outbound | Controller control/test result connection using AES-256 encryption |
EPH | Controller | TCP 443 | Outbound | Controller control/test result connection using AES-256 encryption |
Tests are schedule by the controller which informs a source Endpoint (EPC or EPH) what the destination endpoint is and the type of test to perform. Equally the controller informs the destination endpoint (EPC or EPH) that at test is scheduled to be run against it. Once tests are completed the results are send from both endpoints involved in the test back to the controller over the endpoint -> controller secure connection established previously.
For P2P tests, test traffic flows directly between the Endpoints:
Source | Destination | Protocol | Traffic Direction | Remarks |
---|---|---|---|---|
EPC | EPH | UDP 29999 | Outbound | P2P network test |
For VoIP tests, test traffic flows directly between the Endpoints. A VoIP call is established between the source and destination endpoints using the standard Session Initiation Protocol (SIP) and then bidirectional audio data passes between them using the standard Realtime Protocol (RTP):
Source | Destination | Protocol | Traffic Direction | Remarks |
---|---|---|---|---|
EPC | EPH | TCP 5060 (SIP) | Outbound | Session Initiation Protocol |
EPC | EPH | UDP 30000-50000 (RTP) | Outbound | Realtime Protocol (audio from source) |
EPH | EPC | UDP 30000-50000 (RTP) | Outbound | Realtime Protocol (audio to source) |
Foundation APM: Monitored Devices and Applications
Destination | Foundation APM to Destination | Destination to Foundation APM | Notes |
Avaya AES | ICMP, UDP:161 | UDP:162 | |
Avaya CMS | ICMP, UDP:161 | UDP:162 | TCP:22/23 for CMS versions < r17 |
Avaya Communication Manager | TCP:5022 ICMP, UDP:161 | TCP:9001 UDP:162 | 9001 default, configurable |
Avaya G860 Gateway | ICMP, UDP:161 | UDP:162 | |
Avaya IP Phones/ Endpoints | ICMP, UDP:161 | UDP:5005 | |
Avaya IP Boards (CLAN, IPSI, etc.) | ICMP | ||
Avaya IP Office | TCP:50808/50809/8443 ICMP, UDP:161 | UDP:162 | 50808/50809 not needed as of Nectar r8 and IPO r10.1 |
Avaya IP Office VM Pro | ICMP, UDP:161 | UDP:162 | Windows VM Pro |
Avaya Media Gateways/ MedPro | ICMP, UDP:161 | UDP:162/5005 | |
Avaya Modular Messaging | TCP:443/80/3389 ICMP, UDP:161 | UDP:162 | |
Avaya System Manager | TCP:80/443 ICMP, UDP:161 | UDP:162 | |
Avaya Session Manager | TCP:443 ICMP, UDP:161 | UDP:162 | |
Avaya VAL Boards | ICMP, UDP:161 | ||
Avaya/Verint Recording | ICMP, UDP:161/2161 | UDP:162 | |
Avaya Voice/Experience Portal | ICMP, UDP:161 | UDP:162 | MPP and VMPS |
Cisco Communications Manager | TCP:22/8443 ICMP, UDP:161 | UDP:162 | |
Cisco CUBE | ICMP, UDP:161 | UDP:162 | |
Cisco Expressway | TCP:443 ICMP, UDP:161 | UDP:162 | |
Cisco IM & Presence | TCP:443 ICMP, UDP:161 | UDP:162 | |
Cisco Meeting Server | TCP:443 ICMP, UDP:161 | UDP:162 | |
Cisco Unity | TCP:8443 ICMP, UDP:161 | UDP:162 | |
Acme Net-Net SBC | ICMP, UDP:161 | UDP:162 | |
AudioCodes Mediant Series | ICMP, UDP:161 | UDP:162 | |
Avaya SBC | ICMP, UDP:161 | UDP:162 | |
AVST Messaging | TCP:80/443/5985/5986 UDP:161 | UDP:162 | |
IPC Unigy | TCP:80/443 | UDP:162 | |
Nice NTR | TCP:3306 ICMP, UDP 161 | UDP:162 | |
Nortel BCM | ICMP, UDP:161 | UDP:162 | |
Nortel CallPilot | ICMP, UDP:161 | UDP:162 | |
Nortel CS1K Call Server | TCP:22 ICMP, UDP:161 | UDP:162 | |
Nortel CS1K Media Gateways | ICMP, UDP:161 | UDP:162 | |
Nortel CS1K Signaling Server | TCP:22 ICMP, UDP:161 | UDP:162 | |
Ribbon SBC | ICMP, UDP:161 | UDP:162 | |
Skype for Business | TCP:433/1433 TCP:5985/5986 ICMP, UDP:161 | UDP:162 | Additional TCP ports, if using dynamic SQL port |
UPS | ICMP, UDP:161 | UDP:162 | RFC-1628 compliant |
Windows Server | TCP:5985/5986 ICMP, UDP:161 | UDP:162 | |
Linux Server | ICMP, UDP:161 | UDP:162/514 | |
Data Gear | ICMP, UDP:161 | UDP:162 |
Port Definitions
TCP Port Number | Description |
20,21 | FTP |
22 | SSH |
23 | Telnet |
25 | SMTP |
80 | HTTP |
IP Protocol:89 | OSPF Peering |
179 | BGP Peering |
389 | LDAP |
443 | HTTPS |
636 | SSH LDAP |
1433 | SQL |
1527 | JDBC |
3306 | MySQL |
3389 | RDP |
5022 | SSH Avaya SAT |
5023 | Telnet Avaya SAT |
5900 | VNC |
5985/5986 | PowerShell HTTP/HTTPS |
5989 | Nortel Element Manager |
6001 | Nortel Call Recording Socket |
8443 | Cisco SOAP, IP Office API |
9001 | Avaya Call Detail Records (CDRs) |
9006/9008/9010 | Nectar Proprietary |
50808 | IP Office System Status |
50809 | IP Office System Status - Secure |
UDP Port Number | Description |
69 | TFTP |
123 | NTP |
161 | SNMP Poll |
162 | SNMP Trap |
5005 | RTCP |