date:20210728

Re: [Blink] debian buster

2021-07-28 Thread Adrian Georgescu

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 22:39:43] WARNING[24030]: pjproject: : tsx0x7f7e5c315d48 
> .Error sending Response msg 200/INVITE/cseq=19985 (tdta0x7f7e50010d68): 
> Invalid operation (PJ_EINVALIDOP)
> 
> 
> 
> On Wed, 28 Jul 2021 at 22:54, Alberto  > wrote:
> 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 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 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: https://icanblink.com/help/problems-qt/ 
>>> 
>>> but I don't see anything useful here. Any advice?
>>> 
>>> $ gdb -c core blink
>>> GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
>>> Copyright (C) 2020 Free Software Foundation, Inc.
>>> License GPLv3+: GNU GPL version 3 or later 
>>> >
>>> This is free software: you are free to change and redistribute it.
>>> There is NO WARRANTY, to the extent permitted by law.
>>> Type "show copying" and "show warranty" for details.
>>> This GDB was configured as "x86_64-linux-gnu".
>>> Type "show configuration" for configuration details.
>>> For bug reporting instructions, please see:
>>> >> >.
>>> Find the GDB manual and other documentation resources online at:
>>> >> >.
>>> 
>>> For help, type "help".
>>> Type "apropos word" to search for commands related to "word"...
>>> "/usr/bin/blink": not in executable format: file format not recognized
>>> [New LWP 3893]
>>> [New LWP 3887]
>>> [New LWP 3905]
>>> [New LWP 3910]
>>> [New LWP 3914]
>>> [New LWP 3883]
>>> [New LWP 3885]
>>> [New LWP 3891]
>>> [New LWP 3917]
>>> [New LWP 3901]
>>> [New LWP 3884]
>>> [New LWP 3886]
>>> [New LWP 3889]
>>> [New LWP 3890]
>>> [New LWP 3912]
>>> [New LWP 3902]
>>> [New LWP 3913]
>>> [New LWP 3881]
>>> [New LWP 3915]
>>> [New LWP 3916]
>>> Core was generated by `/usr/bin/python3 /usr/bin/blink'.
>>> Program terminated with signal SIGSEGV, Segmentation fault.
>>> #0  0x7f945cf6a955 in ?? ()
>>> [Current thread is 1 (LWP 3893)]
>>> (gdb) 
>>> 
>>> 
>>> 
>>> 
>>> On Wed, 28 Jul 2021 at 17:43, >> > wrote:
>>> 
>>> 
 On 28 Jul 2021, at 17:24, Alberto >>> > wrote:
 
 the problem is that the server only accepts tls 1 and 
>>> 
>>> 
>>> i thought TLS 1.0 and TLS 1.1 had been deprecated?
>>> 
>>> If you had to make it work, could you use asterisk to connect to the SIP 
>>> provider, and then use Blink to connect to asterisk? (In other worse, 
>>> running your own PBX until the SIP trunk provider upgrades their security 
>>> to something more modern.)
>>> 
>>> Best wishes
>>> 
>>> Neil
>>> 
>>> 
>>> 
>>> ___
>>> Blink mailing list
>>> Blink@lists.ag-projects.com 
>>> https://lists.ag-projects.com/mailman/listinfo/blink 
>>> 
>>> ___
>>> Blink mailing list
>>> Blink@lists.ag-projects.com 
>>> https://lists.ag-projects.com/mailman/listinfo/blink 
>>> 
>> 
>> ___
>> Blink mailing list
>> Blink@lists.ag-projects.com 
>> https://lists.ag-projects.com/mailman/listinfo/blink 
>> 
>> ___
>> Blink mailing list
>> Blink@lists.ag-projects.com 
>> https://lists.ag-projects.com/mailman/listinfo/blink 
>> 
> 
> ___
>

Re: [Blink] debian buster

2021-07-28 Thread Alberto

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 (PJ_EINVALIDOP)



On Wed, 28 Jul 2021 at 22:54, Alberto  wrote:

> 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 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 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:
>>> https://icanblink.com/help/problems-qt/
>>> but I don't see anything useful here. Any advice?
>>>
>>> $ gdb -c core blink
>>> GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
>>> Copyright (C) 2020 Free Software Foundation, Inc.
>>> License GPLv3+: GNU GPL version 3 or later <
>>> http://gnu.org/licenses/gpl.html>
>>> This is free software: you are free to change and redistribute it.
>>> There is NO WARRANTY, to the extent permitted by law.
>>> Type "show copying" and "show warranty" for details.
>>> This GDB was configured as "x86_64-linux-gnu".
>>> Type "show configuration" for configuration details.
>>> For bug reporting instructions, please see:
>>> .
>>> Find the GDB manual and other documentation resources online at:
>>> .
>>>
>>> For help, type "help".
>>> Type "apropos word" to search for commands related to "word"...
>>> "/usr/bin/blink": not in executable format: file format not recognized
>>> [New LWP 3893]
>>> [New LWP 3887]
>>> [New LWP 3905]
>>> [New LWP 3910]
>>> [New LWP 3914]
>>> [New LWP 3883]
>>> [New LWP 3885]
>>> [New LWP 3891]
>>> [New LWP 3917]
>>> [New LWP 3901]
>>> [New LWP 3884]
>>> [New LWP 3886]
>>> [New LWP 3889]
>>> [New LWP 3890]
>>> [New LWP 3912]
>>> [New LWP 3902]
>>> [New LWP 3913]
>>> [New LWP 3881]
>>> [New LWP 3915]
>>> [New LWP 3916]
>>> Core was generated by `/usr/bin/python3 /usr/bin/blink'.
>>> Program terminated with signal SIGSEGV, Segmentation fault.
>>> #0  0x7f945cf6a955 in ?? ()
>>> [Current thread is 1 (LWP 3893)]
>>> (gdb)
>>>
>>>
>>>
>>>
>>> On Wed, 28 Jul 2021 at 17:43,  wrote:
>>>


 On 28 Jul 2021, at 17:24, Alberto  wrote:

 the problem is that the server only accepts tls 1 and


 i thought TLS 1.0 and TLS 1.1 had been deprecated?

 If you had to make it work, could you use asterisk to connect to the
 SIP provider, and then use Blink to connect to asterisk? (In other worse,
 running your own PBX until the SIP trunk provider upgrades their security
 to something more modern.)

 Best wishes

 Neil



 ___
 Blink mailing list
 Blink@lists.ag-projects.com
 https://lists.ag-projects.com/mailman/listinfo/blink

>>> ___
>>> Blink mailing list
>>> Blink@lists.ag-projects.com
>>> https://lists.ag-projects.com/mailman/listinfo/blink
>>>
>>>
>>> ___
>>> Blink mailing list
>>> Blink@lists.ag-projects.com
>>> https://lists.ag-projects.com/mailman/listinfo/blink
>>>
>> ___
>> Blink mailing list
>> Blink@lists.ag-projects.com
>> https://lists.ag-projects.com/mailman/listinfo/blink
>>
>>
>> ___
>> Blink mailing list
>> Blink@lists.ag-projects.com
>> https://lists.ag-projects.com/mailman/listinfo/blink
>>
>
___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] debian buster

2021-07-28 Thread Alberto

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 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 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:
>> https://icanblink.com/help/problems-qt/
>> but I don't see anything useful here. Any advice?
>>
>> $ gdb -c core blink
>> GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
>> Copyright (C) 2020 Free Software Foundation, Inc.
>> License GPLv3+: GNU GPL version 3 or later <
>> http://gnu.org/licenses/gpl.html>
>> This is free software: you are free to change and redistribute it.
>> There is NO WARRANTY, to the extent permitted by law.
>> Type "show copying" and "show warranty" for details.
>> This GDB was configured as "x86_64-linux-gnu".
>> Type "show configuration" for configuration details.
>> For bug reporting instructions, please see:
>> .
>> Find the GDB manual and other documentation resources online at:
>> .
>>
>> For help, type "help".
>> Type "apropos word" to search for commands related to "word"...
>> "/usr/bin/blink": not in executable format: file format not recognized
>> [New LWP 3893]
>> [New LWP 3887]
>> [New LWP 3905]
>> [New LWP 3910]
>> [New LWP 3914]
>> [New LWP 3883]
>> [New LWP 3885]
>> [New LWP 3891]
>> [New LWP 3917]
>> [New LWP 3901]
>> [New LWP 3884]
>> [New LWP 3886]
>> [New LWP 3889]
>> [New LWP 3890]
>> [New LWP 3912]
>> [New LWP 3902]
>> [New LWP 3913]
>> [New LWP 3881]
>> [New LWP 3915]
>> [New LWP 3916]
>> Core was generated by `/usr/bin/python3 /usr/bin/blink'.
>> Program terminated with signal SIGSEGV, Segmentation fault.
>> #0  0x7f945cf6a955 in ?? ()
>> [Current thread is 1 (LWP 3893)]
>> (gdb)
>>
>>
>>
>>
>> On Wed, 28 Jul 2021 at 17:43,  wrote:
>>
>>>
>>>
>>> On 28 Jul 2021, at 17:24, Alberto  wrote:
>>>
>>> the problem is that the server only accepts tls 1 and
>>>
>>>
>>> i thought TLS 1.0 and TLS 1.1 had been deprecated?
>>>
>>> If you had to make it work, could you use asterisk to connect to the SIP
>>> provider, and then use Blink to connect to asterisk? (In other worse,
>>> running your own PBX until the SIP trunk provider upgrades their security
>>> to something more modern.)
>>>
>>> Best wishes
>>>
>>> Neil
>>>
>>>
>>>
>>> ___
>>> Blink mailing list
>>> Blink@lists.ag-projects.com
>>> https://lists.ag-projects.com/mailman/listinfo/blink
>>>
>> ___
>> Blink mailing list
>> Blink@lists.ag-projects.com
>> https://lists.ag-projects.com/mailman/listinfo/blink
>>
>>
>> ___
>> Blink mailing list
>> Blink@lists.ag-projects.com
>> https://lists.ag-projects.com/mailman/listinfo/blink
>>
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink
>
>
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink
>
2021-07-28 22:39:50.257621 [blink 4871]: DNS lookup A sip.provider.net 
succeeded, ttl=200: 217.75.85.122
2021-07-28 22:39:50.579991 [blink 4871]: SENDING: Packet 1, +0:00:03.916067
192.168.0.15:38763 -(SIP over TLS)-> 217.75.85.122:5061
INVITE sip:0...@sip.provider.net SIP/2.0
Via: SIP/2.0/TLS 
192.168.0.15:38763;rport;branch=z9hG4bKPj23b82272-efee-11eb-87c5-0b6133481102;alias
Max-Forwards: 70
From: "1000" 
;tag=23b67670-efee-11eb-a38e-bf287a1ec4b6
To: 
Contact: 
Call-ID: 23b2a3ec-efee-11eb-b432-03abb3025312
CSeq: 22331 INVITE
Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, BYE, CANCEL, UPDATE, MESSAGE, REFER
Supported: replaces, norefersub, gruu
User-Agent: Blink 5.1.3 (Linux)
Content-Type: application/sdp
Content-Length:   420

v=0
o=- 3836497190 3836497190 IN IP4 192.168.0.15
s=Blink 5.1.3 (Linux)
t=0 0
m=audio 5 RTP/SAVP 3 8 101
c=IN IP4 192.168.0.15
a=rtcp:50001
a=rtpmap:3 GSM/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=crypto:1 AES_CM_128_HMAC_SHA1_80 
inline:IIRLjPLH3GORA/BDNGN6dmYLRAQVvMAPNs7I2tab
a=crypto:2 AES_CM_128_HMAC_SHA1_32 
inline:FvxVbZNRvRW3M8dfP2KwSTUai2syhr9eDYYDWEVJ
a=sendrecv

--
2021-07-28 22:39:50.741376 [blink 4871]: RECEIVED: Packet 2, +0:00:04.077452
217.75.85.122:5061 -(SIP over TLS)-> 192.168.0.15:38763
SIP/2.0 401 Unauthorized
Via: SIP/2.0/TLS

Re: [Blink] debian buster

2021-07-28 Thread Alberto

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 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: https://icanblink.com/help/problems-qt/
> but I don't see anything useful here. Any advice?
>
> $ gdb -c core blink
> GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
> Copyright (C) 2020 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <
> http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> Type "show copying" and "show warranty" for details.
> This GDB was configured as "x86_64-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> .
> Find the GDB manual and other documentation resources online at:
> .
>
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> "/usr/bin/blink": not in executable format: file format not recognized
> [New LWP 3893]
> [New LWP 3887]
> [New LWP 3905]
> [New LWP 3910]
> [New LWP 3914]
> [New LWP 3883]
> [New LWP 3885]
> [New LWP 3891]
> [New LWP 3917]
> [New LWP 3901]
> [New LWP 3884]
> [New LWP 3886]
> [New LWP 3889]
> [New LWP 3890]
> [New LWP 3912]
> [New LWP 3902]
> [New LWP 3913]
> [New LWP 3881]
> [New LWP 3915]
> [New LWP 3916]
> Core was generated by `/usr/bin/python3 /usr/bin/blink'.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  0x7f945cf6a955 in ?? ()
> [Current thread is 1 (LWP 3893)]
> (gdb)
>
>
>
>
> On Wed, 28 Jul 2021 at 17:43,  wrote:
>
>>
>>
>> On 28 Jul 2021, at 17:24, Alberto  wrote:
>>
>> the problem is that the server only accepts tls 1 and
>>
>>
>> i thought TLS 1.0 and TLS 1.1 had been deprecated?
>>
>> If you had to make it work, could you use asterisk to connect to the SIP
>> provider, and then use Blink to connect to asterisk? (In other worse,
>> running your own PBX until the SIP trunk provider upgrades their security
>> to something more modern.)
>>
>> Best wishes
>>
>> Neil
>>
>>
>>
>> ___
>> Blink mailing list
>> Blink@lists.ag-projects.com
>> https://lists.ag-projects.com/mailman/listinfo/blink
>>
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink
>
>
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink
>
___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] debian buster

2021-07-28 Thread Alberto

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: https://icanblink.com/help/problems-qt/
but I don't see anything useful here. Any advice?

$ gdb -c core blink
GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
"/usr/bin/blink": not in executable format: file format not recognized
[New LWP 3893]
[New LWP 3887]
[New LWP 3905]
[New LWP 3910]
[New LWP 3914]
[New LWP 3883]
[New LWP 3885]
[New LWP 3891]
[New LWP 3917]
[New LWP 3901]
[New LWP 3884]
[New LWP 3886]
[New LWP 3889]
[New LWP 3890]
[New LWP 3912]
[New LWP 3902]
[New LWP 3913]
[New LWP 3881]
[New LWP 3915]
[New LWP 3916]
Core was generated by `/usr/bin/python3 /usr/bin/blink'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7f945cf6a955 in ?? ()
[Current thread is 1 (LWP 3893)]
(gdb)

On Wed, 28 Jul 2021 at 17:43,  wrote:

>
>
> On 28 Jul 2021, at 17:24, Alberto  wrote:
>
> the problem is that the server only accepts tls 1 and
>
>
> i thought TLS 1.0 and TLS 1.1 had been deprecated?
>
> If you had to make it work, could you use asterisk to connect to the SIP
> provider, and then use Blink to connect to asterisk? (In other worse,
> running your own PBX until the SIP trunk provider upgrades their security
> to something more modern.)
>
> Best wishes
>
> Neil
>
>
>
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink
>
___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] debian buster

2021-07-28 Thread Alberto

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 me, so how can
I make blink support tls 1 as well ?

Thanks

On Wed, 28 Jul 2021 at 01:35, Adrian Georgescu  wrote:

> 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 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 something?
>
> Thanks
> A
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink
>
>
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink
>
___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] debian buster

Re: [Blink] debian buster

Re: [Blink] debian buster

Re: [Blink] debian buster

Re: [Blink] debian buster

Re: [Blink] debian buster

6 matches

Site Navigation

Mail list logo

Footer information