UC LabFree University

T6 · T6-R01

UCCE from carrier to agent

Learn it in 5 minutes

  • Ingress, routing, queue treatment, and the agent are different stages.
  • CVP can front the call and ask ICM for a label.
  • The routing script returns a destination. It is not the audio file.
  • Finesse shows agent state.
  • CUIC reports what was logged, which can lag the call.

Visual

UCCE from carrier to agent diagram

What is going on

Unified Contact Center Enterprise is a system of pieces: gateway, CVP, the ICM router and logger, peripheral gateways, and the desktop. A teaching path is PSTN to the gateway, control to CVP and ICM, then delivery to an agent on CUCM. Your deployment can be a different model. Name the model before you debug.

Confirm before relying. Confirm component names against the design guide for your UCCE release.

Worked example

The caller hears queue music, so CVP treatment works. No agent is offered the call. Look at skill group staffing and the script's queue node before you restart the gateway.

Quiz

1. Queue music means an agent phone is ringing.

Ecosystem

Sister pieces sit on the ecosystem page: the glossary, the mind map, the integration map, and the sibling labs.

  • CVP — Customer Voice Portal, the voice browser and call-control front in many designs.
  • ICM — The routing brain in UCCE.

Config. Save the script name, the label returned, and the agent device target.

Troubleshooting. Separate 'no route' from 'no agent available'.

Bridge. CUCM still places the agent call. A CUCM partition mistake looks like an ICM failure.

Mind map, sister technologies, and future hooks live on the ecosystem page.

Sources

Product screens move. Confirm the guide for your release before you change a live system.

Sources and go deeper

Opened 2026-10. A row marked confirm has no link, because that page was not verified.

sources.json Markdown