THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#435 - crash in parser/sdp/sdp_helpr_funcs.c
User who did this - Michael Ricordeau (mricordeau)
----------
Hi Daniel,
I have attached the output gdb trace (trace1.txt) .
Thanks !
----------
One or more files have been attached.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=435#comment1481
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#435 - crash in parser/sdp/sdp_helpr_funcs.c
User who did this - Daniel-Constantin Mierla (miconda)
----------
Can you attach the output from gdb for:
set print elements 3000
frame 26
p *buf
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=435#comment1480
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Michael Ricordeau (mricordeau)
Attached to Project - sip-router
Summary - crash in parser/sdp/sdp_helpr_funcs.c
Task Type - Bug Report
Category - Core
Status - Unconfirmed
Assigned To -
Operating System - Linux
Severity - High
Priority - Normal
Reported Version - 4.1
Due in Version - Undecided
Due Date - Undecided
Details - Hi,
Kamailio 4.1.2 is crashing sometimes while parsing sdp.
I can't reproduce it directly but it happened a few times .
Kamailio version :
version: kamailio 4.1.2 (x86_64/linux) 6fa599
flags: STATS: Off, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, DBG_QM_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 4MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: 6fa599
compiled on 10:30:24 Mar 18 2014 with gcc 4.4.5
I have also attached the gdb bt full (gdb.txt)
Mike
One or more files have been attached.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=435
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
Hi all,
At 1&1 we have a patch for the Acc module that allows us to log CDRs
from expired dialogs (for example when a UA would fail and would not
transmit a final message). Would you see a benefit from pushing this
code upstream? If so, would you like to see this implemented as a
switchable feature
(through the use of a config parameter) or as something enabled all the
time?
I know that the current view on things, stated in the Acc module
documentation is:
"If a UA fails in middle of conversation, a proxy will never find out
about it. In general, a better practice is to account from an end-device
(such as PSTN gateway), which best knows about call status (including
media status and PSTN status in case of the gateway). "
What do you think?
Thank you!