linphone-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Linphone-users] Linphone SIP registration stopped working - DNS pro


From: Russell Treleaven
Subject: Re: [Linphone-users] Linphone SIP registration stopped working - DNS problem (or not)
Date: Mon, 30 Jan 2017 10:48:42 -0500

man hosts

On Mon, Jan 30, 2017 at 8:00 AM, sebalis <address@hidden> wrote:
Hi,

My existing and regularly used Linphone instance stopped working recently. The log messages say that server DNS resolution fails. Other SIP clients debug a similar configuration are still working. Any idea what I could do?

Something really strange is that I can't detect any network traffic coming from Linphone between starting a fresh process, seeing that it won't connect, copying the contents of the debug window to the clipboard, and ending the process. This throws the debug messages in doubt I would say. There is no local firewall that would prevent Linphone from accessing the network (I have UFW installed but it’s disabled).

Here are some extracts from my .linphonerc and the debug window. I have an account with well-known German provider sipgate and have configured Linphone to use STUN via stun.sipgate.net:10000. I don’t know if this is relevant but I am on Arch Linux and my system is fully updated.

.linphonerc extracts: (some strings changed to ___, some comments in brackets)
[sip]
root_ca=/etc/ssl/certs
verify_server_certs=1
verify_server_cn=1
media_encryption=none
default_proxy=0
multi_transport_migration_done=1
guess_hostname=1
inc_timeout=30
in_call_timeout=0
delayed_timeout=4
use_ipv6=0
register_only_when_network_is_up=1
register_only_when_upnp_is_ok=1
contact="" <sip:address@hidden:5060>
[...]
[net]
download_bw=0
upload_bw=0
adaptive_rate_control=1
mtu=1300
stun_server=stun.sipgate.net:10000
nat_policy_ref=___ (matches ref in nat_policy_0)
[...]
[proxy_0]
reg_proxy=sip:sipgate.de
reg_identity=sip:address@hiddene
quality_reporting_enabled=0
quality_reporting_interval=0
reg_expires=60
reg_sendregister=1
publish=0
avpf=0
avpf_rr_interval=5
dial_escape_plus=0
privacy=32768
publish_expires=60
[...]
[nat_policy_0]
ref=___
stun_server=stun.sipgate.net:10000
protocols=stun
[...]
[auth_info_2]
username=___ (matches userid)
userid=___
ha1=___
realm=sipgate.de
domain=sipgate.de

Messages that look like potential problems from the debug window: (10.1.0.1 is my router)
message: 2017-01-30 13:17:20:460 Resolver is using DNS server(s):
message: 2017-01-30 13:17:20:460        10.1.0.1
message: 2017-01-30 13:17:20:460 No SRV result for [_stun._udp.stun.sipgate.net], trying A/AAAA.
message: 2017-01-30 13:17:20:460 Resolver is using DNS server(s):
message: 2017-01-30 13:17:20:460        10.1.0.1
warning: 2017-01-30 13:17:20:460 Stun server resolution failed.
message: 2017-01-30 13:17:20:460 MTU is supposed to be 1300, rtp payload max size will be 1240

Testing DNS resolution for this first problem:
$ dig @10.1.0.1 _stun._udp.stun.sipgate.net srv

; <<>> DiG 9.11.0-P2 <<>> @10.1.0.1 _stun._udp.stun.sipgate.net srv
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 35818
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;_stun._udp.stun.sipgate.net.   IN      SRV

;; AUTHORITY SECTION:
sipgate.net.            3600    IN      SOA     ns1.netzquadrat.de. dnsadmin.netzquadrat.de. 2017010200 10800 3600 604800 86400

;; Query time: 98 msec
;; SERVER: 10.1.0.1#53(10.1.0.1)
;; WHEN: Mon Jan 30 13:27:32 CET 2017
;; MSG SIZE  rcvd: 119


Back to the debug window:
message: 2017-01-30 13:17:20:460 Could not find encoder for SILK
(Several messages like this one follow)
[...]
message: 2017-01-30 13:17:20:594 New local ip address is 10.1.0.100
message: 2017-01-30 13:17:20:594 SIP network reachability state is now [UP]
message: 2017-01-30 13:17:20:594 Resolver is using DNS server(s):
message: 2017-01-30 13:17:20:594        10.1.0.1
message: 2017-01-30 13:17:20:594 No SRV result for [_stun._udp.stun.sipgate.net], trying A/AAAA.
message: 2017-01-30 13:17:20:594 Resolver is using DNS server(s):
message: 2017-01-30 13:17:20:595        10.1.0.1
warning: 2017-01-30 13:17:20:595 Stun server resolution failed.
message: 2017-01-30 13:17:20:595 Media network reachability state is now [UP]
message: 2017-01-30 13:17:20:595 LinphoneProxyConfig [0x265c430] about to register (LinphoneCore version: 3.10.2)
message: 2017-01-30 13:17:20:597 belle_sip_client_transaction_send_request(): waiting channel to be ready
message: 2017-01-30 13:17:20:597 channel [0x27645d0]: starting resolution of sipgate.de
message: 2017-01-30 13:17:20:597 channel 0x27645d0: state RES_IN_PROGRESS
message: 2017-01-30 13:17:20:597 transaction [0x275b960] channel state changed to [RES_IN_PROGRESS]
message: 2017-01-30 13:17:20:597 Resolver is using DNS server(s):
message: 2017-01-30 13:17:20:597        10.1.0.1
message: 2017-01-30 13:17:20:597 No SRV result for [_sip._udp.sipgate.de], trying A/AAAA.
message: 2017-01-30 13:17:20:597 Resolver is using DNS server(s):
message: 2017-01-30 13:17:20:597        10.1.0.1
error: 2017-01-30 13:17:20:597 channel_res_done: DNS resolution failed for sipgate.de
message: 2017-01-30 13:17:20:597 channel 0x27645d0: state ERROR
message: 2017-01-30 13:17:20:597 Neither Expires header nor corresponding Contact header found, checking from original request
message: 2017-01-30 13:17:20:598 Refresher [0x27628c0] takes ownership of transaction [0x275b960]
message: 2017-01-30 13:17:20:598 Proxy config [0x265c430] for identity [sip:address@hidden] moving from state [LinphoneRegistrationNone] to [LinphoneRegistrationProgress] on core [0x2605960]
message: 2017-01-30 13:17:20:600 Linphone core [0x2605960] notifying [registration_state_changed]
message: 2017-01-30 13:17:20:600 LinphoneProxyConfig [0x26b1680] about to register (LinphoneCore version: 3.10.2)
message: 2017-01-30 13:17:20:602 belle_sip_client_transaction_send_request(): waiting channel to be ready

This section contains the DNS error about my STUN server sipgate.net a second time, and another such error about my SIP account itself at sipgate.de – testing that one too:

$ dig @10.1.0.1 _stun._udp.sipgate.de srv

; <<>> DiG 9.11.0-P2 <<>> @10.1.0.1 _stun._udp.sipgate.de srv
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3293
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;_stun._udp.sipgate.de.         IN      SRV

;; ANSWER SECTION:
_stun._udp.sipgate.de.  28794   IN      SRV     0 0 3478 stun.sipgate.net.

;; Query time: 67 msec
;; SERVER: 10.1.0.1#53(10.1.0.1)
;; WHEN: Mon Jan 30 13:32:17 CET 2017
;; MSG SIZE  rcvd: 86

This is followed by similar messages regarding two other SIP accounts that I use. And as I said, this used to work in Linphone until some time in December or early January.

Thanks for any help you can give.

sebalis

_______________________________________________
Linphone-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/linphone-users



--
Sincerely,

Russell Treleaven


reply via email to

[Prev in Thread] Current Thread [Next in Thread]