Troubleshooting Webex Contact Center Agent Desktop sign-in and station login

See also

Sources

1. 1
   The agent's details are saved in browser preferences whether or not Don't show this again is checked, and auto sign-in can be turned off later in Profile Settings.

   Sign in to Agent Desktop · Sign in to Agent Desktop > step 6 Don't show this again · Checked 2026-09-30
2. 2
   If an automatic sign-in (Don't show this again checked) fails, for example because the previously used dial number is no longer valid or is in use, Agent Desktop falls back to the interaction preferences screen, pre-populated with the saved preferences.

   Sign in to Agent Desktop · Sign in to Agent Desktop > step 6 Don't show this again · Checked 2026-09-30
3. 3
   If a banner says some Desktop features are unavailable, reloading the browser refreshes the session and removes the banner.

   Sign in to Agent Desktop · Sign in to Agent Desktop > banner note · Checked 2026-09-30
4. 4
   The current Desktop system requirements set minimum browser versions of Chrome 144+, Microsoft Edge 144+ and Firefox 140+, and recommend the latest stable version of each.

   System requirements for Webex Contact Center Desktop · System requirements for Webex Contact Center Desktop > Browser requirements table · Checked 2026-09-30
5. 5
   The browser must have cookies and site data enabled, the pop-up blocker disabled, JavaScript enabled, images enabled and security level set to Medium.

   System requirements for Webex Contact Center Desktop · System requirements for Webex Contact Center Desktop > Browser settings list · Checked 2026-09-30
6. 6
   To avoid unexpected Desktop sign-outs, Cisco recommends turning off Memory Saver and Energy Saver in Chrome and the equivalent settings in Edge, or adding the Desktop URL as an exception, and setting browser.tabs.unloadOnLowMemory to false in Firefox.

   Configure Environment to Prevent Agent Desktop Logout · Configure Environment to Prevent Agent Desktop Logout > Browser configuration · Checked 2026-09-30
7. 7
   For a Control Hub user to act as an agent, the contact center user record needs contact center access enabled, a site, one or more teams, an agent (desktop) profile and a user profile. A multimedia profile is also needed where the administrator uses one.

   Manage Contact Center Users · Manage Contact Center Users > Edit user agent settings · Checked 2026-09-30
8. 8
   The Desktop system requirements recommend a minimum of 512 kbps of network bandwidth and list 10 Mbps as the minimum network speed.

   System requirements for Webex Contact Center Desktop · System requirements for Webex Contact Center Desktop > Network requirements · Checked 2026-09-30
9. 9
   Agent Desktop needs these domains allowed through the firewall and VPN, all over HTTPS on port 443: *.cisco.com, *.ciscoccservice.com, *.ciscospark.com, *.wbx2.com, *.webex.com and *.broadcloudpbx.net.

   Webex Contact Center network connectivity requirements · Webex Contact Center network connectivity requirements > Domain access for Desktop · Checked 2026-09-30
10. 10
    The Agent Desktop display must be larger than 500 x 500 pixels (width x height), and browser zoom should be 100%.

    Sign in to Agent Desktop · Sign in to Agent Desktop > display notes · Checked 2026-09-30
11. 11
    For a Dial Number, Agent Desktop accepts an international format (+ country code, then number) and a non-international entry in either E.164 format or IDD format (IDD prefix, country code, number).

    Sign in to Agent Desktop · Sign in to Agent Desktop > Dial Number > International format / Non-international format · Checked 2026-09-30
12. 12
    With desktop profile DN validation set to Provisioned DN, the sign-in DN is restricted to the Default DN provisioned in the agent's user settings.

    Manage desktop profiles · Manage desktop profiles > Voice channel options > Agent DN validation > Provisioned DN · Checked 2026-09-30
13. 13
    With desktop profile DN validation set to Unrestricted, agents can sign in with any DN through the Station Credentials prompt, but an ad hoc DN that breaks the sign-in syntax rules is rejected.

    Manage desktop profiles · Manage desktop profiles > Voice channel options > Agent DN validation > Unrestricted · Checked 2026-09-30
14. 14
    In the release entry dated 2025-10-29 (Simplified agent sign-in experience), the sign-in screen began showing only the options relevant to the agent's profile and pre-filling a single configured dial number or extension.

    What's new for agents in Webex Contact Center · What's new for agents > October 29, 2025 > Simplified agent sign-in experience · Checked 2026-09-30
15. 15
    If an agent has accepted E911 notifications but still cannot connect with desktop telephony, the cause may be RONA, and the agent should give the administrator the Tracking ID.

    Sign in to Agent Desktop · Sign in to Agent Desktop > Desktop option E911 note · Checked 2026-09-30
16. 16
    If an agent picks a team at sign-in and then clears it, Save & Continue stays enabled, and clicking it with no team selected causes a sign-in error.

    Sign in to Agent Desktop · Sign in to Agent Desktop > step 7 team note · Checked 2026-09-30
17. 17
    An Extension is a short-form internal number that may belong to a Webex Calling endpoint or a Unified Communications endpoint, and every dialed number and extension must be configured and reachable in Webex PSTN and routing and in the organisation's telephony.

    Set up voice channels for Webex Contact Center · Set up voice channels for Webex Contact Center > Extension definition and reachability note · Checked 2026-09-30
18. 18
    When an agent enters an Extension, the sign-in screen tries to match it to a registered Webex Calling endpoint. If a match is found, extra phone control features become available, including choosing a preferred device.

    Set up voice channels for Webex Contact Center · Set up voice channels for Webex Contact Center > Extension definition · Checked 2026-09-30
19. 19
    On Firefox ESR V104.0 or later on Windows or macOS, Enhanced Tracking Protection must be turned off for the Desktop URL.

    System requirements for Webex Contact Center Desktop · System requirements for Webex Contact Center Desktop > Firefox ESR note · Checked 2026-09-30
20. 20
    Agent Desktop can take a few seconds to load the first time it is opened or after the browser cache is cleared.

    Sign in to Agent Desktop · Sign in to Agent Desktop > loading note · Checked 2026-09-30
21. 21
    The tenant desktop setting Force default DN, when enabled, restricts agents to their provisioned default DN when they sign in to Agent Desktop.

    Desktop settings for Webex Contact Center · Desktop settings for Webex Contact Center > Manage voice features for desktop > Force default DN · Checked 2026-09-30
22. 22
    An administrator can force an agent to sign out in Control Hub at Services > Contact Center > User management > Contact center users > Signed in users tab, using the Force sign out icon on the agent's row.

    Manage Contact Center Users · Manage Contact Center Users > Force sign out agents · Checked 2026-09-30
23. 23
    To force an agent to sign out, the administrator or supervisor needs the Sign out agents permission, found in their user profile under Supervisory & desktop permissions.

    Manage Contact Center Users · Manage Contact Center Users > Force sign out agents > prerequisite · Checked 2026-09-30
24. 24
    If logout problems continue after these configuration changes, Cisco tells customers to open a TAC case with the Desktop Error Report and the browser networking (HAR) logs.

    Configure Environment to Prevent Agent Desktop Logout · Configure Environment to Prevent Agent Desktop Logout > Troubleshoot · Checked 2026-09-30
25. 25
    If the tenant Inactivity timeout is enabled, Agent Desktop automatically signs out an agent who stays inactive for the configured time. The configurable range is 3 to 10,000 minutes.

    Desktop settings for Webex Contact Center · Desktop settings for Webex Contact Center > Manage desktop experience > Inactivity timeout · Checked 2026-09-30
26. 26
    For an agent who is already signed in elsewhere, the documented fixes are to click Continue in the multiple-instance prompt in the browser they want to use, or have an administrator or supervisor with the Sign out agents permission force a sign-out from Control Hub.inferred

    Manage Contact Center Users · Manage Contact Center Users > Force sign out agents; with n6lmci8 multiple-instance note · Checked 2026-09-30
27. 27
    When a station login is rejected for a dial number, the first things to check are the desktop profile's DN validation mode (Unrestricted syntax rules or Provisioned DN), whether the tenant Force default DN setting is on, and whether the agent has a Default DN provisioned.inferred

    Manage desktop profiles · Manage desktop profiles > Agent DN validation; with nu0du4c Force default DN · Checked 2026-09-30
28. 28
    An SSO loop or failure at Agent Desktop sign-in most likely comes from the Control Hub and IdP configuration, such as a uid-email mismatch, an expired SSO certificate, or a stale IdP session with no Single Logout, rather than from a Contact Center setting. That makes the SAML tracer and a private window the first diagnostics.inferred

    Single Sign-On Integration in Control Hub · Single Sign-On Integration in Control Hub > requirements and Troubleshooting; combined with nstvmyo certificate and SLO sections · Checked 2026-09-30
29. 29
    An agent is signed out of Agent Desktop when a network outage outlasts the Lost Connection Recovery Timeout. The default is 120 seconds and the range is 120 to 600 seconds.

    Desktop settings for Webex Contact Center · Desktop settings for Webex Contact Center > Manage system settings > Lost Connection Recovery Timeout · Checked 2026-09-30
30. 30
    Agent Desktop cannot be used in multiple browsers or in multiple tabs of the same browser. Signing in to a second instance shows a prompt, and clicking Continue signs the agent in on that window.

    Sign in to Agent Desktop · Sign in to Agent Desktop > note on multiple browsers or tabs · Checked 2026-09-30
31. 31
    If no Default DN is provisioned for an agent, the agent can enter any DN to sign in.

    Manage desktop profiles · Manage desktop profiles > Voice channel options > Agent DN validation > Default DN note · Checked 2026-09-30
32. 32
    Sign-in does not check device status in real time. The agent must make sure the selected or entered dial number or extension belongs to an active, available device.

    What's new for agents in Webex Contact Center · What's new for agents > October 29, 2025 > Simplified agent sign-in experience · Checked 2026-09-30
33. 33
    To get incoming-call notifications reliably, the agent must check their notification settings, in particular the Do not disturb option.

    Set up voice channels for Webex Contact Center · Set up voice channels for Webex Contact Center > notifications note · Checked 2026-09-30
34. 34
    The same TechNote recommends lengthening the Windows sleep timer and turning on the macOS option that prevents automatic sleep when the display is off, so agents stay signed in.

    Configure Environment to Prevent Agent Desktop Logout · Configure Environment to Prevent Agent Desktop Logout > Operating system settings · Checked 2026-09-30
35. 35
    An inactivity timeout set in a desktop profile overrides the tenant-level inactivity timeout.

    Configure Environment to Prevent Agent Desktop Logout · Configure Environment to Prevent Agent Desktop Logout > Application configuration > Desktop inactivity timeout · Checked 2026-09-30
36. 36
    The desktop profile sets which voice options an agent can use at sign-in: Agent DN, Extension, and Desktop (browser WebRTC).

    Manage desktop profiles · Manage desktop profiles > Voice channel options · Checked 2026-09-30
37. 37
    For an agent using a PSTN number, the older station credentials screen needs Dial Number selected, International Dialing Format checked and the correct country code chosen. Leaving these out can cause immediate RONA when a call is offered.

    Troubleshoot RONA Issue When Agents Enter Dial Number in Wrong Tab · Troubleshoot RONA Issue When Agents Enter Dial Number in Wrong Tab > Solution > PSTN numbers · Checked 2026-09-30
38. 38
    The Signed in users tab does not show users signed in only as Supervisors, but it does show users signed in as Supervisor/Agent.

    Manage Contact Center Users · Manage Contact Center Users > Force sign out agents > note · Checked 2026-09-30
39. 39
    Agent Desktop sign-in runs in this order: open the administrator-provided URL, enter an email address, enter a password, choose an interaction (calling) preference, choose a team, then click Save & Continue.

    Sign in to Agent Desktop · Sign in to Agent Desktop > procedure steps 1-8 · Checked 2026-09-30
40. 40
    To sign out, the agent sets availability to Idle, then chooses User Profile > Sign Out. Sign-out is blocked during an active conversation or an ongoing monitoring task.

    Sign in to Agent Desktop · Sign in to Agent Desktop > sign out paragraph · Checked 2026-09-30
41. 41
    If an SSO certificate expires, users may lose access to Webex services.

    Manage single sign-on integration in Control Hub · Manage single sign-on integration in Control Hub > certificate renewal · Checked 2026-09-30
42. 42
    If Single Logout is not configured, the IdP session stays valid after Webex sign-out, so users may not be asked to reauthenticate next time, and Webex tells users to close their browsers to invalidate open sessions.

    Manage single sign-on integration in Control Hub · Manage single sign-on integration in Control Hub > Single Logout · Checked 2026-09-30
43. 43
    When updating SSO metadata, Cisco recommends running Test SSO Update and checking the sign-in experience in a private browser window so cached information does not interfere.

    Manage single sign-on integration in Control Hub · Manage single sign-on integration in Control Hub > update metadata / test · Checked 2026-09-30
44. 44
    For SSO troubleshooting, Cisco recommends the SAML tracer add-on for Firefox, Chrome or Edge to inspect the SAML flow.

    Single Sign-On Integration in Control Hub · Single Sign-On Integration in Control Hub > Troubleshooting · Checked 2026-09-30
45. 45
    With Control Hub SSO, the IdP must conform to SAML 2.0 and must match one of the user's email addresses to the uid at sign-in.

    Single Sign-On Integration in Control Hub · Single Sign-On Integration in Control Hub > requirements · Checked 2026-09-30
46. 46
    The help article Troubleshoot Webex Contact Center Agent Desktop (WBX9000037385, updated 2025-02-24) still lists Chrome V76.0.3809+, Firefox ESR V68+ and Edge Chromium V79+ as supported browsers, which conflicts with the current system requirements article.disputed

    Troubleshoot Webex Contact Center Agent Desktop · Troubleshoot Webex Contact Center Agent Desktop > Browser Requirements · Checked 2026-09-30
47. 47
    Agent Desktop offers three calling preferences at sign-in (Desktop, Extension and Dial Number), and which of them appear depends on the agent's profile configuration.

    Sign in to Agent Desktop · Sign in to Agent Desktop > step 5 interaction preferences · Checked 2026-09-30
48. 48
    The Desktop system requirements list Windows 10/11, macOS 10.15+, ChromeOS, iOS 18+ and Linux as supported operating systems.

    System requirements for Webex Contact Center Desktop · System requirements for Webex Contact Center Desktop > Operating system · Checked 2026-09-30
49. 49
    When collecting information for a Webex Contact Center TAC case, include the Customer Org ID, which appears at the bottom of the Control Hub page.

    Troubleshoot Webex Contact Center Agent Desktop · Troubleshoot Webex Contact Center Agent Desktop > Collect Generic Information for all Webex Contact Center Issues · Checked 2026-09-30
50. 50
    If the optional Microsoft Teams authentication during sign-in is cancelled or fails, a warning icon and a notification appear, and the agent can authenticate later from profile settings after signing in to Desktop.

    Sign in to Agent Desktop · Sign in to Agent Desktop > step 4 Microsoft Teams authentication · Checked 2026-09-30
51. 51
    When an API request or event fails to load data, Desktop shows an error notification. The agent can open Error Details, copy the tracking ID for the administrator, and download an error report.

    Resolve error issues · Resolve error issues > procedure · Checked 2026-09-30
52. 52
    Agent Desktop is supported in VDI, but WebRTC (the Desktop voice option) is not.

    System requirements for Webex Contact Center Desktop · System requirements for Webex Contact Center Desktop > VDI note · Checked 2026-09-30
53. 53
    WebRTC needs at least 100 kbps of network bandwidth per call.

    Set up voice channels for Webex Contact Center · Set up voice channels for Webex Contact Center > WebRTC section · Checked 2026-09-30
54. 54
    WebRTC Desktop support is not available to Webex Contact Center customers hosted in the Japan data center.

    Set up voice channels for Webex Contact Center · Set up voice channels for Webex Contact Center > WebRTC section · Checked 2026-09-30
55. 55
    The Desktop option handles voice through WebRTC in the browser, and Agent Desktop does not support headset control actions for WebRTC-based calls.

    Sign in to Agent Desktop · Sign in to Agent Desktop > step 5 > Desktop note · Checked 2026-09-30
56. 56
    The Desktop (WebRTC) voice option is available to both Premium and Standard agents and needs no extra licence.

    Manage desktop profiles · Manage desktop profiles > Voice channel options > Desktop · Checked 2026-09-30
57. 57
    Picking the wrong station credentials option for the agent's actual endpoint lets sign-in succeed, but the result is an immediate Route-On-No-Answer (RONA) when the first call is offered.

    Troubleshoot RONA Issue When Agents Enter Dial Number in Wrong Tab · Troubleshoot RONA Issue When Agents Enter Dial Number in Wrong Tab > Problem statement · Checked 2026-09-30
58. 58
    For Webex Calling users, sign-in checks that an extension or dial number chosen from the drop-down is valid and assigned to the agent's Webex Calling profile.

    What's new for agents in Webex Contact Center · What's new for agents > October 29, 2025 > Simplified agent sign-in experience · Checked 2026-09-30

Documents

Cite this page

WarmTransfer. (2026, September 30). Troubleshooting Webex Contact Center Agent Desktop sign-in and station login. WarmTransfer. https://warmtransfer.net/knowledge/wxcc-agent-login-troubleshooting

@misc{warmtransfer-wxcc-agent-login-troubleshooting,
  title  = {Troubleshooting Webex Contact Center Agent Desktop sign-in and station login},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/wxcc-agent-login-troubleshooting},
  note   = {Verified 2026-09-30}
}