No Installation Charge - First Month Free
VoIP One-Way Audio: A Troubleshooting Guide for Tampa Bay Businesses
Can hear the caller but they can't hear you (or the reverse)? Here's a structured way to find the cause of one-way audio on VoIP calls and fix it.
Drew Martin
9/19/20267 min read
Introduction
A call connects, rings, and gets answered — and then something's off. You're talking, but there's nothing coming back. Or you can hear the other person perfectly while they keep asking "hello? are you there?" It's an unsettling problem precisely because the call looks like it's working: the timer is running, the line is open, and yet only half the conversation is getting through.
This isn't a rare glitch. It's one of the more common VoIP support calls, and it also happens to be one of the easier problems to actually solve — once you understand what's really happening on the network when you place a call. This guide walks through a practical way to narrow down the cause, starting with the fastest checks and working toward the network-level fixes.
The Root Cause: A Phone Call Is Two Separate Conversations
It helps to know that a VoIP call isn't a single stream of data. Setting up the call and carrying the actual audio are handled by two different systems working together.
One system (called SIP, or Session Initiation Protocol) handles the "handshake" — dialing, ringing, and getting both parties connected. The other system (called RTP, or Real-time Transport Protocol) carries the actual sound of your voice, and it does so as two completely separate one-directional streams: one carrying your audio out, and one carrying the other person's audio in.
Because these are separate systems, it's entirely possible for the handshake to succeed — the call connects, the timer starts — while only one of the two audio streams actually gets through. That's the whole story behind one-way audio: nothing is "half-broken." One specific path for one specific direction of sound is being blocked, while everything else about the call works normally.
Knowing this changes how you troubleshoot. Instead of treating it as a vague "bad call quality" issue, you can treat it as a routing problem with a specific direction — and the direction you're missing tells you a lot about where to look first.
Start Here: Does It Follow the Person or the Place?
Before digging into routers and firewalls, answer one question: is this happening to one specific employee everywhere they call from, or is it happening to anyone using a particular phone, location, or network?
If it follows one person — say, it happens on every call they make, regardless of who they're calling — the cause is almost always sitting on their desk, not buried in the network. Check these first, because they take seconds to rule out:
Is the microphone physically muted? Check the headset's inline mute switch, the desk phone's mute button, and the softphone app's own mute control — it's common for more than one of these to exist on the same setup, and easy to trip one without realizing it.
Does the computer or phone actually have microphone permission granted to the calling app? Both Windows and macOS gate microphone access per-application, and an OS update can silently reset that permission.
Is a Bluetooth headset actually carrying both directions of audio? Bluetooth devices sometimes pair for listening only, leaving the microphone on a different device (or the laptop's built-in mic) than the person expects.
If it follows a place — multiple people on the same office network or same remote location all report it — the cause is environmental: something in the network path is blocking audio in one direction for everyone who uses it. That's a different investigation, covered below.
When It's Everyone: The Network Usually Has One of Three Problems
A router feature quietly rewriting your calls
The single most common network cause is a router setting called SIP ALG (Application Layer Gateway). It ships turned on by default on a large share of consumer and small-business routers, and its job is supposed to be helping VoIP traffic pass through the router more smoothly. In practice, it frequently does the opposite: it rewrites addressing information inside the call's setup data without properly opening a matching path for the audio itself, so one of the two RTP streams ends up addressed to nowhere.
The practical fix isn't to adjust it — it's to turn it off entirely. It's usually listed in router or firewall settings as "SIP ALG," "SIP Helper," or "SIP Transformations." Disable it and restart the router. A modern hosted VoIP platform manages this addressing on its own and doesn't benefit from the router trying to help. If this problem started right after your internet provider replaced a router or gateway, this is the first thing to check — replacement hardware very often ships with this setting back on, even if it was disabled on the old unit.
A firewall rule that let the handshake through but not the audio
Because call setup and call audio travel on different network ports, it's possible for a firewall to correctly allow the setup traffic while blocking the audio. This is especially common right after a firewall is replaced, upgraded, or has its rules tightened for security reasons — the specific port range VoIP audio needs may simply not have been carried over. Your VoIP provider can give you the exact ports to open; this isn't something you need to guess at.
Two routers both trying to manage the same traffic
If your internet connection runs through a combined modem/router from your ISP, and you've added your own router behind it, both devices may be performing network address translation independently — a setup known as double NAT. When that happens, voice traffic can get translated twice, and the return path for audio can get lost in the process. The fix is usually to put the ISP-provided device into "bridge mode" so it stops managing addresses, leaving that job to a single router.
Older on-site equipment
If the affected lines run through an analog telephone adapter or legacy on-premises phone equipment rather than modern VoIP hardware, one-way audio can simply be a symptom of equipment that predates how today's networks handle address translation. If that's the case, it's often one signal among several that it's time to look at replacing the equipment — see our guide on what's required for a clear VoIP setup for what a modern setup looks like.
Remote Workers Run Into This More Often — Here's Why
A remote employee's call travels through equipment your business doesn't control: their home router (very possibly running that same default SIP ALG setting), sometimes a shared connection in an apartment building, and often a company VPN layered on top. VPNs deserve special attention here, because routing voice traffic through a VPN tunnel can let the call's setup information through while the audio streams take a different path that never arrives.
If a remote employee only experiences one-way audio while connected to the VPN, ask your IT team about split tunneling — a configuration that routes voice traffic outside the VPN tunnel while keeping other traffic secured through it. For a broader look at what a home setup needs to support reliable calls, see our guides on how VoIP helps remote workers and testing your internet connection.
A Fast Way to Narrow It Down Before You Call Support
Before reaching out to your provider, gather three things: which direction the audio is missing, whether it's affecting one person or everyone, and whether anything on the network changed recently (a new router, a firewall update, a new VPN policy). If you have a moment, also try placing the same call from a mobile softphone app on cellular data, with Wi-Fi turned off — if the problem disappears, that confirms the office or home network is the cause rather than the VoIP platform itself.
Handing your provider a specific description — "outbound audio only, started this week, coincides with a new firewall" — turns a vague complaint into something they can actually act on quickly.
What Your Provider Should Be Able to Tell You
A VoIP provider that runs its own platform should be able to pull the record of a specific call and tell you directly whether your audio left your network and whether the other side's audio was sent back — which immediately narrows the problem to your side or theirs. You shouldn't be left guessing. If your provider can't look at a specific failed call and give you a concrete answer about where it broke down, that's worth factoring into how you think about your service.
Frequently Asked Questions
Why does the call connect normally if the audio isn't working? Because connecting a call and carrying its audio are handled separately. The setup only needs a brief handshake to succeed for the call to connect and the timer to run; the audio then flows as two independent one-directional streams, and only one of those streams needs to fail to produce one-way audio.
What's the most common fix for one-way audio? Disabling SIP ALG on the router. It's on by default on many routers and is the single most frequent cause of this specific symptom, especially when it affects every phone on a network at once.
How can I tell if it's a device problem instead of a network problem? If it follows a specific person across every call they make while everyone else is fine, it's a device issue — check mute settings, microphone permissions, and Bluetooth pairing first. If it affects multiple people on the same network, or started right after an equipment change, it's a network issue.
Why does this happen more to remote employees? Their calls pass through network equipment the business doesn't manage — typically a home router and often a VPN — either of which can mishandle the audio streams even when the call setup goes through fine.
Is one-way audio a sign my phone system is failing? No — it's a network routing symptom, not a hardware failure. That said, if it's recurring, it's worth diagnosing properly rather than working around it, since the same misconfiguration can also contribute to other call quality problems.
Conclusion
One-way audio looks like a mysterious half-failure, but it almost always comes down to one specific, findable cause: a router feature rewriting your calls, a firewall blocking one type of traffic while allowing another, two devices fighting over network addressing, or something as simple as a muted headset. Working through whether the problem follows a person or a place is the fastest way to point yourself in the right direction, and a provider that can actually look at the call itself should be able to confirm the rest.
If your Tampa Bay business is dealing with one-way audio or other call quality issues, Turnkey VoIP can help pinpoint whether it's your network or the platform side — call us at (813) 852-2222 to talk through what you're experiencing.
Sources
Note: Router and firewall interfaces vary by manufacturer, so exact steps to disable SIP ALG or open firewall ports will differ by device. Consult your specific router's documentation or your VoIP provider for exact settings.
Internal link note: the linked guides above point to companion pieces already produced for this project. Swap in your live site's actual URL structure before publishing if it differs.