> 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/telecom-references/sip-and-voip/enabling-remote-nat-traversal.md).

# Enabling Remote NAT Traversal

> **Applies to:** Tmedia 3.0, 3.2, 3.3; SBC 3.1, 3.3

To enable Remote NAT Traversal:

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

![EnableRemoteNatTraversal 0](https://docs.telcobridges.com/w/images/1/15/EnableRemoteNatTraversal_0_.png)

2- Select a SIP NAP from the **Network Access Point List**

![EnableRemoteNatTraversal 1](https://docs.telcobridges.com/w/images/3/37/EnableRemoteNatTraversal_1.png)

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

* Choose the desired "remote method".
* Click **Save**

![EnableRemoteNatTraversal 2](https://docs.telcobridges.com/w/images/b/be/EnableRemoteNatTraversal_2.png)

The 3 Remote NAT Traversal Methods are described as follows:

**No NAT**

The local endpoint is NOT behind a NAT. This means, your local endpoint has a Public IP address, which is globally routable on the Internet. For further information, refer to <http://en.wikipedia.org/wiki/Private\\_network>.

**Force Passive Mode**

The TMG will NOT send any RTP packets and will wait for the first RTP packet. The remote endpoint will send the first RTP packet. It will ignore the IP address/port sent in the SDP (in the SIP '200 OK' message)and use the IP address/port from where it received the RTP packet.

Note: If the remote endpoint is also set as passive, this method will not work because both sides will wait for the first incoming RTP packet.

**Parse Direction Attribute**

The TMG will look in the SDP to find an attribute direction:active. If it finds this attribute, the TMG will act exactly as the “Force Passive Mode” method. In fact, this a dynamic way to enable the “Force Passive Mode”.

**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://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/sip-voip/nat-traversal/README.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://prosbcdocs.telcobridges.com/telecom-references/sip-and-voip/enabling-remote-nat-traversal.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.