[Blink] debian buster

[Alberto]

Hi,
did you have a chance to look into this?

Thanks

On Thu, 29 Jul 2021 at 09:52, Alberto <alberto.rinaudo at gmail.com> wrote:

> ... and notifications
>
> On Thu, 29 Jul 2021 at 09:51, Alberto <alberto.rinaudo at gmail.com> wrote:
>
>> he, here's a new call
>>
>> On Wed, 28 Jul 2021 at 23:26, Adrian Georgescu <ag at ag-projects.com>
>> 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 <alberto.rinaudo at gmail.com> 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 <alberto.rinaudo at gmail.com> wrote:
>>>
>>>> attached, thanks for looking into this.
>>>>
>>>> On Wed, 28 Jul 2021 at 22:01, Adrian Georgescu <ag at ag-projects.com>
>>>> wrote:
>>>>
>>>>> Can you show the sip trace. Enable SIP trace file logging.
>>>>>
>>>>> Adrian
>>>>>
>>>>>
>>>>>
>>>>> On 28 Jul 2021, at 17:57, Alberto <alberto.rinaudo at gmail.com> wrote:
>>>>>
>>>>> I have python3-sipsimple 5.2.5buster  amd64
>>>>>
>>>>> On Wed, 28 Jul 2021 at 17:57, Adrian Georgescu <ag at ag-projects.com>
>>>>> wrote:
>>>>>
>>>>>> What version of python3-sipsimple are you running?
>>>>>>
>>>>>> dpkg -l python3-sipsimple
>>>>>>
>>>>>> On 28 Jul 2021, at 13:50, Alberto <alberto.rinaudo at gmail.com> 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:
>>>>>> <http://www.gnu.org/software/gdb/bugs/>.
>>>>>> Find the GDB manual and other documentation resources online at:
>>>>>>     <http://www.gnu.org/software/gdb/documentation/>.
>>>>>>
>>>>>> 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  0x00007f945cf6a955 in ?? ()
>>>>>> [Current thread is 1 (LWP 3893)]
>>>>>> (gdb)
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, 28 Jul 2021 at 17:43, <blink at neilzone.co.uk> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On 28 Jul 2021, at 17:24, Alberto <alberto.rinaudo at gmail.com> 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 at lists.ag-projects.com
>>>>>>> https://lists.ag-projects.com/mailman/listinfo/blink
>>>>>>>
>>>>>> _______________________________________________
>>>>>> Blink mailing list
>>>>>> Blink at lists.ag-projects.com
>>>>>> https://lists.ag-projects.com/mailman/listinfo/blink
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Blink mailing list
>>>>>> Blink at lists.ag-projects.com
>>>>>> https://lists.ag-projects.com/mailman/listinfo/blink
>>>>>>
>>>>> _______________________________________________
>>>>> Blink mailing list
>>>>> Blink at lists.ag-projects.com
>>>>> https://lists.ag-projects.com/mailman/listinfo/blink
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Blink mailing list
>>>>> Blink at lists.ag-projects.com
>>>>> https://lists.ag-projects.com/mailman/listinfo/blink
>>>>>
>>>> _______________________________________________
>>> Blink mailing list
>>> Blink at lists.ag-projects.com
>>> https://lists.ag-projects.com/mailman/listinfo/blink
>>>
>>>
>>> _______________________________________________
>>> Blink mailing list
>>> Blink at lists.ag-projects.com
>>> https://lists.ag-projects.com/mailman/listinfo/blink
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ag-projects.com/pipermail/blink/attachments/20210804/3d1d4338/attachment.htm>