Hello,
looking a bit over our makefiles, I am thinking of simplifying some
parts related to compiler optimizations, as I noticed some of them are
for gcc 2.x. So I would like to see if people are still using old OSes
and/or old GCC versions.
In other words, if you use old or some dedicated systems and plan to
deploy most recent Kamailio versions, reply here with the gcc version in
use, particularly interested to see the use of gcc 2.x or 3.x.
The idea is not to remove the support for it completely, but to simply
and don't try to find all tunings for old versions, but go more with the
default gcc options.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.comhttp://miconda.eu
Hello,
I don't understand why msg_apply changes() can be called from
REQUEST_ROUTE *only*. Can someone explain? Can this be extended to
*FAILURE_ROUTES *also?
Basically I need to call this from FAILURE_ROUTES in order to avoid
double SDP for rtpengine offers. Searching in the mailing list I could
see that there could be other means of handling this like keeping and
reading the SDP from an avp(write/read_sdp_pv), but I find the above
method pretty straightforward.
Thanks,
Stefan
I am trying to create a cluster of Kamailio servers. I want users that are
registered on one server to be able to contact and call users on other
servers. How can I implement this in Kamailio?
PS: My servers are in a private network and I do not have DNS.
Hello,
as a follow up to previous discussions on the mailing list, I would like
to propose Wednesday, Feb 3, 2016 as the day to freeze the development
for next major release. It will allow the people going at Fosdem to chat
and do last minute tunings before freezing.
Other suggestions or comments are welcome!
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.comhttp://miconda.eu
Hi,
While compiling Kamailio 4.3.4 from package sources for Debian 7 Wheezy
(kamailio repository) I'm running into a problem. I've forked the CNXCC
module which I was trying to keep up to date with upstream changes. But
before I could do that, there is a dependency of redis added.
Unfortunately, installing redis devel libs and libevent doesn't provide
the correct version of redis. Also, I noticed on Debian 8 Jessie, it
does compile correctly.
How could Kamailio be compiled for Wheezy with these sources? I'm
missing something obvious I feel. Attached is the compile log, this is
with a completely unaltered sources.
root@devhost:/usr/src/kamailio-4.3.4+wheezy# make -C modules/cnxcc
make: Entering directory `/usr/src/kamailio-4.3.4+wheezy/modules/cnxcc'
CC (gcc) [L libkmi.so.1.0] attr.o
CC (gcc) [L libkmi.so.1.0] fmt.o
CC (gcc) [L libkmi.so.1.0] mi.o
CC (gcc) [L libkmi.so.1.0] tree.o
LD (gcc) [L libkmi.so.1.0] libkmi.so.1.0
CC (gcc) [L libsrdb1.so.1.0] db.o
CC (gcc) [L libsrdb1.so.1.0] db_id.o
CC (gcc) [L libsrdb1.so.1.0] db_pool.o
CC (gcc) [L libsrdb1.so.1.0] db_query.o
CC (gcc) [L libsrdb1.so.1.0] db_res.o
CC (gcc) [L libsrdb1.so.1.0] db_row.o
CC (gcc) [L libsrdb1.so.1.0] db_ut.o
CC (gcc) [L libsrdb1.so.1.0] db_val.o
LD (gcc) [L libsrdb1.so.1.0] libsrdb1.so.1.0
CC (gcc) [L libkcore.so.1.0] cmpapi.o
CC (gcc) [L libkcore.so.1.0] faked_msg.o
CC (gcc) [L libkcore.so.1.0] kstats_wrapper.o
CC (gcc) [L libkcore.so.1.0] parse_privacy.o
CC (gcc) [L libkcore.so.1.0] parse_sst.o
CC (gcc) [L libkcore.so.1.0] regexp.o
CC (gcc) [L libkcore.so.1.0] statistics.o
CC (gcc) [L libkcore.so.1.0] strcommon.o
LD (gcc) [L libkcore.so.1.0] libkcore.so.1.0
LD (gcc) [M cnxcc.so] cnxcc.so
cnxcc_mod.o: In function `redisLibeventReadEvent':
/usr/include/hiredis/adapters/libevent.h:10: multiple definition of
`redisLibeventReadEvent'
cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:10: first defined
here
cnxcc_mod.o: In function `redisLibeventWriteEvent':
/usr/include/hiredis/adapters/libevent.h:16: multiple definition of
`redisLibeventWriteEvent'
cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:16: first defined
here
cnxcc_mod.o: In function `redisLibeventAddRead':
/usr/include/hiredis/adapters/libevent.h:22: multiple definition of
`redisLibeventAddRead'
cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:22: first defined
here
cnxcc_mod.o: In function `redisLibeventDelRead':
/usr/include/hiredis/adapters/libevent.h:27: multiple definition of
`redisLibeventDelRead'
cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:27: first defined
here
cnxcc_mod.o: In function `redisLibeventAddWrite':
/usr/include/hiredis/adapters/libevent.h:32: multiple definition of
`redisLibeventAddWrite'
cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:32: first defined
here
cnxcc_mod.o: In function `redisLibeventDelWrite':
/usr/include/hiredis/adapters/libevent.h:37: multiple definition of
`redisLibeventDelWrite'
cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:37: first defined
here
cnxcc_mod.o: In function `redisLibeventCleanup':
/usr/include/hiredis/adapters/libevent.h:42: multiple definition of
`redisLibeventCleanup'
cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:42: first defined
here
cnxcc_mod.o: In function `redisLibeventAttach':
/usr/include/hiredis/adapters/libevent.h:49: multiple definition of
`redisLibeventAttach'
cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:49: first defined
here
cnxcc_redis.o: In function `redisLibeventReadEvent':
/usr/include/hiredis/adapters/libevent.h:10: multiple definition of
`redisLibeventReadEvent'
cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:10: first defined
here
cnxcc_redis.o: In function `redisLibeventWriteEvent':
/usr/include/hiredis/adapters/libevent.h:16: multiple definition of
`redisLibeventWriteEvent'
cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:16: first defined
here
cnxcc_redis.o: In function `redisLibeventAddRead':
/usr/include/hiredis/adapters/libevent.h:22: multiple definition of
`redisLibeventAddRead'
cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:22: first defined
here
cnxcc_redis.o: In function `redisLibeventDelRead':
/usr/include/hiredis/adapters/libevent.h:27: multiple definition of
`redisLibeventDelRead'
cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:27: first defined
here
cnxcc_redis.o: In function `redisLibeventAddWrite':
/usr/include/hiredis/adapters/libevent.h:32: multiple definition of
`redisLibeventAddWrite'
cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:32: first defined
here
cnxcc_redis.o: In function `redisLibeventDelWrite':
/usr/include/hiredis/adapters/libevent.h:37: multiple definition of
`redisLibeventDelWrite'
cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:37: first defined
here
cnxcc_redis.o: In function `redisLibeventCleanup':
/usr/include/hiredis/adapters/libevent.h:42: multiple definition of
`redisLibeventCleanup'
cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:42: first defined
here
cnxcc_redis.o: In function `redisLibeventAttach':
/usr/include/hiredis/adapters/libevent.h:49: multiple definition of
`redisLibeventAttach'
cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:49: first defined
here
collect2: error: ld returned 1 exit status
make: *** [cnxcc.so] Error 1
make: Leaving directory `/usr/src/kamailio-4.3.4+wheezy/modules/cnxcc'
Cheers,
Dirk
Hello.
I feel like a total idiot.
I was inspecting the various GitHub branches for Kamailio using a GitHub
visual client, and I think I managed to accidentally merge a branch back
into master.
The branch I was inspecting was 'lazedo/presence_improvements'.
I was inspecting diffs and branches, and was amazed that I was able to
screw up so badly with one single click, but I guess that's the danger of a
visual git client.
Anyway, before trying to do anything more, I figured I'd asked for advice,
because I don't want to screw up further.
Hopefully there's a simple way to revert the accidental merge, but I first
wanted to confirm that I actually did make that mistake, and that it's
visible to others.
Thanks.
Hello there,
Can anyone tell me what is the exactly memory size that kamailio use for
one sip register saved on memory?
How much memory i need allocate to kamailio in order to support 50.000
subscribers.
Best Regards
Hello,
only few days left, so we need to nail the location down for Kamailio
dinner at Fosdem.
One suggestion in walking distance is:
- http://restaurant-italien-picotin-bruxelles.be/en
I understood that it was used in the past also for Fosdem Speaker's
Dinner, so it might be busy and we can't get the seats. So new
suggestions are more than welcome in order to have some backups to try!
If there is no strong preference for something else by end of today,
tomorrow we should attempt to do the reservation at this place.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.comhttp://miconda.eu