McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 38

↗ View in doc context
page
38
source
cucm/v15/preferred-architecture/preferred-architecture.md
chunk_id
cucm::v15::preferred-architecture::preferred-architecture::43

Preferred Architecture for Cisco Collaboration Release 15 On-Premises Deployments PAGE 38
Collaboration Management Services

Recommended Deployment Figure 18 illustrates the following recommended architectural aspects of the CCUC deployment: • CCUC cloud connectors run on each collaboration application node (in this case Unified CM and Unified CM IM&P). • The CCUC cloud connector and related services collect system telemetry data for endpoints, headsets, trunks, and call records. • The collected data is sent to Webex via an HTTPS connection that is initiated outbound from the UC infrastructure applications (in this case Unified CM and Unified IM&P). The telemetry data is encapsulated in HTTPS (TLS 1.2) and sent through the organization’s firewall and/or HTTPS proxy on port 443. • The collected telemetry data is analyzed and reported to the customer administrator within Webex Control Hub. • This outbound connection is also used to provide the additional services between the Webex Control Hub and the on-premises UC infrastructure and devices. This includes the management of the Unified CM application certificates, using a web-based RTMT client for troubleshooting, and troubleshooting Unified CM calls.

Figure 18. Architecture for Webex Cloud-Connected UC

Benefits Webex Cloud-Connected UC provides the following benefits: • Single pane of glass via Control Hub for both cloud and on-premises UC management. • Centralized location via Control Hub for key operational and troubleshooting activities for on-premises UC applications.

Image 1 from page 38

Image 2 from page 38