WarmTransfer
migration · published

Migrating a Unified CM dial plan to Webex Calling or Teams

Verified 2026-09-25 · 60 sources · tier 2

Migrating dial plans from Cisco Unified Communications Manager (Unified CM) to cloud telephony platforms involves redesigning internal digit manipulation, routing constructs, and emergency profiles 1​8. Both Webex Calling and Microsoft Teams enforce specific limits and configuration structures that govern extension length, normalization, and PSTN gateway routing during phased coexistence 46​16​24.

Webex Calling Dial Plan Architecture

In Webex Calling, all extensions in a deployment have the same length, which can be configured to any value from 2 to 10 digits 46. The default internal extension length is 4 digits 44. Configuring location extensions with a length that differs from the global Webex Calling extension length triggers a Control Hub warning, and dialing from physical phones may then require en-bloc dialing 45. After any dialing preference change, users must restart their phones for the change to take effect 51.

When multiple locations share identical extension ranges, a location routing prefix of 1 to 7 digits must be dialed 54. The location routing prefix length setting counts the steering digit as part of the prefix 49. Cisco advises that the steering digit should not overlap the first digit of any location extension or any location outbound dial digit 56. Abbreviated extension dialing between locations functions only if the dialed extension is unique across the entire organization; the "Allow extension dialing between locations" toggle should only be enabled when all extensions are unique 47. Where overlapping extensions exist across sites, Cisco's design guidance specifies building an enterprise numbering plan that prefixes extensions with an access code and a site code 55.

A Webex Calling location's outbound dial digit defaults to none, and administrators can optionally enforce its use 48. Webex Calling ignores the outbound dial digit requirement for outbound calls dialed in E.164 format, which Cisco highly recommends for both incoming and outgoing PSTN calls 39. A dedicated setting allows users to dial emergency calls with or without the location's outbound dial digit 42.

Outgoing call permissions in Webex Calling classify calls into types such as internal, toll free, national, international, operator assistance, chargeable directory assistance, special services, and premium services 37. Each call type can be set to allowed, blocked, gated by an authorization code, or auto-transferred 37. Translation patterns can be defined at the organization level (up to 1,000 patterns) and the location level (up to 500 patterns per location), with location-level patterns taking precedence 59. Control Hub provides a call routing verification tool to simulate calls from a user, workspace, virtual line, or premises trunk, displaying the applied outgoing permissions, digit patterns, call intercept, and translation patterns 58.

Routing and Coexistence with Unified CM

For coexistence with Webex Calling, Cisco recommends that Unified CM normalize all dialing habits to +E.164 using translation patterns that inherit the originator's calling search space (CSS) 34. Cisco identifies +E.164 dialing, extension dialing, abbreviated inter-site dialing, forced on-net dialing, and callback from the missed calls directory as required dialing behaviors from Unified CM to Webex Calling during coexistence 1.

The Cisco coexistence design requires a dedicated Webex Calling partition in Unified CM so calls originating from Webex Calling receive a differentiated class of service 36. In Cisco's example, an urgent +E.164 route pattern matching each Webex Calling location's number range is added to this partition 35. Unified CM best-match routing ensures that a +E.164 directory number still hosted on Unified CM wins over the wildcarded +E.164 route pattern pointing at Webex Calling 32. In Cisco's example, abbreviated inter-site dialing to a Webex Calling site with site code 121 and extensions 2XXX is enabled by adding route pattern 8121.2XXX to the Webex Calling partition 31. To prevent call loops, the inbound CSS on the Unified CM trunk from the Local Gateway should not have access to the Webex Calling partition 33.

A Webex Calling dial plan consists of a set of dial patterns—such as extensions, enterprise/ESN numbers, +E.164 patterns, or SIP URI domains—that routes matching calls to on-premises destinations through a single routing choice of trunk or route group 38. Within a route group, calls are distributed randomly among trunks of identical priority and fall back to lower-priority trunks only if higher-priority trunks are unavailable 52. When premises (unknown) extension routing is enabled on a location, calls from its users to an unknown 2 to 10 digit extension are sent as premises calls to the selected trunk or route group 57.

Cisco specifies configuring trunks and local gateways first, then creating enterprise dial plans pointing at the appropriate route group, and finally migrating users in batches 5. Cisco states that enterprise dial plans should contain only the patterns needed to route calls to on-premises destinations 3. When migrating numbers, Cisco advises ordering and porting phone numbers with the provider prior to configuring them in Control Hub, and subsequently disabling or deleting the migrated directory numbers and features on Unified CM 4. Phased PSTN migrations can be complicated by providers capping concurrent port requests or restricting the porting of subsets of large number blocks 6. During configuration, the Webex Calling migration tool maps Unified CM device pools to Webex Calling locations, though this mapping can be left undefined and completed later 29.

Webex Calling routing architecture includes the following configurable limits: 53

Routing Element Maximum Limit Scope
Trunks 100 53 Per location 53
Trunks 10 53 Per route group 53
Route groups 10,000 53 Per enterprise 53
Dial plans 10,000 53 Per enterprise 53
Dial patterns 10,000 53 Per dial plan 53

Teams Dial Plan and Call Routing Architecture

Microsoft Teams structures dial plans across 3 scopes: a Microsoft-managed service dial plan per country or region, a tenant Global dial plan, and user dial plans 8. A user's effective dial plan merges the service plan with either the Global plan or an assigned user plan, never both 8. Rule evaluation hierarchy gives user rules precedence over tenant rules, which take precedence over service rules 8. A Teams tenant can contain at most 1,000 tenant dial plans 17.

Each Teams dial plan supports a maximum of 50 normalization rules 16. Normalization rules are evaluated top-down, and the first matching rule is applied, requiring more restrictive rules to be ordered above less restrictive rules 20. These rules are written as .NET Framework regular expressions defining a pattern and a translation 19. Microsoft recommends that every normalization rule output a number starting with +, because output without a leading + is normalized again by tenant and regional rules; Direct Routing customers can strip the + downstream using trunk translation rules 21. If no normalization rule matches a dialed number, the service dial plan automatically prepends +CC matching the user's usage-location country code across Calling Plans, Direct Routing, and PSTN conference dial-out 26. Dial plans can be validated using "Test dial plan" in the Teams admin center, or via the Get-CsEffectiveTenantDialPlan and Test-CsEffectiveTenantDialPlan PowerShell cmdlets against a target user 27.

For Calling Plan, Operator Connect, or Teams Phone Mobile deployments, dial plans and voice routing policies are preconfigured at the service level, whereas Direct Routing or extension dialing requires explicit configuration of voice routes and voice routing policies 7. Teams Direct Routing call routing links voice routing policies to PSTN usages, PSTN usages to voice routes, and voice routes to online PSTN gateways (SBCs) paired with number patterns 24.

The ordering of PSTN usages within a voice routing policy is significant: usages are evaluated sequentially, and once a match is found within a usage, subsequent usages are not evaluated 22. Within an individual voice route, listed SBCs are attempted in random order, with lower-priority voice routes serving as backup only when all SBCs in higher-priority routes are unreachable 25. If a Teams user has only Teams Phone and a Direct Routing policy and dials a number not matched by any voice route, the call is dropped; users who also have a Calling Plan licence fall back to Calling Plan routing 18. Microsoft cautions that configuring the global org-wide default voice routing policy causes all voice-enabled users to inherit it, which can unintentionally route Calling Plan and Operator Connect users' PSTN calls to a Direct Routing trunk 15.

For inbound Reverse Number Lookup (RNL), Direct Routing numbers can range from 3 to 38 digits, followed by an optional extension of 1 to 12 digits using ;ext= 23. A user assigned a number with an extension only matches RNL if the inbound dialed number includes that extension 23. When a called number contains ;ext=, Teams matches the voice route number pattern only against the portion preceding the extension 14. Translation rules on Direct Routing SBCs are configured via 4 gateway parameters (InboundTeams, InboundPSTN, OutboundTeams, and OutboundPSTN NumberTranslationRules), evaluated in listed order, up to a cumulative maximum of 400 translation rules 28.

Emergency Calling Considerations

Basic emergency calling in Webex Calling requires assigning at least 1 customer-owned +E.164 number to each location 40. For basic emergency calling, Webex Calling does not store or know the Emergency Service Address (ESA); the PSTN provider supplies the ESA, typically by statically mapping the received Emergency Callback Number (ECBN) 43. An ECBN can be configured as the user's own number, the location default ECBN, or the number of a user, workspace, virtual line, or hunt group located at that site 41. If the assigned number is deleted, the ECBN falls back to the user's own number or the location default 41. For US deployments requiring enhanced emergency calling, Webex Calling integrates RedSky Horizon Mobility for emergency call routing, and includes a setting allowing test calls to 933 for location verification 50.

Teams emergency call routing policies define emergency numbers and PSTN routes for Direct Routing users, whereas under Shared Calling with Calling Plans or Operator Connect they serve only to identify emergency dial strings 9. If a Direct Routing user is located at a network site associated with an emergency call routing policy, the network site's policy overrides any user-level policy assignment 10. Teams clients do not prepend a + to Direct Routing emergency dial strings, requiring voice route patterns to match the emergency string exactly 12. Emergency dial masks translate alternate dialed numbers (such as 112) into the target emergency dial string (such as 911), and each dial string and mask must be unique within a policy 11. The PSTN usage in an emergency call routing policy dictates call routing; Microsoft states that this route should point to an ELIN gateway routing to the nearest PSAP or to a SIP trunk dedicated to emergency calls 13.

See also

Applicability

Applies to: Cisco Webex Calling, Cisco Unified Communications Manager, Microsoft Teams Phone, and Microsoft Teams Phone Direct Routing. Deployments: on-premises and multi-tenant. Sources checked 2026-09-25. The enhanced emergency calling integration with RedSky Horizon Mobility applies specifically to US region deployments 50.

What remains uncertain

Vendor-stated mapping of Unified CM partitions and CSS to Webex Calling call permissions and digit pattern permissions is not covered by the sources below. Teams dynamic emergency calling and LIS setup for sites moved off Unified CM ELIN is not covered by the sources below. Unified CM to Teams coexistence trunk design via Cisco Unified Border Element (CUBE), including extension dialing and loop avoidance on the Teams side, is not covered by the sources below. Details from a re-read of the dial plan chapter of the Cisco Unified CM to Webex Calling transitioning PDF are not covered by the sources below. Teams unassigned number routing for DID blocks only partly moved from Unified CM is not covered by the sources below. The interplay of outbound dial digit settings with US MLTS direct-dial 911 rules is not covered by the sources below. Webex Calling dial plan and dial pattern API or CSV bulk upload capabilities for migrating large route pattern sets are not covered by the sources below. Webex Calling virtual extensions as a routing target for Unified CM extensions that stay on premises are not covered by the sources below.

See also

Related to

  • Emergency callback numbers in Webex Calling — Emergency callback number design is a required step of the Webex Calling location dial plan; this packet only covers ECBN as far as the migration design guide and ECBN article state it
  • SIP trunk redundancy and failover design — Webex Calling route group trunk priority and Teams voice route SBC priority are the target-side redundancy constructs a migrated route list maps onto
  • Teams location-based routing — Teams network sites carry emergency call routing policies and location-based routing; LBR itself is not researched here

Referenced by

  • UC licensing models compared — Licence choice (user versus workspace versus common area) decides which dial-plan objects exist after a migration

Sources

  1. 1
    Cisco lists +E.164 dialing, extension dialing, abbreviated inter-site dialing, forced on-net dialing and callback from the missed calls directory as dialing behaviours that must work from Unified CM to Webex Calling during coexistence.
    Design to migrate from Unified CM to Webex Calling · Coexistence dial plan; Unified CM to Webex Calling requirements list · Checked 2026-09-25
  2. 2
    Class-of-service restrictions that Unified CM expresses through partitions and calling search spaces have to be re-expressed in Webex Calling as outgoing call permissions set at location, user, workspace or virtual line level, because Webex Calling has no partition or CSS construct in the sources reviewed.inferred
    Configure call permissions in Control Hub · Configuration levels; digit pattern permissions · Checked 2026-09-25
  3. 3
    Cisco says Webex Calling enterprise dial plans should contain only the patterns needed to route calls to on-premises destinations.
    Implement the migration from Unified CM to Webex Calling · Configure trunks, route groups and dial plans step · Checked 2026-09-25
  4. 4
    Cisco advises ordering and porting phone numbers with the provider before configuring them in Control Hub, and disabling or deleting the migrated directory numbers and features on Unified CM afterwards.
    Implement the migration from Unified CM to Webex Calling · Number porting step; post-migration Unified CM cleanup · Checked 2026-09-25
  5. 5
    Cisco's implementation sequence is to set up trunks and local gateways first, then create enterprise dial plans pointing at the right route group, and only then migrate users in batches.
    Implement the migration from Unified CM to Webex Calling · Configure trunks, route groups and dial plans step · Checked 2026-09-25
  6. 6
    Cisco warns that providers may cap concurrent port requests or restrict porting subsets of large number blocks, which complicates phased PSTN migration.
    Design to migrate from Unified CM to Webex Calling · PSTN design; number porting challenges paragraph · Checked 2026-09-25
  7. 7
    With Calling Plan, Operator Connect or Teams Phone Mobile, dial plans and voice routing policies are preconfigured at the service level; Direct Routing or extension dialing needs extra configuration of voice routes and voice routing policies.
    Microsoft Teams Dial plans for phone call routing · User dial plans with Calling Plans and Operator Connect; User dial plans with Direct Routing or extension dialing · Checked 2026-09-25
  8. 8
    Teams has three dial plan scopes: a Microsoft-managed service dial plan per country or region, a tenant Global dial plan and user dial plans. A user's effective dial plan merges the service plan with either the Global or an assigned user plan, never both, and user rules take precedence over tenant rules, which take precedence over service rules.
    Microsoft Teams Dial plans for phone call routing · Dial plan scopes and a user's effective dial plan · Checked 2026-09-25
  9. 9
    Teams emergency call routing policies define emergency numbers and their PSTN routes for Direct Routing; with Shared Calling on Calling Plans or Operator Connect they only identify emergency numbers.
    Manage emergency call routing policies for Direct Routing · Introduction and first Note · Checked 2026-09-25
  10. 10
    If a Direct Routing user is at a network site that has an emergency call routing policy, the site's policy overrides the policy assigned to the user.
    Manage emergency call routing policies for Direct Routing · Introduction; paragraph on network site versus user assignment · Checked 2026-09-25
  11. 11
    A Teams emergency dial mask translates alternate emergency numbers such as 112 into the configured emergency dial string such as 911, and every dial string and dial mask must be unique within a policy.
    Manage emergency call routing policies for Direct Routing · Create a custom emergency call routing policy; step 5.2 Emergency dial mask and Note · Checked 2026-09-25
  12. 12
    For Direct Routing, Teams clients no longer put + in front of the emergency dial string, and the voice route pattern must match the emergency dial string exactly.
    Manage emergency call routing policies for Direct Routing · Create a custom emergency call routing policy; step 5.1 Emergency dial string and Note · Checked 2026-09-25
  13. 13
    The PSTN usage in a Teams emergency call routing policy selects the route for emergency calls, and Microsoft says that route should point to a SIP trunk dedicated to emergency calls or to an ELIN gateway that routes to the nearest PSAP.
    Manage emergency call routing policies for Direct Routing · Create a custom emergency call routing policy; step 5.3 PSTN usage record · Checked 2026-09-25
  14. 14
    When a Teams called number contains ;ext=, the voice route number pattern is matched only against the number without the extension.
    Configure call routing for Direct Routing · Voice routing policy considerations; Caution item 2 · Checked 2026-09-25
  15. 15
    Microsoft cautions that configuring the global (org-wide default) online voice routing policy makes every voice-enabled user inherit it, which can unintentionally route Calling Plan and Operator Connect users' PSTN calls to a Direct Routing trunk.
    Configure call routing for Direct Routing · Voice routing policy considerations; Caution item 1 · Checked 2026-09-25
  16. 16
    Microsoft enforces a maximum of 50 normalization rules in a Teams dial plan.
    Normalization rules for Microsoft Teams dial plans · Introductory note after matching-order paragraph · Checked 2026-09-25
  17. 17
    A Teams tenant can have at most 1,000 tenant dial plans.
    Microsoft Teams Dial plans for phone call routing · Dial plans and routing considerations · Checked 2026-09-25
  18. 18
    A Teams user with only Teams Phone and a Direct Routing policy whose number is not matched by any voice route has the call dropped; a user who also has a Calling Plan licence falls back to Calling Plan routing.
    Configure call routing for Direct Routing · Example 1 notes; Voice routing policy considerations · Checked 2026-09-25
  19. 19
    Teams normalization rules are written as .NET Framework regular expressions with a pattern and a translation.
    Normalization rules for Microsoft Teams dial plans · Creating normalization rules · Checked 2026-09-25
  20. 20
    Teams normalization rules are evaluated top-down and the first matching rule is used, so more restrictive rules must be ordered above less restrictive ones.
    Normalization rules for Microsoft Teams dial plans · Introductory section on rule matching order · Checked 2026-09-25
  21. 21
    Microsoft recommends that every Teams normalization rule produce a number starting with +, because output without + is normalized again by tenant and regional rules; Direct Routing customers can strip the + later with trunk translation rules.
    Create and manage dial plans · Using the Teams admin center; Create a dial plan, step 4 note · Checked 2026-09-25
  22. 22
    The order of PSTN usages in a Teams voice routing policy is significant: usages are evaluated in order, and once a match is found in one usage the later usages are never evaluated.
    Configure call routing for Direct Routing · Example 2: Voice routing with multiple PSTN usages; note under summary table · Checked 2026-09-25
  23. 23
    For Teams inbound Reverse Number Lookup, Direct Routing numbers can be 3 to 38 digits, an optional extension of 1 to 12 digits can follow ;ext=, and a number assigned with an extension only matches if the inbound dialed number includes that extension.
    Microsoft Teams Dial plans for phone call routing · Number lookup for inbound calls · Checked 2026-09-25
  24. 24
    Teams Direct Routing call routing is built from voice routing policies that contain PSTN usages, PSTN usages that contain voice routes, and voice routes that pair a number pattern with online PSTN gateways (SBCs).
    Configure call routing for Direct Routing · Call routing overview; element list · Checked 2026-09-25
  25. 25
    In Teams voice routes, the SBCs listed within a route are tried in random order, while lower-priority routes act as backup only when the SBCs of higher-priority routes are unavailable.
    Configure call routing for Direct Routing · Example 1: Voice routing with one PSTN usage · Checked 2026-09-25
  26. 26
    If a user's effective Teams dial plan applies no normalization rule to a dialed number, the service dial plan prepends +CC for the user's usage-location country code; this applies to Calling Plans, Direct Routing and PSTN conference dial-out.
    Translate phone numbers for Direct Routing · Route-based number translations - for outbound calls; Note · Checked 2026-09-25
  27. 27
    Teams dial plans can be tested in the Teams admin center with Test dial plan, or in PowerShell with Get-CsEffectiveTenantDialPlan and Test-CsEffectiveTenantDialPlan against a specific user.
    Create and manage dial plans · Create a dial plan step 6; Using single cmdlets · Checked 2026-09-25
  28. 28
    Teams Direct Routing number translation rules are applied per SBC through four gateway parameters (InboundTeams, InboundPSTN, OutboundTeams and OutboundPSTN NumberTranslationRules), in listed order, with a maximum of 400 translation rules in total.
    Translate phone numbers for Direct Routing · Considerations; Configuring translation rules with PowerShell · Checked 2026-09-25
  29. 29
    The Webex Calling migration tool maps Unified CM device pools to Webex Calling locations, and the mapping can be left undefined and completed later.
    Migrate Unified CM data to Webex Calling · Location mapping step · Checked 2026-09-25
  30. 30
    The Cisco migration tool article describes migrating users, devices, numbers and locations but does not describe migrating partitions, calling search spaces, route patterns or translation patterns, so the dial plan is likely rebuilt by hand.inferred
    Migrate Unified CM data to Webex Calling · Whole article; scope of migrated objects · Checked 2026-09-25
  31. 31
    In the Cisco example, abbreviated inter-site dialing to a Webex Calling site with site code 121 and extensions 2XXX is enabled by adding route pattern 8121.2XXX to the Webex Calling partition.
    Design to migrate from Unified CM to Webex Calling · Coexistence dial plan; abbreviated inter-site dialing example · Checked 2026-09-25
  32. 32
    Unified CM best-match routing ensures that a +E.164 directory number still hosted on Unified CM wins over the wildcarded +E.164 route pattern that points a migrating range at Webex Calling.
    Design to migrate from Unified CM to Webex Calling · Coexistence dial plan; best match paragraph · Checked 2026-09-25
  33. 33
    To avoid call loops, the inbound calling search space on the Unified CM trunk from the Local Gateway should not have access to the Webex Calling partition.
    Design to migrate from Unified CM to Webex Calling · Coexistence dial plan; trunk calling search space paragraph · Checked 2026-09-25
  34. 34
    For coexistence, Cisco recommends that Unified CM normalise all dialing habits to +E.164 using translation patterns that inherit the originator's calling search space.
    Design to migrate from Unified CM to Webex Calling · Coexistence dial plan; Unified CM dial plan assumptions (normalization and Use originator's calling search space) · Checked 2026-09-25
  35. 35
    In the Cisco coexistence example, an urgent +E.164 route pattern matching each Webex Calling location's number range is added to the Webex Calling partition in Unified CM.
    Design to migrate from Unified CM to Webex Calling · Coexistence dial plan; example location +1 221 555 2XXX with site code 121 · Checked 2026-09-25
  36. 36
    The Cisco coexistence design requires a dedicated Webex Calling partition in Unified CM so that calls originating from Webex Calling can be given a differentiated class of service.
    Design to migrate from Unified CM to Webex Calling · Coexistence dial plan; Webex Calling partition paragraph · Checked 2026-09-25
  37. 37
    Webex Calling outgoing call permissions classify calls into types such as internal, toll free, national, international, operator assistance, chargeable directory assistance, special services and premium services, and each can be allowed, blocked, gated by an authorization code or auto-transferred.
    Configure call permissions in Control Hub · Outgoing call permissions; call type list and actions · Checked 2026-09-25
  38. 38
    A Webex Calling dial plan is a set of dial patterns (extensions, enterprise/ESN numbers, +E.164 patterns or SIP URI domains) that routes matching calls to on-premises destinations through a single routing choice of trunk or route group.
    Configure trunks, route groups, and dial plans for Webex Calling · Dial plans section; dial pattern definitions · Checked 2026-09-25
  39. 39
    Webex Calling ignores the outbound dial digit requirement for outbound calls dialed in E.164 format, and Cisco highly recommends E.164 for incoming and outgoing PSTN calls.
    Configure your Webex Calling dial plan · External dialing settings; E.164 recommendation note · Checked 2026-09-25
  40. 40
    Basic emergency calling in Webex Calling requires at least one customer-owned +E.164 number to be assigned to each location.
    Design to migrate from Unified CM to Webex Calling · Emergency calling design; basic emergency calling · Checked 2026-09-25
  41. 41
    A Webex Calling ECBN can be the user's own number, the location default ECBN, or a user, workspace, virtual line or hunt group number in the location, and falls back to the user's own number or the location default if the chosen number is deleted.
    Emergency Callback Number (ECBN) in Control Hub · ECBN configuration options; fallback behaviour · Checked 2026-09-25
  42. 42
    Webex Calling has a setting that lets users dial emergency calls with or without the location's outbound dial digit.
    Configure your Webex Calling dial plan · External dialing settings; emergency call option · Checked 2026-09-25
  43. 43
    For basic emergency calling, Webex Calling does not know or store the Emergency Service Address; the PSTN provider supplies it, typically by statically mapping the ECBN it receives.
    Emergency Callback Number (ECBN) in Control Hub · ECBN overview; Emergency Service Address note · Checked 2026-09-25
  44. 44
    The default Webex Calling internal extension length is 4 digits.
    Configure your Webex Calling dial plan · Internal dialing settings; Extension length · Checked 2026-09-25
  45. 45
    Configuring location extensions whose length differs from the global Webex Calling extension length triggers a Control Hub warning, and dialing from phones may then require en-bloc dialing.
    Design to migrate from Unified CM to Webex Calling · Dial plan design; extension length paragraph · Checked 2026-09-25
  46. 46
    In Webex Calling all extensions in a deployment have the same length, and the internal extension length can be set to any value from two to ten digits.
    Design to migrate from Unified CM to Webex Calling · Dial plan design; extension length paragraph and Internal extension length parameter · Checked 2026-09-25
  47. 47
    Abbreviated extension dialing between Webex Calling locations works only if the dialed extension is unique across the organisation, and the Allow extension dialing between locations toggle should only be enabled when all extensions are unique.
    Design to migrate from Unified CM to Webex Calling · Dial plan design; inter-location dialing paragraph and Allow extension dialing between locations parameter · Checked 2026-09-25
  48. 48
    A Webex Calling location's outbound dial digit defaults to none, and the admin can optionally enforce that users dial it.
    Configure your Webex Calling dial plan · External dialing settings; Outbound dial digit and enforcement option · Checked 2026-09-25
  49. 49
    The Webex Calling location routing prefix length setting counts the steering digit as part of the prefix.
    Design to migrate from Unified CM to Webex Calling · Dial plan design; calling service settings parameter table (Location routing prefix length) · Checked 2026-09-25
  50. 50
    For US deployments that need enhanced emergency calling, Webex Calling uses RedSky Horizon Mobility integrated into Webex Calling for emergency call routing, and a setting allows test calls to 933 for location verification.
    Design to migrate from Unified CM to Webex Calling · Emergency calling design; enhanced emergency calling with RedSky · Checked 2026-09-25
  51. 51
    After a Webex Calling dialing preference change, users must restart their phones for it to take effect.
    Configure your Webex Calling dial plan · Closing note on dialing preference changes · Checked 2026-09-25
  52. 52
    Within a Webex Calling route group, calls are distributed randomly among trunks of the same priority and fall back to lower-priority trunks only when the higher-priority trunks are unavailable.
    Configure trunks, route groups, and dial plans for Webex Calling · Route groups section; trunk priority example · Checked 2026-09-25
  53. 53
    Webex Calling allows up to 100 trunks per location, 10 trunks per route group, 10,000 route groups and 10,000 dial plans per enterprise, and 10,000 dial patterns per dial plan.
    Configure trunks, route groups, and dial plans for Webex Calling · Configurable limits table · Checked 2026-09-25
  54. 54
    The Webex Calling location routing prefix can be 1 to 7 digits long, and users must dial it when multiple locations share the same extension.
    Configure your Webex Calling dial plan · Internal dialing settings; Location routing prefix · Checked 2026-09-25
  55. 55
    Where extensions overlap across sites, the Cisco design guidance is to build an enterprise numbering plan that prefixes extensions with an access code and a site code.
    Design to migrate from Unified CM to Webex Calling · Dial plan design; enterprise numbering plan paragraph · Checked 2026-09-25
  56. 56
    Cisco advises that the Webex Calling steering digit should not overlap the first digit of any location extension or any location outbound dial digit.
    Design to migrate from Unified CM to Webex Calling · Dial plan design; parameter table, Steering digit in routing prefix · Checked 2026-09-25
  57. 57
    When premises (unknown) extension routing is enabled on a Webex Calling location, calls from its users to an unknown 2-10 digit extension are sent as premises calls to the selected trunk or route group.
    Configure trunks, route groups, and dial plans for Webex Calling · Unknown extension routing section · Checked 2026-09-25
  58. 58
    Control Hub has a call routing verification tool that simulates a call from a user, workspace, virtual line or premises trunk and shows the outgoing permissions, digit patterns, call intercept and translation patterns applied.
    Configure trunks, route groups, and dial plans for Webex Calling · Verify call routing section · Checked 2026-09-25
  59. 59
    Webex Calling translation patterns can be defined at organisation level (up to 1000) and location level (up to 500 per location), and location-level patterns take precedence.
    Translation patterns for outbound calls · Overview; organisation and location levels · Checked 2026-09-25
  60. 60
    Webex Calling translation patterns apply to outbound and redirected calls, including transfers and forwards, but not to emergency calls, repair calls or call center callbacks.
    Translation patterns for outbound calls · Overview; calls to which translation patterns apply · Checked 2026-09-25

Documents

tier 2 current vendor documentation

Configure call permissions in Control Hub

Cisco Systems · 2025-01-10 · accessed 2026-09-05

tier 2 current vendor documentation

Configure call routing for Direct Routing

Microsoft · 2026-09-10 · accessed 2026-09-21

tier 2 current vendor documentation

Configure trunks, route groups, and dial plans for Webex Calling

Cisco Systems, Inc. (Webex Help Center) · 2026-09-07 · accessed 2026-09-16

tier 2 current vendor documentation

Configure your Webex Calling dial plan

Cisco Systems · 2026-04-22 · accessed 2026-09-25

tier 2 current vendor documentation

Create and manage dial plans

Microsoft · 2025-04-25 · accessed 2026-09-21

tier 2 current vendor documentation

Design to migrate from Unified CM to Webex Calling

Cisco Systems, Inc. (Webex Help Center) · accessed 2026-09-16

tier 2 current vendor documentation

Emergency Callback Number (ECBN) in Control Hub

Cisco Systems, Inc. (help.webex.com) · 2025-04-01 · accessed 2026-09-16

tier 2 current vendor documentation

Implement the migration from Unified CM to Webex Calling

Cisco Systems, Inc. (Webex Help Center) · accessed 2026-09-16

tier 2 current vendor documentation

Manage emergency call routing policies for Direct Routing

Microsoft · 2025-04-25 · accessed 2026-09-24

tier 2 current vendor documentation

Microsoft Teams Dial plans for phone call routing

Microsoft · 2025-08-11 · accessed 2026-09-23

tier 2 current vendor documentation

Migrate Unified CM data to Webex Calling

Cisco Systems, Inc. (Webex Help Center) · 2026-04-27 · accessed 2026-09-04

tier 2 current vendor documentation

Normalization rules for Microsoft Teams dial plans

Microsoft · 2025-08-11 · accessed 2026-09-23

tier 2 current vendor documentation

Translate phone numbers for Direct Routing

Microsoft · 2026-09-10 · accessed 2026-09-21

tier 2 current vendor documentation

Translation patterns for outbound calls

Cisco Systems · 2026-05-11 · accessed 2026-09-25

Cite this page

APA

WarmTransfer. (2026, September 25). Migrating a Unified CM dial plan to Webex Calling or Teams. WarmTransfer. https://warmtransfer.net/knowledge/dial-plan-migration

BibTeX

@misc{warmtransfer-dial-plan-migration,
  title  = {Migrating a Unified CM dial plan to Webex Calling or Teams},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/dial-plan-migration},
  note   = {Verified 2026-09-25}
}