I've applied the patch to kamailio 5.2.2 and this seems to fix the crash! Thank
you very much for your help!
I see that Kamailio is still using source addresses where it is not listening
on. Means 192.168.1.X from the example above. Do you think that's correct? In
my point of view it should not
Unfortunately I lost the previous core dump, but as the problem is reproducible
I got a new immediately. I will post also the output of the previous commands
to be consistent.
```
(gdb) frame 0
#0 0xb6b614c6 in populate_leg_info (dlg=0xb4c02160, msg=0xb7290f40,
t=0xb4bcebec, leg=1, tag=0xbffd6
Any news regarding this issue?
--
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/2028#issuecomment-524349153___
Kamailio (SER) - Developmen
The problem is reproducible and happens always!
Following the requested information
```
(gdb) frame 0
#0 0xb6c3b4c6 in populate_leg_info (dlg=0xb4ca5b6c, msg=0xb736af40,
t=0xb4ca2890, leg=1, tag=0xbf8a3cec) at dlg_handlers.c:257
257 in dlg_handlers.c
(gdb) p*msg
$1 = {id = 3, pid = 26360, tva
```
kamctl srv sockets
list listen sockets
{
"jsonrpc": "2.0",
"result": [
{
"PROTO": "udp",
"NAME": "192.168.147.1",
"ADDRLIST": {
"ADDR": "192.168.147.1"
},
"PORT": "5070",
"MCAST": "no",
"MHOMED": "no",
"ADVERTISE": "-"
}, {
> @schneuwlym : you list in the message flow that Kamailio uses 192.168.1.1 at
> the top of the initial comment, but then you also say "Interestingly Kamailio
> does not listen on interface 192.168.1.1, so why does it use this socket?"
You misunderstood my my setup description. The box where Kam
/etc/os-release does not exist on our distro...
But we are using openssl:
```
openssl version
OpenSSL 1.0.1p 9 Jul 2015
```
Did you mean this?
--
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/kamail
If I add 192.168.1.1 and 192.168.1.2 as listen address then everything seems to
work.
So the question is, why is the behavior different for plain and encrypted SIP?
Why does Kamailio use another socket if TLS is used?
--
You are receiving this because you are subscribed to this thread.
Reply t
### Description
Hi
We have a situation where Kamailio crashes always just after receiving a SIP
ACK. We are using the following setup:
phoneA(192.168.147.100) -(TLS)- (192.168.147.1)KamailioA(192.168.1.1) -(TLS)-
(192.168.1.2)KamailioB(192.168.148.1) -(TLS)- (192.168.148.100)phoneB
If I do a cal
Thanks for the fix!
I've installed the patch about one week ago and I don't see any negative issue
till now. I have to say that I saw the problem just once, so I can't reproduce
it and I can't really confirm the fix. So feel free to close this ticket.
--
You are receiving this because you are
Alright, I had to specify where gdb shall search for sources
```
(gdb) list
246 }
247
248 if(leg==DLG_CALLER_LEG)
249 dlg->from_rr_nb = skip_recs;
250
251 LM_DBG("leg(%d) route_set [%.*s], contact [%.*s], cseq [%.*s]"
252
This is the only thing I get:
```
(gdb) list
246 in dlg_handlers.c
```
Do I need to add the sources somehow? Sorry, I'm not familiar with gdb...
--
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
### Description
While doing some fail over tests I suddenly found one kamailio dead.
### Troubleshooting
Debugging Data
```
(gdb) bt full
#0 0xb6be2dd7 in populate_leg_info (dlg=0xb4d848bc, msg=0xb728901c,
t=0xb4dfcbe8, leg=1, tag=0xbfee046c) at dlg_handlers.c:251
__llevel = 3
13 matches
Mail list logo
