How To Fix One-Way Audio On VoIP Calls
Understanding One-Way Audio
One-way audio occurs when voice packets travel in one direction but fail to return. For example, you may be able to hear the caller, but they cannot hear you. This is rarely a handset hardware failure and is usually caused by network configuration, firewall settings, or router protocols that interfere with Session Initiation Protocol (SIP) traffic.
Australian small businesses often share a single internet connection for both data and voice, whether on NBN, ADSL, or a business fibre service. Without proper prioritisation and open ports, audio streams can be blocked or dropped by perimeter security devices.
Distinguish Between Inbound-Only and Outbound-Only Audio
Before troubleshooting, identify which direction is failing. This helps narrow down whether the issue is with your outbound firewall rules or your provider's inbound routing.
- Inbound-only audio: You can hear the caller, but they cannot hear you. This usually indicates your outbound RTP media stream is being blocked by your firewall or router.
- Outbound-only audio: The caller can hear you, but you cannot hear them. This usually indicates inbound RTP media is not reaching your handset, often due to NAT issues or missing port forwarding.
- No audio in either direction: Both signalling and media streams are likely blocked, or the handset is not registered correctly with the SIP server.
Also note whether the issue affects only mobile or remote workers using softphones over 4G/5G, or only desk phones on your office NBN connection. Remote workers may be affected by their home router's NAT settings rather than your office firewall.
Step 1: Test With Multiple Devices
Before changing network settings, determine if the issue is isolated to a single handset or affects the entire system.
- Make a test call from the affected VoIP handset to an external number.
- Make a test call from a different handset on the same office network.
- If using a softphone application, test the call from a different computer or mobile device.
- Note whether the problem follows the device, the user, or occurs across all endpoints.
If only one device is affected, proceed to Step 5. If multiple devices experience one-way audio, the issue is likely network-wide and you should continue with Step 2.
Step 2: Disable SIP ALG on Your Router
SIP Application Layer Gateway (ALG) is a feature found on many business routers. It is intended to help VoIP traffic pass through network address translation (NAT), but it often corrupts SIP packets and causes one-way audio.
Common menu paths by router type:
- DrayTek: Advanced > NAT > SIP ALG
- Netgear Business: Advanced > Security > SIP ALG
- TP-Link Omada: Settings > Wireless > VoIP > SIP ALG (varies by firmware)
- Cisco Small Business: Firewall > Application Layer Gateways > SIP
- Log into your business router or gateway administration interface using the admin username and password, typically found on a sticker on the device.
- Navigate to the SIP ALG, SIP Helper, or VoIP passthrough setting using the menu paths above.
- Set SIP ALG to Disabled or Off.
- Click Save, Apply, or Update, then restart the router.
- Test a call to confirm whether two-way audio has been restored.
Step 3: Configure Firewall Rules and Ports
Firewalls can block Real-time Transport Protocol (RTP) audio streams while allowing call signalling to pass through. This results in a connected call with no audio in one or both directions.
RTP port ranges vary by provider. Do not assume a universal range such as 10,000–20,000 applies to your service. Obtain the exact SIP signalling ports and RTP media port range from your provider's documentation or welcome email.
- Identify your VoIP provider's server IP addresses from their documentation, welcome email, or support portal.
- Log into your router or firewall administration interface.
- Navigate to the firewall or security section. Common paths include Advanced > Security > Firewall Rules or WAN > Port Forwarding.
- Create allow rules for UDP traffic to and from your provider's IP addresses on the required SIP and RTP ports.
- Apply the rules to both inbound and outbound traffic.
- Click Save or Apply.
- Test inbound and outbound calls separately to verify audio works in both directions.
Step 4: Configure NAT and STUN/TURN Settings
If your VoIP handsets are behind a router using NAT, the private IP address of the phone may be embedded in SIP packets instead of your public IP address. This prevents the provider from sending audio back to your handset, causing one-way audio.
- Determine your public IP address by visiting a site such as whatismyip.com.au from a computer on your office network.
- Log into your VoIP handset's web interface using the phone's local IP address.
- Navigate to the Network or SIP settings, often found under Settings > Network > SIP or Account > Network.
- Enable NAT traversal or STUN (Session Traversal Utilities for NAT).
- Enter your VoIP provider's STUN server address, for example
stun.provider.com.au, or use a public STUN server such asstun.l.google.com:19302if your provider does not supply one. - If your provider supports TURN servers for relaying media through restrictive firewalls, enter the TURN server address and credentials provided by your carrier.
- Save the settings and reboot the handset.
For remote workers using softphones from home, ensure their home router has SIP ALG disabled and that their softphone app has STUN enabled in its network settings.
Step 5: Configure Quality of Service (QoS)
When internet bandwidth is shared between VoIP calls, video conferencing, file transfers, and web browsing, voice packets can be delayed or dropped. QoS prioritises voice traffic so calls remain clear even during heavy network use.
Australian ADSL, NBN FTTC, and FTTN connections often have limited upstream capacity, making QoS especially important for outbound call audio.
- Access your router's QoS or traffic management settings, often located under Advanced > QoS or Traffic Management > QoS.
- Enable QoS or WMM (Wi-Fi Multimedia) if using wireless handsets.
- Create a rule that prioritises traffic from your VoIP handsets or IP phones by MAC address or VLAN.
- Set the priority level to High or Voice.
- Reserve upload bandwidth for voice traffic. A typical G.711 call requires approximately 80–100 kbps upstream per concurrent call.
- Click Save or Apply.
- Conduct a test call while another device is downloading a large file to confirm voice quality remains stable.
Step 6: Check Handset and Softphone Configuration
Incorrect local settings on the handset can prevent audio from being transmitted or received correctly.
- Verify the handset is registered to the correct SIP server provided by your VoIP carrier.
- Check that the correct audio codec is selected. G.711 is common for local networks, while G.729 may be used to save bandwidth on slower ADSL connections.
- Ensure the microphone and speaker are not muted on the handset or headset.
- For softphones, confirm the correct microphone and speaker devices are selected in the application settings.
- Restart the handset or softphone application and test again.
Step 7: Test Internal Network Path
If the issue persists, inspect the local network path between the handset and the router.
- Connect the affected handset directly to the router using an Ethernet cable, bypassing switches or Wi-Fi extenders.
- Make a test call. If audio works, the issue may be a faulty switch, patch cable, or Wi-Fi interference.
- If using Power over Ethernet (PoE), confirm the switch is providing stable power to the handset.
- Replace any suspect Ethernet cables and retest.
When To Escalate
If you have completed all steps above and one-way audio continues, the issue may be with your internet service provider, VoIP carrier, or external network routing. Document which calls are affected, the time of day, and whether the problem occurs on inbound, outbound, or both call types.
For further assistance, Open a Ticket with our support team.