# What are the IP and port ranges of sipgate? ## sipgate.de {% tabs %} {% tab title="IPv4" %} **Signaling:** * IP: `217.10.79.9` * Port: `5060` * Protocol: UDP **RTP:** * IP: `212.9.44.0/24` and `217.10.77.0/24` * Port range: `15000 - 30000` * Protocol: UDP {% endtab %} {% tab title="IPv6" %} **Signaling:** * `[2001:ab7::1]`, `[2001:ab7::2]`, `[2001:ab7::3]`, `[2001:ab7::4]` * Port `5060` * Protocol: UDP **RTP:** * IP range: `[2001:ab7:2000:3::0/64]` * Port range: `15000 - 30000` * Protocol: UDP {% endtab %} {% endtabs %} ## sip.sipgate.de Protocol: **TCP**, **TLS** {% tabs %} {% tab title="IPv4" %} **Signaling** * IP: `212.9.44.242`, `212.9.44.244`, `217.10.77.242`, `217.10.77.244` * Port: `5060/TCP`, `5061/TLS`, `443/WSS` * Protocol: TCP, TLS, WSS **RTP:** * IP range: `212.9.44.0/24` and `217.10.77.0/24` * Port range: `15000 - 30000` * Protocol: UDP {% endtab %} {% tab title="IPv6" %} **Signaling:** * IP: `[2001:ab7::17]`, `[2001:ab7::18]`, `[2001:ab7::19]`, `[2001:ab7::1a]` * Port: `5060/TCP`, `5061/TLS`, `443/WSS` * Protocol: TCP, TLS, WSS **RTP:** * IP range: `[2001:ab7:2000:3::0/64]` * Port range: `15000 - 30000` * Protocol: UDP {% endtab %} {% endtabs %} ## sipconnect.sipgate.de Protocol: **UDP** {% tabs %} {% tab title="IPv4" %} **Signaling** * IP: `217.10.68.150` * Port: `5060` * Protocol: UDP **RTP:** * IP: `212.9.44.0/24` and `217.10.77.0/24` * Port range: `15000 - 30000` * Protocol: UDP {% endtab %} {% tab title="IPv6" %} **Signaling:** * IP: `[2001:ab7::9]`, `[2001:ab7::10]`, `[2001:ab7::11]`, `[2001:ab7::12]` * Port: `5060` * Protocol: UDP **RTP:** * IP: `[2001:ab7:2000:3::0/64]` * Port range: `15000 - 30000` * Protocol: UDP {% endtab %} {% endtabs %} {% hint style="info" %} Note: IP addresses and port ranges may change due to expansions on our platform. {% endhint %} The IP address ranges used by sipgate are: {% tabs %} {% tab title="IPv4" %} * `217.10.64.0/20` * `217.116.112.0/20` * `212.9.32.0/19` {% endtab %} {% tab title="IPv6" %} * `2001:ab0::/29` {% endtab %} {% endtabs %} Further information on the IP and firewall settings for the sipgate app can be found in the following article: [What are the IP and firewall settings for the sipgate app?](https://help.sipgate.de/hc/de/articles/12150947366173-Was-sind-die-IP-und-Firewalleinstellungen-f%C3%BCr-die-sipgate-App) *** ## Firewall configurations ### sipgate.de via UDP + Sophos Firewall {% stepper %} {% step %} **Disable SIP Helper** The Sophos Firewall has a SIP module, the so-called SIP Helper. In exceptional cases, however, using this module can lead to disruptions. In such cases, it makes sense to disable the SIP Helper. How to disable the SIP Helper in SFOS: 1. Connect to the firewall via SSH 2. Select the option **4. Device Console** from 3. Display the status of the SIP module: ``` system system_modules show ``` 4. Disable the SIP module: ``` system system_modules sip unload ``` 5. If necessary, you can then re-enable the SIP module: ``` system system_modules sip load ``` {% hint style="info" %} After disabling the SIP Helper, the VoIP firewall rules must be configured correctly so that communication works smoothly. {% endhint %} {% endstep %} {% step %} **Increase UDP session timeout** A common reason for VoIP problems with the Sophos Firewall is a UDP timeout that is set too short. For smooth data transmission with sipgate, you need a longer timeout duration so that connections are not terminated prematurely. How to adjust the UDP timeout in SFOS: 1. Connect to the firewall via SSH 2. Option **4. Device Console** select 3. Display current value: ``` show advanced-firewall ``` 4. Set timeout value (e.g. 180 seconds): ``` set advanced-firewall udp-timeout-stream 180 ``` {% hint style="info" %} We recommend values between 30 and 3600 seconds. {% endhint %} {% endstep %} {% step %} **Create dedicated firewall rule for VoIP** A separate firewall rule for VoIP traffic provides more control and better troubleshooting. A possible configuration can look like this: * **Source zone:** LAN * **Source network:** VoIP end devices (e.g. IP phones or telephone system) * **Destination zone:** WAN * **Destination network:** IP addresses or hostnames of the VoIP provider * **Services:** SIP (port 5060), RTP (e.g. ports 10000–20000) The rule should be placed as high as possible in the policy order and have logging enabled. {% endstep %} {% step %} **Enable Quality of Service (QoS) for VoIP** To ensure that VoIP packets are not delayed even under high network load, prioritization via traffic/packet shaping is recommended. How to set up QoS for VoIP on the Sophos Firewall: 1. Go to **System Services** → **Traffic Shaping** 2. Create a new policy 3. Policy settings: * **Policy type:** Guarantee * **Priority:** High * **Bandwidth usage:** Real-Time * **Guaranteed bandwidth:** depending on codec and number of simultaneous calls 4. Assign traffic shaping policy to the VoIP firewall rule {% endstep %} {% step %} **Monitoring & troubleshooting** After configuration, it is recommended to monitor the voice connections and packet flows: * Firewall logs (Log Viewer → Firewall) * Live view (Diagnostics → Packet Capture) * SNMP monitoring can be used to monitor quality and latency. {% endstep %} {% endstepper %} ### sipgate.de via UDP + SecurePoint Firewall In connection with the SecurePoint Firewall, the SIP Helper sometimes leads to undesirable behavior such as connection drops or one-way audio transmission. Disabling the SIP Helper can help here. The manufacturer provides the following information on this: [UTM/FAQ-VoIP](https://wiki.securepoint.de/UTM/FAQ-VoIP#VoIP_ohne_SIP_Helper) ### sipgate.de via UDP + Mikrotik Firewall Sometimes the SIP Helper/ALG causes undesirable behavior such as dropped connections or one-way audio transmission. Disabling the SIP Helper/ALG can help here. **via terminal:** ``` ip firewall service-port disable sip ``` **via web:** IP → Firewall → Service ports: disable SIP Then restart the firewall and VoIP apps/phones. Further information can be found on the website of [Mikrotik](https://mikrotik-blog.com/disable-sip-alg-sip-alg-deaktivieren-sip-helper-mikrotik). ### sipgate.de via UDP + FortiGate Firewall Sometimes the SIP Helper/ALG causes undesirable behavior such as dropped connections or one-way audio transmission. Disabling the SIP Helper/ALG can help here. Instructions from the manufacturer can be found here: [Disabling VoIP Inspection](https://community.fortinet.com/t5/FortiGate/Technical-Tip-Disabling-VoIP-Inspection/ta-p/194131) ### sipgate.de via UDP + Lancom Firewall Sometimes the SIP Helper/ALG causes undesirable behavior such as dropped connections or one-way audio transmission. Disabling the SIP Helper/ALG can help here. In LANconfig under **Other services** → **Services** → **SIP Application Layer Gateway: disable** (disabled by default) * Notes on SIP ALG: [SIP Application Layer Gateway (SIP-ALG)](https://www.lancom-systems.de/docs/LCOS/Refmanual/DE/topics/voip_sip-alg.html) * Disable SIP ALG: [Configuration](https://www.lancom-systems.de/docs/LCOS/Refmanual/DE/topics/voip_sip-alg_configuration.html) ### sipgate.de via UDP + TP-Link Firewall Sometimes the SIP Helper/ALG causes undesirable behavior such as dropped connections or one-way audio transmission. Disabling the SIP Helper/ALG can help here. In the Deco app, go to More → Advanced → NAT Forwarding → SIP ALG to disable this option. Images / manufacturer instructions: [How do I disable SIP-ALG on my Decos?](https://www.tp-link.com/de/support/faq/2422/) ### sipgate.de via UDP + Netgear Firewall Sometimes the SIP Helper/ALG causes undesirable behavior such as dropped connections or one-way audio transmission. Disabling the SIP Helper/ALG can help here. 1. Click on the "Advanced" tab. 2. Click "Configure". 3. Then click "WAN Configuration". 4. Then check the box for "Disable SIP ALG". {% hint style="info" %} Please note that this setting only exists from firmware 1.0.0.50 onwards. {% endhint %} ### sipgate.de via UDP + Huawei Firewall Sometimes the SIP Helper/ALG causes undesirable behavior such as dropped connections or one-way audio transmission. Disabling the SIP Helper/ALG can help here. Click on "Security" and then under the sub-item "SIP ALG settings" → disable SIP ALG. ### sipgate.de via UDP + Vodafone GigaCube Firewall Sometimes the SIP Helper/ALG causes undesirable behavior such as dropped connections or one-way audio transmission. Disabling the SIP Helper/ALG can help here. Go to "Security" and then disable SIP ALG under the item "SIP ALG settings" → SIP ALG. *** ## Errors and solutions
sipgate app error: "The action is not possible. You are offline. Check your internet connection" **Analysis:** sipgate app → Help → Export logs → renderer.log ``` [error] [contacts] Error starting streaming: undefined ``` **Cause 1:** There is no internet connection **Solution 1:** Check internet connection **Cause 2:** Internet connection works, Google IP range blocked outbound via firewall rule software / hardware firewall **Solution 2:** Check local firewall rules software firewall: "Windows Defender" or hardware firewall: router and allow Google IP range
sipgate app error: Call accepted, but no audio on either side **Analysis:** ``` [2025-08-25 16:09:10.140] [info] [call] Inbound Audio Level Report: [2025-08-25 16:09:10.141] [info] [call] { 'No Audio': '123.394s (100%)', ``` **Cause IPv4 internet:** Firewall IPv4 `212.9.44.0/24` and `217.10.77.0/24` blocks **Solution IPv4 internet:** Firewall IPv4 `212.9.44.0/24` and `217.10.77.0/24` allow **Cause IPv6 internet:** Firewall IPv6 `2001:ab7:2000:3::0/64` blocks **Solution IPv6 internet:** Firewall IPv6 `2001:ab7:2000:3::0/64` allow
sipgate app error: Status offline and outgoing calls do not work **Analysis:** sipgate.de → Help → Export logs: renderer.log ``` [2025-08-25 15:48:26.109] [info] [call] [sip.UserAgent] Reconnection attempt 1 of 4 - failed [2025-08-25 15:48:26.110] [info] [call] [sip.UserAgent] Reconnection attempt 2 of 4 - trying [2025-08-25 15:48:33.111] [error] [call] [sip.UserAgent] WebSocket closed wss://sip.sipgate.de (code: 1006) [2025-08-25 15:48:33.112] [info] [call] [sip.UserAgent] Reconnection attempt 2 of 4 - failed [2025-08-25 15:48:33.112] [info] [call] [sip.UserAgent] Reconnection attempt 3 of 4 - trying ``` **Cause IPv4 internet:** `212.9.44.242`, `212.9.44.244`, `217.10.77.242`, `217.10.77.244` blocks **Solution IPv4 internet:** `212.9.44.242`, `212.9.44.244`, `217.10.77.242`, `217.10.77.244` allow **Cause IPv6 internet:** `[2001:ab7::17]`, `[2001:ab7::18]`, `[2001:ab7::19]`, `[2001:ab7::1a]` blocks **Solution IPv6 internet:** `[2001:ab7::17]`, `[2001:ab7::18]`, `[2001:ab7::19]`, `[2001:ab7::1a]` allow
--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://help.sipgate.de/trunking/en/was-sind-die-ip-und-port-bereiche-von-sipgate.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.