What are the IP and firewall settings for the sipgate app CLINQ?
In most cases, the sipgate app CLINQ will work without additional configuration of routers or firewalls. However, in corporate networks, adjustments may be necessary, and specific domains and ports need to be allowed. Below, we have listed all the gateways and ports required for the sipgate app CLINQ to connect.
Internet connection requirements
- A minimum bandwidth of 100-400 kbit/s download/upload is needed.
- Latency should be below 270 ms to avoid offline notifications in the client and issues with making calls.
Call setup (without audio)
Here’s an overview of the domains, ports, and protocols used by the sipgate app for communication:
- gateway.clinq.com + Port: 443 + TCP (Call setup)
- api.q.clinq.com + Port: 443 + TCP (Negotiate codecs, etc., before accepting a call)
- socket.clinq.com + Port: 443 + TCP (CLINQ Client ↔ Google Server connection)
- Google IP ranges can be found here.
For a typical home router, domains should be allowed by default without extra configuration. In highly restrictive corporate networks, where many domains and IPs are blocked, it may be necessary to work with your network administrator to allow specific domains and ports.
Call accepted with audio
- IP Range + UDP + Port range: 10,000 - 60,000 (Audio)
Fixed IP addresses used:
- 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
- 3.125.165.239
- 3.64.29.229
- 3.74.37.174
- 3.75.1.227
- 3.77.130.221
- 35.157.146.136
- 52.29.34.109
SIP Registration – Device IP Address
When using the sipgate app CLINQ, the IP address of the VoIP device (viewable under “My Telephony” on the web) may differ from the IP address of the desktop running the app. This is because the SIP registration occurs through the app’s backend services, not directly via the desktop client.
Login
- sipgate App Firebase (all logins): 35.208.0.0 - 35.247.255.255
- via Apple: www.apple.com + appleid.apple.com + Port 443 + TLS 1.2
- via Microsoft: live.com + microsoftonline.com + microsoft.com + Port 443 + TLS 1.2
sipgate app Updates
Allow downloads from s3-eu-central-1.amazonaws.com (Amazon AWS).
Voice and Signal Encryption
Signals are encrypted via TLS, while voice encryption is done using SRTP.
Errors and Solutions
| Error | Error Message | Cause | Solution |
|---|---|---|---|
| Login works, but outgoing calls fail / incoming calls cannot be answered. | "Audio connection could not be established, please check network and microphone." | Analysis 1: sipgate App → Help → Log → renderer.log: "Call could not be dialed -> Saving local call event {error: 'Timeout: Could not build a WebRTC connection.'" | Unblock gateway.v2.clinq.com:443 + TLS 1.2 in firewall/filter. |
| Analysis 2: Firewall temporarily blocked api.q.clinq.com + Port 443 and/or Audio IP ranges. | Unblock api-q-clinq.com:433 and the Audio IP ranges (see above for audio). | ||
| Analysis 3: Temporary sipgate App outage. | Wait for a fix from sipgate App support. | ||
| Calls have error code 500 + Nexu 502 error in logs | Report to sipgate App Support and wait for a resolution. | ||
| Login works but error message appears | "You are offline. Please check your internet connection." | Analysis: sipgate App → Help → Logs → renderer.log: "[error] [ws] Socket error Error: websocket error false" | Unblock socket.clinq.com:433 + TLS 1.2 in firewall/filter. |
| Connection via WiFi in train with LTE (80-200 km/h) has +250ms latency. | |||
| Connection with Google failed | "Connection with Google failed." | google.bridge.clinq.com + 433 + TLS 1.2 blocked by firewall/filter. | Unblock google.bridge.clinq.com:433. |
| Connection with Microsoft failed | "Connection with Microsoft failed." | outlook-contacts.bridge.clinq.com + 433 + TLS 1.2 blocked by firewall/filter. | Unblock outlook-contacts-bridge.clinq.com:433. |
| Data could not be saved | "Data could not be saved." | sipgate.bridge.clinq.com + 433 + TLS 1.2 blocked by firewall/filter. | Unblock sipgate.cridge.clinq.com:433. |
| Microsoft Integration opens briefly and closes immediately | microsoft.com and/or microsoftonline.com/live.com blocked by firewall. | Unblock microsoft.com, microsoftonline.com, live.com. | |
| Update could not be installed | "Update could not be installed." | s3-eu-central-1.amazonaws.com + 433 + TLS 1.2 blocked by firewall/filter. | Unblock s3-eu-central-1.amazonaws.com. |
| CLINQ.AppImage is in a system folder without write permissions. | Move CLINQ.AppImage to Downloads, update should now work. | ||
| CLINQ.dmg / CLINQ.exe was installed from NAS/Network drive. | Uninstall the sipgate App, copy sipgateApp.dmg/exe from the network drive to the local hard drive, reinstall, and update. | ||
| Outgoing calls not possible | "Call could not be started. Please check your network connection." | Analysis: sipgate App Log: renderer.log: "[api] Could not create call event" | Unblock gateway.v2.clinq.com:433 + TLS 1.2 in firewall/filter. |
| Analysis: sipgate App → Logs → renderer.log: "[error] [ws] Socket disconnected transport close (https://socket.clinq.com)" | Restart the sipgate App or press CMD+R/CTRL+R, or go to sipgate App → View → "Reload". | ||
| Network change or sleep mode prevents reconnect. | End and restart the app, or press CMD+R/CTRL+R to reconnect. | ||
| Incorrect internet proxy configuration. | Disable the proxy and test the connection, then adjust proxy settings. | ||
| VPN blocking transmission. | Test without VPN, if VPN is the issue, inform the VPN admin. | ||
| Docker with various network connections set up incorrectly. | Test connection without virtual Docker network adapters, then review Docker settings. | ||
| Software firewall blocks sipgate App CLINQ | "[error] [call] Could not build a WebRTC connection in 10s. Error: Could not get microphone stream." | Analysis: sipgate App → Help → Logs → renderer.log: (Firewall blocking connection) | Add sipgate App CLINQ to trusted apps in the software firewall. |