00 · Header

T4 · Webex Contact Center Enterprise

Classroom Index

Color-coded sequence: PSTN → CVP → Router → Desktop. A packet moves along the arrows. Reduced motion keeps every step visible.

This index maps each T4 topic to an official Cisco chapter. Session numbers, dates, and a session-by-session classroom pack are TODO-verify because that pack is not published here.

Room T4-R09 Version v0.1 last-verified: TODO Difficulty L2 Est. time 70–90 min Prereq T4-R01 Reading 18 min

01 · Executive summary

Five lines, then why it matters

Use the written Canon rooms for CVP, Finesse, CUIC, and sizing. Use this index to point the unwritten component, call-flow, and scripting topics at the chapter that already states them. [cite:1] [cite:2]
The Router selects a peripheral or agent. The Logger stores configuration, real-time, and historical data. The PG talks to the telephony device. The Administration & Data Server holds a configuration copy and hosts Script Editor. [cite:1]
A Router and Logger on one side are often called the Central Controller. Historical data later moves from the Logger to an optional Historical Data Server. [cite:1]
Comprehensive call flow and SendToVRU live in the CVP configuration guide. Device majority and the two networks live in the design-guide high-availability chapter. [cite:2] [cite:3]
Webex Contact Center Enterprise as a product name is help article nmhk7ve. The Unified CCE component model is the serviceability chapter. Keep those pages apart. [cite:1] [cite:4]

Why it matters. A classroom index that invents session numbers becomes a second source of truth. The official chapter is the source. The missing pack stays marked until it is in the repository.

02 · Architecture map

Canon room to official chapter

1Product name lives on help.webex
2Component roles live in the serviceability chapter
3SendToVRU is named; a scripting course is not
6Session map stays TODO-verify

Mermaid source (not rendered)

flowchart LR
  ADS[Administration and Data Server] --> R[Router]
  R --> L[Logger]
  L --> R
  R --> PG[PG and other clients]

03 · Core concepts

What the index is allowed to say

Four components

Router, Logger, Peripheral Gateway, and Administration & Data Server. The Router makes the routing decision. The Logger stores configuration, real-time, and historical data. The PG normalizes the peripheral. The Administration & Data Server provides configuration from the Logger, a real-time interface, and the historical data server platform, and it offers Script Editor and Internet Script Editor. [cite:1] re-check

Lock-step is not every process

MDS delivers the same messages in the same order to duplex processes that hold centralized state. Both Router sides are concurrently in service. OPC on the PG is kept in lock-step. The PIM is not a lock-step process and does not share data between sides. Either the Side A or the Side B PIM is active for each peripheral. [cite:1]

Logger recovery is Logger to Logger

Side A Router sends messages only to the Side A Logger. Side B Router sends messages only to the Side B Logger. Because the Routers run in lock-step, those messages match while they are flowing. Recovery between Loggers uses bulk database copy. [cite:1]

Session map

The Canon source map names a classroom pack as an internal citation style. That pack is not in this repository. Session numbers, dates, and any claim that a particular class covered a particular slide are TODO-verify. Study the chapter listed in the crosswalk.

Crosswalk

Canon topic	Official place to read	What that page actually says	Cite
T4-R01 overview	nmhk7ve, nyosarq, ny65x1bb	Webex Contact Center Enterprise is named as a cloud contact center model, distinct from UCCX, UCCE, PCCE, and multi-tenant WxCC. Quick deployment states 500 to 24,000 concurrent agents and an initial U.S. scope.	[cite:4] [cite:5]
T4-R02 components	Serviceability guide, Product Architecture, updated April 30, 2025	Router, Logger, PG, Administration & Data Server. Duplex via MDS. PIM is not lock-step.	[cite:1] re-check
T4-R03 call flow	CVP call-flow models, and the design-guide note that Comprehensive is the Reference Design call flow	Use the written T4-R05 room for the legs. The unwritten call-flow room should not invent a second sequence.	[cite:2] [cite:6]
T4-R04 scripting	CVP guide sentence on the SendToVRU node	The node connects the call to the Network VRU. A step-by-step Script Editor course is TODO-verify.	[cite:2]
T4-R05 through T4-R08	The rooms in this slice	CVP, Finesse, CUIC, and duplex sizing already cite their chapters.	[cite:2] [cite:3]
T4-R10 hybrid	nhy3hvdb dated sections	Hybrid model names, regional media, digital channels, and the 48,000-agent sentence. Read T4-R10 before merging those dates.	[cite:7]

04 · Ecosystem

Where the index stops

Mini map of the neighbors named on this room’s sequence. Orientation sketch, not a new product claim.

Glossary

Router: Selects a peripheral or agent for an inbound contact. Both sides stay in service and share data through MDS. [cite:1]
Logger: Stores configuration, real-time, and historical data. Hears only its own Router. [cite:1]
Central Controller: A Router and Logger combination. Often collocated on one server. [cite:1]
PG: Talks to the telephony device, tracks agent and call state, and forwards routing requests. Duplexed with MDS, with one side active for many components. [cite:1]
PIM: Peripheral Interface Manager. Not lock-step. One side is active per peripheral. [cite:1]
OPC: Open Peripheral Controller. Critical PG process. Kept in lock-step with the other side. [cite:1]
Administration & Data Server: Configuration copy, real-time interface, historical data server platform, and the Script Editor interface. [cite:1]
HDS: Optional Historical Data Server. Long-term repository. Offloads historical reporting from the Logger. [cite:1]
SendToVRU: ICM Script Editor node that connects the call to the Network VRU. [cite:2]
VRU PG and MR PG: These PGs do not maintain agent state. They maintain call or task state and expose an interface for instructions from the Router. [cite:1]
Classroom session: TODO-verify. No session number is stored in this room.

Mind map

Mermaid source (not rendered)

mindmap
  root((Index))
    Router
    Logger
    PG
    Administration and Data Server

Sister matrix

Orientation only. Peer columns name where to read next. They are not a parity matrix.

Sister	What the cited page says	Why it matters	Config touchpoint	Typical failure	Cite
Workforce management	py6u9h is the WFO SKU article. The product-architecture chapter does not size WFM.	Agent state on the PG is not a WFM schedule.	SKU article, then the WFM guide.	Treating OPC state as a forecast.	[cite:8]
Quality management and recording	The architecture chapter stores historical data in the Logger and optionally the HDS. It does not define a recording file.	A half-hour summary is not an audio archive.	Recording guide for the release you run.	Querying the Logger for the WAV.	[cite:1]
E911, RAY BAUM, Kari, RedSky	The architecture chapter does not configure emergency calling. nhy3hvdb points 9-1-1 compliance at the partner technical guide.	Emergency location is a different article.	T4-R10 and the partner guide section the what’s-new page names.	Looking for a RedSky trunk inside Script Editor.	[cite:7]
Analytics and reporting	The Router feeds real-time data to Administration Servers. The Logger stores historical data and replicates it to the Historical Database.	CUIC reads that data. The index does not replace T4-R07.	T4-R07 for stock reports.	Editing a CUIC grid to change Router lock-step.	[cite:1]
Salesforce, Dynamics 365, ServiceNow	The architecture chapter lists traditional CTI clients such as wallboards and desktops. It does not name those CRMs.	A CRM gadget is a CTI client only when a Finesse or CTI guide says so.	T4-R06 for gadgets.	Adding a CRM name to the four-component list.	[cite:1]
Virtual agents	The Router can route voice, email, and chat. Virtual-agent hosting is a what’s-new topic, not this chapter.	Keep CCAI on nhy3hvdb and T4-R10.	T4-R05 for IVR legs.	Calling a Dialogflow bot a PIM.	[cite:1] [cite:7]
IVR and self-service	A VRU PG does not maintain agent state. SendToVRU connects the call to the Network VRU.	IVR treatment and agent selection are different steps.	T4-R05.	Expecting the VRU PG to own agent state.	[cite:1] [cite:2]
Digital channels	The Router description includes email and chat as contacts. Webex Connect channel names are on nhy3hvdb.	A contact type in the Router sentence is not the Connect channel list.	T4-R10 for the dated channel list.	Equating “chat” in the architecture chapter with a specific messenger product.	[cite:1] [cite:7]
Identity and SSO	Not configured in the product-architecture chapter read here.	Sign-in is a Finesse and IdS topic.	T4-R06 and the IdS paragraphs in T4-R08.	Restarting the Logger to fix a desktop sign-in.	[cite:1]

Integration edges

From	To	Mechanism	What moves	Cite
Routing client	Router	PG notification	A call that needs a routing decision	[cite:1]
Router side	Its own Logger	Direct messages	Call detail and PG summary messages	[cite:1]
Logger	HDS	Distributor-style replication	Historical data, so reporting can leave the Logger	[cite:1]
PIM	Peripheral	Proprietary CTI, one active side	Normalized state for OPC	[cite:1]
ICM Script Editor	Network VRU	SendToVRU node	The call connection into Unified CVP	[cite:2]
Administration & Data Server	Logger	DBAgent, then Router, then Logger	Configuration updates. Logger database is authoritative.	[cite:1]

Bridges

This index	Neighbor	Peer label	Cite
Unified CCE four components	Webex Contact Center Enterprise help articles name a cloud offer. They do not replace the serviceability chapter.	Multi-tenant Analyzer is utqcm7, not this index.	[cite:1] [cite:4]
Script Editor on the ADS	Flow Designer is the multi-tenant article nhovcy4.	Call Studio is the CVP application tool in T4-R05.	[cite:1] [cite:9]
Missing classroom pack	Official chapters stay citable without the pack.	No vendor course is substituted for a session number.	[cite:1]

Future hooks

When a classroom pack is added to the repository, replace each TODO-verify session row with the internal citation style the source map names, and still keep the Cisco chapter beside it.
Re-read the serviceability chapter when Cisco updates it past April 30, 2025.
A Script Editor lab belongs in a future T4-R04 room, and only after a page that walks the editor is cited.

Ecosystem troubleshooting

Symptom	Likely mix-up	Check	Move	Cite
Both PIMs are drawn as active	Router lock-step was copied onto the PIM	The chapter says the PIM is not lock-step and one side is active	Redraw the PIM as active or standby per peripheral.	[cite:1]
Side B Logger is fed from Side A Router	The “same messages” sentence was read as a cross-link	Each Logger hears only its own Router	Draw two vertical pairs.	[cite:1]
A study note cites “session 4” for SendToVRU	A classroom number was invented	The node is named in the CVP guide. The session pack is absent.	Cite the CVP page. Leave the session TODO-verify.	[cite:2]
Flow Designer steps are used to explain ICM scripts	The multi-tenant flow article was used as Script Editor	nhovcy4 is the Flow Designer article	Stay on SendToVRU until a scripting page is read.	[cite:9]

05 · Flow

From a routing request to a stored summary

Step	From	To	Mechanism	Notes	Cite
1	Peripheral	PIM	Proprietary CTI	One PIM side is active. The other activates if that side loses the connection.	[cite:1]
2	PIM	OPC	Normalized messages	OPC keeps agent state and stays in lock-step with the other side.	[cite:1]
3	PG	Router	Status and routing request	The Router runs a user-defined script and tells the routing client what to do.	[cite:1]
4	Script	Network VRU	SendToVRU	Named in the CVP guide. Further editor steps are TODO-verify.	[cite:2]
5	Router	Matching Logger	Detail and summary messages	Half-hour summaries are an example of what PGs compute and send through the Router.	[cite:1]
6	Logger	HDS	Replication	Optional. Offloads historical reporting.	[cite:1]

06 · Config

Where each setting actually lives

Item	Where the guide puts it	Rule	Cite
Routing script	Administration & Data Server interface: Script Editor or Internet Script Editor	The Router runs the script. The ADS is the admin interface.	[cite:1]
Authoritative configuration	Logger configuration database	ADS copies can send updates. Only the Logger database is authoritative.	[cite:1]
ConAPI	Administration & Data Server	API for reading and changing configuration. Procedure detail is not copied here.	[cite:1]
CTI Server	Coresident with the PG, called the CTI Gateway in this chapter	At any given time only Side A or Side B CTI Server is active.	[cite:1]
Unified CM PIM	JTAPI Gateway between Unified CM and OPC	Unified CM knows lines. The PG is primary for agent state in that case.	[cite:1]
SendToVRU	ICM Script Editor node	Connects the call to the Network VRU. See T4-R05 for the call-flow models around it.	[cite:2]

07 · Limits

Boundaries this index will not cross

Boundary	What is known	What stays open	Cite
Classroom sessions	The source map expects an internal session citation when a pack exists.	Pack absent. Every session number is TODO-verify.	[cite:1]
Script Editor tutorial	SendToVRU is named. The ADS hosts the editor.	Node-by-node editor instruction beyond that sentence is TODO-verify.	[cite:2]
Guide age	Product architecture chapter updated April 30, 2025.	Re-check. Facts older than 12 months stay marked.	[cite:1]
Agent-count slides	nyosarq states 500 to 24,000 for the quick deployment. nhy3hvdb states 48,000 in a later what’s-new line. The design guide states a Finesse cluster total of 2,000.	Do not add them in this index. Read the room that owns each number.	[cite:5] [cite:7] [cite:3]
NIC	A Network Interface Controller is a more limited routing client, typically coresident with the Router, used for Unified ICM deployments.	A Webex CCE cloud NIC design is not in the paragraphs used here.	[cite:1]

08 · Troubleshooting

Rows you can check without a classroom slide

Symptom	What to inspect	What the page implies	Cite
Both Router sides look idle	Side A and Side B service state	Both Router sides are concurrently in service during normal duplex operation.	[cite:1]
A PG failover dropped call context	Whether OPC had the sibling’s context	The chapter says the opposite side continues with the other side’s context without losing calls.	[cite:1]
Agent state on Unified CM does not match the ACD mental model	Which PG type is attached	An ACD PG mirrors ACD agent state. A Unified CM PG is primary for agent state because Unified CM tracks lines.	[cite:1]
Two CTI Servers both show active	CG on each PG side	Only one CTI Server side is active.	[cite:1]
Historical report is aimed at the Logger months later	Whether an HDS was installed	HDS is the long-term repository and offloads historical reporting from the Logger.	[cite:1]
A note says “the class taught three extra components”	The four-name list in the chapter	Router, Logger, PG, Administration & Data Server. Extra names need their own page. TODO-verify if they came only from a missing pack.	[cite:1]

09 · Self-question

Twelve rungs

L0Which four components does the serviceability chapter call major?

Router, Logger, Peripheral Gateway, and Administration & Data Server. [cite:1]

L1Are both Router sides in service at once?

Yes. They stay in lock-step through MDS and both are concurrently in service. [cite:1]

L1Which Logger does Side B Router talk to?

Only the Side B Logger. [cite:1]

L2What is a Central Controller?

A Router and Logger combination, often on the same server. [cite:1]

L2Which PG process is lock-step, and which is not?

OPC is lock-step. The PIM is not. One PIM side is active per peripheral. [cite:1]

L2What does a VRU PG maintain?

Call state, not agent state. An MR PG maintains task state. [cite:1]

L3Where is the authoritative configuration database?

On the Logger. ADS databases are copies. [cite:1]

L3What does SendToVRU do, in the sentence the CVP guide gives?

It connects the call to the Network VRU. [cite:2]

L3Why is Unified CM agent state different from ACD agent state?

Unified CM knows lines. The PG is primary for agent state. An ACD PG mirrors the ACD. [cite:1]

L4How does a configuration change reach the Logger?

ADS client to DBAgent, DBAgent to Router through MDS, Router validates and sends it to the Logger, Logger confirms, Router distributes to clients. [cite:1]

L4Which Canon room owns the 2,000-user Finesse line?

T4-R08, from the design-guide high-availability chapter. This index does not merge it with 24,000 or 48,000. [cite:3]

L5What would you need before you write a session-by-session map?

The classroom pack in the repository, cited in the source map’s internal style, beside the Cisco chapter. Until then the map is TODO-verify.

10 · Lab

Paper lab: build the crosswalk

Goal: label each T4 topic with one official URL and zero invented session numbers.
Prereq: the Release 15.0(1) product-architecture chapter. [cite:1]
Step 1. Write the four component names and which process is lock-step.
Step 2. Draw Side A Router to Side A Logger only.
Step 3. Point T4-R05, T4-R06, T4-R07, and T4-R08 at the rooms already written.
Step 4. Write SendToVRU as a single node name. Leave the rest of Script Editor blank and mark it TODO-verify.
Evidence: the April 30, 2025 update line on the serviceability chapter.
Break it: add “session 7, 12 March” with no pack. Recovery: delete the row.
Reflection: which numbers did you refuse to add together?

11 · Quiz

Twelve checks

0 revealedAnswers stay closed until you open them.

Q1MCQ

The four major components in the serviceability chapter are:

Router, Logger, PG, Administration & Data Server
CUBE, Expressway, IdS, Analyzer
Finesse, CUIC, CVP, Cloud Connect only
Flow Designer, Agent Desktop, Control Hub, Edge Connect

Reveal

A. [cite:1]

Q2MCQ

MDS is used so that duplex processes:

Receive the same messages in the same order
Load-balance calls 50/50
Store recordings
Replace the Logger

Reveal

A. [cite:1]

Q3MCQ

The PIM is:

Not lock-step. One side is active per peripheral.
Always active on both sides
The authoritative configuration database
A CUIC subscriber

Reveal

A. [cite:1]

Q4Scenario

Side A Router fails. What does the chapter say the other Router side does?

Reveal

The opposite side assumes sole responsibility for routing decisions. Both sides had the same data. [cite:1]

Q5MCQ

SendToVRU is:

An ICM Script Editor node that connects the call to the Network VRU
A Finesse gadget XML file
A BGP community
A CUIC stock report

Reveal

A. [cite:2]

Q6MCQ

The authoritative configuration database is:

The Logger
Every ADS copy equally
The PIM
Flow Designer

Reveal

A. [cite:1]

Q7Scenario

You want a session-by-session classroom map. What is the status of that map in this room?

Reveal

TODO-verify. Use the official chapter.

Q8MCQ

A VRU PG maintains:

Call state, not agent state
Agent skill profiles only
CUIC permissions
BGP routes

Reveal

A. [cite:1]

Q9MCQ

CTI Server activity is:

One side active, not both
Both sides active like the Router
Inactive until CUIC opens
Hosted on the publisher only

Reveal

A. [cite:1]

Q10Scenario

Unified CM does not track agent state. Who is primary?

Reveal

The PG attached to Unified CM. [cite:1]

Q11Draw it

Draw the configuration update after the Router validates it.

Reveal

Router to Logger, Logger confirms, Router distributes to clients. [cite:1]

Q12MCQ

The product-architecture chapter used here was updated:

April 30, 2025, so mark re-check
September 23, 2026
December 12, 2025
It has no date

Reveal

A. [cite:1]

12 · Audio

Slots for Studio

Transcript slot

Studio fills this from the cites.

Transcript slot

Studio fills this from the cites.

Transcript slot

Studio fills this from the cites.

13 · Interview

Oral answers

30 seconds. Unified CCE’s serviceability chapter names four major components: Router, Logger, PG, and Administration & Data Server. Both Routers stay in service. Each Logger listens only to its own Router.

2 minutes. MDS keeps duplex state processes on the same messages in the same order. OPC is one of those processes. The PIM is not. One PIM side is active per peripheral, and the other side activates if the connection drops. A Unified CM PG is primary for agent state because Unified CM tracks lines. A VRU PG tracks calls, not agents. Configuration changes go through DBAgent and the Router, and the Logger database is the authoritative copy. Historical reporting can move to an HDS.

30 seconds, the index. I map T4 topics to those chapters. I do not invent a classroom session number. SendToVRU is a named Script Editor node. The rest of a scripting course stays TODO-verify.

2 minutes, the boundaries. Webex Contact Center Enterprise as a cloud offer is a help article, not a replacement for this chapter. Flow Designer is a different product’s flow tool. The 500-to-24,000 quick-deployment range, the Finesse 2,000 line, and the 48,000 what’s-new sentence stay in their own rooms. The architecture chapter I am quoting was updated April 30, 2025, so it stays re-check.

What you will not say. You will not quote a class date, a session number, or a personal biography.

14 · Citations

Ledger

Retrieved 2026-10-14. Study notes from public sources.

Serviceability Guide for Cisco Unified ICM/Contact Center Enterprise, Release 15.0(1), Product Architecture — cisco.com — updated April 30, 2025 — Product architecture. Four components, MDS, Logger pairing, PIM versus OPC, CTI Server, configuration path, HDS. re-check
Configuration Guide for Cisco Unified Customer Voice Portal, Release 15.0(1), Unified CVP Call Flow Models — cisco.com — updated December 12, 2025 — CVP call flow models. SendToVRU node of the ICM Script Editor.
Solution Design Guide for Cisco Unified Contact Center Enterprise, Release 15.0(1), High Availability and Network Design — cisco.com — updated March 15, 2025 — High availability. Finesse cluster total and duplex networks. Detail is T4-R08. re-check
Webex Dedicated Instance Contact Center integration — help.webex — article nmhk7ve — help.webex.com article nmhk7ve. Model names. Detail is T4-R01.
Webex Contact Center Enterprise Quick Deployment Solution — help.webex — article nyosarq — help.webex.com article nyosarq. 500 to 24,000 concurrent agents. Initial U.S. scope. Detail is T4-R01.
Solution Design Guide for Cisco Unified Contact Center Enterprise, Release 15.0(1), Non-Reference Designs — cisco.com — updated March 15, 2025 — Non-reference designs. Comprehensive is the Reference Design call flow. re-check
What’s new for administrators in Webex Contact Center Enterprise — help.webex — article nhy3hvdb — help.webex.com article nhy3hvdb. Hybrid names, digital channels, 48,000 agents, 9-1-1 pointer. Dated sections are re-check. Detail is T4-R10. re-check
Webex WFO: Feature Specific SKUs — help.webex — article py6u9h — help.webex.com article py6u9h. WFO scope. Not a component diagram.
Build and manage flows with Flow Designer — help.webex — article nhovcy4 — help.webex.com article nhovcy4. Multi-tenant flows. Not Script Editor.

15 · Re-engineer later

Still open

Open questions: session-by-session classroom mapping TODO-verify. Script Editor steps beyond SendToVRU TODO-verify.
Facts still marked re-check: the April 30, 2025 architecture chapter, the March 15, 2025 design-guide chapters, and the dated nhy3hvdb sections.
Assets missing: crosswalk SVG export, audio, the classroom pack itself.
Ideas for v1.0: one row per future room that an integrator can link when T4-R02, T4-R03, and T4-R04 are written.
Next review: re-read product architecture when Cisco updates it past April 30, 2025, and attach the pack only from the repository.

Sources and go deeper

Checked links were opened this month. A confirm row has no address because that page was not opened.

Wikipedia Webex (Wikipedia) last checked 2026-10
Vendor doc Webex Help Center last checked 2026-10
DevDocs Webex developer documentation last checked 2026-10
DevDocs Webex developer getting started last checked 2026-10
Community Webex community last checked 2026-10
SRND Cisco Collaboration design zone last checked 2026-10
RFC RFC 3261 SIP: Session Initiation Protocol last checked 2026-10
Port table IANA service name and port number registry last checked 2026-10
Port table Port reference for Webex Calling last checked 2026-10
Wikipedia Call centre (Wikipedia) last checked 2026-10
Wikipedia Interactive voice response (Wikipedia) last checked 2026-10
Release notes What's new for administrators in Webex Contact Center last checked 2026-10
Vendor doc Product architecture last checked 2026-10
Vendor doc CVP call flow models last checked 2026-10
Vendor doc High availability last checked 2026-10
Vendor doc help.webex.com article nmhk7ve last checked 2026-10
Vendor doc help.webex.com article nyosarq last checked 2026-10
Vendor doc Non-reference designs last checked 2026-10
Vendor doc help.webex.com article nhy3hvdb last checked 2026-10
Vendor doc help.webex.com article py6u9h last checked 2026-10
Vendor doc help.webex.com article nhovcy4 last checked 2026-10

sources.json for this page.