### Description
we are using version: kamailio 5.5.1 (x86_64/linux) 8aa8df-dirty and we have a
setup with 2 kamailio instances. First one is doing topoh, and the second one
is supposed to not do it
Despite this we do see that some replies the second instance is masking some
headers like recor
hello all
we have seen some cores on the same server like this one
```
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1 0x7f02297a0537 in __GI_abort () at abort.c:79
#2 0x55caeb47dc3d in qm_debug_check_frag (qm=0x7f00aba53000,
f=0x7f019c02c760, file=0x7f0222
hello Daniel we have had another core
```
#0 0x7fa0db0799b0 in ?? ()
#1 0x7fa10d780741 in run_trans_callbacks_internal (cb_lst=0x7fa0b54752f0,
type=131072, trans=0x7fa0b5475278, params=0x7ffdfb6b4d90) at t_hooks.c:258
#2 0x7fa10d780871 in run_trans_callbacks (type=131072,
trans=0x
ok thanks Daniel. I will activate the core per pid, and we will check to
upgrade to 5.6
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3593#issuecomment-1774656304
You are receiving this because you are subscribed to this thread.
Message ID: __
version: kamailio 5.5.6 (x86_64/linux) 21a9bc
Operating System: Debian GNU/Linux 11 (bullseye)
Kernel: Linux 5.10.0-22-amd64
we see this core it has repeated some times in different days
```
(gdb) bt
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1 0x
hello all
I tried to set the machine default route to 87.1.1.1 but I still got messages
of that kind
I also tried to add force socket on cancel requests before the t_relay(), since
I saw that maybe when the error generated was when we have a CANCEL request
which seemed to not be processed the
Hello all
we are seeing these kind of logs in a Debian GNU/Linux 11 using kamailio 5.5.6
```Sep 21 17:41:13 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155702]:
ERROR: [core/forward.c:183]: get_out_socket(): no corresponding socket
found for(udp:[164.152.22.248:5060](http://164.152.22.248:5
