> For the complete documentation index, see [llms.txt](https://teamhelp.sipgate.co.uk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://teamhelp.sipgate.co.uk/integrations-and-connections/using-sipgate-trunking/firewall-settings-for-sipgate.md).

# Using sipgate with a firewall

IP addresses, ports, and configuration guidance for operating sipgate smoothly in a corporate network.

## Signalling & audio transmission (SIP & RTP) <a href="#signalling-and-audio-transmission-sip-and-rtp" id="signalling-and-audio-transmission-sip-and-rtp"></a>

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

### Signalling UDP (Port 5060)

| Function   | DNS host names                                                             | IP address                                                                                                                                                                                                                                                                     | Port | Protocol |
| ---------- | -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---- | -------- |
| Signalling | 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      |

### Signalling TCP (Port 5060), TLS (Port 5061), WebSocket (Port 443)

| Function   | DNS host names                                     | IP address                                                                                                                                                                                                                                                                                                                                         | Port            | Protocol            |
| ---------- | -------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | ------------------- |
| Signalling | 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 host name | 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 due to expansions of the sipgate platform. Where possible, we recommend using the DNS host names. Otherwise, the IP addresses should be checked against this documentation regularly.
{% endhint %}

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

To use all features of the sipgate Apps, additional services are integrated. **In addition** to the rules from "[Signalling & audio transmission (SIP & RTP)](#signalling-and-audio-transmission-sip-and-rtp)", further firewall rules are required, for example for real-time events, contacts, and app updates.

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

The sipgate App runs on one of two platforms depending on your account: the modern neo platform (NeoPBX) or the older classic platform. Both use different backend infrastructures, so the required rules differ. You can see which platform your account uses in the account menu at the top right after logging in.

**neo platform (NeoPBX)**

| Function             | DNS host name / 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 host name     | IPv4                                                                                                                                                                                                         | Port          | Protocol |
| -------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------- | -------- |
| SIP signalling (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.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      |

### sipgate Webphone

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

## General recommendations

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

## Basic requirements for trouble-free 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) | below 250 ms                                                   |
