You are using DMQ to replicate usrloc between registrars ?
This should not affect the "proxy servers", although their exact role is
not mentioned.
If this is the case, you could do some kamcmd ul.dump on both registrars.
Also the DMQ traffic can be traced by tcpdump etc.
You may also want to
Did you look at the tcpops module.
I am sometimes getting confused but I think this is the one made by the
kernel and it is simply a socket option flag.
On Thu, Mar 21, 2024, 6:14 AM Ihor Olkhovskyi via sr-users <
sr-users@lists.kamailio.org> wrote:
> Hello,
>
> A bit generic question, does
Hi Daniel, I hope you are well, I miss the community !
I just want to make sure you got my submission, I made it yesterday so I am
not expecting an answer right away but just in case something went wrong ...
Cheers !
On Mon, Jan 8, 2024 at 7:30 AM Daniel-Constantin Mierla via sr-users <
The on failure route was not triggered because I was doing a t_reply before
the timeout was triggered ...
On Tue, Nov 21, 2023 at 1:51 PM Julien Chavanton
wrote:
> Sorry for the incomplete email.
>
> My problem is that the failure route does not trigger on TCP timeout.
>
> ...
&
tcp_send_timeout=3
t_set_max_lifetime(3000, 3000);
I also waited a lot more than 32 seconds.
Maybe I need to run in debug mode to find out what is going on.
On Tue, Nov 21, 2023 at 1:46 PM Julien Chavanton
wrote:
> Hi,
>
> I would like to catch TCP timeouts when I use a socket that was not c
Hi,
I would like to catch TCP timeouts when I use a socket that was not closed.
In this example I am sending SIP MESSAGE
...
t_on_reply("ON_REPLY_MESSAGE");
t_on_failure("FAILURE_MESSAGE");
if (!t_relay())
sl_reply_error();
__
Hi again Pyry, it would be great if you could cherry-pick the commit/patch
and test it and add a comment in the MR.
https://github.com/kamailio/kamailio/pull/3232
On Tue, Sep 6, 2022 at 10:34 AM Julien Chavanton
wrote:
> Hi Pyry, I just made some tests and found the misalignment, I
Hi Pyry, I just made some tests and found the misalignment, I am preparing
a patch.
I made some tests with 3 and 6 gateways, disabling one and then two, I
found how the indexes could get mixed up between the call to
ds_sorted_by_priority() and ds_manage_routes_fill_reordered_xavp().
Hopefully
ription of that commit looks quite same that what I’m now facing
> with only the xavp_dst values.
>
> If the highest priority destination is inactive the destination is updated
> but the corresponding xavp_dst values are not correct(or missing
> completely).
>
>
>
> With my
The rest of the dispatcher "features", like failover should be supported
based on what I remember from the way it was integrated and tested.
If it is not the case I can have a look.
On Thu, Sep 1, 2022 at 9:21 AM Julien Chavanton
wrote:
> On second thought, the documentation l
lance using round-robin prioritizing the
gateways with the highest priority. "
On Thu, Sep 1, 2022 at 9:09 AM Julien Chavanton
wrote:
> Maybe the documentation should be improved, it seems the first bullet
> point should say.
>
> "The algorithm will load balance usi
Maybe the documentation should be improved, it seems the first bullet point
should say.
"The algorithm will load balance using round-robin prioritizing the
gateways with the highest *adjusted* priority. "
On Thu, Sep 1, 2022 at 9:06 AM Julien Chavanton
wrote:
> Hi,
Hi, did you look at the documentation of algorithm 13 ?
The priority is used in combination with the latency to determine the
preferred gateway.
Once you confirm that this is what you want "latency latency optimized
dispatching", we can help to clarify why and how this may not work as
expected.
Hi Adarsh,
You could consider, since they support SIP OPTION, you will be able to
always use most responsive/closest one first :
13” - latency optimized dispatching
http://www.kamailio.net/docs/modules/devel/modules/dispatcher.html
On Tue, Jan 11, 2022 at 11:27 PM Adarsh Chauhan
wrote:
> Hi
/
>
> Kamailio services – https://gilawa.com
>
>
>
> *From:* sr-users *On Behalf Of *Julien
> Chavanton
> *Sent:* Tuesday, November 30, 2021 10:37 PM
> *To:* Kamailio (SER) - Users Mailing List
> *Subject:* Re: [SR-Users] DMQ Usrloc/Dialog - Experiences
>
>
>
>
e.
>
> Thanks,
> Carsten
> --
> Carsten Bock I CTO & Founder
>
> ng-voice GmbH
>
> Trostbrücke 1 I 20457 Hamburg I Germany
> T +49 179 2021244 I www.ng-voice.com
>
> Registry Office at Local Court Hamburg, HRB 120189
> Managing Directors: Dr. David Bachmann, C
Hi Carsten, from my experience Usrloc + DMQ works very well, rare
replication race conditions are insignificant since the state is quite
volatile anyway.
However you can only have that many nodes, great for clustering.
On Mon, Nov 29, 2021 at 6:47 AM Carsten Bock wrote:
> Hi,
>
> I wanted to
Thanks for sharing Daniel !
On Tue, Sep 7, 2021 at 5:35 AM Giovanni Maruzzelli
wrote:
> Thanks a lot Daniel, much appreciated (#metoo was in holidays).
>
> -giovanni
>
>
>
> On Tue, Sep 7, 2021 at 9:04 AM Daniel-Constantin Mierla
> wrote:
>
>> Hello,
>>
>> the recordings were made private to
On Thu, Apr 22, 2021 at 12:36 AM Giovanni Maruzzelli
wrote:
> On Wed, Apr 21, 2021 at 5:19 PM Julien Chavanton
> wrote:
>
>>
>> Few notes on the mos-lq (listening quality), it consider both losses from
>> jitter (discarded) and never received.
>> I tried t
luded
> into acceptable, warning, or critical ranges.If the call has gone well,
> sipnagios print performance data for Nagios graphs, and returns 0.If the
> call fails, or if its measured values are not inside acceptable ranges, it
> exits with Nagios conventional WARNING or CRITICAL values.
Hi Ivan, must be a limitation/problem in the computation, can you open an
issue.
Since I have built on top of algorithm 11, I could have a look, we may also
notify the original author to see what can be done.
On Tue, Mar 30, 2021 at 8:52 AM Ivan Matvieiev
wrote:
> Hello Community,
>
> There is
Hi Daniel, 25th is the day before thanksgiving, works for me ...
On Tue, Nov 17, 2020 at 3:36 AM Daniel-Constantin Mierla
wrote:
> Hello,
>
> of course you can join and present the status of the LREProxy module --
> note that this is a text chatting online meeting done on a matrix server,
>
degrades (but doesn’t
>> fail) although calls are affected (latency) what we normally do in these
>> cases is force-route to only a specific set of servers from one location
>> until the degradation is over.
>>
>> I almost sure this version of algorithm 13 will handle
gradation is over.
>
> I almost sure this version of algorithm 13 will handle that case totally
> automatic for us.
>
> Really excited about this!
>
> Joel.
>
>
> On Fri, Nov 13, 2020 at 18:10 Julien Chavanton
> wrote:
>
>> I did some load tests today and a
gmail.com> wrote:
>
>> Nice!
>>
>> On Thu, 12 Nov 2020 at 22:01, Julien Chavanton
>> wrote:
>>
>>> About The Algorithm “13” - latency optimized dispatching,
>>>
>>> Is now reviewed once and tested, it will most likely be ready to merge
>>
About The Algorithm “13” - latency optimized dispatching,
Is now reviewed once and tested, it will most likely be ready to merge soon.
I want to share my thoughts on it one more time as it is not too late to
get more feedback before we merge.
I think it is the best algorithm in most use cases,
You could use an htable and wait for the ACK to dlg_bye the caller.
Or you could try rewriting the response and sending dlg_bye to the callee,
just seems less predictable in terms of what can happen.
On Mon, Oct 5, 2020 at 2:47 PM Julien Chavanton
wrote:
> Indeed, the call m
is correct.
On Fri, Sep 25, 2020 at 6:15 PM Julien Chavanton
wrote:
> It seems I found the problem and I have a fix.
>
> The root cause is probably that the locally generated 408 is not updating
> the dialog to-tag.
>
> However, always checking for a to-tag match, before a non to-ta
discussing the option
always matching to-tag first.
On Fri, Sep 25, 2020 at 11:27 AM Julien Chavanton
wrote:
> I did catch the logs, and after looking at the trace, it seems like dialog
> mismatch with a serial forking scenario :
>
> - log line 3 is telling us that a NO-ACK disconne
I did catch the logs, and after looking at the trace, it seems like dialog
mismatch with a serial forking scenario :
- log line 3 is telling us that a NO-ACK disconnection should be triggered
- log line 1-2 is telling us what happened when the ACK was received in
dlg_onroute(), oddly enough state
I created a special branch in case someone wants to propose more
debuggability modifications
https://github.com/kamailio/kamailio/pull/2483
On Wed, Sep 23, 2020 at 10:33 AM Julien Chavanton
wrote:
> I will start isolating to problem with this patch
>
>
>
> On Wed, Sep 23,
I will start isolating to problem with this patch
On Wed, Sep 23, 2020 at 9:17 AM Julien Chavanton
wrote:
> Hi, I am also troubleshooting unexpected no-ack disconnection.
>
> recently I added a modification to catch them before they would take place
> in the logs
AM Julien Chavanton
wrote:
> Hi, I am also troubleshooting unexpected no-ack disconnection.
>
> recently I added a modification to catch them before they would take place
> in the logs
>
>
> commit 2f1338a67579c8fef58deec911d417851ff55cda (tag: v5.3.3.fr.4)
> Author: Julien
Hi, I am also troubleshooting unexpected no-ack disconnection.
recently I added a modification to catch them before they would take place
in the logs
commit 2f1338a67579c8fef58deec911d417851ff55cda (tag: v5.3.3.fr.4)
Author: Julien Chavanton
Date: Fri Jul 24 14:51:02 2020 -0700
dialog
the transactions with delayed processing may be an option to
favor consistency over availability.
I do not think there is such feature in Kamailio, probably because most
transactions can be recreated on the fly.
On Tue, Aug 4, 2020, 09:27 Julien Chavanton wrote:
> So in fact it may simply work with
So in fact it may simply work without any replication, except that you have
to disable the failing server
On Tue, Aug 4, 2020, 08:45 Julien Chavanton wrote:
> You may wonder what kind of failure scenario you are trying to address as
> replication will probably fail as well in many
You may wonder what kind of failure scenario you are trying to address as
replication will probably fail as well in many cases.
One technique would be to use a domain name in the Via, the transaction may
not need to be replicated as it can be recreated by the server receiving
the reply, thanks to
e way to make it work as you want, so let's continue
> there for further discussions.
>
> Cheers,
> Daniel
> On 31.07.20 08:51, Julien Chavanton wrote:
>
> Hi, considering this example :
>
> modparam("acc_json", "acc_missed_flag", 6)
>
> failure_r
Yes ...
On Fri, Jul 31, 2020 at 1:27 PM Daniel-Constantin Mierla
wrote:
> Do you keep float numbers as strings in avps?
>
> Cheers,
> Daniel
> On 30.07.20 21:43, Julien Chavanton wrote:
>
> Yes, this was an example I have for float comparison ...
>
> good, we w
p(var3) and 1
> or 0)");
>
> just assuming is was on your local testing.
>
> Cheers,
> Daniel
> On 30.07.20 18:50, Julien Chavanton wrote:
>
>
> lua_dostring("sr.pv.seti(\"$$var(var1)\", $avp(var1) < $avp(var3) and 1 or
> 0)");
>
> re
lua_dostring("sr.pv.seti(\"$$var(var1)\", $avp(var1) < $avp(var3) and 1 or
0)");
results in error :
kamailio app lual_dostring(): error from Lua: attempt to index global 'sr'
(a nil value)
replacing sr with KSR is working :
lua_dostring("KSR.pv.seti(\"$$var(var1)\", $avp(var1) < $avp(var3) and
This seems standard behavior.
One advise, make sure you clear the xavps between each ds_select unless you
are sure to iterate over the ds_select_next until it is emptied.
On Fri, Jul 10, 2020, 10:51 David VILLAUME wrote:
> Hello,
>
>
>
> Is it possible to use the following logic :
>
>
>
>
e 3 weeks time frame for review and
> merge.
>
> Cheers,
> Daniel
> On 17.06.20 23:08, Julien Chavanton wrote:
>
> I guess we won't have time to merge this one.
>
> https://github.com/kamailio/kamailio/pull/2359
>
> tested locally, a review would be best.
>
&g
I guess we won't have time to merge this one.
https://github.com/kamailio/kamailio/pull/2359
tested locally, a review would be best.
On Tue, Jun 16, 2020, 23:26 Daniel-Constantin Mierla
wrote:
> Hello,
>
> quick reminder that the development for next major release 5.4.0 is
> going to be
s,
>
>
>
> Henning
>
>
>
> --
>
> Henning Westerholt – https://skalatan.de/blog/
>
> Kamailio services – https://gilawa.com
>
>
>
> *From:* sr-dev
> *On Behalf Of *Julien Chavanton
> *Sent:* Thursday, May 14, 2020 7:26 PM
> *To:* Kamailio (SER)
Hi Folks,
Just found another simple use case of the dispatcher latency stats.
Just shraing this idea of a feature I want to contribute.
When using dispatcher algorithm 8:
“8” - select destination sorted by priority attribute value (serial
forking ordered by priority).
If the gateway as the
I hope I am wrong :)
On Fri, May 8, 2020 at 5:33 AM Julien Chavanton
wrote:
>
>
> I started the work, this could have need handled by a Kamailio module,
> before concluding that it would only work with a few endpoints since the
> fact that an endpoint advertise this SDP para
I started the work, this could have need handled by a Kamailio module,
before concluding that it would only work with a few endpoints since the
fact that an endpoint advertise this SDP param does not mean that it is
supporting it when sending.
https://tools.ietf.org/html/rfc3605
a=rtcp:53020
Hi David, I looked into using sdp rtcp address param in the past. It is
only supported by Microsoft.
The IP will always be the same as RTP
Using a different IP address and relaying rtcp packets could be nice
however it would affect RTT computation slightly and not supported...
On Thu, May 7,
Good question, you did clarify that SIP.js, simply waits.
Since then there was some new ideas
https://tools.ietf.org/id/draft-ietf-mmusic-trickle-ice-sip-10.html
For Kamailio it would will probably be already supported.
Would be good to have inputs from SIP.js and RTP engine.
On Fri, May 1,
I do not think this is a client issue, since I was able to connect earlier.
Chromium
Version 81.0.4044.122 (Official Build) snap (64-bit)
Forefix
74.0
On Wed, Apr 29, 2020 at 7:05 AM Julien Chavanton
wrote:
> Error 1 :
> Trying to login
> Unable to connect to Homeserver.
Error 1 :
Trying to login
Unable to connect to Homeserver. Retrying
Error 2 :
Explore rooms :
"Riot failed to get the protocol list from the homeserver. The homeserver
may be too old to support third party networks."
On Wed, Apr 29, 2020 at 6:41 AM Daniel-Constantin Mierla
wrote:
> Hello,
The main gain in using a B2BUA is that you take responsibility for
terminating the extra call legs, it is as good as your B2BUA will be, by
delegating the responsibility upstream you can not always be sure it is
handled properly.
I wonder if Kamailio should consider evolving in B2BUA support.
I
You are right that this is not very explicit.
Kamailio will cancel automatically once one branch connects but if it
failed to cancel (meaning other branches connects)
The originiting UAC will have to disconnect the extra calls.
Which is something that is handled properly by most if not all.
On
Kamailio will use an ephemeral ports (assigned by the kernel) when making
outbound TCP connections, this is recommended for several reasons.
You can google "bind before connect", if you want to find out more about
this concept in Linux socket programming, this can be done to force the
source port
ip_patrol tool. Is the
> xml language for config/scenarios documented?
>
> Cheers,
> Daniel
> On 01.04.20 07:21, Julien Chavanton wrote:
>
> Hi Daniel,
>
> A little late, but I created a quick start doc on how to use voip_patrol
> docker container pre-configured to an
I also have an image for the RTP media server module, I think is it also
coming ready to play a file.
https://hub.docker.com/repository/docker/jchavanton/rtp_media_server
On Tue, Mar 31, 2020 at 10:21 PM Julien Chavanton
wrote:
> Hi Daniel,
>
> A little late, but I created a quick
Hi Daniel,
A little late, but I created a quick start doc on how to use voip_patrol
docker container pre-configured to answer anything and play a file
https://github.com/jchavanton/voip_patrol/blob/quick_start/QUICK_START.md
The docker image is quite large I keep it easily debugable, in this
Setflag is only setting the value of a transaction flag to true. We always
need to make sure each flag as a unique integer value (It will be the bit
position in an int32)
Example:
#!define FLT_ACCMISSED 2
The value 2 must not be used by any other flag, this is one thing you need
to verify.
The
12, 2020 at 2:01 PM Julien Chavanton
wrote:
> 5.3 yes the patch I had in mine is in.
>
> It seems like what you are doing is fine.
> We do not see the definition of your FLAGS in you example I am assuming
> they are not overlapping another flag "bit" that could b
using kamailio 5.3 from debian (installed in ubuntu 16.04)
>> repository.
>>
>> Could you please explain bit more what flag to reset call-id you mean.
>> What does the code you pasted, where it should be in kamailio.cfg?
>>
>> Thanks upfront for explanation!
>
The flag will prevent duplicates. Which version are you using, there was a
patch a few months ago
The explanation shold be that you are resetting them.
Are you using the following, one option to confirm that your logic is good
is add one log line at INFO / NOTICE level logging each time you
Glad to see that pv_isset can be used, I will use this one more, it seems
more consistent than some other alternatives !
On Tue, Jan 21, 2020 at 7:35 AM Ovidiu Sas wrote:
> Here's something that works:
> $xavp(x=>a) = "1";
> $xavp(x[0]=>b) = "2";
> $xavp(x=>a) = "10";
>
This code as it is is useless, unless we print the content or do something
before making the copy but can provide a way to to duplicate/reorder stacks.
Maybe looping over
if (defined $xavp(x[$var(i)]))
Is sufficient, no need to pv_unset
___
Kamailio
work:
> $var(i) = 0;
> while (pv_isset("$xavp(x[$var(i)])")) {
> xavp_copy("x", "$var(i)", "y");
> $var(i) = $var(i) + 1;
> }
>
>
> -ovidiu
>
> On Mon, Jan 20, 2020 at 6:34 PM Julien Chavanton
> wrote:
of the stack?
> This doesn't work:
> $var(i) = 0;
> while (pv_isset("$xavp(x[$var(i)])")) {
> xavp_copy("x", "$var(i)", "y");
> $var(i) = $var(i) + 1;
> }
>
>
> -ovidiu
>
> On Mon, Jan 20,
Hi,
To print all the elements in the stack, you will have to do a while loop.
(You can make a copy using xavp_copy, it may come in handy in some cases)
while (pv_unset("$xavp(name)")) {
// xavp_params_implode
if(!defined $xavp(name)) {
break;
}
}
Or if
3 to 6
Except that you will also accept non 2xx on the BYEs.
SIP accounting and hangup handling can be complicated sometimes.
The accounting module for example will generate ACC events on transactions
completion or missed.
.
On Mon, Dec 30, 2019, 04:06 Duarte Rocha wrote:
> Greetings,
>
>
I also want to share my good thoughts from the Pacific Northwest.
Happy holidays to everyone in this very productive and positive community !
I am glad that we exist !
Special thanks to Daniel and Henning for their huge comitment to this
kamailio.
On Tue, Dec 24, 2019, 11:01 Daniel-Constantin
dy playing with it. Still
> stuck with needing a client certificate, though. I shouldn't need that
> for a client, I'd think. But I'll try my best.
>
> Regards,
> Sebastian
>
> On Wed, Dec 18, 2019 at 7:31 PM Julien Chavanton
> wrote:
> >
> > Hi Sebastian, th
Hi, I know they have a few customisations to SIP and RTP.
Nothing concerning from what I know.
One example the SDP RTCP address, I do not have the RFC on top of my head.
But the certification is probably only needed for them yo list you as a
certified equipment, etc.
On Fri, Nov 29, 2019,
on in the bug report
On Wed, Nov 13, 2019 at 11:44 PM Julien Chavanton
wrote:
> It is running in docker, the interval is not stable ~30sec.
> I know this is not related to DNS slow queries since I am monitoring them
> as well.
> I wonder what else can be intermittently blocking ...
>
ime the VM manager "freezes" the VM for different purposes, like
> backup snapshots, ...
>
> Cheers,
> Daniel
> On 13.11.19 23:40, Julien Chavanton wrote:
>
> I guess action type 16 IF_T is accounting for the entire scope block since
> it is recursive.
>
> I w
/kamailio/kamailio.cfg:115] took too long [2579486 us]
$var(reply) = 0; // I wonder how this can endup blocking ?
On Wed, Nov 13, 2019 at 2:22 PM Julien Chavanton
wrote:
> I am troubleshooting intermittent latency on a server, several processes
> will report slow action at the same time eve
I am troubleshooting intermittent latency on a server, several processes
will report slow action at the same time every now and then,
something odd it that some of the actions are most likely not using any
mutexes, I can not imagine how they can end up blocking unless the process
is actually
Hi Gaurav,
Form my experience,
PJSSIP is one very good option for end to end testing, it is a very RFC
compliant SIP stack, it will fail if anything is wrong and will usually
provide verbose logging explaining why it failed.
If you want to integrate such a CLI tool in CI/CD to provide automated
Did you set them to the public IP address (elastic IP or whatever) on each
of them.
Since you are natted, I guess you are using the listen=udp x.x.x.x
advertise x.x.x.x
parameter.
similar IP preset is needed in this case.
On Mon, Jun 17, 2019 at 12:00 PM Julien Chavanton
wrote:
> Can
Can you share the settings you are using :
modparam("dmq", "server_address", "?")
modparam("dmq", "notification_address", "?")
On Mon, Jun 17, 2019 at 11:30 AM wrote:
> Hi all,
>
> Is there any other way to filter DMQ peers? I now have a issue with
> dmq_usrloc when running in a docker
If we were to implement queue and forward, we could use the mqueue
module/API
This a very simple and elegant module, we could later improve this module,
this would be sinergetic.
On Fri, May 10, 2019 at 12:03 PM Julien Chavanton
wrote:
> Hi Charles,
>
> By the way, great work impleme
timestamp is later.
>
> What do you/others think?
>
> Cheers,
>
> Charles
>
>
> On Thu, 9 May 2019 at 11:57, Julien Chavanton
> wrote:
>
>> I guess, we could simply use tcp with t_relay using only one process in
>> the module.
>>
>> On Thu, May 9, 2
I guess, we could simply use tcp with t_relay using only one process in the
module.
On Thu, May 9, 2019, 04:52 Julien Chavanton wrote:
>
> Yesterday at Kamailio World there was an interesting question, raising a
> concern about replication of user location and DMQ in general, we shoul
Yesterday at Kamailio World there was an interesting question, raising a
concern about replication of user location and DMQ in general, we should
track it in the mailing list and use it as a feature request and I can
share my initial thoughts on the topic.
The concern was about DMQ reordering
This should restore the message in failure route as it was before you
modify it from the main route , call it before anything else that could
modify the message.
t_save_lumps()
On Sat, Apr 27, 2019, 16:02 Sergiu Pojoga wrote:
> Hi ppl,
>
> After a branch route fails, I need to re-evaluate the
Hi, I have used t_replicate a lot in the past, it is a great strait forward
solution in general.
With DMQ_USERLOC, when you restart a node, it will retrieve all the
contacts from the other nodes.
You could try to do that by using a USRLOC DB backend, but I believe you
will may end up facing other
Hi, I missed the meeting, it seems like I needed to register my nickname to
connect but I never received the email from NickServ, was not able to
identify
"
NickServ 08:40:53
You are already logged in as jchavanton.
Please check your email for instructions to complete your registration.
"
On
*https://www.kamailio.org/docs/modules/5.2.x/modules/db_sqlite.html#db_sqlite.p.db_set_journal_mode
<https://www.kamailio.org/docs/modules/5.2.x/modules/db_sqlite.html#db_sqlite.p.db_set_journal_mode>*
On Wed, Feb 27, 2019 at 10:27 AM Julien Chavanton
wrote:
>
> Hi, you can use the
Hi, you can use the WAL mode, so that readers are never delayed.
Just make sure all the connections to the DB are using the WAL mode.
The downside is that the writers can be delayed sometimes, similar to
Postgres read only replica
On Wed, Feb 27, 2019 at 9:57 AM Duarte Rocha
wrote:
>
Thanks updated the issue with the link
On Mon, Feb 11, 2019 at 9:50 AM Daniel Tryba wrote:
> On Mon, Feb 11, 2019 at 09:07:04AM -0800, Julien Chavanton wrote:
> > Hi Marco, not sure if it is the same issue, but I am looking at a
> problem I
> > am facing where in-dialog re
Hi Marco, not sure if it is the same issue, but I am looking at a problem I
am facing where in-dialog requests are failing after 3 minutes.
It seems you are also using topos_redis
Tracing TOPOS traffic is seems some leg related infomation is set to expire
after 3 minutes.
Just sharing in case
The solution that worked for me was to use :
trace_mode=1
This is capturing both version of the message, I think this is about using
a core event hook instead of a transaction callback
3.18. trace_mode (integer)
If set to 1, the module uses core events triggered when receiving or
sending SIP
Not sure if the logs a clear on what/when connection is rejected.
I can share a few troubleshooting hints :
1: Check if you are using the setting require_certificate try to set it to
no and test again.
2: You can verify that you can connect to our proxy using libssl
openssl s_client -showcerts
Quick look at the logs
"tlsv1 alert unknown ca"
This means your CA list does not include lets encrypt, download it from
https://letsencrypt.org/certificates/
Not sure how you generate your ca_list.pem lets encrypt became trusted by
default, at one point on Debian not sure about the exact
Depending on the use case, you could use the dispatcher module latency
stats.
https://kamailio.org/docs/modules/devel/modules/dispatcher.html#dispatcher.p.ds_ping_latency_stats
Regards
On Tue, Jan 15, 2019 at 2:29 AM Daniel Tryba wrote:
> On Sun, Jan 13, 2019 at 10:08:31PM +0300, Soltanici
This is correct, insert_update is used instead of insert when needed and
available by userloc.
This is providing better consistency in some cases, because the insert will
not fail in case of constraint violation but will update instead last one
will prevail.
Not a problem, just a warning to let
t,
> Rogelio
>
>
> On Wed, Aug 22, 2018 at 11:39 AM Julien Chavanton
> wrote:
>
>> Hi Rogerio, did you have any luck digging this leak further ?
>>
>> On Wed, Aug 8, 2018 at 3:37 AM Charles Chance <
>> charles.cha...@sipcentric.com> wrote:
>>
&
write-back)? Do you experience the
> same symptoms if you disable the database completely on the secondary nodes
> (or just one for testing) and instead, enable sync in dmq_usrloc?
>
> Cheers,
>
> Charles
>
>
> On 7 August 2018 at 16:42, Julien Chavanton wrote:
>
>&
I wonder if this could be introduced by a regression or if you are facing a
specific edge case
I briefly looked at the commits of DMQ and DMQ_USRLOC
It seems there was significant work done.
I would give a try with 5.0.0 and then we will at least learn that this is
not a recent regression.
On
Since it seem you are recovering the memory this does not seems like a real
"leak"
One hypothesis :
When you restart a node on the DMQ bus, it can trigger memory usage on the
other nodes since they will start to do a SYNC and send one DMQ message /
contact
It could be that one node in the DMQ
Nice finding ! however Rogelio is saying there was no errors in the logs,
looking at the patch he would have seen some.
LM_ERR("running job failed\n");
Hope I am wrong.
Rogerio is this a slow leak of you mean suddenly it is using 1.5G ?
There can be a lot of shm used by sip_msg_shm_clone if
Hi, I have a scenario where I am using.
t_save_lumps(), lookup() and then I can choose to drop some branches in
branch routes.
However, it is possible that I endup without any branch left, in this case
t_relay() is returning and no failure route is called/created.
At this point I need to recover
1 - 100 of 115 matches
Mail list logo
