What Causes One Way Audio on Business Calls?

By Nicky Smith, Founder, Carolina Digital Phone · Published September 18, 2026 · Last updated September 18, 2026 · 9 min read

Few phone problems are stranger than one-way audio. The call rings. Someone answers. And then one of you is talking to silence: you can hear them but they cannot hear you, or the reverse. The connection is clearly alive, so how can only half of it work?

The answer is that a phone call is not one connection. It is two different kinds of traffic taking two different roads, and one of those roads can be blocked while the other is wide open. Once you see that, one-way audio stops being a mystery and becomes one of the most diagnosable problems in business telephony. This guide names the usual causes in plain English, gives you a ten-minute isolation method, and tells you exactly what to hand your provider when it is their road that is blocked. It joins our guides on why calls drop and what your network owes call quality as the third leg of the troubleshooting family.

How can a call connect but the sound only go one way?

Because the handshake and the voices are different traffic. When you dial, SIP signaling does the negotiating: it finds the other phone, makes it ring, and agrees on how the call will run. Once both sides accept, the actual audio flows over RTP, and here is the key detail: RTP is two independent streams. Your voice travels to them on one stream. Their voice travels to you on another.

One-way audio means the handshake succeeded and exactly one of those two streams is being blocked or misdirected. That is why the call connects, why the timer runs, and why one person hears everything while the other hears a hallway. Nothing is "half broken." One specific road is closed, and the direction of the silence is your map to which one. If you can hear them but they cannot hear you, your outbound audio stream is not arriving, which usually points at equipment on your side. If they can hear you but you hear nothing, the inbound stream is blocked on its way in, which points at your firewall or router settings.

Is SIP ALG really the usual suspect?

Yes, and it deserves its reputation. SIP ALG, short for Application Layer Gateway, is a feature built into most routers, usually switched on at the factory. Its stated job is to help voice traffic cross your router by rewriting addresses inside the packets. In practice, poor SIP ALG implementations rewrite them wrong, and the audio stream gets sent to an address where nobody is listening. The result is exactly the symptom you are living with: calls that connect and then run silent in one direction, often affecting every phone in the office at once.

The fix is not to tune it. It is to turn it off. Look in the router or firewall settings for SIP ALG, SIP Helper, or SIP Transformations, disable it, and reboot the router. Hosted platforms like ours handle the address bookkeeping properly on their own and do not want the router's help. If your office phones developed one-way audio right after an internet provider swapped your router, this paragraph is very likely your whole answer, because replacement routers arrive with SIP ALG switched back on.

What else on the network blocks audio one way?

When SIP ALG is off and the problem persists, three network suspects remain. First, firewall rules. Call setup and call audio use different ports, so a firewall can happily pass the handshake while blocking the voice streams. If a new firewall was installed or security rules were tightened recently, the audio ports may simply not be on the guest list, and your provider can supply the exact ranges to allow.

Second, double NAT. If two devices on your network are both doing address translation, commonly the internet company's combo box plus your own router behind it, voice traffic gets translated twice and the return path gets lost. The fix is putting the front device into bridge mode so only one device manages addresses.

Third, aging adapters and closet equipment. Analog adapters and legacy PBX gear that predate modern NAT handling are famous for exactly this symptom. If your one-way audio lives on lines running through an old closet system, it may be one more entry on the list of signs a PBX needs replacement.

When is it the device and not the network?

Before touching any router, spend ninety seconds on the humble causes, because they account for more tickets than anyone admits. A muted microphone, on the headset's inline switch, the phone's mute key, or the softphone's own button. A computer that never gave the softphone permission to use the microphone, which both Windows and Mac handle in privacy settings, and which security updates sometimes reset. A Bluetooth headset that connected for listening but not for the microphone, or that a laptop grabbed while the earpiece stayed on the phone. And on mobile apps like Digital Voice Plus, a microphone permission that was declined once during setup and never revisited.

The tell for device problems: they follow one person. If a single employee has one-way audio everywhere, on every call, while the rest of the office is fine, the network is innocent and the answer is on that desk.

Why do remote workers hit this more often?

Because a remote worker's calls cross equipment nobody at the company manages: a home router with SIP ALG on by default, an apartment complex's shared internet doing its own translation, and often a corporate VPN in the middle. VPNs are a special repeat offender, since routing voice through a VPN tunnel can deliver the handshake while the audio streams take a path that dead-ends. If a remote employee has one-way audio only when the VPN is on, the fix is asking IT to route voice traffic outside the tunnel, called split tunneling.

Home internet quality plays a part too, and the FCC's household broadband guide is a useful plain-language reference for what a shared home connection can carry. For the remote worker's checklist itself, our network readiness guide covers the home-office section.

How do you isolate it in ten minutes?

Four questions, in order, and each answer cuts the suspect list in half.

• Who has it? One person means a device problem on that desk. Everyone means the network, almost always SIP ALG, the firewall, or double NAT.
• Which direction is silent? You hear them but they cannot hear you points at your outbound audio. They hear you but you hear silence points at inbound blocking on your router or firewall.
• Does it happen off your network? Put the mobile app on cellular data with Wi-Fi off and make the same call. If the problem vanishes, your office or home network owns it. If it persists, the platform side needs a look.
• When did it start? One-way audio that appears the week a router was replaced, a firewall was upgraded, or a VPN was rolled out is not a coincidence. The newest change is the prime suspect.

Write down the answers plus three specifics, the time of a failed call, the extension, and the number dialed. Those five facts turn your support call from a description into a diagnosis.

What belongs to your provider?

The platform side of the call: the servers that relay audio, the carrier routes it rides, and the media handling that modern hosted systems use precisely so customers do not have to manage port forwarding by hand. A provider that operates its own platform can pull the actual call, see whether your audio arrived and whether theirs was sent, and tell you in minutes which side of the line the blockage sits on. The FCC's VoIP overview sketches the layers involved; the practical point is that you should never be left arguing with silence. If your current provider cannot look at a specific call and give you a specific answer, that itself is a finding, and our guide to what happens when your business phone breaks covers what good support looks like under pressure.

Why do Piedmont businesses call Carolina Digital Phone?

Because one-way audio is a solved problem when someone owns the whole picture. We configure the router side correctly at installation, SIP ALG off, firewall ranges set, before the first call is made, and we operate our own geo-redundant platform, so when a call misbehaves an engineer in Greensboro pulls that call and reads it with you. No national queue, no scripted denial. That accountability is why organizations choose us, and it has held through our 25-plus years as a trusted communications partner for businesses, K-12 schools, and government agencies across the Carolinas and Virginia. The full story is at Carolina Digital Phone.

Frequently asked questions