Chapter 1. Port Utilization in Unified CCX

Port Utilization Table Columns

Unified CCX Port Utilization

Unified IP IVR Port Utilization

Chapter 2. Port Utilization in Finesse

Port Utilization Table Columns

Finesse Port Utilization

Chapter 3. Port Utilization in MediaSense

Port Utilization Table Columns

MediaSense Port Utilization

Chapter 4. Port Utilization in SocialMiner

Port Utilization Table Columns

SocialMiner Port Utilization

Chapter 5. Port Utilization in Unified Intelligence Center

Port Utilization Table Columns

Unified Intelligence Center Port Utilization

Copyright Page

Chapter 1. Port Utilization in Unified CCX

- Port Utilization Table Columns

- Unified CCX Port Utilization

- Unified IP IVR Port Utilization

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.

Unified CCX Port Utilization

Unified CCX Port Utilization

Listener (Process or Application Protocol)

Listener Protocol and Port

Remote Device (Process or Application Protocol)

Remote Protocol and Port

Traffic direction

Purpose

System Service

TCP 7

Editor

—

Bidirectional

- Echo for Editor

- ICM Controller

System Service

TCP 22

—

—

Bidirectional

SFTP and SSH access

Tomcat (HTTP)

TCP 80

—

—

Bidirectional

Web access

FIPPA Server

TCP 80

Intracluster communication (see table note)

—

Bidirectional

Used for page push to phone from the FIPPA Service

System Service

UDP 123

—

—

Bidirectional

Network time sync

SNMP Agent

UDP 161

—

—

Inbound

Provide services for SNMP-based management applications

AON Management Console (AMC) Service

TCP 1090

Intracluster communication

—

Bidirectional

Provide RTMT data collecting, logging and alerting functionalities (AMC RMI Object Port)

AON Management Console (AMC) Service

TCP 1099

Intracluster communication

—

Bidirectional

Provide RTMT data collecting, logging and alerting functionalities (AMC RMI Registry Port)

Cisco Unified CCX Socket.IO Service

TCP 12014

—

—

Bidirectional

This is the port where live-data reporting clients can connect to socket.IO server.

Cisco Unified CCX Socket.IO Service

TCP 12015

—

—

Bidirectional

This is the secure port where live-data reporting clients can connect to socket.IO server.

DBMON

TCP 1500

—

—

Bidirectional

This is the port where the IDS engine listens for DB clients

DBMON

TCP 1501

—

—

Bidirectional

- This is an alternate port to bring up a second instance of IDS during upgrade.

- Localhost traffic only

Informix Dynamic Server (IDS)

TCP 1504

External process like HRC, WallBoard Client, External DB clients (like Squirrel or others for custom reporting) can connect

—

Bidirectional

Unified CCX database port

DBL RPC (XML)

TCP 1515

Intracluster communication

—

Bidirectional

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

Real-Time Information Server (RIS) Data Collector service (RISDC)

TCP 2555

Intracluster communication

—

Bidirectional

Connect to other RISDC services in the cluster to provide cluster-wide real-time information

RISDC

TCP 2556

Intracluster communication

—

Bidirectional

Allowed RIS client connection to retrieve real-time information

JTAPI Client (QBE)

TCP 2789

Unified CM

2748

Bidirectional

Provide services to CTI applications

Disaster Recovery System (DRS)

TCP 4040

—

Bidirectional

DRF master agent server port accepts connections from local agent GUI and CLI

Real-time service

TCP 5001

—

—

Bidirectional

SOAP Monitor

Perfmon service

TCP 5002

—

—

Bidirectional

SOAP Monitor

Control center service

TCP 5003

—

—

Bidirectional

SOAP Monitor

Log Collection Service

TCP 5004

—

—

Bidirectional

SOAP Monitor

System Service

TCP 5007

—

—

Bidirectional

SOAP Monitor - a troubleshooting tool for SOAP infrastructure

Engine

UDP 5065

SIP gateway

—

Bidirectional

Communicate with SIP gateway

Notification Service

TCP 5222

Openfire/SMAC

—

Bidirectional

OpenFire socket based client connection

Notification Service

TCP 5443

Openfire/SMAC

—

Bidirectional

OpenFire socket based client connection

CVD

TCP 5900

CVD of other node in cluster

—

Bidirectional

Heartbeats between CVDs in the cluster

CVD

ActiveMQ

TCP 6161

Internal

6161

Bidirectional

Publish JMS events across JMS network connectors in the cluster

CVD

TCP 6999

Engine, Tomcat, CVD, and Editor

—

Bidirectional

RMI Port

Notification Service

TCP 7071

Web Browser

—

Bidirectional

HTTP bind

Notification Service

TCP 7443

Web Browser

—

Bidirectional

Secure HTTP bind

DBMON (CN)

TCP 8001

Intracluster communication

—

Bidirectional

DB change notification port

Tomcat (HTTP)

TCP 8080

Client Browser

—

Bidirectional

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

Cisco Unified Intelligence Center Tomcat (HTTP)

TCP 8081

Client Browsers

—

Bidirectional

Client browser trying to access the Cisco Unified Intelligence Center web interface

Cisco Finesse Tomcat (HTTP)

TCP 8082

Cisco Finesse Agent/Supervisor Desktop, Cisco Finesse Administration Console, and REST APIs

—

Bidirectional

HTTP port to access Cisco Finesse Tomcat web applications.
Note:   Cisco Finesse Agent/Supervisor Desktop and Cisco Finesse Administration Console accessed using port 8082 is automatically redirected to port 8445.

Tomcat (HTTPs)

TCP 8443

Client Browser

—

Bidirectional

- 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

Cisco Unified Intelligence Center Tomcat (HTTPs)

TCP 8444

Client Browsers

—

Bidirectional

Client browser trying to access the Cisco Unified Intelligence Center web interface

Cisco Finesse Tomcat (HTTPs)

TCP 8445

Cisco Finesse Agent/Supervisor Desktop, Cisco Finesse Administration Console, and REST APIs

—

Bidirectional

Secured HTTP port to access Cisco Finesse Tomcat web applications.

IPSec Manager daemon

UDP 8500

—

—

Bidirectional

Cluster replication of platform data (hosts) certificates. Uses a proprietary protocol.

IPSec Manager daemon

TCP 8500

—

—

Bidirectional

Connectivity testing. Uses a proprietary protocol.

Engine

TCP 9080

—

—

Bidirectional

- Tomcat instance used by Unified CCX engine

- Clients trying to access HTTP triggers or documents / prompts / grammars / live data

Engine

TCP 9443

—

—

Bidirectional

- Secure port used by Tomcat instance

- Used by live-data client for authentication

Unified CCX Engine, Cisco Mobile Supervisor

TCP 12028

—

—

Bidirectional

CTI Server

Cisco IP Voice Media Streaming application (RTP RTCP)

UDP 24576 ~ 32767

—

—

Bidirectional

- Audio media streaming

- Kernel streaming device driver

TCP 32768 ~ 61000

—

—

Bidirectional

Generic ephemeral TCP ports (see table note)

UDP 32768 ~ 61000

—

—

Bidirectional

Generic ephemeral UDP ports (see table note)

UDP 58000

Custom application

—

Bidirectional

Provides an interface to control Agent Desktop over a custom protocol.

Notification Service

ActiveMQ

TCP 61616

Chat applications

—

Bidirectional

Notification Service — ActiveMQ OpenWire transport connector

Table Notes

1. Intracluster communication in the table represents communication between Unified CCX servers in a cluster.

2. 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.

3. 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.

4. Port 38983 is open only on Unified CCX systems that were upgraded from versions earlier than 9.0(1).

Unified IP IVR Port Utilization

Cisco Unified IP IVR Port Utilization

Listener (Process or Application Protocol)

Listener Protocol and Port

Remote Device (Process or Application Protocol)

Remote Protocol and Port

Traffic direction

Purpose

System Service

TCP 7

Editor

—

Bidirectional

- Echo for Editor

- ICM Controller

System Service

TCP 22

—

—

Bidirectional

SFTP and SSH access

Tomcat (HTTP)

TCP 80

—

—

Bidirectional

Web access

System Service

UDP 123

—

—

Bidirectional

Network time sync

SNMP Agent

UDP 161

—

—

Inbound

Provide services for SNMP-based management applications

Tomcat

TCP 443

Client Browser

—

Bidirectional

Web access

AON Management Console (AMC) Service

TCP 1090

Intracluster communication (see table note 1)

—

Bidirectional

Provide RTMT data collecting, logging and alerting functionalities (AMC RMI Object Port)

AON Management Console (AMC) Service

TCP 1099

Intracluster communication

—

Bidirectional

Provide RTMT data collecting, logging and alerting functionalities (AMC RMI Registry Port)

DBMON

TCP 1500

—

—

Bidirectional

This is the port where the IDS engine listens for DB clients

DBMON

TCP 1501

—

—

Bidirectional

- This is an alternate port to bring up a second instance of IDS during upgrade.

- Localhost traffic only

Informix Dynamic Server (IDS)

TCP 1504

External process like HRC, WallBoard Client, External DB clients (like Squirrel or others for custom reporting) can connect

—

Bidirectional

Unified IP IVR database port

DBL RPC (XML)

TCP 1515

Intracluster communication

—

Bidirectional

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

Unified IP IVR Cluster View Daemon (CVD)

TCP 1994

—

Bidirectional

Real-Time Information Server (RIS) Data Collector service (RISDC)

TCP 2555

Intracluster communication

—

Bidirectional

Connect to other RISDC services in the cluster to provide cluster-wide real-time information

RISDC

TCP 2556

Intracluster communication

—

Bidirectional

Allowed RIS client connection to retrieve real-time information

JTAPI Client (QBE)

TCP 2789

Unified CM

2748

Bidirectional

Provide services to CTI applications

Disaster Recovery System (DRS)

TCP 4040

—

—

Bidirectional

DRF master agent server port accepts connections from local agent GUI and CLI

Unified IP IVR Engine

TCP 5000

Unified ICM

—

Bidirectional

Using this port Unified ICM Subsystem listens to GED-125Clients. This port is modifiable

Real-time service

TCP 5001

—

—

Bidirectional

SOAP Monitor

Perfmon service

TCP 5002

—

—

Bidirectional

SOAP Monitor

Control center service

TCP 5003

—

—

Bidirectional

SOAP Monitor

Log Collection Service

TCP 5004

—

—

Bidirectional

SOAP Monitor

System Service

TCP 5007

—

—

Bidirectional

SOAP Monitor - a troubleshooting tool for SOAP infrastructure

CVD

TCP 5900

CVD of other node in cluster

—

Bidirectional

Heartbeats between CVDs in the cluster

CVD

TCP 6161

Intracluster communication only

6161

Bidirectional

Publish JMS events across JMS network connectors in the cluster (ActiveMQ)

CVD

TCP 6999

Engine, Tomcat, CVD, and Editor

—

Bidirectional

RMI Port

DBMON (CN)

TCP 8001

Intracluster communication

—

Bidirectional

DB change notification port.

Tomcat (HTTP)

TCP 8080

Client Browser

—

Bidirectional

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

Tomcat

TCP 8443

—

—

Bidirectional

DB access via SOAP; Tomcat forwards the SOAP request to AXL

Tomcat (HTTPS)

TCP 8443

Client Browser

—

Bidirectional

- 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

IPSec Manager daemon

UDP 8500

—

—

Bidirectional

Cluster replication of platform data (hosts) certificates etc. Uses a proprietary protocol.

IPSec Manager daemon

TCP 8500

—

—

Bidirectional

Connectivity testing. Uses a proprietary protocol.

Engine

TCP 9080

—

—

Bidirectional

- Tomcat instance used by Unified CCX engine

- Clients trying to access HTTP triggers or documents / prompts / grammars

Cisco IP Voice Media Streaming application (RTP RTCP)

UDP 24576 ~ 32767

—

—

Bidirectional

- Audio media streaming. - Kernel streaming device driver

—

TCP 32768 ~ 61000

—

—

Bidirectional

Generic ephemeral TCP ports (see table note 2)

—

UDP 32768 ~ 61000

—

—

Bidirectional

Generic ephemeral UDP ports (see table note 3)

Table Notes

1. Intracluster communication in the table represents communication between Unified IP IVR servers in a cluster.

2. 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.

3. 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.

Chapter 2. Port Utilization in Finesse

- Port Utilization Table Columns

- Finesse Port Utilization

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

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.

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.

Platform Database

Listener (Process or Application Protocol)

Listener Protocol and Port

Remote Device (Process or Application Protocol)

Remote Protocol and Port

Traffic Direction

Notes

JDBC

TCP 1500, 1501

Browser

Bidirectional

Informix Database Software (IDS) access and replication

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.

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

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.

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.

Unified Contact Center Enterprise

Listener (Process or Application Protocol)

Listener Protocol and Port

Remote Device (Process or Application Protocol)

Remote Protocol and 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

Side A:

TCP 42027^1

Side B:

TCP 43027^1

Bidirectional

Connection to the Agent PG for CTI Server events (such as Agents, Teams, Queues, and Call events)

1The ports listed are the default ports for these connections. You can use different ports than the ones specified in this table.

Chapter 3. Port Utilization in MediaSense

- Port Utilization Table Columns

- MediaSense Port Utilization

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.

MediaSense Port Utilization

MediaSense Port Utilization

Listener (Process or Application Protocol)

Listener Protocol and Port

Remote Device (Process or Application Protocol)

Remote Protocol and Port

Traffic Direction

Note

HTTPS

TCP 443, 8443

Web browser

Any

Used by Administration, serviceability

HTTPS

TCP 8440

Client application

Any

Used by API access

HTTPS

TCP 9443

Client application

Any

Used by media service to redirect authenticated requests.

HTTPS

TCP 8446

Web browser, API client

Any

Used by Call control service.

HTTPS

TCP 9081

Client application

Any

Used by media service to redirect authenticated requests.

HTTP

TCP 80, 8080

Web browser

Any

Used by Administration, serviceability

HTTP

TCP 8081

Web browser, API client

Any

Used by Call control service

HTTP

TCP 8085

Another CMS node

Any

Used by Call control service

HTTP

TCP 8087

CMS cluster nodes only

Any

Used by System service

HTTP

TCP 8088

CMS cluster nodes only

Any

Used by Configuration service

RTSP

TCP 554, 8554

RTSP media player

Any

Used by SM agent

RTSP

TCP 9554

Client application or media player

Any

Used by media service to redirect authenticated requests.

SIP

TCP 5060

UDP 5060

Unified Communications Manager or Unified Border Element

TCP 5060

UDP 5060

Call control service.

TCP/IP

TCP 1543

CMS cluster nodes only

Any

Used by Informix ER to make connections between primary server and secondary servers.

Used by API service or configuration service to make JDBC connections with Informix.

Keep-alive heartbeats

UDP 8091

CMS cluster nodes only

UDP 8091

Used by a call control service to detect availability of other call control services.

JMS

TCP 61610

CMS cluster nodes only

Any

Used by API service

JMS

TCP 61612

CMS cluster nodes only

Any

Used by Call control service

JMS

TCP 61616

CMS cluster nodes only

Any

Used by SM agent

Ephemeral port range

UDP 32768 - 61000

Phone or gateway that sends RTP media streams.

Any

Range of ports used by media service to receive RTP media streams.

Chapter 4. Port Utilization in SocialMiner

- Port Utilization Table Columns

- SocialMiner Port Utilization

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.

SocialMiner Port Utilization

SocialMiner Port Utilization

Listener (Process or Application Protocol)

Listener Protocol and Port

Remote Device (Process or Application Protocol)

Remote Protocol and Port

Traffic Direction

Notes

Email notifications

Port 25

Outward, from SocialMiner to the configured email server.

SocialMiner communicates with the configured email server (that can be in the corporate intranet or on the internet) to send email notifications.

HTTP

Port 80

Bidirectional

Used for unsecure (HTTP) traffic:

- From the SocialMiner user interface (browser) or APIs to the SocialMiner server.

- From the SocialMiner server to the internet. SocialMiner communicates outward to the internet to fetch social contact information (such as Facebook posts and tweets) over HTTP.

- From the internet or corporate website to the SocialMiner server. SocialMiner receives incoming chat and callback requests from the internet or corporate website over HTTP.

HTTPS

Port 443

Bidirectional

Used for secure (HTTPS) traffic:

- From the SocialMiner user interface (browser) or APIs to the SocialMiner server.

- From the SocialMiner server to the internet. SocialMiner communicates outward to the internet to fetch social contact information (such as Facebook posts and tweets) over HTTPS.

- From the internet or corporate website to the SocialMiner server. SocialMiner receives incoming chat and callback requests from the internet or corporate website over HTTPS.

Email notifications SSL/TLS

Port 465 (configurable)

Outward, from SocialMiner to the configured email server.

SocialMiner communicates with the configured email server (that can be in the corporate intranet or on the internet) to send email notifications.

Email (SMTP)

Port 587 (configurable in Unified CCX Administration)

Outward, from SocialMiner to the Exchange Server.

Used by the Email Reply API to send email.

The Email Reply API uses SMTP to send a response to a customer email message.

Email (secure IMAP/IMAPS)

Port 993 (configurable in Unified CCX Administration)

Outward, from SocialMiner to the Exchange Server.

Used by email feeds to retrieve email.

IMAPS allows email feeds to fetch email from the Exchange Servers and allows the Email Reply API to retrieve email and save draft email messages.

Reporting

Port 1526

Inward, from CUIC to the SocialMiner server.

CUIC communicates with SocialMiner to gather reporting information.

Active Directory

Port 3268 (configurable)

Outward, from SocialMiner to the configured Active Directory host

SocialMiner communicates outward to the configured Active Directory host for unsecure Active Directory connections.

Active Directory SSL

Port 3269 (configurable)

Outward, from SocialMiner to the configured Active Directory host

SocialMiner communicates outward to the configured Active Directory host for secure Active Directory connections.

XMPP (IM) notifications using an external XMPP server

Port 5222 (configurable)

Outward, from SocialMiner to the configured XMPP Notifications server.

SocialMiner communicates with the configured XMPP Notifications server (that can be in the corporate intranet or on the internet) to send XMPP (IM) notifications.

Notification Service (XMPP eventing over TCP sockets)

Port 5222

Inward, from CCX to the SocialMiner server.

SocialMiner listens for incoming TCP socket connections to register and receive XMPP events. Unified CCX uses this port to receive social contact events.

Eventing and chat (BOSH)

Port 7071

Bidirectional

The unsecure BOSH connection supports eventing and chat communication between the SocialMiner user interface and the SocialMiner server.

Eventing and chat (secure BOSH)

Port 7443 is used for secure BOSH connections to the XMPP eventing server.

Bidirectional

The secure BOSH connection supports eventing and chat communication between the SocialMiner user interface and the SocialMiner server.

Media routing (in CCE deployments)

Port 38001 (configurable)

Inward, from the CCE MR PG to the SocialMiner server.

The CCE Media Routing Peripheral Gateway (MR PG) communicates over a socket connection to SocialMiner to support the media routing connection.

Chapter 5. Port Utilization in Unified Intelligence Center

- Port Utilization Table Columns

- Unified Intelligence Center Port Utilization

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.

Unified Intelligence Center Port Utilization

Web Requests to Cisco Unified Intelligence Center and Operation Administration Maintenance and Provisioning (OAMP)

Listener (Process or Application Protocol)

Listener Protocol and Port

Remote Device (Process or Application Protocol)

Remote Protocol and Port

Traffic Direction

Notes

Unified Intelligence Center

TCP 8081

Browser

HTTP - Unified Intelligence Center

TCP 8444

Browser

HTTPS - Unified Intelligence Center

OAMP

TCP 8080

Browser

HTTP - OAMP

TCP 8443

Browser

HTTPS - OAMP

Cisco Unified Intelligence Center and Live Data

Listener (Process or Application Protocol)

Listener Protocol and Port

Remote Device (Process or Application Protocol)

Remote Protocol and Port

Traffic Direction

Notes

Storm DRPC service

TCP 3772

Live Data DRPC port

TCP 3773

Live Data DRPC invocation port

CCE Live Data Cassandra Service

TCP 12000

Live Data Cassandra TCP port for commands and data

TCP 12001

Live Data Cassandra SSL port for encrypted communication. (Unused unless enabled in encryption_options.)

TCP 9160

Live Data Cassandra port that Thrift uses to listen to clients

CCE Live Data Zookeeper Service

TCP 2181

Live Data Reporting

CCE Live Data ActiveMQ Service

TCP 12002

ActiveMQ JMX connector port

TCP 12003

ActiveMQ JMX rmi port

CCE Live Data Web Service

TCP 12004 - 12006

Live Data Reporting

CCE Live Data Active MQ Service

TCP 61616

Live Data ActiveMQ Openwire transport Connector port

TCP 61612

Live Data ActiveMQ Stomp transport connector port

CCE Live Data Storm Nimbus Service

TCP 6627

Live Data Nimbus Thrift port

CCE Live Data Socket.IO Service

TCP 12007 - 12008

Live Data Socket.IO listening port

Intracluster Ports Between Cisco Unified Intelligence Center

Listener (Process or Application Protocol)

Listener Protocol and Port

Remote Device (Process or Application Protocol)

Remote Protocol and Port

Traffic Direction

Notes

Platform (DB)

TCP 1500 - 1501

Platform (DB)

IDS access and replication (but not open to external access)

CUIC Reporting Process

UDP 54327 (Multicast)

Unified Intelligence Center node

Hazelcast Discovery

CUIC Reporting Process

TCP 57011

Unified Intelligence Center Node

Hazelcast

For more information on other port usages, see: Click Here

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: Click Here . Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)