Sometimes your IP and firewall settings prevent CLINQ from operating properly. The solution can be a few, quick adjustments to these settings. We strongly recommend checking to make sure that the minimum technical requirements to use CLINQ are met before making any changes to your IP or firewall settings:
- a bandwidth of at least 100-400kbit/s which is required for download/upload.
- response time must be a minimum 270ms. Anything less than 270ms will result in being offline in the client and not being able to make calls.
Important: we only recommend making changes to your IP and firewall settings together with your IT professional.
There are URL, port, and TLS setting specifications for telephony, contacts, login, and software updates.
Telephony:
- gateway.v2.clinq.com + Port: 443 + TLS 1.2 (call setup)
- api.q.clinq.com + Port 443 + TLS 1.2 (call language)
- socket.clinq.com + Port 443 + TLS 1.2 (CLINQ client<->CLINQ server connection)
- turn.q.clinq.com (34.159.189.255) + 443 + TLS 1.2 (NAT detection)
- stun.sipgate.net + 3478 + TLS 1.2 (NAT detection)
Telephony - call accepted with audio:
// Google Cloud can expand the IPs they use at any time, therefore this information is only based upon the current situation:
- IP Range + TCP + Port range - 10.000 - 60.000 (Audio)
- IP Range: 34.64.0.0 - 34.127.255.255 (34.64.0.0/10)
- IP Range: 34.128.0.0 - 34.191.255.255 (34.128.0.0/10)
- IP Range: 35.192.0.0 - 35.207.255.255 (35.192.0.0/12)
- IP Range: 35.208.0.0 - 35.247.255.255 (35.240.0.0/13, 35.224.0.0/12, 35.208.0.0/12)
- IP Range: 3.0.0.0 - 3.127.255.255 oder 3.0.0.0/9 (Amazon Cloud)
- IP Range:18.32.0.0 - 18.255.255.255 oder 18.128.0.0/9, 18.32.0.0/11, 18.64.0.0/10 (Amazon Cloud)
SIP registration: possible IP ranges:
// Amazon AWS can expand the IPs they use at any time, therefore this information is only based upon the current situation:
- 3.0.0.0 - 3.127.255.255 oder 3.0.0.0/9 (Amazon Cloud)
- 18.32.0.0 - 18.255.255.255 oder 18.128.0.0/9, 18.32.0.0/11, 18.64.0.0/10 (Amazon Cloud)
- 35.152.0.0 - 35.183.255.255 oder 35.160.0.0/12,35.176.0.0/13, 35.152.0.0/13 (Amazon Cloud)
- 52.0.0.0 - 52.79.255.255 oder 52.64.0.0/12, 52.0.0.0/10 (Amazon Cloud)
- 54.64.0.0 - 54.95.255.255 oder 54.64.0.0/11 (Amazon Cloud)
Contacts:
Google:
- google.bridge.clinq.com +Port 443 + TLS 1.2
Microsoft:
- outlook-contacts.bridge.clinq.com + Port 443 + TLS 1.2
- live.com + Port 443 + TLS 1.2
- microsoftonline.com + Port 443 + TLS 1.2
- microsoft.com + Port 443 + TLS 1.2
sipgate:
- sipgate.bridge.clinq.com + Port 443 + TLS 1.2
CRM Examples:
- ActiveCampaign: activecampaign.bridge.clin q.com + Port 443 + TCP/TLS 1.2
- copper: copper.bridge.clinq.com + Port 443 + TCP/TLS 1.2
- Hubspot: hubspot.integration.clinq.com + Port 443 + TCP/TLS 1.2
- moco: moco.bridge.clinq.com + Port 443 + TCP/TLS 1.2
- salesforce: salesforce.bridge.clinq.com + Port 443 + TCP/TLS 1.2
- weclapp: weclapp.integration.clinq.com + Port 443 + TCP/TLS 1.2
Login:
Apple:
- www.apple.com + appleid.apple.com + Port 443 + TLS 1.2
Microsoft:
- live.com + microsoftonline.com + microsoft.com + Port 443 + TLS 1.2
CLINQ software updates:
- s3-eu-central-1.amazonaws.com + Port 443 + TLS 1.2
Click the arrow below to reveal common error codes and their possible causes / solutions:
Error: login successful, outgoing calls are dropped, incoming calls cannot be answered
IDeveloper tools -> Console:
- Could not dial y3 {message: 'Network Error', name: 'AxiosError', code: 'ERR_NETWORK', config: {…}
PUT https://gateway.v2.clinq.com/call net::ERR_SSL_PROTOCOL_ERROR
Cause: gateway.v2.clinq.com:443 + TLS 1.2 blocked via Firewall / Filter
Solution: allow gateway.v2.clinq.com:443
Error: login successful, outgoing calls are dropped, incoming calls cannot be answered
Developer tools -> Console:
- POST https://api.q.clinq.com/peer net::ERR_SSL_PROTOCOL_ERROR
- Could not dial Error: Request timed out
Cause: api.q.clinq.com + Port 443 + TLS 1.2 blocked via Firewall / Filter
Solution: allow api.q.clinq.com:443
Error: login successful, outgoing calls are dropped, incoming calls cannot be answered
Developer tools -> Console:
- Connection error Error: websocket error
Cause: socket.clinq.com + 443 + TLS 1.2 blocked via Firewall / Filter
Solution: allow socket.clinq.com:443
Error: "Failed to connect with Google"
Cause: google.bridge.clinq.com + 443 + TLS 1.2 blocked via Firewall / Filter
Solution: allow google.bridge.clinq.com:443
Error: "Failed to connect with Microsoft"
Cause: outlook-contacts.bridge.clinq.com + 443 + TLS 1.2 blocked via Firewall / Filter
Solution: allowoutlook-contacts.bridge.clinq.com:443
Error: "Data could not be saved."
Cause: sipgate.bridge.clinq.com + 443 + TLS 1.2 blocked via Firewall / Filter
Solution: allow sipgate.bridge.clinq.com:443
Error: Integration -> Microsoft opens for 1 second and the windows closes again immediately
Cause: microsoft.com und/oder microsoftonline.com / live.com blocked via Firewall
Solution: allow microsoft.com , microsoftonline.com , live.com
Error: "Update could not be installed"
Cause 1: s3-eu-central-1.amazonaws.com + 443 + TLS 1.2 blocked via Firewall / Filter
Solution 1: allow s3-eu-central-1.amazonaws.com
Cause 2: CLINQ.AppImage was installed into a system folder without writing / editing rights
Solution 2: move CLINQ.AppImage from Home -> Downloads and try updating again
Cause 3: CLINQ.dmg / CLINQ.exe was installed from a NAS/Network drive
Solution 3:
- uninstall CLINQ.
- copy CLINQ.dmg/exe from the network drive to own hard disk, install, and start.
- the update should now be installed. If not, try updating again.