Calling Party Transformation Patterns applied at the gateway rewrite inbound calling numbers into E.164 before CUCM processes them. This satisfies the stem's normalisation requirement at the gateway level, unlike route patterns or translation patterns that operate on dialled digits rather than the calling party.
Why this answer
Calling Party Transformation Patterns are applied at the gateway or trunk level to normalize the calling party number (ANI) into E.164 format before the call is routed within CUCM. They can be assigned to a gateway, trunk, or route list, and they manipulate the calling number using digit manipulations (prefix, strip, etc.). For normalizing incoming PSTN caller IDs, this is the correct tool because it specifically targets the calling party field.
Exam trap
CLCOR often tests the difference between Translation Patterns (called party/dialed digits) and Calling Party Transformation Patterns (calling party/ANI), causing candidates to pick Translation Pattern for caller ID normalization.
How to eliminate wrong answers
Option A is wrong because a Translation Pattern is used to translate dialed digits (called party) and route calls; it can also transform calling party, but it is not the dedicated gateway-level tool for normalizing incoming ANI and is typically used for dial plan translation, not PSTN caller ID normalization. Option B is wrong because a Route Filter is used to filter route groups based on dialed digits or calling party number for route selection, not to transform the number itself. Option C is wrong because a Route Pattern matches dialed digits and points to a route list/gateway; it does not normalize the calling party number.