> For the complete documentation index, see [llms.txt](https://prosbcdocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prosbcdocs.telcobridges.com/tmedia-documentation/configuration/web-portal-3-3/protocol-stack/sip/enabling-local-nat-traversal.md).

# Enabling Local NAT Traversal

> **Applies to:** Tmedia 3.0, 3.2, 3.3

To enable Local NAT Traversal:

1- Select **NATs** from the navigation panel.

![EnableLocalNatTraversal 0](https://docs.telcobridges.com/w/images/7/7e/EnableLocalNatTraversal_0.png)

2- Click **Create New NAT Traversal**

![EnableLocalNatTraversal 1](https://docs.telcobridges.com/w/images/d/d1/EnableLocalNatTraversal_1.png)

3- Enter a meaningful name.

* Choose a Local Method.
* If necessary, provide an extra parameter.
* Click **Create**

![EnableLocalNatTraversal 2](https://docs.telcobridges.com/w/images/a/af/EnableLocalNatTraversal_2.png)

Once the NAT configuration is completed, it must be associated with a NAP.

3- Select **NAPs** from the navigation panel

![EnableLocalNatTraversal 3](https://docs.telcobridges.com/w/images/3/33/EnableLocalNatTraversal_3.png)

4- Select a SIP NAP from the **Network Access Point** list

![EnableLocalNatTraversal 4](https://docs.telcobridges.com/w/images/3/38/EnableLocalNatTraversal_4.png)

5- In the **Network Address Translation** section:

* Choose the desired "Local Method". The select box will contain the same name as the Local NAT configuration, that you provided in step #2.
* Click **Save**

![EnableLocalNatTraversal 5](https://docs.telcobridges.com/w/images/4/4a/EnableLocalNatTraversal_5.png)

The following describes the 2 Local NAT Traversal Methods:'''

**No NAT**

This method is used if you are not behind a NAT. This is the default value.

**Force Public IP**

This method will set some of the SIP Headers and SDP fields with the IP address that you set.

**Path**

```
/configurations/@[configuration_name]/naps/@[nap_name]/sip_cfg/network_address_translation
```

**Parameters (text)**

```
/configurations/@[configuration_name]/naps/@[nap_name]/sip_cfg/network_address_translation
local_method  = ""
remote_method = "None"
```

**Parameters (json)**

```
{
    "network_address_translation" : {
      "local_method" : "",
      "remote_method" : "None"
    }
  }
}
```

### Related actions

[Symmetric NAT traversal](https://prosbcdocs.telcobridges.com/telecom-references/sip-and-voip/sip/nat-traversal)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://prosbcdocs.telcobridges.com/tmedia-documentation/configuration/web-portal-3-3/protocol-stack/sip/enabling-local-nat-traversal.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.