Question

A global enterprise uses globalized call routing in Cisco UCM. All PSTN calls are normalized to +E.164 and routed through a single route pattern that points to a route list containing a Standard Local Route Group. A user in the Singapore site places a call to a local Singapore number. The call correctly matches the global route pattern, but it egresses through the US gateway instead of the Singapore gateway. What is the most likely cause?

Accepted Answer

The Local Route Group setting is not configured in the Singapore phone's Device Pool, so UCM falls back to the route list's explicitly configured route group

Answer

The global route pattern is assigned to the wrong partition, preventing the Singapore CSS from matching it

Answer

The called-party transformation on the Singapore gateway is stripping the +E.164 prefix before routing

Answer

The Singapore phone's calling search space does not include the emergency partition required for local calls