Module: sip-router
Branch: master
Commit: 61ecd1118194f5cdbf718fb6072498cabd7bbcd2
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=61ecd11…
Author: Nils Ohlmeier <nils(a)iptel.org>
Committer: Nils Ohlmeier <nils(a)iptel.org>
Date: Tue May 19 02:07:13 2009 +0200
make: excluded modules with radius dependency
- excluded and moved misc_radius and peering modules to the radius
module group to allow to build the basic set of modules without
dependency on radius library being installed.
---
Makefile | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Makefile b/Makefile
index 160f1c4..ca97f78 100644
--- a/Makefile
+++ b/Makefile
@@ -155,7 +155,7 @@ module_group_mysql=acc_db auth_db avp_db db_ops uri_db domain lcr msilo mysql\
speeddial
# For radius
-module_group_radius=acc_radius auth_radius avp_radius
+module_group_radius=acc_radius auth_radius avp_radius misc_radius peering
# For presence
module_group_presence=dialog pa presence_b2b rls xcap
@@ -190,7 +190,7 @@ else
db_unixodbc memcached mi_xmlrpc \
nat_traversal perlvdb purple seas siptrace \
snmpstats uac_redirect xmpp \
- carrierroute
+ carrierroute misc_radius peering
# excluded because they do not compile (remove them only after they are
# fixed) -- andrei
exclude_modules+= avpops bdb dbtext iptrtpproxy pa rls
Hello,
when I call 'make modules' as described in the wiki on a current copy of
the GIT repository the build process tries to build the misc_radius and
peering modules from the modules directory. But both of them fail to
build because of the missing radiusclient-ng.h header on my system
(recent Gentoo Linux). Is this a bug in the build system, or is it now
with sip-router intended behavior that modules with external
dependencies are tried to build?
Thanks
Nils
Hello,
long awaited period of SIP Router integration phase is more and more
approaching the end. Apart of 4 modules that are not integrated yet from
Kamailio - seas, siptrace, uac_redirect and nat_traversal (work being
undertaken) -- the rest of 88 modules are ready for
http://sip-router.org core.
I have created a page to collect guidelines for the default Kamailio
configuration file used with sip-router. I invite all of you to test it,
not only this one, but your private configs as well.
http://sip-router.org/wiki/migration/kamailio-3.0-config
Feel free to add to the wiki page or post questions about it to
sr-users(a)lists.sip-router.org. This is a new list created for users of
sip-router project, you can subscribe to it at:
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
At this stage, sip router can be used with modules from both Kamailio
(OpenSER) and SER projects, mixed in same instance at the same time.
Therefore you can choose the best ones that fit your needs. For Kamailio
(OpenSER) users there is a page that tries to collect new features they
got from SER side (still a lot to add there, hope ser developers will
contribute what they find missing). Another page collects links for ser
and kamailio users to find what the other project brings:
http://sip-router.org/wiki/migration/new-features-for-k-usershttp://sip-router.org/wiki/features/inherited-features
It was not only integration work in the past months, sip router has
quite a bunch of brand new feature. The wiki page to collect the summary
is available at:
http://sip-router.org/wiki/features/new-in-devel
Jan just set online documentation portal, available for web browsing:
http://sip-router.org/docbook/sip-router/branch/master/
Common modules are located in directory 'modules' while kamailio and ser
specific modules can be found under module_k and modules_s. Project's
wiki portal got also good content and it is under heavy work -- note
that everyone can contribute to wiki:
http://sip-router.org/wiki
Couple of core and tm features are not yet integrated or not exactly as
they were in Kamailio. Please report the ones you are missing in your
config at:
http://sip-router.org/wiki/devel/kamailio-integration#tm_and_core_extensions
It is the place that should set the priority rank for integration. I
hope that in 1-2 months time frame to get into beta stage and prepare a
stable release.
Many thanks for those that allocated resources to make things evolve to
this stage and many thanks in advance for those that will start testing
and help improving the sip router project. Beware that is still very
early stage and not recommended for production.
Cheers,
Daniel
PS. Codename 3.0 refers to Kamailio (OpenSER) or SER using sip router
core, there is not a stable release yet.
--
Daniel-Constantin Mierla
http://www.asipto.com/
Module: sip-router
Branch: master
Commit: 3e004ccaddd1d9a671dac012021116c7bda2c733
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=3e004cc…
Author: Miklos Tirpak <miklos(a)iptel.org>
Committer: Miklos Tirpak <miklos(a)iptel.org>
Date: Fri May 15 10:04:50 2009 +0200
@ruri forces parsing the URI.
The entire RURI value is rearly used as it is,
rather its subparts are important. The result of this
patch is that for example @ruri.user and @ruri.host
cause one parsing instead of two when the RURI has
not been parsed yet.
---
select_core.c | 10 ++++++++++
1 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/select_core.c b/select_core.c
index 8f7c0f5..0ecd1c9 100644
--- a/select_core.c
+++ b/select_core.c
@@ -69,6 +69,16 @@
int select_ruri(str* res, select_t* s, struct sip_msg* msg)
{
+ /* Parse the RURI even if it is not needed right now
+ * because the nested select calls can access the
+ * parsed URI in this case.
+ * Go ahead even if the parsing fails, so the
+ * value of the broken RURI can be accessed at least.
+ * Subsequent select calls will fail when they try to parse
+ * the URI anyway. (Miklos)
+ */
+ parse_sip_msg_uri(msg);
+
if (msg->parsed_uri_ok)
select_uri_p = &msg->parsed_uri;