> 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/hardware/nat/create-nat-traversal.md).

# Create a NAT Traversal

> **Applies to:** SBC 3.1, 3.3

One or more NAT traversals can be configured to manage the IP connections traversing network address translation (NAT) gateways.

### To configure a NAT traversal

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

![CreateNatTraversal Tsbc 0](https://docs.telcobridges.com/w/images/c/cb/CreateNatTraversal_Tsbc_0.png)

2. Click **Create New NAT Traversal**

![CreateNatTraversal 1](https://docs.telcobridges.com/w/images/7/76/CreateNatTraversal_1.png)

3. Configure the following fields:

* Enter a name for the NAT Traversal.
* Set the local Nat traversal method to **Force public IP**.
* Enter the public IP address of the unit.
* Click **Create**

![CreateNatTraversal 2](https://docs.telcobridges.com/w/images/1/14/CreateNatTraversal_2.png)

4. Verify that the **NAT Configuration was successfully created** message is displayed

![CreateNatTraversal 3](https://docs.telcobridges.com/w/images/7/70/CreateNatTraversal_3.png)

### List of Parameters

* [Name](https://prosbcdocs.telcobridges.com/telecom-references/parameter-reference/m3ua#n)
* [Method](https://prosbcdocs.telcobridges.com/telecom-references/parameter-reference/sip#m)
* [Public Interface](https://prosbcdocs.telcobridges.com/telecom-references/parameter-reference/ip-network#p)


---

# 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/hardware/nat/create-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.