> For the complete documentation index, see [llms.txt](https://help.sipgate.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sipgate.de/cloud-telefonanlage/en/getting-started/konfigurationsanleitungen/wie-richte-ich-die-sip-signalisierung-via-tcp-ein.md).

# How do I set up SIP signaling via TCP?

Configure SIP signaling over TCP in sipgate – for more stable VoIP connections behind firewalls.

#### **SIP signaling via TCP**

{% hint style="info" %}
**Note:** We recommend connecting via **TLS** instead of TCP. You can find the complete configuration details for all transport protocols in the article [Configuring Devices](https://help.sipgate.de/cloud-telefonanlage/erste-schritte/konfigurationsanleitungen/konfiguration-von-endgeraeten).
{% endhint %}

**Transmission Control Protocol (TCP)** is a transport protocol used for reliable, connection-oriented, packet-switched data transmission over the internet. TCP/TLS connections are currently available over both IPv4 and IPv6.

The **User Datagram Protocol (UDP)** is also a transport protocol, but it transmits data without establishing a connection. Unlike TCP, UDP data transmission **does not verify** that the data has been delivered. This allows data to be transmitted faster, but the sender cannot tell whether the complete message reached the intended recipient.

For real-time applications such as telephony, UDP is recommended because of its shorter transmission time, but TCP can be advantageous or even necessary in some cases. UDP is usually the default setting on phones and routers.

If you use a firewall, allow the [sipgate IP and port ranges](https://help.sipgate.de/cloud-telefonanlage/erste-schritte/alles-fur-den-start-mit-sipgate/nutzung-von-sipgate-mit-einer-firewall) through.

You can find the general SIP configuration details (registrar, outbound proxy, ports) for all transport protocols in the article [Configuring Devices](https://help.sipgate.de/cloud-telefonanlage/en/getting-started/konfigurationsanleitungen/konfiguration-von-endgeraeten.md). To use TCP, set the transport protocol on your phone, router or VoIP app to **TCP**.

{% hint style="info" %}
**Tip:** If you do not see a field for changing the transport protocol in the settings, you can enter **sip.sipgate.de;transport=tcp** as the outbound proxy.
{% endhint %}


---

# 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://help.sipgate.de/cloud-telefonanlage/en/getting-started/konfigurationsanleitungen/wie-richte-ich-die-sip-signalisierung-via-tcp-ein.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.
