Jeff Bilyk writes:
> https://lists.kamailio.org/pipermail/sr-users/2013-March/077235.html may
> contain a helpful workaround,
Jeff,
Thanks for your reply. I do have
tcp_accept_aliases=no
and this problems appears before event_route [xhttp:request], that is,
already during TLS handshake.
--
Hi Joel,
Thanks, that's precisely it!
Indeed, `dlg.stats_active` works correctly and what's nice about it is that
it shows stats summary from all DMQ nodes combined. However, I
use xHTTP_PROM module to export my stats, which seems to rely on the
'problematic' counters. Sad... Let's hope this
Hey Sergiu,
I think I've been through a similar case... have a look at:
https://github.com/kamailio/kamailio/issues/1591 in case you find it
helpful.
You might have to rely on the different metric that Daniel added.
Joel.
On Fri, Oct 16, 2020 at 3:35 AM Sergiu Pojoga wrote:
> Hi Daniel,
>
Henning Westerholt writes:
> Interesting. Does e.g. 5.4 still works for you? Might be then a
> regression in trunk.
Same problem with 5.4.
-- Juha
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
Simple way to show this problem without any WebRTC SIP client is to
point Chrome browser to K's TLS listening port:
https://:5061
and look with wireshark or tshark how the handshake gets terminated by
Chrome right after Server Hello.
The same with Firefox works fine.
-- Juha
Hello,
you can specify on command line during start:
henning@kam01:~$ /usr/sbin/kamailio -h | grep mem
-m nrSize of shared memory allocated in Megabytes
-M nrSize of private memory allocated, in Megabytes
Cheers,
Henning
--
Henning Westerholt -
Hello Juha,
https://lists.kamailio.org/pipermail/sr-users/2013-March/077235.html may
contain a helpful workaround,
Jeff
On Fri, Oct 16, 2020, 11:14 AM Juha Heinanen wrote:
> Henning Westerholt writes:
>
> > Interesting. Does e.g. 5.4 still works for you? Might be then a
> > regression in
Dear Users
How can I increase private memory in the Kamailio container?
the service was started with the following command
docker run -d --restart unless-stopped --network host -v
/root/volumes/scscf/:/etc/kamailio --name scscf -e IP=10.161.224.90 -e
INT_IP=10.161.224.90
Hi Juha,
Interesting. Does e.g. 5.4 still works for you? Might be then a regression in
trunk.
Cheers,
Henning
--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://gilawa.com
-Original Message-
From: sr-users On Behalf Of Juha Heinanen
Sent: Friday, October
Hello
Yes I bet more in the system race condition, but yes it's hard to identify
it because I tried several times to replicate it and it didn't happen.
When it failed the restart was performed by Chef, and I'm trying to
replicate it doing the restarts by myself without using chef, not sure if
chef
Hello,
It might be something during the restart, that some of the processes did not
started correctly due to still allocated resources from the “old” processes
still running. Maybe a race condition in this particular system environment,
but hard to say if you cannot reproduce it.
Cheers,
no, I'm pretty sure that didn't happen, I don't have any other config files
there.
Regards
Ovidiu Sas escreveu no dia sexta, 16/10/2020 à(s)
13:47:
> Maybe you restarted with a different config file?
>
> -ovidiu
>
> On Fri, Oct 16, 2020 at 04:54 José Seabra wrote:
>
>> Hi Ovidiu,
>>
>> I
Maybe you restarted with a different config file?
-ovidiu
On Fri, Oct 16, 2020 at 04:54 José Seabra wrote:
> Hi Ovidiu,
>
> I compared both logs and when kamailio didn't started all processes, there
> is missing the log msg from usrloc_dmq:
>
> INFO: dmq_usrloc [dmq_usrloc.c:77]: mod_init():
Hi Daniel,
You guessed right, two dmq nodes with dialog replication.
Thanks,
On Fri., Oct. 16, 2020, 2:15 a.m. Daniel-Constantin Mierla, <
mico...@gmail.com> wrote:
> Hello,
>
> is this happening when using dmq for dialog with multiple sip servers? Or
> is a single instance sip server?
>
>
Hi Ovidiu,
I compared both logs and when kamailio didn't started all processes, there
is missing the log msg from usrloc_dmq:
INFO: dmq_usrloc [dmq_usrloc.c:77]: mod_init(): dmq usrloc replication mode = 1
But I still have doubts why it happened, do you guys know any possible
reason that could
Hello,
is this happening when using dmq for dialog with multiple sip servers?
Or is a single instance sip server?
Cheers,
Daniel
On 16.10.20 04:12, Sergiu Pojoga wrote:
> Hi there,
>
> Every now and then, the value of active dialogs metric spikes to an
> erroneous huge number, messing up my
When you have detected a failed target, you can update the dispatcher table
and then reload dispatchers
On Thu, Oct 15, 2020 at 9:57 PM Sergey Safarov wrote:
> you one dispatcher destination failed you can try other
>
> Example
>
>
17 matches
Mail list logo
