Skip to content
Skip to search
Skip to footer

Port Utilization Guide for Cisco Unified Contact Center Solutions, Release 12.6(1)

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Book Contents

Find Matches in This Book

Results

Updated:: May 14, 2021

Chapter: Port Utilization in Cisco Cloud Connect

Port Utilization in Cisco Cloud Connect
Port Utilization in Cisco Cloud Connect

Port Utilization in Cisco Cloud Connect

Port Utilization in Cisco Cloud Connect

Table 1. Cisco Unified Web Proxy
Listener (Process or Application Protocol)	Listener Protocol and Port	Remote Device (Process or Application Protocol)	Remote Port	Traffic Direction	Notes
Cisco Unified Web Proxy Service (HTTPS)	TCP 8445	Applications	—	Inward from applications to Cloud Connect Services.	—

Table 2. Cloud Connect Services
Listener (Process or Application Protocol)	Listener Protocol and Port	Remote Device (Process or Application Protocol)	Remote Port	Traffic Direction	Notes
CherryPoint Service	TCP 3551	CherryPoint Service on the other node in the same cluster.	—	Bidirectional	CherryPoint services use this port for secure cluster management.
Inventory Service	TCP 5551	Inventory Service on the other node in the same cluster.	—	Bidirectional	Inventory services use this port for secure cluster management.
CloudConnectMgmt Service	TCP 6551	CloudConnectMgmt Service on the other node in the same cluster.	—	Bidirectional	CloudConnectMgmt services use this port for secure cluster management.
Ansible Controller	—	SSH Server on Orchestration target node	TCP 22	Outward from Ansible Controller to SSH Server on Orchestration target node	Used for connecting to target node for Orchestration.
Ansible Controller	—	SMTP Relay Server	TCP 25	Outward from Ansible Controller to SMTP Relay Server	Used for sending email notification.

Cloud Connect External Connections

Note

When using a proxy for Cloud Connect integration, ensure the domains and URLs listed in the table below are added to the proxy allowlist.

Table 3. Cloud Connect External Connections
(Process or Application Protocol)	Protocol and Port	Remote Device (Process or Application Protocol)	Remote Port	Traffic Direction	Notes
CloudConnectMgmt	—	Fusion Management Service https://hercules-a.wbx2.com, https://hercules-k.wbx2.com, https://hercules-r.wbx2.com	TCP 443	—	—
CloudConnectMgmt	—	WxCC Services https://*.ciscoservice.com	TCP 443	—	—
CloudConnectMgmt	—	Webex Identity https://idbroker.webex.com https://idbroker-eu.webex.com https://idbroker-b-us.webex.com	TCP 443	—	—
CherryPoint	—	Webex Experience Management	TCP 443	—	Get remote host address from the Webex Experience Management
Ansible Controller	—	Cisco Devhub Artifactory	TCP 443	Outward from Ansible Controller to Cisco Devhub Artifactory	Used for communicating with Cisco Devhub Artifactory.
Feature Flag Mgmt	—	Split.io	Both	Outbound traffic	—

Was this Document Helpful?

Feedback

Feedback

Contact Cisco

Open a Support Case
(Requires a Cisco Service Contract)