Hello,
following the IRC devel meeting that just ended, I am trying to identify
the compile time options that are relevant to build for. The goal is to
detect if changes that compile fine with some of those options, don't
break the compilation when options are different.
In my mind comes only those related to memory debugging. So the builds
should be:
A) Using PKG malloc
1) memory debugging turned off
MEMDBG=0 make ...
2) memory debugging turned on
MEMDBG=1 make
B) compile with system malloc instead of pkg malloc
-DPKG_MALLOC needs to be removed from Makefile.defs
Not really relevant here, -DDBG_SYS_MALLOC can be added to compile flags
as a second time compile.
I will try to simplify setting this options, so for now A would be good
to have.
Besides these, I wonder if people here use other compile flags that the
default one, in order to identify what other combination of flags should
be used for testing that compilation is done ok.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
Kamailio Advanced Training, Sep 28-30, 2015, in Berlin - http://asipto.com/u/kat
Hello,
I would like to propose organizing the next IRC devel meeting to sync on
the plans for Kamailio short term evolution. A wiki page has been
created to keep track of what should be discussed there. Feel free to
add your suggestions there:
* http://www.kamailio.org/wiki/devel/irc-meetings/2015b
First proposed date is next week on Wednesday, September 16, at 14:00
UTC (15:00 London, 16:00 Berlin, ...). The date can be changed based on
availability of people willing to attend -- add your preferred date and
time there.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
Kamailio Advanced Training, Sep 28-30, 2015, in Berlin - http://asipto.com/u/kat
Hi,
We're trying to build a db replication based kamailio server redundancy solution. In recent tests, it seems to make more sense to change the db_mode to 2 (write-back) instead of using db only mode, as in db only mode, a lot of commands and stats don't work anymore.
At this point, we're very close to make this work. However, there is a potential issue I just discovered. When db replicates users/clients registered with other servers in the cluster, although the lookup("location") function can correctly identify the remote users (registered with other servers in the cluster), the db write-back seems to still include those users when loading users/contacts to AoRs in memory. It is just that the remote contacts don't have "socket" information in AoR. Just wonder why the remote users need to be loaded back to memory AoR at all. Should the db write-back be consistent with the lookup function in that the non-local users be filtered out from the AoR?
So far, even with remote contacts in AoR we can still make this work, but it seems a waste of memory to load remote contacts without sockets on each server. Hope I didn't miss any design decision/principle that calls for AoR for both local and non-local users.
Thanks,
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/325
There is a small error in the [srv_query ()](http://kamailio.org/docs/modules/4.3.x/modules/ipops.html#ipops.f.srv_query) documentation. The xlog statements put the closing quotes in the wrong location. They should be as shown below.
xlog ("port[$var(i)] $srvquery(udp=>port[$var(i)])\n");
xlog ("priority[$var(i)] $srvquery(udp=>priority[$var(i)])\n");
xlog ("target[$var(i)] $srvquery(udp=>target[$var(i)])\n");
xlog ("weight[$var(i)] $srvquery(udp=>weight[$var(i)])\n");
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/327