# Troubleshooting outbound call failures in Webex Calling

Canonical: https://warmtransfer.net/knowledge/webex-calling-outbound-call-failures

Last verified: 2026-09-30

Webex Calling outgoing call permissions are set per call type, and digit patterns take precedence over them for any number they match[^36][^11]. Control Hub classifies each call in its troubleshooting view as successful, refused or failed, and each Webex Calling location needs PSTN connectivity chosen from Cisco PSTN, Cloud Connected PSTN or Premises-based PSTN (Local Gateway)[^54][^41].

## Diagnosing it in Control Hub

The Control Hub call troubleshooting view requires the full admin, read-only admin or support admin role[^53]. Its search covers calls from the past 21 days[^47]. Hovering over the status of an unsuccessful call shows its outcome code[^54].

| Status | Outcome | Meaning stated in the claim |
|---|---|---|
| Refusal | CallRejected | Rejected due to outgoing call permissions[^52] |
| Refusal | UnassignedNumber | Call to an unassigned destination number[^55] |
| Failure | NoRouteToDestination | No available route to the destination[^51] |

The hop details view shows the inbound or outbound trunk and route group when a Local Gateway is involved in the call, and the PSTN vendor name when PSTN is involved[^50].

WarmTransfer's reading of the sources is that a CallRejected refusal citing outgoing call permissions points the investigation at permissions or digit patterns, whereas a NoRouteToDestination failure or a PSTN-side SIP failure code points at dial plan, trunk or PSTN connectivity[^44].

The Control Hub Verify call routing tool simulates a call and shows the outgoing call permissions, fraud prevention, digit patterns, call intercept and translation patterns applied while routing it[^57]. It takes a call source (a cloud user, workspace, virtual line or premises trunk) and a destination number or URI[^56].

## Outgoing call permissions

Permissions are set per call type, covering internal, toll-free, national, international, operator assistance, chargeable directory assistance, special services I and II, and premium services I and II calls[^36]. For call type determination, Webex Calling merges local and long-distance calls into a single National call type[^25]. Each call type can be set to Allow, Block, Require Authorization Code, or Auto-transfer to number 1, 2 or 3[^35].

By default, international calls are set to Block, and transfer and forward to international destinations are not allowed[^37]. Premium services I and II calls are also set to Block by default[^38]. The Allow transfer/forwards setting on each call type determines whether a call can be transferred or forwarded to that call type, separately from whether it can be dialled directly[^40].

A user or workspace uses its location's outgoing call permissions by default, and an administrator can select Custom Settings to define that user's or workspace's own permissions[^39].

A matching digit pattern can block or allow a number regardless of its call type setting[^11]. When a dialled number matches more than one digit pattern, the pattern with the fewer possible expansions is applied[^9]. A maximum of 500 digit patterns can be configured per location, user, workspace or virtual line[^10]. Up to 1,000 authorization codes can be configured per location, and up to 1,000 per user, workspace or virtual line[^2].

## Outbound dial digit and number format

The location outbound dial digit defaults to None[^27]. When a location enforces its outbound dial digit, external destination numbers configured without that digit, such as call forwarding targets, stop working[^30]. With enforcement enabled, emergency calls can still be dialled with or without the outbound dial digit[^29]. Outbound calls dialled in E.164 format are not subject to the outbound dial digit requirement[^28].

Configuring an outbound dial digit on a location disables permissive dialing there, and E.164 format is always used for that location even if the organization format is set to National[^31]. Cisco advises that users at locations with an outbound dial digit include it when making external calls from Webex App, Webex Desk or Room devices[^26]. Users must restart their phones before changes to dialing preferences take effect[^32]. User extensions should not start with the same digit as the location's steering digit or outbound dial digit[^20].

## Translation patterns

Translation patterns apply to outbound and redirected calls, including transfers and forwards, but not to emergency calls, repair calls or call center callbacks[^60]. Webex Calling allows up to 1,000 translation patterns per organization and up to 500 per location[^58]. Location-level translation patterns take precedence over organization-level translation patterns[^59].

## PSTN, trunks and Local Gateway

Each location's PSTN connectivity is chosen from Cisco PSTN, Cloud Connected PSTN or Premises-based PSTN (Local Gateway)[^41]. See also [Webex Calling PSTN options and selection](https://warmtransfer.net/knowledge/webex-calling-pstn-options).

Control Hub reports Local Gateway trunk status as Online, Offline, Impaired or Unknown, where Impaired means the connection failed with at least one Webex Calling edge proxy[^45]. A route group can contain up to 10 trunks[^42]. Within a route group, calls are distributed randomly among trunks of equal priority, and if the highest-priority trunk is unavailable Webex Calling tries a lower-priority trunk[^43].

Cisco's Local Gateway configuration example assumes Webex Calling presents called numbers to the Local Gateway in +E.164 format and uses a voice translation rule to remove the leading plus before the PSTN[^23]. Webex Calling includes a P-Asserted-Identity header in outbound call INVITEs sent to the Local Gateway[^24].

As of a February 2024 TAC technote, when a premises PSTN provider behind a Local Gateway takes more than 12 seconds of post-dial delay, Webex Calling cancels the call[^33]. The same technote says that extending the 12-second limit requires opening a Webex Calling TAC case with Local Gateway traces (`debug ccsip messages` and `debug voice ccapi inout`)[^34].

## Caller ID

A caller ID number taken from another location must belong to a location with the same PSTN provider, country and zone[^7]. If an unassigned organization number is used as caller ID, callbacks to that number are not answered[^8]. Some PSTN providers may not honor the caller ID name configured in Webex Calling[^6]. See also [Webex Calling locations and number management](https://warmtransfer.net/knowledge/webex-calling-locations-numbers).

## Cisco Calling Plans and regional restrictions

On Cisco Calling Plans trials, international calling and Premium Service call types I and II are blocked for the trial period[^4]. With Cisco Calling Plans, some premium services and international destinations may be unavailable for operational reasons, and customers who need them can request access through a support ticket[^3]. Apart from 911, Cisco Calling Plans do not support calls to X11 services, including directory service calls[^5].

With a Cloud Connected PSTN provider in India, PSTN calling is not possible for a user outside their assigned zone because of toll bypass regulation[^21].

## Emergency calls

At locations enabled for Cisco's RedSky enhanced emergency calling, emergency calls are identified and sent to the E911 service instead of the location's configured PSTN or Local Gateway[^13]. If the E911 service cannot find a dispatchable location for the calling device, the call is routed to an emergency calling relay center, and relay center charges are billed back to the partner or customer[^15]. Cisco instructs administrators to place test calls to 933 to confirm routing before enabling full 911 routing for a location[^12].

Webex Calling accepts PSAP callbacks marked with an emergency Priority header and lifts the inbound call restriction on the device that placed an emergency call for 60 minutes[^16]. Cisco's VoIP emergency calling policy states that if a device's Registered Location is not updated, emergency calls may reach the wrong emergency response center with incorrect location information[^19]. The same policy states that emergency calling will not work if the calling equipment fails or is misconfigured, or during a power or internet service outage[^17].

## Applicability

The 12-second post-dial delay limit is stated as of a February 2024 TAC technote[^33]. The trial, destination and X11 restrictions apply to Cisco Calling Plans[^4][^3][^5]. The toll bypass roaming restriction applies in India[^21]. The enhanced emergency calling statements apply to locations enabled for Cisco's RedSky enhanced emergency calling[^13]. Applies to: Cisco Webex Calling, Cisco Webex Calling Local Gateway on IOS XE, Cisco Webex Calling with Local Gateway, Cisco Calling Plans for Webex Calling, and Cisco VoIP services including Webex Calling. Deployments: multi-tenant, cisco-pstn, cloud-connected-pstn, and premises-based-pstn. Sources checked 2026-09-30.

## What remains uncertain

STIR/SHAKEN attestation for Webex Calling outbound calls, and carrier rejection of unattested or unowned caller ID, is not covered by the sources below. Whether outgoing call permissions or digit patterns can affect emergency numbers is not covered by the sources below. The claims state only that translation patterns do not apply to emergency calls and that emergency calls can be dialled with or without an enforced outbound dial digit[^60][^29]. What the fraud prevention step shown in Verify call routing is, and how it is configured, is not covered by the sources below. The CDR fields that identify an outbound failure cause, such as release cause and redirect reason, are not covered by the sources below. A country-level international block list in Webex Calling is not covered by the sources below. Carrier-side rejection responses for an invalid caller origination number are not covered by the sources below. Provider-specific caller ID and number format rules for Cloud Connected PSTN are not covered by the sources below. The mapping of Control Hub outcome reasons to SIP and Q.850 codes is not covered by the sources below.

## Sources

[^1]: Webex Calling authorization codes can be up to 14 digits long. Source: [Outgoing call permissions for Webex Calling locations](https://help.webex.com/en-us/article/nt2lz3d/Outgoing-Calling-Permissions-for-Webex-Calling-Locations), Authorization Codes. Checked 2026-09-30.
[^2]: Up to 1,000 authorization codes can be configured per location, and up to 1,000 per user, workspace or virtual line. Source: [Outgoing call permissions for Webex Calling locations](https://help.webex.com/en-us/article/nt2lz3d/Outgoing-Calling-Permissions-for-Webex-Calling-Locations), Authorization Codes. Checked 2026-09-30.
[^3]: With Cisco Calling Plans, some premium services and international destinations may be unavailable for operational reasons, and customers who need them can request access through a support ticket. Source: [Get Started with the Cisco Calling Plans](https://help.webex.com/en-us/article/nousk9ab/Get-Started-with-the-Cisco-Calling-Plan), Cisco Calling Plans requirements and limitations. Checked 2026-09-30.
[^4]: On Cisco Calling Plans trials, international calling and Premium Service call types I and II are blocked for the trial period. Source: [Get Started with the Cisco Calling Plans](https://help.webex.com/en-us/article/nousk9ab/Get-Started-with-the-Cisco-Calling-Plan), Cisco Calling Plans trials. Checked 2026-09-30.
[^5]: Apart from 911, Cisco Calling Plans do not support calls to X11 services, including directory service calls. Source: [Get Started with the Cisco Calling Plans](https://help.webex.com/en-us/article/nousk9ab/Get-Started-with-the-Cisco-Calling-Plan), Cisco Calling Plans requirements and limitations. Checked 2026-09-30.
[^6]: Some PSTN providers may not honor the caller ID name configured in Webex Calling. Source: [Specify caller ID for users and workspaces](https://help.webex.com/en-us/article/nh3x9zt/Specify-caller-ID-options-for-users-and-workspaces), Caller ID name options. Checked 2026-09-30.
[^7]: A caller ID number taken from another location must belong to a location with the same PSTN provider, country and zone. Source: [Specify caller ID for users and workspaces](https://help.webex.com/en-us/article/nh3x9zt/Specify-caller-ID-options-for-users-and-workspaces), Caller ID phone number options (Other number from organization). Checked 2026-09-30.
[^8]: If an unassigned organization number is used as caller ID, callbacks to that number are not answered. Source: [Specify caller ID for users and workspaces](https://help.webex.com/en-us/article/nh3x9zt/Specify-caller-ID-options-for-users-and-workspaces), Caller ID phone number options (Other number from organization). Checked 2026-09-30.
[^9]: When a dialled number matches more than one outgoing permission digit pattern, the pattern with the fewer possible expansions is applied. Source: [Outgoing call permissions for Webex Calling locations](https://help.webex.com/en-us/article/nt2lz3d/Outgoing-Calling-Permissions-for-Webex-Calling-Locations), Pattern match. Checked 2026-09-30.
[^10]: A maximum of 500 digit patterns can be configured per location, user, workspace or virtual line for outgoing call permissions. Source: [Outgoing call permissions for Webex Calling locations](https://help.webex.com/en-us/article/nt2lz3d/Outgoing-Calling-Permissions-for-Webex-Calling-Locations), Permissions by digit pattern. Checked 2026-09-30.
[^11]: Outgoing permission digit patterns take precedence over permissions by call type, so a matching digit pattern can block or allow a number regardless of its call type setting. Source: [Outgoing call permissions for Webex Calling locations](https://help.webex.com/en-us/article/nt2lz3d/Outgoing-Calling-Permissions-for-Webex-Calling-Locations), Pattern match. Checked 2026-09-30.
[^12]: Cisco instructs administrators to place test calls to 933 to confirm routing before enabling full 911 routing for a location. Source: [Enhanced Emergency Calling for Webex Calling](https://help.webex.com/en-us/article/av6oo3/Enhanced-Emergency-Calling-for-Webex-Calling), Enable enhanced emergency calling for a location. Checked 2026-09-30.
[^13]: At locations enabled for Cisco's RedSky enhanced emergency calling, emergency calls are identified and sent to the E911 service instead of the location's configured PSTN or Local Gateway. Source: [Enhanced Emergency Calling for Webex Calling](https://help.webex.com/en-us/article/av6oo3/Enhanced-Emergency-Calling-for-Webex-Calling), Enhanced emergency calling overview; Local Gateway locations. Checked 2026-09-30.
[^14]: An organization whose PSTN provider handles emergency calling can opt out of enhanced emergency calling, in which case emergency calls follow the provider's routing and the customer must confirm the provider can handle them. Source: [Enhanced Emergency Calling for Webex Calling](https://help.webex.com/en-us/article/av6oo3/Enhanced-Emergency-Calling-for-Webex-Calling), Enhanced emergency calling (opt out / service provider routing). Checked 2026-09-30.
[^15]: If the E911 service cannot find a dispatchable location for the calling device, the emergency call is routed to an emergency calling relay center, and relay center charges are billed back to the partner or customer. Source: [Enhanced Emergency Calling for Webex Calling](https://help.webex.com/en-us/article/av6oo3/Enhanced-Emergency-Calling-for-Webex-Calling), Enhanced emergency calling (unknown location handling). Checked 2026-09-30.
[^16]: Webex Calling accepts PSAP callbacks marked with an emergency Priority header and lifts the inbound call restriction on the device that placed an emergency call for 60 minutes. Source: [What's new in Webex Calling](https://help.webex.com/en-us/article/rdmb0/What's-new-in-Webex-Calling), What's new entry dated March 26, 2025: Emergency Callback for workspaces. Checked 2026-09-30.
[^17]: Cisco's VoIP emergency calling policy states that emergency calling will not work if the calling equipment fails or is misconfigured, or during a power or internet service outage. Source: [Cisco VoIP Emergency Calling Policy](https://help.webex.com/en-us/article/04id6db/Cisco-VoIP-Emergency-Calling-Policy), Service limitations section. Checked 2026-09-30.
[^18]: Neither Cisco call permission article (nt2lz3d location level, q94e8c user level) states whether outgoing call permissions or digit patterns can affect emergency calls, so an answer that permissions never touch emergency calls is not supported by those pages (inferred). Source: [Outgoing call permissions for Webex Calling locations](https://help.webex.com/en-us/article/nt2lz3d/Outgoing-Calling-Permissions-for-Webex-Calling-Locations), Whole article (absence of any emergency-call statement); compare q94e8c whole article. Checked 2026-09-30.
[^19]: Cisco's VoIP emergency calling policy states that if a device's Registered Location is not updated, emergency calls may reach the wrong emergency response center with incorrect location information. Source: [Cisco VoIP Emergency Calling Policy](https://help.webex.com/en-us/article/04id6db/Cisco-VoIP-Emergency-Calling-Policy), Registered Location section. Checked 2026-09-30.
[^20]: User extensions should not start with the same digit as the location's steering digit or outbound dial digit. Source: [Configure your Webex Calling dial plan](https://help.webex.com/en-us/article/pxtu15/Configure-your-Webex-Calling-dial-plan), Internal Dialing. Checked 2026-09-30.
[^21]: With a Cloud Connected PSTN provider in India, PSTN calling is not possible for a user outside their assigned zone because of toll bypass regulation. Source: [Webex Calling with Cloud Connected PSTN Provider in India](https://help.webex.com/en-us/article/gvzxbu/Webex-Calling-with-Cloud-Connected-PSTN-Provider-in-India), Toll bypass call scenarios (roaming users). Checked 2026-09-30.
[^22]: In India toll-bypass deployments, transferring or forwarding an incoming PSTN call to a user in a different zone fails. Source: [Webex Calling with Cloud Connected PSTN Provider in India](https://help.webex.com/en-us/article/gvzxbu/Webex-Calling-with-Cloud-Connected-PSTN-Provider-in-India), Toll bypass call scenarios (transfer and forward). Checked 2026-09-30.
[^23]: Cisco's Local Gateway configuration example assumes Webex Calling presents called numbers to the Local Gateway in +E.164 format and uses a voice translation rule to remove the leading plus before the PSTN. Source: [Configure Local Gateway on Cisco IOS XE for Webex Calling](https://help.webex.com/en-us/article/jr1i3r/Configure-Local-Gateway-on-Cisco-IOS-XE-for-Webex-Calling), TDM trunk / voice translation rule example (rule 100). Checked 2026-09-30.
[^24]: Webex Calling includes a P-Asserted-Identity header in outbound call INVITEs sent to the Local Gateway. Source: [Configure Local Gateway on Cisco IOS XE for Webex Calling](https://help.webex.com/en-us/article/jr1i3r/Configure-Local-Gateway-on-Cisco-IOS-XE-for-Webex-Calling), Configure Local Gateway (asserted-id pai discussion). Checked 2026-09-30.
[^25]: For outgoing call type determination, Webex Calling merges local and long-distance calls into a single National call type. Source: [Configure dialing behavior for outbound calls](https://help.webex.com/en-us/article/nityras/Configure-Dialing-Behavior-for-Outbound-Calls), Calling phone number format. Checked 2026-09-30.
[^26]: Cisco advises that users at locations with an outbound dial digit include it when making external calls from Webex App, Webex Desk or Room devices. Source: [Configure dialing behavior for outbound calls](https://help.webex.com/en-us/article/nityras/Configure-Dialing-Behavior-for-Outbound-Calls), Calling phone number format. Checked 2026-09-30.
[^27]: The location outbound dial digit defaults to None in Webex Calling. Source: [Configure your Webex Calling dial plan](https://help.webex.com/en-us/article/pxtu15/Configure-your-Webex-Calling-dial-plan), Dialing (location external dialing). Checked 2026-09-30.
[^28]: Outbound calls dialled in E.164 format are not subject to the location's outbound dial digit requirement. Source: [Configure your Webex Calling dial plan](https://help.webex.com/en-us/article/pxtu15/Configure-your-Webex-Calling-dial-plan), Dialing. Checked 2026-09-30.
[^29]: With outbound dial digit enforcement enabled, emergency calls can still be dialled with or without the outbound dial digit. Source: [Configure your Webex Calling dial plan](https://help.webex.com/en-us/article/pxtu15/Configure-your-Webex-Calling-dial-plan), Dialing (Enforce outbound dial digit). Checked 2026-09-30.
[^30]: When a location enforces its outbound dial digit, external destination numbers configured without that digit, such as call forwarding targets, stop working. Source: [Configure your Webex Calling dial plan](https://help.webex.com/en-us/article/pxtu15/Configure-your-Webex-Calling-dial-plan), Dialing (Enforce outbound dial digit). Checked 2026-09-30.
[^31]: Configuring an outbound dial digit on a location disables permissive dialing there, and E.164 format is always used for that location even if the organization format is set to National. Source: [Configure dialing behavior for outbound calls](https://help.webex.com/en-us/article/nityras/Configure-Dialing-Behavior-for-Outbound-Calls), Calling phone number format. Checked 2026-09-30.
[^32]: Users must restart their phones before changes to dialing preferences take effect. Source: [Configure your Webex Calling dial plan](https://help.webex.com/en-us/article/pxtu15/Configure-your-Webex-Calling-dial-plan), Dialing. Checked 2026-09-30.
[^33]: As of a February 2024 TAC technote, when a premises PSTN provider behind a Local Gateway takes more than 12 seconds of post-dial delay, Webex Calling cancels the call. Source: [Troubleshoot PDD in Webex Calling with Premises Based PSTN](https://www.cisco.com/c/en/us/support/docs/unified-communications/jabber-windows/221643-troubleshoot-pdd-in-webex-calling-with-p.html), Background Information. Checked 2026-09-30.
[^34]: The same technote says that extending the 12-second post-dial delay limit requires opening a Webex Calling TAC case with Local Gateway traces (debug ccsip messages and debug voice ccapi inout). Source: [Troubleshoot PDD in Webex Calling with Premises Based PSTN](https://www.cisco.com/c/en/us/support/docs/unified-communications/jabber-windows/221643-troubleshoot-pdd-in-webex-calling-with-p.html), Troubleshoot / resolution section. Checked 2026-09-30.
[^35]: Each outgoing call type can be set to Allow, Block, Require Authorization Code, or Auto-transfer to number 1, 2 or 3. Source: [Outgoing call permissions for Webex Calling locations](https://help.webex.com/en-us/article/nt2lz3d/Outgoing-Calling-Permissions-for-Webex-Calling-Locations), Outgoing call permissions (permission options). Checked 2026-09-30.
[^36]: Webex Calling outgoing call permissions are set per call type, covering internal, toll-free, national, international, operator assistance, chargeable directory assistance, special services I and II, and premium services I and II calls. Source: [Outgoing call permissions for Webex Calling locations](https://help.webex.com/en-us/article/nt2lz3d/Outgoing-Calling-Permissions-for-Webex-Calling-Locations), Permissions by call type. Checked 2026-09-30.
[^37]: By default, international calls are set to Block in Webex Calling location outgoing call permissions, with transfer and forward to international destinations not allowed. Source: [Outgoing call permissions for Webex Calling locations](https://help.webex.com/en-us/article/nt2lz3d/Outgoing-Calling-Permissions-for-Webex-Calling-Locations), Permissions by call type (default permissions table). Checked 2026-09-30.
[^38]: By default, premium services I and II calls are set to Block in Webex Calling location outgoing call permissions. Source: [Outgoing call permissions for Webex Calling locations](https://help.webex.com/en-us/article/nt2lz3d/Outgoing-Calling-Permissions-for-Webex-Calling-Locations), Permissions by call type (default permissions table). Checked 2026-09-30.
[^39]: A user or workspace uses its location's outgoing call permissions by default and an administrator can select Custom Settings to define that user's or workspace's own permissions. Source: [Configure call permissions in Control Hub](https://help.webex.com/en-us/article/q94e8c/Configure-call-permissions-in-Control-Hub), Configure outgoing call permissions for a user or a workspace. Checked 2026-09-30.
[^40]: The Allow transfer/forwards setting on each call type determines whether a call can be transferred or forwarded to that outgoing call type, separately from whether it can be dialled directly. Source: [Outgoing call permissions for Webex Calling locations](https://help.webex.com/en-us/article/nt2lz3d/Outgoing-Calling-Permissions-for-Webex-Calling-Locations), Permissions by call type. Checked 2026-09-30.
[^41]: Each Webex Calling location needs PSTN connectivity set up, chosen from Cisco PSTN, Cloud Connected PSTN or Premises-based PSTN (Local Gateway). Source: [Configure trunks, route groups, and dial plans for Webex Calling](https://help.webex.com/article/n0xb944/Configure-Trunks-Route-Groups-and-Dial-Plans-for-Cisco-Webex-Calling), PSTN connection options for a location. Checked 2026-09-30.
[^42]: A Webex Calling route group can contain up to 10 trunks. Source: [Configure trunks, route groups, and dial plans for Webex Calling](https://help.webex.com/article/n0xb944/Configure-Trunks-Route-Groups-and-Dial-Plans-for-Cisco-Webex-Calling), Route groups. Checked 2026-09-30.
[^43]: Within a route group, calls are distributed randomly among trunks of equal priority, and if the highest-priority trunk is unavailable Webex Calling tries a lower-priority trunk. Source: [Configure trunks, route groups, and dial plans for Webex Calling](https://help.webex.com/article/n0xb944/Configure-Trunks-Route-Groups-and-Dial-Plans-for-Cisco-Webex-Calling), Route groups. Checked 2026-09-30.
[^44]: A CallRejected refusal citing outgoing call permissions points the investigation at permissions or digit patterns, whereas a NoRouteToDestination failure or a PSTN-side SIP failure code points at dial plan, trunk or PSTN connectivity (inferred). Source: [Troubleshoot Webex Calling calls in Control Hub](https://help.webex.com/en-us/article/frj1efb/Troubleshoot-Webex-Calling-Media-Quality-in-Control-Hub), Troubleshooting failed and refusal calls; Call outcome reasons. Checked 2026-09-30.
[^45]: Control Hub reports Local Gateway trunk status as Online, Offline, Impaired or Unknown, where Impaired means the connection failed with at least one Webex Calling edge proxy. Source: [Configure trunks, route groups, and dial plans for Webex Calling](https://help.webex.com/article/n0xb944/Configure-Trunks-Route-Groups-and-Dial-Plans-for-Cisco-Webex-Calling), Trunk status. Checked 2026-09-30.
[^46]: Local Gateway trunk status in Control Hub updates at roughly three-minute intervals, so a just-repaired trunk may still show its previous state briefly. Source: [Configure trunks, route groups, and dial plans for Webex Calling](https://help.webex.com/article/n0xb944/Configure-Trunks-Route-Groups-and-Dial-Plans-for-Cisco-Webex-Calling), Trunk status. Checked 2026-09-30.
[^47]: The Control Hub call troubleshooting search covers calls from the past 21 days. Source: [Troubleshoot Webex Calling calls in Control Hub](https://help.webex.com/en-us/article/frj1efb/Troubleshoot-Webex-Calling-Media-Quality-in-Control-Hub), Search view. Checked 2026-09-30.
[^48]: The refusal outcome reasons listed for the Control Hub troubleshooting view include AdminCallBlock, UserCallBlock and LocalGatewayLoop. Source: [Troubleshoot Webex Calling calls in Control Hub](https://help.webex.com/en-us/article/frj1efb/Troubleshoot-Webex-Calling-Media-Quality-in-Control-Hub), Call outcome reasons (Refusal rows). Checked 2026-09-30.
[^49]: Failure outcome reasons listed for the Control Hub troubleshooting view include DestinationOutOfOrder, SIP501, SIP503, ProtocolError, SIP606, NoRouteToDestination, Internal and MaxConcurrentTerminatingAlertingRequestsExceeded. Source: [Troubleshoot Webex Calling calls in Control Hub](https://help.webex.com/en-us/article/frj1efb/Troubleshoot-Webex-Calling-Media-Quality-in-Control-Hub), Call outcome reasons (Failure rows). Checked 2026-09-30.
[^50]: The hop details view shows the inbound or outbound trunk and route group when a Local Gateway is involved in the call, and the PSTN vendor name when PSTN is involved. Source: [Troubleshoot Webex Calling calls in Control Hub](https://help.webex.com/en-us/article/frj1efb/Troubleshoot-Webex-Calling-Media-Quality-in-Control-Hub), Hop details view. Checked 2026-09-30.
[^51]: A call with no available route to the destination is shown in the Control Hub troubleshooting view as a failure with the NoRouteToDestination outcome. Source: [Troubleshoot Webex Calling calls in Control Hub](https://help.webex.com/en-us/article/frj1efb/Troubleshoot-Webex-Calling-Media-Quality-in-Control-Hub), Call outcome reasons (Failure: NoRouteToDestination). Checked 2026-09-30.
[^52]: A call blocked by outgoing call permissions appears in the Control Hub troubleshooting view as a refusal with the CallRejected outcome, described as rejected due to outgoing call permissions. Source: [Troubleshoot Webex Calling calls in Control Hub](https://help.webex.com/en-us/article/frj1efb/Troubleshoot-Webex-Calling-Media-Quality-in-Control-Hub), Troubleshooting failed and refusal calls; Call outcome reasons (Refusal: CallRejected). Checked 2026-09-30.
[^53]: The Control Hub call troubleshooting view requires the full admin, read-only admin or support admin role. Source: [Troubleshoot Webex Calling calls in Control Hub](https://help.webex.com/en-us/article/frj1efb/Troubleshoot-Webex-Calling-Media-Quality-in-Control-Hub), Prerequisites. Checked 2026-09-30.
[^54]: Control Hub classifies each call in the troubleshooting view as successful, refused or failed, and hovering over the status of an unsuccessful call shows its outcome code. Source: [Troubleshoot Webex Calling calls in Control Hub](https://help.webex.com/en-us/article/frj1efb/Troubleshoot-Webex-Calling-Media-Quality-in-Control-Hub), Troubleshooting failed and refusal calls. Checked 2026-09-30.
[^55]: A call to an unassigned destination number is shown in the Control Hub troubleshooting view as a refusal with the UnassignedNumber outcome. Source: [Troubleshoot Webex Calling calls in Control Hub](https://help.webex.com/en-us/article/frj1efb/Troubleshoot-Webex-Calling-Media-Quality-in-Control-Hub), Call outcome reasons (Refusal: UnassignedNumber). Checked 2026-09-30.
[^56]: Verify call routing takes a call source (a cloud user, workspace, virtual line or premises trunk) and a destination number or URI. Source: [Configure trunks, route groups, and dial plans for Webex Calling](https://help.webex.com/article/n0xb944/Configure-Trunks-Route-Groups-and-Dial-Plans-for-Cisco-Webex-Calling), Verify call routing. Checked 2026-09-30.
[^57]: The Control Hub Verify call routing tool simulates a call and shows the outgoing call permissions, fraud prevention, digit patterns, call intercept and translation patterns applied while routing it. Source: [Configure trunks, route groups, and dial plans for Webex Calling](https://help.webex.com/article/n0xb944/Configure-Trunks-Route-Groups-and-Dial-Plans-for-Cisco-Webex-Calling), Verify call routing. Checked 2026-09-30.
[^58]: Webex Calling allows up to 1,000 translation patterns per organization and up to 500 per location. Source: [Translation patterns for outbound calls](https://help.webex.com/en-us/article/nib9o6h/Translation-patterns-for-outbound-calls), Organization and location level translation patterns. Checked 2026-09-30.
[^59]: Location-level translation patterns take precedence over organization-level translation patterns. Source: [Translation patterns for outbound calls](https://help.webex.com/en-us/article/nib9o6h/Translation-patterns-for-outbound-calls), Organization and location level translation patterns. Checked 2026-09-30.
[^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. Source: [Translation patterns for outbound calls](https://help.webex.com/en-us/article/nib9o6h/Translation-patterns-for-outbound-calls), Overview of translation patterns. Checked 2026-09-30.