00 · Header

Core Components

T4-R02. The four major components in the Unified CCE 15.0(1) Product Architecture chapter: Router, Logger, Peripheral Gateway, and Administration & Data Server, plus Unified Intelligence Center. Updated April 30, 2025. This is the component guide the Enterprise overview points at. It is not a cloud Webex CCE data-sheet inventory.

Prereq rooms: T4-R01 for the product-name boundary. Call flow is T4-R03. Script nodes are T4-R04.

01 · TL;DR

Four components, then the reporting tier

• Unified CCE in this chapter integrates only with Unified CM. It was derived from Unified ICME. [cite:1]
• A Router plus Logger on one server is a Central Controller. [cite:1]
• PGs are duplex, but for many PG parts only one side is active. [cite:1]
• Direct CTI desktop use of GED-188 is deprecated in this chapter. [cite:1]
• Finesse is not named in the Product Architecture chapter read for this room. TODO-verify before you add it to this drawing.

02 · Map

The 15.0(1) component set

Study diagram of the serviceability chapter, updated April 30, 2025. That date is older than 12 months. [cite:1] re-check

03 · Core

Duplex does not mean both sides are active everywhere

The Product Architecture chapter of the Serviceability Guide for Unified CCE Release 15.0(1), updated April 30, 2025, says Unified CCE delivers intelligent contact routing, call treatment, network-to-desktop CTI, and multichannel contact management. It was derived from Unified ICME. The primary difference stated there is that Unified CCE integrates only with the Cisco Unified Communications Manager IP PBX. There is no single-server implementation. re-check [cite:1]

Four major components: the Router makes routing decisions and selects a peripheral or agent for a voice call, email, chat, and so on. The Logger stores and replicates configuration, real-time, and historical data. The Peripheral Gateway is the gateway to a peripheral such as an IP PBX or a VRU, and a CTI gateway toward desktops. The Administration & Data Server provides configuration from the Logger, real-time data, a platform for the Historical Data Server, and the interface for Script Editor and Internet Script Editor. [cite:1]

Administration & Data Server types in the chapter: AW with configuration and real-time and no historical data; AW-HDS-DDS with configuration, real-time, historical, and call detail; AW-HDS with configuration, real-time, and historical data but no call detail. The HDS is optional on an AW and is the long-term store. Historical data replicates from the Logger to one or more HDS databases. The Logger configuration database is authoritative. [cite:1]

Unified Intelligence Center is the web reporting platform for Unified ICME and Unified CCE. You install it standalone or in a cluster of at most eight nodes: one publisher, called the Controller, and up to seven subscribers, called Members. The Controller includes a Member, so a Controller-only deployment is valid. Reporting runs on Members. Administration runs on the Controller. The standard Unified CCE deployment uses the AW-HDS as the data source, and the chapter also allows the CVP Reporting Server as a data source. Stock report templates for Unified CCE data are preinstalled. Grid reports export to Microsoft Excel. [cite:1]

Finesse does not appear in this chapter. Putting Finesse on the core drawing is TODO-verify until a 15.0(1) page that names it is read. T4-R01 already warns that the help articles read for the Enterprise overview do not restate Router, Logger, CVP, or Finesse as components of cloud Webex CCE. This room teaches the Unified CCE chapter, and it does not move those names onto the multi-tenant product. [cite:1] [cite:2]

04 · Ecosystem

Ecosystem and sister technologies

These components are Unified CCE 15.0(1). Multi-tenant Webex Contact Center does not use this drawing.

Router

Runs the script and picks the target. Both sides stay in service. [cite:1]

Logger

First store for historical data, and the authoritative configuration database. [cite:1]

Central Controller

Router and Logger, often co-located. [cite:1]

MDS

Message Delivery Service. Feeds both sides the same messages in the same order. [cite:1]

PG

Normalizes the peripheral and tracks agent or task state. [cite:1]

PIM

Peripheral Interface Manager. One side active. Not lock-step. [cite:1]

OPC

Open Peripheral Controller. Lock-step. Primary agent state for a Unified CM PG. [cite:1]

GED-125

VRU PIM protocol. [cite:1]

GED-188

CTI Server protocol. Direct desktop use is deprecated in this chapter. [cite:1]

AW-HDS

Configuration, real-time, and historical data, no call detail. CUIC’s standard source. [cite:1]

CUIC Controller

The mandatory publisher. Includes a Member. Administration runs here. [cite:1]

Finesse gap

Not named in this chapter. TODO-verify. [cite:1]

mindmap
  Unified CCE 15.0.1
    Router
    Logger
    PG
      PIM
      OPC
    ADS
      HDS
    CUIC
    Not Finesse here

Sister-technology matrix

Integration edges

Cross-platform bridges

T4-R01 quotes the Dedicated Instance contact-center article: Webex Contact Center Enterprise is a cloud contact center for large enterprises, and UCCE and PCCE readers are sent to Unified CCE component documentation. This room is that component documentation. It does not claim the cloud data sheet lists these processes. [cite:2]

Multi-tenant Webex Contact Center architecture is article utqcm7. Do not draw a Logger on that product because this chapter has one. [cite:3]

Amazon Connect and Genesys have no component parity in this chapter.

Future-integration hooks

• Canon planning: T4-R03 is the route request. T4-R04 is Script Editor. T4-R08, still unwritten, is the HA chapter.
• Finesse placement: TODO-verify.
• April 30, 2025 is older than 12 months. re-check [cite:1]
• PCCE coresident PG layout is in the solution design guide overview and is not restated as a new fact beyond the PG types already quoted.

Ecosystem troubleshooting

05 · Flow

Status and requests move inward

06 · Config

Paths the articles name

1. Read the four major components before you add a box. [cite:1]
2. Pair Router A with Logger A only. [cite:1]
3. Choose the AW type for whether you need historical data and call detail. [cite:1]
4. Point CUIC’s standard deployment at an AW-HDS. [cite:1]
5. Author scripts from the Administration & Data Server’s Script Editor. The node rules are T4-R04. [cite:1]
6. Do not add Finesse to this diagram until a cited 15.0(1) page names it. TODO-verify

07 · Limits

Numbers worth memorizing

08 · Trouble

Trouble

09 · Self-question

Oral ladder

10 · Lab

Label the four boxes from the chapter

• Goal: draw Router, Logger, PG, and Administration and Data Server with the correct active-side notes.
• Prereq: the 15.0(1) chapter. No production cluster changes.
• Write Side A Router to Side A Logger only.
• Mark the PIM as single-active and OPC as lock-step.
• Add CUIC beside the AW-HDS, not on top of the Logger.
• Break it: add a Finesse box because the track title mentions it. Recovery: the chapter does not name Finesse.
• Evidence: the four names and the CUIC eight-node count.
• Reflection: which duplex rule you almost generalized.

11 · Quiz

Quiz

12 · Audio

Studio fills these

13 · Interview

Oral-ready

1. 30 seconds. Unified CCE 15.0(1) has four major components: Router, Logger, PG, and Administration and Data Server. [cite:1]

1. 2 minutes. Both router sides stay in service through MDS. Router A talks only to Logger A. The co-located pair is the Central Controller. The chapter date is April 30, 2025, so I re-check it. [cite:1]

2. 30 seconds. On Unified CM, the PG is primary for agent state. [cite:1]

2. 2 minutes. The PIM is single-active and not lock-step. OPC is lock-step. VRU PIM is GED-125 and does not keep agent state. [cite:1]

3. 30 seconds. CUIC is at most eight nodes, and the standard source is an AW-HDS. [cite:1]

3. 2 minutes. The Controller is mandatory and already includes a Member. Reporting runs on Members. AW-HDS has no call detail. [cite:1]

4. 30 seconds. Direct GED-188 desktops are deprecated in this chapter. [cite:1]

4. 2 minutes. Only one CTI Server side is active. I do not invent Finesse on this drawing. [cite:1]

5. 30 seconds. This is not the multi-tenant cloud component list. [cite:2]

5. 2 minutes. T4-R01 says the Enterprise help articles point UCCE readers at component documentation and do not restate these processes as cloud Webex CCE parts. Analyzer is still a different reporter. [cite:2] [cite:3]

14 · Citations

Ledger

Retrieved 2026-10-14. Mirrors cites/T4-R02.md. Facts older than 12 months, and pages whose header date was not in the extract, stay marked re-check.

1. Serviceability Guide for Cisco Unified Contact Center Enterprise, Release 15.0(1), Product Architecture — cisco.com — Product Architecture — updated April 30, 2025, retrieved 2026-10-14. Four components, MDS, PIM, OPC, GED-125, GED-188, AW types, CUIC cluster. re-check
2. Webex Dedicated Instance for Webex Contact Center integration context — help.webex — article nmhk7ve, as used by T4-R01 — boundary. This room does not move Unified CCE process names onto cloud Webex CCE.
3. Webex Contact Center architecture — help.webex — article utqcm7 — contrast only. Multi-tenant components are not this chapter.

15 · Re-engineer later

Open

• Open questions: the 15.0(1) page that names Finesse, if one does.
• Facts still TODO-verify: Finesse’s place on this drawing.
• Facts still re-check: the April 30, 2025 chapter.
• Assets missing: component SVG export, audio. No production server names.
• Next review date: next read of the 15.0(1) serviceability guide.