> 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/alles-fur-den-start-mit-sipgate/nutzung-von-sipgate-mit-einer-firewall.md).

# Using sipgate with a firewall

Here you will find IP addresses, ports, and configuration notes for smooth operation in your company network.

## Signaling & Audio Transmission (SIP & RTP) <a href="#signalisierung-and-audioubertragung-sip-and-rtp" id="signalisierung-and-audioubertragung-sip-and-rtp"></a>

These endpoints are used for SIP signaling and RTP voice transmission. Which rows are relevant depends on the protocol you use to access our products.

### Signaling UDP (port 5060)

| Function  | DNS hostname                                                               | IP address                                                                                                                                                                                                                                                                     | Port | Protocol |
| --------- | -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---- | -------- |
| Signaling | sipgate.de, sipgate.co.uk, sipconnect.sipgate.de, sipconnect.sipgate.co.uk | 217.10.68.150, 217.10.68.151, 217.10.79.9, 217.10.79.23, 2001:ab7::1, 2001:ab7::2, 2001:ab7::3, 2001:ab7::4, 2001:ab7::5, 2001:ab7::6, 2001:ab7::7, 2001:ab7::8, 2001:ab7::9, 2001:ab7::10, 2001:ab7::11, 2001:ab7::12, 2001:ab7::13, 2001:ab7::14, 2001:ab7::15, 2001:ab7::16 | 5060 | UDP      |

### Signaling TCP (port 5060), TLS (port 5061), WebSocket (port 443)

| Function  | DNS hostname                                       | IP address                                                                                                                                                                                                                                                                                                                                         | Port            | Protocol            |
| --------- | -------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | ------------------- |
| Signaling | sip.sipgate.de, sip.sipgate.co.uk, sip.sipgate.com | 212.9.44.242, 212.9.44.243, 212.9.44.244, 212.9.44.245, 217.10.77.242, 217.10.77.243, 217.10.77.244, 217.10.77.245, 217.10.79.10, 217.10.79.11, 217.10.79.12, 217.10.79.13, 2001:ab7::17, 2001:ab7::18, 2001:ab7::19, 2001:ab7::1a, 2001:ab7::1b, 2001:ab7::1c, 2001:ab7::21, 2001:ab7::22, 2001:ab7::37, 2001:ab7::38, 2001:ab7::39, 2001:ab7::3a | 5060, 5061, 443 | TCP, TLS, WebSocket |

### Voice data (RTP, SRTP)

| Function   | DNS hostname | IP address            | Port          | Protocol |
| ---------- | ------------ | --------------------- | ------------- | -------- |
| Voice data | –            | 212.9.44.0/24         | 15000 - 30000 | UDP      |
| Voice data | –            | 217.10.77.0/24        | 15000 - 30000 | UDP      |
| Voice data | –            | 2001:ab7:2000:3::0/64 | 15000 - 30000 | UDP      |
| Voice data | –            | 2001:ab7:3000:2::0/64 | 15000 - 30000 | UDP      |

{% hint style="warning" %}
Note: IP addresses and port ranges may change as the sipgate platform expands. Where possible, we recommend using DNS hostnames. Otherwise, check the IP addresses against this documentation regularly.
{% endhint %}

## sipgate apps <a href="#sipgate-apps" id="sipgate-apps"></a>

Additional services are required to use all the features of the sipgate apps. **In addition** to the permissions listed under "[Signaling & Audio Transmission (SIP & RTP)](#signalisierung-and-audioubertragung-sip-and-rtp)" additional firewall permissions are required, for example for real-time events, contacts, and app updates.

### sipgate app <a href="#sipgate-app" id="sipgate-app"></a>

Depending on the account, the sipgate app runs on one of two platforms: the modern neo platform (NeoPBX) or the older classic platform. They use different backend infrastructures, so the required permissions differ. You can see which platform your account uses in the top-right corner of your account after logging in.

**neo platform (NeoPBX)**

| Function             | DNS hostname/IP               | Port | Protocol |
| -------------------- | ----------------------------- | ---- | -------- |
| Authentication       | workspace.sipgate.com         | 443  | TCP      |
| Authentication       | login.sipgate.com             | 443  | TCP      |
| Connection control   | socket.clinq.com              | 443  | TCP      |
| Contacts, CRM        | integration.sipgate.com       | 443  | TCP      |
| Event list, settings | 35.208.0.0 - 35.247.255.255   | 443  | TCP      |
| App updates          | s3-eu-central-1.amazonaws.com | 443  | TCP      |

**classic platform**

| Function            | DNS hostname         | IPv4                                                                                                                                                                                                         | Port          | Protocol |
| ------------------- | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------- | -------- |
| SIP signaling (TLS) | –                    | 3.64.29.229, 3.74.37.174, 3.75.1.227, 3.77.130.221, 3.125.165.239, 18.153.199.104, 18.192.192.27, 18.193.158.169, 18.195.254.166, 18.196.255.246, 18.197.212.58, 18.199.119.88, 35.157.146.136, 52.29.34.109 | 443           | TCP      |
| Voice data (SRTP)   | –                    | 3.64.29.229, 3.74.37.174, 3.75.1.227, 3.77.130.221, 3.125.165.239, 18.153.199.104, 18.192.192.27, 18.193.158.169, 18.195.254.166, 18.196.255.246, 18.197.212.58, 18.199.119.88, 35.157.146.136, 52.29.34.109 | 15000 - 20000 | UDP      |
| Call setup          | gateway.v2.clinq.com |                                                                                                                                                                                                              | 443           | TCP      |
| Codec negotiation   | api.q.clinq.com      |                                                                                                                                                                                                              | 443           | TCP      |
| Connection control  | socket.clinq.com     |                                                                                                                                                                                                              | 443           | TCP      |
| Event list          | ws-eu.pusher.com     |                                                                                                                                                                                                              | 443           | TCP      |
| Events, settings    | –                    | 35.208.0.0 - 35.247.255.255                                                                                                                                                                                  | 443           | TCP      |

### satellite app

| Function                                  | DNS hostname                                                    | Port        | Protocol |
| ----------------------------------------- | --------------------------------------------------------------- | ----------- | -------- |
| Authentication                            | login.sipgate.com                                               | 443         | TCP      |
| Authentication                            | api.sipgate.com                                                 | 443         | TCP      |
| Authentication, feedback                  | gateway.v2.clinq.com                                            | 443         | TCP      |
| Contacts, CRM                             | integration.sipgate.cloud                                       | 443         | TCP      |
| satellite backend                         | api.satellite.me                                                | 443         | TCP      |
| How-to videos                             | embed-ssl.wistia.com                                            | 443         | TCP      |
| Observability                             | eum-blue-saas.instana.io                                        | 443         | TCP      |
| Observability                             | crashlytics.com                                                 | 443         | TCP      |
| Account, feature toggles, porting, survey | satellite-29f5c.firebaseio.com                                  | 443         | TCP      |
| Call information                          | satellite-calls-29f5c.europe-west1.firebasedatabase.app         | 443         | TCP      |
| Channel data, presence                    | satellite-channels-29f5c.europe-west1.firebasedatabase.app      | 443         | TCP      |
| Organization data                         | satellite-organisations-29f5c.europe-west1.firebasedatabase.app | 443         | TCP      |
| Tracking                                  | amp.sipgate.de                                                  | 443         | TCP      |
| Tracking                                  | api.mixpanel.com                                                | 443         | TCP      |
| Google SDK                                | \*.googleapis.com                                               | 443         | TCP      |
| Google SDK                                | \*.google.com                                                   | 443         | TCP      |
| Google Push Socket                        | \*.mtalk.google.com                                             | 5228 - 5230 | TCP      |

### sipgate fax printer

| Function             | DNS hostname      | Port | Protocol |
| -------------------- | ----------------- | ---- | -------- |
| Contacts, PDF upload | api.sipgate.com   | 443  | TCP      |
| Authentication       | login.sipgate.com | 443  | TCP      |

### sipgate webphone

| Function | DNS hostname    | Port | Protocol |
| -------- | --------------- | ---- | -------- |
| Contacts | api.sipgate.com | 443  | TCP      |

## General recommendations

* **Disable SIP-ALG (Application Layer Gateway) on your firewall/router.** SIP-ALG modifies SIP packets (e.g., IP and port entries in headers and SDP), typically causing one-way audio issues, phones that do not ring, or failed registrations. sipgate does not require SIP-ALG; see the tables above for all required firewall rules.
* Firewall rules usually only need to be configured for outbound traffic.
* For SIP over UDP, after registration we send keepalive packets every few seconds. If these packets do not arrive and the endpoint does not send keepalive packets itself, it may not be reachable for incoming calls. Switching to TCP may help.
* Static port forwarding to specific endpoints is generally not required and poses a security risk.
* For SIP over TLS and WebSocket, SRTP is required for voice data.
* The SIP protocols supported depend on the product.

## Basic requirements for reliable telephony

Your internet connection should meet the following basic requirements:

| Criterion            | Requirement                                                    |
| -------------------- | -------------------------------------------------------------- |
| Bandwidth            | Approx. 100 kbit/s per simultaneous call (upload and download) |
| Latency (round trip) | Under 250 ms                                                   |

## Revision history <a href="#anderungshistorie" id="anderungshistorie"></a>

{% updates format="full" %}
{% update date="2026-11-12" %}

## Endpoint changed

`gateway.clinq.com` has been replaced by `gateway.v2.clinq.com` (sipgate App classic platform and satellite App). Customers with allow rules for `gateway.clinq.com` should adjust their firewall rules accordingly.
{% endupdate %}

{% update date="2026-11-11" %}

## New recommendation

Added: recommendation to disable SIP-ALG in the firewall/router (SIP-ALG modifies SIP packets and causes one-way audio issues or failed registrations).
{% endupdate %}
{% endupdates %}


---

# 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/alles-fur-den-start-mit-sipgate/nutzung-von-sipgate-mit-einer-firewall.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.
