SIP call causes segfault everytime

[Larry_Y_]

Steps:

OS: CentOS Linux release 7.2.1511 (Core) 

MCU version: 3.2.1

1)Start kamailio;

2)Start mcu all;

3)Launch jitsi and call mcu.

The /var/log/messages shows:

Dec 16 22:58:04 iZ25bi6zryeZ /usr/sbin/kamailio[7985]: NOTICE: acc [acc.c:317]: acc_log_request(): ACC: transaction answered: timestamp=1481900284;method=INVITE;from_tag=3fd81862;to_tag=12068c75d37c0eab;call_id=dc5ab079e586083bf0dea8c3a58b91a2@0:0:0:0:0:0:0:0;code=200;reason=Answering;src_user=jitsi;src_domain=112.126.94.56;src_ip=71.45.11.157;dst_ouser=mcu;dst_user=mcu-0x7f1dd004e040;dst_domain=112.126.94.56
Dec 16 22:58:05 iZ25bi6zryeZ kernel: woogeen_sip[8642]: segfault at 68 ip 00007f1ddf7623bd sp 00007f1ddd955a00 error 4 in libsip_gateway.so[7f1ddf750000+37000]
Please help.

[Lei_Z_Intel1]

Hi, Larry

It's better you can provide the core dump file for woogeen_sip when error happens. Please follow below steps in case you don't know how to collect core dump file.

“ulimit -c unlimited” to make it effective immediately in current console;

Modify the /etc/security/limits.conf (on Ubuntu) or /etc/security/limits.d/xxx.conf to add the following lines

“* soft core unlimited”

“* hard core unlimited”

Then execute command below:

echo ‘/tmp/core.%e.%p.%t’ | sudo tee /proc/sys/kernel/core_pattern

if crash happened, related coredump file would be generated in /tmp/ folder with core.xxx file name.