Hi all,
I've dug into this a bit more. Firstly I enabled debug logs and spotted the
following record-route header being loaded from redis:
21(28) DEBUG: PY3 {ACK}: topos_redis [topos_redis_storage.c:1079]:
tps_redis_load_dialog(): r[5]: s[,]
127.0.0.8 is the wrong IP which explains why the ACK
Sorry, I forgot to add this information
version: kamailio 5.6.4 (x86_64/linux)
> flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS,
> DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC,
> F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT,
>
Hi all,
I am using Kamailio (5.7.2, Debian 11, Python KEMI) in a
mutli-homed environment with the topos module to hide the topology.
I have noticed that when I use `set_send_socket` or `$fsn` to force the
socket it's sent from, it breaks topos and the ACK is not proxied to the
other leg of the
Hello,
maybe I missed it, but what version of Kamailio you are using? If its an older
version, it might be a good idea to update to a maintained version, e.g. the
latest 5.7.x.
Regarding further debugging if it happens on a recent version, try to generate
a core dump. Documentation about that
More info if some body can help
Oct 17 13:38:21 proxy kernel: [2471140.725674] kamailio[24471]: segfault at
5f96000e ip 5f96000e sp 7ffc26aed398 error 14 in zero
(deleted)[7f9fd0e6a000+1000]
Oct 17 13:38:21 proxy kernel: [2471140.744537] Code: Unable to access
opcode bytes at
docs read like you can filter on headers and body. So maybe
is_present_hf("Sia") works for filtering xhttp replies.
Regards,
Bastian
On Tue, Oct 17, 2023 at 1:54 PM Benoit Panizzon via sr-users <
sr-users@lists.kamailio.org> wrote:
> Hi
>
> Further trying to eliminate every possible cause of
Hi,
Now the error was not coming,
Do you recommend making changes to the code as you have described?
On Fri, Oct 13, 2023 at 6:53 PM Patrick Karton
wrote:
> Hi,
>
> ok from kamailio source code, i see that the returned value of last
> function called in failure route is also taken also as
Hi,
Any reply would be appreciated.
On Mon, Oct 16, 2023 at 10:10 PM satyaprakash ch <
chiramchetty.satyaprak...@gmail.com> wrote:
> Hi,
>
> We possess a code within Kamailio, which specifically handles malformed
> SIP responses. Below is the code snippet:
>
>
>
>
>
> *reply_routeCopy code
On 12/10/23 15:32, Richard Fuchs via sr-users wrote:
On 12/10/2023 09.02, [EXT] Leonardo Arena via sr-users wrote:
I've opened the captured traffic with Wireshark and I've found out
that Kamailio is actually forwarding the call with a double SDP
header. ngrep was showing only a partial header.
Hi
Further trying to eliminate every possible cause of UDP drops...
We use Homer as HEP server in conjunction with the siptrace module.
So to prevent DQM traffic to be sent to Homer I added:
event_route[siptrace:msg] {
if(is_method("KDMQ")) {
drop();
}
}
And had a closer look
Hi Gang
While still hunting DMQ issues, I noticed that the OS is reporting UDP
drops. Maybe DMQ packets? Would DMQ re-send a lost packet?
I increased OS UDP RX buffers times 10 and monitoring counters.
I also found that DMQ can use tcp or tls as transport.
Could this help to prevent loosing
Hello,
if you can suggest changes to the 3rd party library that is used to encrypt the
data, it should work. Just have a look to the source code how the Kamailio side
its doing it. It might be just a different mode that its used from the library,
for example.
Cheers,
Henning
--
Henning
12 matches
Mail list logo
