Re: [Blink] debian buster

Hi, did you have a chance to look into this? Thanks On Thu, 29 Jul 2021 at 09:52, Alberto wrote: > ... and notifications > > On Thu, 29 Jul 2021 at 09:51, Alberto wrote: > >> he, here's a new call >> >> On Wed, 28 Jul 2021 at 23:26, Adrian Georgescu >> wrote: >> >>> The 200 OK is not

Re: [Blink] debian buster

... and notifications On Thu, 29 Jul 2021 at 09:51, Alberto wrote: > he, here's a new call > > On Wed, 28 Jul 2021 at 23:26, Adrian Georgescu wrote: > >> The 200 OK is not correctly handed. Can you enable both notifications and >> pjsip traces as well >> >> On 28 Jul 2021, at 19:00, Alberto

Re: [Blink] debian buster

he, here's a new call On Wed, 28 Jul 2021 at 23:26, Adrian Georgescu wrote: > The 200 OK is not correctly handed. Can you enable both notifications and > pjsip traces as well > > On 28 Jul 2021, at 19:00, Alberto wrote: > > Hi, > I mentioned I'm reproducing this on my own asterisk vm, > I

Re: [Blink] debian buster

The 200 OK is not correctly handed. Can you enable both notifications and pjsip traces as well > On 28 Jul 2021, at 19:00, Alberto wrote: > > Hi, > I mentioned I'm reproducing this on my own asterisk vm, > I happen to have the cli open and noticed this error when blink cores > > [Jul 28

Re: [Blink] debian buster

Hi, I mentioned I'm reproducing this on my own asterisk vm, I happen to have the cli open and noticed this error when blink cores [Jul 28 22:39:43] WARNING[24030]: pjproject: : tsx0x7f7e5c315d48 .Error sending Response msg 200/INVITE/cseq=19985 (tdta0x7f7e50010d68): Invalid operation

Re: [Blink] debian buster

attached, thanks for looking into this. On Wed, 28 Jul 2021 at 22:01, Adrian Georgescu wrote: > Can you show the sip trace. Enable SIP trace file logging. > > Adrian > > > > On 28 Jul 2021, at 17:57, Alberto wrote: > > I have python3-sipsimple 5.2.5buster amd64 > > On Wed, 28 Jul 2021 at

Re: [Blink] debian buster

I have python3-sipsimple 5.2.5buster amd64 On Wed, 28 Jul 2021 at 17:57, Adrian Georgescu wrote: > What version of python3-sipsimple are you running? > > dpkg -l python3-sipsimple > > On 28 Jul 2021, at 13:50, Alberto wrote: > > I could do that, at least now we know that the "Unsupported

Re: [Blink] debian buster

I could do that, at least now we know that the "Unsupported Protocol" is about. But now I have another problem, I tried to make a call using tls 1.2 and sdes. Blink established the call, I got less than half a second of audio, then cored. I followed this for crash reports:

Re: [Blink] debian buster

Hi, I did some more tests with a different asterisk server on a vm, the problem is that the server only accepts tls 1 and blink(libraries) only support tls 1.2. When I change this setting on the server to tls 1.2, blink works just fine. However, I can't make the real provider change protocol for

Re: [Blink] debian buster

Please enable logging and check the log files for more information that can reveal the reason https://icanblink.com/help/problems-qt/ > On 27 Jul 2021, at 19:31, Alberto wrote: > > Hi, > > I have reinstalled my debian buster, and immediately

[Blink] debian buster

Hi, I have reinstalled my debian buster, and immediately added your repository and installed blink. But when I try to login to a tls account it says "Registration Failed (Unsupported Protocol)". I'm using a backup of the configuration that was working before on the same pc. Am I missing