Why UCCE Architecture Comes Before Touching a Script
Opening chapter: a map of the UCCE components, and why knowing the data path first saves hours of troubleshooting later.
A lot of people come to UCCE through the wrong door. They open Script Editor on day one, copy a pattern from the system they used before, and then wonder why calls stop somewhere that makes no sense. This chapter holds off on scripts until the component map is clear.
The components worth memorising
- Router: makes the routing decisions.
- Logger: stores configuration and historical data.
- PG (Peripheral Gateway): the bridge to CUCM, CVP, and other systems.
- CVP: handles call treatment before an agent picks up.
Those four explain most of what you will run into during your first year.
How a call travels
- The call arrives through the gateway.
- CVP asks the Router what to do.
- The Router runs the routing script and picks a target.
- The PG sends the call to an agent through CUCM.
Why the order matters
When a call fails, the useful question is not which line of the script is wrong. It is which step the call stopped at. That second question gets answered much faster, and it almost always points straight at the right component.
The next chapter covers reading a routing script without guessing.