Port Utilization in Finesse

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.

Finesse Port Utilization

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 Platform Tomcat

Listener (Process or Application Protocol)

Listener Protocol and Port

Remote Device (Process or Application Protocol)

Remote Protocol and Port

Traffic Direction

Notes

HTTP

UDP 8080

Browser

Bidirectional

Unsecure port used for access to platform administration, platform serviceability, and Disaster Recovery System.

HTTPS

UDP 8443

Browser

Bidirectional

Secure port used for access to platform administration, platform serviceability, and Disaster Recovery System.

Table 3 Platform Database

Listener (Process or Application Protocol)

Listener Protocol and Port

Remote Device (Process or Application Protocol)

Remote Protocol and Port

Traffic Direction

Notes

DBMON

TCP 1500

Bidirectional

Informix Database Software (IDS) access and replication

DBL RPC

TCP 1515

Intra-Cluster communication

Bidirectional

DBL RPC, this is used during installation to set up IDS replication between nodes

Table 4 Cisco Finesse Notification Service

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

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 5 Platform System Services

Listener (Process or Application Protocol)

Listener Protocol and Port

Remote Device (Process or Application Protocol)

Remote Protocol and Port

Traffic Direction

Notes

SFTP

TCP 22

Bidirectional

SFTP access for hosted third-party gadget support

SSH

TCP 22

SSH client

Bidirectional

Platform CLI

NTP

UPD 123

NTP server

Bidirectional

Network time synchronization

Platform Alert Manager and Collector (AMC) service

TCP 1090, 1099

RTMT client

 

Bidirectional

The platform AMC service uses this connection to allow the RTMT tool to retrieve and display platform alerts.

Real-time Information Service Data Collector (RISDC) service

TCP 2555

RTMT client

 

Bidirectional

Used by the RISDC platform service. The Real-time Information Server (RIS) maintains real-time Cisco Unified CM information such as device registration status, performance counter statistics, critical alarms generated, and so on. The Cisco RISDC service provides an interface for applications, such as RTMT, SOAP applications, Cisco Unified CM Administration and AMC to retrieve the information that is stored in all RIS nodes in the cluster.

Disaster Recovery Framework (DRF) Master Agent Service

TCP 4040

Platform Administration webapp

 

Bidirectional

DRF service

Table 6 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 7 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.