VoIP One-Way Audio: Common Causes and What to Check

VoIP one-way audio is one of the most common business phone system problems. A call may connect successfully, but only one person can hear the other. At first, the issue may look like a phone problem. However, the real cause often involves firewall rules, NAT behavior, RTP routing, SIP settings, codec negotiation, or provider-side media handling.

Common Symptoms of VoIP One-Way Audio

One-way audio can appear in different ways. For example, inbound calls may work while outbound calls fail, or internal calls may have audio while external calls do not.

• The call connects, but only one side hears audio
• Inbound calls work, but outbound calls have no audio
• Outbound calls work, but inbound calls have no audio
• Audio works internally but fails externally
• Calls work from one location but not another
• Audio fails after a firewall, router, ISP, or PBX change
• Remote phones have audio problems while local phones work

Why One-Way Audio Happens

VoIP calls normally use SIP for call setup and RTP for the actual audio stream. As a result, a call can appear connected even when the audio path has a problem.

For example, a firewall may allow SIP signaling but block or misroute RTP audio traffic. In that case, both phones may ring and answer correctly, but audio may only work in one direction.

For general background, Cloudflare provides an overview of VoIP and how internet-based calling works:
What is VoIP?

Common Causes of VoIP One-Way Audio

Several systems must work together for VoIP audio to work correctly. Therefore, troubleshooting should review the PBX, phones, firewall, NAT, internet connection, SIP provider, and RTP path.

• Incorrect NAT settings
• Blocked RTP ports
• Wrong public IP advertised by the PBX or phone system
• Firewall SIP ALG interference
• Provider routing or media relay issues
• VPN or double NAT behavior
• Codec negotiation problems
• Remote phone or hosted phone configuration problems
• Firewall rules that allow signaling but block audio

What to Check First

Before making changes, collect a few call examples. This helps identify whether the issue affects inbound calls, outbound calls, specific extensions, remote phones, or certain destinations.

• Check whether the issue affects inbound calls, outbound calls, or both
• Confirm whether all phones or only some phones have the problem
• Review recent firewall, ISP, router, or PBX changes
• Check RTP port ranges and firewall rules
• Review public IP and NAT settings
• Collect SIP provider call examples and timestamps
• Check whether remote phones or VPN phones are involved
• Confirm whether SIP ALG or similar inspection features are enabled

When to Request VoIP Troubleshooting Help

If one-way audio affects business calls, customer calls, support calls, or front desk activity, request help before making random firewall or PBX changes. Random changes can make the issue worse or create new call routing problems.

A structured review can help identify whether the issue comes from SIP signaling, RTP flow, NAT behavior, firewall policy, provider routing, codec negotiation, or endpoint configuration.