Hello!
After running over a long time stable since having massive problems with
multiple DNS SRV records (see ASTERISK-26738), I got today a new segfault.
I got the attached core (unfortunately I don't have any pcap trace
running any more). But I fear, that this new segfault could be the same
pro
Correction, seems like this requires a bit more architecture than I
anticipated.
Basically, we need to separate this into several files and turn the entire
AstDB concept
into a pluggable module type module.
But, as AstDB is a mandatory module for Asterisk, can we create a situation
where
a plugga
I'll have a look at it.
If I read the code correctly, the AstDB is invoked from the asterisk.c
file, when asterisk is launched.
I think the best would be to add a configuration file like astdb.conf,
which will look something like this:
[general]
engine=builtin ; values can be either builtin, redi
> On 26 Oct 2017, at 15:25, Nir Simionovich wrote:
>
> I suspect the original code didn't change the overall mechanism dramatically,
> it's mainly a new implementation.
> This thing is this - replacing the implementation seems straight forward
> enough, making it configurable, seems
> like a p
I suspect the original code didn't change the overall mechanism
dramatically, it's mainly a new implementation.
This thing is this - replacing the implementation seems straight forward
enough, making it configurable, seems
like a pain in the butt.
On Thu, Oct 26, 2017 at 4:23 PM Olle E. Johansso
> On 26 Oct 2017, at 15:20, Nir Simionovich wrote:
>
> Just looked into the code, this is not a simple task to put a new backend for
> astdb. The code isn't even designed
> for something like that. Judging from what I can tell, and tell me if I'm
> wrong - turning this into a configurable thin
Just looked into the code, this is not a simple task to put a new backend
for astdb. The code isn't even designed
for something like that. Judging from what I can tell, and tell me if I'm
wrong - turning this into a configurable thing
would be more or less an open-heart surgery.
On Thu, Oct 26,
Somewhere in Asterisk space, there’s an old patch where I added ASTDB over
realtime, meaning you can use
any realtime storage. If I remember correctly there was a bit of
chicken-and-egg problem with some astdb
calls happening before realtime got launched, but otherwise it worked just fine
in pr
I'd like to +1 on that idea.
While I'm somewhat reluctant to using mySQL as the base of such a change,
as mySQL is an overkill for AstDB,
having a proper AstDB configurable backend is an interesting thing.
Personally speaking, I would actually prefer
something like Memcache or preferably Redis. Bo
▓██▓██░─
░███░░███░──
──█▒──█─
─▓█▓███░──░▒▓█─▒
──▓███─██▓███───
─▓██──░███──
▓█──░░████▓██▓▒─
█▒─░
10 matches
Mail list logo
