Webex Worked Until I Turned On the VPN—Here’s What Fixed the Meeting

The Webex window opened normally. I could see the client’s name in the participant list, the microphone button responded, and the meeting timer began counting. But the audio panel stayed on “Connecting,” while the video froze on its first frame. I blamed the hotel Wi-Fi, restarted the app, and joined again. Nothing changed.

I had eleven minutes before I was supposed to present a contract revision. The obvious clue was sitting in the menu bar: my VPN was connected.

Normally, that would have reassured me. I was working on a network shared with an entire hotel floor, and disconnecting the VPN just to make a call felt like solving one problem by creating another.

Still, I tried it.

I disconnected the VPN, rejoined Webex, and heard the entry tone immediately.

The microphone connected. The camera stopped freezing. The meeting worked.

That narrowed the problem quickly. Webex was not down, my account was fine, and the hotel Wi-Fi was capable of carrying the call. The failure appeared only when the meeting traffic passed through that particular VPN route.

A Meeting Can Join Without Really Connecting

Webex uses separate paths for meeting controls and live media. That is why a meeting can show your name, accept button clicks, and appear connected while the audio remains silent.

Cisco’s network guidance says Webex prefers UDP for meeting media, with TCP and TLS available as fallbacks. When the preferred path is unavailable or the fallback route becomes congested, the meeting may technically connect while audio and video struggle.

The practical meaning was simpler than the documentation: the VPN tunnel was open, but the route inside it was not handling the call well.

Cisco has also documented cases in which users connected through remote-access VPNs experienced missing or one-way Webex audio. Public discussions among system administrators describe the same diagnostic pattern: Webex works with the VPN disconnected, then…

Those reports mattered because they pointed away from the microphone and toward the network path. I had already spent several minutes restarting the wrong thing.

First, Check Whether It Is Your VPN to Change

Before testing another service, there is one important distinction.

A company-managed VPN is not the same as a personal VPN you installed for travel. If your employer requires the tunnel for access to internal systems, replacing it with a consumer app may violate policy and may not give you access to the resources you need anyway.

Cisco documents split tunneling as one way administrators can let Webex media take a more direct route while other work traffic remains inside the corporate tunnel. That is a decision for the IT team.

The useful report to send them is specific:

Webex works when the company VPN is disconnected. With the VPN active, the meeting opens, but audio or video does not connect reliably.

That gives an administrator something more useful than “Webex is broken.” They can investigate the media route, firewall rules, proxy handling, packet loss, or tunnel configuration.

My situation was different. The VPN was personal. I was using it because I was traveling and handling client material on shared Wi-Fi. I could change the app without losing access to a company network.

So the question became narrower: could I keep the protection of a VPN without sacrificing the meeting?

The Established Provider Was the Reasonable First Choice

I had started with a major VPN provider for ordinary reasons. It had a long public history, a large server network, and an interface I already understood.

I chose the nearest city and ran a speed test. The download result looked comfortably high enough for a video call.

Webex still failed.

I switched protocols. One attempt joined without sound. Another produced a few seconds of audio before freezing. I changed servers, first nearby and then farther away. The farther route only added delay.

At that point, the speed-test result stopped looking useful.

A VPN can download a large file quickly and still perform poorly during a live meeting. Webex does not need one short burst of impressive bandwidth. It needs a route that keeps small, time-sensitive packets moving without repeatedly stalling.

The large provider offered more countries, more servers, and more settings. None of those advantages told me which choice would make the meeting work in the next few minutes.

I considered leaving the VPN off. That was the fastest workaround, and it had already succeeded once. But I would still be discussing a client contract over hotel Wi-Fi without the protection I had chosen to use.

I wanted both requirements met, not one abandoned.

The Smaller App Asked a More Useful Question

I opened OnlydogVPN because its interface approached the decision differently. Instead of asking me to choose among a long list of countries and server locations, it offered presets based on what I was trying to do.

I chose the option intended for calls and unstable networks.

Then I returned to Webex.

The entry tone played.

The audio panel moved past “Connecting.” The microphone meter reacted to my voice. I switched on the camera, shared the contract, and moved through the pages without the call falling back into silence.

The client did not need to know what had changed. From their side, I had simply joined a few minutes late and started the presentation.

That was the first result that mattered.

Only after the meeting was running did the technical difference become relevant. The smaller app uses an HTTP/3-based transport with additional traffic obfuscation. In practical terms, it gave the VPN traffic a different way to cross the same network instead of repeating the route that had already failed.

I could not observe the hotel’s internal filtering or traffic-management rules, so I cannot say exactly which part of the network objected to the earlier connections. What I could observe was the sequence: the direct connection worked, the established VPN repeatedly disrupted Webex, and the second service carried the meeting while remaining connected.

The interface also saved time. I did not need to guess which country, city, or protocol combination might suit a live call. The decision was framed around the task rather than the map.

Under normal conditions, that might feel like a minor convenience. With someone waiting in a meeting room, fewer decisions became part of the solution.

The Second Test Happened Without Warning

Halfway through the presentation, the hotel Wi-Fi dropped.

My laptop moved to the phone hotspot. I expected Webex to freeze while the VPN rebuilt its connection. There was a short interruption, but the call recovered and continued without forcing me to leave and rejoin.

That mattered almost as much as the initial connection.

Travel networks rarely fail cleanly. Hotel Wi-Fi weakens, captive portals reappear, and laptops jump to mobile data. A VPN that works only while the underlying connection remains perfectly stable is less useful in the exact situations where travelers need it most.

The service’s recovery behavior solved a smaller problem that appeared only after the main one was fixed. I no longer needed to choose between keeping the VPN on and keeping the meeting alive whenever the network changed.

The Limitation Is Easier to Accept When the Job Is Clear

The smaller service does not have the same public history as the major provider. It offers fewer server locations and has fewer independent reviews.

Those are real disadvantages. They would matter more if my goal were to compare the broadest global coverage or choose the company with the longest public record.

But those were not the decisions in front of me.

I needed to join one Webex meeting from an unreliable network while keeping a VPN active. The established provider was stronger on the usual comparison points, yet it failed the task repeatedly. The smaller app offered fewer choices, but its route worked and recovered when the network changed.

That changed what I thought I was comparing.

What to Do When Webex Stops Working With a VPN

The fastest diagnostic step is still the simplest: when policy permits, test the same meeting once with the VPN connected and once without it.

If Webex fails only on a company-managed VPN, document the difference and send it to IT. Ask whether Webex media can use an approved split-tunnel configuration. Do not install another VPN to bypass company controls.

If the VPN is personal, stop judging the problem only by download speed or the number of servers shown in the app. Test whether the service can complete the actual task:

Does the audio connect?

Does the camera remain stable?

Can screen sharing continue?

Does the tunnel recover when the network changes?

The established provider remained the better-known service. Disconnecting remained the fastest emergency workaround. But only the smaller app preserved both things I needed at the same time: the VPN stayed on, and the client meeting happened.

For a Webex call that was already late, a usable route mattered more than a larger server list.