Port Utilization in 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. | |
Digital Routing Service (Redis Service) | TCP 6379 | Digital Routing Service on the other node in the same cluster. | Bidirectional | Default Redis service port 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 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. |
Orchestration Inventory Service | TCP 8445 | Orchestration target node | — | Inward from Orchestration target node to Cloud Connect Orchestration Inventory Service | Used for fetching Orchestration inventory status, getting Cloud Connect public key, Orchestration onboarding, updating, and removing target node from Orchestration inventory on Cloud Connect server. |
Table 3. Cloud Connect Services
| (Process or Application Protocol) | Protocol and Port | Remote Device (Process or Application Protocol) | Remote Port | Traffic Direction | Notes |
|---|---|---|---|---|---|
Dataconn Service | Webex Engage API end points for user sync. US region — https://api-us-site-1.imiengage.io EU region 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 | TCP 443 | Outbound traffic | ||
CloudConnectMgmt | Fusion Management Service | TCP 443 | |||
CloudConnectMgmt | WxCC Services https://*.ciscoservice.com | TCP 443 | |||
CloudConnectMgmt | Webex Identity | TCP 443 | |||
CherryPoint | Webex Experience Management | TCP 443 | Get remote host address from the Webex Experience Management | ||
Digital Routing | 38001 | CCE Media Routing Peripheral Gateway | Media routing application port | ||
Digital Routing JMX | TCP 10006 | JConsole | Bidirectional | JMX access by JConsole into Digital Routing service | |
Digital Routing | Webex Connect tenant specific Webhook endpoint | TCP 443 | Outbound traffic | Asynchronous Webhook notifications sent from Digital Routing service to Webex Connect to invoke flows | |
Ansible Controller | — | Cisco Devhub Artifactory | TCP 443 | Outward from Ansible Controller to Cisco Devhub Artifactory | Used for communicating with Cisco Devhub Artifactory. |
Feedback