port utilization guide for cisco unified contact center...
TRANSCRIPT
Port Utilization Guide for Cisco Unified Contact Center Solutions,Release 12.5(1)Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706USAhttp://www.cisco.comTel: 408 526-4000
800 553-NETS (6387)Fax: 408 527-0883
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 WITHTHE 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 ofthe UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHERWARRANTY 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 OFMERCHANTABILITY, 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, WITHOUTLIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERSHAVE 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, networktopology 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 unintentionaland coincidental.
All printed copies and duplicate soft copies of this document are considered uncontrolled. See the current online version for the latest version.
Cisco has more than 200 offices worldwide. Addresses and phone numbers are listed on the Cisco website at www.cisco.com/go/offices.
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:https://www.cisco.com/c/en/us/about/legal/trademarks.html. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply apartnership relationship between Cisco and any other company. (1721R)
© 1994–2020 Cisco Systems, Inc. All rights reserved.
C O N T E N T S
Preface v
Change History v
About This Guide v
Audience v
Obtaining Documentation and Submitting a Service Request v
Field Notice v
Documentation Feedback vi
Conventions vi
Port Utilization in System Services 1C H A P T E R 1
Port Utilization Table Columns 1
System Services Port Utilization 2
Port Utilization in Contact Center Enterprise 7C H A P T E R 2
Port Utilization Table Columns 7
Unified CCE and Packaged CCE Port Utilization 8
Cloud Connect Port Utilization 23
Unified CCMP Port Utilization 24
Unified CRM Connectors Port Utilization 26
Port Utilization in CVP 27C H A P T E R 3
Port Utilization Table Columns 27
Unified CVP Port Utilization 28
Port Utilization in Cisco VVB 35C H A P T E R 4
Port Utilization Table Columns 35
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)iii
Cisco VVB Port Utilization 36
Port Utilization in Finesse 39C H A P T E R 5
Port Utilization Table Columns 39
Finesse Port Utilization 40
Port Utilization in Customer Collaboration Platform 45C H A P T E R 6
Port Utilization Table Columns 45
Customer Collaboration Platform Port Utilization 46
Port Utilization in Unified Intelligence Center 49C H A P T E R 7
Port Utilization Table Columns 49
Unified Intelligence Center Port Utilization 50
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)iv
Contents
Preface
Change HistoryThis table lists changes made to this guide. Most recent changes appear at the top.
DateSeeChange
September, 2019Initial Release of Document for Release 12.5(1)
Cloud Connect Port UtilizationIncluded a new section for CloudConnect port information
About This GuideThis document provides a list of the TCP and UDP ports that Cisco Unified Contact Center products use. Youuse this information to configure Quality of Service (QoS) and Firewall/VPN solutions. Proper configurationis important on a network with an Architecture for Voice, Video, and Integrated Data (AVVID) solution.
AudienceThis document is intended primarily for network administrators.
Obtaining Documentation and Submitting a Service RequestFor information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a servicerequest, and gathering additional information, see What's New in Cisco Product Documentation athttps://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html.
Subscribe to What's New in Cisco Product Documentation, which lists all new and revised Cisco technicaldocumentation as an RSS feed and delivers content directly to your desktop using a reader application. TheRSS feeds are a free service.
Field NoticeCisco publishes Field Notices to notify customers and partners about significant issues in Cisco products thattypically require an upgrade, workaround, or other user action. For more information, see Product Field NoticeSummary at https://www.cisco.com/c/en/us/support/web/tsd-products-field-notice-summary.html.
You can create custom subscriptions for Cisco products, series, or software to receive email alerts or consumeRSS feeds when new announcements are released for the following notices:
• Cisco Security Advisories
• Field Notices
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)v
• End-of-Sale or Support Announcements
• Software Updates
• Updates to Known Bugs
For more information on creating custom subscriptions, see My Notifications at https://cway.cisco.com/mynotifications.
Documentation FeedbackTo provide comments about this document, send an email message to the following address:[email protected]
We appreciate your comments.
ConventionsThis document uses the following conventions:
DescriptionConvention
Boldface font is used to indicate commands, such as user entries, keys, buttons,folder names, and submenu names.
For example:
• Choose Edit > Find.
• Click Finish.
boldface font
Italic font is used to indicate the following:
• To introduce a new term. Example: A skill group is a collection of agentswho share similar skills.
• A syntax value that the user must replace. Example: IF (condition, true-value,false-value)
• A book title. Example: See the .
italic font
Window font, such as Courier, is used for the following:
• Text as it appears in code or that the window displays. Example:<html><title>Cisco Systems, Inc. </title></html>
window font
Angle brackets are used to indicate the following:
• For arguments where the context does not allow italic, such as ASCII output.
• A character string that the user enters but that does not appear on the windowsuch as a password.
< >
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)vi
PrefaceDocumentation Feedback
C H A P T E R 1Port Utilization in System Services
• Port Utilization Table Columns, on page 1• System Services Port Utilization, on page 2
Port Utilization Table ColumnsThe 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 applicationprotocol.
Listener Protocol and Port
An identifier for the TCP or UDP port that the server or application is listening on, along with the IPaddress 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 withthe IP address for incoming connection requests when acting as the server.
Traffic Direction
The direction that traffic flows through the port: Inbound, Bidirectional, Outbound.
• The operating system dynamically assigns the source port that the local application or serviceuses to connect to the destination port of a remote device. In most cases, this port is assignedrandomly above TCP/UDP 1024.
• For security reasons, keep open only the ports mentioned in this guide and those required byyour application. Keep the rest of the ports blocked.
Note
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)1
System Services Port UtilizationTable 1: System Services Port Utilization
PurposeTrafficdirection
RemoteProtocol andPort
Remote Device (Process orApplication Protocol)
ListenerProtocol andPort
Listener(Process orApplicationProtocol)
- Echo for Editor
- ICM Controller
Bidirectional—EditorTCP 7SystemService
SFTP and SSH accessBidirectional——TCP 22SystemService
- Web access
- Call recording server
- Unified CCMP Web serverand AXL provisioning
- CRM Connector server
- Default port for voice browsersto fetch media and "externalVXML" files frommedia server
Bidirectional——TCP 80Tomcat(HTTP)
NTP, network time syncBidirectional——UDP 123SystemService
Provide services forSNMP-based managementapplications
Bidirectional——UDP 161SNMP Agent
Web access for CCE WebAdministration and InternetScript Editor
- Unified CCMP clients
- Default port for voice browsersto fetch media and "externalVXML" files frommedia server
Bidirectional—Client Browser
Unified CCE Admin(AW-HDS)
TCP 443Tomcat
Web access for CCE WebAdministration and InternetScript Editor
- Unified CCMP clients
- Default port for voice browsersto fetch media and "externalVXML" files frommedia server
Bidirectional—Client Browser
Unified CCE Admin(AW-HDS)
TCP 443Tomcat
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)2
Port Utilization in System ServicesSystem Services Port Utilization
PurposeTrafficdirection
RemoteProtocol andPort
Remote Device (Process orApplication Protocol)
ListenerProtocol andPort
Listener(Process orApplicationProtocol)
Provide RTMT data collecting,logging and alertingfunctionalities (AMC RMIObject Port)
Bidirectional—Intracluster communicationTCP 1090AONManagementConsole(AMC)Service
Provide RTMT data collecting,logging and alertingfunctionalities (AMC RMIRegistry Port)
Bidirectional—Intracluster communicationTCP 1099AONManagementConsole(AMC)Service
This is the port where the IDSengine listens for DB clients
Bidirectional——TCP 1500DBMON
- This is an alternate port tobring up a second instance ofIDS during upgrade.
- Localhost traffic only
Bidirectional——TCP 1501DBMON
DBL RPC, this is used duringinstallation to set up IDSreplication between nodes
Bidirectional—Intracluster communicationTCP 1515DBL RPC
Used by the RISDC platformservice. The Real-timeInformation Server (RIS)maintains real-time CiscoUnified CM information suchas device registration status,performance counter statistics,critical alarms generated, and soon. The Cisco RISDC serviceprovides an interface forapplications, such as RTMT,SOAP applications, CiscoUnified CMAdministration andAMC to retrieve the informationthat is stored in all RIS nodes inthe cluster.
Bidirectional—Intracluster communicationTCP 2555Real-TimeInformationServer (RIS)Data Collectorservice(RISDC)
Allowed RIS client connectionto retrieve real-time information
Bidirectional—Intracluster communicationTCP 2556RISDC
Real-time serviceBidirectional——TCP 4040DisasterRecoverySystem (DRS)
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)3
Port Utilization in System ServicesSystem Services Port Utilization
PurposeTrafficdirection
RemoteProtocol andPort
Remote Device (Process orApplication Protocol)
ListenerProtocol andPort
Listener(Process orApplicationProtocol)
SOAP Monitor
Used by SOAP to monitor theReal Time Monitoring Serviceand fetch the Server informationfor selection of specific CMdevices and other suchactivities.
Bidirectional——TCP 5001Real-timeservice
SOAP Monitor
Used by SOAP to monitor thePerformance Monitor Servicefor opening and closingsessions, collecting session dataand fetching various other data.
Bidirectional——TCP 5002Perfmonservice
SOAP Monitor
Used by SOAP to monitor theControl Center Service foractivities like getting the ServiceStatus and performing servicedeployment.
Bidirectional——TCP 5003Control centerservice
SOAP MonitorBidirectional——TCP 5004LogCollectionService
SOAP Monitor - atroubleshooting tool for SOAPinfrastructure
Bidirectional——TCP 5007SystemService
Data or Service grid to manageCisco IdS cluster nodes.
Bidirectional5701
Note: TheCisco IdSserver node inthe clusterconnects to thisport.
Intra-cluster communicationTCP 5701Cisco IdentityService DataGrid
DB change notification port.Bidirectional—Intracluster communicationTCP 8001DBMON (CN)
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)4
Port Utilization in System ServicesSystem Services Port Utilization
PurposeTrafficdirection
RemoteProtocol andPort
Remote Device (Process orApplication Protocol)
ListenerProtocol andPort
Listener(Process orApplicationProtocol)
- Client browser trying to accessany of the Administrationinterfaces or User Optionsinterface.
- Web services client usingRTMT, configuration APIs, andmobile supervisor applications.
- Data replication for callrecording server
- OAMP for Live Data
- CRM Connector for SAP(adjustable through registry)
Bidirectional—Client BrowserTCP 8080Tomcat(HTTP)
- Client browser trying to accessany of the Administrationinterfaces or User Optionsinterface.
- Web services client usingRTMT, configuration APIs, andmobile supervisor applications.
- DB access via SOAP; Tomcatforwards the SOAP request toAXL.
Bidirectional—Client BrowserTCP 8443Tomcat(HTTPS)
Connectivity testing. Uses aproprietary protocol.
Bidirectional——TCP 8500IPSecManagerdaemon
Cluster replication of platformdata (hosts) certificates etc. Usesa proprietary protocol.
Bidirectional——UDP 8500IPSecManagerdaemon
HTTPS for Cisco IdS———TCP 8553Cisco IdentityService ( CiscoIdS)1
1 Not applicable to Cisco Virtualized Voice Browser.
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)5
Port Utilization in System ServicesSystem Services Port Utilization
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)6
Port Utilization in System ServicesSystem Services Port Utilization
C H A P T E R 2Port Utilization in Contact Center Enterprise
• Port Utilization Table Columns, on page 7• Unified CCE and Packaged CCE Port Utilization, on page 8• Unified CCMP Port Utilization, on page 24• Unified CRM Connectors Port Utilization, on page 26
Port Utilization Table ColumnsThe 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 applicationprotocol.
Listener Protocol and Port
An identifier for the TCP or UDP port that the server or application is listening on, along with the IPaddress 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 withthe IP address for incoming connection requests when acting as the server.
Traffic Direction
The direction that traffic flows through the port: Inbound, Bidirectional, Outbound.
• The operating system dynamically assigns the source port that the local application or service uses toconnect to the destination port of a remote device. In most cases, this port is assigned randomly aboveTCP/UDP 1024.
• For security reasons, keep open only the ports mentioned in this guide and those required by yourapplication. Keep the rest of the ports blocked.
Note
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)7
Unified CCE and Packaged CCE Port UtilizationThis table includes information for Unified CCE and CTI OS.
Some port definitions use a formula. For example:
TCP 40007 + (Instance Number * 40)
In this example, instance 0 uses port 40007, instance 1 uses port 40047, instance 2 uses port 40087, and soon.
In the following table, PG1, PG2, and PG3 are not specific PG numbers or DMP IDs. They are the order inwhich the PGs get installed.
Note
This document does not include the Enterprise Chat and Email (ECE) port details. For more information onECE ports, see the ECE documentation at: https://www.cisco.com/c/en/us/support/customer-collaboration/cisco-enterprise-chat-email/tsd-products-support-series-home.html.
Note
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)8
Port Utilization in Contact Center EnterpriseUnified CCE and Packaged CCE Port Utilization
Table 2: Unified CCE Port Utilization: Routers, PGs, Administration & Data Servers, and Loggers
NotesTrafficDirection
RemoteProtocol andPort
Remote Device(Process orApplicationProtocol)
Listener Protocol and PortListener(Process orApplicationProtocol)
Private network at the centralcontroller site
UDP ports are notused, if QoS isenabled on the routerprivate interface.
Note
Bi-directionalRouter (sideA)(MDS)
Private low:
• TCP 41004 + (instancenumber * 40)
Private medium:
• TCP 41016 + (instancenumber * 40)
Private high:
• TCP 41005 + (instancenumber * 40)
State Xfer for CIC:
• TCP 41022 + (instancenumber * 40)
State Xfer for HLGR:
• TCP 41021 + (instancenumber * 40)
• TCP 41032 + (instancenumber * 40)
State Xfer for RTR:
• TCP 41020 + (instancenumber * 40)
UDP 39500–39999
State Xfer for DBAgent:
• TCP 41033 + (instancenumber * 40)
Router (side B)(MDS)
Bi-directionalMDS processclient
MDS process port
TCP 41000
Router (side B)(MDS)
Bi-directionalMDS processclient(synchronized)
MDS state transfer port
TCP 41001
Router (side B)(MDS)
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)9
Port Utilization in Contact Center EnterpriseUnified CCE and Packaged CCE Port Utilization
NotesTrafficDirection
RemoteProtocol andPort
Remote Device(Process orApplicationProtocol)
Listener Protocol and PortListener(Process orApplicationProtocol)
Bi-directionalDB Workerprocess client
DB Worker process port
UDP 445
Router (side Aand B) (DBWorker)
Public network (test-other-side)Bi-directionalICM PG1(OppositeSide: A or B)(pgagent)
TCP 43006 + (instance number* 40)
ICMPG1 (sideA and B)(pgagent)
Public network (test-other-side)Bi-directionalICM PG2(OppositeSide: A or B)(pgagent)
TCP 45006 + (instance number* 40)
ICMPG2 (sideA and B)(pgagent)
Public network (test-other-side)Bi-directionalICM PG3(OppositeSide: A or B)(pgagent)
TCP 47506 + (instance number* 40)
ICMPG3 (sideA and B)(pgagent)
Private network
UDP ports are notused, if QoS isenabled on the ICMPG private interface.
Note
Bi-directionalICM PG1(OppositeSide: A or B)
• Private low:
TCP 43004 + (instancenumber * 40)
• Private medium:
TCP 43016 + (instancenumber * 40)
• Private high:
TCP 43005 + (instancenumber * 40)
• State Xfer for OPC:
TCP 43023 + (instancenumber * 40)
UDP 39500–39999
ICMPG1 (sideA and B)(MDS)
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)10
Port Utilization in Contact Center EnterpriseUnified CCE and Packaged CCE Port Utilization
NotesTrafficDirection
RemoteProtocol andPort
Remote Device(Process orApplicationProtocol)
Listener Protocol and PortListener(Process orApplicationProtocol)
Private network
UDP ports are notused if QoS isenabled on the ICMPG private interface.
Note
Bi-directionalICM PG2(OppositeSide: A or B)
• Private low:
TCP 45004 + (instancenumber * 40)
• Private medium:
TCP 45016 + (instancenumber * 40)
• Private high:
TCP 45005 + (instancenumber * 40)
• State Xfer for OPC:
TCP 45023 + (instancenumber * 40)
UDP 39500–39999
ICMPG2 (sideA and B)(MDS)
Private network
UDP ports are notused if QoS isenabled on the ICMPG private interface.
Note
Bi-directionalICM PG3(OppositeSide: A or B)
• Private low:
TCP 47504 + (instancenumber * 40)
• Private medium:
TCP 47516 + (instancenumber * 40)
• Private high:
TCP 47505 + (instancenumber * 40)
• State Xfer for OPC:
TCP 47523 + (instancenumber * 40)
UDP 39500–39999
ICMPG3 (sideA and B)(MDS)
Bi-directionalMDS processclient
MDS process port
TCP 43000
ICMPG1 (sideB) (MDS)
Bi-directionalMDS processclient(synchronized)
MDS state transfer port
TCP 43001
ICMPG1 (sideB) (MDS)
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)11
Port Utilization in Contact Center EnterpriseUnified CCE and Packaged CCE Port Utilization
NotesTrafficDirection
RemoteProtocol andPort
Remote Device(Process orApplicationProtocol)
Listener Protocol and PortListener(Process orApplicationProtocol)
Bi-directionalMDS processclient
MDS process port
TCP 45000
ICMPG2 (sideB) (MDS)
Bi-directionalMDS processclient(synchronized)
MDS state transfer port
TCP 45001
ICMPG2 (sideB) (MDS)
Bi-directionalMDS processclient
MDS process port
TCP 47500
ICMPG3 (sideB) (MDS)
Bi-directionalMDS processclient(synchronized)
MDS state transfer port
TCP 47501
ICMPG3 (sideB) (MDS)
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)12
Port Utilization in Contact Center EnterpriseUnified CCE and Packaged CCE Port Utilization
NotesTrafficDirection
RemoteProtocol andPort
Remote Device(Process orApplicationProtocol)
Listener Protocol and PortListener(Process orApplicationProtocol)
Private network at the centralcontroller site
UDP ports are notused if QoS isenabled on the routerprivate interface.
Note
Bi-directionalRouter (side B)(MDS)
Private low:
• TCP 41004 + (instancenumber * 40)
Private medium:
• TCP 41016 + (instancenumber * 40)
Private high:
• TCP 41005 + (instancenumber * 40)
State Xfer for CIC:
• TCP 41022 + (instancenumber * 40)
State Xfer for HLGR:
• TCP 41021 + (instancenumber * 40)
• TCP 41032 + (instancenumber * 40)
State Xfer for RTR:
• TCP 41020 + (instancenumber * 40)
UDP 39500–39999
State Xfer for DBAgent:
• TCP 41033 + (instancenumber * 40)
Router (sideA)(MDS)
Bi-directionalMDS processclient
MDS process port
TCP 40000
Router (sideA)(MDS)
Bi-directionalMDS processclient(synchronized)
MDS state transfer port
TCP 40001
Router (sideA)(MDS)
Bi-directionalMDS processclient
MDS process port
TCP 42000
ICMPG1 (sideA) (MDS)
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)13
Port Utilization in Contact Center EnterpriseUnified CCE and Packaged CCE Port Utilization
NotesTrafficDirection
RemoteProtocol andPort
Remote Device(Process orApplicationProtocol)
Listener Protocol and PortListener(Process orApplicationProtocol)
Bi-directionalMDS processclient(synchronized)
MDS state transfer port
TCP 42001
ICMPG1 (sideA) (MDS)
Bi-directionalMDS processclient
MDS process port
TCP 44000
ICMPG2 (sideA) (MDS)
Bi-directionalMDS processclient(synchronized)
MDS state transfer port
TCP 44001
ICMPG2 (sideA) (MDS)
Bi-directionalMDS processclient
MDS process port
TCP 46000
ICMPG3 (sideA) (MDS)
Bi-directionalMDS processclient(synchronized)
MDS state transfer port
TCP 46001
ICMPG3 (sideA) (MDS)
Public network connecting thePG to the central controller
Router to pre-5.0 PGcommunication.
UDP ports are notused if QoS isenabled on the ICMPG private interface.
Note
Bi-directionalICM PG(pgagent)
• Public low:
TCP 40002 + (instancenumber * 40)
• Public medium:
TCP 40017 + (instancenumber * 40)
• Public high:
TCP 40003 + (instancenumber * 40)
UDP 39500–39999
Router (sideA)DMP (ccagent)
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)14
Port Utilization in Contact Center EnterpriseUnified CCE and Packaged CCE Port Utilization
NotesTrafficDirection
RemoteProtocol andPort
Remote Device(Process orApplicationProtocol)
Listener Protocol and PortListener(Process orApplicationProtocol)
Public network connecting thePG to the central controller
Router to pre-5.0 PGcommunication.
UDP ports are notused if QoS isenabled on the ICMPG private interface.
Note
Bi-directionalICM PG(pgagent)
• Public low:
TCP 41002 + (InstanceNumber * 40)
• (instance number
Public medium:
TCP 41017 + (instancenumber * 40)
• Public high:
TCP 41003 + (instancenumber * 40)
UDP 39500–39999
Router (side B)DMP (ccagent)
Real-time feedBi-directionalAdministration& Data Server
TCP 40007 + (instance number* 40)
Router A(rtfeed)
Real-time feedBi-directionalAdministration& Data Server
TCP 41007 + (instance number* 40)
Router B(rtfeed)
ReplicationBi-directionalAdministration& Data ServerHistorical DataServer (HDS)
TCP 40026 + (instance number* 40)
TCP 40028 + (instance number* 40)
Logger (sideA)
Campaign Manager EMT portto Dialer
Bi-directionalDialer andImport
TCP 40032 + (instance number* 40)
Logger (sideA)
ReplicationBi-directionalAdministration& Data ServerHistorical DataServer (HDS)
TCP 41026 + (instance number* 40)
TCP 41028 + (instance number* 40)
Logger (sideB)
Campaign Manager EMT portto Dialer
Bi-directionalDialer andImport
TCP 41036 + (instance number* 40)
Logger (sideB)
Real-time feedBi-directionalAdministrationclient
TCP 48008 + (instance number* 40)
PrimaryAdministration& Data Server(rtfeed)
Real-time feedBi-directionalAdministrationclient
TCP 49008 + (instance number* 40)
SecondaryAdministration& Data Server(rtfeed)
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)15
Port Utilization in Contact Center EnterpriseUnified CCE and Packaged CCE Port Utilization
NotesTrafficDirection
RemoteProtocol andPort
Remote Device(Process orApplicationProtocol)
Listener Protocol and PortListener(Process orApplicationProtocol)
Public network connecting theNAM to the CICM
Bi-directionalNAM Router(CIC)
UDP 40025 + (instance number* 40)
CICM Router(side A)(INCRPNIC)
Public network connecting theNAM to the CICM
Bi-directionalNAM Router(CIC)
UDP 41025 + (instance number* 40)
CICM Router(side B)(INCRPNIC)
CSFS event synchronizationlink
Bi-directionalCSFSduplexed peer
TCP 40015CSFS
RecoveryBi-directional40013 + (instance number *40)Logger (sideA)
RecoveryBi-directional41013 + (instance number *40)Logger (sideB)
This serviceability componentis installed on major CCEcomponent servers (e.g. router,logger, PG, and Administrationand Data Servers)
Bi-directionalTCP 7890Diagnosticframework
Table 3: Unified CCE Port Utilization: Distributor and Internet Script Editor
NotesTrafficDirection
RemoteProtocol andPort
Remote Device(Process orApplicationProtocol)
Listener Protocol and PortListener(Process orApplicationProtocol)
Bi-directionalTCP 1433Logger
Distributor
MSSQL
Table 4: Unified CCE Port Utilization: CCE Outbound Option Dialer
NotesTrafficDirection
RemoteProtocol andPort
Remote Device(Process orApplicationProtocol)
Listener Protocol and PortListener(Process orApplicationProtocol)
Set in theSIPDialerPortBaseNumberregistry key.
Bi-directionalUDP 58800Cisco UnifiedCommunicationsManager(Unified CM)
SIP
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)16
Port Utilization in Contact Center EnterpriseUnified CCE and Packaged CCE Port Utilization
NotesTrafficDirection
RemoteProtocol andPort
Remote Device(Process orApplicationProtocol)
Listener Protocol and PortListener(Process orApplicationProtocol)
Receive ports for reservationcalls.
Use the following registry keyto select and configure UDPports: RTPPortRangeStart
Bi-directionalVoice gatewayUDP ports in a range based onthese formulas:
• RangeStart =RTPPortRangeStart +(instNum * 2000)
• RangeEnd = RangeStart +2000
You can set RTPPortRangeStartin the registry key:RTPPortRangeStart. instNumis the instance number for theDialer.
RTP for SIP
Bi-directionalUDP 69TFTP serverTFTP
Bi-directionalEphemeralTFTP filetransfer
TheMR PG connects to the SIPDialer using this port.
Bi-directionalTCP 38001+ (instance number)MR PG
This port is used with UnifiedCommunications Manager,Voice Gateway, or SIP Proxy.
Bi-directional5060 and"SIPDialerPortBaseNumber +instance number"
MR PG (SIP)
Table 5: Unified CCE Port Utilization: CTI and CTI Object Server
NotesTrafficDirection
RemoteProtocol andPort
Remote Device(Process orApplicationProtocol)
Listener Protocol and PortListener(Process orApplicationProtocol)
Bi-directionalARM Interface
CTI OS Server
CAD Server
Side A
TCP 42027 + (instance number* 40)
Side B
TCP 43027 + (instance number* 40)
GED-188 (CTIServer)
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)17
Port Utilization in Contact Center EnterpriseUnified CCE and Packaged CCE Port Utilization
NotesTrafficDirection
RemoteProtocol andPort
Remote Device(Process orApplicationProtocol)
Listener Protocol and PortListener(Process orApplicationProtocol)
Applicable to first CTI OSinstance.Multi-instance CTIOSand Cisco Unified ContactCenter Hosted require a customport be defined.
Bi-directionalCTI OS Client
CTI OS ServerPeers
CAD Desktop
Cisco SyncService
TCP 42028CTI OS Server
Desktop Silent MonitoringBi-directionalCTI OS ClientUDP 39200CTI OSSupervisorDesktop
Bi-directionalTCP 42228CTI OS SilentMonitorService
Support for screen call contextBi-directionalSiebel serverTCP 42228CiscoEnterpriseDataStore
Table 6: Unified CCE Port Utilization: TDM/IP Peripherals
NotesTrafficDirection
RemoteProtocol andPort
Remote Device(Process orApplicationProtocol)
Listener Protocol and PortListener(Process orApplicationProtocol)
IP Process Communications
JTAPIBi-directionalTCP 2748Unified CMCTI/QBE
Unified ICM/IVR messageinterface, VRU PIM
Bi-directionalTCP5000–5001
CustomerVoice Portal(or ISN)
Cisco UnifiedIP-IVR
PG, VRU PIM(GED-125)
JTAPI application serverBi-directionalUnified CMTCP 2789CCE PG
Bi-directionalTCP 38001Media Routingprocess
MR PIM
TDM Process Communications
For more information on peripheral communication, see the “ACD Supplement” user documentation for the specificswitch you are using.
Note
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)18
Port Utilization in Contact Center EnterpriseUnified CCE and Packaged CCE Port Utilization
NotesTrafficDirection
RemoteProtocol andPort
Remote Device(Process orApplicationProtocol)
Listener Protocol and PortListener(Process orApplicationProtocol)
Used by real-time bridgeBi-directionalTCP 8000Aspect ACDAspect PIM
Application bridge
Event link
Bi-directionalTCP 6101
TCP 6102
TCP 9001
Aspect ContactCenter server
Aspect ContactCenter serverPIM
Event linkBi-directionalTCP 5678Avaya ACD
CMS
TCP 6060–6070Avaya PIM
Connects to CTI server, listensfor VRU PIM
Bi-directionalVRUTCP 3000–3030MIS Process
Bi-directionalTCP 3000Avaya ACDAvaya AuraContact Center(AACC) PIM
Port number is configurableBi-directionalTCP 12028UCCE SystemPG
UCCEGateway PIM
For port utilization information about Network Interface Controllers (NICs), refer to the TCP/IP-based NICSystem Management Guide Supplements and setup parameters of the NIC or SCP connections.
Note
Table 7: Unified CCE Port Utilization: Windows Authentication and Remote Administration Ports
NotesTrafficDirection
RemoteProtocol andPort
Remote Device(Process orApplicationProtocol)
Listener Protocol and PortListener(Process orApplicationProtocol)
Bi-directionalTCP 135
UDP 135
RPC
Bi-directionalTCP 139NetBIOSSession
Bi-directionalTCP 137
UDP 137
NetBIOSNameResolution
Bi-directionalUDP 138NetBIOSNetlogon/Browsing
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)19
Port Utilization in Contact Center EnterpriseUnified CCE and Packaged CCE Port Utilization
NotesTrafficDirection
RemoteProtocol andPort
Remote Device(Process orApplicationProtocol)
Listener Protocol and PortListener(Process orApplicationProtocol)
Bi-directionalTCP 445
UDP 4452SMB
Bi-directionalTCP 389
UDP 389
LDAP
Bi-directionalTCP 636LDAP SSL
Bi-directionalTCP 3268LDAP GC
Bi-directionalTCP 3269LDAPGCSSL
Bi-directionalTCP 53
UDP 53
DNS
Bi-directionalTCP 88
UDP 88
Kerberos
See Q287932Bi-directionalTCP 1433
UDP 1434
SQL Server
2 DB Worker uses UDP 445. This port is also used for named pipes connectivity.
For more information on Windows authentication, see Service overview and network port requirements forthe Windows Server system (Microsoft knowledge base article Q832017).
Note
Table 8: Unified CCE Port Utilization: Network Management and Remote Administration
NotesTrafficDirection
RemoteProtocol andPort
Remote Device(Process orApplicationProtocol)
Listener Protocol and PortListener(Process orApplicationProtocol)
Bi-directionalUDP 162SNMP–Trap
Bi-directionalUDP 514Syslog
Bi-directionalTCP 23Telnet
Bi-directionalTCP 3389RDP (TerminalServices)
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)20
Port Utilization in Contact Center EnterpriseUnified CCE and Packaged CCE Port Utilization
NotesTrafficDirection
RemoteProtocol andPort
Remote Device(Process orApplicationProtocol)
Listener Protocol and PortListener(Process orApplicationProtocol)
Bi-directionalTCP 5631
UDP 5632
pcAnywhere
RealVNCBi-directionalTCP 5900
TCP 5800 (Java HTTP)
VNC
Table 9: Unified CCE Port Utilization: Customer Interaction Analyzer
NotesTrafficDirection
RemoteProtocol andPort
Remote Device(Process orApplicationProtocol)
Listener Protocol and PortListener(Process orApplicationProtocol)
Bi-directionalCall recordingserver
TCP 3389VPN/terminalservices
Table 10: Unified CCE Port Utilization: Live Data
NotesTrafficDirection
RemoteProtocol andPort
Remote Device(Process orApplicationProtocol)
Listener Protocol and PortListener(Process orApplicationProtocol)
Public network Live DataEvents.
Bi-directionalCUIC/LiveData
Router A: 40034 + (instancenumber * 40)
Router B: 41034 + (instancenumber * 40)
Router (side Aand B) (TIPEvent)
Public network Live Data TestOther Side.
Bi-directionalCUIC/LiveData
Router A: 40035 + (instancenumber * 40)
Router B: 41035 + (instancenumber * 40)
Router (side Aand B) (TIPTOS)
Public network Live DataEvents.
Bi-directionalCUIC/LiveData
Side A: 42034 + (instancenumber * 40)
Side B: 43034 + (instancenumber * 40)
ICMPG1 (sideA and B) (TIPEvent) 3
Public network Live DataEvents.
Bi-directionalCUIC/LiveData
Side A: 44034 + (instancenumber * 40)
Side B: 45034 + (instancenumber * 40)
ICMPG2 (sideA and B) (TIPEvent)
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)21
Port Utilization in Contact Center EnterpriseUnified CCE and Packaged CCE Port Utilization
NotesTrafficDirection
RemoteProtocol andPort
Remote Device(Process orApplicationProtocol)
Listener Protocol and PortListener(Process orApplicationProtocol)
Public network Live Data TestOther Side.
Bi-directionalCUIC/LiveData
Side A: 42035 + (instancenumber * 40)
Side B: 43035 + (instancenumber * 40)
ICMPG1 (sideA and B) (TIPTOS)
Public network Live Data TestOther Side.
Bi-directionalCUIC/LiveData
Side A: 44035 + (instancenumber * 40)
Side B: 45035 + (instancenumber * 40)
ICMPG2 (sideA and B) (TIPTOS)
Bi-directionalSocket.IOCUIC/LiveData
TCP 12007Socket.IOunsecured port
Bi-directionalSocket.IOCUIC/LiveData
TCP 12008Socket.IOsecured port
Live Data Cassandra TCP portfor commands and data
Bi-directionalTCP 12000CCELiveDataCassandraService
Live Data Cassandra SSL portfor encrypted communication.(Unused unless enabled inencryption_options.)
Bi-directionalTCP 12001CCELiveDataCassandraService
Live Data Cassandra port thatThrift uses to listen to clients
Bi-directionalTCP 9160CCELiveDataCassandraService
Live Data DRPC portBi-directionalTCP 3772CCELiveDataStorm DRPCService
LiveDataDRPC invocation portBi-directionalTCP 3773CCELiveDataStorm DRPCService
Live Data ReportingBi-directionalTCP 2181CCELiveDataZookeeperService
Live Data ReportingBi-directionalTCP 12004–12006CCELiveDataWeb Service
Live Data Nimbus Thrift portBi-directionalTCP 6627CCELiveDataStorm NimbusService
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)22
Port Utilization in Contact Center EnterpriseUnified CCE and Packaged CCE Port Utilization
NotesTrafficDirection
RemoteProtocol andPort
Remote Device(Process orApplicationProtocol)
Listener Protocol and PortListener(Process orApplicationProtocol)
LiveDataActiveMQOpenWiretransport Connector port
Bi-directionalTCP 61616CCELiveDataActive MQService
Live Data Active MQ Stomptransport connector port
Bi-directionalTCP 61612CCELiveDataActive MQService
HTTP - Unified IntelligenceCenter
Bi-directionalTCP 8081UnifiedIntelligenceCenter
3 The ports for TIP/TOS connections are assigned based on the order in which the PG pair (side A/B) is installed on the sameserver. For example, the first PG pair (PG1 Side A/B) installed, is assigned TIP base ports 42034 and 43034 respectively. Thesecond PG pair (PG2 Side A/B) installed, is assigned ports 44034 and 45034 respectively. The same assignment is applicableto TOS ports as well.
Cloud Connect Port Utilization
Table 11: Cisco Unified Web Proxy
NotesTrafficDirection
RemoteProtocol andPort
Remote Device (Process orApplication Protocol)
ListenerProtocol andPort
Listener(Process orApplicationProtocol)
Cloud Connect services use thisport for HTTPS connections.
Inward fromapplications toCloudConnectServices.
—ApplicationsTCP 8445Cisco UnifiedWeb ProxyService(HTTPS)
Table 12: Cloud Connect Services
NotesTrafficDirection
RemoteProtocol andPort
Remote Device (Process orApplication Protocol)
ListenerProtocol andPort
Listener(Process orApplicationProtocol)
Services use this port for securecluster management.
Bidirectional(between twonodes in thesame cluster)
Dataconn Service on the othernode in the same cluster.
TCP 2551DataconnService
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)23
Port Utilization in Contact Center EnterpriseCloud Connect Port Utilization
NotesTrafficDirection
RemoteProtocol andPort
Remote Device (Process orApplication Protocol)
ListenerProtocol andPort
Listener(Process orApplicationProtocol)
CherryPoint services use thisport for secure clustermanagement.
BidirectionalCherryPoint Service on theother node in the same cluster.
TCP 3551CherryPointService
EvaPoint services use this portfor secure cluster management.
BidirectionalEvaPoint Service on the othernode is the same cluster.
TCP 4551EvaPointService
Unified CCMP Port UtilizationTable 13: Cisco Unified Contact Center Management Portal Port Utilization
NotesTrafficDirection
Remote Device(Process orApplicationProtocol)
Remote Protocol and PortListenerProtocol andPort
Listener(Process orApplicationProtocol)
CCMP Web/Application server A
Standard SQL connectionCCMP DB server A/BTCP 1433SQL
Used to read AD accountinformation for supervisorprovisioning
UDP 389Domain ControllerTCP 389LDAP
CCMP Web/Application server B
Standard SQL connectionCCMP DB server A/BTCP 1433SQL
Used to read AD accountinformation for supervisorprovisioning
UDP 389Domain ControllerTCP 389LDAP
CCMP Database server A
For SQL replicationCCMP DB server BTCP 1433SQL
For import of CCE/CCHdimension data
CCE/CCH Administration andData server side A
TCP 1433
For import of CCE/CCHdimension data
CCE/CCH Administration andData server side B
TCP 1433
For the CCMP audit archive jobTCP1024-5000
CCMP DB sever BTCP 135*MSDTC
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)24
Port Utilization in Contact Center EnterpriseUnified CCMP Port Utilization
NotesTrafficDirection
Remote Device(Process orApplicationProtocol)
Remote Protocol and PortListenerProtocol andPort
Listener(Process orApplicationProtocol)
For CVP file upload filereplication
TCP 445UDP 445*SMB over IP
* Also used for named pipes connectivity.
CCMP Database server B
For SQL replicationCCMP DB server ATCP 1433SQL
For import of CCE/CCHdimension data
CCE/CCH Administration &Data sever side A
TCP 1433
For import of CCE/CCHdimension data
CCE/CCH Administration &Data sever side B
TCP 1433
For the CCMP audit archive jobTCP1024-5000
CCMP DB sever ATCP 135*MSDTC
For CVP file upload filereplication
TCP 445UDP 445*SMB over IP
These assume all server names are either TCP/IP addresses or DNS names (hence no NETBIOS portrequirements).
Ports are also required to access all Unified Contact Center Management Portal servers for support reasons(either pcAnywhere or terminal services).
This list does not include standard Windows ports such as DNS and Kerberos.Note
* MSDTC response ports by default use a dynamically allocated port in the range of 1024 to 5000. You canconfigure this range creating the HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\Internet locationregistry key and adding the following registry values:
• Ports (REG_MULTI_SZ) - specify one port range per line, for example, 3000-3005
• PortsInternetAvailable (REG_SZ) - always set this value to "Y" (do not include the quotes)
• UseInternetPorts (REG_SZ) - always set this value to "Y" (do not include the quotes)
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)25
Port Utilization in Contact Center EnterpriseUnified CCMP Port Utilization
Unified CRM Connectors Port UtilizationTable 14: Cisco Unified CRM Connector for SAP
NotesTrafficDirection
RemoteProtocol andPort
Remote Device (Process orApplication Protocol)
ListenerProtocol andPort
Listener(Process orApplicationProtocol)
CRM Connector for SAPTCP 42029CRMDataStore forSAP
Table 15: Cisco Unified CRM Connector for Microsoft CRM, Oracle PeopleSoft, Salesforce.com
NotesTrafficDirection
RemoteProtocol andPort
Remote Device (Process orApplication Protocol)
ListenerProtocol andPort
Listener(Process orApplicationProtocol)
MSCRM only.MSCRM ClientTCP 81MSCRMServer
Configurable in \ProgramFiles\Cisco\CRMConnector\MCIS\Config.ini
CRM AdaptersTCP 5666CRMConnectorServer
Remoting Port.Agent DesktopTCP 5558.NET Adapter
Default port for side A.Configurable in the Config.inifile [CTIModule Setting]Port_A.
Cisco CTI ServerTCP 42027CRMConnectorServer
Default port for side B.Configurable in the Config.inifile [CTIModule Setting]Port_B.
Cisco CTI ServerTCP 44027CRMConnectorServer
Configurable under \ProgramFiles\Cisco\CRMConnector\MCIS\Config.ini and\Program Files\Cisco\CRMConnector\ ServerAdministrationTool\WebComponent\server.config
Server Administration ToolTCP 65372CRMConnectorServer
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)26
Port Utilization in Contact Center EnterpriseUnified CRM Connectors Port Utilization
C H A P T E R 3Port Utilization in CVP
• Port Utilization Table Columns, on page 27• Unified CVP Port Utilization, on page 28
Port Utilization Table ColumnsThe 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 applicationprotocol.
Listener Protocol and Port
An identifier for the TCP or UDP port that the server or application is listening on, along with the IPaddress 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 withthe IP address for incoming connection requests when acting as the server.
Traffic Direction
The direction that traffic flows through the port: Inbound, Bidirectional, Outbound.
The operating system dynamically assigns the source port that the local application or service uses to connectto the destination port of a remote device. In most cases, this port is assigned randomly above TCP/UDP 1024.
Note
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)27
Unified CVP Port UtilizationTable 16: Cisco Unified Customer Voice Portal Port Utilization
NotesTraffic DirectionRemoteProtocoland Port
RemoteDevice(Process orApplicationProtocol)
Listener Protocol and PortListener(Process orApplicationProtocol)
Sub to phoneBi-directional2000-2002TCP
JMX access byJConsole into CallServer
Bi-directionalRandomJConsole2098Call Server JMX
JMX access byJConsole into CallServer
Bi-directionalRandomJConsole2097Call Server JMXRMI port
JMX access byJConsole into WSM
Bi-directionalRandomJConsoleTCP 10002WSM JMX
JMX access byJConsole into WSM
Bi-directionalRandomJConsoleTCP 10003WSMJMXRMI
JMX access byJConsole into OAMP
Bi-directionalRandomJConsoleTCP 10001OAMP JMX
JMX access byJConsole into OAMP
Bi-directionalRandomJConsoleTCP 10000OAMP JMXRMI
CVP Message Buscommunications
Bi-directionalCVPSubsystem
TCP 23000 - 28000 (Firstavailable)
CVP MessagingLayer
Cisco 7960-CUVAVideo Phone
7960-CUVAUDP 54457960-CUVAVideo
Listen port forincoming SIP requests.Port is configurable.
Bi-directionalLocal /RemotebetweenCVPcomponents
SIPendpoints
UDP 5060
TCP 5060
TLS 5061
CVP SIPSubsystem, SIPProxy Server,Gateway,UnifiedCM: SIP(SessionInitiationProtocol)
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)28
Port Utilization in CVPUnified CVP Port Utilization
NotesTraffic DirectionRemoteProtocoland Port
RemoteDevice(Process orApplicationProtocol)
Listener Protocol and PortListener(Process orApplicationProtocol)
Listen port forincoming Heartbeat.
Bi-directionalRandomSIPendpoints
UDP 5067
TCP 5067
This port must bedifferent from thedefault SIP port whichis 5060/5061 (seeaforementioned row).
Note
SIP HeartbeatLocal ListenPort
VXML over HTTP.Calls/sessionsanswered on port 7000by HTTP server whichrelays request to WASon local system port9080.
Bi-directionalRandomIOS VXMLgateways/VVB
TCP 7000VXML Server:HTTP
VXML over HTTPS.Calls/sessionsanswered on port 7443by HTTPS server.
Bi-directionalRandomIOS VXMLgateways/VVB
TCP 7443VXML Server:HTTPS
Port restricted to localaccess only
LocalLocalmachine
TCP 7005VXML Serverwith Tomcat
AJP/1.3 ConnectorLocalTCP 7009
JMX access byJConsole into VXMLServer
Bi-directionalJConsoleTCP 9696VXML ServerJMX
JMX access byJConsole into VXMLServer
Bi-directionalRandomJConsoleTCP 9697VXML ServerJMX RMI port
Port restricted to localaccess only
LocalLocalVXMLServerAdministrationScripts
TCP 10100VXML Server
HTTPBi-directionalRandomBrowserTCP 8000CVPCall ServerTomcat: HTTP
HTTPSBi-directionalLocal /RemoteRandom
BrowserTCP 8443CVPCall ServerTomcat: HTTPS
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)29
Port Utilization in CVPUnified CVP Port Utilization
NotesTraffic DirectionRemoteProtocoland Port
RemoteDevice(Process orApplicationProtocol)
Listener Protocol and PortListener(Process orApplicationProtocol)
Message over TCPLocalVXMLServer
TCP 8002CVP IVRServer
Port restricted to localaccess only
LocalTCP 8005CVP CallServer: HTTP
Web-based interfacefor configuring CVPcomponents
Bi-directionalRandomWebBrowser
TCP 9000CVPOPSConsole:HTTP
Web based interfacefor configuring CVPcomponents with SSL
Bi-directionalRandomWebBrowser
TCP 9443CVPOPSConsole:HTTPS
Port restricted to localaccess only
LocalLocalmachine
TCP 9005CVPOPSConsole
AJP/1.3 ConnectorLocalTCP 9009CVPOPSConsole
Port restricted to localaccess only
LocalLocalmachine
TCP 1529CVPOPSConsole
Only opened byResource Managerresiding on the samemachine as the CVPOPSConsole
Bi-directionalRandomContentServicesSwitch
TCP 21CVP ResourceManager FTPServer
JMX communicationfrom OPSConsole toCVP ResourceManager on remotedevice
Bi-directionalRandomCVPOPSConsole
TCP 2099CVP ResourceManager
JMX communicationfrom OPSConsole toCVP ResourceManager on remotedevice
Bi-directionalRandomCVPOPSConsole
TCP 3000CVP ResourceManager RMIPort
CVP ResourceManager ServiceWrapper will no longeraccept connectionsafter the first JVMinstance is connected.
LocalRandomJVMinstancelaunched bywrapper
TCP 32000 - 32999 (firstavailable)
CVP ResourceManager JavaServiceWrapper
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)30
Port Utilization in CVPUnified CVP Port Utilization
NotesTraffic DirectionRemoteProtocoland Port
RemoteDevice(Process orApplicationProtocol)
Listener Protocol and PortListener(Process orApplicationProtocol)
MRCP session betweengateway voice browserandMRCP server. Thisis the signaling path;the media path usesRTP.
Also, Helix streamingaudio/ ASR/TTS(MRCP/RTSP)
VXMLgateway
TCP 554MRCP V1(RTSP)
MRCP session betweengateway voice browserandMRCP server. Thisis the signaling path;the media path usesRTP.
VXMLgateway
TCP 5060MCRP V2 (SIP)
CVP SNMP SubAgentservices local requestsfrom CVP SNMPsubsystem
LocalCVP SNMPsubsystem
UDP 5517, 5519, 5521, 5523,5525, 5527, 5529, 5531, 5533,5535, 5537, 5539, 5541, 5543,5545, 5547, 5549, 5551, 5553,5555
CVP SNMPSubAgent
CVPSNMP subsystemservices local requestsfrom CVP SNMPSubAgent
LocalCVP SNMPSubAgent
UDP 5516, 5518, 5520, 5522,5524, 5526, 5528, 5530, 5532,5534, 5536, 5538, 5540, 5542,5544, 5546, 5548, 5550, 5552,5554
CVP SNMPsubsystem
Between CVP ICMSubsystem (CallServer) and UnifiedCCE/ICM VRU PG.Port is configurable.
Bi-directionalRandomIPCCEnterpriseVRU CTI(ICM/IVRmessageinterface)
TCP 5000CVP ICMSubsystem
Voice browsers fetchesmedia and "ExternalVXML" files frommedia server.
This port isconfigurable.
Bi- directionalRandomVoiceBrowsers
TCP 80Web Server:HTTP
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)31
Port Utilization in CVPUnified CVP Port Utilization
NotesTraffic DirectionRemoteProtocoland Port
RemoteDevice(Process orApplicationProtocol)
Listener Protocol and PortListener(Process orApplicationProtocol)
Voice browsers fetchesmedia and "ExternalVXML" files frommedia server.
This port isconfigurable.
Bi- directionalRandomVoiceBrowsers
TCP 443Web Server:HTTPS
Database ConnectionBi-directionalRandomfromCUIC
CVPReportingSubsystem
TCP 1526IBM Informix
IBM Informix StorageManager Services
LocalTCP 7939 - 7942 TCP 111IBM InformixStorageManager
Bi-directionalRandomforremotedesktop
TCP 9043, 9060IBM WASConsole
REST Web Services
TCP 10000, 10001,10002, 10003 OAMPports are used fortransferring datarelated to theconfiguration andadministration ofVXMLServer andCallServer.
Bi-directionalRandomUnifiedSystem CLI,DiagnosticPortal,CustomAgentDesktop
TCP 8101, 8110, 8111
TCP 10000, 10001, 10002,10003
CVP WebServicesManager:HTTP/HTTPS
Table 17: Network Management and Remote Administration
NotesTrafficDirection
RemoteProtocol andPort
Remote Device (Process orApplication Protocol)
ListenerProtocol andPort
Listener(Process orApplicationProtocol)
SNMPPrimaryAgent listens forTCP connections from localSNMP subagents.
LocalLocal SNMP subagentsTCP 7161SNMPPrimaryAgent
SNMP Primary Agent sendsSNMP traps to SNMPmanagement application.
Bi-directionalRandomSNMP Primary AgentUDP 162SNMP–Trap
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)32
Port Utilization in CVPUnified CVP Port Utilization
NotesTrafficDirection
RemoteProtocol andPort
Remote Device (Process orApplication Protocol)
ListenerProtocol andPort
Listener(Process orApplicationProtocol)
Syslog protocol provides atransport to allow a machine tosend event notificationmessagesacross IP network to eventmessage collectors. Port isconfigurable.
Bi-directionalRandomUDP 514Syslog
TCP 23Telnet
Bi-directionalRandomTCP 3389RDP (TerminalServices)
TCP 5631
UDP 5632
pcAnywhere
TCP 5900
TCP 5800
VNC
Table 18: Windows Authentication and Remote Administration Ports
NotesTrafficDirection
RemoteProtocol andPort
Remote Device (Process orApplication Protocol)
ListenerProtocol andPort
Listener(Process orApplicationProtocol)
TCP 135RPC
TCP 139NetBIOSSession
TCP 137
UDP 137
NetBIOSNameResolution
UDP 138NetBIOSNetlogon/Browsing
Microsoft CIFSTCP 445
UDP 445
SMB
TCP 53
UDP 53
DNS
TCP Optima VNETTCP 1051optima-vnet
UDP Optima VNETUDP 1051optima-vnet
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)33
Port Utilization in CVPUnified CVP Port Utilization
• Ephemeral loopback client ports may be opened locally for CVP services to talk to port 1529 forcommunications with Derby database.
• Similarly, ephemeral loopback client/server ports may be opened locally by CVP services for internalcalls.
• Ephemeral loopback client ports may also be opened by local subagents for talking to the SNMP primaryagent running on port 7161.
The above ports are closed when the services concerned are shut down.
From a security perspective, it is recommended to review the ports opened by the underlying Windowsoperating system or other services running on a machine and close all ports except those required for normalsystem operation.
Note
For more information on Windows authentication and remote administration ports, see Service overview andnetwork port requirements for the Windows Server system (Microsoft Knowledge Base Article Q832017) athttps://support.microsoft.com/en-us/help/832017/service-overview-and-network-port-requirements-for-windows.
Note
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)34
Port Utilization in CVPUnified CVP Port Utilization
C H A P T E R 4Port Utilization in Cisco VVB
• Port Utilization Table Columns, on page 35• Cisco VVB Port Utilization, on page 36
Port Utilization Table ColumnsThe 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 applicationprotocol.
Listener Protocol and Port
An identifier for the TCP or UDP port that the server or application is listening on, along with the IPaddress 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 withthe IP address for incoming connection requests when acting as the server.
Traffic Direction
The direction that traffic flows through the port: Inbound, Bidirectional, Outbound.
The operating system dynamically assigns the source port that the local application or service uses to connectto the destination port of a remote device. In most cases, this port is assigned randomly above TCP/UDP 1024.
Note
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)35
Cisco VVB Port UtilizationTable 19: Cisco VVB Port Utilization
NotesTrafficDirection
RemoteProtocoland Port
Remote Device (Processor Application Protocol)
ListenerProtocoland Port
Listener(Process orApplicationProtocol)
Cisco VVB database portBidirectional—External process such asExternal DB clients (likeSquirrel or others forcustom reporting) canconnect
TCP 1504VBONINIT
Communicates with SIPgateway
Bidirectional—SIPSIP overTCP, SIPover UDP5060
VVB_Engine
Communicates with SIPgateway
Bidirectional—SIPSIP overTLS 5061
VVB_Engine
Publishes JMS eventsacross JMS networkconnectors in the cluster
Bidirectional6161InternalTCP 6161VVB_CVD
Bootstrap HTTPD serviceport
Bidirectional—CVD of other node incluster
TCP 6295CVD
RMI PortBidirectional—Engine, Tomcat, CVD,and Editor
TCP 6999VVB_CVD
- Clients trying to accessHTTP triggers,documents, prompts, orgrammars
- Tomcat instance used byCisco VVB engine
Bidirectional——TCP 9080VVB_Engine
- Audio media streaming.
- Kernel streaming devicedriver
Bidirectional——UDP 24576~ 32767
Cisco IPVoiceMediaStreamingapplication
Generic ephemeral TCPand UDP ports
Bidirectional——TCP, UDP32768 ~61000
GenericPorts
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)36
Port Utilization in Cisco VVBCisco VVB Port Utilization
SIP signalling is possible over TCP or TLS. For RTP, underlying protocol is UDP always (not configurable).If TLS is used for SIP signalling, then the same exchanged keys will be used to encrypt and decrypt the RTPpackets - for SRTP
Note
To view the system services for port utilization for Cisco Virtualized Voice Browser, see System ServicesPort Utilization, on page 2
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)37
Port Utilization in Cisco VVBCisco VVB Port Utilization
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)38
Port Utilization in Cisco VVBCisco VVB Port Utilization
C H A P T E R 5Port Utilization in Finesse
• Port Utilization Table Columns, on page 39• Finesse Port Utilization, on page 40
Port Utilization Table ColumnsThe 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 applicationprotocol.
Listener Protocol and Port
An identifier for the TCP or UDP port that the server or application is listening on, along with the IPaddress 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 withthe IP address for incoming connection requests when acting as the server.
Traffic Direction
The direction that traffic flows through the port: Inbound, Bidirectional, Outbound.
• The operating system dynamically assigns the source port that the local application or service uses toconnect to the destination port of a remote device. In most cases, this port is assigned randomly aboveTCP/UDP 1024.
• For security reasons, keep open only the ports mentioned in this guide and those required by yourapplication. Keep the rest of the ports blocked.
Note
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)39
Finesse Port UtilizationTable 20: Cisco Finesse Server
NotesTrafficDirection
RemoteProtocol andPort
Remote Device (Process orApplication Protocol)
ListenerProtocol andPort
Listener(Process orApplicationProtocol)
Secure port used for Finesseadministration console, Finesseagent and supervisor desktop,Finesse Desktop Modules(gadgets) with the Finessedesktop and Finesse IP PhoneAgent.
Secure port used tocommunicate between UnifiedCCX Publisher and Subscriberfor synchronizingconfigurations.
Bidirectional—Browser and third-party RESTclients
TCP 443, 8445Cisco UnifiedWeb ProxyService(HTTPS)
Finesse desktop uses specific ports for communication between Finesse servers for intra-cluster traffic. Forthe complete list of the ports that are used, see System Services Port Utilization.
Note
Table 21: Cisco Finesse Notification Service
NotesTrafficDirection
RemoteProtocol andPort
Remote Device (Process orApplication Protocol)
ListenerProtocol andPort
Listener(Process orApplicationProtocol)
Secure XMPP connectionbetween the Finesse server andcustom third-party applications.
Secure XMPP connectionbetweenUnified CCXPublisherand Subscriber.
Bidirectional—Browser and agent desktopTCP 5223XMPP
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)40
Port Utilization in FinesseFinesse Port Utilization
NotesTrafficDirection
RemoteProtocol andPort
Remote Device (Process orApplication Protocol)
ListenerProtocol andPort
Listener(Process orApplicationProtocol)
Unsecured BOSH connectionbetween the Finesse server andagent and supervisor desktopsfor communication over HTTP.
From Cisco Finesse Release12.5(1) onwards, this port isdisabled by default. Use the CLIcommand utils finesseset_property webservicesenableInsecureOpenfirePorttrue to enable this port.
For more information on theCLI commands, see ServiceProperties section in CiscoFinesse AdministrationGuideCisco Unified ContactCenter Express Administrationand Operations Guide athttps://www.cisco.com/c/en/us/support/customer-collaboration/finesse/products-maintenance-guides-list.htmlhttps://www.cisco.com/c/en/us/support/customer-collaboration/unified-contact-center-express/products-maintenance-guides-list.html.
Bidirectional—Browser and agent desktopTCP 7071BOSH (HTTP)
Secure BOSH connectionbetween the Finesse server andagent and supervisor desktopsfor communication overHTTPS.
Bidirectional—Browser and agent desktopTCP 7443BOSH(HTTPS)
• A network connection is required to open between the Finesse Server and the ECE Web server.
• Finesse desktop uses specific ports on CUIC and Live Data to render Live Data gadgets and reports. Forthe complete list of the ports that can be used, see Unified Intelligence Center Port Utilization.
Note
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)41
Port Utilization in FinesseFinesse Port Utilization
Table 22: Primary and Secondary Node Communication
NotesTrafficDirection
RemoteProtocol andPort
Remote Device (Process orApplication Protocol)
ListenerProtocol andPort
Listener(Process orApplicationProtocol)
The primary and secondaryFinesse servers use this XMPPconnection to communicatewitheach other to monitorconnectivity.
From Cisco Finesse Release12.5(1) onwards, this port isdisabled by default. Use the CLIcommand utils finesseset_property webservicesenableInsecureOpenfirePorttrue to enable this port.
For more information on theCLI commands, see ServiceProperties section in CiscoFinesse AdministrationGuideCisco Unified ContactCenter Express Administrationand Operations Guide athttps://www.cisco.com/c/en/us/support/customer-collaboration/finesse/products-maintenance-guides-list.htmlhttps://www.cisco.com/c/en/us/support/customer-collaboration/unified-contact-center-express/products-maintenance-guides-list.html.
Bidirectional——TCP 5222XMPP
Third-Party (External) Web Server
Gadgets hosted on a third-party (external) web server are fetched through the Finesse server on the portexposed by said web server.
Note
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)42
Port Utilization in FinesseFinesse Port Utilization
Table 23: Unified Contact Center Enterprise
NotesTrafficDirection
RemoteProtocol andPort
Remote Device (Process orApplication Protocol)
ListenerProtocol andPort
Listener(Process orApplicationProtocol)
Administration & Data Server settings
Connection to the AWDB forauthentication and authorizationof agents and supervisors
BidirectionalTCP 14331——JDBC (SQL)
CTI Server settings (Side A and B)
Connection to the Agent PG forCTI Server events (such asAgents, Teams, Queues, andCall events)
BidirectionalSide A:
TCP 420271
Side B:
TCP 430271
——GED-188
1The ports listed are the default ports for these connections. You can use different ports than the ones specifiedin this table.
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)43
Port Utilization in FinesseFinesse Port Utilization
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)44
Port Utilization in FinesseFinesse Port Utilization
C H A P T E R 6Port Utilization in Customer CollaborationPlatform
• Port Utilization Table Columns, on page 45• Customer Collaboration Platform Port Utilization, on page 46
Port Utilization Table ColumnsThe 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 applicationprotocol.
Listener Protocol and Port
An identifier for the TCP or UDP port that the server or application is listening on, along with the IPaddress 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 withthe IP address for incoming connection requests when acting as the server.
Traffic Direction
The direction that traffic flows through the port: Inbound, Bidirectional, Outbound.
• The operating system dynamically assigns the source port that the local application or service uses toconnect to the destination port of a remote device. In most cases, this port is assigned randomly aboveTCP/UDP 1024.
• For security reasons, keep open only the ports mentioned in this guide and those required by yourapplication. Keep the rest of the ports blocked.
Note
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)45
Customer Collaboration Platform Port UtilizationTable 24: Customer Collaboration Platform Port Utilization
NotesTrafficDirection
RemoteProtocol andPort
Remote Device (Process orApplication Protocol)
ListenerProtocol andPort
Listener(Process orApplicationProtocol)
Used for unsecure (HTTP)traffic:
• From the CustomerCollaboration Platformuser interface (browser) orAPIs to the CustomerCollaboration Platformserver.
• From the CustomerCollaboration Platformserver to the internet.Customer CollaborationPlatform communicatesoutward to the internet tofetch social contactinformation (such asFacebook posts and tweets)over HTTP.
• From the internet orcorporate website to theCustomer CollaborationPlatform server. CustomerCollaboration Platformreceives incoming chat andcallback requests from theinternet or corporatewebsite over HTTP.
BidirectionalPort 80HTTP
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)46
Port Utilization in Customer Collaboration PlatformCustomer Collaboration Platform Port Utilization
NotesTrafficDirection
RemoteProtocol andPort
Remote Device (Process orApplication Protocol)
ListenerProtocol andPort
Listener(Process orApplicationProtocol)
Used for secure (HTTPS)traffic:
• From the CustomerCollaboration Platformuser interface (browser) orAPIs to the CustomerCollaboration Platformserver.
• From the CustomerCollaboration Platformserver to the internet.Customer CollaborationPlatform communicatesoutward to the internet tofetch social contactinformation (such asFacebook posts and tweets)over HTTPS.
• From the internet orcorporate website to theCustomer CollaborationPlatform server. CustomerCollaboration Platformreceives incoming chat andcallback requests from theinternet or corporatewebsite over HTTPS.
BidirectionalPort 443HTTPS
Customer CollaborationPlatform communicates with theconfigured XMPPNotificationsserver (that can be in thecorporate intranet or on theinternet) to send XMPP (IM)notifications.
Outward, fromCustomerCollaborationPlatform to theconfiguredXMPPNotificationsserver.
Port 5222(configurable)
XMPP (IM)notificationsusing anexternalXMPPserver
The unsecure BOSH connectionsupports eventing and chatcommunication between theCustomer CollaborationPlatform user interface and theCustomer CollaborationPlatform server.
BidirectionalPort 7071Eventing andchat (BOSH)
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)47
Port Utilization in Customer Collaboration PlatformCustomer Collaboration Platform Port Utilization
NotesTrafficDirection
RemoteProtocol andPort
Remote Device (Process orApplication Protocol)
ListenerProtocol andPort
Listener(Process orApplicationProtocol)
The secure BOSH connectionsupports eventing and chatcommunication between theCustomer CollaborationPlatform user interface and theCustomer CollaborationPlatform server.
BidirectionalPort 7443 isused for secureBOSHconnections tothe XMPPeventingserver.
Eventing andchat (secureBOSH)
The CCE Media RoutingPeripheral Gateway (MR PG)communicates over a socketconnection to CustomerCollaboration Platform tosupport the media routingconnection.
Inward, fromthe CCE MRPG to theCustomerCollaborationPlatformserver.
Port 38001(configurable)
Media routing(in CCEdeployments)
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)48
Port Utilization in Customer Collaboration PlatformCustomer Collaboration Platform Port Utilization
C H A P T E R 7Port Utilization in Unified Intelligence Center
• Port Utilization Table Columns, on page 49• Unified Intelligence Center Port Utilization, on page 50
Port Utilization Table ColumnsThe 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 applicationprotocol.
Listener Protocol and Port
An identifier for the TCP or UDP port that the server or application is listening on, along with the IPaddress 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 withthe IP address for incoming connection requests when acting as the server.
Traffic Direction
The direction that traffic flows through the port: Inbound, Bidirectional, Outbound.
• The operating system dynamically assigns the source port that the local application or service uses toconnect to the destination port of a remote device. In most cases, this port is assigned randomly aboveTCP/UDP 1024.
• For security reasons, keep open only the ports mentioned in this guide and those required by yourapplication. Keep the rest of the ports blocked.
Note
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)49
Unified Intelligence Center Port UtilizationTable 25: Web Requests to Cisco Unified Intelligence Center and Operation Administration Maintenance and Provisioning (OAMP)
NotesTrafficDirection
RemoteProtocol andPort
Remote Device (Process orApplication Protocol)
ListenerProtocol andPort
Listener(Process orApplicationProtocol)
HTTP - Unified IntelligenceCenter
BrowserTCP 8081UnifiedIntelligenceCenter
HTTPS - Unified IntelligenceCenter
BrowserTCP 8444
HTTPS - Unified IntelligenceCenter - Online Help
BrowserTCP 8447
HTTP - OAMPBrowserTCP 8080OAMP
HTTPS - OAMPBrowserTCP 8443
Table 26: Cisco Unified Intelligence Center and Live Data
NotesTrafficDirection
RemoteProtocol andPort
Remote Device (Process orApplication Protocol)
ListenerProtocol andPort
Listener(Process orApplicationProtocol)
Live Data DRPC portTCP 3772Storm DRPCservice
LiveDataDRPC invocation portTCP 3773Storm DRPCservice
Live Data Cassandra TCP portfor commands and data
TCP 12000CCELiveDataCassandraService
Live Data Cassandra SSL portfor encrypted communication.(Unused unless enabled inencryption_options.)
TCP 12001CCELiveDataCassandraService
Live Data Cassandra port thatThrift uses to listen to clients
TCP 9160CCELiveDataCassandraService
Live Data ReportingTCP 2181CCELiveDataZookeeperService
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)50
Port Utilization in Unified Intelligence CenterUnified Intelligence Center Port Utilization
NotesTrafficDirection
RemoteProtocol andPort
Remote Device (Process orApplication Protocol)
ListenerProtocol andPort
Listener(Process orApplicationProtocol)
ActiveMQ JMX connector portTCP 12002CCELiveDataActiveMQService
ActiveMQ JMX rmi portTCP 12003CCELiveDataActiveMQService
Live Data ReportingBrowserTCP 12004 -12005
CCELiveDataWeb Service
Live Data ActiveMQOpenwiretransport Connector port
TCP 61616CCELiveDataActive MQService
Live Data ActiveMQ Stomptransport connector port
TCP 61612CCELiveDataActive MQService
Live Data Nimbus Thrift portTCP 6627CCELiveDataStorm NimbusService
Live Data Socket.IO listeningport
BrowserTCP 12007 -12008
CCELiveDataSocket.IOService
Table 27: Intracluster Ports Between Cisco Unified Intelligence Center
NotesTrafficDirection
RemoteProtocol andPort
Remote Device (Process orApplication Protocol)
ListenerProtocol andPort
Listener(Process orApplicationProtocol)
Hazelcast DiscoveryUnified IntelligenceCenter nodeUDP 54327(Multicast)
CUICReportingProcess
HazelcastUnified Intelligence CenterNode
TCP 57011CUICReportingProcess
Cisco Unified Intelligence Center, which runs on the Cisco VOS operating system uses the following ports:TCP 5001, TCP 5002, and TCP 5003 for SOAP monitoring. For more information on these ports, see PortUtilization for System Services section.
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)51
Port Utilization in Unified Intelligence CenterUnified Intelligence Center Port Utilization
Formore information on other port usages, see: https://www.cisco.com/c/en/us/support/unified-communications/unified-communications-manager-callmanager/products-maintenance-guides-list.html
Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.5(1)52
Port Utilization in Unified Intelligence CenterUnified Intelligence Center Port Utilization