You are not logged in.

#1 2017-01-24 16:09:36

resident
Member
Registered: 2007-04-16
Posts: 11

linphone registration

hi,  linphone-3.10.2-3 will not register with my voip provider;
installed ekiga and can register and make phone calls with
my voip provider; not sure if its a linphone bug or one
of its dependencys; any ideas? thanks resident

Offline

#2 2017-01-24 17:25:12

x33a
Forum Fellow
Registered: 2009-08-15
Posts: 4,587

Re: linphone registration

Try launching it with the --verbose switch and see if there are any useful messages.

Offline

#3 2017-01-24 23:48:05

resident
Member
Registered: 2007-04-16
Posts: 11

Re: linphone registration

linephonec -d 6 output:  note: edited DNS addys and voip provider for security reasons
2017-01-24 18:06:39:513 ortp-message-Resolver is using DNS server(s):
2017-01-24 18:06:39:513 ortp-message-    DNS.server.1
2017-01-24 18:06:39:513 ortp-message-    DNS.server.2
2017-01-24 18:06:39:513 ortp-message-    DNS.server.3
2017-01-24 18:06:39:545 ortp-message-No SRV result for [_sip._udp.myvoipprovider.com], trying A/AAAA.
2017-01-24 18:06:39:545 ortp-message-Resolver is using DNS server(s):
2017-01-24 18:06:39:545 ortp-message-    DNS.server.1
2017-01-24 18:06:39:545 ortp-message-    DNS.server.2
2017-01-24 18:06:39:545 ortp-message-    DNS.server.3
2017-01-24 18:06:39:573 ortp-error-channel_res_done: DNS resolution failed for myvoipprovider.com
2017-01-24 18:06:39:573 ortp-message-channel 0x2245b20: state ERROR
2017-01-24 18:06:39:575 ortp-message-Neither Expires header nor corresponding Contact header found, checking from original request

without verbose option:
linphone: 2017-01-24 12:06:08:252 ortp-error-Connection to the pulseaudio server failed Ready Warning:
video is disabled in linphonec, use -V or -C or -D to enable.
linphonec> 2017-01-24 12:06:08:364 ortp-error-channelresdone: DNS resolution failed for myvoipprovider.com
Refreshing on sip:myvoipaddy0@myvoipprovider.com...
linphonec> Registration on sip:myvoipaddy@myvoipprovider.com failed: io error
linphonec> 2017-01-24 12:06:08:938 ortp-error-channelresdone: DNS resolution failed for myvoipprovider.com
Registration on sip:myvoipaddy@myvoipprovider.com failed: io error

Offline

#4 2017-01-25 02:29:50

x33a
Forum Fellow
Registered: 2009-08-15
Posts: 4,587

Re: linphone registration

Well, the logs clearly say that DNS resolution is failing for your voip provider. See if you are able to fetch the records involved (SRV, A, AAAA) manually.

Offline

#5 2017-01-25 15:46:47

resident
Member
Registered: 2007-04-16
Posts: 11

Re: linphone registration

what linux apps to use to get SRV, A, AAAA info?
dig myvoipprovider.com states that A is available thru my ivp4 ISP; no AAAA info may be due to my ISP being ivp4 only but just a guess;
dig -t SRV _sip._udp.myvoipprovider.com indicates that SRV is available for all its servers
;; Got answer: NOERROR, id: 3618
;; OPT PSEUDOSECTION:; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:;_sip._udp.myvoipprovider.com IN SRV
ANSWER SECTION: _sip._udp.myvoipprovider.com 431    IN    SRV    20 0 5080 alpha13.myvoipprovider.com
if ekiga allows calls to my voip provider and linphone does not then the problem is with linphone or ortp and not my voip provider?

Offline

#6 2017-01-25 17:13:15

corruption2013
Member
Registered: 2013-02-26
Posts: 11

Re: linphone registration

Hi, its clearly a linphone problem. I had the same issue about 2 months ago (after a update? dunno exactly). My workaround was quite simple: I just put the ip address instead of the domain into the field "SIP Proxy address" and it works again.

Error with domain instead of ip:

message: 2017-01-25 18:03:43:581 Changing [client] [REGISTER] transaction [0xa3a0d0], from state [INIT] to [TERMINATED]
message: 2017-01-25 18:03:43:581 Client internal REGISTER transaction [0xa3a0d0] terminated
message: 2017-01-25 18:03:44:093 belle_sip_client_transaction_send_request(): waiting channel to be ready
message: 2017-01-25 18:03:44:093 channel [0xc5d800]: starting resolution of tel.t-online.de
message: 2017-01-25 18:03:44:093 channel 0xc5d800: state RES_IN_PROGRESS
message: 2017-01-25 18:03:44:093 transaction [0xc83cb0] channel state changed to [RES_IN_PROGRESS]
message: 2017-01-25 18:03:44:093 Resolver is using DNS server(s):
message: 2017-01-25 18:03:44:093     192.168.137.1
message: 2017-01-25 18:03:44:093 No SRV result for [_sip._udp.tel.t-online.de], trying A/AAAA.
message: 2017-01-25 18:03:44:093 Resolver is using DNS server(s):
message: 2017-01-25 18:03:44:093     192.168.137.1
error: 2017-01-25 18:03:44:093 channel_res_done: DNS resolution failed for tel.t-online.de
message: 2017-01-25 18:03:44:093 channel 0xc5d800: state ERROR
message: 2017-01-25 18:03:44:123 transaction [0xc83cb0] channel state changed to [ERROR]


My /etc/resolv.conf looks fine, and i can reach the domain with the computer running linphone.

If someone have a better solution/workaround instead of putting the ip directly into linphone please let me know.

Last edited by corruption2013 (2017-01-25 17:13:29)

Offline

#7 2017-01-25 17:32:05

eiscreme
Member
Registered: 2016-05-19
Posts: 8

Re: linphone registration

I have the same error and I'm thinking too its a client problem. Android linphpne app works! Don't know if its linphone problem or an OS problem. Suddenly after holiday I couldnt make any calls.

Offline

#8 2017-01-25 19:20:34

captaincurrie
Member
From: /dev/random
Registered: 2013-11-01
Posts: 82

Re: linphone registration

I had the same problem since i upgrades to 3.10 until i read the solution posted by @corruption2013.
It works!!!

Thanks

For those who don't know what to do

if

SIP Proxy Address = <sip:URL;...>

then resolve the URL to its ip address with the following command

dig +short URL | sed 1q

and replace the above field with the output

The dig command can be found in the bind-tools package

EDIT:
Nevermind. When i performed the above linphone asked me
for my password and showed a checkmark to say it had connected,
so i thought it was working...

But then i tried calling someone and i got the same I/O error i was getting
before. Then i looked in the debug window and i'm still get DNS resolution
failure.

Will just have to wait for an update it seems. Until then i'm using Ekiga....:(

Last edited by captaincurrie (2017-01-25 19:31:02)

Offline

#9 2017-01-25 19:57:53

corruption2013
Member
Registered: 2013-02-26
Posts: 11

Re: linphone registration

captaincurrie wrote:

I had the same problem since i upgrades to 3.10 until i read the solution posted by @corruption2013.
It works!!!

Thanks

For those who don't know what to do

if

SIP Proxy Address = <sip:URL;...>

then resolve the URL to its ip address with the following command

dig +short URL | sed 1q

and replace the above field with the output

The dig command can be found in the bind-tools package

EDIT:
Nevermind. When i performed the above linphone asked me
for my password and showed a checkmark to say it had connected,
so i thought it was working...

But then i tried calling someone and i got the same I/O error i was getting
before. Then i looked in the debug window and i'm still get DNS resolution
failure.

Will just have to wait for an update it seems. Until then i'm using Ekiga....:(

For me it works, could be that you have a SIP provider that have more then one server behind the domain name?

Maybe you need a stun server, because you are behind a NAT and you have to replace the stun server domain name to an ip address too? (i dont use a stun server)

I dont know if this is Arch related or an overall problem with linphone. (Cant find a issue tracker for linphone and dont have time to download the source) Maybe we should post this on the linphone mailing list?

Last edited by corruption2013 (2017-01-25 20:00:17)

Offline

#10 2017-01-25 23:48:27

resident
Member
Registered: 2007-04-16
Posts: 11

Re: linphone registration

thanks all; your comments gave me an idea that works;
edit /etc/hosts and add the output of this command to
the file: dig +short myvoipprovider.com | sed '1s/$/ myvoioprovider.com/'
example output: 000.00.000.000 myvoipprovider.com
works for me; linphonec starts ok with this ouput:
linphonec> Registration on sip:myvoipaddy@myvoipprovider.com successful.
i made two calls to test and both worked without a problem; ciao

Offline

#11 2017-01-26 10:11:24

corruption2013
Member
Registered: 2013-02-26
Posts: 11

Re: linphone registration

Its still a linphoneproblem. Lets hope for an update soon.

Offline

#12 2017-01-26 12:33:14

eiscreme
Member
Registered: 2016-05-19
Posts: 8

Re: linphone registration

resident wrote:

thanks all; your comments gave me an idea that works;
edit /etc/hosts and add the output of this command to
the file: dig +short myvoipprovider.com | sed '1s/$/ myvoioprovider.com/'
example output: 000.00.000.000 myvoipprovider.com
works for me; linphonec starts ok with this ouput:
linphonec> Registration on sip:myvoipaddy@myvoipprovider.com successful.
i made two calls to test and both worked without a problem; ciao

works for me too, thanks!

Offline

#13 2017-01-26 13:05:25

piie
Member
Registered: 2007-02-20
Posts: 33

Re: linphone registration

resident wrote:

thanks all; your comments gave me an idea that works;
edit /etc/hosts and add the output of this command to
the file: dig +short myvoipprovider.com | sed '1s/$/ myvoioprovider.com/'
example output: 000.00.000.000 myvoipprovider.com
works for me; linphonec starts ok with this ouput:
linphonec> Registration on sip:myvoipaddy@myvoipprovider.com successful.
i made two calls to test and both worked without a problem; ciao

Thanks, works for me too.

Offline

#14 2017-01-27 17:31:11

x33a
Forum Fellow
Registered: 2009-08-15
Posts: 4,587

Re: linphone registration

If you people want Linphone devs to fix the problem, you have to report it first. A quick search led me to their Github repo, someone might want to report this issue there.

https://github.com/BelledonneCommunicat … ne-desktop

Offline

#15 2017-01-29 09:25:08

captaincurrie
Member
From: /dev/random
Registered: 2013-11-01
Posts: 82

Re: linphone registration

corruption2013 wrote:
captaincurrie wrote:

I had the same problem since i upgrades to 3.10 until i read the solution posted by @corruption2013.
It works!!!

Thanks

For those who don't know what to do

if

SIP Proxy Address = <sip:URL;...>

then resolve the URL to its ip address with the following command

dig +short URL | sed 1q

and replace the above field with the output

The dig command can be found in the bind-tools package

EDIT:
Nevermind. When i performed the above linphone asked me
for my password and showed a checkmark to say it had connected,
so i thought it was working...

But then i tried calling someone and i got the same I/O error i was getting
before. Then i looked in the debug window and i'm still get DNS resolution
failure.

Will just have to wait for an update it seems. Until then i'm using Ekiga....:(

For me it works, could be that you have a SIP provider that have more then one server behind the domain name?

Maybe you need a stun server, because you are behind a NAT and you have to replace the stun server domain name to an ip address too? (i dont use a stun server)

I dont know if this is Arch related or an overall problem with linphone. (Cant find a issue tracker for linphone and dont have time to download the source) Maybe we should post this on the linphone mailing list?

Yes, this is the case. The $(dig +short ....) command returns 7 different addresses. So thats probably why it didn't work.
Thanks for the suggestions.

The idea of @resident works!! I register now and i don't get the I/O error i would previously get when i tried
calling someone. Yay!

Offline

#16 2017-02-08 15:27:47

resident
Member
Registered: 2007-04-16
Posts: 11

Re: linphone registration

is not the job of the arch package maintainer for linphone to compile, package, install
and test the new package before it is committed to the arch repository?

Offline

#17 2017-02-08 17:01:01

x33a
Forum Fellow
Registered: 2009-08-15
Posts: 4,587

Re: linphone registration

resident wrote:

is not the job of the arch package maintainer for linphone to compile, package, install
and test the new package before it is committed to the arch repository?

It is no one's *job*. The package maintainers are volunteers and do this in their free time. I am sure the package compiled fine and only then was it pushed to the repos. Testing each and every package for functionality isn't feasible and that's where the users come in. But since no one seems to want to report the bug, you can either play with workarounds or blame the Arch devs.

Offline

Board footer

Powered by FluxBB