How to Fix One-Way Audio Issue on VoIP Calls? A Technical Guide

You’re on an important client call with your virtual phone system. Everything seems fine. You can hear them perfectly. But when you start talking, you’re met with silence. “Hello? Can you hear me?” Nothing. They can’t hear a word you’re saying.

You’ve just run into the classic one-way audio issue, one of the most frustrating and common VoIP issues in the world of VoIP technology. It’s a common headache for businesses using a modern business phone system. The good news? It’s almost always fixable. You don’t need to be a network engineer to troubleshoot one-way audio.

To help you fix this audio issue permanently, we have come up with this step-by-step technical guide that will allow you to find and fix the problem. First, we will take you through the quick fixes before getting into the deeper solutions, in case there are those that you have to live to see another day.

Let’s get your calls back to crystal-clear, two-way conversations.

What is One-Way Audio? A Simple Explanation

One-way audio is exactly what it sounds like. During a conversation, sound travels successfully in one direction but fails in the other. One person can speak and be heard. The other person’s voice never reaches its destination.

This is different from having no audio at all. If you have no audio, the connection likely failed completely. The one-way audio issue is more subtle. It means the call is established, but the RTP packets (the tiny bits of data that carry your voice) are getting lost on their return journey.

This problem often points to a specific type of network or call routing misconfiguration.

Understanding the One-Way Audio Issue on VoIP Calls

To make VoIP calls, there are two components involved. The first one is SIP (Session Initiation Protocol), which initiates and terminates the call as well. Just consider the SIP to be the dial tone and the greeting of hello that establishes the communication. The second is RTP (Real-time Transport Protocol), which carries the actual audio. RTP is the conversation itself.

In a typical call flow, a one-way audio issue almost always means SIP did its job, but the RTP stream is blocked or misdirected in one direction. Your voice leaves your phone but never arrives at the other end.

Any device can have this problem. You may encounter it either on your desk IP phone, a desktop application on your computer, or even the mobile application on your smartphone. The good news? Most cases can be fixed quickly.

Quick Checklist: 5 Common Fixes for One-Way Audio Issues

Before we dive deep, try these quick fixes. These five steps solve a surprising number of VoIP audio issues without needing to log into any complex settings.

1. Power Cycle Your Network: This is the classic “turn it off and on again” for a reason. Unplug your modem, router, and VoIP device. Wait a full 60 seconds. Plug the modem back in first. Wait for it to fully connect. Then plug in the router. Finally, plug in your VoIP phone or restart your computer.
2. Check Your Headset & Mute Button: It sounds silly, but you’d be surprised. Make sure your headset is plugged in correctly. Check for a physical mute button on the cord or headset itself. Also, check the software mute button in your desktop app.
3. Disable SIP ALG on Your Router: This is a huge one. SIP ALG (Application Layer Gateway) is a router feature that’s supposed to help VoIP traffic, but it often causes more harm than good. We’ll show you how to turn it off later.
4. Check Your Firewall: The Firewall on your computer or router may be too restrictive and prevent voice traffic from your VoIP provider. Ensure that the firewall settings have been checked and that the rules can permit voice data to flow.
5. Use a VoIP Quality Test: A quick online test can check the network for packet loss, jitter, and NAT issues. This can point you directly to the source of the one-way audio issue.

If these steps didn’t work, don’t worry. We just need to dig a little deeper.

What Causes One-Way Audio in VoIP?

To truly fix a problem, we need to understand what causes it. In the world of VoIP, audio issues are often traced back to how your private network talks to the public internet. Here are the technical culprits behind your routing issues.

1. Network Address Translation (NAT)

Network Address Translation (NAT) is a way that routers use to map one or more private IP addresses inside a local network to only one public IP address to communicate with the Internet. It includes changing the IP header of packets so that traffic being sent out looks as if it is coming from the router. This methodology saves the user from public IP addresses and provides an additional security layer.

Cause

The issue arises because VoIP signaling (like SIP) embeds the phone’s private IP address within its data payload, which basic NAT does not inspect. The remote party then tries to send the return audio stream (RTP) to this unrouteable private address, causing the packets to be lost.

Scenario Example
An employee on a private network (192.168.1.50) makes an outbound call to a client. The client can hear the employee perfectly. However, the client’s system attempts to send its audio back to the 192.168.1.50 address, which is invalid on the public internet, so the employee hears only silence.

2. SIP ALG

SIP Application Layer Gateway (ALG) is a router feature designed to inspect and intelligently modify VoIP traffic. Its purpose is to help SIP packets traverse NAT correctly by rewriting IP addresses and port information within the packet data. This process is intended to prevent communication issues like one-way audio.

Cause

The issue is that most SIP ALG implementations are flawed and outdated. Instead of helping, they often misinterpret or corrupt the SIP packets by rewriting them incorrectly, which breaks the communication path for the return audio stream.

Scenario Example

During a call setup, the SIP ALG inspects the SIP packet and attempts to “fix” the contact information. However, due to its buggy nature, it inserts the wrong public IP address or an incorrect port. The remote party then sends audio to this invalid destination, resulting in the caller hearing nothing.

3. Other Potential Causes

While NAT and SIP ALG are the main villains, a few other things can cause similar symptoms:

• Overly Strict Firewalls: Both your router’s firewall and software firewalls (such as Windows Defender) can block the UDP ports required for RTP traffic.
• Double NAT: This occurs when two routers are connected (e.g., your ISP’s modem/router combo is connected to your own Wi-Fi router). Both devices are attempting to act as the “receptionist,” which confuses call routing and loses packets.
• Codec Mismatches: A codec is a technology used to compress and decompress your voice. Think of it as a digital language. If your phone is speaking one language (such as G.711) and your provider’s system is expecting another (such as G.729), the audio can’t be appropriately decoded.
• Packet Loss and Bandwidth Issues: If your internet connection is unstable, some voice packets might get dropped along the way. While this usually causes choppy audio, severe packet loss can result in one-way audio.

Now that we know the suspects, let’s start the investigation.

The Troubleshooting Flow: A Step-by-Step Guide

Follow this process from Level 1 to Level 3. Don’t skip steps. The solution is often found in the earliest stages.

Level 1: The Basic Checks

This is your first line of defense. These steps rule out simple hardware or local device problems.

Step 1 – Rule Out the Simple Stuff

Before you touch your network, check your immediate equipment.

• Check Mute Buttons: Look for a physical mute switch on your headset. Then, check the mute button in your softphone application, such as Zoom Workplace or the Ooma Office desktop app. It’s easy to click by mistake during live audio calls.
• Test Your Microphone: Is Your Mic Even Working? On Windows, open the “Sound Recorder” app. On a Mac, open “QuickTime Player” and select “New Audio Recording.” Speak into your mic. If you see the audio levels move or can play back a call recording, your mic is fine.

This simple check can save you a lot of time.

Step 2 – Power Cycle Everything

We mentioned this in the quick checklist, but it’s worth repeating with more detail. A proper power cycle clears out temporary data in your router, including the NAT table that might be causing the problem.

Follow this exact order:

1. Unplug the power from your Modem.
2. Unplug the power from your Router.
3. Unplug the power from your VoIP Desk Phone (if you use one).
4. Wait a full 60 seconds. This is crucial for the internal components to reset fully.
5. Plug the Modem back in. Wait for all the lights to become solid (usually 1-2 minutes).
6. Plug the Router back in. Wait for its lights to stabilize.
7. Finally, plug your VoIP device back in or restart your computer.

This process ensures that each device receives a fresh IP address and connection, distinct from the one before it.

Step 3 – Isolate the Problem

Now, we play detective to determine if the problem lies with the device, the network, or the provider.

• Test on the same Network with a Different Device: Of course, should you have a one-way audio problem with your IP phone, you can also try to make a call using a softphone application on your computer that is connected to the same Wi-Fi. Assuming the app is working, then the issue must be with the hardware or setup of the desk phone.
• Try the Same Device on a Different Network: This is the ultimate test. Take your laptop or mobile device to a different location (like a coffee shop) or connect it to your phone’s mobile hotspot. Make a test call. If the audio works perfectly on the hotspot, you have 100% confirmed the problem is with your primary network (your router or modem).

This step tells you exactly where to focus your efforts to troubleshoot one way.

Level 2: Router Configuration Fixes

If the Level 1 checks don’t work and you suspect your network is the culprit, it’s time to log in to your router. Don’t be intimidated. We’ll guide you through it.

How to Fix One-Way Audio Issue in VoIP: Disable SIP ALG

This is the most effective single solution to this problem.

Step 1- Find Your Router’s IP Address

A. On iPhone/iPad or Android:

• Go to your phone’s Wi-Fi Settings.
• Tap on the network you are connected to (on iPhone, tap the “i” icon; on Android, tap the gear icon ⚙️ or press and hold).
• Look for the address listed under “Router” or “Gateway.” It will look like 192.168.1.1.

B. On Windows/macOS:

• Windows: Open Command Prompt, type ipconfig, and find the “Default Gateway” address.
• macOS: Go to System Preferences > Network > Advanced > TCP/IP and find the “Router” address.

Step 2- Log Into Your Router

• Using the web browser on your phone or computer, type the router’s IP address from Step 1 into the address bar and press Enter.
• You will be asked for a username and a password. These are often printed on a sticker on the router itself. (Common defaults are admin/password or admin/admin).

Step 3- Find and Disable SIP ALG

This setting is usually buried in an “Advanced,” “Security,” or “Firewall” menu. The navigation might be a bit tricky on a small phone screen, so zoom in if you need to.

1. Look for an option called SIP ALG, SIP Passthrough, or SIP Transformation.
2. Disable this feature.
3. Save your settings and reboot the router.

Port Forwarding (If Disabling SIP ALG Doesn’t Work)

If SIP ALG was already disabled or turning it off didn’t help, the next step is port forwarding. This tells your router to always send specific types of data (like voice traffic) directly to your VoIP device.

You will need to create rules to forward the RTP ports used by your VoIP provider to the private IP address of your VoIP device. You can find this IP address in your device’s settings.

Here are the standard ports used for VoIP:

Your provider may use a different range, so always check their documentation. In your router’s “Port Forwarding” or “Virtual Phone Servers” section, create a rule for each required port or range, pointing it to your device’s IP.

Check Firewall Rules

Finally, check your firewalls. A firewall can block the outbound RTP traffic that carries your voice.

• Router Firewall: Look for settings related to “outbound traffic” or “UDP filtering.” Ensure it’s not set to a high-security level that blocks these ports.
• Software Firewall (on your PC): Check Windows Defender Firewall or your macOS firewall settings. Make sure your softphone application (e.g., your cloud PBX’s desktop app) is listed as an allowed application. If not, add an exception for it.

These Level 2 fixes resolve the vast majority of network-related one-way audio problems.

Level 3: Advanced Network Troubleshooting

If you’re still stuck, the issue is likely more complex. Here are a few advanced scenarios.

Double NAT (Two Routers Detected)

This is a common issue in home offices where an ISP-provided modem/router is connected to a secondary personal router (like a Google Nest or Eero).

Symptom: You log in to your personal router and view its WAN or Internet IP address. If that address is a private IP (like 192.168.x.x or 10.0.x.x), you have Double NAT.)

Solution: The best fix is to put the ISP-provided device into “bridge mode” or “IP passthrough mode.” This disables its router functions, allowing your personal router to manage the network directly. You may need to call your ISP to have them enable this for you.

Codec Mismatches

This is less common with modern VoIP providers, but it can still happen. As we said, codecs are digital audio formats. Common codecs include G.711 (high-quality, high-bandwidth) and G.729 (compressed, low-bandwidth).

Symptom: The call connects, but the audio is garbled or nonexistent in one direction.

Solution: Log in to your VoIP phone’s web interface or your softphone’s settings. Look for a “Codecs” or “Audio” section. Ensure the list of preferred codecs matches the recommendations of your VoIP provider. Usually, setting G.711u (for North America) or G.722 as the top priority is a safe bet to fix an incompatible codec issue.

Quality of Service (QoS)

QoS cannot fix one-way audio directly, but it can prevent it by guaranteeing that voice packets never drop due to network congestion. QoS tells your router to set voice traffic above anything else (like video streaming, or this large download).

How it Works: You can set a rule in the QoS setting of your router that would allow the traffic of your IP address, or the specific UDP ports that may handle RTP, to be the first in line.

This is a great preventative measure to improve overall call quality and reliability.

When All Else Fails: Get Professional Help

You have done all you can. You have rebooted, turned off SIP ALG, ensured that you get no port blocking in your firewalls, and you are still stuck with the same issue of one-sided audio. The professionals should be brought in. This problem is dealt with by your VoIP provider’s support personnel or your IT department in your company each day.

To make the call as productive as possible, have this information ready:

• The type of router you have.
• A record of the troubleshooting steps that you have already undertaken.
• What your tests reflect (e.g., the mobile app runs on a 4G hotspot and not on the Wi-Fi at my office).
• Some recent call history (date, time the call was made, number called, and your number called).

This information will help them diagnose the problem much faster.

Conclusion

Dealing with a one-way audio issue can be a disruptive puzzle, but there is a solution. Almost always, the culprit is the communication between your internal network and the outside internet, and most often, the violators are NAT and SIP ALG.

With a logical troubleshooting flow, you can identify and repair the source cause systematically. Do not forget to eliminate the mundane factors, isolate the issue, and never underrate the might of disabling the SIP ALG.

In a short time, you can have your business phone engine returning to its normal, two-way communication flow that you are accustomed to.

🚀 Still stuck? Do not hesitate to contact your VoIP service provider, such as Dialaxy, or IT specialists for assistance. They possess the equipment and expertise to resolve the most persistent audio issues.

FAQs

1. Can a bad internet connection cause a one-way audio issue?

Yes, but it is not common so easily. Slow or unstable connection in general is a factor that tends to create choppy, delayed, or garbled audio (an indicator of packet loss or jitter). Yet, it may, in theory, cause a one-way audio issue if the packets in a particular direction are dropped in most cases. Usually, the problem is not related to speed but to configuration.

2. Why does my VoIP call work on my mobile app but not my desk phone?

This tends to be the case since your cellular phone (e.g., 4G/5G) is a totally separate network, which your mobile app might be able to utilize and which does not experience the local Wi-Fi issues. It identifies the problem that lies in the router settings of your local network (probably SIP ALG or firewall problem) and not in the VoIP provider or account itself.

3. Is the “VoIP phone can hear but not be heard” issue the same as one-way audio?

Yes, that is the most common form of the one-way audio issue, where the audio happens in one direction only. The problem can also be reversed (you can be heard, but you can’t hear them), but the underlying causes and troubleshooting steps are exactly the same. It all comes down to the RTP voice stream failing in one direction.

4. What is the point of turning off SIP ALG on the router?

SIP ALG is an old router option that usually corrupts call data in VoIP call information and leads to the creation of one-sided audio. The most popular solution is to disable it, as it will direct the call data through your router in a proper way.

5. How can a one-way audio be rectified very quickly?

Step one: Power cycle your network. Unplug your modem, router, and phone, and wait 60 seconds before re-plugging them (in that order, starting with the modem). It is a simple reboot because it resolves the majority of temporary network errors that may cause this problem.

6. What is Double NAT, and can it cause one-way audio?

Yes. The situation of double NAT occurs when you have two routers on your network (such as an ISP modem/router and your own router). This mixes voice traffic and is a probable cause of one-way audio.