
SIP ALG: What It Is, Why It Breaks VoIP Calls, and When to Disable It
SIP ALG is a feature built into many routers and firewalls that tries to help Session Initiation Protocol (SIP) voice calls work through Network Address Translation (NAT). In practice, it is one of the most common causes of broken business phone calls. If your team can dial out but cannot hear the caller, if calls drop after about 30 seconds, or if desk phones keep losing registration, SIP ALG is one of the first settings to check.
This guide explains what SIP ALG does, how it works, why it so often makes VoIP worse instead of better, when you should disable it, and how to turn it off safely on FortiGate, Cisco, UniFi, pfSense, MikroTik, and common home and small-business routers. You will also find a symptom table, a vendor-by-vendor disable guide, a safe testing checklist, and better alternatives such as a session border controller (SBC), STUN, and SIP over TLS.
What Is SIP ALG?
SIP ALG stands for Session Initiation Protocol Application Layer Gateway. It is a helper, sometimes called a SIP helper, SIP inspection, or SIP NAT helper, that watches SIP traffic passing through a router or firewall. When it sees a SIP message, it tries to rewrite the private IP addresses and ports inside that message so they match the public IP address and ports used on the internet.
SIP is the signalling protocol that sets up, manages, and ends most Voice over IP (VoIP) calls. It is used by desk phones, softphones, cloud PBX systems, and SIP trunk providers. A separate stream, usually Real-time Transport Protocol (RTP), carries the actual voice. That split is exactly why SIP and NAT do not get along without help.
When a phone behind a router sends a SIP INVITE message, the message does not only use IP addresses in the normal IP packet header. It also embeds IP addresses and ports inside the message body, in SIP headers such as Contact and Via, and in the Session Description Protocol (SDP) section that negotiates where voice packets should be sent. A normal NAT router rewrites only the outer packet header. It does not look inside the SIP message. The phone therefore tells the provider, in effect, to send its voice to 192.168.1.20 on port 10000, which is a private address that cannot be reached from the internet.
SIP ALG was designed to solve that problem. It opens the SIP packet, finds those private addresses, replaces them with the router’s public address, and opens temporary firewall pinholes for the RTP voice stream. In the late 1990s and early 2000s, when most SIP devices had no NAT traversal of their own, that was a useful idea.
Today, most modern SIP phones, PBXs, and cloud providers handle NAT themselves. They use STUN, ICE, outbound proxies, keep-alive messages, and session border controllers. When both the ALG and the phone try to fix the same addresses, they often rewrite each other, and the call breaks in confusing ways. That is why most VoIP providers now recommend disabling SIP ALG.
How SIP ALG Works, Step by Step
Understanding the normal call flow makes the failure modes much easier to recognise.
- Registration: A desk phone sends a SIP REGISTER message to its provider or PBX, saying it is extension 204, reachable at this IP address and port.
- Call setup: When you dial, the phone sends a SIP INVITE with SDP. The SDP says which IP address and UDP ports should receive the RTP voice stream, and which codecs are supported.
- ALG inspection: If SIP ALG is enabled, the router inspects the SIP packet, rewrites the private address in the Contact, Via, and SDP fields to its public address, and creates a NAT mapping for the RTP ports.
- Answering: The called phone replies with its own SDP, the call is connected, and RTP voice packets flow in both directions.
- Teardown: A SIP BYE message ends the call, and the NAT mappings should close.
That sequence only works if the ALG understands the exact SIP dialect, the ports, and the timing used by your phones and provider. Many ALG implementations are old, incomplete, or based on an early version of SIP. They may rewrite only some fields, change the length of a packet and corrupt its checksum, mishandle SIP over a non-standard port, or fail to open the full RTP port range. The result is a call that appears to connect but has no voice, or a call that drops when the session timer expires.
For a broader grounding in how internet phone calls work, read our guide to Voice over IP (VoIP): definition, how it works, and how to secure it. SIP ALG sits between your phones and that VoIP service, and it is a frequent source of trouble at that boundary.
Common Symptoms That Point to SIP ALG
SIP ALG problems are distinctive because the phone system often looks healthy. Phones register, calls ring, and the call timer runs, but the voice path is wrong. Use the table below to match what users report with the likely cause.
| Symptom | What users experience | Why SIP ALG is a likely cause |
|---|---|---|
| One-way audio | One side can hear, the other cannot | ALG rewrote the SDP address for one direction only, or opened RTP pinholes for one direction only |
| No audio at all | Call connects, then silence on both sides | SDP addresses point to a private IP, or RTP ports were not opened |
| Calls drop after 30 seconds | Call ends at about 30 seconds, repeatedly | Re-INVITE or session refresh messages were altered or blocked, so one side thinks the call ended |
| Calls drop after 15 minutes | Long calls end at a regular interval | Session timer or NAT mapping expired because the ALG did not track the refresh correctly |
| Phones lose registration | Phones show unregistered, then recover | REGISTER messages were modified, or the NAT binding timed out |
| Inbound calls fail, outbound work | External callers get no answer or a fast busy signal | ALG changed the Contact address, so the provider cannot route inbound calls to the phone |
| Caller ID or transfer fails | Transfers, hold, or caller ID behave strangely | ALG altered SIP headers used by transfer and caller ID features |
| Only some phones fail | One model or one site has problems, others do not | That phone or PBX already handles NAT, so the ALG second rewrite conflicts with it |
If several of these symptoms appear together, and they started after a router change, a firmware update, or a move to a new internet provider, disable SIP ALG as a test before you replace phones, change providers, or rebuild the network. It is a five-minute test that solves a large share of VoIP audio faults.
Is SIP ALG a Security Feature?
No. SIP ALG is not a security control, and it should not be treated as one. It does not encrypt calls, authenticate callers, or block toll fraud. It is a NAT compatibility helper that inspects and changes voice traffic in transit. In fact, from a security point of view, disabling it is often the safer choice.
First, SIP ALG requires the firewall to open SIP messages and rewrite them. That is the opposite of the modern approach to VoIP security, which is to encrypt SIP signalling with TLS and voice with Secure RTP (SRTP). When SIP is encrypted, the ALG cannot read the SIP headers or SDP at all, so it cannot help, and it may interfere with the encrypted session. A well-configured system should not depend on a middlebox reading clear-text call setup.
Second, a buggy ALG can expose more than it protects. Some implementations open wide RTP port ranges, keep pinholes open too long, or mishandle SIP messages in ways that can be probed. SIP ALG does not replace a firewall rule, an access list, or a session border controller. It does not stop SIP scanning, brute-force registration attempts, or toll fraud, which are the real threats to a phone system.
Third, disabling SIP ALG does not open your network to the internet. Your firewall still controls which ports are reachable. The SIP and RTP ports you need should be opened deliberately, to the provider or SBC only, not to everyone. That is a much stronger posture than relying on an ALG to open ports dynamically and unpredictably.
Secure VoIP instead with a short list of controls that actually work: use SIP over TLS on port 5061 and SRTP for voice where your provider supports them, use strong, unique SIP passwords and disable unused extensions, restrict SIP access to your provider’s IP addresses, put phones on a separate voice VLAN, and monitor call records for unusual international or premium-rate calls. A network switch that supports VLANs makes that separation practical, even in a small office.
Should You Disable SIP ALG? The Short Answer
For most modern VoIP deployments, yes: disable SIP ALG. That is the recommendation of most cloud PBX and SIP trunk providers, including Nextiva, RingCentral, and 3CX, because their platforms already handle NAT traversal.
There are exceptions. You may need to keep SIP ALG, or a similar helper, if you have a very old PBX that cannot do NAT traversal, if your provider explicitly requires it, or if you have no SBC, no STUN server, and no way to configure static NAT or port forwarding. In those cases, test carefully, and treat the ALG as a temporary workaround while you plan a proper replacement, not as a permanent design.
| Situation | Recommended setting | Reason |
|---|---|---|
| Cloud PBX or hosted VoIP | Disable | Provider handles NAT with SBC, STUN, and ICE |
| SIP trunk to a modern PBX | Disable | PBX and SBC handle NAT; ALG causes double rewriting |
| SIP over TLS and SRTP | Disable | Encrypted SIP cannot be read or rewritten by an ALG |
| Remote workers on softphones | Disable | Softphones use ICE and keep-alives; ALG breaks them |
| Legacy PBX with no NAT support | Test both settings | ALG may be the only NAT fix, but test an SBC first |
| Provider explicitly requires ALG | Follow provider guidance | Ask the provider to confirm in writing, and retest after any change |
If you are unsure, disable it in a maintenance window, test the five call types below, and leave it off if the tests pass. If the tests fail with it off, re-enable it and test again. The comparison, not a guess, should decide the setting.
How to Disable SIP ALG on Common Routers and Firewalls
Menu names vary by vendor and firmware, but the setting is usually in the firewall, NAT, VoIP, or application-layer gateway section. Back up the router configuration before you change anything, and note the original setting so you can restore it.
| Vendor or platform | Where to find it | What to do |
|---|---|---|
| FortiGate | CLI, or Policy and Objects, then Protocol Options | Disable the SIP session helper and SIP ALG; use the session-helper configuration to delete the SIP helper, then set the SIP ALG to disable in the VoIP profile |
| Cisco ASA and Firepower | Inspection policies | Disable SIP inspection in the global policy, or remove inspect sip from the policy map |
| Cisco IOS routers | CLI | Remove SIP inspection for SIP, or disable the SIP ALG in the NAT and firewall configuration |
| UniFi (Ubiquiti) | UniFi OS, Settings, Firewall and Security, or the gateway CLI | Turn off the SIP ALG and conntrack SIP helper; on UniFi gateways this is often under the firewall settings or the configure CLI |
| pfSense and OPNsense | Firewall, NAT, Outbound | No SIP ALG is enabled by default; do not install or enable the siproxd package unless you have a specific legacy need |
| MikroTik RouterOS | IP, Firewall, Service Ports | Disable the SIP service port, which is the SIP helper |
| TP-Link, Netgear, D-Link, Zyxel | Advanced, NAT, ALG, or Security settings | Untick SIP ALG, SIP Passthrough, or SIP Helper, then save and reboot the router |
| DrayTek Vigor | Firewall, ALG, or VoIP settings | Disable SIP ALG, then reboot the router and the phones |
| SonicWall | VoIP, Settings, or Firewall settings | Disable SIP transformations, also called SIP ALG, and enable consistent NAT for VoIP |
| WatchGuard | Policy, SIP proxy or ALG settings | Disable the SIP ALG or SIP proxy, and use a specific SIP policy for your provider instead |
After changing the setting, reboot the router if the vendor recommends it, and reboot or re-register the phones. Some NAT bindings and ALG state survive a settings change until the device restarts, so a test done without a reboot can give a misleading result.
Generic steps for any router
- Log in to the router or firewall admin interface and export a backup of the current configuration.
- Search the settings for SIP ALG, SIP Helper, SIP Passthrough, SIP Inspection, or SIP Transformations.
- Turn the setting off, save the change, and reboot the router if prompted.
- Reboot the desk phones or restart the softphone app so they register again with a clean NAT binding.
- Test the five call types in the checklist below, and record the result for each.
- If all five pass, leave SIP ALG off. If a specific test fails, note exactly which one, then try the troubleshooting steps in the next section.
Testing After You Disable SIP ALG
Do not judge the change on a single call. Test each path that uses SIP, because inbound, outbound, internal, transfer, and long calls can fail in different ways.
- Outbound call: Call an external number. Confirm two-way audio for at least two minutes.
- Inbound call: Call in from a mobile phone. Confirm two-way audio and correct caller ID.
- Internal call: Call another extension in the same office. Confirm audio and that the call does not drop.
- Transfer and hold: Put a call on hold, transfer it to another extension, and confirm audio resumes after the transfer.
- Long call: Keep a call open for more than 15 minutes, or at least past the point where calls used to drop, and confirm it stays connected.
Also test voicemail, call forwarding, and conference calls if your team uses them. If a test fails, capture the time, the extensions involved, the direction of the call, and whether audio failed in one direction or both. That detail is what your provider or PBX vendor needs to help you.
If Disabling SIP ALG Does Not Fix the Call
SIP ALG is a common cause, but it is not the only one. Work through the other likely causes before you re-enable it.
- Double NAT: Two routers in series, for example an ISP router and your own firewall, each create NAT. Put the ISP device in bridge or pass-through mode, or use only one NAT device.
- RTP ports blocked: SIP uses port 5060, or 5061 for TLS, but voice uses a wide RTP range, often UDP 10000 to 20000. Your firewall must allow that range to and from your provider.
- Short NAT timeout: If the NAT mapping expires between keep-alive messages, inbound calls fail. Shorten the phone registration interval, enable keep-alives, or increase the NAT timeout.
- Wrong SIP port: Some providers use a non-standard SIP port. Make sure the phone, PBX, and firewall all use the same port.
- Bandwidth and QoS: Voice is sensitive to delay, jitter, and packet loss. Give voice traffic priority with Quality of Service (QoS), and check that a backup, video call, or large download is not saturating the link during the test.
- Codec mismatch: If the phone and provider cannot agree on a codec, the call may connect with no audio. Use a common codec such as G.711 for testing, then re-enable the preferred codec.
- Firewall rules: A strict firewall may block SIP or RTP from the provider new IP addresses. Confirm the provider current IP ranges and allow them explicitly.
If the problem returns only when SIP ALG is off, and your provider cannot suggest another NAT method, you may have a legacy system that genuinely needs the helper. In that case, keep it on for that specific site, document the exception, and plan to replace the legacy PBX or add an SBC.
Better Alternatives to SIP ALG
Modern VoIP does not need a router to rewrite SIP packets. These alternatives are more reliable and more secure.
Session Border Controller (SBC)
An SBC sits at the edge of your network, or in your provider cloud, and handles NAT, security, transcoding, and call routing for SIP. It is the proper replacement for an ALG in a business deployment. It can hide internal addresses, enforce SIP policies, and log call activity.
STUN, TURN, and ICE
STUN lets a phone discover its public IP address and port. TURN relays media when a direct path is not possible. ICE tests several possible paths and picks the one that works. Together, they let endpoints negotiate a working media path without a router rewriting SIP messages.
SIP over TLS and SRTP
Encrypting SIP with TLS and voice with SRTP protects call setup and media from eavesdropping and tampering. It also removes the ALG from the path, because the ALG cannot read encrypted SIP. Ask your provider whether it supports TLS on port 5061 and SRTP.
Static NAT and port forwarding
For a single on-premises PBX, a static NAT mapping and explicit port forwarding for SIP and RTP can be more predictable than an ALG. Open only the ports you need, to the provider only, and document the rules.
Cloud PBX
Moving the PBX to the cloud removes most on-site NAT problems. Phones register outbound to the cloud PBX, which handles NAT, and the office firewall only needs to allow outbound SIP and RTP. That is a good option for small offices that do not want to manage a PBX and an SBC.
Frequently Asked Questions
Should I disable SIP ALG on my home router?
Yes, if you use VoIP at home and have audio problems, disable it and test. If you do not use VoIP, the setting has no effect on normal browsing, streaming, or gaming.
Will disabling SIP ALG break my internet?
No. It affects only SIP voice traffic. Web browsing, email, video streaming, and other services do not use SIP ALG.
Does SIP ALG affect Microsoft Teams, Zoom, or WhatsApp calls?
No. Those services use their own signalling and media protocols, not SIP in the way a SIP phone or PBX does. Disabling SIP ALG should not affect them.
Why do some routers have SIP ALG on by default?
It was a useful default when SIP devices had poor NAT support. Many vendors have kept it on for compatibility, even though modern providers recommend it off. Check the setting after every firmware update, because updates can re-enable it.
What is the difference between SIP ALG and a SIP proxy?
A SIP ALG is a NAT helper in a router that rewrites SIP packets in transit. A SIP proxy is a server that routes SIP messages between endpoints, often with authentication, logging, and policy. A session border controller is a specialised proxy at a network edge.
Do I need SIP ALG for a SIP trunk?
Usually no. A modern SIP trunk provider or SBC handles NAT. If your provider documentation says to disable SIP ALG, follow that guidance and test the trunk after the change.
Bottom Line
SIP ALG was built to help SIP calls survive NAT, but on modern networks it more often breaks them. It can cause one-way audio, no audio, dropped calls, and registration failures, and it is not a security control. For most cloud PBX, SIP trunk, and softphone deployments, the right move is to disable SIP ALG, reboot the router and phones, and test inbound, outbound, internal, transfer, and long calls. If the tests pass, leave it off, and secure VoIP properly with SIP over TLS, SRTP, strong SIP credentials, a voice VLAN, QoS, and an SBC where needed. If you have a legacy PBX that truly needs the helper, document that exception and plan a replacement, rather than leaving a buggy ALG as a permanent part of your phone system.


