> 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/creating-a-sip-transport-server.md).

# Creating a SIP Transport Server

Step-by-step: adding a SIP transport server to a SIP stack in the web portal, and choosing the transport protocol it will carry signalling over. SBC 3.1 and 3.3.

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

After you create a SIP stack, you must must create a new SIP transport server for your SIP configuration.

**Note:** In order to employ SIP transport servers, the protocol that they will use to transport the SIP signaling traffic must be defined.

To create a SIP Transport server:

1- Click **SIP** in the navigation panel

![SIP NavigationMenu](https://docs.telcobridges.com/w/images/5/58/SIP_NavigationMenu.png)

2- Select a SIP stack for which you wish to create a transport server

![Select SIP](https://docs.telcobridges.com/w/images/9/9c/Select_SIP.png)

3- Click **Create New Transport Server**

![Create New SIP TransportServer](https://docs.telcobridges.com/w/images/6/69/Create_New_SIP_TransportServer.png)

4- Create the new SIP transport server:

* Enter a **name** for the server
* Select an appropriate **port type**
* Select an appropriate host **IP interface**
* Click **Create**

![Create New SIP TransportServer1](https://docs.telcobridges.com/w/images/a/a6/Create_New_SIP_TransportServer1.png)

5- Verify that the **"SIP transport server was successfully created"** message appears, and that the new server is listed in the **Transport Servers** list

![Create New SIP TransportServer2](https://docs.telcobridges.com/w/images/7/72/Create_New_SIP_TransportServer2.png)

![Create New SIP TransportServer3](https://docs.telcobridges.com/w/images/c/ce/Create_New_SIP_TransportServer3.png)

### List of Parameters

* [Name](https://prosbcdocs.telcobridges.com/telecom-references/parameter-reference/m3ua#n)
* [Port Type](https://prosbcdocs.telcobridges.com/telecom-references/parameter-reference/sip#p)
* [Port](https://prosbcdocs.telcobridges.com/telecom-references/parameter-reference/sip#p)
* [IP Interface](https://prosbcdocs.telcobridges.com/telecom-references/parameter-reference/sip#i)


---

# 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/creating-a-sip-transport-server.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.