Arch Linux

I meant "linphone version" and not "sipgate version"...

since a few weeks I have the same errorie IO error .
I cannot use anymore my archlinux linphone with my VOIP provider (freephonie.fr).
A few weeks ago my freephonie account worked well and is still working well on the android version and the Mac OS X version.
When I look the traces on the debug window the archlinux Linphone version has the following error:

message: 2017-01-30 16:13:30:203 New local ip address is 192.168.10.112
message: 2017-01-30 16:13:30:203 SIP network reachability state is now [UP]
message: 2017-01-30 16:13:30:203 Media network reachability state is now [UP]
message: 2017-01-30 16:14:12:732 Cannot parse a sip/sips uri as a generic uri
error: 2017-01-30 16:14:12:732 header_address parser error for [sip:;transport=udp]
message: 2017-01-30 16:14:12:733 Publish params have changed on proxy config [0x2061800]
message: 2017-01-30 16:14:12:746 LinphoneProxyConfig [0x2061800] about to register (LinphoneCore version: 3.10.2)
message: 2017-01-30 16:14:12:753 belle_sip_client_transaction_send_request(): waiting channel to be ready
message: 2017-01-30 16:14:12:753 channel [0x2066490]: starting resolution of freephonie.net
message: 2017-01-30 16:14:12:753 channel 0x2066490: state RES_IN_PROGRESS
message: 2017-01-30 16:14:12:753 transaction [0x20adcd0] channel state changed to [RES_IN_PROGRESS]
message: 2017-01-30 16:14:12:753 Resolver is using DNS server(s):
message: 2017-01-30 16:14:12:753 194.239.134.83
message: 2017-01-30 16:14:12:753 193.162.153.164
message: 2017-01-30 16:14:12:754 No SRV result for [_sip._udp.freephonie.net], trying A/AAAA.
message: 2017-01-30 16:14:12:754 Resolver is using DNS server(s):
message: 2017-01-30 16:14:12:754 194.239.134.83
message: 2017-01-30 16:14:12:754 193.162.153.164
error: 2017-01-30 16:14:12:754 channel_res_done: DNS resolution failed for freephonie.net
message: 2017-01-30 16:14:12:754 channel 0x2066490: state ERROR


If I look on the MacBookPro debug log I have more or less the same log before the error and between the two error line:
message: 2017-01-30 16:06:12:258 New local ip address is 192.168.10.114
message: 2017-01-30 16:06:12:258 SIP network reachability state is now [UP]
message: 2017-01-30 16:06:12:258 Media network reachability state is now [UP]
message: 2017-01-30 16:06:12:259 LinphoneProxyConfig [0x7fa6b8a08780] about to register (LinphoneCore version: 3.10.2)
message: 2017-01-30 16:06:12:261 belle_sip_client_transaction_send_request(): waiting channel to be ready
message: 2017-01-30 16:06:12:261 Activity started
message: 2017-01-30 16:06:12:261 channel [0x7fa6b69a3c00]: starting send background task with id=[1].
message: 2017-01-30 16:06:12:261 channel [0x7fa6b69a3c00]: starting resolution of freephonie.net
message: 2017-01-30 16:06:12:261 channel 0x7fa6b69a3c00: state RES_IN_PROGRESS
message: 2017-01-30 16:06:12:261 transaction [0x7fa6b883dda0] channel state changed to [RES_IN_PROGRESS]
message: 2017-01-30 16:06:12:261 Resolver is using DNS server(s):
message: 2017-01-30 16:06:12:261 194.239.134.83
message: 2017-01-30 16:06:12:261 193.162.153.164
message: 2017-01-30 16:06:12:270 resolver_process_data dns_res_check() in progress
message: 2017-01-30 16:06:12:270 DNS resolution awaiting response, queued to main loop
message: 2017-01-30 16:06:12:270 Neither Expires header nor corresponding Contact header found, checking from original request
message: 2017-01-30 16:06:12:270 Refresher [0x7fa6b89ba390] takes ownership of transaction [0x7fa6b883dda0]
message: 2017-01-30 16:06:12:270 Proxy config [0x7fa6b8a08780] for identity [sip:0950053347@freephonie.net] moving from state [LinphoneRegistrationNone] to [LinphoneRegistrationProgress] on core [0x7fa6b6880c00]
message: 2017-01-30 16:06:12:272 Linphone core [0x7fa6b6880c00] notifying [registration_state_changed]
message: 2017-01-30 16:06:12:289 resolver_process_data dns_res_check() in progress
message: 2017-01-30 16:06:12:320 No SRV result for [_sip._udp.freephonie.net], trying A/AAAA.
message: 2017-01-30 16:06:12:320 Resolver is using DNS server(s):
message: 2017-01-30 16:06:12:320 194.239.134.83
message: 2017-01-30 16:06:12:320 193.162.153.164
message: 2017-01-30 16:06:12:330 resolver_process_data dns_res_check() in progress
message: 2017-01-30 16:06:12:330 DNS resolution awaiting response, queued to main loop
message: 2017-01-30 16:06:12:350 freephonie.net resolved to 212.27.52.5
message: 2017-01-30 16:06:12:350 channel 0x7fa6b69a3c00: state RES_DONE

So it's seems there is a problem in the DNS resolution.

Can it be result of recent /etc/nsswitch.conf changes in filesystem package?

Please try to revert nsswitch.conf to this one for example:
https://git.archlinux.org/svntogit/packages.git/tree/trunk/nsswitch.conf?h=packages/filesystem&id=ec288b55787dce3d2d18eb10ace1941e71cd526e

Reverting /etc/nsswitch.conf to the linked one doesn't help

I have the same error messages telling me that there are DNS resolution problems.
I've replaced Linphone in the meantime. I need SIP calling on my laptop. I sometimes have to attend phone conferences remotely and this is far too expensive and unegonomic with a cell phone.
But as I would really prefer to switch back to Linphone it would be great if some fix could be found...

Workaround:
Summarised on Github at https://github.com/BelledonneCommunications/linphone-desktop/issues/13#issuecomment-277682411
Details for sipgate at http://lists.nongnu.org/archive/html/linphone-users/2017-01/msg00045.html

The entry for stun.sipgate.net depends on whether you have configured to use sipgate’s STUN server, and with which hostname.

Disable the systemd-resolver seems to work for me. Change the hosts: line of /etc/nsswitch.conf to following one:

hosts: files mymachines dns

or

hosts: files dns

The clue is to remove "resolve" keyword, which is related to systemd-resolver, from it.

As I wrote on linphone-users (link in my previous comment), I was able to resolve the SRV records using dig on the command line. So the statement that resolved is buggy seems a bit too general to me.

Seems, that linphone tries to resolve the name in some special manner... Anyway, this "special manner" seems to work with standard dns-resolvers and not to work with systemd- one.

what about 3.11.1? does it still fail?

no more IO error here with the 3.11.1-1 version.
Many thanks.