Physical Locations are used in Unified CM to group together devices residing in the same network location and used later for Device Mobility. Also there is The location concept in Unified CM and it is purely used for Call Admission Control (CAC). Devices are assigned to Physical locations and Locations (CAC) by selecting a location at the device pool level.
With Webex Calling, there is a concept of location, but it does not have any CAC capabilities, Webex Calling locations concept group together devices or users sharing the same geographical location (address) or sites, PSTN access (on-prem or cloud connected PSTN), main number, site code, PSTN steering digit (PSTN Access Code) etc.
Local route groups in Unified CM to define or to determine the egress gateway for PSTN calls originated from a given site using the local gateway.
In Webex Calling, the equivalent of the local route group is the Location, a single egress connection can be configured per location (per site). This connection can be a Cloud Connected PSTN (CCP) trunk or a trunk via a Cisco Unified Border Element (CUBE) acting as Local Gateway (LGW). Each site is deployed with Local Gateway. When you configure a Trunk to the Local Gateway (CUBE), you assign the trunk to the specific location.
Route Groups are used in Unified CM to group trunks and gateways into equivalence groups which are used to configure redundancy, load balancing or to prioritizes egress gateway or trunk selection.
In Webex Calling, there is a Route Group concept for the same purpose, it is a group of Trunks that allow Webex Calling to distribute calls over multiple Trunks or to provide redundancy, priority for Trunks to on-premise gateways.
In CUCM a route list is a set of route groups in a specified priority order. A route list then is associated with one or more route patterns and determines the order in which those route groups are accessed to route calls.
In Webex Calling, there is no concept of Route List.
In CUCM a route pattern is a string of numbers that CUCM uses to determine where to route calls. The call can be either inter-site to another Cisco UCM Cluster or PSTN. Route patterns can point directly to a trunk/gateway or a Route List.
In Webex Calling, the equivalent of Route Pattern is Dial Plan, it allows Webex Calling to route calls to on-premises extension. Dial Plan can point directly to Trunks or Route Groups.
A dial pattern represents on-premises extensions:
1- ESN/on-net numbers
2- +E164 patterns
3- SIP URI domains
Numeric patterns can either represent +E164 numbers or enterprise specific numbers (ESN). Patterns for E.164 numbers start with a leading +, followed by a sequence of digits (1-9), and then optional wildcard characters. You cannot use the Globalized Route Pattern \+!. Instead you can only use numeric pattern such as: +1408555XXXX, +496100!, 84969XXX (Enterprise Specific Number ESN).
When you create a Dial Plan, you give a name and you point it to either a Trunk or Route Group. Unlike with a Route Pattern which contains only one pattern, the Dial Plan can contain multiple Dial Patterns. For example you can create a single Dial Plan with 30 +E164 + 30 ESN patterns that routes calls for the on-premises devices.
