Hello,
I am introducing Vicente as a new registered developer - he submitted
lately very useful patches to ndb_redis module (e.g., array support in
replies, redis free function for config), new ones being on the pipe --
he can present better his plans or you just watch the commits.
Mainly he will be in charge with ndb_redis module, being a heavy user of
it, but there have been submissions from him to other parts of code, we
welcome improvements and new good features anywhere!
Welcome and looking forward to your contributions!
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - http://asipto.com/u/katu
Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - http://asipto.com/u/kpw
Module: sip-router
Branch: master
Commit: a2f9844c01eb19d42d2a2864213c301c53f9b4ec
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=a2f9844…
Author: Vicente Hernando <vhernando(a)systemonenoc.com>
Committer: Vicente Hernando <vhernando(a)systemonenoc.com>
Date: Wed Jun 20 21:08:19 2012 +0200
ndb_redis: README file update for unix domain socket support.
---
modules/ndb_redis/README | 12 +++++++++---
1 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/modules/ndb_redis/README b/modules/ndb_redis/README
index f66c4db..7d72d58 100644
--- a/modules/ndb_redis/README
+++ b/modules/ndb_redis/README
@@ -96,9 +96,12 @@ Chapter 1. Admin Guide
Specify the details to connect to REDIS server. It takes a list of
attribute=value separated by semicolon, the attributes can be name,
- addr, port and db. Name is a generic identifier to be used with module
- functions. addr and port are the IP address and the port to connect to
- REDIS server. db is the DB number to use (defaults to 0 if not
+ unix, addr, port and db. Name is a generic identifier to be used with
+ module functions. unix is the path to the unix domain socket provided
+ by redis server. addr and port are the IP address and the port to
+ connect to REDIS server. unix and (addr, port) are mutually exclusive.
+ If both appear in same server settings unix domain socket is
+ configured. db is the DB number to use (defaults to 0 if not
specified).
You can set this parameter many times, in case you want to connect to
@@ -111,6 +114,9 @@ Chapter 1. Admin Guide
...
modparam("ndb_redis", "server", "name=srvN;addr=127.0.0.1;port=6379;db=1")
modparam("ndb_redis", "server", "name=srvX;addr=127.0.0.2;port=6379;db=4")
+
+# Unix domain socket
+modparam("ndb_redis", "server", "name=srvY;unix=/tmp/redis.sock;db=3")
...
4. Functions
Kamailio v3.3.0 is out – a major release with a very large number of new
features and improvements.
This release is a result of about 6 months of development and 2 months
of testing from the teams of Kamailio (OpenSER) and SIP Express Router
(SER) projects. Version 3.3.0 comes with 7 brand new modules in addition
to a lot of fresh features in core and old modules. You can read
detailed release notes at:
* http://www.kamailio.org/w/kamailio-v3-3-0-release-notes/
Many thanks to all developers and community members that made possible
this release.
Enjoy SIP routing in a secure, flexible and easier way with Kamailio v3.3.0!
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#237 - Kamailio does not handle HTTP Via: headers in requests and responses
User who did this - Daniel-Constantin Mierla (miconda)
----------
Btw, the sip via was ignored so far by the http clients, not sure what happens in the http proxies ... Not getting the parsing error is probably higher priority, fortunately looks easy enough.
And it just came in my mind, we can hook up in the core for sent replies and replace '\nVia:' with other same-size-and-format token if it is HTTP. Something similar does topoh to hide the SIP sensitive headers. But it is not really that clean, the hook callback impacting all replies, including SIP (even if not replaced, it will be some extra check to detect is sip vs http).
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=237#comment697
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.