Troubleshooting inbound calls that fail to reach Webex Contact Center
Verified 2026-09-30 · 44 sources · tier 2 · 2 disputed
Voice calls route into Webex Contact Center via Webex Calling PSTN services and Webex edge access services before being answered by voice ingress services that run the flow assigned to an entry point 18. Inbound call failures can stem from PSTN connectivity issues, dial number mapping discrepancies, or entry point routing configuration 191418.
PSTN Connectivity and Media Requirements
Webex Contact Center voice supports 4 PSTN options: Webex Contact Center PSTN, Webex Calling Cloud Connected PSTN, Cisco Calling Plan, and Webex Calling Local Gateway 32. Cisco advises testing that successful inbound and outbound calls function over the selected Webex Calling PSTN option before finishing remaining Webex Contact Center deployment tasks 38.
PSTN configurations must adhere to specific platform constraints:
- PSTN Availability and Add-ons: Webex Contact Center PSTN is available only in the contiguous United States and Canada 44. For Cisco-provided Webex Contact Center PSTN, mapping toll-free numbers requires the Bundle 2 inbound toll-free number access add-on; otherwise, toll numbers must be used 39.
- Endpoint Exclusions: Cisco does not support endpoint devices within the same Webex Calling location as Webex Contact Center PSTN and warns that doing so may result in unexpected overage charges 28.
- Carrier Routing Limits: Introducing a second upstream PSTN carrier that forwards calls to an intermediary carrier prior to Webex Contact Center is not a supported setup for Cloud Connected PSTN, Local Gateway, or Webex Contact Center PSTN 33. To keep latency low, Cisco advises restricting the number of PSTN carriers involved in routing to no more than 2 before the call reaches Webex Contact Center 27.
- Media and Signaling: Webex Contact Center PSTN media requires G.711 u-law or A-law codecs 5. Any other codec—such as G.729, iLBC, or Opus—must be transcoded prior to reaching Webex Contact Center 5. Webex Contact Center does not provide transcoding or media termination point services for calls using unsupported codecs 29. In addition, media requirements specify RFC 2833 DTMF and a 20 ms packetization time in the SDP 8.
Dial Number and Entry Point Configuration
In Control Hub, dial numbers are mapped to entry points under Contact Center > Tenant Settings > Voice by selecting an available dial number (DN) and the target entry point 7. Cisco warns administrators to configure only numbers allocated to their Webex Contact Center PSTN connection, as entering invalid numbers can cause call routing failures 19.
Sources disagree on entry point number requirements: sources disagree on whether Webex Contact Center supports mapping only PSTN numbers in globalized +E.164 format without supporting extensions 10, or whether an inbound entry point requires a Webex Calling location and a PSTN region and can be populated with a PSTN number, an extension number, or both 11. When extensions are used for entry points, Cisco notes that administrators should avoid mixing prefixed and non-prefixed locations and avoid overlapping extensions across locations, as both can cause unexpected routing 15.
Additional number and mapping behaviors include:
- Cisco describes the phone number as the key configuration of a voice entry point, typically a valid PSTN number from the chosen PSTN provider 12.
- Cloud Connected PSTN providers are provisioned to support +E.164 format for both DID and toll-free numbers 2.
- Premises-based PSTN DIDs or toll-free numbers configured in Control Hub for Local Gateway are saved in +E.164 format 22.
- The Webex Calling location main number does not appear in the list of numbers available for dial number to entry point mapping 26.
- A dial number must be mapped to an entry point to be selectable as the default outdial ANI; when unmapped, the Default Outdial ANI field displays "Not Configured" 31.
- In Control Hub, administrators can search and sort phone numbers associated with an entry point 13.
A tenant can support up to 6000 active entry points, up to 500 dialed numbers per entry point, and up to 15000 dialed number to entry point mappings 2324.
Flow Execution and Diagnostics
In Flow Designer, a flow must be validated and its errors resolved before it can be published 16. An entry point configuration defines the routing flow and specifies a Version Label field to select which version of that flow runs 14. WarmTransfer's reading of the sources is that if an entry point references a version label other than the one recently published, callers will run the older version, causing a republished fix to appear ineffective 42.
When troubleshooting inbound failures:
- Service Verification: Cisco's checklist specifies confirming under Contact Center > Settings > Service Details that the voice media platform is Real Time Media Service and telephony is Webex Calling 34. Agents using Webex devices or the Webex App require a valid Webex Calling subscription 1.
- Trunk Health: For Local Gateway, Control Hub displays trunk status as Online, Offline, Impaired (at least 1 Webex Calling Edge proxy cannot connect), or Unknown (connection in progress for a new gateway) 40. This status updates every 3 minutes 41.
- Call Leg Diagnostics: Control Hub's Webex Calling call troubleshooting view retains calls from the past 21 days, including PSTN legs across Cloud Connected PSTN and Local Gateway with trunk and route group details 3. Viewing this requires the full admin, read-only admin, or support admin role 4. Note that Cisco's technote for incoming call problems for Webex Calling users focuses on user settings (number assignment, call forwarding, DND, permissions) and does not cover contact center routing, Local Gateway trunk status, or SIP response codes 43.
- Isolation Sequence: WarmTransfer's reading of the sources is that a defensible isolation order is to confirm the PSTN path functions with a plain Webex Calling number, verify trunk status for Local Gateway, ensure the dial number is mapped to the intended entry point, check the entry point's flow and version label, and review the flow debug path 20.
- Escalation Data: When escalating to Cisco TAC, required data includes the ANI or Contact Session ID, exact timestamps, agent details, and full error screenshots 36. TAC questions for inbound failures evaluate whether the agent phone rings, whether an error appears on the Agent Desktop, and whether the issue is restricted to specific sites or newly added extensions 37.
Applicability
Applies to: Cisco Webex Contact Center and Cisco Webex Calling. Deployments: multi-tenant. Sources checked 2026-09-30. Webex Contact Center PSTN features and restrictions apply specifically to the contiguous United States and Canada 443928. Search and sort capabilities for entry point phone numbers apply from July 24 2026 13.
What remains uncertain
What callers hear (such as a fast busy, reorder tone, or announcement) for each ingress failure cause is not covered by the sources below. Raw-page verification of Flow Designer version labels, OnGlobalError, and Debug flows subsections is not covered by the sources below. The specific SIP response code returned when a dial number is unmapped or when a flow fails is not covered by the sources below. Entry point capacity and calls-per-second limits are not covered by the sources below. Resolving the conflict between sources requiring E.164-only entry point mapping versus sources permitting extension mapping is not covered by the sources below. Local Gateway IOS-XE inbound dial-peer and codec configuration toward Webex Calling for Webex Contact Center numbers is not covered by the sources below. PSTN region and regional media selection errors on entry points are not covered by the sources below. Carrier routing and number porting issues to Cloud Connected PSTN providers as an inbound failure cause are not covered by the sources below.
See also
Part of
- Webex contact center — Symptom-driven troubleshooting slice of the Webex Contact Center platform topic
Related to
- Setting up bring-your-own PSTN for Webex Contact Center — Setup guide for the PSTN path whose misconfiguration produces many of these failures
- Troubleshooting Webex Contact Center calls that wait in queue with agents availablestub — Downstream stage: this topic stops once the call reaches the entry point and flow; agent delivery failures belong there
- Troubleshooting inbound calls to Webex Calling numbers — Webex Calling PSTN and Local Gateway ingress is the upstream leg for Webex Contact Center voice
Referenced by
- Troubleshooting Webex Contact Center calls that wait in queue with agents availablestub — Neighbouring symptom: calls that fail before or at the entry point rather than waiting in queue
- Troubleshooting inbound calls to Webex Calling numbers — Contact center inbound failures can sit on top of Webex Calling PSTN numbers; this packet stops at Webex Calling users; workspaces and features. Proposed by this packet; not previously recorded.
- Webex contact center — Troubleshooting topic for the voice path described here (entry points; PSTN options; Common Edge).
Sources
- 1A valid Webex Calling subscription is required for agents who use Webex devices or the Webex App.Set up voice channels for Webex Contact Center · Webex Calling Configuration Checklist > Active Subscriptions · Checked 2026-09-30
- 2Cloud Connected PSTN providers are provisioned to support +E.164 format numbers for both DID and toll-free numbers used with Webex Contact Center.Set up voice channels for Webex Contact Center · Cloud Connected PSTN number requirements · Checked 2026-09-30
- 3Control Hub's Webex Calling call troubleshooting view shows calls from the past 21 days and includes PSTN legs through Cloud Connected PSTN and Local Gateway with trunk and route group details.Troubleshoot Webex Calling calls in Control Hub · Troubleshoot calls > search and call legs · Checked 2026-09-30
- 4Access to the Control Hub Webex Calling troubleshooting view requires the full admin, read-only admin or support admin role.Troubleshoot Webex Calling calls in Control Hub · Before you begin / required roles · Checked 2026-09-30
- 5Webex Contact Center PSTN media requires G.711 u-law or A-law, and any other codec such as G.729, iLBC or Opus must be transcoded before reaching Webex Contact Center.Set up voice channels for Webex Contact Center · PSTN Media and Signaling Requirements > Codec · Checked 2026-09-30
- 6Flow Designer's Debug flows feature shows the call control path a production interaction took and can be filtered by interaction or session ID.Build and manage flows with Flow Designer · Debug flows · Checked 2026-09-30
- 7Dial numbers are mapped to entry points in Control Hub under Contact Center > Tenant Settings > Voice by selecting an available number or DN and the target entry point.Set up voice settings for Webex Contact Center · Map dial numbers to entry points (Tenant Settings > Voice) · Checked 2026-09-30
- 8Webex Contact Center PSTN requirements specify RFC 2833 DTMF and a 20 ms packetization time in the SDP.Set up voice channels for Webex Contact Center · PSTN Media and Signaling Requirements > DTMF; Packetization Timer in SIP SDP · Checked 2026-09-30
- 9Webex Contact Center PSTN signaling requirements list SIP Early Offer as not supported and SIP Delayed Offer as supported.Set up voice channels for Webex Contact Center · PSTN Media and Signaling Requirements > SIP Early Offer / Delay Offer · Checked 2026-09-30
- 10The Set up a channel article states that Webex Contact Center supports mapping only PSTN numbers in globalized +E.164 format to entry points and that extensions are not supported for this mapping.disputedSet up a channel · Set up a channel > inbound telephony entry point > Support Number step · Checked 2026-09-30
- 11The Webex Calling based voice channel setup article states that an inbound entry point requires a Webex Calling location and a PSTN region, and can be populated with a PSTN number, an extension number, or both.disputedSet up voice channels for Webex Contact Center · Configuration of Inbound Entry Points to Webex Contact Center · Checked 2026-09-30
- 12Cisco's architecture article describes the phone number as the key configuration of a voice entry point, typically a valid PSTN number from the chosen PSTN provider.Webex Contact Center Architecture · Entry point (voice ingress) · Checked 2026-09-30
- 13A July 24 2026 admin update added the ability to search and sort phone numbers associated with an entry point in Control Hub.What's new for administrators in Webex Contact Center · July 24 2026 entry > admin experience improvements · Checked 2026-09-30
- 14Entry point configuration includes a routing flow selection and a Version Label field that chooses which version of that flow the entry point runs.Set up a channel · Set up a channel > Entry point settings > Routing Flow; Version Label · Checked 2026-09-30
- 15When entry points use extensions Cisco says to avoid mixing prefixed and non-prefixed locations and to avoid overlapping extensions across locations because both can cause unexpected call routing.Set up voice channels for Webex Contact Center · Important considerations for extension numbers · Checked 2026-09-30
- 16In Flow Designer a flow must be validated and its errors fixed before it can be published.Build and manage flows with Flow Designer · Flow Designer interface > Footer pane (validation and publish) · Checked 2026-09-30
- 17Flow developers can branch flow logic on the version label in execution using the NewContact.FlowVersionLabel variable.Build and manage flows with Flow Designer · Create and manage flows > Apply version labels to a flow (NewContact variables) · Checked 2026-09-30
- 18Voice calls are routed into Webex Contact Center using Webex Calling PSTN services and Webex edge access services, then answered by voice ingress services that run the flow assigned to the entry point.Webex Contact Center Architecture · Voice ingress / Calls are routed into Webex Contact Center · Checked 2026-09-30
- 19Cisco warns administrators to configure only the numbers allocated to their Webex Contact Center PSTN connection because entering invalid numbers may result in call routing failures.Set up voice channels for Webex Contact Center · Configuration of Webex Contact Center PSTN numbers (warning note) · Checked 2026-09-30
- 20A defensible isolation order for an inbound failure is: confirm the PSTN path works with a plain Webex Calling number, check trunk status for Local Gateway, confirm the DN is mapped to the intended entry point, then confirm the entry point's flow and version label and review the flow debug path.inferredWebex Contact Center Architecture · Voice ingress path (combined with nhy3codb checklist and nhovcy4 Debug flows) · Checked 2026-09-30
- 21When a flow is published it can carry version labels such as Live, Test or Dev, and Latest is a default version label that cannot be removed from a flow version.Build and manage flows with Flow Designer · Create and manage flows > Apply version labels to a flow · Checked 2026-09-30
- 22Premises-based PSTN DIDs or toll-free numbers configured in Control Hub for Local Gateway are saved in +E.164 format.Set up voice channels for Webex Contact Center · Local Gateway number requirements · Checked 2026-09-30
- 23The Webex Contact Center system limits table sets a maximum of 6000 active entry points per tenant.System limits in Webex Contact Center · Table 1. Maximum system limits for configuration entities and attributes > Entry points > Active · Checked 2026-09-30
- 24The Webex Contact Center system limits table allows at most 500 dialed numbers per entry point and 15000 dialed number to entry point mappings per tenant.System limits in Webex Contact Center · Table 1 > Dialed numbers > Entry Point; Per entry point · Checked 2026-09-30
- 25The Webex Contact Center system limits article as fetched gives no calls-per-second or per-entry-point concurrent call capacity figure.inferredSystem limits in Webex Contact Center · Tables 1 and 3 (absence of CPS or entry point capacity rows) · Checked 2026-09-30
- 26The Webex Calling location main number does not appear in the list of numbers available for dial number to entry point mapping.Set up voice settings for Webex Contact Center · Map dial numbers to entry points (note under Available numbers/DN) · Checked 2026-09-30
- 27Cisco advises limiting the number of PSTN carriers involved in routing to no more than two before the call reaches Webex Contact Center to keep latency low.Set up voice channels for Webex Contact Center · PSTN Call Forwarding Scenarios and Best Practices (best practice note) · Checked 2026-09-30
- 28Cisco does not support endpoint devices in the same Webex Calling location as Webex Contact Center PSTN and warns this may cause unexpected overage charges.Set up voice channels for Webex Contact Center · Configuration of Webex Contact Center PSTN Locations · Checked 2026-09-30
- 29Webex Contact Center does not provide transcoding or media termination point services for calls using unsupported codecs.Set up voice channels for Webex Contact Center · PSTN Media and Signaling Requirements · Checked 2026-09-30
- 30When an activity has no error path configured the flow uses the default path defined in the OnGlobalError event handler on the Event Flows tab.Build and manage flows with Flow Designer · Event flows > OnGlobalError · Checked 2026-09-30
- 31A dial number must be mapped to an entry point to be available as the default outdial ANI, and the Default Outdial ANI field shows Not Configured when the number is not mapped.Set up voice settings for Webex Contact Center · Call Settings > Default Outdial ANI · Checked 2026-09-30
- 32Webex Contact Center voice supports four PSTN options: Webex Contact Center PSTN, Webex Calling Cloud Connected PSTN, Cisco Calling Plan, and Webex Calling Local Gateway.Set up voice channels for Webex Contact Center · PSTN connectivity options · Checked 2026-09-30
- 33Introducing a second upstream PSTN carrier that forwards calls to an intermediary carrier before Webex Contact Center is not a supported configuration for Cloud Connected PSTN, Local Gateway or Webex Contact Center PSTN.Set up voice channels for Webex Contact Center · PSTN Call Forwarding Scenarios and Best Practices · Checked 2026-09-30
- 34Cisco's Webex Calling configuration checklist for Webex Contact Center says to confirm under Contact Center > Settings > Service Details that the voice media platform is Real Time Media Service and telephony is Webex Calling.Set up voice channels for Webex Contact Center · Webex Calling Configuration Checklist > Service Details · Checked 2026-09-30
- 35No retrieved Cisco source states what a caller hears (fast busy, reorder, announcement or silence) when a dialed number is not mapped to an entry point or the flow errors, so symptom-to-cause mapping by audible tone cannot be sourced.inferredSet up voice settings for Webex Contact Center · Map dial numbers to entry points (no caller-experience statement) · Checked 2026-09-30
- 36Cisco TAC asks for the ANI or Contact Session ID of the failed call, exact timestamps, agent information and full error screenshots when troubleshooting Webex Contact Center calls.Data Requirements to Troubleshoot Webex Contact Center Calls · Call-specific data · Checked 2026-09-30
- 37For inbound failures the TAC data note asks whether the agent phone rings or the agent gets an error on Agent Desktop, and whether the problem is limited to specific sites or newly added extensions.Data Requirements to Troubleshoot Webex Contact Center Calls · Call-specific data > Inbound call failures · Checked 2026-09-30
- 38Cisco says to make successful inbound and outbound calls over the chosen Webex Calling PSTN option before completing the remaining Webex Contact Center deployment tasks.Set up voice channels for Webex Contact Center · Webex Calling Configuration Checklist (pre-deployment note) · Checked 2026-09-30
- 39For Cisco-provided Webex Contact Center PSTN, mapping toll-free numbers requires the Bundle 2 inbound toll-free number access add-on; without it toll numbers must be used.Set up voice settings for Webex Contact Center · Map dial numbers to entry points (entitlement note) · Checked 2026-09-30
- 40Control Hub shows a Local Gateway trunk as Online, Offline, Impaired (at least one Webex Calling Edge proxy cannot connect) or Unknown (connection in progress for a new gateway).Configure trunks, route groups, and dial plans for Webex Calling · Trunk status · Checked 2026-09-30
- 41Local Gateway trunk status in Control Hub updates every 3 minutes.Configure trunks, route groups, and dial plans for Webex Calling · Trunk status · Checked 2026-09-30
- 42If an entry point points at a version label other than the one the administrator recently published, callers will run the older flow version, so a republished fix may appear not to take effect.inferredSet up a channel · Set up a channel > Entry point settings > Version Label · Checked 2026-09-30
- 43Cisco's technote on incoming call problems for Webex Calling users covers user-level settings such as number assignment, forwarding, DND and incoming permissions and does not cover Contact Center, Local Gateway trunk status or SIP response codes.Troubleshoot Incoming Call Problems for Webex Calling Users · Troubleshoot sections (whole document) · Checked 2026-09-30
- 44Webex Contact Center PSTN is available in the contiguous United States and Canada only.Set up voice channels for Webex Contact Center · PSTN connectivity options > Webex Contact Center PSTN · Checked 2026-09-30
Documents
Build and manage flows with Flow Designer
Configure trunks, route groups, and dial plans for Webex Calling
Data Requirements to Troubleshoot Webex Contact Center Calls
Set up a channel
Set up voice channels for Webex Contact Center
Set up voice settings for Webex Contact Center
System limits in Webex Contact Center
Troubleshoot Incoming Call Problems for Webex Calling Users
Troubleshoot Webex Calling calls in Control Hub
Webex Contact Center Architecture
What's new for administrators in Webex Contact Center
Cite this page
APA
WarmTransfer. (2026, September 30). Troubleshooting inbound calls that fail to reach Webex Contact Center. WarmTransfer. https://warmtransfer.net/knowledge/wxcc-inbound-call-failures
BibTeX
@misc{warmtransfer-wxcc-inbound-call-failures,
title = {Troubleshooting inbound calls that fail to reach Webex Contact Center},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/wxcc-inbound-call-failures},
note = {Verified 2026-09-30}
}