How to resolve VoIP one-way audio or no sound issues on your Brisbane business network
Summary
This guide helps you troubleshoot and resolve: How to resolve VoIP one-way audio or no sound issues on your Brisbane business network. Follow the steps below to fix the issue.
Common Causes
VoIP audio issues, such as one-way sound or no audio at all, are typically caused by network configuration problems, firewall restrictions, or hardware misconfigurations. This guide helps Brisbane small business customers resolve VoIP call audio problems where one or both parties cannot hear each other.
Quick Fix Steps
- Restart your VoIP handset or softphone application.
- Restart your business router and modem.
- Ensure your headset or speakers are selected as the default audio device in your computer settings.
- Check that the microphone is not muted on the handset or within the application.
- Test a call to a different internal extension to determine if the issue is specific to one contact or affects all calls.
Determine the Scope of the Issue
Before changing network settings, identify whether the audio problem affects all handsets or just a single device. This helps isolate whether the issue is device-specific or network-wide.
Single Device Issues
- Check the handset's network status indicators to ensure it has a valid IP address.
- If using a softphone, ensure the application is not running in "Offline" or "Do Not Disturb" mode.
- Swap the handset with another device on the same network port to rule out faulty cabling or hardware.
- Check for duplicate IP addresses on your network. Access your router's DHCP client list and look for any IP conflicts. If a conflict exists, assign a static IP to the VoIP device outside the DHCP range.
Network-Wide Issues
- Test both internal calls (between extensions) and external calls (to outside numbers).
- If internal calls work but external calls have one-way or no audio, the issue is likely related to NAT traversal or your ISP.
- If all calls fail regardless of destination, check your internet connection and VoIP provider registration status.
Verify Network Connectivity and Bandwidth
- Connect your VoIP handset via Ethernet for the most stable experience. Wi-Fi is not recommended for business VoIP due to potential interference and packet loss.
- Run a speed test from a device connected to the same network. VoIP requires a minimum of 100kbps upload and 100kbps download per concurrent call, with low latency and minimal jitter.
- Power cycle your networking equipment by unplugging the router and modem for 30 seconds, then plugging them back in.
- If you are on an NBN business plan, contact your ISP (such as Telstra or Optus) to confirm there are no outages or line faults affecting your premises.
Check Audio Device Settings
Windows
- Right-click the speaker icon in the taskbar and select Open sound settings.
- Under Output, ensure the correct speakers or headset are selected.
- Under Input, ensure the correct microphone is selected.
- Click Device properties for the microphone and ensure the volume is turned up and not muted.
macOS
- Go to System Settings > Sound.
- Select the Input tab and verify the correct microphone is chosen.
- Select the Output tab and verify the correct speakers or headset are chosen.
Check Firewall and Router Settings
- Log into your router's administration panel via a web browser.
- Ensure SIP ALG (Application Layer Gateway) is disabled, as this often interferes with VoIP traffic.
- Contact your VoIP provider to obtain their specific port requirements and STUN server settings. Do not open broad port ranges without provider guidance.
- If your provider specifies ports, open only the required UDP ports (commonly 5060 for SIP and 5061 for SIP over TLS) and the specific RTP media range recommended by your provider.
- If you are using a VLAN for voice traffic, configure QoS (Quality of Service) to prioritise VoIP packets.
- To verify QoS is working, run a call while transferring a large file on the network. Audio should remain clear without chopping or delay.
NAT Traversal and STUN/TURN Configuration
Many Australian business broadband connections use carrier-grade NAT (CGNAT), which can prevent VoIP audio from reaching your handset. This is common on NBN and business-grade connections from Telstra, Optus, and other providers.
Internal vs External Calls
- Internal calls work, external calls do not: This usually indicates a NAT traversal issue. Your VoIP provider may need to configure STUN or TURN server settings on your handset or PBX.
- One-way audio on external calls: This often occurs when your router rewrites the IP address in SIP packets. Disable SIP ALG and ensure your VoIP provider has your public IP address.
- No audio on all calls: Verify your handset is registering with the VoIP server and check for ISP-level SIP blocking.
STUN/TURN Server Settings
- Contact your VoIP provider for their recommended STUN server address.
- Enter the STUN server details in your handset or softphone network settings.
- If your provider uses TURN servers for relay, obtain the TURN server address, username, and password from them.
- Save the settings and reboot the handset or restart the softphone application.
ISP Considerations for Brisbane Businesses
Some Australian ISPs implement SIP blocking or carrier-grade NAT that interferes with VoIP traffic. If you are on a Telstra, Optus, or other NBN business plan:
- Ask your ISP whether they block SIP traffic or use CGNAT on your connection.
- Request a static public IP address if your provider supports it, as this simplifies VoIP configuration.
- If your ISP blocks SIP, you may need to use a VPN or switch to a provider that supports VoIP traffic.
If you have completed these steps and are still experiencing audio issues, please Open a Ticket with our Brisbane support team.
Still Having Issues?
💻 Open a Ticket