webex contact center · published

Webex Contact Center network and browser requirements for agents

Verified 2026-10-02 · 57 sources · tier 2 · 2 disputed

Disputed: 2 sources below carry conflicting evidence.

Webex Contact Center network and browser requirements for agents

Cisco publishes minimum browser, operating system, memory and network-speed figures for Webex Contact Center Desktop, and a list of domains that administrators add to the firewall or VPN allowed list 2425282615. The WebRTC (Desktop) voice option has its own per-call bandwidth figure, its own supported browsers, and a network test that Cisco directs administrators to run before deployment 434644.

Browser, operating system and hardware

The minimum supported browsers for Webex Contact Center Desktop are Chrome 144 or later, Microsoft Edge 144 or later, and Firefox 140 or later 24. Cisco recommends the latest stable version of Chrome, Microsoft Edge or Firefox 29.

The minimum operating systems listed are Windows 10 or 11, macOS 10.15 or later, ChromeOS, iOS 18 or later, and Linux 25. The Desktop requires at least 4 GB of RAM, and Cisco recommends 8 GB or more 28.

The Agent Desktop display must be larger than 500 x 500 pixels, and Cisco recommends 100 percent browser zoom 33. When the viewing area is narrower than 1280 pixels, the task list appears above the task page and the interaction control pane 21. Below 736 pixels wide, the title and logo are hidden 21.

An agent cannot use the Agent Desktop in multiple browsers at the same time, or in multiple tabs of the same browser window 34.

Network speed and bandwidth

The System requirements article lists 10 Mbps as the minimum network speed for the Desktop and 10 Mbps or higher as recommended 26. For optimal Desktop performance, Cisco states a minimum recommended network bandwidth of 512 kbps 14. Desktop data payloads average 1 to 100 kbps and can peak at 2 to 3 MB 14. The WebRTC (Desktop) voice option requires a minimum network bandwidth of 100 kbps per call 43.

WarmTransfer's reading of the sources is that Cisco gives these as separate figures, 512 kbps for desktop data and 100 kbps per WebRTC call, and publishes no combined per-agent bandwidth budget 19. We infer that planners who add these figures together are making their own assumption 19.

Firewall and domain allowlisting

Cisco instructs administrators to add the domains listed under Domain access for desktop to the firewall or VPN allowed list so that the Desktop responds as expected on their network 15. All domains in that list use HTTPS by default and therefore operate over TCP port 443 16. A leading asterisk, as in *.webex.com, means that the top-level domain and all of its subdomains must be reachable 54.

Domain Stated purpose
*.ciscoccservice.com Critical microservices domain; Cisco gives its purpose as routing, analytics and AI-powered assistance 5
*.cisco.com, *.ciscospark.com, *.wbx2.com, *.webex.com Webex Contact Center microservice domains 6
*.webexengage.com Digital channels such as SMS, email, live chat, Facebook Messenger and WhatsApp 42
*.split.io, *.lr-ingest.com Performance tracking, error and crash capture, and session telemetry 35
*.broadcloudpbx.net BroadCloud integration 2
cjp-ccone-prod<region>-media-storage-recording Region-specific Amazon S3 buckets that serve as the regional CDN for media storage and recordings 30

Region-specific media storage and recording buckets are listed for the US, Australia (ap-southeast-2), Canada (ca-central-1), Singapore (ap-southeast-1), Japan (ap-northeast-1), Europe (eu-west-2 and eu-central-1) and India (ap-south-1) 31. For the US region, the listed domains are cjp-ccone-produs1-media-storage-recording.s3.amazonaws.com and cjp-ccone-produs1-media-storage-recording.s3.us-east-1.amazonaws.com 32.

Published IP addresses

The network connectivity article publishes static public IP addresses for Webex Engage and Webex Connect for each data centre 17. Those data centres are AWS Ireland, Oregon, Canada, London, Sydney, Mumbai and Singapore, plus Azure US 17.

Cisco also publishes per-data-centre source IP addresses that Webex Contact Center uses when it calls external services on customer premises, so that customers can allow those calls through their firewalls 27. These addresses vary by data centre, covering the US, UK, Australia, Germany, Canada, Japan, Singapore and India 27.

Content Security Policy allowed list

Webex Contact Center has a Content Security Policy allowed list that defines the trusted domains Webex Contact Center applications may access 13. Administrators set this list in Control Hub under Services > Contact Center > Tenant settings > Security 13. After a domain is added to the list, it takes 10 minutes before the Agent Desktop loads within an iFrame 12.

WebRTC (Desktop) voice option

To offer the Desktop (WebRTC) voice option, an administrator enables the Desktop checkbox in the Voice Channel options of the agent's Desktop Profile, under Desktop Experience > Desktop Profiles 47. The option is supported on Google Chrome, Microsoft Edge and Mozilla Firefox 46. Support for Edge and Firefox, in addition to Chrome, was announced in the agent release notes entry dated October 30, 2024 48.

Cisco's WebRTC guidance includes configuring browser and Windows notification and Do Not Disturb settings in Chrome, Edge and Firefox so that agents reliably get notified of incoming calls 51. The Agent Desktop does not support headset control actions for WebRTC-based calls 50.

WebRTC support for Supervisor Desktop, which lets supervisors take calls in the browser with a headset, was announced in the release entry dated November 13, 2024 52. Background Noise Removal for agents using the WebRTC desktop was announced in the release entry dated June 11, 2026 45.

Agent devices and phones

Agents who handle voice interactions must have a phone, and they enter its dial number or extension in the Station Credentials at sign-in 40. Supported agent devices include Webex Calling desk phones, the Webex Calling desktop app, Webex App for mobile, Webex App integrated with Webex Calling, and the Microsoft Teams softphone 1.

Virtual desktop infrastructure

The Agent Desktop is supported in a Virtual Desktop Infrastructure (VDI), but the WebRTC (Desktop) voice option is not supported in VDI 38. In third-party VDI systems, some Desktop keyboard shortcuts may not work as intended 39.

Ports, transport and QoS

For Desktop firewall requirements, the Webex Contact Center System requirements article points to the Webex Calling port reference article 18. WarmTransfer's reading of the sources is that the WebRTC rows of that Webex Calling reference are the best available Cisco statement of the media ports a Webex Contact Center browser softphone needs, because no Webex Contact Center-specific WebRTC port table was found 20.

The Webex Calling port reference lists DSCP markings for Webex App audio and Webex App video 56. The same reference recommends an enterprise proxy server option if the firewall does not support domain or URL filtering 55.

For all Webex voice and video media streams, Cisco prefers and strongly recommends UDP as the transport, because TCP retransmission and buffering add latency and jitter 41. When Webex apps fall back to TLS for media and a proxy is configured, the media is routed through the proxy, which Cisco warns can create bandwidth bottlenecks and packet loss 36.

Testing network quality with CScan

For network quality, the System requirements article points to CScan 18. Cisco advises checking network quality after enabling the Desktop (WebRTC) voice option 4. Before deploying WebRTC, Cisco directs administrators to run the Advanced CScan test from the networks where WebRTC will be deployed 44.

The CScan Basic test reports the following toward Webex Calling 8:

  • estimated concurrent calls 8
  • download and upload bandwidth 8
  • latency (RTT) 8
  • a traceroute 8
  • TCP port reachability 8

The Advanced diagnostic test adds download and upload packet loss and jitter to the Basic test results 7. It needs access to the PC speaker and microphone 7.

CScan cannot detect any of the following 9:

  • whether the network is wired or wireless 9
  • DHCP or DNS availability 9
  • SRV support 9
  • the NTP port 9
  • proxies 9
  • QoS (ToS/DSCP) marking 9
  • VPN use 9

When raising Webex Contact Center issues, Cisco's agent desktop troubleshooting guidance asks for environment details, including virtual desktop use, work-from-home status and VPN use 37.

See also

Applicability

Applies to: Cisco Webex Contact Center, Cisco Webex Calling, and Cisco Webex App. Deployments: multi-tenant. Sources checked 2026-10-02. WebRTC Desktop support is unavailable to Webex Contact Center customers hosted in the Japan data centre 49. This is disputed material: the older Troubleshoot Webex Contact Center Agent Desktop article that this article compares against was updated 2025-02-24 22.

What remains uncertain

Sources disagree on browser minimums: the older Troubleshoot Webex Contact Center Agent Desktop article lists Chrome 76.0.3809 or later, Firefox ESR 68 or later, and Edge Chromium 79 or later 22, while the System requirements article lists Chrome 144, Edge 144 and Firefox 140 or later 24. Sources disagree on memory and operating systems: the older article states 2 GB of application RAM, excluding the operating system allocation, and lists Windows 10+, macOS 10.12+ and Chrome OS 70 (64-bit)+ 23, while the System requirements article lists 4 GB minimum and macOS 10.15 or later 2825.

Cisco's agent troubleshooting guidance asks whether a VPN is in use 37. A Cisco VPN split-tunnel recommendation for the Agent Desktop URL is not covered by the sources below.

The desktop domain list includes region-specific Amazon S3 buckets 30. Whether the desktop also needs third-party CDN domains outside that list is not covered by the sources below.

WarmTransfer's reading of the sources is that the CScan help article does not publish numeric pass thresholds for latency, jitter or packet loss 10. Cisco latency, jitter and packet-loss thresholds for Webex Contact Center WebRTC agents from any other source are not covered by the sources below.

A human read of the WebRTC and CScan rows in the Webex Calling port reference is not covered by the sources below. The Webex Calling media IP subnet list referenced by those WebRTC rows is not covered by the sources below.

The Webex Calling port reference recommends an enterprise proxy when the firewall cannot filter by domain or URL 55, and Cisco warns that TLS media routed through a proxy can create bottlenecks and packet loss 36. Proxy guidance specific to the Webex Contact Center desktop and WebRTC, including explicit proxy TLS inspection, is not covered by the sources below.

Network requirements for Webex Contact Center on Webex for Government or FedRAMP are not covered by the sources below. Regional Agent Desktop URLs are not covered by the sources below.

See also

Related to

Referenced by

Sources

  1. 1
    Supported Webex Contact Center agent devices include Webex Calling desk phones, the Webex Calling desktop app, Webex App for mobile, Webex App integrated with Webex Calling, and the Microsoft Teams softphone.
    System requirements for Webex Contact Center Desktop · section 'Agent devices' · Checked 2026-10-02
  2. 2
    *.broadcloudpbx.net is on the Webex Contact Center desktop domain list for BroadCloud integration.
    Webex Contact Center network connectivity requirements · section 'Domain access for desktop', domain table row *.broadcloudpbx.net · Checked 2026-10-02
  3. 3
    The Webex Contact Center System requirements article requires these browser settings: cookies enabled, JavaScript enabled, images enabled, pop-up blockers disabled, and the security level set to Medium.
    System requirements for Webex Contact Center Desktop · browser settings list within the minimum requirements content (exact heading not captured) · Checked 2026-10-02
  4. 4
    Cisco advises checking network quality after enabling the Desktop (WebRTC) voice option.
    System requirements for Webex Contact Center Desktop · section 'Network and Firewall requirements', first sentence · Checked 2026-10-02
  5. 5
    *.ciscoccservice.com is listed as a critical Webex Contact Center microservices domain that the desktop must reach; Cisco gives its purpose as routing, analytics and AI-powered assistance.
    Webex Contact Center network connectivity requirements · section 'Domain access for desktop', domain table row *.ciscoccservice.com · Checked 2026-10-02
  6. 6
    The Webex Contact Center desktop domain list includes *.cisco.com, *.ciscospark.com, *.wbx2.com and *.webex.com, which are described as Webex Contact Center microservice domains.
    Webex Contact Center network connectivity requirements · section 'Domain access for desktop', domain table rows *.cisco.com, *.ciscospark.com, *.wbx2.com, *.webex.com · Checked 2026-10-02
  7. 7
    The CScan Advanced diagnostic test adds download and upload packet loss and jitter to the Basic test results, and it needs access to the PC speaker and microphone.
    Use CScan to test Webex Calling network quality · section 'Advanced diagnostic test' · Checked 2026-10-02
  8. 8
    The CScan Basic test reports estimated concurrent calls, download and upload bandwidth, latency (RTT), a traceroute, and TCP port reachability toward Webex Calling.
    Use CScan to test Webex Calling network quality · section 'Basic test' · Checked 2026-10-02
  9. 9
    CScan cannot detect whether the network is wired or wireless, DHCP or DNS availability, SRV support, the NTP port, proxies, QoS (ToS/DSCP) marking, or VPN use.
    Use CScan to test Webex Calling network quality · section 'Before you begin', limitations list · Checked 2026-10-02
  10. 10
    The CScan help article does not publish numeric pass thresholds for latency, jitter or packet loss.inferred
    Use CScan to test Webex Calling network quality · whole article; sections 'CScan report information' and 'Interpret test results' · Checked 2026-10-02
  11. 11
    The Webex Calling port reference lists CScan as using TCP to destination ports 8934 and 443 and UDP to a 19569-19760 destination range on Webex Calling subnets.
    Port Reference Information for Webex Calling · table under 'IP Subnets for Webex Calling services', row CScan · Checked 2026-10-02
  12. 12
    After a domain is added to the Webex Contact Center Content Security Policy allowed list, it takes 10 minutes before the Agent Desktop loads within an iFrame.
    Set up security for Webex Contact Center · section 'Set up content security policy', note · Checked 2026-10-02
  13. 13
    Webex Contact Center has a Content Security Policy allowed list, set in Control Hub under Services > Contact Center > Tenant settings > Security, that defines the trusted domains Webex Contact Center applications may access.
    Set up security for Webex Contact Center · section 'Set up content security policy' · Checked 2026-10-02
  14. 14
    For optimal Webex Contact Center Desktop performance, Cisco states a minimum recommended network bandwidth of 512 kbps; desktop data payloads average 1 to 100 kbps and can peak at 2 to 3 MB.
    System requirements for Webex Contact Center Desktop · section 'Bandwidth requirements' · Checked 2026-10-02
  15. 15
    Cisco instructs administrators to add the domains listed under Domain access for desktop to the firewall or VPN allowed list so that the Webex Contact Center Desktop responds as expected on their network.
    Webex Contact Center network connectivity requirements · section 'Domain access for desktop', introductory sentence · Checked 2026-10-02
  16. 16
    All domains in the Webex Contact Center desktop domain list use HTTPS by default and therefore operate over TCP port 443.
    Webex Contact Center network connectivity requirements · section 'Domain access for desktop', note above the domain table · Checked 2026-10-02
  17. 17
    The Webex Contact Center network connectivity article publishes static public IP addresses for Webex Engage and Webex Connect for each data centre, covering AWS Ireland, Oregon, Canada, London, Sydney, Mumbai and Singapore, plus Azure US.
    Webex Contact Center network connectivity requirements · section 'Public IP and domain access', IP address table · Checked 2026-10-02
  18. 18
    For Desktop firewall requirements, the Webex Contact Center System requirements article points to the Webex Calling port reference article, and for network quality it points to CScan.
    System requirements for Webex Contact Center Desktop · section 'Network and Firewall requirements' · Checked 2026-10-02
  19. 19
    Cisco gives separate figures, 512 kbps for desktop data and 100 kbps per WebRTC call, but publishes no combined per-agent bandwidth budget; planners who add them together are making their own assumption.inferred
    System requirements for Webex Contact Center Desktop · section 'Bandwidth requirements' read with the WebRTC 100 kbps statement in cisco-help-2dputx-wxcc-voice-channel-duplicate · Checked 2026-10-02
  20. 20
    Because the WxCC System requirements article sends Desktop firewall questions to the Webex Calling port reference, the WebRTC rows of that reference are the best available Cisco statement of the media ports a WxCC browser softphone needs; no WxCC-specific WebRTC port table was found.inferred
    System requirements for Webex Contact Center Desktop · section 'Network and Firewall requirements' read with cisco-help-b2exve-port-reference WebRTC row · Checked 2026-10-02
  21. 21
    When the Agent Desktop viewing area is narrower than 1280 pixels, the task list appears above the task page and interaction control pane, and below 736 pixels wide the title and logo are hidden.
    System requirements for Webex Contact Center Desktop · section 'Responsiveness' · Checked 2026-10-02
  22. 22
    The older Troubleshoot Webex Contact Center Agent Desktop article (updated 2025-02-24) lists Chrome 76.0.3809 or later, Firefox ESR 68 or later, and Edge Chromium 79 or later as supported browsers.disputed
    Troubleshoot Webex Contact Center Agent Desktop · section 'Browser Requirements' · Checked 2026-10-02
  23. 23
    The older Troubleshoot Webex Contact Center Agent Desktop article states 2 GB of application RAM (excluding the operating system allocation) and lists Windows 10+, macOS 10.12+ and Chrome OS 70 (64-bit)+.disputed
    Troubleshoot Webex Contact Center Agent Desktop · section 'System Requirements' · Checked 2026-10-02
  24. 24
    The minimum supported browsers for Webex Contact Center Desktop are Chrome 144 or later, Microsoft Edge 144 or later, and Firefox 140 or later.
    System requirements for Webex Contact Center Desktop · section 'Minimum system requirements', browser row · Checked 2026-10-02
  25. 25
    The minimum operating systems listed for Webex Contact Center Desktop are Windows 10 or 11, macOS 10.15 or later, ChromeOS, iOS 18 or later, and Linux.
    System requirements for Webex Contact Center Desktop · section 'Minimum system requirements', operating system row · Checked 2026-10-02
  26. 26
    The System requirements article lists 10 Mbps as the minimum network speed for Webex Contact Center Desktop and 10 Mbps or higher as recommended.
    System requirements for Webex Contact Center Desktop · sections 'Minimum system requirements' and 'Recommended system requirements', network row · Checked 2026-10-02
  27. 27
    Cisco publishes per-data-centre source IP addresses that Webex Contact Center uses when calling external services on customer premises, so that customers can allow those calls through their firewalls; the addresses vary by data centre (US, UK, Australia, Germany, Canada, Japan, Singapore, India).
    Set up security for Webex Contact Center · section 'Source IP Addresses for Webex Contact Center' · Checked 2026-10-02
  28. 28
    Webex Contact Center Desktop requires at least 4 GB of RAM, and Cisco recommends 8 GB or more.
    System requirements for Webex Contact Center Desktop · sections 'Minimum system requirements' and 'Recommended system requirements', memory rows · Checked 2026-10-02
  29. 30
    The Webex Contact Center desktop domain list includes region-specific Amazon S3 buckets (cjp-ccone-prod<region>-media-storage-recording) that serve as the regional CDN for media storage and recordings.
    Webex Contact Center network connectivity requirements · section 'Domain access for desktop', domain table rows cjp-ccone-*-media-storage-recording · Checked 2026-10-02
  30. 31
    Region-specific media storage and recording buckets are listed for the US, Australia (ap-southeast-2), Canada (ca-central-1), Singapore (ap-southeast-1), Japan (ap-northeast-1), Europe (eu-west-2 and eu-central-1) and India (ap-south-1).
    Webex Contact Center network connectivity requirements · section 'Domain access for desktop', domain table, S3 rows · Checked 2026-10-02
  31. 32
    For the US region, the listed media storage and recording domains are cjp-ccone-produs1-media-storage-recording.s3.amazonaws.com and cjp-ccone-produs1-media-storage-recording.s3.us-east-1.amazonaws.com.
    Webex Contact Center network connectivity requirements · section 'Domain access for desktop', domain table, US region rows · Checked 2026-10-02
  32. 33
    The Webex Contact Center Agent Desktop display must be larger than 500 x 500 pixels, and Cisco recommends 100 percent browser zoom.
    System requirements for Webex Contact Center Desktop · section 'Screen resolution' · Checked 2026-10-02
  33. 34
    An agent cannot use the Agent Desktop in multiple browsers, or in multiple tabs of the same browser window, at the same time.
    Sign in to Agent Desktop · sign-in prerequisites / general requirements · Checked 2026-10-02
  34. 35
    *.split.io and *.lr-ingest.com are on the Webex Contact Center desktop domain list for performance tracking, error and crash capture, and session telemetry.
    Webex Contact Center network connectivity requirements · section 'Domain access for desktop', domain table rows *.split.io and *.lr-ingest.com · Checked 2026-10-02
  35. 36
    When Webex apps fall back to TLS for media with a proxy configured, the media is routed through the proxy, which Cisco warns can create bandwidth bottlenecks and packet loss.
    Network Requirements for Webex Services · section 'Disadvantages of using TLS as a media transport protocol' · Checked 2026-10-02
  36. 37
    Cisco's agent desktop troubleshooting guidance asks for environment details, including virtual desktop use, work-from-home status and VPN use, when raising Webex Contact Center issues.
    Troubleshoot Webex Contact Center Agent Desktop · section 'Collect Generic Information for all Webex Contact Center Issues' · Checked 2026-10-02
  37. 38
    Webex Contact Center Agent Desktop is supported in a Virtual Desktop Infrastructure (VDI), but the WebRTC (Desktop) voice option is not supported in VDI.
    System requirements for Webex Contact Center Desktop · section 'Virtual Desktop Infrastructure (VDI)' · Checked 2026-10-02
  38. 39
    In third-party VDI systems, some Webex Contact Center Desktop keyboard shortcuts may not work as intended.
    System requirements for Webex Contact Center Desktop · section 'Virtual Desktop Infrastructure (VDI)' · Checked 2026-10-02
  39. 40
    Webex Contact Center agents who handle voice interactions must have a phone, and they enter its dial number or extension in the Station Credentials at sign-in.
    System requirements for Webex Contact Center Desktop · section 'Phone requirements' · Checked 2026-10-02
  40. 41
    For all Webex voice and video media streams, Cisco prefers and strongly recommends UDP as the transport, because TCP retransmission and buffering add latency and jitter.
    Network Requirements for Webex Services · section 'Disadvantages of using TCP as a media transport protocol' · Checked 2026-10-02
  41. 42
    *.webexengage.com is on the Webex Contact Center desktop domain list to support digital channels such as SMS, email, live chat, Facebook Messenger and WhatsApp.
    Webex Contact Center network connectivity requirements · section 'Domain access for desktop', domain table row *.webexengage.com · Checked 2026-10-02
  42. 43
    The Webex Contact Center WebRTC (Desktop) voice option requires a minimum network bandwidth of 100 kbps per call.
    Set up voice channels for Webex Contact Center · WebRTC section, network and browser requirements paragraph · Checked 2026-10-02
  43. 44
    Before deploying WebRTC, Cisco directs administrators to run the Advanced CScan test from the networks where WebRTC will be deployed.
    Set up voice channels for Webex Contact Center · WebRTC section, network and browser requirements paragraph (link to article y27bej) · Checked 2026-10-02
  44. 45
    Background Noise Removal for agents using the WebRTC desktop was announced in the release entry dated June 11, 2026.
    What's new for agents in Webex Contact Center · release entry dated June 11, 2026 · Checked 2026-10-02
  45. 46
    The Webex Contact Center WebRTC (Desktop) voice option is supported on Google Chrome, Microsoft Edge and Mozilla Firefox.
    Set up voice channels for Webex Contact Center · WebRTC section, network and browser requirements paragraph · Checked 2026-10-02
  46. 47
    To offer the Desktop (WebRTC) voice option, an administrator enables the Desktop checkbox on the Voice Channel options of the agent's Desktop Profile (Desktop Experience > Desktop Profiles).
    Set up voice channels for Webex Contact Center · WebRTC section, desktop profile configuration steps · Checked 2026-10-02
  47. 48
    Support for the Desktop (WebRTC) voice option in Edge and Firefox, in addition to Chrome, was announced in the agent release notes entry dated October 30, 2024.
    What's new for agents in Webex Contact Center · release entry dated October 30, 2024 · Checked 2026-10-02
  48. 49
    WebRTC Desktop support is unavailable to Webex Contact Center customers hosted in the Japan data centre.
    Set up voice channels for Webex Contact Center · WebRTC section, regional availability note · Checked 2026-10-02
  49. 50
    Webex Contact Center Agent Desktop does not support headset control actions for WebRTC-based calls.
    Sign in to Agent Desktop · station credentials, Desktop option note · Checked 2026-10-02
  50. 51
    Cisco's WebRTC guidance includes configuring browser and Windows notification and Do Not Disturb settings in Chrome, Edge and Firefox so that agents reliably get notified of incoming calls.
    Set up voice channels for Webex Contact Center · WebRTC section, notification settings subsection · Checked 2026-10-02
  51. 52
    WebRTC support for Supervisor Desktop, which lets supervisors take calls in the browser with a headset, was announced in the release entry dated November 13, 2024.
    What's new for agents in Webex Contact Center · release entry dated November 13, 2024 · Checked 2026-10-02
  52. 53
    The Webex Calling port reference notes that browsers use ephemeral UDP source ports for WebRTC media, which can be constrained with the WebRtcUdpPortRange browser policy delivered through a device management profile.
    Port Reference Information for Webex Calling · table under 'IP Subnets for Webex Calling services', WebRTC call media row, Notes column · Checked 2026-10-02
  53. 54
    In the Webex Contact Center domain list, a leading asterisk (for example *.webex.com) means the top-level domain and all of its subdomains must be reachable.
    Webex Contact Center network connectivity requirements · section 'Domain access for desktop', wildcard note · Checked 2026-10-02
  54. 55
    The Webex Calling port reference recommends an enterprise proxy server option if the firewall does not support domain or URL filtering.
    Port Reference Information for Webex Calling · proxy guidance section · Checked 2026-10-02
  55. 56
    The Webex Calling port reference lists DSCP Expedited Forwarding (46) for Webex App audio and Assured Forwarding 41 (34) for Webex App video.
    Port Reference Information for Webex Calling · section 'Quality of Service (QoS)/Type of Service (ToS)', Webex App rows · Checked 2026-10-02
  56. 57
    In the Webex Calling port reference, the WebRTC call-media row lists UDP from browser-ephemeral source ports to Webex Calling media subnets on destination ports 5004, 9000, 8500-8699 and 19560-65535 (SRTP over UDP).
    Port Reference Information for Webex Calling · table under 'IP Subnets for Webex Calling services', row 'Call media to Webex Calling (STUN, SRTP/SRTCP, T38, DTLS)', source WebRTC · Checked 2026-10-02

Documents

tier 2 current vendor documentation

Network Requirements for Webex Services

Cisco Systems, Inc. (help.webex.com) · 2026-09-09 · accessed 2026-09-16

tier 2 current vendor documentation

Port Reference Information for Webex Calling

Cisco Systems, Inc. (help.webex.com) · 2026-09-08 · accessed 2026-09-16

tier 2 current vendor documentation

Set up security for Webex Contact Center

Cisco Systems, Inc. (Webex Help Center) · 2026-06-11 · accessed 2026-09-05

tier 2 current vendor documentation

Set up voice channels for Webex Contact Center

Cisco Systems, Inc. (Webex Help Center) · 2026-06-25 · accessed 2026-09-04

tier 2 current vendor documentation

Sign in to Agent Desktop

Cisco Systems, Inc. (Webex Help Center) · 2025-11-12 · accessed 2026-09-16

tier 2 current vendor documentation

System requirements for Webex Contact Center Desktop

Cisco Systems, Inc. (help.webex.com) · 2026-09-01 · accessed 2026-09-16

tier 2 current vendor documentation

Troubleshoot Webex Contact Center Agent Desktop

Cisco Systems (Webex Help Center) · 2025-02-24 · accessed 2026-09-30

tier 2 current vendor documentation

Use CScan to test Webex Calling network quality

Cisco Systems (Webex Help Center) · 2025-05-13 · accessed 2026-09-24

tier 2 current vendor documentation

Webex Contact Center network connectivity requirements

Cisco Systems (Webex Help Center) · 2026-01-22 · accessed 2026-09-30

tier 2 current vendor documentation

What's new for agents in Webex Contact Center

Cisco · 2025-10-29 · accessed 2026-09-24

Cite this page

APA

WarmTransfer. (2026, October 2). Webex Contact Center network and browser requirements for agents. WarmTransfer. https://warmtransfer.net/knowledge/wxcc-network-requirements

BibTeX

@misc{warmtransfer-wxcc-network-requirements,
  title  = {Webex Contact Center network and browser requirements for agents},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/wxcc-network-requirements},
  note   = {Verified 2026-10-02}
}