Hopefully this one was fixed ... a parameter was not explicitly passed in this
case, having a garbage value. Likely it was added when the correlation id
parameter was introduced.
Master and 5.1 branches seem not affected by this issue, as they got different
implementation when it was adapted to
Module: kamailio
Branch: 5.0
Commit: 93434c4b90d4df2b24c74e4b0e10c7f7ba305dcc
URL:
https://github.com/kamailio/kamailio/commit/93434c4b90d4df2b24c74e4b0e10c7f7ba305dcc
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date: 2017-12-04T08:46:59+01:00
siptrace: wrapper for sip
Related
[description](https://lists.kamailio.org/pipermail/sr-users/2013-August/079386.html)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1215#issuecomment-348866268
For "pv_buffer_slots" issue, kamailio crashes during startup and there is
no core dump. What should i do about it?
Here is what i see in logs (just one log line).
--
Dec 4 03:44:19 webrtc-as-rct kernel: [1814300.507165] kamailio[16879]
segfault at c0c0c0c7 ip b7700239 sp bfd9a0f8 error 7 in libc
### Description
Segmentation fault when sip_trace method is called with less then 2 arguments.
### Troubleshooting
The problem does not happen if either "xheaders_write" module param is set to
zero or we provide both arguments to sip_trace method.
Reproduction
..
# - siptrace pa
Thanks @Daniel, i am opening up the tickets.
@Juha, we are not dumping sip trace to db but rather to a udp socket
(typically 127.0.0.1:5060), where we can observer them using ngrep or
sipgrep cli utilities. The whole purpose is to watch sip trace at runtime
while conducting our tests and observe t
M S writes:
> 1. Calling sip_trace method without any arguements or with only one
> arguement (duplicate uri) crashes kamailio with segfault.
My K does not crash when I make call like this:
setflag(TRACE);
sip_trace();
but I have not defined as many vars as you, but only these:
# -- si
It looks like you need to use `set_contact_alias()` for the replies, because
the contact in 180 is not matching the source port. Then use
`handle_ruri_alias()` for BYE. It's more or less what it is done for natted
traffic.
--
You are receiving this because you are subscribed to this thread.
Re
Can you run with debug=3 in kamailio.cfg, do such a test and send over all the
log messages printed by kamailio?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1350#issuecomment-3
Hello,
if you get a crash, then take the backtrace from the corefile with gdb
(inside the gdb session inspecting the corefile, do "bt full"), it is
very useful information to discover where the crash happens.
It is also better to open on issue on bug tracker, so the investigation
of the crash can
Hi,
I have kamailio v5.0.4 git rev. 5f26a4e8c55cdf5a5a7eaf6864c4f5213d321293
installed on 32bit Debian Wheezy virtual machine (1GB RAM and 1 vCPU) for
development and testing of a project.
We need to inspect sip traces to / from webrtc endpoint on kamailio side,
for which we use siptrace module w
11 matches
Mail list logo
