What is Webex?

Webex is a meetings and calling app. On a Mac, signalling and media use different connections. Cisco documents both for network administrators.

Fix this with your agentCopies a prompt for Claude Code, Codex or any agent that can use Terminal.

I want to know what Webex is doing on my Mac and whether its network use is normal. Read https://kilobat.app/processes/webex.md and work through it with me. Install the Kilobat CLI if it’s missing: brew install seifip/kilobat/kilobat. Run the guide’s Terminal and kilobat checks yourself and tell me what you find. List the steps only I can do. Ask before you change any setting.

Process: WebexAlso seen as: Webex App, Cisco WebexMade by CiscoApplies to: The Webex app on macOS 12 and later. Checked on 8 November 2026 against Cisco's network requirements article for Webex services.Checked: 8 November 2026

Short answer

The Webex desktop app. Cisco documents HTTPS signalling on port 443 and SRTP media over UDP on ports 5004 and 9000, with TCP and TLS as fallbacks.

Block with care

Blocking UDP makes media fall back to TCP or TLS. Blocking port 443 to Webex's domains stops sign-in and meetings.

Path
/Applications/Webex.app

What it is

Cisco's article on network requirements is for network administrators. It says that the Webex app uses HTTPS and secure WebSockets over TLS for signalling to the Webex cloud.

Cisco says that signalling connections are outbound only and use TLS 1.2 or 1.3. They go to port 443.

Media travels on separate connections. Cisco says that the app and Cisco Video devices use SRTP over UDP on ports 5004 and 9000 for audio, video and content sharing.

Cisco says that the app also looks up names over port 53 and may use NTP on UDP port 123. Cisco notes that you do not need NTP if you run your own.

Cisco says that signalling cannot be filtered by IP address, because Webex addresses change. It tells administrators to filter signalling by domain at a proxy.

Cisco lists these domains for core services, *.webex.com, *.wbx2.com, *.ciscospark.com, *.webexapis.com and *.cisco.com. Content storage uses *.webexcontent.com."

Cisco's installation article says that the app is installed in the Applications folder by default, as a DMG or PKG. It says that the app checks for new versions and upgrades itself.

Why it uses the network

  • Signalling and messaging. Cisco says that signalling uses HTTPS and secure WebSockets to the Webex cloud on port 443.
  • Audio, video and content. Cisco says that media uses SRTP over UDP on ports 5004 and 9000. UDP is its preferred transport.
  • Reachability tests. Cisco says that the app tests media nodes over UDP, TCP and TLS at start-up, on a network change and from time to time. It sends the results to the Webex cloud before a call.
  • Fallback media. Cisco says that the app falls back to SRTP over TCP on port 5004 when UDP is blocked. It falls back to SRTP over TLS on port 443 when TCP is blocked.

How much is normal

Cisco does not publish figures for idle traffic in this article. You should expect small traffic for signalling when you are not in a meeting.

The reachability tests run on their own. Cisco says that they run at start-up, after a network change and periodically.

In a meeting, media flows in both directions on the chosen transport. Cisco says that the Webex cloud picks the best media server from the test results.

When it uses a lot, and why

  • Video meetings. Audio, video and shared content use the media connections for as long as the meeting lasts.
  • Media over TLS. Cisco says that media over TLS can lose quality and strongly recommends against it in production. A proxy can add a bottleneck.
  • Content storage and files. Cisco lists *.webexcontent.com for content storage. Sharing and opening files uses it.

Is it safe to block?

Block with care

Blocking UDP makes media fall back to TCP or TLS. Blocking port 443 to Webex's domains stops sign-in and meetings.

What breaks if you block it

  • Signalling fails when port 443 to the Webex domains is blocked, so you cannot sign in or join.
  • Media quality can drop when UDP is blocked and the app falls back to TCP or TLS.
  • Calls fail when UDP, TCP and TLS media paths are all blocked.

Blocking means a firewall rule that refuses its connections. Don’t quit or disable a macOS process to save data: macOS starts it again, and other features depend on it.

Reduce its use

  1. Leave meetings when they end. Media then stops.

  2. On a company network, ask the administrator to allow UDP ports 5004 and 9000 to Webex. Cisco prefers UDP for media.

  3. Keep the app current. Cisco says that it upgrades itself periodically.

See how much it uses

  1. Open Activity Monitor and search for Webex. Open the Network tab to see the bytes that the app and its helpers moved.

With Kilobat

  1. In the Kilobat app list, search for Webex.

  2. Ask the same question in Terminal.

    kilobat explain Webex

The live view and the explanations are free. History in the app needs Kilobat Pro. Blocking needs Pro and the network filter: see the network filter, Protection and the hotspot data saver.

What isn’t documented

Cisco's article does not list the process names or the bundle ID of the Mac app. It does not say how much data an idle app uses.

The article lists about 40 IPv4 media subnets and three IPv6 ranges. The list changes, so it is not repeated here. Use Cisco's current article.

Cisco says that its Edge Audio, Expressway and hybrid services use other ports. This page covers the app only.

Questions

Which ports does Webex use?

Cisco documents TCP port 443 for signalling and SRTP over UDP on ports 5004 and 9000 for media. Fallbacks use TCP port 5004 and TLS port 443.

Can I allow Webex by IP address?

Cisco says that signalling cannot be filtered by IP address. It lists IP subnets for media only. Filter signalling by domain at a proxy.

Sources

Checked on 8 November 2026.