Hi everyone,
just a short request for comments:
Similar to the dialog-variables, which i implemented in my IMS branch
recently, i need something similar for usrloc. Basically, i need to
store additional data to a registration; which i can access after
"lookup()" or upon a "is_registered()" call. Basically:
$reg_var(test) = "some value";
save();
- - -
lookup();
xlog("reg_var(test) is $reg_var(test)\n");
Now there are different approaches:
1) implement this funtionality in usrloc/registrar directly (similar
to my dialog-pvar-implementation). The performance when doing this
impact should be minor if not used, since simply an empty pointer
would be carried along every registration. This would be the cleanest
way to do this; but however since many people are using usrloc i have
a little respect doing changes on such core-module. Maybe it could be
implemented as a change in usrloc and a dedicated module just for
getting and setting the values.
2) another way would be to implement this in a dedicated module. This
would mean, that i would not touch usrloc module and it would of
course have no impact on "regular" usrloc usage at all if not used. I
would have to add a second list of in-memory values, which would have
to be synched with db, a second timer to do so. The list would be
dependent on the usrloc callbacks. There is always the danger
data-inconsistency.
3) is there any way, to do this with some event-routes,
shared-variables or something similar?
Any thoughts?
Comments very welcome!
Kind regards,
Carsten
P.S.: If i do not receive any comments, i would implement the first
approach (directly in usrloc/registrar) in my IMS-branch for later
merging into master.
Hello,
Kamailio SIP Server v3.1.2 stable release is out.
This is a maintenance release of latest stable branch, 3.1, that
includes fixes since release of v3.1.1. There is no change to database
or configuration file required to upgrade to 3.1.2 from 3.1.0 or 3.1.1
versions, therefore it is strongly recommended to upgrade to v3.1.2.
For more details about version 3.1.2, visit:
http://www.kamailio.org/w/2011/02/kamailio-v3-1-2-released/
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com
Revision: 6053
http://openser.svn.sourceforge.net/openser/?rev=6053&view=rev
Author: timoreimann
Date: 2011-02-08 16:03:20 +0000 (Tue, 08 Feb 2011)
Log Message:
-----------
dialog: added missing parameter in example
Backport from git commit 1705424e70650ae0d173227221b04d1160c3e2c4.
Modified Paths:
--------------
branches/1.5/modules/dialog/doc/dialog_admin.xml
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
Revision: 6052
http://openser.svn.sourceforge.net/openser/?rev=6052&view=rev
Author: timoreimann
Date: 2011-02-08 13:24:35 +0000 (Tue, 08 Feb 2011)
Log Message:
-----------
modules/dialog: set null value parameter for get_dlg_profile() with 2
params
- because of using same internal function for cfg get_dlg_profile(...),
when only 2 params were provided, the third was unpredicted and not
null most probably, potentially resulting in a crash
- reported by Eugene Oden
Backport from git commit 028e3cc1a34f1e682d604a7c0e3fb1a7da03a211.
Modified Paths:
--------------
branches/1.5/modules/dialog/dialog.c
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
Module: sip-router
Branch: 3.1
Commit: ce67a1bad7ca3e7964fba33eb6537e2e4ff3666a
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=ce67a1b…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: Sat Jan 29 20:51:07 2011 +0100
acc: fixed typo in example
- updated the route types where acc_*_request() can be used
---
modules_k/acc/README | 8 ++++----
modules_k/acc/doc/acc_admin.xml | 8 ++++----
2 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/modules_k/acc/README b/modules_k/acc/README
index 3e38cdc..1075a7c 100644
--- a/modules_k/acc/README
+++ b/modules_k/acc/README
@@ -859,7 +859,7 @@ modparam("acc", "diameter_extra", "7846=$hdr(Content-type);7847=$avp(s:email)")
Meaning of the parameters is as follows:
* comment - Comment to be appended.
- This function can be used from REQUEST_ROUTE, FAILURE_ROUTE.
+ This function can be used from ANY_ROUTE.
Example 1.35. acc_log_request usage
...
@@ -876,7 +876,7 @@ acc_log_request("Some comment");
* comment - Comment to be appended.
* table - Database table to be used.
- This function can be used from REQUEST_ROUTE, FAILURE_ROUTE.
+ This function can be used from ANY_ROUTE.
Example 1.36. acc_db_request usage
...
@@ -891,7 +891,7 @@ acc_log_request("Some comment", "Some table");
Meaning of the parameters is as follows:
* comment - Comment to be appended.
- This function can be used from REQUEST_ROUTE, FAILURE_ROUTE.
+ This function can be used from ANY_ROUTE.
Example 1.37. acc_rad_request usage
...
@@ -906,7 +906,7 @@ acc_rad_request("Some comment");
Meaning of the parameters is as follows:
* comment - Comment to be appended.
- This function can be used from REQUEST_ROUTE, FAILURE_ROUTE.
+ This function can be used from ANY_ROUTE.
Example 1.38. acc_diam_request usage
...
diff --git a/modules_k/acc/doc/acc_admin.xml b/modules_k/acc/doc/acc_admin.xml
index 82184fa..fadf022 100644
--- a/modules_k/acc/doc/acc_admin.xml
+++ b/modules_k/acc/doc/acc_admin.xml
@@ -968,7 +968,7 @@ modparam("acc", "diameter_extra", "7846=$hdr(Content-type);7847=$avp(s:email)")
</listitem>
</itemizedlist>
<para>
- This function can be used from REQUEST_ROUTE, FAILURE_ROUTE.
+ This function can be used from ANY_ROUTE.
</para>
<example>
<title>acc_log_request usage</title>
@@ -1001,7 +1001,7 @@ acc_log_request("Some comment");
</listitem>
</itemizedlist>
<para>
- This function can be used from REQUEST_ROUTE, FAILURE_ROUTE.
+ This function can be used from ANY_ROUTE.
</para>
<example>
<title>acc_db_request usage</title>
@@ -1031,7 +1031,7 @@ acc_log_request("Some comment", "Some table");
</listitem>
</itemizedlist>
<para>
- This function can be used from REQUEST_ROUTE, FAILURE_ROUTE.
+ This function can be used from ANY_ROUTE.
</para>
<example>
<title>acc_rad_request usage</title>
@@ -1060,7 +1060,7 @@ acc_rad_request("Some comment");
</listitem>
</itemizedlist>
<para>
- This function can be used from REQUEST_ROUTE, FAILURE_ROUTE.
+ This function can be used from ANY_ROUTE.
</para>
<example>
<title>acc_diam_request usage</title>