Unified CCE and Packaged CCE Port Utilization
This 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 so on.
![]() Note |
In the following table, PG1, PG2, and PG3 are not specific PG numbers or DMP IDs. They are the order in which the PGs get installed. |
![]() Note |
This document does not include the Enterprise Chat and Email (ECE) port details. For more information on ECE 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. |
Listener (Process or Application Protocol) |
Listener Protocol and Port |
Remote Device (Process or Application Protocol) |
Remote Port |
Traffic Direction |
Notes |
||
---|---|---|---|---|---|---|---|
Router (side B) (MDS) |
Private low:
Private medium:
Private high:
State Xfer for CIC:
State Xfer for HLGR:
State Xfer for RTR:
UDP 39500–39999 State Xfer for DBAgent:
|
Router (side A) (MDS) |
Bi-directional |
Private network at the central controller site
|
|||
Router (side B) (MDS) |
MDS process port TCP 41000 |
MDS process client |
Bi-directional |
||||
Router (side B) (MDS) |
MDS state transfer port TCP 41001 |
MDS process client (synchronized) |
Bi-directional |
||||
Router (side A and B) (DB Worker) |
DB Worker process port UDP 445 |
DB Worker process client |
Bi-directional |
||||
ICM PG1 (side A and B) (pgagent) |
TCP 43006 + (instance number * 40) |
ICM PG1 (Opposite Side: A or B) (pgagent) |
Bi-directional |
Public network (test-other-side) |
|||
ICM PG2 (side A and B) (pgagent) |
TCP 45006 + (instance number * 40) |
ICM PG2 (Opposite Side: A or B) (pgagent) |
Bi-directional |
Public network (test-other-side) |
|||
ICM PG3 (side A and B) (pgagent) |
TCP 47506 + (instance number * 40) |
ICM PG3 (Opposite Side: A or B) (pgagent) |
Bi-directional |
Public network (test-other-side) |
|||
ICM PG1 (side A and B) (MDS) |
UDP 39500–39999 |
ICM PG1 (Opposite Side: A or B) |
Bi-directional |
Private network
|
|||
ICM PG2 (side A and B) (MDS) |
UDP 39500–39999 |
ICM PG2 (Opposite Side: A or B) |
Bi-directional |
Private network
|
|||
ICM PG3 (side A and B) (MDS) |
UDP 39500–39999 |
ICM PG3 (Opposite Side: A or B) |
Bi-directional |
Private network
|
|||
ICM PG1 (side B) (MDS) |
MDS process port TCP 43000 |
MDS process client |
Bi-directional |
||||
ICM PG1 (side B) (MDS) |
MDS state transfer port TCP 43001 |
MDS process client (synchronized) |
Bi-directional |
||||
ICM PG2 (side B) (MDS) |
MDS process port TCP 45000 |
MDS process client |
Bi-directional |
||||
ICM PG2 (side B) (MDS) |
MDS state transfer port TCP 45001 |
MDS process client (synchronized) |
Bi-directional |
||||
ICM PG3 (side B) (MDS) |
MDS process port TCP 47500 |
MDS process client |
Bi-directional |
||||
ICM PG3 (side B) (MDS) |
MDS state transfer port TCP 47501 |
MDS process client (synchronized) |
Bi-directional |
||||
Router (side A) (MDS) |
Private low:
Private medium:
Private high:
State Xfer for CIC:
State Xfer for HLGR:
State Xfer for RTR:
UDP 39500–39999 State Xfer for DBAgent:
|
Router (side B) (MDS) |
Bi-directional |
Private network at the central controller site
|
|||
Router (side A) (MDS) |
MDS process port TCP 40000 |
MDS process client |
Bi-directional |
||||
Router (side A) (MDS) |
MDS state transfer port TCP 40001 |
MDS process client (synchronized) |
Bi-directional |
||||
ICM PG1 (side A) (MDS) |
MDS process port TCP 42000 |
MDS process client |
Bi-directional |
||||
ICM PG1 (side A) (MDS) |
MDS state transfer port TCP 42001 |
MDS process client (synchronized) |
Bi-directional |
||||
ICM PG2 (side A) (MDS) |
MDS process port TCP 44000 |
MDS process client |
Bi-directional |
||||
ICM PG2 (side A) (MDS) |
MDS state transfer port TCP 44001 |
MDS process client (synchronized) |
Bi-directional |
||||
ICM PG3 (side A) (MDS) |
MDS process port TCP 46000 |
MDS process client |
Bi-directional |
||||
ICM PG3 (side A) (MDS) |
MDS state transfer port TCP 46001 |
MDS process client (synchronized) |
Bi-directional |
||||
Router (side A) DMP (ccagent) |
UDP 39500–39999 |
ICM PG (pgagent) |
Bi-directional |
Public network connecting the PG to the central controller Router to pre-5.0 PG communication.
|
|||
Router (side B) DMP (ccagent) |
UDP 39500–39999 |
ICM PG (pgagent) |
Bi-directional |
Public network connecting the PG to the central controller Router to pre-5.0 PG communication.
|
|||
Router A (rtfeed) |
TCP 40007 + (instance number * 40) |
Administration & Data Server |
Bi-directional |
Real-time feed |
|||
Router B (rtfeed) |
TCP 41007 + (instance number * 40) |
Administration & Data Server |
Bi-directional |
Real-time feed |
|||
Logger (side A) |
TCP 40026 + (instance number * 40) TCP 40028 + (instance number * 40) |
Administration & Data Server Historical Data Server (HDS) |
Bi-directional |
Replication |
|||
Logger (side A) |
TCP 40032 + (instance number * 40) |
Dialer and Import |
Bi-directional |
Campaign Manager EMT port to Dialer |
|||
Logger (side B) |
TCP 41026 + (instance number * 40) TCP 41028 + (instance number * 40) |
Administration & Data Server Historical Data Server (HDS) |
Bi-directional |
Replication |
|||
Logger (side B) |
TCP 41036 + (instance number * 40) |
Dialer and Import |
Bi-directional |
Campaign Manager EMT port to Dialer |
|||
Primary Administration & Data Server (rtfeed) |
TCP 48008 + (instance number * 40) |
Administration client |
Bi-directional |
Real-time feed |
|||
Secondary Administration & Data Server (rtfeed) |
TCP 49008 + (instance number * 40) |
Administration client |
Bi-directional |
Real-time feed |
|||
Contact Sharing |
TCP 61616 |
Active MQ for Live Data |
TCP 61616 |
Bidirectional |
|||
CICM Router (side A) (INCRPNIC) |
UDP 40025 + (instance number * 40) |
NAM Router (CIC) |
Bi-directional |
Public network connecting the NAM to the CICM |
|||
CICM Router (side B) (INCRPNIC) |
UDP 41025 + (instance number * 40) |
NAM Router (CIC) |
Bi-directional |
Public network connecting the NAM to the CICM |
|||
CSFS |
TCP 40015 |
CSFS duplexed peer |
Bi-directional |
CSFS event synchronization link |
|||
Logger Recovery Process (side A) |
41013 + (instance number *40) |
Bi-directional |
|||||
Logger Recovery Process (side B) |
40013 + (instance number *40) |
Bi-directional |
|||||
Diagnostic framework |
TCP 7890 |
Any client that is requesting information from the diagnostic service. |
Bi-directional |
This serviceability component is installed on major CCE component servers (e.g. router, logger, PG, and Administration and Data Servers) |
Listener (Process or Application Protocol) |
Listener Protocol and Port |
Remote Device (Process or Application Protocol) |
Remote Port |
Traffic Direction |
Notes |
---|---|---|---|---|---|
MSSQL |
TCP 1433 |
Logger Distributor |
Bi-directional |
Listener (Process or Application Protocol) |
Listener Protocol and Port |
Remote Device (Process or Application Protocol) |
Remote Port |
Traffic Direction |
Notes |
---|---|---|---|---|---|
Dialer |
58800 + instNum instNum is the instance number for the Dialer. |
Voice Gateway |
UDP 58800 |
Bi-directional |
Set in the SIPDialerPortBaseNumber registry key. |
RTP for SIP |
UDP ports in a range based on these formulas:
You can set RTPPortRangeStart in the registry key: RTPPortRangeStart. |
Voice gateway |
Bi-directional |
Receive ports for reservation calls. Use the following registry key to select and configure UDP ports: RTPPortRangeStart |
|
MR PG |
TCP 38001+ (instance number) |
Dialer |
Bi-directional |
The MR PG connects to the SIP Dialer using this port. |
|
Dialer (SIP) |
5060 and "SIPDialerPortBaseNumber + instance number" |
Voice Gateway or SIP Proxy |
Bi-directional |
Set in the SIPServerPortNumber registry key. |
Listener (Process or Application Protocol) |
Listener Protocol and Port |
Remote Device (Process or Application Protocol) |
Remote Port |
Traffic Direction |
Notes |
---|---|---|---|---|---|
GED-188 (CTI Server) unsecured |
Side A TCP 42027 + (instance number * 40) Side B TCP 43027 + (instance number * 40) |
Finesse Cisco Outbound Dialer ARM Interface CTI OS Server |
Bi-directional |
CTI OS is only supported for TDM and System PG. |
|
GED-188 (CTI Server) secured |
Side A TCP 42030 + (instance number * 40) Side B TCP 43030 + (instance number * 40) |
Finesse Cisco Outbound Dialer ARM Interface CTI OS Server |
Bi-directional |
CTI OS is only supported for TDM and System PG. |
|
CTI OS Server |
TCP 42028 |
CTI OS Client CTI OS Server Peers CAD Desktop Cisco Sync Service |
Bi-directional |
Applicable to first CTI OS instance. Multi-instance CTI OS require a custom port be defined. | |
CTI OS Server |
TCP 42028 |
CTI OS Client CTI OS Server Peers Cisco Sync Service |
Bi-directional |
CTI OS is only supported for TDM and System PG. Applicable to first CTI OS instance. Multi-instance CTI OS require a custom port be defined. |
|
CTI OS Supervisor Desktop |
UDP 39200 |
CTI OS Client |
Bi-directional |
Desktop Silent Monitoring CTI OS Supervisor Desktop is only supported for System PG. |
|
CTI OS Silent Monitor Service |
TCP 42228 |
CTI OS Client |
Bi-directional |
CTI OS Silent Monitor Service is only supported for System PG. |
Listener (Process or Application Protocol) |
Listener Protocol and Port |
Remote Device (Process or Application Protocol) |
Remote Port |
Traffic Direction |
Notes |
||
---|---|---|---|---|---|---|---|
IP Process Communications |
|||||||
CTI/QBE |
TCP 2748 |
Bi-directional |
JTAPI |
||||
Customer Voice Portal — Call Server Cisco Unified IP-IVR |
PG, VRU PIM (GED-125) |
TCP 5000–5001 |
Bi-directional |
Unified ICM/IVR message interface, VRU PIM |
|||
CCE PG |
TCP 2789 |
Unified CM |
Bi-directional |
JTAPI application server |
|||
Media Routing process |
MR PIM |
TCP 38001 |
Bi-directional |
||||
TDM Process Communications
|
|||||||
Avaya ACD CMS |
TCP 6060–6070 |
Avaya PIM |
TCP 5678 |
Bi-directional |
Event link |
||
UCCE System PG / CTI Server |
TCP 42027 |
UCCE Gateway PIM |
Bi-directional |
Port number is configurable |
![]() Note |
For port utilization information about Network Interface Controllers (NICs), refer to the TCP/IP-based NIC System Management Guide Supplements and setup parameters of the NIC or SCP connections. |
Listener (Process or Application Protocol) |
Listener Protocol and Port |
Remote Device (Process or Application Protocol) |
Remote Port |
Traffic Direction |
Notes |
---|---|---|---|---|---|
RPC |
TCP 135 UDP 135 |
Bi-directional |
|||
NetBIOS Session |
TCP 139 |
Bi-directional |
|||
NetBIOS Name Resolution |
TCP 137 UDP 137 |
Bi-directional |
|||
NetBIOS Netlogon/ Browsing |
UDP 138 |
Bi-directional |
|||
SMB |
TCP 445 UDP 4451 |
Bi-directional |
|||
LDAP |
TCP 389 UDP 389 |
Bi-directional |
|||
LDAP SSL |
TCP 636 |
Bi-directional |
|||
LDAP GC |
TCP 3268 |
Bi-directional |
|||
LDAP GC SSL |
TCP 3269 |
Bi-directional |
|||
Active Directory Web Services |
TCP 9389 UDP 9389 |
Bi-directional |
Powershell uses this port. |
||
DNS |
TCP 53 UDP 53 |
Bi-directional |
|||
Kerberos |
TCP 88 UDP 88 |
Bi-directional |
|||
SQL Server |
TCP 1433 UDP 1434 |
Bi-directional |
For more information, see Configure the Windows Firewall to Allow SQL Server Access in Microsoft documentation. |
![]() Note |
For more information on Windows authentication, see Service overview and network port requirements for the Windows in Microsoft documentation. |
Listener (Process or Application Protocol) |
Listener Protocol and Port |
Remote Device (Process or Application Protocol) |
Remote Port |
Traffic Direction |
Notes |
---|---|---|---|---|---|
SNMP–Trap |
UDP 162 |
Bi-directional |
|||
Syslog |
UDP 514 |
Bi-directional |
|||
Telnet |
TCP 23 |
Bi-directional |
|||
RDP (Terminal Services) |
TCP 3389 |
Bi-directional |
|||
pcAnywhere |
TCP 5631 UDP 5632 |
Bi-directional |
|||
VNC |
TCP 5900 TCP 5800 (Java HTTP) |
Bi-directional |
RealVNC |
Listener (Process or Application Protocol) |
Listener Protocol and Port |
Remote Device (Process or Application Protocol) |
Remote Protocol and Port |
Traffic Direction |
Notes |
---|---|---|---|---|---|
Router (side A and B) (TIP Event) |
Router A: 40034 + (instance number * 40) Router B: 41034 + (instance number * 40) |
CUIC/Live Data |
Bi-directional |
Public network Live Data Events. |
|
Router (side A and B) (TIP TOS) |
Router A: 40035 + (instance number * 40) Router B: 41035 + (instance number * 40) |
CUIC/Live Data |
Bi-directional |
Public network Live Data Test Other Side. |
|
ICM PG1 (side A and B) (TIP Event) 2 |
Side A: 42034 + (instance number * 40) Side B: 43034 + (instance number * 40) |
CUIC/Live Data |
Bi-directional |
Public network Live Data Events. |
|
ICM PG2 (side A and B) (TIP Event) |
Side A: 44034 + (instance number * 40) Side B: 45034 + (instance number * 40) |
CUIC/Live Data |
Bi-directional |
Public network Live Data Events. |
|
ICM PG1 (side A and B) (TIP TOS) |
Side A: 42035 + (instance number * 40) Side B: 43035 + (instance number * 40) |
CUIC/Live Data |
Bi-directional |
Public network Live Data Test Other Side. |
|
ICM PG2 (side A and B) (TIP TOS) |
Side A: 44035 + (instance number * 40) Side B: 45035 + (instance number * 40) |
CUIC/Live Data |
Bi-directional |
Public network Live Data Test Other Side. |
Process or Application Protocol |
Protocol and Port |
Remote Device |
Remote Port |
Traffic Direction |
Notes |
---|---|---|---|---|---|
AW Tomcat |
— |
Hybrid Services on cloud | 443 | Bi-directional |
Following URLs must be included in the allowed list of network: *.wbx2.com *.ciscoccservice.com |