Revision: 5913
http://openser.svn.sourceforge.net/openser/?rev=5913&view=rev
Author: miconda
Date: 2009-08-26 18:07:09 +0000 (Wed, 26 Aug 2009)
Log Message:
-----------
- use the dedicated append_branch() in Perl function instead of mk_action()
- avoid lot of pkg operations and fixes the memory leak (reported by James Puckett)
Modified Paths:
--------------
branches/1.5/modules/perl/openserxs.xs
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
according to s domain module documentation
In addition to that domain-level attributes, if any, will be available
as either $fd.<name> or $td.<name>.
i tried like this:
if (lookup_domain("$fd", "$var(from_uri_domain)")) {
xlog("L_INFO", "Got lcr_id <$fd.lcr_id>\n");
but got error at startup:
Aug 26 10:39:10 localhost /usr/sbin/sip-router[9075]: ERROR: <core> [pvapi.c:500]: error searching pvar "fd.lcr_id"
why?
-- juha
Hello everybody,
during the last IRC devel meeting, we pinned end of summer to be the
time to enter testing phase for the new major release - codenamed
kamailio 3.0.
There was quite a lot of brand new features, considering that most of
devel effort was directed to integration. A try to collect new items is
available at:
http://sip-router.org/wiki/features/new-in-devel
Of course, all ser features are available as well, resulting a large
amount of new stuff in kamailio 3.0 vs kamailio 1.5.x. See:
http://sip-router.org/benefits/http://www.iptel.org/ser/features
I propose to start the testing phase sometime next week.
Meanwhile, let's see if something important was forgotten from kamailio
core or tm. To my knowledge:
- path support in tm - Andrei has it on his todo afaik - in a way or
another, it must get in next release
- drop compatibility - drop reply in reply_route - internally drop and
exit are now differentiated by core, needs review and update of handling
after running the routes - on my to-do
Apart seas, all Kamailio modules are fully ugraded to new core - I
started but lack of test env + busy summer resulted in delays - can be
done during testing period, being just api updates.
If you have discovered something else, let us know.
Thanks,
Daniel
--
Daniel-Constantin Mierla
* http://www.asipto.com/