Hi,
regarding ndb_redis,
I have 3 sentinels like this:
"192.168.88.155:26379"
"192.168.88.156:26379"
"192.168.88.157:26379"
So was thinking that I would configure ndb_redis this way:
modparam("ndb_redis", "server",
"name=srvZ;sentinel_group=myredis;sentinel_master=1;sentinel=
PS. Kamailio gives you lots of low-level building blocks that can be used to
stitch together a custom location service, if you want to rewrite
usrloc/registrar. There are quite a few ways to replicate data out of Kamailio
at little to no cost to an external consumer.
But if you want to use the
> On 20 Oct 2023, at 11:34, Jawaid Bazyar wrote:
>
> Would a DMQ cluster with RAM-based store and a relatively small number of
> nodes (say, 5 for example) be able to handle a location table measured in the
> scale of 1 million nodes?
A million rows isn't really that much in contemporary
Would a DMQ cluster with RAM-based store and a relatively small number of nodes
(say, 5 for example) be able to handle a location table measured in the scale
of 1 million nodes?
Has anyone done this before?
I assume DMQ has some provision to prevent loops / etc ?
Wondering about scaling a
> On 20 Oct 2023, at 09:17, Jawaid Bazyar wrote:
>
> Hi Alex,
>
> Well I guess the other effects if any are unclear.
>
> As to what I want..
>
> The goal is to ensure that all the nodes in a large-scale
> geographically-distributed system have routing information to locate the
> dynamic
Hi,
This is one of the effects I was remembering:
" For example NAT pinging is a killer since during each ping cycle all nated
contact are loaded from the DB;"
On 10/20/23, 9:17 AM, "Jawaid Bazyar" mailto:baz...@gmail.com>> wrote:
Hi Alex,
Well I guess the other effects if any are
My point was simply that there's more challenge in the bureaucracy than
technical implementation.
>From a technical standpoint, the corner cases to consider are:
1. Number validity. Sure things that fit into an e.164 and/or recognizable
number patterns are simple. What happens when someone
Hello,
at least for some ideas you can have a look at the p_usrloc module. This
implements a clustered registration database, where the data location is
queried from another database table. In the end you can of course also use
native partition means provided from your database and build it by
Hi Alex,
Well I guess the other effects if any are unclear.
As to what I want..
The goal is to ensure that all the nodes in a large-scale
geographically-distributed system have routing information to locate the
dynamic contacts of registered endpoints.
This requires that information to be
Absolutely like my experience. We also only saw the issue when using TLS in
kamailio, not using SSL for mysql. the advice we received did not make
sense but resolved the problem.
On Fri, 20 Oct 2023 at 14:49, Benoît Panizzon
wrote:
> Hi Antony
>
> > Are you connecting to mysql?
> >
> > We had
Hi Antony
> Are you connecting to mysql?
>
> We had similar sounding issues and adding this to kamailio.cfg made a
> difference
> modparam( "db_mysql", "opt_ssl_mode", 1 )
I am using MySQL, but I didn't deliberately configure it to use SSL.
I'm using TLS for SIP client registration on port
Hi Benoit
Are you connecting to mysql?
We had similar sounding issues and adding this to kamailio.cfg made a
difference
modparam( "db_mysql", "opt_ssl_mode", 1 )
On Fri, 20 Oct 2023 at 11:56, Benoît Panizzon via sr-users <
sr-users@lists.kamailio.org> wrote:
> Hi Gang
>
> I just updated our
Hi Gang
I just updated our dev plattform from 5.6 to 5.7
5.5 was working fine with TLS under Ubuntu Focal.
5.6 under Jammy started to dump cores.
5.7 still shows the same behaviour, usually shortly after a restart.
Oct 20 09:45:01 dev-cpereg01 kamailio[11925]: CRITICAL:
> On 19 Oct 2023, at 18:46, Alex Balashov via sr-users
> wrote:
>
> Would join Kaufman here to say that free-range STIR/SHAKEN implementations in
> the US are limited by the small number of certified authentication providers,
> but presumably the EU version will to some extent avoid
14 matches
Mail list logo
