Revision: 5948
http://openser.svn.sourceforge.net/openser/?rev=5948&view=rev
Author: eliasbaixas
Date: 2009-10-23 12:16:17 +0000 (Fri, 23 Oct 2009)
Log Message:
-----------
Fixed a core-dump
Modified Paths:
--------------
branches/1.4/modules/seas/seas_action.c
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
Revision: 5947
http://openser.svn.sourceforge.net/openser/?rev=5947&view=rev
Author: mariuszbihlei
Date: 2009-10-23 11:41:54 +0000 (Fri, 23 Oct 2009)
Log Message:
-----------
Try to fix a crash (segmentation fault) in k1.3 in the get_carrier_tree function (NULL pointer deref)
Modified Paths:
--------------
branches/1.3/modules/carrierroute/carrier_tree.c
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
But not in XML format...
The readme doesn't state the copyright either.
On the other hand, the source is well documented! A good example!
One plus, one minus, Alfred :-)
/O
Module: sip-router
Branch: master
Commit: 54d552f42a188f231df33402612215f6f8bd703f
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=54d552f…
Author: oej <oej(a)edvina.net>
Committer: oej <oej(a)edvina.net>
Date: Thu Oct 22 22:15:28 2009 +0200
Updating SER to SIP-router, spelling fixes
---
modules_s/sanity/README | 29 +++++++++++++++--------------
modules_s/sanity/doc/functions.xml | 10 ++++++++--
modules_s/sanity/doc/params.xml | 16 +++++++++++-----
modules_s/sanity/doc/sanity.xml | 10 +++++-----
4 files changed, 39 insertions(+), 26 deletions(-)
diff --git a/modules_s/sanity/README b/modules_s/sanity/README
index 3bab7b4..0e364e3 100644
--- a/modules_s/sanity/README
+++ b/modules_s/sanity/README
@@ -25,20 +25,21 @@ Nils Ohlmeier
This module aims to implement several sanity checks on incoming
requests which are suggested or even required by a RFC, but are not
- available yet in the core of SER.
+ available yet in the core of SIP-router.
- This checks are not required by SER itself for its functionality. But
- on the other side it makes not much sence if a broken request traverses
- through a SIP network if it is rejected sooner or later by a SIP device
- any way. As every sanity cost extra performance because of additional
- parsing and evaluation it is now with this module up to the SER
- adminstrator which checks should be done on which request.
+ This checks are not required by SIP-router itself for its
+ functionality. But on the other side it makes not much sence if a
+ broken request traverses through a SIP network if it is rejected sooner
+ or later by a SIP device any way. As every sanity cost extra
+ performance because of additional parsing and evaluation it is now with
+ this module up to the SIP-router adminstrator which checks should be
+ done on which request.
The following checks are available:
* ruri sip version - (1) - checks if the SIP version in the request
URI is supported, currently only 2.0.
* ruri scheme - (2) - checks if the URI scheme of the request URI is
- supported (sip[s]|tel[s]) by SER.
+ supported (sip[s]|tel[s]) by SIP-router.
* required headers - (4) -checks if the minimum set of required
headers to, from, cseq, callid and via is present in the request.
* via sip version - (8) - not working because parser fails already
@@ -57,7 +58,7 @@ Nils Ohlmeier
header are present in the list of the extensions from the module
parameter proxy_require.
* parse uri's - (1024) - checks if the specified URIs are present and
- parseable by the SER parsers
+ parseable by the SIP-router parsers
* digest credentials (2048) Check all instances of digest credentials
in a message. The test checks whether there are all required digest
parameters and have meaningful values.
@@ -100,10 +101,10 @@ modparam("sanity", "default_checks", "1")
1.3.3. proxy_require (string)
- This parameter set the list of supported extensions for this SER. The
- value is expected as comma seperated list of the extensions. This list
- is seperated into single tokens. Each token from a proxy require header
- will be compare to the tokens from this list.
+ This parameter set the list of supported extensions for this
+ SIP-router. The value is expected as comma separated list of the
+ extensions. This list is separated into single tokens. Each token from
+ a proxy require header will be compare to the tokens from this list.
Example 2. Set proxy_require parameter
...
@@ -115,7 +116,7 @@ modparam("sanity", "proxy_require", "foo, bar")
Revision History
Revision $Revision$ $Date$
-1.4.1. sanity_check()
+1.4.1. sanity_check()
This function makes a row of sanity checks on the given request. The
function returns true if one of the checks failed. If one of the checks
diff --git a/modules_s/sanity/doc/functions.xml b/modules_s/sanity/doc/functions.xml
index 1d60930..85f788d 100644
--- a/modules_s/sanity/doc/functions.xml
+++ b/modules_s/sanity/doc/functions.xml
@@ -1,6 +1,12 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!-- Include general documentation entities -->
+<!ENTITY % docentities SYSTEM "../../../docbook/entities.xml">
+%docentities;
+
+]>
<section id="options.functions" xmlns:xi="http://www.w3.org/2001/XInclude">
<sectioninfo>
diff --git a/modules_s/sanity/doc/params.xml b/modules_s/sanity/doc/params.xml
index 82b31df..b56affd 100644
--- a/modules_s/sanity/doc/params.xml
+++ b/modules_s/sanity/doc/params.xml
@@ -1,6 +1,12 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!-- Include general documentation entities -->
+<!ENTITY % docentities SYSTEM "../../../docbook/entities.xml">
+%docentities;
+
+]>
<section id="sanity.parameters" xmlns:xi="http://www.w3.org/2001/XInclude">
<sectioninfo>
@@ -54,9 +60,9 @@ modparam("sanity", "default_checks", "1")
<section id="proxy_require">
<title><varname>proxy_require</varname> (string)</title>
<para>
- This parameter set the list of supported extensions for this SER.
- The value is expected as comma seperated list of the extensions.
- This list is seperated into single tokens. Each token from
+ This parameter set the list of supported extensions for this SIP-router.
+ The value is expected as comma separated list of the extensions.
+ This list is separated into single tokens. Each token from
a proxy require header will be compare to the tokens from this
list.
</para>
diff --git a/modules_s/sanity/doc/sanity.xml b/modules_s/sanity/doc/sanity.xml
index c808cf5..9e3accc 100644
--- a/modules_s/sanity/doc/sanity.xml
+++ b/modules_s/sanity/doc/sanity.xml
@@ -33,15 +33,15 @@
<para>
This module aims to implement several sanity checks on incoming
requests which are suggested or even required by a RFC, but are
- not available yet in the core of SER.
+ not available yet in the core of SIP-router.
</para>
<para>
- This checks are not required by SER itself for its functionality.
+ This checks are not required by SIP-router itself for its functionality.
But on the other side it makes not much sence if a broken
request traverses through a SIP network if it is rejected sooner
or later by a SIP device any way. As every sanity cost extra
performance because of additional parsing and evaluation it
- is now with this module up to the SER adminstrator which checks
+ is now with this module up to the SIP-router adminstrator which checks
should be done on which request.
</para>
<para>
@@ -56,7 +56,7 @@
<listitem>
<para>
ruri scheme - (2) - checks if the URI scheme of the request URI is
- supported (sip[s]|tel[s]) by SER.
+ supported (sip[s]|tel[s]) by SIP-router.
</para>
</listitem>
<listitem>
@@ -111,7 +111,7 @@
<listitem>
<para>
parse uri's - (1024) - checks if the specified URIs are present and
- parseable by the SER parsers
+ parseable by the SIP-router parsers
</para>
</listitem>
<listitem>
Module: sip-router
Branch: master
Commit: 2723ba88d9d061c9c33534983024bc0e6e3d2099
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=2723ba8…
Author: oej <oej(a)edvina.net>
Committer: oej <oej(a)edvina.net>
Date: Thu Oct 22 21:11:09 2009 +0200
Documentation updates
These documentation files contains a lot of promises about future
development. I think that belongs to todo's, maybe not to the documentation.
---
modules_s/presence_b2b/README | 32 +++++++++++++-------------
modules_s/presence_b2b/doc/functions.xml | 2 +-
modules_s/presence_b2b/doc/params.xml | 10 ++++++-
modules_s/presence_b2b/doc/presence_b2b.xml | 26 +++++++++++++--------
version.h | 8 ++++++
5 files changed, 49 insertions(+), 29 deletions(-)
diff --git a/modules_s/presence_b2b/README b/modules_s/presence_b2b/README
index 09781f1..3c8ba81 100644
--- a/modules_s/presence_b2b/README
+++ b/modules_s/presence_b2b/README
@@ -15,26 +15,26 @@ Vaclav Kubart
future it will do subscriptions to reg events and presence with
resource lists too.
- It is accessible only using internal Querry Status API (QSA).
- Everywhere (in C code) you need subscriptions to presentity status, you
- only create an internal subscription to it and the rest is done by this
- module. It processes internal subscription and creates a SIP
- subscription (SUBSCRIBE-NOTIFY dialog) to requested presentity. Every
- NOTIFY request produces new QSA message with status information into
- destination message queue.
+ It is accessible only using the internal Query Status API (QSA).
+ Everywhere (in the C code) where you need subscriptions to presentity
+ status, you only create an internal subscription to it and the rest is
+ done by this module. It processes the internal subscription and creates
+ a SIP subscription (SUBSCRIBE-NOTIFY dialog) to requested presentity.
+ Every NOTIFY request produces new QSA message with status information
+ into destination message queue.
Instead of this module can be used PA module with parameter
accept_internal_subscriptions set to 1. In that case the subscription
will be only to internal status hold by PA.
- For every requested (record, subscriber) is created new SIP
- subscription! This is due to authorization of such subscriptions - B2B
- UA can't decide about authorization rules, thus it has to leave it on
- the presence server to which it creates the subscription and this
- means, that it has to create the subscription as the subscriber. There
- is a possibility to do subscriptions with the same To + From only once,
- but this is left for future optimalizations (it will probably not help
- a lot).
+ For every requested (record, subscriber) a new SIP subscription is
+ created. This is due to authorization of such subscriptions - B2B UA
+ can't decide about authorization rules, thus it has to leave it on the
+ presence server to which it creates the subscription and this means,
+ that it has to create the subscription as a subscriber. There is a
+ possibility to do subscriptions with the same To + From only once, but
+ this is left for future optimalizations (it will probably not help a
+ lot).
1.1. Dependencies
@@ -130,7 +130,7 @@ Vaclav Kubart
handle_notify()
Handles NOTIFY request.
- The module tries to find subscription to which the NOTIFY
+ The module tries to find the subscription to which the NOTIFY
belongs to (it tries both - confirmed and unconfirmed
subscriptions because NOTIFY may arrive before 2xx response on
SUBSCRIBE request). If no such subscription exists, the function
diff --git a/modules_s/presence_b2b/doc/functions.xml b/modules_s/presence_b2b/doc/functions.xml
index 7d91db8..a44b591 100644
--- a/modules_s/presence_b2b/doc/functions.xml
+++ b/modules_s/presence_b2b/doc/functions.xml
@@ -8,7 +8,7 @@
<term><varname>handle_notify()</varname></term>
<listitem>
<para>Handles NOTIFY request.</para>
- <para>The module tries to find subscription to which the NOTIFY belongs
+ <para>The module tries to find the subscription to which the NOTIFY belongs
to (it tries both - confirmed and unconfirmed subscriptions because
NOTIFY may arrive before 2xx response on SUBSCRIBE request). If no such
subscription exists, the function returns -1, otherwise it processes the
diff --git a/modules_s/presence_b2b/doc/params.xml b/modules_s/presence_b2b/doc/params.xml
index adfcc8e..7dacb70 100644
--- a/modules_s/presence_b2b/doc/params.xml
+++ b/modules_s/presence_b2b/doc/params.xml
@@ -1,6 +1,12 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!-- Include general documentation entities -->
+<!ENTITY % docentities SYSTEM "../../../docbook/entities.xml">
+%docentities;
+
+]>
<section id="presence_b2b.parameters"><title>Parameters</title>
diff --git a/modules_s/presence_b2b/doc/presence_b2b.xml b/modules_s/presence_b2b/doc/presence_b2b.xml
index 0399248..2ee4e0f 100644
--- a/modules_s/presence_b2b/doc/presence_b2b.xml
+++ b/modules_s/presence_b2b/doc/presence_b2b.xml
@@ -1,6 +1,12 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
+"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+<!-- Include general documentation entities -->
+<!ENTITY % docentities SYSTEM "../../../docbook/entities.xml">
+%docentities;
+
+]>
<section id="presence_b2b"><title>Presence B2B UA</title>
@@ -17,12 +23,12 @@
future it will do subscriptions to reg events and presence with resource lists
too.</para>
-<para>It is accessible only using internal Querry Status API (QSA). Everywhere
-(in C code) you need subscriptions to presentity status, you only create an internal
-subscription to it and the rest is done by this module. It processes internal
-subscription and creates a SIP subscription (SUBSCRIBE-NOTIFY dialog) to
-requested presentity. Every NOTIFY request produces new QSA message with status
-information into destination message queue.
+<para>It is accessible only using the internal Query Status API (QSA). Everywhere
+(in the C code) where you need subscriptions to presentity status, you only create
+an internal subscription to it and the rest is done by this module.
+It processes the internal subscription and creates a SIP subscription
+(SUBSCRIBE-NOTIFY dialog) to requested presentity. Every NOTIFY request produces
+new QSA message with status information into destination message queue.
</para>
<para>Instead of this module can be used PA module with parameter
@@ -30,11 +36,11 @@ information into destination message queue.
subscription will be only to internal status hold by PA.
</para>
-<para>For every requested (record, subscriber) is created new SIP subscription!
+<para>For every requested (record, subscriber) a new SIP subscription is created.
This is due to authorization of such subscriptions - B2B UA can't decide about
authorization rules, thus it has to leave it on the presence server to which it
creates the subscription and this means, that it has to create the subscription
-as the subscriber. There is a possibility to do subscriptions with the same
+as a subscriber. There is a possibility to do subscriptions with the same
To + From only once, but this is left for future optimalizations (it will
probably not help a lot).
</para>
diff --git a/version.h b/version.h
index 056e885..1c60539 100644
--- a/version.h
+++ b/version.h
@@ -23,6 +23,14 @@
* Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
*/
+/*!
+ * \file
+ * \brief SIP-router core :: version and compile flag macros
+ * \ingroup core
+ *
+ * Module: \ref core
+ */
+
#ifndef version_h
#define version_h
in order to avoid more surprises with branch routes, here is complete
list of things that i need to be able to do in branch_route:
- call functions is_local() from modules_s/domain, is_method() and
append_hf() from modules_k/textops, verify_destination() from
modules/peering (uses radius), add_rr_param() from modules_k/rr,
fix_nated_sdp() from modules_k/nathelper, use_media_proxy() from
modules_k/mediaproxy, t_on_reply() from modules/tm,
allow_source_address() from modules_k/permissions
- set $var pvs
- test flags, bflags, and gflags as well as set bflags
- test $avp pvs using is_avp_set and operators
- set $du
they are come from my working k configuration. hopefully the last one
is the only one that is not supported yet.
-- juha