SIP ALG: What It Is and When to Disable It

Your SIP phone rings, the call connects and one person hears silence. An online checklist says to disable SIP ALG. Before changing the router, you need to know whether that feature is handling the call and whether the phone service expects it to be enabled.
SIP ALG is a specific network function, not a universal explanation for VoIP problems. This guide explains what it does, when disabling it is worth testing and how to make a controlled change. It also distinguishes SIP phone troubleshooting from browser-based calling, where the relevant network path may be different.
What Is SIP ALG?
SIP ALG is an application-aware function in some routers and firewalls. It understands parts of SIP traffic rather than treating every packet solely by its network address and port.
SIP is a signaling protocol used to establish, modify and end sessions. A SIP message can carry session-description information about the media to be exchanged. The audio itself commonly travels separately, so successful call setup does not by itself establish working sound.
An ALG may inspect signaling, adjust addresses or ports carried inside it and create related access through the firewall. That behavior is intended to support traffic crossing network boundaries. Whether it is useful depends on the rest of the deployment.
Do not assume every router has the same feature or default. The label, implementation, supported protocols and configuration method can vary by model and firmware.
SIP ALG, NAT, Firewalls and SBCs Are Different
Several components can influence call connectivity. Distinguishing them helps avoid disabling an unrelated control while trying to correct an audio problem.
| Component | Role | Practical distinction |
|---|---|---|
| NAT | Translates network address and port mappings | Does not automatically mean SIP payload rewriting |
| Firewall policy | Permits or denies traffic under configured rules | Must still allow the provider’s required flows |
| SIP ALG | Interprets and may modify SIP-related traffic | Can interact with other traversal mechanisms |
| Session border controller | Handles sessions at a defined service boundary | May already provide the needed signaling and media handling |
| Endpoint traversal features | Help a client establish communication across network boundaries | Must match the supported deployment design |
A provider may already account for NAT through an endpoint, relay or border-controller design. An additional rewrite in the customer router can then produce conflicting information. Another deployment may rely on the firewall’s SIP handling. Neither case supports a universal on-or-off instruction.
IETF guidance on SIP NAT traversal describes several mechanisms rather than one setting that solves every topology. Use the service design and observed traffic to decide which layer needs attention.
Why SIP ALG Can Cause Problems
A problem can arise when the ALG changes signaling in a way that does not match the endpoint or service. The useful question is what changed and whether the other side can use the resulting information.
Incorrect address information: A rewritten message may point the other side toward an unusable media destination. A call can connect while one direction of audio fails. The symptom still needs confirmation through the actual call path.
Conflicting traversal behavior: The endpoint or service may already manage address handling. An additional ALG rewrite can conflict with that mechanism. Check the supported configuration instead of adding several traversal features at once.
Session changes: Hold, resume and transfer can change the media negotiation. A problem that appears only after one of those actions gives a different test case from silence immediately after answer. Preserve that distinction in the support record.
Device-specific implementation: Firmware behavior and active inspection profiles matter. A router’s user interface may not describe every SIP-related helper in use. Have the administrator consult the exact release documentation rather than infer the effective behavior from a single checkbox.
These are possible mechanisms, not a claim that an ALG is the most common cause of every failed call. Microphone selection, permissions, media rules and provider-side issues can produce similar symptoms.
When Should You Test Disabling SIP ALG?
Test a change when you have evidence that SIP inspection is relevant or when the deployment’s supported configuration calls for it. Start with the service provider and the network administrator’s documentation.
| Situation | Reasonable next action |
|---|---|
| Provider documentation explicitly requires ALG disabled | Have the administrator apply the documented setting and test the service |
| SIP behavior differs across otherwise comparable networks | Investigate the affected network’s inspection and traversal configuration |
| Authorized traces show an unexpected signaling rewrite | Review the ALG or related helper with the administrator |
| The existing design relies on SIP inspection | Assess the impact before changing it |
| Only one headset or browser has a microphone issue | Check the local device and permissions first |
| Calls work reliably with the current supported setup | Do not change it solely because a generic checklist says to |
Some manufacturers provide distinct controls for ALG and other SIP helpers. Disabling one function does not prove every SIP-aware behavior has stopped. Conversely, removing a broader application policy may affect more than the targeted function.
Ask the administrator what traffic and users the proposed change affects. A global firewall setting can have a wider impact than the one phone used for testing.
How to Test a SIP ALG Change Safely
The following is a change-and-test process, not a universal router menu path or command. Use the instructions for your device and firmware.
Step 1: Record the symptom: Note who cannot hear whom, the call direction and whether the issue begins at answer or after a hold or transfer. Save the time, time zone and available call identifier. Avoid combining several different failures into “VoIP is broken.”
Step 2: Confirm the architecture: Identify the SIP endpoint, router, any upstream NAT device and the provider’s supported media path. Ask whether SIP inspection is actually applied to these flows. An office router is not necessarily the only device between the phone and the service.
Step 3: Preserve the configuration: Have an authorized administrator record or back up the relevant settings and define rollback. Plan around active calls and the impact of any required restart. Do not guess at administrative credentials or change equipment you do not manage.
Step 4: Make the documented change: Follow the manufacturer’s model- and version-specific instructions. Change the relevant ALG function rather than disabling the entire firewall. Apply or commit the setting as the device requires.
Step 5: Retest representative calls: Check inbound and outbound calls, both audio directions and relevant hold, resume and transfer paths. Allow enough time to test an intermittent symptom. One short successful call does not establish that every path is fixed.
Step 6: Compare and decide: Record the result against the baseline. If the change causes a regression or does not support the intended design, use the rollback plan and continue diagnosis. Keep the final effective configuration documented.
What If You Cannot Find the Setting?
A test record should include the effective configuration, not just the intended change. Record the model, firmware, inspection policy, change time and any required commit or session refresh. If the interface shows ALG disabled but another helper still handles the traffic, the two tests may not represent the different conditions you intended.
The feature may use another name, require a different management interface or be controlled upstream. Start with the exact model and firmware rather than trying settings that merely contain the word “SIP.”
For managed equipment, ask the responsible provider or administrator whether SIP inspection is active and what change path is supported. If an upstream device performs NAT or inspection, changing the downstream router alone may not address the relevant behavior.
Do not factory-reset the router to make a menu appear. A reset can remove unrelated connectivity settings and makes it harder to compare the original problem. Obtain the supported configuration route instead.
Does SIP ALG Affect Browser-Based Calling?
It depends on the architecture. A browser calling interface does not establish that ordinary inspectable SIP signaling crosses the local router.
WebRTC has its own media connectivity mechanisms, described in RFC 8835. A browser call may involve encrypted signaling, ICE connectivity checks and relayed media. The local SIP ALG may not be the component handling those flows.
For browser-only microphone or audio trouble, start with the selected input and output, site and operating-system permissions and the application’s diagnostics. If the issue follows the network across devices, ask support which network flows need review. Do not assume that changing a SIP setting fixes every webphone.
Checks That Still Matter After ALG Is Disabled
Disabling an ALG does not automatically correct every media path or network policy. Continue from the evidence if the symptom remains.
Use a small comparison log. For each test, record the call direction, whether both parties could hear speech, and the result after hold, resume or transfer where those functions matter. Include any previously healthy function that the change could affect. For example, fixing outbound audio while breaking inbound calls is a regression to investigate, not a completed repair.
If restarting an endpoint or clearing a session was part of the procedure, record that too. The restart may itself change the outcome, so a single successful call does not prove the ALG setting was the only cause. For an intermittent issue, repeat representative tests under comparable conditions and review the evidence with the administrator before assigning a definitive cause.
Check provider-specified destinations and media requirements, upstream NAT, endpoint configuration and any required relay connectivity. Use the documented port and destination requirements for the actual service rather than a generic range copied from another platform.
Do not place phones in a router’s DMZ or broadly open inbound ports as a default workaround. A working test achieved by removing unrelated protections does not identify the minimal correct configuration.
A broader VoIP troubleshooting process can help distinguish dropped calls, quality problems and local audio issues. Keep the current investigation specific to the symptom you can reproduce.
What to Give the Administrator or Voice Provider
A useful handoff describes the topology, exact symptom and controlled tests. It should make clear which observations are confirmed and which are still hypotheses.
- Router or firewall model, firmware and relevant inspection settings.
- Endpoint or application version and the affected network path.
- Call identifiers and timestamps with time zone.
- Direction of the call and the missing audio.
- Whether hold, transfer or a period of idle time triggers it.
- Before-and-after results and any rollback performed.
Share captures and sensitive configuration only through the approved support process. Ask what evidence is needed before collecting it. A trace can contain addressing, identifiers or call information that should not be posted publicly.
Next step
Keep the Setting That the Evidence Supports
Treat SIP ALG as a deployment-specific setting. Confirm its role, make one documented change and compare representative calls before deciding whether the result supports keeping it disabled.
Calilio provides cloud business calling; troubleshooting should follow the application and network path actually in use.
Frequently Asked Questions
These answers clarify the main practical questions about SIP ALG.
What does SIP ALG stand for?
It stands for Session Initiation Protocol Application Layer Gateway. It is an application-aware router or firewall function that can inspect and modify SIP-related traffic.
Should SIP ALG always be disabled?
No. The appropriate setting depends on the device and service design. Follow the supported configuration and use a controlled test when evidence suggests inspection is interfering.
Does one-way audio prove SIP ALG is the cause?
No. Local audio devices, permissions, media filtering, NAT behavior and service-side issues can produce similar symptoms. Diagnose the call path before deciding which setting to change.
Is disabling SIP ALG the same as disabling the firewall?
No. They are different controls. Use the documented function for the exact device rather than turning off broader protection or creating unrestricted access.
Why is there no universal router command here?
Names, interfaces and helper behavior vary by model and firmware. A command for another device can be irrelevant or disruptive. Use the manufacturer’s current instructions for your equipment.
Will disabling it fix a browser microphone problem?
Not necessarily. A browser call may use a different signaling and media path. Check input selection, permissions and the application’s diagnostics before assuming a local SIP ALG is involved.
Summarize this blog with:
Stay in the loop
Get the latest call insights, trends, and updates delivered straight to your inbox.
By subscribing, you agree to receive updates from Calilio.
You can unsubscribe anytime.
Enter the World of AI Business Phone System with Calilio
Improve your business operation with Calilio's advanced virtual phone system. Join today for a better way to connect.
4.6 rating from 125+ reviews, 16+ badges