[Blink] Blink not connecting SIP account

[Dan Pascu]

On 5 Jan 2017, at 14:49, Lars Noodén wrote:

>>> Which logs and other information are needed to help solve this?
>> 
>> In preferences enable sip trace and notifications trace. Restart
>> blink and send the 2 files (you can send to support at ag-projects.com
>> and mention this issue if the privacy of the traces is important). Do
>> NOT edit the logs to replace IP addresses.
>> 
> 
> Thanks.  I've sent the two logs directly to the other mail address.

According to the logs, their DNS name server seems to be the culprit. Half the time it replies, half the time it times out. I can see Blink did register, but then failed to publish presence or initiate a call.

This excerpt shows the issue (this is just for the SRV records, but I noticed it does the same for every record type: A, NAPTR, TXT):

2017-01-05 14:35:33.924633 [blink 18271]: DNS lookup SRV _sips._tcp.sip2sip.info. failed: no DNS response received, the query has timed out
2017-01-05 14:35:33.932106 [blink 18271]: DNS lookup SRV _sips._tcp.sip2sip.info. failed: no DNS response received, the query has timed out
2017-01-05 14:35:33.971674 [blink 18271]: DNS lookup SRV _sip._tcp.sip2sip.info. succeeded, ttl=3600: 100 100 5060 proxy.sipthor.net.
2017-01-05 14:35:59.060338 [blink 18271]: DNS lookup SRV _sips._tcp.sip2sip.info. failed: no DNS response received, the query has timed out
2017-01-05 14:36:24.174190 [blink 18271]: DNS lookup SRV _sip._tcp.sip2sip.info. succeeded, ttl=3600: 100 100 5060 proxy.sipthor.net.
2017-01-05 14:36:24.185869 [blink 18271]: DNS lookup SRV _sip._tcp.sip2sip.info. succeeded, ttl=3600: 100 100 5060 proxy.sipthor.net.
2017-01-05 14:36:24.266908 [blink 18271]: DNS lookup SRV _sips._tcp.sip2sip.info. succeeded, ttl=3063: 100 100 443 proxy.sipthor.net.

The name server that is used is at 127.0.1.1. Blink has code to detect if a name server is usable or not and if not it will automatically fall back to using the Google name servers at 8.8.8.8 and 8.8.4.4. But if during the probing the name servers happen to work, then the fallback will not happen.

The conclusion is that they have to either fix their DNS resolver, or replace their buggy resolver with the google name servers (8.8.8.8 and 8.8.4.4) in /etc/resolv.conf

--
Dan