Port Utilization Guide for Cisco Unified Contact Center Express Solutions, Release 11.5(1)

Port Utilization Table Columns

The columns in the port utilization tables in this document describe the following:

Listener (Process or Application Protocol): A value representing the server or application and where applicable, the open or proprietary application protocol.
Listener Protocol and Port: 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.
Remote Device (Process or Application Protocol): 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.
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.
Traffic Direction: 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.
For security reasons, keep open only the ports mentioned in this guide and those required by your application. Keep the rest of the ports blocked.

Table 1. Cisco Finesse Tomcat
Listener (Process or Application Protocol)	Listener Protocol and Port	Remote Device (Process or Application Protocol)	Remote Protocol and Port	Traffic Direction	Notes
HTTP	TCP 80, 8082	Browser		Bidirectional	Unsecure port used for Finesse administration console, Finesse agent and supervisor desktop, Finesse Web Services, and Finesse Desktop Modules (gadgets) with the Finesse desktop.
HTTPS	TCP 443, 8445	Browser		Bidirectional	Secure port used for Finesse administration console, Finesse agent and supervisor desktop, Finesse Web Services, and Finesse Desktop Modules (gadgets) with the Finesse desktop.

Table 2. Cisco Finesse Notification Service
Listener (Process or Application Protocol)	Listener Protocol and Port	Remote Device (Process or Application Protocol)	Traffic Direction	Notes
XMPP	TCP 5222	Browser, agent desktop	Bidirectional	Unsecure XMPP connection between the Finesse server and custom applications on the agent or supervisor desktops for communication over HTTP.
XMPP	TCP 5223	Browser, agent desktop	Bidirectional	Secure XMPP connection between the Finesse server and custom applications on the agent or supervisor desktops for communication over HTTPS.
BOSH (HTTP)	TCP 7071	Browser, agent desktop	Bidirectional	Unsecure BOSH connection between the Finesse server and agent and supervisor desktops for communication over HTTP.
BOSH (HTTPS)	TCP 7443	Browser, agent desktop	Bidirectional	Secure BOSH connection between the Finesse server and agent and supervisor desktops for communication over HTTPS.

Table 3. Primary and Secondary Node Communication
Listener (Process or Application Protocol)	Listener Protocol and Port	Remote Device (Process or Application Protocol)	Remote Protocol and Port	Traffic Direction	Notes
XMPP	TCP 5222			Bidirectional	The primary and secondary Finesse servers use this XMPP connection to communicate with each other to monitor connectivity.

Table 4. Third-Party (External) Web Server
Listener (Process or Application Protocol)	Listener Protocol and Port	Remote Device (Process or Application Protocol)	Remote Protocol and Port	Traffic Direction	Notes
HTTP			TCP 80, 8082	Bidirectional	Gadgets hosted on a third-party (external) web server are fetched through the Finesse server on the port exposed by said web server.
HTTPS			TCP 443, 8445	Bidirectional	Gadgets hosted on a third-party (external) web server are fetched through the Finesse server on the port exposed by said web server.