Hi Community,
We are setting up a new provider in our VoIP setup for outgoing calls
(FreeSWITCH --> Kamailio --> Provider).
When the provider sends a 200 OK in response to our INVITE, FreeSWITCH's
SIP stack discards the message, and we are unable to determine the cause of
this behavior.
I am sha
Hi, Daniel.
Thank you for the quick response!
I will update you after testing the fix.
Regards,
Vanderlei
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Import
Yes, exactly, but with the caveat that the B2BUA in the middle must aggregate
responses with differing To tags in a satisfactory way.
Proxy forking is messy. Proxies aren't UAs, and their call attempts aren't call
legs, but "branches". Proxies essentially fork calls with one hand tied behind
th
Yes Alex, this is what I understood as well.
To have something like:
"Caller" <-> "B2BUA" <-> "Kamailio" <-> "Callee"
right?
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.ka
Hello Vanderlei,
thanks for the follow up, this looks indeed suspicious. I think Daniel already
pushed a possible fix to git master branch, maybe you give this a try to see if
it solves your problem.
Cheers,
Henning
From: Vanderlei Torres Batistela via sr-users
Sent: Mittwoch, 10. Juli 2024
Hello Henning,
Thank you for your quick response.
The increase happens in the core module (create-avp). See bellow:
[root@labcom070 kamailio]# kamcmd mod.stats all shm
Module: core
{
create_avp(178): 52257504
<
counters
Hello,
first, the value for -M is too high, I cannot easily think of a case
when one needs 1GB of private memory for each kamailio process.
You can try to run the rpc command shm.stats and look in the syslog for
the report to check if it is different that what you get with mod.mem_stats.
Cheers,
Hello,
I couldn't spot any error message in the log file that you attached,
have you taken it when you encountered the problem?
Anyhow, I am not familiar with the implementation of the
event_route[network:msg], but the shm info indicates the leak to be
related to avp, so I pushed a patch to destr
Hello!
I'm trying to get where all the SHM memory gone. For the moment I'm using
these settings:
-m 8192 -M 1024
which means 8G of SHM meory.
Kamailio parameters are the following
fork=yes
children=8
tcp_children=12
enable_tls=yes
enable_sctp=no
tls_threads_mode=2
tcp_accept_no_cl=yes
tcp_max_con
Denys,
I assume a different places where callback is happening
Le mer. 10 juil. 2024 à 09:42, Denys Pozniak a
écrit :
> Hey,
> Thanks, I'll have to try it.
> Just out of curiosity, what is the difference between routes *onsend_route
> {}* and *event_route[network:msg] {}* in the context of catc
Hey,
Thanks, I'll have to try it.
Just out of curiosity, what is the difference between routes *onsend_route
{}* and *event_route[network:msg] {}* in the context of catching outgoing
requests (also locally generated) from Kamailio.
ср, 3 июл. 2024 г. в 11:37, Ihor Olkhovskyi :
> Hello,
>
> Out of
11 matches
Mail list logo
