- Port Utilization in System Services for Unified CCE for Release 12.5(1)
- Port Utilization in Contact Center Enterprise for Unified CCE for Release 12.5(1)
- Port Utilization in Unified CVP for Unified CCE for Release 12.5(1)
- Port Utilization in Cisco VVB for Unified CCE for Release 12.5(1)
- Port Utilization in Finesse for Unified CCE for Release 12.5(1)
- Port Utilization in Customer Collaboration Platform for Unified CCE for Release 12.5(1)
- Port Utilization in Unified Intelligence Center for Unified CCE for Release 12.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.
- Remote Port
The remote port is used to make an outgoing connection to the corresponding listener port.
- Traffic Direction
The direction that traffic flows through the port: Inbound, Bidirectional, Outbound.
Note |
|
Finesse Port Utilization
Listener (Process or Application Protocol) | Listener Protocol and Port | Remote Device (Process or Application Protocol) | Remote Port | Traffic Direction | Notes |
---|---|---|---|---|---|
Cisco Unified Web Proxy Service (HTTPS) | TCP 443, 8445 | Browser and third-party REST clients | - | Bidirectional | Secure port used for Finesse administration console, Finesse agent and supervisor desktop, Finesse Desktop Modules (gadgets) with the Finesse desktop and Finesse IP Phone Agent. Secure port used to communicate between Unified CCX Publisher and Subscriber for synchronizing configurations. |
Note | Finesse desktop uses specific ports for communication between Finesse servers for intra-cluster traffic. For the complete list of the ports that are used, see System Services Port Utilization. The Manage Digital Channel gadget uses HTTPS Port 443 to access the internet. The URI used will vary depending on the region. For more information on region-specific URI, see Manage Digital Channels gadget section in Cisco Finesse Administration Guide at https://www.cisco.com/c/en/us/support/customer-collaboration/finesse/products-installation-guides-list.html. |
Listener (Process or Application Protocol) | Listener Protocol and Port | Remote Device (Process or Application Protocol) | Remote Port | Traffic Direction | Notes |
---|---|---|---|---|---|
XMPP | TCP 5223 | Browser and agent desktop | - | Bidirectional | Secure XMPP connection between the Finesse server and custom third-party applications. Secure XMPP connection between Unified CCX Publisher and Subscriber. |
BOSH (HTTPS) | TCP 7443 | Browser and agent desktop | - | Bidirectional | Secure BOSH connection between the Finesse server and agent and supervisor desktops for communication over HTTPS. |
Note |
|
Listener (Process or Application Protocol) | Listener Protocol and Port | Remote Device (Process or Application Protocol) | Remote 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. |
Third-Party (External) Web Server
Note | Gadgets hosted on a third-party (external) web server are fetched through the Finesse server on the port exposed by said web server. |
Listener (Process or Application Protocol) | Listener Protocol and Port | Remote Device (Process or Application Protocol) | Remote Port | Traffic Direction | Notes |
---|---|---|---|---|---|
Administration & Data Server settings | |||||
JDBC (SQL) | - | - | TCP 1433 1 | Bidirectional | Connection to the AWDB for authentication and authorization of agents and supervisors |
CTI Server settings (Side A and B) | |||||
GED-188 | - | - | Bidirectional | Connection to the Agent PG for CTI Server events (such as Agents, Teams, Queues, and Call events) |