From: maxim.cournoyer@gmail.com
To: Ben Sturmfels <ben@sturm.com.au>
Cc: 41483@debbugs.gnu.org
Subject: bug#41483: Linphone won't connect to SIP account
Date: Tue, 18 Aug 2020 00:52:30 -0400 [thread overview]
Message-ID: <87r1s4pnch.fsf@hurd.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87tv0622wj.fsf@sturm.com.au> (Ben Sturmfels's message of "Sat, 23 May 2020 23:31:56 +1000")
Hello Ben,
[...]
> 2020-05-23 23:05:54:365 MESSAGE New local ip address is 192.168.1.134
> 2020-05-23 23:05:54:365 MESSAGE SIP network reachability state is now [UP]
> 2020-05-23 23:05:54:365 MESSAGE Media network reachability state is now [UP]
> 2020-05-23 23:05:54:366 MESSAGE LinphoneProxyConfig [0x7f57c800d030] about to register (LinphoneCore version: 3.12.0)
> 2020-05-23 23:05:54:367 ERROR No listening point matching for [tls://sip.linphone.org:5061]
> 2020-05-23 23:05:54:367 ERROR belle_sip_client_transaction_send_request(): no channel available
Have you used the account assistant to create that SIP account? I found
configuring an account manually confusing without it (the input text
fields expect some protocol prefix I wasn't sure about). Perhaps that
protocol line is wrong. With my voip.ms service, it works fine (using
TLS):
--8<---------------cut here---------------start------------->8---
[00:35:00:105][Info]Core:linphone: New local ip address is 192.168.10.15
[00:35:00:105][Info]Core:linphone: SIP network reachability state is now [UP]
[00:35:00:105][Info]Core:linphone: Media network reachability state is now [UP]
[00:35:00:105][Info]Core:linphone: LinphoneProxyConfig [0x7f590c00cad0] about to register (LinphoneCore version: 3.12.0)
[00:35:00:107][Info]Core:belle-sip: belle_sip_client_transaction_send_request(): waiting channel to be ready
[00:35:00:107][Info]Core:belle-sip: channel [0x159b3c0]: starting resolution of xxx.voip.ms
[00:35:00:107][Info]Core:belle-sip: channel 0x159b3c0: state RES_IN_PROGRESS
[00:35:00:107][Info]Core:belle-sip: transaction [0x11916f0] channel state changed to [RES_IN_PROGRESS]
[00:35:00:107][Info]Core:belle-sip: Resolver is using DNS server(s):
[00:35:00:107][Info]Core:belle-sip: 192.168.55.1
[00:35:00:107][Info]Core:belle-sip: 192.168.50.37
[00:35:00:107][Info]Core:belle-sip: 192.168.10.1
[00:35:00:108][Info]Core:belle-sip: resolver_process_data dns_res_check() in progress
[00:35:00:108][Info]Core:belle-sip: DNS resolution awaiting response, queued to main loop
--8<---------------cut here---------------end--------------->8---
So I know for sure that it works fine, but debugging is not easy when we
dial in a setting wrong.
Maxim
next prev parent reply other threads:[~2020-08-18 4:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-23 13:31 bug#41483: Linphone won't connect to SIP account Ben Sturmfels
2020-08-18 4:52 ` maxim.cournoyer [this message]
2020-08-28 5:37 ` Ben Sturmfels
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r1s4pnch.fsf@hurd.i-did-not-set--mail-host-address--so-tickle-me \
--to=maxim.cournoyer@gmail.com \
--cc=41483@debbugs.gnu.org \
--cc=ben@sturm.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).