Follow

thinQ Redundancy Instructions and FAQs

**No action will be need in lcr.thinq.com**
Twilio and Plivio customers will not need to make any changes, please continue sending traffic to wap@thinq.com.
Changing from IP to DNS SRV
In your outbound setup, locate your current configurations with thinQ and update to:
srv.lcr.thinq.com 
 
Changing from IP to DNS A
A DNS A Record is also available if your installation doesn’t support DNS SRV. Just like DNS SRV, the A record is automatically updated by our APIs in the event that a service node in any of our geographies is put into maintenance mode or has an issue.  
 

Installation is identical, swap the IP address for thinQ in your setup with:
a.lcr.thinq.com 

 
After saving this change, the upgrade will immediately take effect. No other action is necessary.
Our goal continues to be optimizing the path of your traffic to ensure delivery, quality, and redundancy. 
 
FAQs 
  1. What are whitelisted IP ranges? 
    192.81.236.0/22
  1. How do I perform a text lookup on the DNS SRV and Smart A (below example is using Google's DNS server 8.8.8.8):

    dig @8.8.8.8 _sip._udp.srv.lcr.thinq.com
    or
    dig @8.8.8.8 a.lcr.thinq.com

As an alternative https://mxtoolbox.com/SRVLookup.aspx can be used to lookup _sip._udp.srv.lcr.thinq.com and https://mxtoolbox.com/DNSLookup.aspx can be used to lookup a.lcr.thinq.com

 

As shared by our CTO, Michael Tindall, in our May webinar, we've expanded the footprint and geo-redundancy of our technology and rolled out additional points of interconnect.
The steps are detailed at this point in the video. After saving this change, the upgrade will immediately take effect. No other action is necessary.
If you have specific questions about your setup. Where can you get help?
Please submit a ticket to support@thinq.com
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk