Hi Marius,
since you did some updates to this module, I am opening for debate some
needed enhancements I did during 3.0 testing phase and want to get
opinions how to get in the code repo.
Practically is a new module I named for now ratelimit2 and my last idea
is to get it named pipelimit in the trunk.
The reason for a new module are some major changes. The module uses the
same algorithm but its core is overhaul.
- definitions of pipes are loaded from database
- there can be unlimited number of pipes
- pipes are identified by string names
- should be possible to reload pipes at runtime (iirc, not yet in)
- new pipes can be added at runtime
- functions accept variables to identify the pipe
Since I never used queues from this module and haven't spent time to
understand the concept behind, this functionality is completely missing.
The old module might be good to keep in place, probably many people are
using it in this form. So, proposals? What is the way to go on? Common
code (algorithms) can be made lib at some point.
Cheers,
Daniel
--
Daniel-Constantin Mierla
* http://www.asipto.com/
Hello,
a reminder for developers to write a short note for each new feature
either to NEWS file in source tree or to wiki page:
http://sip-router.org/wiki/features/new-in-devel
Makes life much easier when the next major release is going to happen
and help people to spot quickly what new features are already available
in devel branch, hopefully attracting some of them to go for it and test.
Now the wiki page is updated with most of NEWS content for 3.1.
Thanks,
Daniel
--
Daniel-Constantin Mierla
Kamailio SIP Router Masterclass, Berlin, March 22-26, 2010
* http://www.asipto.com/index.php/sip-router-masterclass/
Hello,
I am going to visit CeBIT 2010 in Hannover next week. Drop me an email
if you are around and want to meet and chat about Kamailio, SIP Router
projects, etc.
Cheers,
Daniel
--
Daniel-Constantin Mierla
Kamailio SIP Router Masterclass, Berlin, March 22-26, 2010
* http://www.asipto.com/index.php/sip-router-masterclass/
Hi, I'm dealing with presence right now. I've read full OMA and RCS
specifications/proposals/guidelines for presence and XCAP but I don't feel
comfortable with some parts of them.
So let me to explain the question (it involves the sr/kamailio presence module
behavior for a future re-design in which I want to participate):
In presence/XCAP/XDM there are three ways bob can deny alice to see his
presence status (by modifying the XCAP documents according):
1) Ignore alice's request. This is, bob doesn't "allow" neither "blocks"
alice, so alice just gets the first NOTIFY from the server with:
Subscription-Status: pending
After some long time the server will send:
Subscription-Status: terminated ; reason=expired
2) Block alice by invoking a "block" action. This means that alice receives a
NOTIFY from the server with:
Subscription-Status: terminated; reason=rejected
This is: alice *knows* that she has been explicitely blocked by bob.
3) Polite-block alice by invoking "polite-block" action. In this way the
presence server generates a spoofed NOTIFY for alice containing "offline"
information but the header:
Subscription-Status: active
This is: alice *things* she has been allowed by bob and bob it's offline right
now (not true).
Well, in real IM/presence world (MSN, Skype, XMPP, Yahoo...) option 2 doesn't
exist, am I right? This is, if you block an user he doesn't know that you have
blocked him. Instead just options 1 or 3 are used (and in some networks just
option 1).
Do you see any advantage in point 2? Personally I don't see it and it just
introduces too much complexity for presence/XCAP/XDM client developers.
I would appreciate your opinnions about it.
Thanks.
--
Iñaki Baz Castillo <ibc(a)aliax.net>
Module: sip-router
Branch: master
Commit: 2372a7d5039a72f9cdb6b8bb7acb8a5ae2cb5c5f
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=2372a7d…
Author: Henning Westerholt <henning.westerholt(a)1und1.de>
Committer: Henning Westerholt <henning.westerholt(a)1und1.de>
Date: Wed Feb 24 17:04:54 2010 +0100
userblacklist(k): short term fix in the docs for redundant table definition
---
modules_k/userblacklist/README | 12 +++++++-----
modules_k/userblacklist/doc/userblacklist_db.xml | 4 +++-
2 files changed, 10 insertions(+), 6 deletions(-)
diff --git a/modules_k/userblacklist/README b/modules_k/userblacklist/README
index 3d7927a..5e0c242 100644
--- a/modules_k/userblacklist/README
+++ b/modules_k/userblacklist/README
@@ -187,7 +187,7 @@ modparam("userblacklist", "use_domain", 0)
4.3. check_blacklist (string table)
-4.1. check_user_blacklist (string user, string domain, string number, string
+4.1. check_user_blacklist (string user, string domain, string number, string
table)
Finds the longest prefix that matches the request URI user (or the
@@ -208,7 +208,7 @@ if (!check_user_blacklist("$avp(i:80)", "$avp(i:82)"))
}
...
-4.2. check_user_whitelist (string user, string domain, string number, string
+4.2. check_user_whitelist (string user, string domain, string number, string
table)
Finds the longest prefix that matches the request URI user (or the
@@ -229,7 +229,7 @@ if (!check_user_whitelist("$avp(i:80)", "$avp(i:82)"))
}
...
-4.3. check_blacklist (string table)
+4.3. check_blacklist (string table)
Finds the longest prefix that matches the request URI for the given
table. If a match is found and it is not set to whitelist, false is
@@ -247,7 +247,7 @@ if (!check_blacklist("global_blacklist")))
5.1. reload_blacklist
-5.1. reload_blacklist
+5.1. reload_blacklist
Reload the internal global blacklist cache. This is necessary after the
database tables for the global blacklist have been changed.
@@ -399,7 +399,9 @@ modparam("userblacklist", "userblacklist_whitelist_col", "whitelist")
8. globalblacklist_table (String)
- Name of the globalblacklist table for the userblacklist module.
+ Name of the globalblacklist table for the userblacklist module. Please
+ not that this table is currently ignored, the table needs to be given
+ as a parameter for the check_blacklist function.
Default value is "globalblacklist".
diff --git a/modules_k/userblacklist/doc/userblacklist_db.xml b/modules_k/userblacklist/doc/userblacklist_db.xml
index f4d2585..5e8df9c 100644
--- a/modules_k/userblacklist/doc/userblacklist_db.xml
+++ b/modules_k/userblacklist/doc/userblacklist_db.xml
@@ -111,7 +111,9 @@ modparam("userblacklist", "userblacklist_whitelist_col", "whitelist")
</section>
<section>
<title><varname>globalblacklist_table</varname> (String)</title>
- <para>Name of the globalblacklist table for the userblacklist module.</para>
+ <para>Name of the globalblacklist table for the userblacklist module.
+ Please not that this table is currently ignored, the table needs to be
+ given as a parameter for the check_blacklist function.</para>
<para>
<emphasis>Default value is <quote>globalblacklist</quote>.</emphasis>
</para>
Revision: 5990
http://openser.svn.sourceforge.net/openser/?rev=5990&view=rev
Author: henningw
Date: 2010-02-24 16:01:34 +0000 (Wed, 24 Feb 2010)
Log Message:
-----------
* add a small note about the global blacklist table
this will be fixed more thoroughly in the upstream
Modified Paths:
--------------
branches/1.5/modules/userblacklist/README
branches/1.5/modules/userblacklist/doc/userblacklist_db.xml
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A user has added themself to the list of users assigned to this task.
FS#38 - make install overwrites existing tls.cfg file
User who did this - Klaus Darilion (klaus3000)
http://sip-router.org/tracker/index.php?do=details&task_id=38
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Klaus Darilion (klaus3000)
Attached to Project - sip-router
Summary - make install overwrites existing tls.cfg file
Task Type - Bug Report
Category - Core
Status - Assigned
Assigned To - Andrei Pelinescu-Onciul
Operating System - All
Severity - Low
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - at least when using kamailio 3.0 a "make install" overwrites the existing tls.cfg :-(
damn!
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=38
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.