Cloud Connect UC Webex
“
Product Information
Specifications
- Brand: Cisco
- Product Name: Cloud Connect
- Supported Protocols: TCP
Product Usage Instructions
Cisco Unified Web Proxy Service (HTTPS)
The Cisco Unified Web Proxy Service uses TCP port 8445 for
inbound traffic from applications to Cloud Connect Services.
Cloud Connect Services
The following services are available in Cloud Connect:
Dataconn Service
TCP port 2551 is used for Dataconn Service on the other node in
the same cluster. Bidirectional services utilize this port for
secure cluster management.
Inventory Service
TCP port 5551 is designated for Inventory Service on the other
node in the same cluster. Bidirectional Inventory services use this
port for secure cluster management.
CloudConnectMgmt Service
TCP port 6551 is allocated for CloudConnectMgmt Service on the
other node in the same cluster. Bidirectional CloudConnectMgmt
services use this port for secure cluster management.
Digital Routing Service (Redis Service)
TCP port 6379 is utilized by Digital Routing Service on the
other node in the same cluster. This port is bidirectional and
serves as the default Redis service port for connecting locally and
replicating data between nodes.
Ansible Controller – SSH Server on Orchestration
TCP port 22 is used outward from Ansible Controller to connect
to the target node for Orchestration via SSH.
Ansible Controller – SMTP Relay Server
TCP port 25 is employed outward from Ansible Controller for
sending email notifications using the SMTP Relay Server.
Feature Flag Controller – Feature Flag target node
Used for fetching configured Feature Flag values from solution
components to Cloud Connect Feature Flag Service.
Cloud Connect External Connections
When integrating Cloud Connect with a proxy, ensure that the
specified domains and URLs are added to the proxy allowlist.
FAQ (Frequently Asked Questions)
Q: How do I configure the ports for Cloud Connect
services?
A: To configure the ports for Cloud Connect services, refer to
the respective service documentation or contact Cisco support for
assistance.
Q: What is the default port for Digital Routing Service?
A: The default port for Digital Routing Service is TCP 6379.
“`
Port Utilization in Cisco Cloud Connect
· Port Utilization in Cisco Cloud Connect, on page 1
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)
Cisco Unified Web Proxy Service (HTTPS)
TCP 8445
Applications
Remote Port Traffic Direction
Notes
—
Inward from
applications to
Cloud Connect
Services.
Table 2: Cloud Connect Services
Listener (Process or Application Protocol) Dataconn Service
Inventory Service
CloudConnectMgmt Service
Listener Remote Device (Process or Protocol Application Protocol) and Port
Remote Port Traffic Direction
Notes
TCP 2551 Dataconn Service on the other node in the same cluster.
Bidirectional Services use this port for (between two secure cluster management. nodes in the same cluster)
TCP 5551 Inventory Service on the other node in the same cluster.
Bidirectional Inventory services use this port for secure cluster management.
TCP 6551 CloudConnectMgmt Service on the other node in the same cluster.
Bidirectional CloudConnectMgmt services use this port for secure cluster management.
Port Utilization in Cisco Cloud Connect 1
Port Utilization in Cisco Cloud Connect
Port Utilization in Cisco Cloud Connect
Listener (Process or Application Protocol)
Listener Remote Device (Process or Protocol Application Protocol) and Port
Remote Port
Traffic Direction
Notes
Digital Routing Service TCP 6379 Digital Routing Service on the
(Redis Service)
other node in the same cluster.
Bidirectional
Default Redis service port that is used by Digital Routing Service to connect locally, and for Redis instances on Publisher and Subscriber to replicate data between both the nodes.
Ansible Controller
–
SSH Server on Orchestration TCP 22 target node
Outward from Used for connecting to target
Ansible
node for Orchestration.
Controller to
SSH Server
on
Orchestration
target node
Ansible Controller
–
SMTP Relay Server
TCP 25
Outward from Used for sending email
Ansible
notification.
Controller to
SMTP Relay
Server
Feature Flag Controller –
Feature Flag target node
Inward from solution components to Cloud Connect Feature Flag Service
Used for fetching the configured Feature Flag values. For more information, see the Feature Flag Commands section of the CLI Commands chapter of the Cisco Unified Contact Center
Enterprise Installation and
Upgrade Guide, Release
15.0(1) at https://www.cisco.com/c/en/ us/support/ customer-collaboration/ unified-contact-center-enterprise/ products-installation-guides-list.html.).
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.
Port Utilization in Cisco Cloud Connect 2
Port Utilization in Cisco Cloud Connect
Port Utilization in Cisco Cloud Connect
Table 3: Cloud Connect External Connections
(Process or Application Protocol)
Protocol and Remote Device (Process or
Port
Application Protocol)
Remote Port
Dataconn Service
Webex Engage API endpoints TCP 443 for user sync.
US region–https://api-us-site-1.imiengage.io
London / UK–https://api-uk-site-1.imiengage.io
EU region Ireland–https://api-eu-site-1.imiengage.io
ANZ region–https://api-syd-site-1.imiengage.com.au
Canada region–https://api-ca-site-1.imiengage.io
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
TCP 443
CherryPoint
Webex Experience Management TCP 443
Traffic Direction
Outbound traffic
Digital Routing
Webex Connect tenant specific TCP 443 Webhook endpoint
Outbound traffic
Digital Routing
Region-specific OAuth access TCP 443 token URL of Webex Connect. For the list of URLs based on the location of Webex Connect data center, see the Integrate
Cloud Connect with Webex
Connect section in the Cisco Unified Contact Center Enterprise Features Guide
Outbound traffic
Notes
Get remote host address from the Webex Experience Management Asynchronous Webhook notifications sent from Digital Routing service to Webex Connect to invoke flows Used to generate tokens for Webhook notifications.
Port Utilization in Cisco Cloud Connect 3
Port Utilization in Cisco Cloud Connect
Port Utilization in Cisco Cloud Connect
(Process or Application Protocol)
Ansible Controller
Protocol and Remote Device (Process or
Port
Application Protocol)
–
Cisco Devhub Artifactory
Remote Port Traffic Direction
Notes
TCP 443
Outward from Ansible Controller to Cisco Devhub Artifactory
Used for communicating with Cisco Devhub Artifactory.
Port Utilization in Cisco Cloud Connect 4
Documents / Resources
 |
CISCO Cloud Connect UC Webex [pdf] Instructions Cloud Connect UC Webex, Connect UC Webex, UC Webex, Webex |