[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Linphone-developers] Linphone 4 crashes after SIP registration receivin
From: |
Sebastian Gunreben |
Subject: |
[Linphone-developers] Linphone 4 crashes after SIP registration receiving 200 OK |
Date: |
Wed, 10 Jan 2018 21:45:04 +0100 |
User-agent: |
NeoMutt/20170113 (1.7.2) |
Hello Linphone Users and Developers,
I used linphone version 3 successfully behind a router (acting as an
application layer gateway) at a public Internet access.
I used the VOIP service of my provider and experienced a well
working software.
After upgrading the client (Windows) to linphone version 4 (without
touching the configuration file), linphone crashes, i.e. Windows
appcrash. Using Linux OS the issue is reproducible and also leads to a
segfault.
linphone (it does not matter if Linphone GTK, linphonec,
linphone-daemon) crashes in the following scenario (please see attached
image):
1) Client sends SIP registration to network
2) Network answers with 401 unauthorized
3) Client sends SIP registration with authentication information
4) Network answers with 200 OK
5) linphone stops working and crashes
First investigation ...
- Enabling logging information points to
>> belle-sip/src/provider.c:232
>> Updating auth context for ream [tel.t-online.de] next nonce is going to
be [(null)]
null? 200 OK provides a new nonce neq null.
- Enabling gdb debugging points to the segmentation at
>> belle-sip/src/provider.c:1024
>> the strcmp function dies because first argument is "null".
It looks like that the next_nonce is not read out properly from the 200 OK
message. Why? Any help would be appreciated.
It there is more information required, I could provide pcap traces or logs.
Best regards,
Sebastian
--
Dr. Sebastian Gunreben
address@hidden
gpg: 0xC2DF4FDD
linphone_register_crash_after_200OK.pdf
Description: Adobe PDF document
- [Linphone-developers] Linphone 4 crashes after SIP registration receiving 200 OK,
Sebastian Gunreben <=