> Source: [sk53900](https://support.checkpoint.com/results/sk/sk53900)

# sk53900 - Early NAT is applied to SIP / MGCP traffic without any rules for such traffic

| Property | Value |
|----------|-------|
| Solution ID | sk53900 |
| Date Created | 2010-09-09 |
| Last Modified | 2017-06-19 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |

## Symptoms

- * Early NAT is applied to SIP / MGCP traffic without any rules for such traffic (there are no rules that contain these services).  

* Kernel debug ('`fw ctl debug -m fw + mgcp`') may show that Early NAT is performed on MGCP traffic, but then there is no line '`mgcp_standard_hide_nat is on, not doing undo early NAT`'.

## Cause

In certain situations, primarily unsupported configurations, users may attempt to bypass inspection by setting the "Protocol Type" in the MGCP service's "Advanced Properties" to "None".

*Example* :  
Someone attempts to NAT the MGCP call agent, finding out it does not work (unsupported configuration), then trying to bypass the MGCP inspection, by setting the Protocol Type to 'None'.

When policy compiles, even though the Protocol Type in the service is set to 'None', there may be other service definitions in the policy that end up compiling the policy to enforce a Protocol Type on the port, in all rules...

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content