webex contact center · stub
Troubleshooting Webex Contact Center calls that drop after the agent answers
Verified 2026-10-02 · 57 sources · tier 1–2
Also known as wxcc-dropped-calls.
Stub. This topic has 57 sources and no published article. The sources below are everything recorded so far.
So far, no summary has been generated for this topic. The sources below are everything recorded so far.
See also
Related to
- Troubleshooting Webex Contact Center agents stuck in wrap-up or RONA or unable to go available — WebRTC loss moves the voice channel to Idle and RONA returns contacts to queue; both are often reported as drops.
- Troubleshooting Webex Contact Center transfers and conferences — Drops during consult or conference overlap with transfer troubleshooting.
- Troubleshooting agent audio on the Webex Contact Center desktop — WebRTC media diagnostics (webrtc-internals) overlap with audio troubleshooting.
- Troubleshooting browser softphone audio in cloud contact centers — Browser softphone (Desktop or WebRTC) failures are one cause of drops at answer.
- Troubleshooting calls that drop on hold or transfer — Session-timer refresh failures (re-INVITE or UPDATE not delivered) are the generic SIP mechanism behind fixed-time drops on the PSTN trunk leg.
- Webex Contact Center Analyzer and reporting model — Termination Type and Termination Reason fields and the Dropped call summaries report live in Analyzer.
Sources
- 1Webex Contact Center agents can receive calls on a Webex Calling device (Extension), in the browser (Desktop or WebRTC), on a PSTN or premises PBX number (Dial Number), or in Microsoft Teams through a Local Gateway.Set up voice channels for Webex Contact Center · Agent telephony options · Checked 2026-10-02
- 2The Analyzer Termination Reason field (used in the Dropped call summaries report) takes the values Agent Left, Customer Busy, Customer Left, Customer Unavailable, Not Found and Participant Invite Timer Expired.Cisco Webex Contact Center Analyzer User Guide · Stock Reports > Historical Reports > Agent Reports > Dropped call summaries; field Termination Reason · Checked 2026-10-02
- 3In Webex Contact Center Analyzer, the Termination Type field is a text string that specifies how a call was terminated.Cisco Webex Contact Center Analyzer User Guide · Field definitions: Termination Type · Checked 2026-10-02
- 4For a Desktop (WebRTC) agent, a drop at or just after answer can come from the browser side (WebRTC session loss or desktop connectivity loss) and not only from the PSTN trunk, so both the webrtc-internals data and the trunk-side signalling need checking.inferredManage your calls in Agent Desktop · Desktop mode (WebRTC) · Checked 2026-10-02
- 5Control Hub Webex Calling call troubleshooting reports call outcome reasons grouped as Success (for example Normal, UserBusy, NoAnswer), Refusal (for example CallRejected, UnassignedNumber) and Failure (for example DestinationOutOfOrder, NoRouteToDestination, Internal).Troubleshoot Webex Calling calls in Control Hub · Call outcome reasons table · Checked 2026-10-02
- 6Control Hub call troubleshooting for Webex Calling shows calls from the past 21 days and lets you search by email, phone number, MAC address, Call ID or Correlation ID.Troubleshoot Webex Calling calls in Control Hub · Troubleshoot Webex Calling calls: search and time range · Checked 2026-10-02
- 7Opening 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 · Prerequisites / required roles · Checked 2026-10-02
- 8The Control Hub call troubleshooting article covers Webex Calling calls and does not mention Webex Contact Center, so it should not be assumed to show the contact-center leg of a call; at most it may show the Webex Calling legs (for example an Extension agent's device).inferredTroubleshoot Webex Calling calls in Control Hub · Article scope (whole article) · Checked 2026-10-02
- 9If a consulted agent does not answer the consult call, or the consulted agent's device is malfunctioning, the system changes the consulted agent's state to Idle.Manage your calls in Agent Desktop · Consult a call: consulted agent does not answer · Checked 2026-10-02
- 10By default the customer is put on hold when the primary agent starts a consult, unless other participants are already in a conference.Manage your calls in Agent Desktop · Consult a call · Checked 2026-10-02
- 11Cisco's CUBE session timer documentation states that if a refreshing re-INVITE gets no response before the session expires, the user agent sends a BYE to end the call before expiry.Cisco Unified Border Element Configuration Guide (IOS XE) - SIP Session Timer Support · SIP Session Timer Support: information about session timers · Checked 2026-10-02
- 12On Cisco Unified Border Element (IOS XE 17.6 onwards), the min-se value defaults to 1800 seconds and can be set from 90 to 86400 seconds.Cisco Unified Border Element Configuration Guide (IOS XE) - SIP Session Timer Support · SIP Session Timer Support: Min-SE configuration · Checked 2026-10-02
- 13The IOS timer receive-rtcp media inactivity timer accepts 0 to 1000 multiples of the RTCP report interval and defaults to 0 (disabled).Cisco IOS Voice Command Reference - T through Z - timeouts call-disconnect through timing clear-wait · timer receive-rtcp: Syntax Description and Command Default · Checked 2026-10-02
- 14With the IOS timer receive-rtcp command, the gateway multiplies the configured value by the RTCP report interval, and if no RTP or RTCP packets arrive in that time it disconnects the call, sending a SIP BYE toward the VoIP side.Cisco IOS Voice Command Reference - T through Z - timeouts call-disconnect through timing clear-wait · timer receive-rtcp: Usage Guidelines · Checked 2026-10-02
- 15The CUBE command show sip-ua min-se displays the current Min-SE value.Cisco Unified Border Element Configuration Guide (IOS XE) - SIP Session Timer Support · SIP Session Timer Support: verification · Checked 2026-10-02
- 16If the customer leaves during an active consult or conference, the call enters a Post Call state: remaining participants can keep talking but no new participants can be added, and the agent is notified that the customer left.Manage your calls in Agent Desktop · Consult and conference: customer leaves · Checked 2026-10-02
- 17The Agent Desktop error report (Download Error Report) can be downloaded whether the desktop is connected or disconnected.Troublshoot Agent Desktop Disconnect Issues · Troubleshoot: logs to collect, Error Report · Checked 2026-10-02
- 18Agent Desktop sends keepalive messages to the Webex Contact Center backend every 4 seconds, and the backend notification service sends keepalives back in parallel.Troublshoot Agent Desktop Disconnect Issues · Background information: keepalive mechanism · Checked 2026-10-02
- 19In Desktop mode, Agent Desktop uses WebRTC to terminate both the call and its media directly in the browser.Manage your calls in Agent Desktop · Desktop mode (WebRTC) · Checked 2026-10-02
- 20If no messages complete for 16 seconds from either Agent Desktop or the notification service, Agent Desktop starts its connection recovery process.Troublshoot Agent Desktop Disconnect Issues · Background information: recovery trigger · Checked 2026-10-02
- 21During recovery, Agent Desktop tries to reconnect for the interval set by the tenant's Desktop Lost Connection Recovery Timeout.Troublshoot Agent Desktop Disconnect Issues · Background information: connection recovery · Checked 2026-10-02
- 22To inspect desktop connectivity, Cisco says to use the browser developer tools Network tab filtered to WebSocket (WS) traffic to the api.wxcc-<datacenter>.cisco.com domain, and to capture keepalive traffic with Wireshark or similar if needed.Troublshoot Agent Desktop Disconnect Issues · Troubleshoot: browser logs and network capture · Checked 2026-10-02
- 23Analyzer provides a stock report named Dropped call summaries under Stock Reports > Historical Reports > Agent Reports.Cisco Webex Contact Center Analyzer User Guide · Stock Reports > Historical Reports > Agent Reports > Dropped call summaries · Checked 2026-10-02
- 26The Agent Desktop End Consult voice feature, which lets agents end consult calls during an active customer interaction, is enabled by default.Desktop settings for Webex Contact Center · Tenant Settings > Desktop > Voice Features: End Consult · Checked 2026-10-02
- 27A call that consistently drops at a fixed duration, such as just under the session interval or at half of it, points to a session-timer refresh (re-INVITE or UPDATE) that is not sent, not delivered or not answered on some leg, rather than to an agent or desktop action.inferredRFC 4028: Session Timers in the Session Initiation Protocol (SIP) · Section 10 (Performing refreshes) · Checked 2026-10-02
- 28Cisco's Local Gateway configuration for a Webex Calling registration-based trunk includes no session refresh in the tenant configuration, which disables SIP session refresh for calls between CUBE and Webex.Configure Local Gateway on Cisco IOS XE for Webex Calling · Configure Webex Calling registration-based trunk: voice class tenant · Checked 2026-10-02
- 29The Lost Connection Recovery Timeout is set in Control Hub under Services > Contact Center > Tenant Settings > Desktop, in the System Settings section.Desktop settings for Webex Contact Center · Tenant Settings > Desktop > System Settings · Checked 2026-10-02
- 30The Webex Contact Center Lost Connection Recovery Timeout defaults to 120 seconds and accepts 120 to 600 seconds.Desktop settings for Webex Contact Center · Tenant Settings > Desktop > System Settings: Lost Connection Recovery Timeout · Checked 2026-10-02
- 31If an agent's network outage lasts longer than the Lost Connection Recovery Timeout, the agent is signed out of Agent Desktop.Desktop settings for Webex Contact Center · Tenant Settings > Desktop > System Settings: Lost Connection Recovery Timeout · Checked 2026-10-02
- 32Webex Contact Center requires any codec other than G.711 (for example G.729, iLBC or Opus) to be transcoded before it reaches the Webex Contact Center media edge.Set up voice channels for Webex Contact Center · SIP and media requirements: codec · Checked 2026-10-02
- 33On a Local Gateway with media inactivity detection enabled, a call that sends no RTP or RTCP for long enough, as can happen during some hold or consult states, may be released by the gateway; hold-time drops on BYO PSTN should be checked against that timer.inferredCisco IOS Voice Command Reference - T through Z - timeouts call-disconnect through timing clear-wait · timer receive-rtcp: Usage Guidelines · Checked 2026-10-02
- 34Webex Contact Center voice can reach the PSTN through Webex Contact Center PSTN (contiguous US and Canada only), Cloud Connected PSTN through certified providers, Cisco Calling Plan, or a premises Webex Calling Local Gateway.Set up voice channels for Webex Contact Center · PSTN connectivity options · Checked 2026-10-02
- 35Under RFC 4028, a 422 (Session Interval Too Small) response must carry a Min-SE header with the minimum timer the server will accept.RFC 4028: Session Timers in the Session Initiation Protocol (SIP) · Section 6 (422 response code definition) · Checked 2026-10-02
- 36Under RFC 4028, if no session refresh arrives before the session expires, the side that is not the refresher should send a BYE slightly before expiry, recommended at the lesser of 32 seconds and one third of the session interval before it.RFC 4028: Session Timers in the Session Initiation Protocol (SIP) · Section 10 (Performing refreshes), session expiration paragraph · Checked 2026-10-02
- 37Under RFC 4028, the Min-SE value must not be less than 90 seconds and defaults to 90 seconds when the header is absent.RFC 4028: Session Timers in the Session Initiation Protocol (SIP) · Section 5 (Min-SE header field definition) · Checked 2026-10-02
- 38RFC 4028 recommends a session interval (Session-Expires) of 1800 seconds.RFC 4028: Session Timers in the Session Initiation Protocol (SIP) · Section 4 (Session-Expires header field definition) · Checked 2026-10-02
- 39RFC 4028 recommends sending the session refresh once half the session interval has elapsed.RFC 4028: Session Timers in the Session Initiation Protocol (SIP) · Section 10 (Performing refreshes) · Checked 2026-10-02
- 40The RFC 4028 refresher parameter of Session-Expires, set to uac or uas, names which side of the dialog performs the session refreshes.RFC 4028: Session Timers in the Session Initiation Protocol (SIP) · Section 4 (refresher parameter) · Checked 2026-10-02
- 41When an agent does not respond to an offered contact within the RONA time, the contact returns to the queue and the agent's state for that channel changes from Available to Idle.Understand agent states · RONA (Ring No Answer) Behavior Optimization · Checked 2026-10-02
- 42The Webex Contact Center telephony RONA timeout defaults to 18 seconds and is configurable from 1 to 120 seconds.Desktop settings for Webex Contact Center · Tenant Settings > Desktop > RONA Timeouts: Telephony · Checked 2026-10-02
- 43The Webex Contact Center Short Call Threshold, set under Tenant Settings > Voice, determines whether a call is classed as short or abandoned and defaults to 0 seconds.Set up voice settings for Webex Contact Center · Tenant Settings > Voice: Short Call Threshold · Checked 2026-10-02
- 44In the Analyzer Agent Details, Agent Trace and Agent Details by Social Channels stock reports, the Sudden Disconnected Count field is documented as currently not used and not populated.Webex Contact Center Analyzer Stock Reports · Agent Details report; Agent Trace report; Agent Details by Social Channels report: Sudden Disconnected Count note · Checked 2026-10-02
- 45An empty or zero Sudden Disconnected Count in the agent-level Analyzer reports should not be read as evidence that no calls dropped at answer, because Cisco documents that field as unpopulated in those reports; termination fields are the better evidence.inferredWebex Contact Center Analyzer Stock Reports · Agent Details report and Agent Trace report: Sudden Disconnected Count note · Checked 2026-10-02
- 46The Webex Contact Center Sudden Disconnect Threshold is a time interval in seconds that decides whether a call that ends soon after reaching a destination counts as handled by the agent or as a sudden disconnect; its default for a new tenant is 30 seconds.Set up voice settings for Webex Contact Center · Tenant Settings > Voice: Sudden Disconnect Threshold · Checked 2026-10-02
- 47The Sudden Disconnect Threshold is set in Control Hub under Services > Contact Center > Tenant Settings > Voice.Set up voice settings for Webex Contact Center · Tenant Settings > Voice: Sudden Disconnect Threshold · Checked 2026-10-02
- 48Analyzer defines Sudden Disconnect as calls that were answered (connected to an agent or accepted by a destination site) but then disconnected within the Sudden Disconnect threshold provisioned for the enterprise.Cisco Webex Contact Center Analyzer User Guide · Agent Details report field definitions: Sudden Disconnect · Checked 2026-10-02
- 49When opening a TAC case for Agent Desktop problems, Cisco asks for the Customer Org ID, shown at the bottom of the Control Hub page, plus details of the environment (VDI, work from home, VPN) and of recent configuration changes.Troubleshoot Webex Contact Center Agent Desktop · Information to collect before contacting TAC · Checked 2026-10-02
- 50For a troubled Webex Contact Center call, Cisco TAC asks for the ANI or Contact Session ID, the exact timestamp of the failure, the agent information and a screenshot of any error.Data Requirements to Troubleshoot Webex Contact Center Calls · Data to collect for inbound and outbound call failures · Checked 2026-10-02
- 51Cisco documents that CUCM-registered video devices disconnect exactly 15 minutes into a Webex meeting when the session refresh due at half of the 1800-second SIP Session Expires Timer is not received by the far side, which it attributes to network devices in between.Video Calls to Webex Meeting Disconnect after 15 Minutes · Problem; Cause · Checked 2026-10-02
- 52The Webex Contact Center voice channel requirements list SIP Early Offer as not supported and SIP Delayed Offer as supported.Set up voice channels for Webex Contact Center · SIP and media requirements table · Checked 2026-10-02
- 53Webex Contact Center Desktop WebRTC calling supports Google Chrome 144 or later, Microsoft Edge 144 or later and Mozilla Firefox 140 or later.System requirements for Webex Contact Center Desktop · Supported browsers for WebRTC · Checked 2026-10-02
- 54For WebRTC calls in Agent Desktop, Cisco describes opening chrome://webrtc-internals in a new tab during the active call, selecting the session for the desktop.wxcc domain, and using Create a WebRTC-Internals dump to download the statistics.Exploring WebRTC Data and Statistics in WxCC Agent Desktop · Accessing WebRTC statistics; Log collection · Checked 2026-10-02
- 55If WebRTC disconnects after an agent signs in, Agent Desktop moves the voice channel to Idle and disables the Available options for voice until WebRTC reconnects, so voice calls that cannot connect are not routed.Understand agent states · WebRTC and Browser-Based Desktop · Checked 2026-10-02
- 56Agent Desktop is supported in VDI environments, but WebRTC (Desktop) calling is not.System requirements for Webex Contact Center Desktop · VDI support · Checked 2026-10-02
- 57The WebRTC tenant voice setting lets agents and supervisors make and receive calls in the browser, and it is enabled by default for new tenants.Set up voice settings for Webex Contact Center · Tenant Settings > Voice: WebRTC · Checked 2026-10-02
Documents
tier 1 standards and regulators
RFC 4028: Session Timers in the Session Initiation Protocol (SIP)
tier 2 current vendor documentation
Cisco IOS Voice Command Reference - T through Z - timeouts call-disconnect through timing clear-wait
tier 2 current vendor documentation
Cisco Unified Border Element Configuration Guide (IOS XE) - SIP Session Timer Support
tier 2 current vendor documentation
Cisco Webex Contact Center Analyzer User Guide
tier 2 current vendor documentation
Configure Local Gateway on Cisco IOS XE for Webex Calling
tier 2 current vendor documentation
Data Requirements to Troubleshoot Webex Contact Center Calls
tier 2 current vendor documentation
Desktop settings for Webex Contact Center
tier 2 current vendor documentation
Exploring WebRTC Data and Statistics in WxCC Agent Desktop
tier 2 current vendor documentation
Manage your calls in Agent Desktop
tier 2 current vendor documentation
Set up voice channels for Webex Contact Center
tier 2 current vendor documentation
Set up voice settings for Webex Contact Center
tier 2 current vendor documentation
System requirements for Webex Contact Center Desktop
tier 2 current vendor documentation
Troubleshoot Webex Calling calls in Control Hub
tier 2 current vendor documentation
Troubleshoot Webex Contact Center Agent Desktop
tier 2 current vendor documentation
Troublshoot Agent Desktop Disconnect Issues
tier 2 current vendor documentation
Understand agent states
tier 2 current vendor documentation
Video Calls to Webex Meeting Disconnect after 15 Minutes
tier 2 current vendor documentation
Webex Contact Center Analyzer Stock Reports
Cite this page
APA
WarmTransfer. (2026, October 2). Troubleshooting Webex Contact Center calls that drop after the agent answers. WarmTransfer. https://warmtransfer.net/knowledge/wxcc-call-drop-troubleshooting
BibTeX
@misc{warmtransfer-wxcc-call-drop-troubleshooting,
title = {Troubleshooting Webex Contact Center calls that drop after the agent answers},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/wxcc-call-drop-troubleshooting},
note = {Verified 2026-10-02}
}