Experiencing one-way audio on your VOS3000 softswitch is one of the most frustrating VoIP problems you can encounter. 😤 When callers can hear the other party but the other party cannot hear them, or vice versa, the root cause almost always lies in how SIP signaling and RTP media streams traverse your network. This comprehensive VOS3000 one-way audio fix guide walks you through every known cause and solution, from NAT-induced SDP problems to firewall misconfigurations and codec mismatches. Whether you are running a small wholesale operation or a large carrier platform, these troubleshooting steps will help you restore two-way audio quickly and reliably. 🔧
The VOS3000 one-way audio fix process requires understanding the separation between SIP signaling (which sets up the call on port 5060) and RTP media streams (which carry the actual voice on dynamic UDP ports). When either path is disrupted, you get asymmetric audio. In this guide, we cover NAT issues that inject private IP addresses into SDP, firewall rules that silently drop RTP packets, codec negotiation failures, SIP ALG corruption of SIP messages, and media proxy configuration on VOS3000. Each section includes diagnostic commands using tcpdump and practical solutions you can implement immediately. 🛠️
One-way audio occurs when the SIP signaling completes successfully (the call is established) but RTP media flows in only one direction. 📞 This is fundamentally a network-level problem, not a VOS3000 software bug. The table below summarizes the primary causes and their frequency in production environments.Cause Frequency Direction Affected Complexity NAT private IP in SDP Very High (45%) Callee cannot hear caller Medium Firewall blocking RTP ports High (25%) One direction based on firewall location Low Codec mismatch Medium (15%) Both directions (no audio at all sometimes) Low SIP ALG interference Medium (10%) Variable Medium Media proxy misconfiguration Low (5%) Variable High
The single most common cause requiring a VOS3000 one-way audio fix is NAT traversal failure. 🔥 When a SIP endpoint sits behind a NAT device, the SDP (Session Description Protocol) body inside the SIP INVITE contains the private IP address of the endpoint (such as 192.168.1.100) instead of the public IP address. The remote endpoint then tries to send RTP packets to this unreachable private IP, resulting in one-way audio where the caller behind NAT can hear the callee but not vice versa.
In VOS3000, this issue manifests when SIP phones or gateways register from behind NAT routers. The VOS3000 server, typically hosted on a public IP, receives the SDP with the private IP and forwards it to the destination. The destination sends RTP to the private IP address, which goes nowhere on the public internet. The RTP from the destination to the VOS3000 server works fine, but the return path is broken. 🚫
To diagnose NAT-related SDP problems, you need to capture and inspect the SIP INVITE messages on your VOS3000 server. Use tcpdump to capture SIP traffic and examine the SDP body for private IP addresses. 🔍
Capture SIP traffic on port 5060:
tcpdump -n -i eth0 port 5060 -A -s 0 | grep -A 20 "c=IN IP4"
If the SDP shows an IP like 192.168.x.x, 10.x.x.x, or 172.16-31.x.x, you have confirmed a NAT SDP problem. The VOS3000 one-way audio fix for this scenario involves enabling media proxy or configuring the endpoint to use its public IP in SDP. 🎯SDP Line Problem Correct Value c=IN IP4 192.168.1.100 Private IP in SDP c=IN IP4 203.0.113.50 m=audio 8000 RTP/AVP 0 8 Port may be NATed Should match actual RTP port a=rtpmap:0 PCMU/8000 Codec info (usually correct) No change needed
The primary VOS3000 one-way audio fix for NAT issues is to enable the media proxy feature. When media proxy is enabled, VOS3000 intercepts the RTP streams and relays them through the server, ensuring both endpoints send and receive RTP to the VOS3000 server IP address. This eliminates the private IP problem entirely. ✅
To enable media proxy in VOS3000:
1. Log in to VOS3000 Web Interface 2. Navigate to System Configuration 3. Select Media Proxy Settings 4. Enable "Media Proxy" for the relevant SIP trunk or gateway 5. Set the RTP port range (default: 10000-60000) 6. Save and restart the EMP service
Alternatively, configure the SIP endpoint (phone or gateway) to use STUN or manually set its external IP address in the SIP settings. Most IP phones have a “NAT Traversal” or “External IP” setting that replaces the private IP in SDP with the public IP. 📱
The second most common reason for needing a VOS3000 one-way audio fix is firewall rules that block RTP ports. VOS3000 uses a configurable range of UDP ports for RTP media streams. If the firewall on the VOS3000 server or any intermediate network device blocks these ports, RTP packets cannot flow in one or both directions. 🧱
By default, VOS3000 uses UDP ports in the range 10000-60000 for RTP. Every concurrent call uses two UDP ports (one for each direction of the RTP stream). If you have 500 concurrent calls, you need at least 1000 ports available. The iptables firewall on CentOS must be configured to allow this entire range. 🔓
Use tcpdump to verify whether RTP packets are arriving at the VOS3000 server on the expected ports. Run this command while a call with one-way audio is active:
tcpdump -n -i eth0 udp portrange 10000-60000 -c 50
If you see RTP packets in only one direction, the firewall on the sending side is likely blocking outgoing RTP. If you see no RTP packets at all, the firewall on the VOS3000 server is blocking incoming RTP. 📋
Check current iptables rules:
iptables -L -n -v | grep -i udp
Apply the correct iptables rules to allow RTP traffic on your VOS3000 one-way audio fix. The following rules open the RTP port range:
iptables -I INPUT -p udp --dport 10000:60000 -j ACCEPT iptables -I OUTPUT -p udp --sport 10000:60000 -j ACCEPT service iptables save
For CentOS 7+ with firewalld:
firewall-cmd --permanent --add-port=10000-60000/udp firewall-cmd --reload
Also ensure the VOS3000 RTP port range configuration matches the firewall rules. Navigate to System Parameters in the VOS3000 web panel and verify the RTP port range setting. You can read more about VOS3000 system parameters for detailed configuration guidance. ⚙️Firewall Check Command Expected Result Check INPUT chain iptables -L INPUT -n -v ACCEPT udp dpts:10000:60000 Check OUTPUT chain iptables -L OUTPUT -n -v ACCEPT udp spts:10000:60000 Verify port range netstat -anup | grep 10000 udp ports in LISTEN state Test RTP flow tcpdump -n -i eth0 udp portrange 10000-60000 Bidirectional RTP packets
Codec mismatch is another frequent cause that requires a VOS3000 one-way audio fix. When two endpoints negotiate different codecs through VOS3000, or when a codec is not supported by one side, audio may flow in only one direction or not at all. The most common scenario involves G.729 (which requires a license) being offered but not available, causing one endpoint to fall back to a codec the other does not support. 🎶
In VOS3000, codec negotiation happens during the SDP exchange in the SIP INVITE and 200 OK messages. If the originating endpoint offers G.711 A-law (payload 8), G.711 U-law (payload 0), and G.729 (payload 18), but the terminating endpoint only supports G.729 and G.711 A-law, the negotiation should succeed with G.711 A-law or G.729. However, if transcoding is required and the VOS3000 server does not have the codec license or transcoding capability, the call may connect with mismatched codecs. ❌
Capture the SIP INVITE and 200 OK messages and compare the codec lists in the SDP:
tcpdump -n -i eth0 port 5060 -A -s 0 | grep -A 5 "m=audio"
Look for the codec payload numbers in the m=audio line and the corresponding a=rtpmap entries. If the INVITE offers codecs 0,8,18 but the 200 OK only returns codec 18, and your VOS3000 does not have G.729 transcoding, you have a codec mismatch. 🔬Payload Type Codec Bandwidth License Required 0 G.711 U-law (PCMU) 64 kbps No 8 G.711 A-law (PCMA) 64 kbps No 18 G.729 8 kbps Yes 4 G.723.1 5.3/6.3 kbps Yes 9 G.722 64 kbps No
To resolve codec mismatch as part of your VOS3000 one-way audio fix, ensure both endpoints share at least one common codec. The most reliable approach is to configure VOS3000 to prefer G.711 (PCMU/PCMA) as these codecs are universally supported and do not require licenses. Configure the preferred codec list in the SIP trunk or gateway settings within VOS3000. 🏆
For G.729 support, ensure you have valid G.729 codec licenses installed. You can check license status in the VOS3000 web panel under License Management. If you need transcoding between G.711 and G.729, VOS3000 must have the transcoding module enabled with sufficient licenses. Learn more about VOS3000 transcoding codec configuration. 🔑
SIP ALG (Application Layer Gateway) is a feature on many routers and firewalls that modifies SIP messages as they pass through. While intended to help with NAT traversal, SIP ALG frequently corrupts SIP messages, causing one-way audio, failed calls, and registration problems. Disabling SIP ALG is a critical step in any VOS3000 one-way audio fix. ⚠️
SIP ALG modifies the SDP body, changing the IP address and port numbers. This can result in the RTP stream being sent to an incorrect IP address, causing one-way audio. SIP ALG can also modify the Contact header, Via header, and other SIP headers, breaking the signaling path. 🛑
To determine if SIP ALG is causing your VOS3000 one-way audio fix issue, compare the SIP message as sent by the endpoint with the message as received by VOS3000. If the IP addresses or ports in the SDP have been altered, SIP ALG is active. 🕵️
# Capture SIP on the endpoint side tcpdump -n -i eth0 port 5060 -w /tmp/endpoint_sip.pcap # Capture SIP on VOS3000 side tcpdump -n -i eth0 port 5060 -w /tmp/vos3000_sip.pcap # Compare SDP bodies between the two captures
Common signs of SIP ALG interference include unexpected public IP addresses replacing private IPs in Contact headers, modified port numbers in SDP, and extra Via headers inserted by the router. 📝
| Router Brand | SIP ALG Location | How to Disable |
|---|---|---|
| Cisco | Advanced NAT Settings | no ip nat service sip udp |
| Mikrotik | IP Firewall NAT | Remove SIP helper rule |
| Fortinet | VoIP Profile | Disable SIP ALG in profile |
| Palo Alto | App Override | Create SIP app-override rule |
| Juniper | ALG Settings | delete security alg sip |
| Netgear | WAN Settings | Disable SIP ALG checkbox |
Disable SIP ALG on all routers and firewalls between the SIP endpoints and the VOS3000 server. This is essential for a complete VOS3000 one-way audio fix. If you cannot disable SIP ALG on a managed router, configure VOS3000 to use TCP transport for SIP instead of UDP, as SIP ALG typically only inspects UDP traffic. You can also use a VPN tunnel to bypass the SIP ALG device entirely. 🔒
The media proxy feature in VOS3000 is one of the most effective tools for resolving one-way audio. When enabled, VOS3000 acts as a relay for RTP media streams, ensuring both endpoints send and receive audio through the VOS3000 server. This eliminates NAT traversal issues and simplifies firewall configuration. The VOS3000 one-way audio fix often comes down to properly configuring media proxy. 🎛️
Media proxy can be enabled per SIP trunk, per gateway, or globally. When media proxy is active, VOS3000 allocates RTP ports from the configured range and inserts its own IP address into the SDP body. Both endpoints then send RTP to VOS3000, which relays the media between them. This adds slight latency but guarantees two-way audio. 🔄
VOS3000 Media Proxy Configuration Steps: 1. Login to VOS3000 Web Panel 2. Go to Gateway Configuration 3. Select the SIP Gateway or SIP Trunk 4. Enable "Media Proxy" option 5. Verify RTP port range in System Parameters 6. Ensure firewall allows RTP port range 7. Restart EMP service: service vos3000empd restart 8. Test with a call and verify bidirectional audio
When media proxy is disabled (direct media), VOS3000 only handles SIP signaling and lets RTP flow directly between endpoints. This reduces server load but requires both endpoints to have direct network connectivity. If your endpoints are behind NAT, direct media will almost certainly cause one-way audio. For more on media proxy, see our guide on VOS3000 media proxy. 📖Configuration Media Proxy ON Media Proxy OFF RTP Flow Through VOS3000 server Direct between endpoints NAT Compatibility Excellent Poor Server CPU Load Higher Lower Audio Latency Slightly higher Lower One-Way Audio Risk Very Low High (with NAT)
Use this text-based flowchart as your systematic approach to the VOS3000 one-way audio fix. Follow each step in order to identify and resolve the root cause efficiently. 🗺️
============================================= VOS3000 ONE-WAY AUDIO FIX FLOWCHART ============================================= START: One-Way Audio Reported | v [1] Capture SIP INVITE with tcpdump | tcpdump -n -i eth0 port 5060 -A -s 0 v [2] Check SDP for Private IP (192.168.x / 10.x) | +-- YES --> Private IP Found | | | +--> Enable Media Proxy on VOS3000 | +--> OR configure endpoint External IP | +--> OR disable SIP ALG on router | | v v [3] Check RTP Flow with tcpdump | tcpdump -n -i eth0 udp portrange 10000-60000 | +-- One direction only --> Firewall blocking RTP | | | +--> Open RTP port range in iptables | +--> Check intermediate firewalls | +--> Verify VOS3000 RTP port config | v [4] Check Codec Negotiation in SDP | +-- Mismatch found --> Codec mismatch | | | +--> Configure common codecs | +--> Enable transcoding on VOS3000 | +--> Verify G.729 license | v [5] Check SIP ALG Modification | +-- SDP modified by ALG --> Disable SIP ALG on router | Use TCP transport for SIP | Create VPN tunnel | v [6] Verify Media Proxy Configuration | +--> Enable media proxy for affected trunks +--> Restart EMP service +--> Test bidirectional audio | v RESOLVED: Two-Way Audio Restored =============================================
Having the right diagnostic commands at your fingertips is crucial for any VOS3000 one-way audio fix. The table below provides a quick reference for all the essential commands used in troubleshooting one-way audio. 💻Purpose Command What to Look For Capture SIP signaling tcpdump -n -i eth0 port 5060 -A -s 0 SDP body, Contact header, Via header Capture RTP media tcpdump -n -i eth0 udp portrange 10000-60000 Bidirectional UDP packets Check SDP IP address tcpdump -n -i eth0 port 5060 -A | grep “c=IN IP4” Private vs public IP Check EMP service service vos3000empd status Running state Check listening ports netstat -anup | grep vos3000 UDP port bindings Check iptables rules iptables -L -n -v RTP port range rules Monitor RTP in real-time sngrep -c -l Active calls and RTP info Check VOS3000 logs tail -f /var/log/vos3000/emp.log Media proxy events
For a thorough VOS3000 one-way audio fix, you may need to perform deeper packet analysis. These advanced tcpdump techniques help you isolate the exact point of failure in the RTP path. 🧪
Capture RTP to and from a specific IP address:
tcpdump -n -i eth0 host 203.0.113.50 and udp portrange 10000-60000 -c 100
Capture and save to a PCAP file for Wireshark analysis:
tcpdump -n -i eth0 -w /tmp/rtp_capture.pcap udp portrange 10000-60000
Filter RTP by checking the RTP version byte (first byte should be 0x80):
tcpdump -n -i eth0 'udp portrange 10000-60000 and udp[8:1] = 0x80' -c 50
Count RTP packets in each direction:
tcpdump -n -i eth0 udp portrange 10000-60000 -c 1000 | awk '{print $3}' | sort | uniq -c | sort -rn
If you see packets flowing in only one direction, you have confirmed the direction of the one-way audio problem. The side that is not sending RTP is the side with the firewall or NAT issue. This is a critical finding for your VOS3000 one-way audio fix. 📊
Prevention is always better than cure. Implement these best practices to avoid needing a VOS3000 one-way audio fix in the future. 🏗️
First, always enable media proxy for any SIP trunk or gateway that connects to endpoints behind NAT. This single configuration change eliminates the majority of one-way audio problems. Second, standardize on G.711 codecs unless bandwidth constraints require G.729. G.711 is universally supported and eliminates codec mismatch issues. Third, disable SIP ALG on all routers in the network path. Fourth, implement proper firewall rules that allow the full RTP port range. Fifth, monitor your VOS3000 system regularly using the built-in VOS3000 monitoring tools and ASR ACD analysis to detect audio quality degradation early. 📈
For additional troubleshooting resources, refer to the VOS3000 troubleshooting guide 2026 and VOS3000 error codes. You can also explore call analysis tools and CDR analysis billing reports to identify patterns in one-way audio incidents. 🔎Prevention Measure Implementation Effectiveness Enable media proxy Per trunk/gateway config 95% of one-way audio prevented Disable SIP ALG Router/firewall config 90% of SIP corruption prevented Standardize G.711 Codec preference settings 100% codec mismatch prevented Open RTP port range iptables/firewalld rules 100% firewall issues prevented NAT keepalive Session timer config Reduces NAT timeout drops Regular monitoring ASR/ACD dashboards Early detection of issues
The most common cause of one-way audio in VOS3000 is NAT traversal failure, where the SDP body contains a private IP address instead of the public IP. This happens when SIP endpoints are behind NAT routers and the VOS3000 server does not have media proxy enabled. The remote endpoint tries to send RTP to the private IP, which is unreachable from the public internet. Enabling media proxy on VOS3000 resolves this in most cases. 🌐
To verify media proxy is working, make a test call and then run tcpdump on the VOS3000 server to capture RTP traffic. If you see RTP packets flowing through the VOS3000 server IP (both source and destination involve the VOS3000 IP), media proxy is active. You can also check the VOS3000 web panel under active calls to see the media proxy status for each call. Use the command: tcpdump -n -i eth0 host YOUR_VOS3000_IP and udp portrange 10000-60000 🔍
Yes, SIP ALG can still cause one-way audio even when media proxy is enabled. SIP ALG may modify the SIP Contact header or Via header before the message reaches VOS3000, causing signaling issues that prevent proper media proxy establishment. SIP ALG can also modify the SDP in ways that confuse the media proxy allocation. Always disable SIP ALG on all routers for reliable VOS3000 operation. ⚠️
The default RTP port range in VOS3000 is 10000-60000. This provides 50000 ports, supporting up to 25000 concurrent calls (each call uses 2 RTP ports). Ensure your firewall allows the entire range. If you have a very high call volume server, you may need to verify the port range in System Parameters and adjust accordingly. Never use a narrow port range as it can cause port exhaustion and one-way audio. 🔢
The method varies by router brand. On Cisco routers, use “no ip nat service sip udp” in configuration mode. On Mikrotik, remove the SIP helper NAT rule. On Fortinet firewalls, disable SIP ALG in the VoIP profile. On consumer routers (Netgear, TP-Link, D-Link), look for “SIP ALG” or “VoIP ALG” in the advanced WAN or NAT settings and uncheck it. Consult your router documentation for specific instructions. 📱
Yes, enabling media proxy increases CPU and network load on the VOS3000 server because all RTP media flows through the server instead of directly between endpoints. For a typical server handling 1000 concurrent calls with G.711 codecs, media proxy adds approximately 128 Mbps of network throughput and moderate CPU usage. Ensure your server has sufficient resources. For high-capacity deployments, consider dedicated media servers or hardware load balancing. Learn more about server requirements from our VOS3000 hosting guide. 💪
Codec mismatch typically causes no audio in both directions rather than one-way audio. However, in certain scenarios with VOS3000 transcoding, if one direction successfully transcodes but the other fails, you may experience one-way audio. This is less common than NAT or firewall issues but should be checked if other causes are ruled out. Always verify codec negotiation using tcpdump or sngrep during a problem call. 🎵
Install sngrep using “yum install sngrep” or compile from source. Run “sngrep” to see live SIP call flow. Press “c” to capture new calls and select a call to view the full SIP message exchange including SDP. The SDP body shows the IP and port where each endpoint expects to receive RTP. Compare these with the actual RTP flow captured by tcpdump to identify the direction of the audio failure. 🖥️
If you are still struggling with a VOS3000 one-way audio fix after following this guide, our expert team is ready to help. We provide professional VOS3000 support, installation, and hosting services. Reach out to us on WhatsApp for immediate assistance. 🤝
WhatsApp: +8801911119966
We can help you with VOS3000 installation service, server rental, security hardening, and complete architecture design. For official VOS3000 software downloads, visit vos3000.com/downloads. 🚀
For professional VOS3000 installations and deployment, VOS3000 Server Rental Solution:
📱 WhatsApp: +8801911119966
🌐 Website: www.vos3000.com
🌐 Blog: multahost.com/blog
Essential VOS3000 high CPU usage optimization guide. Diagnose CPU spikes with top htop, fix SIP flood attacks, MySQL query optimization,… Read More
Complete VOS3000 database recovery MySQL corruption fix guide. Repair InnoDB corruption, restore from mysqldump, use mysqlcheck, innodb_force_recovery, prevent data loss… Read More
Proven VOS3000 call drop disconnect troubleshooting guide. Fix RTP timeout, SIP session timer expiry, firewall UDP timeout, NAT keepalive, failover… Read More
This website uses cookies.