WarmTransfer
cisco onprem uc · published

Troubleshooting Unified CM call routing failures and reorder tone

Verified 2026-09-30 · 54 sources · tier 2–5

Call routing failures in Cisco Unified Communications Manager (Unified CM) frequently manifest as a reorder or fast busy tone played to the calling device 34. These failures typically stem from dial plan configuration issues—such as calling search space mismatches or exhausted partitions—or runtime resource constraints like location bandwidth limits 34​33.

Dial plan structure and digit analysis

A calling search space (CSS) is an ordered list of partitions that defines which partitions a calling device can search during call setup 7. For calls originating from a Cisco IP phone line, Unified CM searches the partitions configured on both the line CSS and the device CSS 23. When both are present, the line CSS takes precedence over the device CSS 22. In Cisco's Collaboration 14 preferred architecture, class of service is defined using the line CSS only, leaving the device CSS unused for class of service 30.

When dialed digits match a pattern residing in a partition outside the calling device's CSS, digit analysis identifies no potential match, causing the phone to play a reorder tone 34. Cisco identifies hearing reorder tone either before or after dialing the full number as a symptom of partition and CSS misconfiguration 35. In testing dialed numbers, Cisco advises waiting at least 10 seconds following the final digit, as the call may be awaiting the expiration of an interdigit timer 21.

Any dial plan entry or device left without an assigned partition resides in the Null (or <None>) partition 28. The Null partition is reachable by every device regardless of CSS, and Unified CM always searches it last after evaluating the partitions in the device's CSS 28​27. Because any calling device can access entries in the <None> partition, Cisco advises against leaving dial plan entries there to avoid unexpected call routing 26. Dial plan items can also be scheduled: time-of-day routing binds time schedules to partitions, controlling which partitions are searchable at a given time 43.

Patterns, route lists, and routing logic

When dialed digits match a translation pattern, Unified CM alters the digits and performs a second routing lookup using the CSS assigned to that translation pattern 53. WarmTransfer's reading of the sources is that if the translation pattern's CSS omits the target destination's partition, the call fails after translation even when the caller's CSS reached the initial translation pattern 52. In the Collaboration 14 preferred architecture, dialing normalization translation patterns are configured with "Use Originator's Calling Search Space" so the secondary lookup retains the primary lookup's CSS, and are marked urgent to match immediately without waiting for additional digits 54​31.

Outbound routing relies on route lists, which are prioritized lists of one or more route groups; route groups distribute calls across member gateways and trunks in configured order 41. During an outbound call through a route list, the route list process locks the outbound device so no alert message is sent before call setup completes 40. Local route groups allow a single set of route patterns to serve multiple locations by deriving the egress gateway from the calling device 25. WarmTransfer's reading of the sources is that because local route groups resolve per originating device, a pattern routing successfully from one site can fail from another site if that site's device pool maps the local route group to an empty or different route group 24.

Route filters can be used with route patterns, but they apply strictly to patterns containing the @ wildcard 38. Cisco warns that modifying a route filter shared across hundreds of route patterns can trigger a system core crash, and recommends creating duplicate route filters instead 39.

See also Unified CM dial plan partitions and calling search spaces.

See also Unified CM route patterns and partitions configuration.

Non-dial plan causes of reorder tone

Reorder tone after dialing can mean that the location bandwidth allocation for one of the call's endpoints was exceeded, because Unified CM will not set up a call when no bandwidth is available 33.

In call detail records (CDRs), call termination cause codes reflect the underlying failure reasons 1​3​4​2​5:

Cause Code Description
1 Unallocated (unassigned) number 1
3 No route to destination 3
34 No circuit/channel available 4
41 Temporary failure 4
125 Out of bandwidth (Cisco-specific) 2
1107296281 (0x42000019) CCM_SIP_482_LOOP_DETECTED (SIP 482 Loop Detected) 5

Testing with Dialed Number Analyzer

Cisco positions Dialed Number Analyzer (DNA) as the tool for analyzing dial plans involving devices, translation patterns, route patterns, route lists, route groups, and calling and called party transformations prior to deployment 16. Cisco's DNA call-routing tech note states it is based on Unified CM versions 12.x, 14.x, and 15.x 19.

DNA requires the activation of two feature services in Cisco Unified Serviceability under Tools > Service Activation: Cisco Dialed Number Analyzer and Cisco Dialed Number Analyzer Server 8. Because DNA consumes significant resources, Cisco warns that it should be activated only during off-peak hours 14. Cisco does not recommend activating Dialed Number Analyzer on all cluster nodes, and recommends a single node with the least call-processing activity, with the Cisco Dialed Number Analyzer Server service needing activation only on that dedicated node 12​17.

Once running, DNA is accessed in a web browser at https://<cucm-ip-or-fqdn>/dna 18. The DNA Analysis menu contains:

  • Analyzer 9
  • Gateways 9
  • Phones 9
  • Trunks 9
  • Dump DA Information 9
  • Multiple Analyzer 9
  • View File 9

The Analyzer takes dialed digits (including SIP URIs formatted as sip:<uri>), CSS, and time, allowing simulation of a specific class of service at a particular time 10. DNA output provides a summary showing the calling and called numbers, a match result (such as RouteThisPattern), matched pattern details, and an end-to-end call flow showing applied translation and route patterns 15. WarmTransfer's reading of the sources is that if DNA produces a successful route result for a given CSS, time, and digit string but a live call receives reorder tone, the failure is more likely due to runtime state (such as bandwidth exhaustion, codec/region mismatches, far-end rejections, or trunk availability) rather than partition or CSS design 13.

Trace collection and analysis

For dialing issues, Cisco's diagnostic procedure incorporates the Route Plan Report to review all route patterns in partitions reachable from the calling CSS 42. Detailed tracing is enabled by default for the Cisco CallManager service from Unified CM 9.x onward, and Cisco's procedure sets the Debug Trace Level to Detailed 44. From Unified CM 9.x, SDI and SDL trace messages are combined into a single interleaved file set 45.

Traces are gathered using the Cisco Unified Real-Time Monitoring Tool (RTMT) under System > Tools > Trace & Log Central > Collect Files across all cluster nodes for Cisco CallManager and CTIManager services 50. Cisco recommends setting an absolute collection time window spanning from 1 minute prior to the first test call to 1 minute after the last, documenting the calling number, called number, start time, and end time for each call 51.

In Unified CM call-processing traces, the digit analysis match line includes a pss field displaying the partition search space (the calling search space) of the originating device 47. If no reachable pattern matches the dialed digits, digit analysis outputs potentialMatches=NoPotentialMatchesExist 46. In the field, practitioners trace egress device selection through the RouteListControl and RouteListCdrc processes following digit analysis 49.

See also CUCM CallManager SDL trace files.

Applicability

Applies to: Cisco Unified Communications Manager. Deployments: on-premises. Sources checked 2026-09-30. Cisco's Dialed Number Analyzer call-routing tech note states it is based on Unified CM versions 12.x, 14.x, and 15.x 19. Detailed tracing is enabled by default for the Cisco CallManager service from Unified CM 9.x onward 44.

What remains uncertain

Route list reroute rules and the default values for the Stop Routing on User Busy, Unallocated Number, and Out of Bandwidth flags are not covered by the sources below. Route list hunting on SIP trunk responses is not covered by the sources below. RouteListExhausted alarm and RTMT alert definitions are not covered by the sources below. Unified CM's internal translation pattern loop limit and the rejection mechanism for looping calls are not covered by the sources below. The currency of dial plan troubleshooting guidance in the Release 15 troubleshooting guide is not covered by the sources below. DNA operational limitations versus runtime state, including registration, bandwidth, and route group availability, are not covered by the sources below. The behavior of the "Block this pattern" route pattern option and the release cause presented to callers are not covered by the sources below. The Digit Analysis Complexity service parameter and its impact on translation and alternate match tracing are not covered by the sources below.

Sources

  1. 1
    In Unified CM CDRs, call termination cause code 1 means Unallocated (unassigned) number.
    Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager Release 15 and SUs, CDR Field Descriptions · CDR Field Descriptions > Table 4 Call Termination Cause Codes, code 1 · Checked 2026-09-30
  2. 2
    In Unified CM CDRs, cause code 125 is the Cisco-specific Out of bandwidth code.
    Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager Release 15 and SUs, CDR Field Descriptions · CDR Field Descriptions > Table 4 Call Termination Cause Codes, code 125 · Checked 2026-09-30
  3. 3
    In Unified CM CDRs, cause code 3 means No route to destination.
    Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager Release 15 and SUs, CDR Field Descriptions · CDR Field Descriptions > Table 4 Call Termination Cause Codes, code 3 · Checked 2026-09-30
  4. 4
    In Unified CM CDRs, cause code 34 means No circuit/channel available, and cause code 41 means Temporary failure.
    Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager Release 15 and SUs, CDR Field Descriptions · CDR Field Descriptions > Table 4 Call Termination Cause Codes, codes 34 and 41 · Checked 2026-09-30
  5. 5
    Unified CM's Cisco-specific cause code table includes 1107296281 (0x42000019), CCM_SIP_482_LOOP_DETECTED, for a SIP 482 Loop Detected response.
    Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager Release 15 and SUs, CDR Field Descriptions · CDR Field Descriptions > Table 5 Cisco-Specific Call Termination Cause Codes, 1107296281 · Checked 2026-09-30
  6. 6
    When several patterns match the dialed digits, Unified CM picks the closest (most specific) match, and the partition order in the CSS breaks ties between equally specific patterns.
    Preferred Architecture for Cisco Collaboration 14 Enterprise On-Premises Deployments, CVD - Call Control · Call Control > dial plan (closest match discussion) · Checked 2026-09-30
  7. 7
    A calling search space is an ordered list of partitions that determines which partitions a calling device searches when it attempts to complete a call.
    Configure Partition and Calling Search Space · Configure Partition and Calling Search Space > Background / partitions and CSS definitions · Checked 2026-09-30
  8. 8
    Dialed Number Analyzer needs two feature services activated in Cisco Unified Serviceability under Tools > Service Activation: Cisco Dialed Number Analyzer and Cisco Dialed Number Analyzer Server.
    Troubleshoot Call Routing Issue via CUCM Dialed Number Analyzer · Configure > activation steps · Checked 2026-09-30
  9. 9
    The Dialed Number Analyzer Analysis menu offers Analyzer, Gateways, Phones, Trunks, Dump DA Information, Multiple Analyzer and View File.
    Troubleshoot Call Routing Issue via CUCM Dialed Number Analyzer · Configure > Analysis menu options · Checked 2026-09-30
  10. 10
    The Analyzer takes dialed digits (including a SIP URI entered as sip:<uri>), and lets the tester choose the calling search space and time, so a test can be run as a specific class of service at a specific time.
    Troubleshoot Call Routing Issue via CUCM Dialed Number Analyzer · Configure > Analyzer input page · Checked 2026-09-30
  11. 11
    Dialed Number Analyzer evaluates the configured dial plan by simulation and does not place a real call.
    Troubleshoot Call Routing Issue via CUCM Dialed Number Analyzer · Introduction / Benefits (verifying dial plan without live calls) · Checked 2026-09-30
  12. 12
    Cisco does not recommend activating Dialed Number Analyzer on all cluster nodes, and recommends a single node with the least call-processing activity.
    Administration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Services · Services > Cisco Dialed Number Analyzer · Checked 2026-09-30
  13. 13
    If Dialed Number Analyzer returns a route result for the same digits, CSS and time but the live call still gets reorder, the cause is more likely runtime state (location bandwidth, codec or region, gateway or trunk availability, far-end rejection) than partition or CSS configuration.inferred
    Troubleshoot Call Routing Issue via CUCM Dialed Number Analyzer · Introduction / Benefits; read with Device Issues chapter reorder items · Checked 2026-09-30
  14. 14
    Cisco warns that Dialed Number Analyzer consumes a lot of resources when active and should be activated only during off-peak hours.
    Administration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Services · Services > Cisco Dialed Number Analyzer · Checked 2026-09-30
  15. 15
    Analyzer results show a result summary with calling and called number, a match result such as RouteThisPattern, matched pattern information, and a call flow listing the translation and route patterns applied.
    Troubleshoot Call Routing Issue via CUCM Dialed Number Analyzer · Verify / results section · Checked 2026-09-30
  16. 16
    In Release 15, Cisco positions Dialed Number Analyzer as the troubleshooting tool for dial plans that involve devices, translation patterns, route patterns, route lists, route groups and calling and called party transformations, usable before deployment.
    System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Call Routing · Configure Call Routing > Troubleshooting with Dialed Number Analyzer · Checked 2026-09-30
  17. 17
    The Cisco Dialed Number Analyzer Server service needs activating only on the node dedicated to the Cisco Dialed Number Analyzer service.
    Administration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Services · Services > Cisco Dialed Number Analyzer Server · Checked 2026-09-30
  18. 18
    Once activated, Dialed Number Analyzer is reached in a browser at https://<cucm-ip-or-fqdn>/dna.
    Troubleshoot Call Routing Issue via CUCM Dialed Number Analyzer · Configure > access after activation · Checked 2026-09-30
  19. 19
    Cisco's Dialed Number Analyzer call-routing tech note states it is based on Unified CM versions 12.x, 14.x and 15.x.
    Troubleshoot Call Routing Issue via CUCM Dialed Number Analyzer · Components Used · Checked 2026-09-30
  20. 20
    For reorder on gateway calls, Cisco lists restricted or blocked numbers, out-of-service numbers and PSTN equipment problems as causes, and advises an SDI trace plus review of the Q.931 disconnect.
    Troubleshooting Guide for Cisco Unified Communications Manager Release 12.5(1) — Device Issues · Device Issues > Gateway reorder tone · Checked 2026-09-30
  21. 21
    When testing a dialing problem, Cisco advises waiting at least 10 seconds after the last digit because the call may be waiting for the interdigit timer to expire.
    Troubleshooting Guide for Cisco Unified Communications Manager, Release 12.5(1) - Dial Plans and Routing Issues · Dial Plans and Routing Issues > Problem When Dialing a Number, step 6 · Checked 2026-09-30
  22. 22
    Where an IP phone has both a line CSS and a device CSS, the line CSS takes precedence over the device CSS.
    Configure Partition and Calling Search Space · Configure Partition and Calling Search Space > CSS discussion (line and device CSS) · Checked 2026-09-30
  23. 23
    For a call from a Cisco IP phone line, Unified CM searches the partitions of both the line calling search space and the device calling search space.
    Troubleshooting Guide for Cisco Unified Communications Manager, Release 12.5(1) - Dial Plans and Routing Issues · Dial Plans and Routing Issues > Problem When Dialing a Number, step 3 · Checked 2026-09-30
  24. 24
    Because a local route group resolves per originating device, a pattern that routes correctly from one site can fail from another site whose device pool maps the local route group to a different or empty route group.inferred
    Preferred Architecture for Cisco Collaboration 14 Enterprise On-Premises Deployments, CVD - Call Control · Call Control > Local Route Group · Checked 2026-09-30
  25. 25
    Local route groups let a single set of route patterns serve multiple locations by choosing the egress gateway from the calling device.
    System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Call Routing · Configure Call Routing > Configure Local Route Groups · Checked 2026-09-30
  26. 26
    Cisco advises against leaving dial plan entries in the <None> partition because any calling device can reach them, which can produce unexpected routing.
    Configure Partition and Calling Search Space · Configure Partition and Calling Search Space > partitions discussion (<None> partition) · Checked 2026-09-30
  27. 27
    Unified CM always searches the Null partition last, after the partitions in the caller's CSS.
    Troubleshooting Guide for Cisco Unified Communications Manager, Release 12.5(1) - Dial Plans and Routing Issues · Dial Plans and Routing Issues > Problem When Dialing a Number, step 14 · Checked 2026-09-30
  28. 28
    A pattern or device left in no partition (the Null or <None> partition) is reachable by every calling device regardless of its CSS.
    Troubleshooting Guide for Cisco Unified Communications Manager, Release 12.5(1) - Dial Plans and Routing Issues · Dial Plans and Routing Issues > Problem When Dialing a Number, step 14 · Checked 2026-09-30
  29. 29
    The Max Forward UnRegistered Hops to DN service parameter is Cisco's guard against call forward unregistered (CFUR) loops.
    Preferred Architecture for Cisco Collaboration 14 Enterprise On-Premises Deployments, CVD - Call Control · Call Control > call forward unregistered · Checked 2026-09-30
  30. 30
    Cisco's Collaboration 14 preferred architecture defines class of service with the line CSS only and does not use the device CSS for class of service.
    Preferred Architecture for Cisco Collaboration 14 Enterprise On-Premises Deployments, CVD - Call Control · Call Control > class of service · Checked 2026-09-30
  31. 31
    The Collaboration 14 preferred architecture marks dialing normalization translation patterns as urgent so they match without waiting for more digits.
    Preferred Architecture for Cisco Collaboration 14 Enterprise On-Premises Deployments, CVD - Call Control · Call Control > dial plan > dialing normalization · Checked 2026-09-30
  32. 32
    Cisco lists a codec disagreement between regions, where the two call ends share no common codec and no transcoder is available, as a cause of reorder tone.
    Troubleshooting Guide for Cisco Unified Communications Manager Release 12.5(1) — Device Issues · Device Issues > Codec and Region Mismatches · Checked 2026-09-30
  33. 33
    Reorder tone after dialing can mean that the location bandwidth allocation for one of the call's endpoints was exceeded, because Unified CM will not set up a call when no bandwidth is available.
    Troubleshooting Guide for Cisco Unified Communications Manager Release 12.5(1) — Device Issues · Device Issues > Location and Bandwidth (reorder tone) · Checked 2026-09-30
  34. 34
    When the pattern that matches the dialed digits sits in a partition that is not in the calling device's calling search space, digit analysis finds no potential match and the phone plays reorder (fast busy) tone.
    Troubleshooting Guide for Cisco Unified Communications Manager, Release 12.5(1) - Dial Plans and Routing Issues · Dial Plans and Routing Issues > Route Partitions and Calling Search Spaces (trace walkthrough) · Checked 2026-09-30
  35. 35
    Cisco lists hearing reorder tone either before or after the complete number is dialed as a symptom of partition and CSS misconfiguration.
    Configure Partition and Calling Search Space · Configure Partition and Calling Search Space > Troubleshoot (symptom list) · Checked 2026-09-30
  36. 36
    Cisco's Release 15 restriction guidance caps each route filter at 250 associated route patterns.
    System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Call Routing · Configure Call Routing > Call Routing Restrictions · Checked 2026-09-30
  37. 37
    For a 9.@ route pattern that makes callers wait after seven-digit numbers, Cisco suggests applying a route filter with LOCAL-AREA-CODE DOES-NOT-EXIST and END-OF-DIALING DOES-NOT-EXIST.
    Troubleshooting Guide for Cisco Unified Communications Manager, Release 12.5(1) - Dial Plans and Routing Issues · Dial Plans and Routing Issues > Problem When Dialing a Number (route filter step) · Checked 2026-09-30
  38. 38
    Route filters apply only to route patterns that contain the @ wildcard.
    System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Call Routing · Configure Call Routing > route filter overview · Checked 2026-09-30
  39. 39
    Cisco warns that editing a route filter shared by hundreds of route patterns can cause a system core crash, and recommends creating duplicate route filters instead.
    System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Call Routing · Configure Call Routing > Call Routing Restrictions · Checked 2026-09-30
  40. 40
    For an outbound call through a route list, the route list process locks the outbound device so that no alert message is sent before the call is completed.
    System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Call Routing · Configure Call Routing > Configure Route Lists · Checked 2026-09-30
  41. 41
    A route list is a prioritized list of one or more route groups, and a route group distributes calls across its gateways and trunks in a configured order.
    System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Call Routing · Configure Call Routing > Call Routing Overview; Configure Route Lists · Checked 2026-09-30
  42. 42
    Cisco's dialing-problem procedure uses the Route Plan Report to list all route patterns in the partitions reachable from the caller's CSS.
    Troubleshooting Guide for Cisco Unified Communications Manager, Release 12.5(1) - Dial Plans and Routing Issues · Dial Plans and Routing Issues > Problem When Dialing a Number, step 7 · Checked 2026-09-30
  43. 43
    Time-of-day routing ties time schedules to partitions, which controls which partitions a calling device searches at a given time of day.
    System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Call Routing · Configure Call Routing > time-of-day routing · Checked 2026-09-30
  44. 44
    From Unified CM 9.x onward, detailed tracing is enabled by default for the Cisco CallManager service, and Cisco's collection procedure has the Debug Trace Level set to Detailed.
    Collect Trace Data from a CUCM Cluster · Configure trace / verify trace settings · Checked 2026-09-30
  45. 45
    From Unified CM 9.x, SDI and SDL call-processing traces are written into a single interleaved set of files instead of separate files.
    Collect Trace Data from a CUCM Cluster · Background / trace file format · Checked 2026-09-30
  46. 46
    When no pattern in the reachable partitions can match the dialed digits, the trace shows the digit analysis string potentialMatches=NoPotentialMatchesExist.
    Troubleshooting Guide for Cisco Unified Communications Manager, Release 12.5(1) - Dial Plans and Routing Issues · Dial Plans and Routing Issues > Route Partitions and Calling Search Spaces (trace example) · Checked 2026-09-30
  47. 47
    In Unified CM call-processing traces, the digit analysis match line carries a pss field listing the partition search space (the calling search space) of the device placing the call.
    Troubleshooting Guide for Cisco Unified Communications Manager, Release 12.5(1) - Dial Plans and Routing Issues · Dial Plans and Routing Issues > Route Partitions and Calling Search Spaces · Checked 2026-09-30
  48. 48
    The documented trace for a partition-restricted call shows the station being told to play tone 37, ReorderTone (stationOutputStartTone: 37=ReorderTone).
    Troubleshooting Guide for Cisco Unified Communications Manager, Release 12.5(1) - Dial Plans and Routing Issues · Dial Plans and Routing Issues > Route Partitions and Calling Search Spaces (trace example) · Checked 2026-09-30
  49. 49
    Practitioners following a call in traces see egress device selection pass through the RouteListControl and RouteListCdrc processes after digit analysis.field report
    CUCM Traces Analysis: CUCM Architecture · Call flow walkthrough (CdCc to DA to RouteListControl) · Checked 2026-09-30
  50. 50
    Cisco's procedure collects Cisco CallManager (and CTIManager) traces in RTMT under System > Tools > Trace & Log Central > Collect Files, from all cluster nodes.
    Collect Trace Data from a CUCM Cluster · Collect traces with RTMT · Checked 2026-09-30
  51. 51
    Cisco recommends an absolute collection range from one minute before the first test call to one minute after the last, with the calling number, called number, start and end time recorded for each test call.
    Collect Trace Data from a CUCM Cluster · Collect traces with RTMT; reproduce the issue · Checked 2026-09-30
  52. 52
    A translation pattern whose own CSS lacks the partition of the intended target can make a call fail after translation even though the caller's CSS reaches the translation pattern.inferred
    System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Call Routing · Configure Call Routing > Call Routing Overview (translation patterns) · Checked 2026-09-30
  53. 53
    When dialed digits match a translation pattern, Unified CM transforms the digits and then routes the call again using the calling search space configured on the translation pattern.
    System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Call Routing · Configure Call Routing > Call Routing Overview (translation patterns) · Checked 2026-09-30
  54. 54
    Cisco's Collaboration 14 preferred architecture sets Use Originator's Calling Search Space on dialing normalization translation patterns so the secondary lookup uses the same CSS as the primary lookup.
    Preferred Architecture for Cisco Collaboration 14 Enterprise On-Premises Deployments, CVD - Call Control · Call Control > dial plan > dialing normalization · Checked 2026-09-30

Documents

tier 2 current vendor documentation

Administration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Services

Cisco Systems · 2026-08-31 · accessed 2026-09-24

tier 2 current vendor documentation

Call Reporting and Billing Administration Guide for Cisco Unified Communications Manager Release 15 and SUs, CDR Field Descriptions

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

tier 2 current vendor documentation

Collect Trace Data from a CUCM Cluster

Cisco Systems · 2024-08-22 · accessed 2026-09-22

tier 2 current vendor documentation

Configure Partition and Calling Search Space

Cisco Systems · 2016-05-05 · accessed 2026-09-24

tier 2 current vendor documentation

Preferred Architecture for Cisco Collaboration 14 Enterprise On-Premises Deployments, CVD - Call Control

Cisco · 2021-05-21 · accessed 2026-09-23

tier 2 current vendor documentation

System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Call Routing

Cisco · accessed 2026-09-21

tier 2 current vendor documentation

Troubleshoot Call Routing Issue via CUCM Dialed Number Analyzer

Cisco Systems · 2024-10-25 · accessed 2026-09-24

tier 2 current vendor documentation

Troubleshooting Guide for Cisco Unified Communications Manager Release 12.5(1) — Device Issues

Cisco Systems, Inc. (www.cisco.com) · 2023-11-24 · accessed 2026-09-16

tier 2 current vendor documentation

Troubleshooting Guide for Cisco Unified Communications Manager, Release 12.5(1) - Dial Plans and Routing Issues

Cisco Systems · 2023-11-24 · accessed 2026-09-24

tier 5 independent technical research

CUCM Traces Analysis: CUCM Architecture

Aurus · accessed 2026-09-30

Cite this page

APA

WarmTransfer. (2026, September 30). Troubleshooting Unified CM call routing failures and reorder tone. WarmTransfer. https://warmtransfer.net/knowledge/cucm-call-routing-failures

BibTeX

@misc{warmtransfer-cucm-call-routing-failures,
  title  = {Troubleshooting Unified CM call routing failures and reorder tone},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/cucm-call-routing-failures},
  note   = {Verified 2026-09-30}
}