The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The columns in the port utilization tables in this document describe the following:
A value representing the server or application and where applicable, the open or proprietary application protocol.
An identifier for the TCP or UDP port that the server or application is listening on, along with the IP address for incoming connection requests when acting as a server.
The remote application or device making a connection to the server or service specified by the protocol; or listening on the remote protocol and port.
The identifier for the TCP or UDP port that the remote service or application is listening on, along with the IP address for incoming connection requests when acting as the server.
The direction that traffic flows through the port: Inbound, Bidirectional, Outbound.
Note | The operating system dynamically assigns the source port that the local application or service uses to connect to the destination port of a remote device. In most cases, this port is assigned randomly above TCP/UDP 1024. |
Intracluster communication in the table represents communication between Unified CCX servers in a cluster.
TCP Ephemeral ports are used to accept connections during Java RMI communication. Java RMI clients know which port it need to connect, because RMI first connects to RMI Registry (well-known port - 6999) and get the information which ephemeral port client need to connect to Unified
CCX Administration page, Engine and CVD use RMI communication in CCX/IP-IVR, so TCP ephemeral port range is opened up for intracluster communication between these processes.
UDP Ephemeral ports are used to receive audio/video RTP streams; so UDP Ephemeral port range is opened for incoming connections for streaming RTP media from CTI ports.
Port 38983 is open only on Unified CCX systems that were upgraded from versions earlier than 9.0(1).
Intracluster communication (see table note 1) |
Provide RTMT data collecting, logging and alerting functionalities (AMC RMI Object Port) |
||||
Provide RTMT data collecting, logging and alerting functionalities (AMC RMI Registry Port) |
|||||
This is the port where the IDS engine listens for DB clients |
|||||
- This is an alternate port to bring up a second instance of IDS during upgrade. |
|||||
External process like HRC, WallBoard Client, External DB clients (like Squirrel or others for custom reporting) can connect |
|||||
DBL RPC, this is used during installation to set up IDS replication between nodes |
|||||
Real-Time Information Server (RIS) Data Collector service (RISDC) |
Connect to other RISDC services in the cluster to provide cluster-wide real-time information |
||||
Allowed RIS client connection to retrieve real-time information |
|||||
DRF master agent server port accepts connections from local agent GUI and CLI |
|||||
Using this port Unified ICM Subsystem listens to GED-125Clients. This port is modifiable |
|||||
SOAP Monitor - a troubleshooting tool for SOAP infrastructure |
|||||
Publish JMS events across JMS network connectors in the cluster (ActiveMQ) |
|||||
-Client browser trying to access any of the Administration interfaces or User Options interface. Web services client using RTMT, configuration APIs, and mobile supervisor applications. |
|||||
Finesse Tomcat (HTTP) |
TCP 8082 |
Client Browser |
— |
Bidirectional |
To access the Finesse Administration page and Finesse Agent Desktop. |
TCP 8443 |
|||||
- Client browser trying to access any of the Administration interfaces or User Options interface - Web services client using RTMT, configuration APIs, and mobile supervisor applications |
|||||
UDP 8500 |
Cluster replication of platform data (hosts) certificates etc. Uses a proprietary protocol. |
||||
- Tomcat instance used by Unified CCX engine - Clients trying to access HTTP triggers or documents / prompts / grammars |
|||||
Generic ephemeral TCP ports (see table note 2) |
|||||
Generic ephemeral UDP ports (see table note 3) |
Intracluster communication in the table represents communication between Unified IP IVR servers in a cluster.
TCP Ephemeral ports are used to accept connections during Java RMI communication. Java RMI clients know which port it need to connect, because RMI first connects to RMI Registry (well-known port - 6999) and get the information which ephemeral port client need to connect to. AppAdmin, Engine and CVD use RMI communication in CCX/IP-IVR, so TCP ephemeral port range is opened up for intracluster communication between these processes.
UDP Ephemeral ports are used to receive audio/video RTP streams; so UDP Ephemeral port range is opened for incoming connections for streaming RTP media from CTI ports.