docs: cleanup in xml files

- useless revision history removed
- docs depend on entities.xml
- updated global entities
- fixed the links to users and devel mailing lists
- fixed the link to tracker

Makefile.modules

@@ -273,7 +273,7 @@ $(share_prefix)/$(share_dir):
 ifneq (,$(wildcard doc/Makefile))
 #doc/Makefile present => we can generate README
 
-README: doc/*.xml
+README: doc/*.xml ../../docbook/entities.xml
 	$(MAKE) -C doc $(MOD_NAME).txt
 	mv doc/$(MOD_NAME).txt $@
 

docbook/Makefile

@@ -113,7 +113,8 @@ ifeq ($(validate), 0)
 	override xsltproc_flags := $(xsltproc_flags) --novalid
 endif
 
-all_deps = Makefile $(docbook_dir)/Makefile $(dep_xsl) $(catalog) $(extra_deps)
+all_deps = Makefile $(docbook_dir)/Makefile $(docbook_dir)/entities.xml \
+		   $(dep_xsl) $(catalog) $(extra_deps)
 
 all: txt
 

docbook/entities.xml

@@ -3,23 +3,21 @@
 <!ENTITY fhg "FhG FOKUS">
 <!ENTITY iptel "<ulink url='http://iptel.org'>iptel.org</ulink>">
 
+<!-- Kamailio specific attributes -->
+
 <!ENTITY kamailio "Kamailio">
 <!ENTITY kamailiobinary "kamailio">
 <!ENTITY kamailioname "Kamailio SIP Server Platform">
 <!ENTITY kamailioconfig "kamailio.cfg">
 
-<!ENTITY siprouter "SIP Router">
-<!ENTITY siproutername "SIP Router Project">
-<!ENTITY siprouterconfig "sip-router.cfg">
-
 <!ENTITY kamwiki "http://www.kamailio.org/dokuwiki/">
 <!ENTITY kamwikilink "<ulink url='&kamwiki;'>&kamwiki;</ulink>">
 
 <!ENTITY kamailiohome "http://www.kamailio.org/">
-<!ENTITY kamailiobugs "http://sourceforge.net/tracker/?group_id=139143">
-<!ENTITY kamailiohelp "http://lists.kamailio.org/cgi-bin/mailman/listinfo/team">
-<!ENTITY kamailiousers "http://lists.kamailio.org/cgi-bin/mailman/listinfo/users">
-<!ENTITY kamailiodev "http://lists.kamailio.org/cgi-bin/mailman/listinfo/devel">
+<!ENTITY kamailiobugs "http://sip-router.org/tracker">
+<!ENTITY kamailiohelp "http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">
+<!ENTITY kamailiousers "http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">
+<!ENTITY kamailiodev "http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev">
 <!ENTITY kamailiodbdocs "http://www.kamailio.org/docs/db-tables/kamailio-db-devel.html">
 
 <!ENTITY kamailiohomelink "<ulink url='&kamailiohome;'>&kamailiohome;</ulink>">
@@ -29,9 +27,9 @@
 <!ENTITY kamailiodevlink "<ulink url='&kamailiodev;'>&kamailiodev;</ulink>">
 <!ENTITY kamailiodbdocslink "<ulink url='&kamailiodbdocs;'>&kamailiodbdocs;</ulink>">
 
-<!ENTITY kamailiohelpmail "<email>[email protected].org</email>">
-<!ENTITY kamailiousersmail "<email>[email protected].org</email>">
-<!ENTITY kamailiodevmail "<email>[email protected].org</email>">
+<!ENTITY kamailiohelpmail "<email>[email protected].org</email>">
+<!ENTITY kamailiousersmail "<email>[email protected].org</email>">
+<!ENTITY kamailiodevmail "<email>[email protected].org</email>">
 
 <!ENTITY ctltool "kamctl">
 <!ENTITY ctltoolrc "kamctlrc">
@@ -40,15 +38,21 @@
 <!ENTITY develguide "Developer Guide">
 <!ENTITY faqguide "Frequently Asked Questions">
 
+<!-- SER Specific Attributes -->
+
+<!ENTITY siprouter "SIP Router">
+<!ENTITY siproutername "SIP Router Project">
+<!ENTITY siprouterconfig "sip-router.cfg">
+
 <!ENTITY ser "SER">
 <!ENTITY sername "SIP Express Router">
 <!ENTITY sercmd "sercmd">
 <!ENTITY ctlsocket "ser_ctl">
 
 <!ENTITY serhome "http://iptel.org/ser">
-<!ENTITY serbugs "http://iptel.org/ser/bugs">
-<!ENTITY serusers "http://mail.iptel.org/mailman/listinfo/serusers">
-<!ENTITY serdev "http://mail.iptel.org/mailman/listinfo/serdev">
+<!ENTITY serbugs "http://sip-router.org/tracker">
+<!ENTITY serusers "http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">
+<!ENTITY serdev "http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev">
 
 <!ENTITY serhomelink "<ulink url='&serhome;'>&serhome;</ulink>">
 <!ENTITY serbugslink "<ulink url='&serbugs;'>&serbugs;</ulink>">
@@ -56,8 +60,8 @@
 <!ENTITY seruserslink "<ulink url='&serusers;'>&serusers;</ulink>">
 <!ENTITY serdevlink "<ulink url='&serdev;'>&serdev;</ulink>">
 
-<!ENTITY serusersmail "<email>serusers@iptel.org</email>">
-<!ENTITY serdevmail "<email>serdev@iptel.org</email>">
+<!ENTITY serusersmail "<email>s[email protected].org</email>">
+<!ENTITY serdevmail "<email>s[email protected].org</email>">
 
 <!ENTITY defaultdb "mysql://openser:openserrw@localhost/openser">
 <!ENTITY defaultrodb "mysql://openserro:openserro@localhost/openser">
@@ -93,6 +97,3 @@
 <!ENTITY rfc3261 "<ulink url='http://www.ietf.org/rfc/rfc3261.txt'>RFC3261</ulink>">
 <!ENTITY rfc822 "<ulink url='http://www.ietf.org/rfc/rfc822.txt'>RFC822</ulink>">
 <!ENTITY rfc2543 "<ulink url='http://www.ietf.org/rfc/rfc2543.txt'>RFC2543</ulink>">
-
-<!ENTITY vsname "Voice Sistem SRL">
-<!ENTITY voicesystem "<ulink url='http://www.voice-system.ro'>voice-system.ro</ulink>">

modules/app_python/README

@@ -6,28 +6,28 @@ Edited by
 
 Maxim Sobolev
 
-   Copyright © 2010 Maxim Sobolev
+   Copyright © 2010 Maxim Sobolev
      __________________________________________________________________
 
    Table of Contents
 
    1. Admin Guide
 
-        1.1. Overview
-        1.2. Dependencies
+        1. Overview
+        2. Dependencies
 
-              1.2.1. Kamailio Modules
-              1.2.2. External Libraries or Applications
+              2.1. Kamailio Modules
+              2.2. External Libraries or Applications
 
-        1.3. Exported Parameters
+        3. Exported Parameters
 
-              1.3.1. script_name (string)
-              1.3.2. mod_init_function (string)
-              1.3.3. child_init_method (string)
+              3.1. script_name (string)
+              3.2. mod_init_function (string)
+              3.3. child_init_method (string)
 
-        1.4. Exported Functions
+        4. Exported Functions
 
-              1.4.1. python_exec(method [, mystr])
+              4.1. python_exec(method [, mystr])
 
    List of Examples
 
@@ -38,62 +38,89 @@ Maxim Sobolev
 
 Chapter 1. Admin Guide
 
-1.1. Overview
+   Table of Contents
+
+   1. Overview
+   2. Dependencies
+
+        2.1. Kamailio Modules
+        2.2. External Libraries or Applications
+
+   3. Exported Parameters
+
+        3.1. script_name (string)
+        3.2. mod_init_function (string)
+        3.3. child_init_method (string)
+
+   4. Exported Functions
+
+        4.1. python_exec(method [, mystr])
+
+1. Overview
 
    This module allows executing Python scripts from config file, exporting
    functions to access the SIP message from Python.
 
-1.2. Dependencies
+2. Dependencies
+
+   2.1. Kamailio Modules
+   2.2. External Libraries or Applications
 
-1.2.1. Kamailio Modules
+2.1. Kamailio Modules
 
    The following modules must be loaded before this module:
      * none.
 
-1.2.2. External Libraries or Applications
+2.2. External Libraries or Applications
 
    The following libraries or applications must be installed before
    running Kamailio with this module loaded:
      * python-dev - Python devel library.
 
-1.3. Exported Parameters
+3. Exported Parameters
 
-1.3.1. script_name (string)
+   3.1. script_name (string)
+   3.2. mod_init_function (string)
+   3.3. child_init_method (string)
+
+3.1. script_name (string)
 
    TBD.
 
-   Default value is "/usr/local/etc/sip-router/handler.py".
+   Default value is “/usr/local/etc/sip-router/handler.py�.
 
    Example 1.1. Set script_name parameter
 ...
 modparam("app_python", "script_name", "/usr/local/etc/sip-router/myscript.py")
 ...
 
-1.3.2. mod_init_function (string)
+3.2. mod_init_function (string)
 
    TBD.
 
-   Default value is "mod_init".
+   Default value is “mod_init�.
 
    Example 1.2. Set mod_init_function parameter
 ...
 modparam("app_python", "mod_init_function", "my_mod_init")
 ...
 
-1.3.3. child_init_method (string)
+3.3. child_init_method (string)
 
    TBD.
 
-   Default value is "child_init".
+   Default value is “child_init�.
 
    Example 1.3. Set child_init_method parameter
 ...
 modparam("app_python", "child_init_method", "my_child_init")
 ...
 
-1.4. Exported Functions
+4. Exported Functions
+
+   4.1. python_exec(method [, mystr])
 
-1.4.1. python_exec(method [, mystr])
+4.1.  python_exec(method [, mystr])
 
    TBD.
 

modules/auth_identity/README

@@ -4,7 +4,7 @@ Gergely Kovacs
 
    Iptel.org
 
-   Copyright © 2007 Iptel.org
+   Copyright © 2007 Iptel.org
      __________________________________________________________________
 
    1.1. Overview
@@ -150,7 +150,7 @@ modparam("auth_identity","msg_timeout",600)
 
 1.6. Authorizer service functions
 
-1.6.1. auth_date_proc()
+1.6.1.  auth_date_proc()
 
    If a message, the auth service should authorize, contains Date header
    then this function checks whether it falls in message timeout (set by
@@ -163,7 +163,7 @@ modparam("auth_identity","msg_timeout",600)
 
    No dependencies
 
-1.6.2. auth_add_identity()
+1.6.2.  auth_add_identity()
 
    Assembles digest-string from the message, calculates its SHA1 hash,
    encrypts it with the private key (set by privatekey_path parameter) of
@@ -293,7 +293,7 @@ modparam("auth_identity","accept_pem_certs",1)
 
 1.9. Verifier service functions
 
-1.9.1. vrfy_check_date()
+1.9.1.  vrfy_check_date()
 
    Checks Date header of the incoming message whether falls in validity
    time (set by auth_validity_time parameter)
@@ -302,7 +302,7 @@ modparam("auth_identity","accept_pem_certs",1)
 
    No dependencies
 
-1.9.2. vrfy_get_certificate()
+1.9.2.  vrfy_get_certificate()
 
    Tries to get certificate defined by the value of Identity-info header
    from certificate table (which size is set by certificate_cache_limit
@@ -313,7 +313,7 @@ modparam("auth_identity","accept_pem_certs",1)
 
    No dependencies
 
-1.9.3. vrfy_check_certificate()
+1.9.3.  vrfy_check_certificate()
 
    Checks whether the downloaded certificate is valid (is not expired, its
    subject and the domain part of the URL are the same) and adds it to
@@ -323,7 +323,7 @@ modparam("auth_identity","accept_pem_certs",1)
 
    vrfy_get_certificate() must be called before
 
-1.9.4. vrfy_check_msgvalidity()
+1.9.4.  vrfy_check_msgvalidity()
 
    Assembles digest-string from the message, create SHA1 hash and compares
    it with the decrypted value of Identity header.
@@ -333,7 +333,7 @@ modparam("auth_identity","accept_pem_certs",1)
    vrfy_get_certificate() must be called before and
    vrfy_check_certificate() should be called before
 
-1.9.5. vrfy_check_callid()
+1.9.5.  vrfy_check_callid()
 
    Checks whether the current call's been already processed in validity
    time (set by auth_validity_time) to recognize call replay attacks. If

modules/avpops/README

@@ -10,9 +10,7 @@ Ramona-Elena Modroiu
 
    <[email protected]>
 
-   Copyright © 2004, 2005 voice-system.ro
-   Revision History
-   Revision $Revision$ $Date$
+   Copyright © 2004, 2005 Voice Sistem SRL
      __________________________________________________________________
 
    Table of Contents

modules/avpops/doc/avpops.xml

@@ -27,14 +27,8 @@
 	<copyright>
 		<year>2004</year>
 		<year>2005</year>
-		<holder>&voicesystem;</holder>
+		<holder>Voice Sistem SRL</holder>
 	</copyright>
-	<revhistory>
-		<revision>
-			<revnumber>$Revision$</revnumber>
-			<date>$Date$</date>
-		</revision>
-	</revhistory>
 	</bookinfo>
 	<toc></toc>
 

modules/blst/README

@@ -5,8 +5,6 @@ Andrei Pelinescu-Onciul
    iptelorg GmbH
 
    Copyright © 2007 iptelorg GmbH
-   Revision History
-   Revision $Revision$ $Date$
      __________________________________________________________________
 
    1.1. Overview
@@ -28,9 +26,6 @@ Andrei Pelinescu-Onciul
 
 1.2. Functions
 
-   Revision History
-   Revision $Revision$ $Date$
-
 1.2.1.  blst_add([timeout])
 
    Adds the source of the current message to the blacklist for timeout

modules/blst/doc/blst.xml

@@ -18,12 +18,6 @@
 	    <year>2007</year>
 	    <holder>iptelorg GmbH</holder>
 	</copyright>
-	<revhistory>
-	    <revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-	    </revision>
-	</revhistory>
     </sectioninfo>
 
     <title>Blst Module</title>

modules/blst/doc/functions.xml

@@ -4,12 +4,6 @@
 
 <section id="blst.functions" xmlns:xi="http://www.w3.org/2001/XInclude">
     <sectioninfo>
-	<revhistory>
-	    <revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-	    </revision>
-	</revhistory>
     </sectioninfo>
 
     <title>Functions</title>

modules/blst/doc/params.xml

@@ -4,12 +4,6 @@
 
 <section id="textops.parameters" xmlns:xi="http://www.w3.org/2001/XInclude">
     <sectioninfo>
-	<revhistory>
-	    <revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-	    </revision>
-	</revhistory>
     </sectioninfo>
 
     <title>Parameters</title>

modules/carrierroute/README

@@ -13,8 +13,6 @@ Henning Westerholt
    1&1 Internet AG
 
    Copyright © 2007 1&1 Internet AG
-   Revision History
-   Revision $Revision$ $Date$
      __________________________________________________________________
 
    Table of Contents

modules/carrierroute/doc/carrierroute.xml

@@ -44,12 +44,6 @@
 		<year>2007</year>
 		<holder>1&amp;1 Internet AG</holder>
 	</copyright>
-	<revhistory>
-		<revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-		</revision>
-	</revhistory>
 	</bookinfo>
 	<toc></toc>
 

modules/cfg_db/README

@@ -4,9 +4,7 @@ Tomas Mandys
 
    Iptel.org
 
-   Copyright © 2008 Tomas Mandys
-   Revision History
-   Revision $Revision$ $Date$
+   Copyright © 2008 Tomas Mandys
      __________________________________________________________________
 
    1.1. Overview

modules/cfg_db/doc/cfg_db.xml

@@ -23,12 +23,6 @@
 	    <year>2008</year>
 	    <holder>Tomas Mandys</holder>
 	</copyright>
-	<revhistory>
-	    <revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-	    </revision>
-	</revhistory>
 
     </sectioninfo>
 

modules/counters/README

@@ -4,9 +4,7 @@ Andrei Pelinescu-Onciul
 
    iptelorg GmbH
 
-   Copyright © 2010 iptelorg GmbH
-   Revision History
-   Revision $Revision$ $Date$
+   Copyright © 2010 iptelorg GmbH
      __________________________________________________________________
 
    1.1. Overview
@@ -37,9 +35,6 @@ Andrei Pelinescu-Onciul
 
 1.2. Parameters
 
-   Revision History
-   Revision $Revision$ $Date$
-
 1.2.1. script_counter
 
    Define a new counter that can be used from the script. The declaration
@@ -69,9 +64,6 @@ modparam("counters", "script_cnt_grp_name", "my_counters")
 
 1.3. Functions
 
-   Revision History
-   Revision $Revision$ $Date$
-
 1.3.1.  cnt_inc([group.]name)
 
    Increments the counter group.name. The counter must be defined using
@@ -123,9 +115,6 @@ route {
 
 1.4. counters RPC Functions
 
-   Revision History
-   Revision $Revision$ $Date$
-
 1.4.1.  cnt.get group counter_name
 
    Get the value of the counter identified by group.counter_name.

modules/counters/doc/counters.xml

@@ -25,12 +25,6 @@
 		<year>2010</year>
 		<holder>iptelorg GmbH</holder>
 	</copyright>
-	<revhistory>
-		<revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-		</revision>
-	</revhistory>
 	</sectioninfo>
 
 	<title>Counters Module</title>

modules/counters/doc/functions.xml

@@ -11,12 +11,6 @@
 
 <section id="cnts.functions" xmlns:xi="http://www.w3.org/2001/XInclude">
 	 <sectioninfo>
-	<revhistory>
-		<revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-		</revision>
-	</revhistory>
 	</sectioninfo>
 
 	<title>Functions</title>

modules/counters/doc/params.xml

@@ -9,12 +9,6 @@
 
 <section id="cnts.parameters" xmlns:xi="http://www.w3.org/2001/XInclude">
 	<sectioninfo>
-		<revhistory>
-			<revision>
-				<revnumber>$Revision$</revnumber>
-				<date>$Date$</date>
-			</revision>
-		</revhistory>
 	</sectioninfo>
 	<title>Parameters</title>
 

modules/counters/doc/rpc.xml

@@ -9,12 +9,6 @@
 
 <section id="cnts.rpcs" xmlns:xi="http://www.w3.org/2001/XInclude">
 	<sectioninfo>
-		<revhistory>
-			<revision>
-				<revnumber>$Revision$</revnumber>
-				<date>$Date$</date>
-			</revision>
-		</revhistory>
 	</sectioninfo>
 	<title>counters RPC Functions</title>
 

modules/ctl/README

@@ -4,9 +4,7 @@ Andrei Pelinescu-Onciul
 
    iptelorg GmbH
 
-   Copyright © 2009 iptelorg GmbH
-   Revision History
-   Revision $Revision$ $Date$
+   Copyright © 2009 iptelorg GmbH
      __________________________________________________________________
 
    1.1. Overview
@@ -71,9 +69,6 @@ $ sercmd ps
 
 1.3. Parameters
 
-   Revision History
-   Revision $Revision$ $Date$
-
 1.3.1. binrpc (string)
 
    Specifies the transport used for the binrpc protocol. The following
@@ -204,9 +199,6 @@ modparam("ctl", "binrpc_struct_max_body_size", 3)
 
 1.4. SIP-router RPC Functions
 
-   Revision History
-   Revision $Revision$ $Date$
-
 1.4.1.  ctl.listen
 
    List all the sockets on which the ctl module listens.

modules/ctl/doc/ctl.xml

@@ -24,12 +24,6 @@
 		<year>2009</year>
 		<holder>iptelorg GmbH</holder>
 	</copyright>
-	<revhistory>
-		<revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-		</revision>
-	</revhistory>
 	</sectioninfo>
 
 	<title>Ctl Module</title>

modules/ctl/doc/params.xml

@@ -10,12 +10,6 @@
 
 <section id="ctl.parameters" xmlns:xi="http://www.w3.org/2001/XInclude">
 	<sectioninfo>
-	<revhistory>
-		<revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-		</revision>
-	</revhistory>
 	</sectioninfo>
 
 	<title>Parameters</title>

modules/ctl/doc/rpc.xml

@@ -10,12 +10,6 @@
 
 <section id="ctl.rpcs" xmlns:xi="http://www.w3.org/2001/XInclude">
 	<sectioninfo>
-	<revhistory>
-		<revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-		</revision>
-	</revhistory>
 	</sectioninfo>
 
 	<title>SIP-router RPC Functions</title>

modules/db_berkeley/README

@@ -8,10 +8,7 @@ Edited by
 
 Will Quan
 
-   Copyright © 2007 Cisco Systems
-   Revision History
-   Revision $Revision: 846 $ $Date: 2006-05-22 09:15:40 -0500 (Mon, 22 May
-   2006) $
+   Copyright © 2007 Cisco Systems
      __________________________________________________________________
 
    Table of Contents

modules/db_berkeley/doc/db_berkeley.xml

@@ -36,12 +36,6 @@
 	    <year>2007</year>
 	    <holder>Cisco Systems</holder>
 	</copyright>
-	<revhistory>
-	    <revision>
-		<revnumber>$Revision: 846 $</revnumber>
-		<date>$Date: 2006-05-22 09:15:40 -0500 (Mon, 22 May 2006) $</date>
-	    </revision>
-	</revhistory>
     </bookinfo>
     <toc></toc>
     

modules/db_berkeley/km_doc/db_berkeley.xml

@@ -36,12 +36,6 @@
 	    <year>2007</year>
 	    <holder>Cisco Systems</holder>
 	</copyright>
-	<revhistory>
-	    <revision>
-		<revnumber>$Revision: 846 $</revnumber>
-		<date>$Date: 2006-05-22 09:15:40 -0500 (Mon, 22 May 2006) $</date>
-	    </revision>
-	</revhistory>
     </bookinfo>
     <toc></toc>
 

modules/db_flatstore/README

@@ -5,11 +5,17 @@ Jan Janak
    FhG FOKUS
    <[email protected]>
 
-   Copyright © 2004, 2005 FhG FOKUS
-   Revision History
-   Revision $Revision$ $Date$
+   Copyright © 2004, 2005 FhG FOKUS
      __________________________________________________________________
 
+   1.1. Overview
+
+        1.1.1. Rotating Log Files
+
+   1.2. Parameters
+
+        1.2.1. flush (integer)
+
 1.1. Overview
 
    Db_flatstore is one of so-called SIP Router database modules. It does
@@ -82,9 +88,6 @@ sercmd flatstore.rotate
 
 1.2. Parameters
 
-   Revision History
-   Revision $Revision$ $Date$
-
 1.2.1. flush (integer)
 
    Enable or disable flushing after each write.

modules/db_flatstore/doc/db_flatstore.xml

@@ -23,12 +23,6 @@
 	    <year>2005</year>
 	    <holder>FhG FOKUS</holder>
 	</copyright>
-	<revhistory>
-	    <revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-	    </revision>
-	</revhistory>
     </sectioninfo>
 
     <title>Db_flatstore Module</title>

modules/db_flatstore/doc/functions.xml

@@ -4,12 +4,6 @@
 
 <section id="flatstore.functions" xmlns:xi="http://www.w3.org/2001/XInclude">
     <sectioninfo>
-	<revhistory>
-	    <revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-	    </revision>
-	</revhistory>
     </sectioninfo>
 
     <title>Functions</title>

modules/db_flatstore/doc/params.xml

@@ -4,12 +4,6 @@
 
 <section id="flatstore.functions" xmlns:xi="http://www.w3.org/2001/XInclude">
     <sectioninfo>
-	<revhistory>
-	    <revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-	    </revision>
-	</revhistory>
     </sectioninfo>
 
     <title>Parameters</title>

modules/db_flatstore/km_doc/db_flatstore.xml

@@ -34,12 +34,6 @@
 		<year>2005</year>
 		<holder>FhG FOKUS</holder>
 	</copyright>
-	<revhistory>
-		<revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-		</revision>
-	</revhistory>
 	</bookinfo>
 	<toc></toc>
 	

modules/db_mysql/README

@@ -10,7 +10,7 @@ Daniel-Constantin Mierla
 
    <[email protected]>
 
-   Copyright © 2006 voice-system.ro
+   Copyright © 2006 Voice Sistem SRL
      __________________________________________________________________
 
    Table of Contents

modules/db_mysql/doc/db_mysql.xml

@@ -26,7 +26,7 @@
 	</authorgroup>
 	<copyright>
 	    <year>2006</year>
-	    <holder>&voicesystem;</holder>
+	    <holder>Voice Sistem SRL</holder>
 	</copyright>
     </bookinfo>
     <toc></toc>

modules/db_postgres/README

@@ -9,8 +9,6 @@ Edited by
 Greg Fausak
 
    Copyright © 2003 Greg Fausak
-   Revision History
-   Revision $Revision$ $Date$
      __________________________________________________________________
 
    Table of Contents

modules/db_postgres/doc/db_postgres.xml

@@ -33,12 +33,6 @@
 	    <year>2003</year>
 	    <holder>Greg Fausak</holder>
 	</copyright>
-	<revhistory>
-	    <revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-	    </revision>
-	</revhistory>
     </bookinfo>
     <toc></toc>
 

modules/dialplan/README

@@ -12,12 +12,9 @@ Edited by
 
 Juha Heinanen
 
-   Copyright © 2007-2008 voice-system.ro
+   Copyright © 2007-2008 Voice Sistem SRL
 
    Copyright © 2008-2010 Juha Heinanen
-   Revision History
-   Revision $Revision: 1.1 $ $Date: 2007/08/30 13:16:22 $
-   Revision $Revision: 1.2 $ $Date: 2008/10/9 15:57 $
      __________________________________________________________________
 
    Table of Contents
@@ -461,7 +458,4 @@ xlog("translated to var $var(y) \n");
 
 Chapter 2. Developer's Guide
 
-   Revision History
-   Revision $Revision: 1.1 $ $Date: 2007/08/30 13:16:22 $
-
    The module does not provide any API to use in other Kamailio modules.

modules/dialplan/doc/dialplan.xml

@@ -16,7 +16,7 @@
 		<author>
 		<firstname>Andreea-Ancuta</firstname>
 		<surname>Onofrei</surname>
-		<affiliation><orgname>&vsname;</orgname></affiliation>
+		<affiliation><orgname>Voice Sistem SRL</orgname></affiliation>
 		<address>
 			<email>[email protected]</email>
 		</address>
@@ -35,22 +35,12 @@
 	</authorgroup>
 	<copyright>
 		<year>2007-2008</year>
-		<holder>&voicesystem;</holder>
+		<holder>Voice Sistem SRL</holder>
 	</copyright>
 	<copyright>
 		<year>2008-2010</year>
 		<holder>Juha Heinanen</holder>
 	</copyright>
-	<revhistory>
-		<revision>
-		<revnumber>$Revision: 1.1 $</revnumber>
-		<date>$Date: 2007/08/30 13:16:22 $</date>
-		</revision>
-		<revision>
-		<revnumber>$Revision: 1.2 $</revnumber>
-		<date>$Date: 2008/10/9 15:57 $</date>
-		</revision>
-	</revhistory>
 	</bookinfo>
 	<toc></toc>
 	

modules/dialplan/doc/dialplan_devel.xml

@@ -12,12 +12,6 @@
 
 <chapter>
 	<chapterinfo>
-	<revhistory>
-		<revision>
-		<revnumber>$Revision: 1.1 $</revnumber>
-		<date>$Date: 2007/08/30 13:16:22 $</date>
-		</revision>
-	</revhistory>
 	</chapterinfo>
 	<title>Developer's Guide</title>
 	<para>

modules/enum/README

@@ -9,8 +9,6 @@ Otmar Lendl
    <[email protected]>
 
    Copyright © 2002, 2003 Juha Heinanen
-   Revision History
-   Revision $Revision$ $Date$
      __________________________________________________________________
 
    Table of Contents

modules/enum/doc/enum.xml

@@ -28,12 +28,6 @@
 	    <year>2003</year>
 	    <holder>Juha Heinanen</holder>
 	</copyright>
-	<revhistory>
-	    <revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-	    </revision>
-	</revhistory>
     </bookinfo>
     <toc></toc>
     

modules/iptrtpproxy/README

@@ -4,9 +4,7 @@ Tomas Mandys
 
    Iptel.org
 
-   Copyright © 2007 Tomas Mandys
-   Revision History
-   Revision $Revision$ $Date$
+   Copyright © 2007 Tomas Mandys
      __________________________________________________________________
 
    1.1. Overview

modules/iptrtpproxy/doc/iptrtpproxy.xml

@@ -25,12 +25,6 @@
 	    <year>2007</year>
 	    <holder>Tomas Mandys</holder>
 	</copyright>
-	<revhistory>
-	    <revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-	    </revision>
-	</revhistory>
 
     </sectioninfo>
 

modules/lcr/README

@@ -11,8 +11,6 @@ Juha Heinanen
    <[email protected]>
 
    Copyright © 2005-2010 Juha Heinanen
-   Revision History
-   Revision $Revision$ $Date$
      __________________________________________________________________
 
    Table of Contents

modules/lcr/doc/lcr.xml

@@ -27,12 +27,6 @@
 		<year>2005-2010</year>
 	 	<holder>Juha Heinanen</holder>
 	</copyright>
-	<revhistory>
-		<revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-		</revision>
-	</revhistory>
 	</bookinfo>
 	<toc></toc>
 

modules/malloc_test/README

@@ -4,9 +4,7 @@ Andrei Pelinescu-Onciul
 
    iptelorg GmbH
 
-   Copyright © 2010 iptelorg GmbH
-   Revision History
-   Revision $Revision$ $Date$
+   Copyright © 2010 iptelorg GmbH
      __________________________________________________________________
 
    1.1. Overview
@@ -45,9 +43,6 @@ Warning
 
 1.2. Parameters
 
-   Revision History
-   Revision $Revision$ $Date$
-
 1.2.1. check_content
 
    When doing the tests, check also for the possibility of the memory
@@ -66,9 +61,6 @@ $ sercmd cfg.set_now_int malloc_test check_content 1
 
 1.3. Functions
 
-   Revision History
-   Revision $Revision$ $Date$
-
 1.3.1. mt_mem_alloc(size)
 
    Allocates size bytes.
@@ -99,9 +91,6 @@ mem_free();
 
 1.4. malloc_test RPC Functions
 
-   Revision History
-   Revision $Revision$ $Date$
-
 1.4.1.  mt.mem_alloc size [unit]
 
    Allocates the specified number of bytes. unit is optional and can be

modules/malloc_test/doc/functions.xml

@@ -4,12 +4,6 @@
 
 <section id="malloc_test.functions" xmlns:xi="http://www.w3.org/2001/XInclude">
 	<sectioninfo>
-	<revhistory>
-		<revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-		</revision>
-	</revhistory>
 	</sectioninfo>
 
 	<title>Functions</title>

modules/malloc_test/doc/malloc_test.xml

@@ -25,12 +25,6 @@
 			<year>2010</year>
 			<holder>iptelorg GmbH</holder>
 		</copyright>
-		<revhistory>
-			<revision>
-			<revnumber>$Revision$</revnumber>
-			<date>$Date$</date>
-			</revision>
-		</revhistory>
 	</sectioninfo>
 
 	<title>malloc_test Module</title>

modules/malloc_test/doc/params.xml

@@ -9,12 +9,6 @@
 
 <section id="malloc_test.parameters" xmlns:xi="http://www.w3.org/2001/XInclude">
 	<sectioninfo>
-		<revhistory>
-			<revision>
-				<revnumber>$Revision$</revnumber>
-				<date>$Date$</date>
-			</revision>
-		</revhistory>
 	</sectioninfo>
 	<title>Parameters</title>
 

modules/malloc_test/doc/rpc.xml

@@ -9,12 +9,6 @@
 
 <section id="malloc_test.rpcs" xmlns:xi="http://www.w3.org/2001/XInclude">
 	<sectioninfo>
-		<revhistory>
-			<revision>
-				<revnumber>$Revision$</revnumber>
-				<date>$Date$</date>
-			</revision>
-		</revhistory>
 	</sectioninfo>
 	<title>malloc_test RPC Functions</title>
 

modules/matrix/README

@@ -12,9 +12,6 @@ Henning Westerholt
    <[email protected]>
 
    Copyright © 2008 1&1 Internet AG
-   Revision History
-   Revision $Revision: 4863 $ $Date: 2008-09-05 13:11:33 +0200 (Fri, 05
-                              Sep 2008) $
      __________________________________________________________________
 
    Table of Contents

modules/matrix/doc/matrix.xml

@@ -28,12 +28,6 @@
 		<year>2008</year>
 		<holder>1&amp;1 Internet AG</holder>
 	</copyright>
-	<revhistory>
-		<revision>
-		<revnumber>$Revision: 4863 $</revnumber>
-		<date>$Date: 2008-09-05 13:11:33 +0200 (Fri, 05 Sep 2008) $</date>
-		</revision>
-	</revhistory>
 	</bookinfo>
 	<toc></toc>
         <xi:include href="matrix_admin.xml"/>

modules/mediaproxy/README

@@ -11,8 +11,6 @@ Dan Pascu
    <[email protected]>
 
    Copyright © 2004 Dan Pascu
-   Revision History
-   Revision $Revision$ $Date$
      __________________________________________________________________
 
    Table of Contents

modules/mediaproxy/doc/mediaproxy.xml

@@ -27,12 +27,6 @@
     <year>2004</year>
     <holder>Dan Pascu</holder>
   </copyright>
-  <revhistory>
-    <revision>
-    <revnumber>$Revision$</revnumber>
-    <date>$Date$</date>
-    </revision>
-  </revhistory>
   </bookinfo>
   <toc></toc>
 

modules/mi_rpc/README

@@ -11,7 +11,7 @@ Daniel-Constantin Mierla
 
    <[email protected]>
 
-   Copyright © 2009 http://www.asipto.com
+   Copyright © 2009 http://www.asipto.com
      __________________________________________________________________
 
    Table of Contents

modules/pdb/README

@@ -11,10 +11,7 @@ Henning Westerholt
    1&1 Internet AG
    <[email protected]>
 
-   Copyright © 2009 1&1 Internet AG
-   Revision History
-   Revision $Revision: 4863 $ $Date: 2008-09-05 13:11:33 +0200 (Fri, 05
-   Sep 2008) $
+   Copyright © 2009 1&1 Internet AG
      __________________________________________________________________
 
    Table of Contents
@@ -116,7 +113,7 @@ Chapter 1. Admin Guide
 
    This is the timeout in milliseconds for the pdb_query function.
 
-   Default value is "50".
+   Default value is “50�.
 
    Example 1.1. Set timeout parameter
 ...
@@ -138,7 +135,7 @@ modparam("pdb", "server", "localhost:10001,host.name:10001,192.168.1.7:10002")
 
    4.1. pdb_query (string query, string dstavp)
 
-4.1. pdb_query (string query, string dstavp)
+4.1.  pdb_query (string query, string dstavp)
 
    Sends the query string to all configured servers and stores the answer
    in dstavp. If it takes more than the configured timeout, false is
@@ -162,7 +159,7 @@ cr_route("$avp(i:82)", "$rd", "$rU", "$rU", "call_id");
    5.2. pdb_activate
    5.3. pdb_deactivate
 
-5.1. pdb_status
+5.1.  pdb_status
 
    Prints the status of the module. This can either be "active" or
    "deactivated".
@@ -172,7 +169,7 @@ cr_route("$avp(i:82)", "$rd", "$rU", "$rU", "call_id");
 kamctl fifo pdb_status
 ...
 
-5.2. pdb_activate
+5.2.  pdb_activate
 
    Activates the module. This is the default after loading the module.
 
@@ -181,7 +178,7 @@ kamctl fifo pdb_status
 kamctl fifo pdb_activate
 ...
 
-5.3. pdb_deactivate
+5.3.  pdb_deactivate
 
    Deactivates the module. No more queries are performed until it is
    activated again. As long as the module is deactivated, the pdb_query

modules/pdb/doc/pdb.xml

@@ -28,12 +28,6 @@
 		<year>2009</year>
 		<holder>1&amp;1 Internet AG</holder>
 	</copyright>
-	<revhistory>
-		<revision>
-		<revnumber>$Revision: 4863 $</revnumber>
-		<date>$Date: 2008-09-05 13:11:33 +0200 (Fri, 05 Sep 2008) $</date>
-		</revision>
-	</revhistory>
 	</bookinfo>
 	<toc></toc>
 

modules/peering/README

@@ -10,10 +10,7 @@ Juha Heinanen
 
    <[email protected]>
 
-   Copyright © 2008 Juha Heinanen
-   Revision History
-   Revision $Revision: 4261 $ $Date: 2008-05-30 01:03:56 +0200 (Fri, 30
-   Apr 2008) $
+   Copyright © 2008 Juha Heinanen
      __________________________________________________________________
 
    Table of Contents
@@ -119,7 +116,7 @@ Chapter 1. Admin Guide
    This is the location of the configuration file of Radius client
    libraries.
 
-   Default value is "/usr/local/etc/radiusclient-ng/radiusclient.conf".
+   Default value is “/usr/local/etc/radiusclient-ng/radiusclient.conf�.
 
    Example 1.1. radius_config parameter usage
 modparam("peering", "radius_config", "/etc/broker/radiusclient.conf")
@@ -130,7 +127,7 @@ modparam("peering", "radius_config", "/etc/broker/radiusclient.conf")
    sender of SIP Request verifies the request's destination using
    verify_destination() function.
 
-   Default value is the dictionary value of "Sip-Verify-Destination"
+   Default value is the dictionary value of “Sip-Verify-Destination�
    Service-Type.
 
    Example 1.2. verify_destination_service_type parameter usage
@@ -142,7 +139,7 @@ modparam("peering", "verify_destination_service_type", 21)
    receiver of SIP Request verifies the request's source using
    verify_source() function.
 
-   Default value is the dictionary value of "Sip-Verify-Source"
+   Default value is the dictionary value of “Sip-Verify-Source�
    Service-Type.
 
    Example 1.3. verify_source_service_type parameter usage

modules/peering/doc/peering.xml

@@ -27,12 +27,6 @@
 	    <year>2008</year>
 	    <holder>Juha Heinanen</holder>
 	</copyright>
-	<revhistory>
-	    <revision>
-		<revnumber>$Revision: 4261 $</revnumber>
-		<date>$Date: 2008-05-30 01:03:56 +0200 (Fri, 30 Apr 2008) $</date>
-	    </revision>
-	</revhistory>
     </bookinfo>
     <toc></toc>
 

modules/privacy/doc/privacy.xml

@@ -30,12 +30,6 @@
 		<holder>Dimensión Virtual S.L.</holder>
 	</copyright>
 	<para></para>
-	<revhistory>
-		<revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-		</revision>
-	</revhistory>
 	</bookinfo>
 	<toc></toc>
 	

modules/ratelimit/README

@@ -18,11 +18,9 @@ Edited by
 
 Hendrik Scholz
 
-   Copyright © 2006 Freenet Cityline GmbH
+   Copyright © 2006 Freenet Cityline GmbH
 
-   Copyright © 2008-2010 VoIP Embedded Inc.
-   Revision History
-   Revision $Revision$ $Date$
+   Copyright © 2008-2010 VoIP Embedded Inc.
      __________________________________________________________________
 
    Table of Contents
@@ -51,53 +49,33 @@ Hendrik Scholz
               6.1. timer_interval (integer)
               6.2. queue (integer:string)
               6.3. pipe (integer:string:integer)
-              6.4. reply_code (integer)
-              6.5. reply_reason (string)
 
         7. Exported Functions
 
               7.1. rl_check([pvar])
               7.2. rl_check_pipe([pipe_no])
-              7.3. rl_drop([[min ], max])
-
-        8. Exported MI Functions
-
-              8.1. rl_stats
-              8.2. rl_set_pipe
-              8.3. rl_get_pipes
-              8.4. rl_set_queue
-              8.5. rl_get_queues
-              8.6. rl_set_pid
-              8.7. rl_get_pid
-              8.8. rl_push_load
-              8.9. rl_set_dbg
-
-        9. Exported RPC Functions
-
-              9.1. rl.stats
-              9.2. rl.set_pipe
-              9.3. rl.get_pipes
-              9.4. rl.set_queue
-              9.5. rl.get_queues
-              9.6. rl.set_pid
-              9.7. rl.get_pid
-              9.8. rl.push_load
-              9.9. rl.set_dbg
-
-        10. Known limitations
+
+        8. Exported RPC Functions
+
+              8.1. rl.stats
+              8.2. rl.set_pipe
+              8.3. rl.get_pipes
+              8.4. rl.set_queue
+              8.5. rl.get_queues
+              8.6. rl.set_pid
+              8.7. rl.get_pid
+              8.8. rl.push_load
+              8.9. rl.set_dbg
+
+        9. Known limitations
 
    List of Examples
 
    1.1. Set timer_interval parameter
    1.2. Set queue parameter
    1.3. Set pipe parameter
-   1.4. Set reply_code parameter
-   1.5. Set reply_code parameter at runtime
-   1.6. Set reply_reason parameter
-   1.7. Set reply_reason parameter at runtime
-   1.8. rl_check usage
-   1.9. rl_check_pipe usage
-   1.10. rl_drop usage
+   1.4. rl_check usage
+   1.5. rl_check_pipe usage
 
 Chapter 1. Admin Guide
 
@@ -125,40 +103,25 @@ Chapter 1. Admin Guide
         6.1. timer_interval (integer)
         6.2. queue (integer:string)
         6.3. pipe (integer:string:integer)
-        6.4. reply_code (integer)
-        6.5. reply_reason (string)
 
    7. Exported Functions
 
         7.1. rl_check([pvar])
         7.2. rl_check_pipe([pipe_no])
-        7.3. rl_drop([[min ], max])
-
-   8. Exported MI Functions
-
-        8.1. rl_stats
-        8.2. rl_set_pipe
-        8.3. rl_get_pipes
-        8.4. rl_set_queue
-        8.5. rl_get_queues
-        8.6. rl_set_pid
-        8.7. rl_get_pid
-        8.8. rl_push_load
-        8.9. rl_set_dbg
-
-   9. Exported RPC Functions
-
-        9.1. rl.stats
-        9.2. rl.set_pipe
-        9.3. rl.get_pipes
-        9.4. rl.set_queue
-        9.5. rl.get_queues
-        9.6. rl.set_pid
-        9.7. rl.get_pid
-        9.8. rl.push_load
-        9.9. rl.set_dbg
-
-   10. Known limitations
+
+   8. Exported RPC Functions
+
+        8.1. rl.stats
+        8.2. rl.set_pipe
+        8.3. rl.get_pipes
+        8.4. rl.set_queue
+        8.5. rl.get_queues
+        8.6. rl.set_pid
+        8.7. rl.get_pid
+        8.8. rl.push_load
+        8.9. rl.set_dbg
+
+   9. Known limitations
 
 1. Overview
 
@@ -183,7 +146,8 @@ Chapter 1. Admin Guide
 ...
         if (is_method("INVITE|REGISTER|SUBSCRIBE") {
                 if (!rl_check()) {
-                        rl_drop();
+                        append_to_reply("Retry-After: 5\r\n");
+                        sl_send_reply("503","Limiting");
                         exit;
                 };
         };
@@ -294,8 +258,6 @@ Chapter 1. Admin Guide
    6.1. timer_interval (integer)
    6.2. queue (integer:string)
    6.3. pipe (integer:string:integer)
-   6.4. reply_code (integer)
-   6.5. reply_reason (string)
 
 6.1. timer_interval (integer)
 
@@ -360,43 +322,10 @@ modparam("ratelimit", "pipe", "3:FEEDBACK:80")
 modparam("ratelimit", "pipe", "4:NETWORK:10000")
 ...
 
-6.4. reply_code (integer)
-
-   The code of the reply sent by Kamailio while limiting.
-
-   Default value is 503.
-
-   Example 1.4. Set reply_code parameter
-...
-modparam("ratelimit", "reply_code", 505)
-...
-
-   This value cant be modified at runtime using sercmd
-
-   Example 1.5.  Set reply_code parameter at runtime
-sercmd cfg.set_now_int ratelimit reply_code 505
-
-6.5. reply_reason (string)
-
-   The reason of the reply sent by Kamailio while limiting.
-
-   Default value is "Server Unavailable".
-
-   Example 1.6. Set reply_reason parameter
-...
-modparam("ratelimit", "reply_reason", "Limiting")
-...
-
-   This value cant be modified at runtime using sercmd
-
-   Example 1.7.  Set reply_reason parameter at runtime
-sercmd cfg.set_now_string ratelimit reply_reason "Limiting"
-
 7. Exported Functions
 
    7.1. rl_check([pvar])
    7.2. rl_check_pipe([pipe_no])
-   7.3. rl_drop([[min ], max])
 
 7.1.  rl_check([pvar])
 
@@ -417,11 +346,12 @@ sercmd cfg.set_now_string ratelimit reply_reason "Limiting"
 
    This function can be used from REQUEST_ROUTE.
 
-   Example 1.8. rl_check usage
+   Example 1.4. rl_check usage
 ...
         # perform queue/pipe match for current method
         if (!rl_check()) {
-                rl_drop();
+                append_to_reply("Retry-After: 5\r\n");
+                sl_send_reply("503","Limiting");
                 exit;
         };
 ...
@@ -429,7 +359,8 @@ sercmd cfg.set_now_string ratelimit reply_reason "Limiting"
         # set int pvar to 1
         $var(p) = 1;
         if (!rl_check("$var(p)")) {
-                rl_drop();
+                append_to_reply("Retry-After: 5\r\n");
+                sl_send_reply("503","Limiting");
                 exit;
         };
 ...
@@ -437,7 +368,8 @@ sercmd cfg.set_now_string ratelimit reply_reason "Limiting"
         # set str pvar to 1
         $var(p) = "1";
         if (!rl_check("$var(p)") {
-                rl_drop();
+                append_to_reply("Retry-After: 5\r\n");
+                sl_send_reply("503","Limiting");
                 exit;
         };
 ...
@@ -458,206 +390,36 @@ sercmd cfg.set_now_string ratelimit reply_reason "Limiting"
 
    This function can be used from REQUEST_ROUTE.
 
-   Example 1.9. rl_check_pipe usage
+   Example 1.5. rl_check_pipe usage
 ...
         # perform queue/pipe match for current method
         if (!rl_check_pipe()) {
-                rl_drop();
+                append_to_reply("Retry-After: 5\r\n");
+                sl_send_reply("503","Limiting");
                 exit;
         };
 ...
         # use pipe no 1 for the current method
         if (!rl_check_pipe("1") {
-                rl_drop();
+                append_to_reply("Retry-After: 5\r\n");
+                sl_send_reply("503","Limiting");
                 exit;
         };
 ...
 
-7.3.  rl_drop([[min ], max])
-
-   For the current request, a "503 - Server Unavailable" reply is sent
-   back. The reply may or may not have a "Retry-After" header. If no
-   parameter is given, there will be no "Retry-After" header. If only the
-   max parameter is given, the reply will contain a "Retry-After: max"
-   header. If both min and max params are given, the reply will contain a
-   "Retry-After: random" header with random being a random value between
-   the given min and max.
-
-   Meaning of the parameters is as follows:
-     * min - the minimum value of "Retry-After" header.
-     * max - the maximum value of "Retry-After" header.
-
-   This function can be used from REQUEST_ROUTE.
-
-   Example 1.10. rl_drop usage
-...
-        if (!rl_check()) {
-                # send back a "503 - Server Unavailable"
-                # with a "Retry-After: 5"
-                rl_drop("5");
-                exit;
-        };
-...
-
-8. Exported MI Functions
-
-   8.1. rl_stats
-   8.2. rl_set_pipe
-   8.3. rl_get_pipes
-   8.4. rl_set_queue
-   8.5. rl_get_queues
-   8.6. rl_set_pid
-   8.7. rl_get_pid
-   8.8. rl_push_load
-   8.9. rl_set_dbg
-
-8.1.  rl_stats
-
-   Lists the parameters and variabiles in the ratelimit module.
-
-   Name: rl_stats
-
-   Parameters: none
-
-   MI FIFO Command Format:
-                :rl_stats:_reply_fifo_file_
-                _empty_line_
-
-8.2.  rl_set_pipe
-
-   Sets the pipe parameters for the given pipe id.
-
-   Name: rl_set_pipe
-
-   Parameters:
-     * pipe_id - pipe id.
-     * pipe_algorithm - the algorithm assigned to the given pipe id.
-     * pipe_limit - the limit assigned to the given pipe id.
-
-   MI FIFO Command Format:
-                :rl_set_pipe:_reply_fifo_file_
-                2
-                RED
-                10
-                _empty_line_
-
-8.3.  rl_get_pipes
-
-   Gets the list of in use pipes.
-
-   Name: rl_get_pipes
-
-   Parameters: none
-
-   MI FIFO Command Format:
-                :rl_get_pipes:_reply_fifo_file_
-                _empty_line_
-
-8.4.  rl_set_queue
-
-   Sets the queue parameters for the given queue id.
-
-   Name: rl_set_queue
-
-   Parameters:
-     * queue_id - queue id.
-     * queue_method - the method assigned to the given queue id.
-     * pipe_id - the pipe id assigned to the given queue id.
-
-   MI FIFO Command Format:
-                :rl_set_queue:_reply_fifo_file_
-                3
-                INVITE
-                2
-                _empty_line_
-
-8.5.  rl_get_queues
-
-   Gets the list of in use queues.
-
-   Name: rl_get_queues
-
-   Parameters: none
-
-   MI FIFO Command Format:
-                :rl_get_queues:_reply_fifo_file_
-                _empty_line_
-
-8.6.  rl_set_pid
-
-   Sets the PID Controller parameters for the Feedback Algorithm.
-
-   Name: rl_set_pid
-
-   Parameters:
-     * ki - the integral parameter.
-     * kp - the proportional parameter.
-     * kd - the derivative parameter.
-
-   MI FIFO Command Format:
-                :rl_set_pid:_reply_fifo_file_
-                0.5
-                0.5
-                0.5
-                _empty_line_
-
-8.7.  rl_get_pid
-
-   Gets the list of in use PID Controller parameters.
-
-   Name: rl_get_pid
-
-   Parameters: none
-
-   MI FIFO Command Format:
-                :rl_get_pid:_reply_fifo_file_
-                _empty_line_
-
-8.8.  rl_push_load
-
-   Force the value of the load parameter. This methos is usefull for
-   testing the Feedback algorithm.
-
-   Name: rl_push_load
-
-   Parameters:
-     * load - the forced value of load (it must be greater then 0.0 and
-       smaller then 1.0).
-
-   MI FIFO Command Format:
-                :rl_push_load:_reply_fifo_file_
-                0.85
-                _empty_line_
-
-8.9.  rl_set_dbg
-
-   This MI function will enable/disable a WARNING debug log exposing the
-   internal counters for each pipe (useful in monitoring the ratelimit
-   internals).
-
-   Name: rl_set_dbg
-
-   Parameters:
-     * dbg - the debug value (0 means disable and 1 means enable).
-
-   MI FIFO Command Format:
-                :rl_set_dbg:_reply_fifo_file_
-                1
-                _empty_line_
-
-9. Exported RPC Functions
+8. Exported RPC Functions
 
-   9.1. rl.stats
-   9.2. rl.set_pipe
-   9.3. rl.get_pipes
-   9.4. rl.set_queue
-   9.5. rl.get_queues
-   9.6. rl.set_pid
-   9.7. rl.get_pid
-   9.8. rl.push_load
-   9.9. rl.set_dbg
+   8.1. rl.stats
+   8.2. rl.set_pipe
+   8.3. rl.get_pipes
+   8.4. rl.set_queue
+   8.5. rl.get_queues
+   8.6. rl.set_pid
+   8.7. rl.get_pid
+   8.8. rl.push_load
+   8.9. rl.set_dbg
 
-9.1.  rl.stats
+8.1.  rl.stats
 
    Lists the parameters and variabiles in the ratelimit module.
 
@@ -668,7 +430,7 @@ sercmd cfg.set_now_string ratelimit reply_reason "Limiting"
    RPC Command Format:
                 serctl rl.stats
 
-9.2.  rl.set_pipe
+8.2.  rl.set_pipe
 
    Sets the pipe parameters for the given pipe id.
 
@@ -682,7 +444,7 @@ sercmd cfg.set_now_string ratelimit reply_reason "Limiting"
    RPC Command Format:
                 serctl rl.set_pipe 2 RED 10
 
-9.3.  rl.get_pipes
+8.3.  rl.get_pipes
 
    Gets the list of in use pipes.
 
@@ -693,7 +455,7 @@ sercmd cfg.set_now_string ratelimit reply_reason "Limiting"
    RPC Command Format:
                 serctl rl.get_pipes
 
-9.4.  rl.set_queue
+8.4.  rl.set_queue
 
    Sets the queue parameters for the given queue id.
 
@@ -707,7 +469,7 @@ sercmd cfg.set_now_string ratelimit reply_reason "Limiting"
    RPC Command Format:
                 serctl rl.set_queue 3 INVITE 2
 
-9.5.  rl.get_queues
+8.5.  rl.get_queues
 
    Gets the list of in use queues.
 
@@ -718,7 +480,7 @@ sercmd cfg.set_now_string ratelimit reply_reason "Limiting"
    RPC Command Format:
                 serctl rl.get_queues
 
-9.6.  rl.set_pid
+8.6.  rl.set_pid
 
    Sets the PID Controller parameters for the Feedback Algorithm.
 
@@ -732,7 +494,7 @@ sercmd cfg.set_now_string ratelimit reply_reason "Limiting"
    RPC Command Format:
                 serctl rl.set_pid 0.5 0.5 0.5
 
-9.7.  rl.get_pid
+8.7.  rl.get_pid
 
    Gets the list of in use PID Controller parameters.
 
@@ -743,7 +505,7 @@ sercmd cfg.set_now_string ratelimit reply_reason "Limiting"
    RPC Command Format:
                 serctl rl.get_pid
 
-9.8.  rl.push_load
+8.8.  rl.push_load
 
    Force the value of the load parameter. This methos is usefull for
    testing the Feedback algorithm.
@@ -757,7 +519,7 @@ sercmd cfg.set_now_string ratelimit reply_reason "Limiting"
    RPC Command Format:
                 serctl rl.push_load 0.85
 
-9.9.  rl.set_dbg
+8.9.  rl.set_dbg
 
    This MI function will enable/disable a WARNING debug log exposing the
    internal counters for each pipe (useful in monitoring the ratelimit
@@ -771,7 +533,7 @@ sercmd cfg.set_now_string ratelimit reply_reason "Limiting"
    RPC Command Format:
                 serctl rl.set_dbg 1
 
-10. Known limitations
+9. Known limitations
 
    The pipes and queues are stored as static vectors, so no more than
    MAX_PIPES/MAX_QUEUES can be added without recompilation.

modules/ratelimit/doc/ratelimit.xml

@@ -64,12 +64,6 @@
 		<year>2008-2010</year>
 		<holder>VoIP Embedded Inc.</holder>
 	</copyright>
-	<revhistory>
-		<revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-		</revision>
-	</revhistory>
 	</bookinfo>
 	<toc></toc>
 	

modules/rtpproxy/README

@@ -26,13 +26,11 @@ Sas Ovidiu
 
    Copyright © 2003-2008 Sippy Software, Inc.
 
-   Copyright © 2005 voice-system.ro
+   Copyright © 2005 Voice Sistem SRL
 
    Copyright © 2009 TuTPro Inc.
 
    Copyright © 2010 VoIPEmbedded Inc.
-   Revision History
-   Revision $Revision$ $Date$
      __________________________________________________________________
 
    Table of Contents
@@ -625,20 +623,20 @@ Chapter 2. Frequently Asked Questions
        First at all check if your question was already answered on one of our
        mailing lists:
          * User Mailing List -
-           http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
+           http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
          * Developer Mailing List -
-           http://lists.kamailio.org/cgi-bin/mailman/listinfo/devel
+           http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
 
        E-mails regarding any stable Kamailio release should be sent to
-       <[email protected]> and e-mails regarding development versions
-       should be sent to <[email protected].org>.
+       <[email protected]> and e-mails regarding development
+       versions should be sent to <[email protected].org>.
 
        If you want to keep the mail private, send it to
-       <[email protected].org>.
+       <[email protected].org>.
 
    2.4.
 
        How can I report a bug?
 
        Please follow the guidelines provided at:
-       http://sourceforge.net/tracker/?group_id=139143.
+       http://sip-router.org/tracker.

modules/rtpproxy/doc/rtpproxy.xml

@@ -64,7 +64,7 @@
 	</copyright>
 	<copyright>
 		<year>2005</year>
-		<holder>&voicesystem;</holder>
+		<holder>Voice Sistem SRL</holder>
 	</copyright>
 	<copyright>
 		<year>2009</year>
@@ -74,12 +74,6 @@
 		<year>2010</year>
 		<holder><ulink url='http://www.voipembedded.com'>VoIPEmbedded Inc.</ulink></holder>
 	</copyright>
-	<revhistory>
-		<revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-		</revision>
-	</revhistory>
 	</bookinfo>
 	<toc></toc>
 	

modules/sanity/README

@@ -5,8 +5,6 @@ Nils Ohlmeier
    iptelorg GmbH
 
    Copyright © 2006 iptelorg GmbH
-   Revision History
-   Revision $Revision$ $Date$
      __________________________________________________________________
 
    1.1. Overview
@@ -71,9 +69,6 @@ Nils Ohlmeier
 
 1.3. Parameters
 
-   Revision History
-   Revision $Revision$ $Date$
-
 1.3.1. default_checks (integer)
 
    This parameter determines which of the checks from the sanity module
@@ -133,9 +128,6 @@ modparam("sanity", "autodrop", 1)
 
 1.4. Functions
 
-   Revision History
-   Revision $Revision$ $Date$
-
 1.4.1.  sanity_check([msg_checks [, uri_checks]])
 
    This function makes a row of sanity checks over the given SIP request.

modules/sanity/doc/functions.xml

@@ -10,12 +10,6 @@
 
 <section id="options.functions" xmlns:xi="http://www.w3.org/2001/XInclude">
     <sectioninfo>
-	<revhistory>
-	    <revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-	    </revision>
-	</revhistory>
     </sectioninfo>
 
     <title>Functions</title>

modules/sanity/doc/params.xml

@@ -10,12 +10,6 @@
 
 <section id="sanity.parameters" xmlns:xi="http://www.w3.org/2001/XInclude">
     <sectioninfo>
-	<revhistory>
-	    <revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-	    </revision>
-	</revhistory>
     </sectioninfo>
 
     <title>Parameters</title>

modules/sanity/doc/sanity.xml

@@ -18,12 +18,6 @@
 	    <year>2006</year>
 	    <holder>iptelorg GmbH</holder>
 	</copyright>
-	<revhistory>
-	    <revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-	    </revision>
-	</revhistory>
     </sectioninfo>
 
     <title>Sanity Module</title>

modules/sdpops/README

@@ -10,7 +10,7 @@ Daniel-Constantin Mierla
 
    <[email protected]>
 
-   Copyright © 2011 asipto.com
+   Copyright © 2011 asipto.com
      __________________________________________________________________
 
    Table of Contents

modules/sms/README

@@ -1,154 +1,93 @@
-
-SMS Module
+1. SMS Module
 
 Bogdan Iancu
 
    FhG FOKUS
 
-Edited by
-
-Bogdan Iancu
-
-   Copyright � 2003 FhG FOKUS
-     _________________________________________________________
-
-   Table of Contents
-   1. User's Guide
-
-        1.1. Overview
-
-              1.1.1. New Features
-              1.1.2. Hardware Requirements
-              1.1.3. Numbering Plan
-              1.1.4. Address Mapping
-
-        1.2. Dependencies
-
-              1.2.1. SER Modules
-              1.2.2. External Libraries or Applications
+   Copyright © 2003 FhG FOKUS
+     __________________________________________________________________
 
-        1.3. Exported Parameters
+   1.1. Overview
 
-              1.3.1. modems (string)
-              1.3.2. networks (string)
-              1.3.3. links (string)
-              1.3.4. default_net (string)
-              1.3.5. max_sms_parts (integer)
-              1.3.6. domain_str (string)
-              1.3.7. use_contact (integer)
-              1.3.8. sms_report_type (integer)
+        1.1.1. Hardware Requirements
+        1.1.2. Numbering Plan
+        1.1.3. Address Mapping
 
-        1.4. Exported Functions
+   1.2. Dependencies
+   1.3. Parameters
 
-              1.4.1. sms_send_msg_to_net(network_name)
-              1.4.2. sms_send_msg()
+        1.3.1. modems (string)
+        1.3.2. networks (string)
+        1.3.3. links (string)
+        1.3.4. default_net (string)
+        1.3.5. max_sms_parts (integer)
+        1.3.6. domain_str (string)
+        1.3.7. use_contact (integer)
+        1.3.8. sms_report_type (integer)
 
-   2. Developer's Guide
-   3. Frequently Asked Questions
+   1.4. Functions
 
-   List of Examples
-   1-1. Set modems parameter
-   1-2. Set networks parameter
-   1-3. Set links parameter
-   1-4. Set default_net parameter
-   1-5. Set max_sms_parts parameter
-   1-6. Set domain_str parameter
-   1-7. Set use_contact parameter
-   1-8. Set sms_report_type parameter
-   1-9. sms_send_msg_to_net usage
-   1-10. sms_send_msg usage
-     _________________________________________________________
-
-Chapter 1. User's Guide
+        1.4.1. sms_send_msg_to_net(network_name)
+        1.4.2. sms_send_msg()
 
 1.1. Overview
 
-   This module provides a way of communication between SIP
-   network (via SIP MESSAGE) and GSM networks (via
-   ShortMessageService). Communication is possible from SIP to
-   SMS and vice versa. The module provides facilities like SMS
-   confirmation--the gateway can confirm to the SIP user if his
-   message really reached its destination as a SMS--or multi-part
-   messages--if a SIP messages is too long it will be split and
+   This module provides a way of communication between SIP network (via
+   SIP MESSAGE) and GSM networks (via ShortMessageService). Communication
+   is possible from SIP to SMS and vice versa. The module provides
+   facilities like SMS confirmation--the gateway can confirm to the SIP
+   user if his message really reached its destination as a SMS--or
+   multi-part messages--if a SIP messages is too long it will be split and
    sent as multiple SMS.
 
-   Errors occurred because of an invalid number or a too long
-   message or because of an internal modem malfunction are
-   reported back to the SIP user via a SIP message containing
-   explanations regarding the error.
-     _________________________________________________________
-
-1.1.1. New Features
-
-   -) July 2007 
-      The SMS module may no extract the URI from SMS body,
-      configuring the URI in the new modems parameters 's' and
-      't'.
-     _________________________________________________________
-
-1.1.2. Hardware Requirements
-
-   The SMS module needs a GSM modem to be able to send/receive
-   the SMS messages. Usually, this kind of modems are externals,
-   linked to the machine via serial cable. The modem can be a
-   dedicated one (as the ones provided by FALCOM) or can be a GSM
-   telephone that has an internal modem (as the latest mobile
-   phones from NOKIA and ERICSSON).
-     _________________________________________________________
-
-1.1.3. Numbering Plan
-
-   The gateway accepts and advertises phone numbers in
-   international format, more specific like: +(international
-   code)(area code)(number). Ex: Germany, D1 = +49 170 5678181
-   Romania, Connex = +40 722 123456 A number in this format is
-   expected to be placed as username into RURI or in the To
-   header. If RURI misses the username, the To header will be
-   consider. Also, the gateway will advertise in this format the
-   username in Contact headers (in SIP replies and requests) and
-   in From headers (in SIP requests).
-     _________________________________________________________
-
-1.1.4. Address Mapping
-
-   To identify the destination number of the SMS, the gateway
-   expects to have a mobile number in username of the SIP
-   destination address (for example sip:[email protected]).
-   For the reverse direction, because the gateway has only one
-   GSM number, the destination SIP address has to be encapsulated
-   into the SMS body. The gateway expects to find a SIP address
-   at the beginning of the SMS body in "sip:user.host" format.
-   Everything before the SIP address will be discarded, the
-   useful text begins exactly after the address (for example
-   SMS="For sip:user@host hello world!!" -> SIP="hello world"), 
-   view configuration for disable this behavior (modems parameters
-   's' y 't'). In order to facilitate replying, the gateway sends 
-   all the SMS messages with a header containing the source SIP 
-   address in the following format: "From sip:user@host (if you 
-   reply DONOT remove it)<new_line>". When an SMS-reply is received 
-   having this header (all of it or truncated at the end), the header
-   will be left out (it will not be in the SIP message). 
-
-     _________________________________________________________
+   Errors occurred because of an invalid number or a too long message or
+   because of an internal modem malfunction are reported back to the SIP
+   user via a SIP message containing explanations regarding the error.
+
+1.1.1. Hardware Requirements
+
+   The SMS module needs a GSM modem to be able to send/receive the SMS
+   messages. Usually, this kind of modems are externals, linked to the
+   machine via serial cable. The modem can be a dedicated one (as the ones
+   provided by FALCOM) or can be a GSM telephone that has an internal
+   modem (as the latest mobile phones from NOKIA and ERICSSON).
+
+1.1.2. Numbering Plan
+
+   The gateway accepts and advertises phone numbers in international
+   format, more specific like: +(international code)(area code)(number).
+   Ex: Germany, D1 = +49 170 5678181 Romania, Connex = +40 722 123456 A
+   number in this format is expected to be placed as username into RURI or
+   in the To header. If RURI misses the username, the To header will be
+   consider. Also, the gateway will advertise in this format the username
+   in Contact headers (in SIP replies and requests) and in From headers
+   (in SIP requests).
+
+1.1.3. Address Mapping
+
+   To identify the destination number of the SMS, the gateway expects to
+   have a mobile number in username of the SIP destination address (for
+   example sip:[email protected]). For the reverse direction,
+   because the gateway has only one GSM number, the destination SIP
+   address has to be encapsulated into the SMS body. The gateway expects
+   to find a SIP address at the beginning of the SMS body in
+   "sip:user.host" format. Everything before the SIP address will be
+   discarded, the useful text begins exactly after the address (for
+   example SMS="For sip:user@host hello world!!" -> SIP="hello world"),
+   view configuration for disable this behavior (modems parameters 's' y
+   't'). In order to facilitate replying, the gateway sends all the SMS
+   messages with a header containing the source SIP address in the
+   following format: "From sip:user@host (if you reply DONOT remove
+   it)<new_line>". When an SMS-reply is received having this header (all
+   of it or truncated at the end), the header will be left out (it will
+   not be in the SIP message).
 
 1.2. Dependencies
 
-1.2.1. SER Modules
-
    The following modules must be loaded before this module:
-
      * tm - Transaction Manager.
-     _________________________________________________________
-
-1.2.2. External Libraries or Applications
-
-   The following libraries or applications must be installed
-   before running SER with this module loaded:
 
-     * None.
-     _________________________________________________________
-
-1.3. Exported Parameters
+1.3. Parameters
 
 1.3.1. modems (string)
 
@@ -159,36 +98,34 @@ list_of_params   = modem_param *( ";" modem_param )
 modem_param      = name "=" value
 
    The following parameters can be used:
-
-     * d=device (mandatory) - Device associated with modem
-       (/dev/ttyS0, /dev/modem, etc.).
+     * d=device (mandatory) - Device associated with modem (/dev/ttyS0,
+       /dev/modem, etc.).
      * p=pin (optional) - SIM PIN - default is NULL.
      * m=mode (optional) - Modem working mode
        ("ASCII","OLD","DIGICOM","NEW"). Default value is "NEW".
-     * c=SMS_Center (optional) - SMS center number for that
-       modem. Default is the SMS center set on the SIM card.
+     * c=SMS_Center (optional) - SMS center number for that modem. Default
+       is the SMS center set on the SIM card.
      * b=baudrate (optional) - Default is 19600.
-     * r=retry (optional) - How many times to try to re-send a
-       SMS that reported error. Default is twice.
-     * l=looping (optional) - Time for modem to wait before
-       performing a new check for incomimg/outgoing SMS/SIP_MSG.
-       Default is 20.
-     * t=to (optional) - uri for sip header TO - default is NULL. 
-     * s=scan (optional) - 0: NOT SCAN uri from body sms, use URI
-			      in t=to.
-			   1: SCAN uri from body sms (normal mode,
-			      default mode, clasic mode)
-			   2: SCAN MIX (both modes), First SCAN
-
-   No default value, the parameter is mandatory. 
-
-   Example 1-1. Set modems parameter
+     * r=retry (optional) - How many times to try to re-send a SMS that
+       reported error. Default is twice.
+     * l=looping (optional) - Time for modem to wait before performing a
+       new check for incomimg/outgoing SMS/SIP_MSG. Default is 20.
+     * t=to (optional) - uri for sip header TO. Default is NULL.
+     * s=scan (optional) - Values: 0: NOT SCAN uri from body sms, use URI
+       in t=to. 1: SCAN uri from body sms (normal mode, default mode,
+       clasic mode) 2: SCAN MIX (both modes), First SCAN Default is 1
+       (SCAN).
+
+Note
+
+   No default value, the parameter is mandatory.
+
+   Example 1. Set modems parameter
 ...
 modparam("sms", "modems", "Nokia[d=/dev/ttyS1;s=0;t=sip:[email protected]]")
-modparam("sms", "modems", "Nokia[d=/dev/ttyS1;b=9600;m=new;l=30]")
+modparam("sms", "modems", "Nokia [d=/dev/ttyS1;b=9600;m=new;l=30] ")
 modparam("sms", "modems", "Nokia[d=/dev/ttyS1];Siemens[d=/dev/ttyS2]")
 ...
-     _________________________________________________________
 
 1.3.2. networks (string)
 
@@ -199,23 +136,23 @@ list_of_params = set_param *( ";" set_param )
 set_param      = name "=" value
 
    The following parameters can be used:
+     * m=msx_sms_per_call (optional) - Maximum number of SMS send /
+       received from that net in one modem loop. Default is 10. This
+       parameter was introduced to avoid starvation.
+       Example of the starvation--a modem can send SMS for more than 1
+       networks. If you have a huge number of SMS for the first network
+       and the number of incoming SIP messages is equal to the sent SMS
+       per same unit of time, the modem will never get to send SMS for the
+       next networks.
 
-     * m=msx_sms_per_call (optional) - Maximum number of SMS send
-       / received from that net in one modem loop. Default is 10.
-       This parameter was introduced to avoid starvation.
-       Example of the starvation--a modem can send SMS for more
-       than 1 networks. If you have a huge number of SMS for the
-       first network and the number of incoming SIP messages is
-       equal to the sent SMS per same unit of time, the modem
-       will never get to send SMS for the next networks.
+Note
 
-   No default value, the parameter is mandatory. 
+   No default value, the parameter is mandatory.
 
-   Example 1-2. Set networks parameter
+   Example 2. Set networks parameter
 ...
 modparam("sms", "networks", "D1 [m=10] ;d2[ m=20]")
 ...
-     _________________________________________________________
 
 1.3.3. links (string)
 
@@ -224,113 +161,100 @@ links_value = modem_assoc *( ";" modem_assoc )
 modem_assoc = modem_name "[" list_of_networks "]"
 list_of_networks = network *( ";" network )
 
-   No default value, the parameter is mandatory. 
+Note
+
+   No default value, the parameter is mandatory.
 
-   Example 1-3. Set links parameter
+   Example 3. Set links parameter
 ...
 modparam("sms", "links", "NOKIA[D1;d2]")
 ...
 
-   The modem NOKIA will send SMS from D1 and D2 net (in this
-   order !). if in a net queue are more then max_sms_per_call SMS
-   the modem will not sleep before starting the next loop !
-   Shortly, if messages are waiting to be sent, the modem will
-   not go in sleep.
-     _________________________________________________________
+   The modem NOKIA will send SMS from D1 and D2 net (in this order !). if
+   in a net queue are more then max_sms_per_call SMS the modem will not
+   sleep before starting the next loop ! Shortly, if messages are waiting
+   to be sent, the modem will not go in sleep.
 
 1.3.4. default_net (string)
 
-   The default network to use. If no one specified, the first
-   defined network is used. This parameter is useful only if the
-   the "sms_send_msg" exported function is used (see Section
-   1.4).
+   The default network to use. If no one specified, the first defined
+   network is used. This parameter is useful only if the "sms_send_msg"
+   exported function is used (see Section 1.4, “Functions”).
 
-   Example 1-4. Set default_net parameter
+   Example 4. Set default_net parameter
 ...
 modparam("sms", "default_net", "D1")
 ...
-     _________________________________________________________
 
 1.3.5. max_sms_parts (integer)
 
-   Shows in how many parts (SMS messages) a SIP message can be
-   split. If exceeded, the SIP message will be sent truncated and
-   the SIP user will get back another message containing the
-   unsent part.
+   Shows in how many parts (SMS messages) a SIP message can be split. If
+   exceeded, the SIP message will be sent truncated and the SIP user will
+   get back another message containing the unsent part.
 
-   Default value is 4. 
+   Default value is 4.
 
-   Example 1-5. Set max_sms_parts parameter
+   Example 5. Set max_sms_parts parameter
 ...
 modparam("sms", "max_sms_parts", 10)
 ...
-     _________________________________________________________
 
 1.3.6. domain_str (string)
 
-   Specify a fake domain name to be used by the gateway. The
-   Contact headers and the From header from request will be
-   construct based on this fake domain name. It's useful when the
-   gateway is transparently hidden behind a proxy/register
-   (located on different machines).
+   Specify a fake domain name to be used by the gateway. The Contact
+   headers and the From header from request will be construct based on
+   this fake domain name. It's useful when the gateway is transparently
+   hidden behind a proxy/register (located on different machines).
 
-   Default is the name of the machine the gateway is running on. 
+   Default is the name of the machine the gateway is running on.
 
-   Example 1-6. Set domain_str parameter
+   Example 6. Set domain_str parameter
 ...
 modparam("sms", "domain_str", "foo.bar")
 ...
-     _________________________________________________________
 
 1.3.7. use_contact (integer)
 
-   If a contact header should be added to the outgoing SIP
-   messages. Even if the SIP draft forbids this, some UAS require
-   it.
+   If a contact header should be added to the outgoing SIP messages. Even
+   if the SIP draft forbids this, some UAS require it.
 
-   Default is 0 (no). 
+   Default is 0 (no).
 
-   Example 1-7. Set use_contact parameter
+   Example 7. Set use_contact parameter
 ...
 modparam("sms", "use_contact", 1)
 ...
-     _________________________________________________________
 
 1.3.8. sms_report_type (integer)
 
-   If the modem should ask for SMS confirmation from the SMS
-   Center. If the SMSC reply with an error code, the gateway will
-   send back to SIP user a SIP message containing the text (or
-   part of it) that couldn't be send. Two report mechanisms are
-   implemented:
-
-     * 1 - the reports are delivered by the GSM device as SMS
-       reports (so far supported only by Nokia modems);
-     * 2 - the reports are delivered as async. CDS responses
-       (supported by almost all modems, except Ericsson).
+   If the modem should ask for SMS confirmation from the SMS Center. If
+   the SMSC reply with an error code, the gateway will send back to SIP
+   user a SIP message containing the text (or part of it) that couldn't be
+   send. Two report mechanisms are implemented:
+     * 1 - the reports are delivered by the GSM device as SMS reports (so
+       far supported only by Nokia modems);
+     * 2 - the reports are delivered as async. CDS responses (supported by
+       almost all modems, except Ericsson).
 
-   Default is 0 (no report). 
+   Default is 0 (no report).
 
-   Example 1-8. Set sms_report_type parameter
+   Example 8. Set sms_report_type parameter
 ...
 modparam("sms", "sms_report_type", 1)
 ...
-     _________________________________________________________
 
-1.4. Exported Functions
+1.4. Functions
 
-1.4.1. sms_send_msg_to_net(network_name)
+1.4.1.  sms_send_msg_to_net(network_name)
 
-   Put the SIP msg in the specified network queue. The function
-   return error if the number encapsulated into SIP message is
-   malformed, if the content_type is incorrect or because of some
-   internal failures.
+   Put the SIP msg in the specified network queue. The function return
+   error if the number encapsulated into SIP message is malformed, if the
+   content_type is incorrect or because of some internal failures.
 
    Meaning of the parameters is as follows:
-
      * network_name - Name of network.
 
-   Example 1-9. sms_send_msg_to_net usage
+   Example 9. sms_send_msg_to_net usage
 ...
 if (sms_send_msg_to_net("D1"))
 {
@@ -348,14 +272,12 @@ if (sms_send_msg_to_net("D1"))
     break;
 };
 ...
-     _________________________________________________________
 
-1.4.2. sms_send_msg()
+1.4.2.  sms_send_msg()
 
-   The same as the previous one, but use the default network
-   queue.
+   The same as the previous one, but use the default network queue.
 
-   Example 1-10. sms_send_msg usage
+   Example 10. sms_send_msg usage
 ...
 if (sms_send_msg_to_net())
 {
@@ -373,41 +295,3 @@ if (sms_send_msg_to_net())
     break;
 };
 ...
-     _________________________________________________________
-
-Chapter 2. Developer's Guide
-
-   Each modem forks its own process for sending /fetching SMS.
-   Communication and queuing between ser working processes and
-   modem processes is done with pipes.
-     _________________________________________________________
-
-Chapter 3. Frequently Asked Questions
-
-   3.1. Where can I find more about SER?
-   3.2. Where can I post a question about this module?
-   3.3. How can I report a bug?
-
-   3.1. Where can I find more about SER?
-
-   Take a look at http://iptel.org/ser.
-
-   3.2. Where can I post a question about this module?
-
-   First at all check if your question was already answered on
-   one of our mailing lists:
-
-     * http://mail.iptel.org/mailman/listinfo/serusers
-     * http://mail.iptel.org/mailman/listinfo/serdev
-
-   E-mails regarding any stable version should be sent to
-   <[email protected]> and e-mail regarding development versions
-   or CVS snapshots should be send to <[email protected]>.
-
-   If you want to keep the mail private, send it to
-   <[email protected]>.
-
-   3.3. How can I report a bug?
-
-   Please follow the guidelines provided at:
-   http://iptel.org/ser/bugs

modules/sms/doc/functions.xml

@@ -4,12 +4,6 @@
 
 <section id="sms.functions" xmlns:xi="http://www.w3.org/2001/XInclude">
     <sectioninfo>
-	<revhistory>
-	    <revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-	    </revision>
-	</revhistory>
     </sectioninfo>
 
     <title>Functions</title>

modules/sms/doc/params.xml

@@ -4,12 +4,6 @@
 
 <section id="sms.parameters" xmlns:xi="http://www.w3.org/2001/XInclude">
     <sectioninfo>
-	<revhistory>
-	    <revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-	    </revision>
-	</revhistory>
     </sectioninfo>
 
     <title>Parameters</title>

modules/sms/doc/sms.xml

@@ -18,12 +18,6 @@
 	    <year>2003</year>
 	    <holder>FhG FOKUS</holder>
 	</copyright>
-	<revhistory>
-	    <revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-	    </revision>
-	</revhistory>
     </sectioninfo>
 
     <title>SMS Module</title>

modules/tls/README

@@ -4,9 +4,7 @@ Andrei Pelinescu-Onciul
 
    iptelorg GmbH
 
-   Copyright © 2007 iptelorg GmbH
-   Revision History
-   Revision $Revision$ $Date$
+   Copyright © 2007 iptelorg GmbH
      __________________________________________________________________
 
    1.1. Overview
@@ -207,9 +205,6 @@ make -C modules/tls extra_defs="-DTLS_WR_DEBUG -DTLS_RD_DEBUG"
 
 1.8. Quick Certificate Howto
 
-   Revision History
-   Revision $Revision$ $Date$
-
    There are various ways to create, sign certificates and manage small
    CAs (Certificate Authorities). If you want a GUI, try tinyca
    (http://tinyca.sm-zone.net/), a very nice and small CA management
@@ -342,9 +337,6 @@ Revoking a certificate and using a CRL
 
 1.9. Parameters
 
-   Revision History
-   Revision $Revision$ $Date$
-
 1.9.1. tls_method (string)
 
    Sets the SSL/TLS protocol method. Possible values are:
@@ -971,9 +963,6 @@ modparam("tls", "config", "/usr/local/etc/ser/tls.cfg")
 
 1.10. Functions
 
-   Revision History
-   Revision $Revision$ $Date$
-
 1.10.1. is_peer_verified()
 
    Returns true if the connection on which the message was received is TLS
@@ -988,9 +977,6 @@ modparam("tls", "config", "/usr/local/etc/ser/tls.cfg")
 
 1.11. History
 
-   Revision History
-   Revision $Revision$ $Date$
-
    This module was put together by Jan Janak <[email protected]> from code
    from the experimental tls core addon
    (http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/experimental/tls/), code

modules/tls/doc/certs_howto.xml

@@ -4,12 +4,6 @@
 
 <section id="tls.certs_howto" xmlns:xi="http://www.w3.org/2001/XInclude">
     <sectioninfo>
-	<revhistory>
-	    <revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-	    </revision>
-	</revhistory>
     </sectioninfo>
 
 	<title>Quick Certificate Howto</title>

modules/tls/doc/functions.xml

@@ -4,12 +4,6 @@
 
 <section id="textops.functions">
 	<sectioninfo>
-	<revhistory>
-	    <revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-	    </revision>
-	</revhistory>
 	</sectioninfo>
 
 	<title>Functions</title>

modules/tls/doc/history.xml

@@ -4,12 +4,6 @@
 
 <section id="tls.history">
     <sectioninfo>
-	<revhistory>
-	    <revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-	    </revision>
-	</revhistory>
     </sectioninfo>
 
 	<title>History</title>

modules/tls/doc/params.xml

@@ -9,12 +9,6 @@
 
 <section id="tls.parameters">
     <sectioninfo>
-	<revhistory>
-	    <revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-	    </revision>
-	</revhistory>
     </sectioninfo>
 
     <title>Parameters</title>

modules/tls/doc/tls.xml

@@ -21,12 +21,6 @@
 		<year>2007</year>
 		<holder>iptelorg GmbH</holder>
 	</copyright>
-	<revhistory>
-		<revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-		</revision>
-	</revhistory>
 	</sectioninfo>
 
 	<title>TLS Module</title>

modules/tm/README

@@ -11,8 +11,6 @@ Juha Heinanen
    Copyright © 2003 FhG FOKUS
 
    Copyright © 2008 Juha Heinanen
-   Revision History
-   Revision $Revision$ $Date$
      __________________________________________________________________
 
    1.1. Overview
@@ -369,9 +367,6 @@ failure_route["serial"]
 
 1.4. Parameters
 
-   Revision History
-   Revision $Revision$ $Date$
-
 1.4.1. fr_timer (integer)
 
    Timer which hits if no final reply for a request or ACK for a negative
@@ -1172,9 +1167,6 @@ modparam("tm", "e2e_cancel_reason", 0)
 
 1.5. Functions
 
-   Revision History
-   Revision $Revision$ $Date$
-
 1.5.1.  t_relay_to_udp(ip, port), t_relay_to_udp(), t_relay_to_tcp(ip, port)
 t_relay_to_tcp() t_relay_to_tls(ip, port) t_relay_to_tls()
 t_relay_to_sctp(ip, port) t_relay_to_sctp()
@@ -2108,9 +2100,6 @@ opying
 
 1.6. TM Module API
 
-   Revision History
-   Revision $Revision$ $Date$
-
    There are applications which would like to generate SIP transactions
    without too big involvement in SIP stack, transaction management, etc.
    An example of such an application is sending instant messages from a

modules/tm/doc/api.xml

@@ -4,12 +4,6 @@
 
 <section id="tm.api" xmlns:xi="http://www.w3.org/2001/XInclude">
     <sectioninfo>
-	<revhistory>
-	    <revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-	    </revision>
-	</revhistory>
     </sectioninfo>
 
     <title>TM Module API</title>

modules/tm/doc/functions.xml

@@ -4,12 +4,6 @@
 
 <section id="tm.functions" xmlns:xi="http://www.w3.org/2001/XInclude">
     <sectioninfo>
-	<revhistory>
-	    <revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-	    </revision>
-	</revhistory>
     </sectioninfo>
 
     <title>Functions</title>

modules/tm/doc/params.xml

@@ -4,12 +4,6 @@
 
 <section id="tm.parameters" xmlns:xi="http://www.w3.org/2001/XInclude">
     <sectioninfo>
-	<revhistory>
-	    <revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-	    </revision>
-	</revhistory>
     </sectioninfo>
 
     <title>Parameters</title>

modules/tm/doc/tm.xml

@@ -34,12 +34,6 @@
 		<year>2008</year>
 		<holder>Juha Heinanen</holder>
 	</copyright>
-	<revhistory>
-	    <revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-	    </revision>
-	</revhistory>
     </sectioninfo>
 
     <title>TM Module</title>

modules/xmlrpc/README

@@ -3,8 +3,6 @@ Jan Janak
    iptelorg GmbH
 
    Copyright © 2005 iptelorg GmbH
-   Revision History
-   Revision $Revision$ $Date$
      __________________________________________________________________
 
    1.1. Design Goals
@@ -499,9 +497,6 @@ route[XMLRPC]{
 
 1.5. Parameters
 
-   Revision History
-   Revision $Revision$ $Date$
-
 1.5.1. route (string)
 
    Name of the route called for XMLRPC messages.
@@ -608,9 +603,6 @@ modparam("xmlrpc", "url_match", "^/RPC2")
 
 1.6. Functions
 
-   Revision History
-   Revision $Revision$ $Date$
-
 1.6.1.  dispatch_rpc()
 
    This function processes an XMLRPC request, found in the body of the

modules/xmlrpc/doc/functions.xml

@@ -4,12 +4,6 @@
 
 <section id="xmlrpc.functions" xmlns:xi="http://www.w3.org/2001/XInclude">
 	<sectioninfo>
-	<revhistory>
-		<revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-		</revision>
-	</revhistory>
 	</sectioninfo>
 
 	<title>Functions</title>

modules/xmlrpc/doc/params.xml

@@ -4,12 +4,6 @@
 
 <section id="xmlrpc.parameters" xmlns:xi="http://www.w3.org/2001/XInclude">
 	<sectioninfo>
-	<revhistory>
-		<revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-		</revision>
-	</revhistory>
 	</sectioninfo>
 
 	<title>Parameters</title>

modules/xmlrpc/doc/xmlrpc.xml

@@ -18,12 +18,6 @@
 		<year>2005</year>
 		<holder>iptelorg GmbH</holder>
 	</copyright>
-	<revhistory>
-		<revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-		</revision>
-	</revhistory>
 	</sectioninfo>
 
 

modules_k/acc/README

@@ -7,7 +7,7 @@ Jiri Kuthan
 
 Bogdan-Andrei Iancu
 
-   voice-system.ro
+   Voice Sistem SRL
    <[email protected]>
 
 Ramona-Elena Modroiu
@@ -19,14 +19,12 @@ Edited by
 
 Bogdan-Andrei Iancu
 
-   voice-system.ro
+   Voice Sistem SRL
    <[email protected]>
 
    Copyright © 2002, 2003 FhG FOKUS
 
-   Copyright © 2004, 2006 voice-system.ro
-   Revision History
-   Revision $Revision$ $Date$
+   Copyright © 2004, 2006 Voice Sistem SRL
      __________________________________________________________________
 
    Table of Contents
@@ -974,20 +972,20 @@ Chapter 2. Frequently Asked Questions
        First at all check if your question was already answered on one of our
        mailing lists:
          * User Mailing List -
-           http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
+           http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
          * Developer Mailing List -
-           http://lists.kamailio.org/cgi-bin/mailman/listinfo/devel
+           http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
 
        E-mails regarding any stable Kamailio release should be sent to
-       <[email protected]> and e-mails regarding development versions
-       should be sent to <[email protected].org>.
+       <[email protected]> and e-mails regarding development
+       versions should be sent to <[email protected].org>.
 
        If you want to keep the mail private, send it to
-       <[email protected].org>.
+       <[email protected].org>.
 
    2.6.
 
        How can I report a bug?
 
        Please follow the guidelines provided at:
-       http://sourceforge.net/tracker/?group_id=139143.
+       http://sip-router.org/tracker.

modules_k/acc/doc/acc.xml

@@ -22,7 +22,7 @@
 		<author>
 		<firstname>Bogdan-Andrei</firstname>
 		<surname>Iancu</surname>
-		<affiliation><orgname>&voicesystem;</orgname></affiliation>
+		<affiliation><orgname>Voice Sistem SRL</orgname></affiliation>
 		<email>[email protected]</email>
 		</author>
 		<author>
@@ -34,7 +34,7 @@
 		<editor>
 		<firstname>Bogdan-Andrei</firstname>
 		<surname>Iancu</surname>
-		<affiliation><orgname>&voicesystem;</orgname></affiliation>
+		<affiliation><orgname>Voice Sistem SRL</orgname></affiliation>
 		<email>[email protected]</email>
 		</editor>
 	</authorgroup>
@@ -46,14 +46,8 @@
 	<copyright>
 		<year>2004</year>
 		<year>2006</year>
-		<holder>&voicesystem;</holder>
+		<holder>Voice Sistem SRL</holder>
 	</copyright>
-	<revhistory>
-		<revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-		</revision>
-	</revhistory>
 	</bookinfo>
 	<toc></toc>
 

modules_k/alias_db/README

@@ -14,35 +14,35 @@ Daniel-Constantin Mierla
 
    <[email protected]>
 
-   Copyright © 2005 voice-system.ro
+   Copyright © 2005 Voice Sistem SRL
 
-   Copyright © 2008 asipto.com
-     __________________________________________________________
+   Copyright © 2008 asipto.com
+     __________________________________________________________________
 
    Table of Contents
 
    1. Admin Guide
 
-        1.1. Overview
-        1.2. Dependencies
+        1. Overview
+        2. Dependencies
 
-              1.2.1. Kamailio Modules
-              1.2.2. External Libraries or Applications
+              2.1. Kamailio Modules
+              2.2. External Libraries or Applications
 
-        1.3. Exported Parameters
+        3. Exported Parameters
 
-              1.3.1. db_url (str)
-              1.3.2. user_column (str)
-              1.3.3. domain_column (str)
-              1.3.4. alias_user_column (str)
-              1.3.5. alias_domain_column (str)
-              1.3.6. use_domain (int)
-              1.3.7. domain_prefix (str)
-              1.3.8. append_branches (int)
+              3.1. db_url (str)
+              3.2. user_column (str)
+              3.3. domain_column (str)
+              3.4. alias_user_column (str)
+              3.5. alias_domain_column (str)
+              3.6. use_domain (int)
+              3.7. domain_prefix (str)
+              3.8. append_branches (int)
 
-        1.4. Exported Functions
+        4. Exported Functions
 
-              1.4.1. alias_db_lookup(table_name)
+              4.1. alias_db_lookup(table_name)
 
    List of Examples
 
@@ -58,142 +58,176 @@ Daniel-Constantin Mierla
 
 Chapter 1. Admin Guide
 
-1.1. Overview
+   Table of Contents
+
+   1. Overview
+   2. Dependencies
+
+        2.1. Kamailio Modules
+        2.2. External Libraries or Applications
+
+   3. Exported Parameters
+
+        3.1. db_url (str)
+        3.2. user_column (str)
+        3.3. domain_column (str)
+        3.4. alias_user_column (str)
+        3.5. alias_domain_column (str)
+        3.6. use_domain (int)
+        3.7. domain_prefix (str)
+        3.8. append_branches (int)
+
+   4. Exported Functions
 
-   ALIAS_DB module can be used as an alternative for user aliases
-   via usrloc. The main feature is that it does not store all
-   addiacent data as for user location and always uses database
-   for search (no memory caching).
+        4.1. alias_db_lookup(table_name)
 
-   Having no memory caching the speed of search can decrease but
-   the provisioning is easier. With very fast databases like MySQL
-   the speed penalty can be lowered. Also, the search can be
-   performed on different tables in the same script.
+1. Overview
 
-1.2. Dependencies
+   ALIAS_DB module can be used as an alternative for user aliases via
+   usrloc. The main feature is that it does not store all addiacent data
+   as for user location and always uses database for search (no memory
+   caching).
 
-1.2.1. Kamailio Modules
+   Having no memory caching the speed of search can decrease but the
+   provisioning is easier. With very fast databases like MySQL the speed
+   penalty can be lowered. Also, the search can be performed on different
+   tables in the same script.
+
+2. Dependencies
+
+   2.1. Kamailio Modules
+   2.2. External Libraries or Applications
+
+2.1. Kamailio Modules
 
    The following modules must be loaded before this module:
      * database module (mysql, dbtext, ...).
 
-1.2.2. External Libraries or Applications
+2.2. External Libraries or Applications
 
-   The following libraries or applications must be installed
-   before running Kamailio with this module loaded:
+   The following libraries or applications must be installed before
+   running Kamailio with this module loaded:
      * None.
 
-1.3. Exported Parameters
+3. Exported Parameters
 
-1.3.1. db_url (str)
+   3.1. db_url (str)
+   3.2. user_column (str)
+   3.3. domain_column (str)
+   3.4. alias_user_column (str)
+   3.5. alias_domain_column (str)
+   3.6. use_domain (int)
+   3.7. domain_prefix (str)
+   3.8. append_branches (int)
+
+3.1. db_url (str)
 
    Database URL.
 
-   Default value is
-   "mysql://openserro:openserro@localhost/openser".
+   Default value is “mysql://openserro:openserro@localhost/openser�.
 
    Example 1.1. Set db_url parameter
 ...
-modparam("alias_db", "db_url", "dbdriver://username:password@dbhost/dbna
-me")
+modparam("alias_db", "db_url", "dbdriver://username:password@dbhost/dbname")
 ...
 
-1.3.2. user_column (str)
+3.2. user_column (str)
 
    Name of the column storing username.
 
-   Default value is "username".
+   Default value is “username�.
 
    Example 1.2. Set user_column parameter
 ...
 modparam("alias_db", "user_column", "susername")
 ...
 
-1.3.3. domain_column (str)
+3.3. domain_column (str)
 
    Name of the column storing user's domain.
 
-   Default value is "domain".
+   Default value is “domain�.
 
    Example 1.3. Set domain_column parameter
 ...
 modparam("alias_db", "domain_column", "sdomain")
 ...
 
-1.3.4. alias_user_column (str)
+3.4. alias_user_column (str)
 
    Name of the column storing alias username.
 
-   Default value is "alias_username".
+   Default value is “alias_username�.
 
    Example 1.4. Set alias_user_column parameter
 ...
 modparam("alias_db", "alias_user_column", "auser")
 ...
 
-1.3.5. alias_domain_column (str)
+3.5. alias_domain_column (str)
 
    Name of the column storing alias domain.
 
-   Default value is "alias_domain".
+   Default value is “alias_domain�.
 
    Example 1.5. Set alias_domain_column parameter
 ...
 modparam("alias_db", "alias_domain_column", "adomain")
 ...
 
-1.3.6. use_domain (int)
+3.6. use_domain (int)
 
-   Specifies whether to use or not the domain from R-URI when
-   searching for alias. If set to 0, the domain from R-URI is not
-   used, if set to 1 the domain from R-URI is used.
+   Specifies whether to use or not the domain from R-URI when searching
+   for alias. If set to 0, the domain from R-URI is not used, if set to 1
+   the domain from R-URI is used.
 
-   Default value is "0".
+   Default value is “0�.
 
    Example 1.6. Set use_domain parameter
 ...
 modparam("alias_db", "use_domain", 1)
 ...
 
-1.3.7. domain_prefix (str)
+3.7. domain_prefix (str)
 
-   Specifies the prefix to be stripped from the domain in R-URI
-   before doing the search.
+   Specifies the prefix to be stripped from the domain in R-URI before
+   doing the search.
 
-   Default value is "NULL".
+   Default value is “NULL�.
 
    Example 1.7. Set domain_prefix parameter
 ...
 modparam("alias_db", "domain_prefix", "sip.")
 ...
 
-1.3.8. append_branches (int)
+3.8. append_branches (int)
 
-   If the alias resolves to many SIP IDs, the first is replacing
-   the R-URI, the rest are added as branches.
+   If the alias resolves to many SIP IDs, the first is replacing the
+   R-URI, the rest are added as branches.
 
-   Default value is "0" (0 - don't add branches; 1 - add
-   branches).
+   Default value is “0� (0 - don't add branches; 1 - add branches).
 
    Example 1.8. Set append_branches parameter
 ...
 modparam("alias_db", "append_branches", 1)
 ...
 
-1.4. Exported Functions
+4. Exported Functions
+
+   4.1. alias_db_lookup(table_name)
 
-1.4.1.  alias_db_lookup(table_name)
+4.1.  alias_db_lookup(table_name)
 
-   The function takes the R-URI and search to see whether it is an
-   alias or not. If it is an alias for a local user, the R-URI is
-   replaced with user's SIP uri.
+   The function takes the R-URI and search to see whether it is an alias
+   or not. If it is an alias for a local user, the R-URI is replaced with
+   user's SIP uri.
 
-   The function returns TRUE if R-URI is alias and it was replaced
-   by user's SIP uri.
+   The function returns TRUE if R-URI is alias and it was replaced by
+   user's SIP uri.
 
    Meaning of the parameters is as follows:
-     * table_name - the name of the table where to search for
-       alias. It can include pseudo-variables.
+     * table_name - the name of the table where to search for alias. It
+       can include pseudo-variables.
 
    This function can be used from REQUEST_ROUTE, FAILURE_ROUTE.
 

modules_k/alias_db/doc/alias_db.xml

@@ -31,7 +31,7 @@
 	</authorgroup>
 	<copyright>
 	    <year>2005</year>
-	    <holder>&voicesystem;</holder>
+	    <holder>Voice Sistem SRL</holder>
 	</copyright>
 	<copyright>
 	    <year>2008</year>

modules_k/auth_db/README

@@ -11,7 +11,7 @@ Jakob Schlyter
 
 Bogdan-Andrei Iancu
 
-   voice-system.ro
+   Voice Sistem SRL
    <[email protected]>
 
 Daniel-Constantin Mierla
@@ -26,9 +26,7 @@ Jan Janak
 
    Copyright © 2002, 2003 FhG FOKUS
 
-   Copyright © 2005 voice-system.ro
-   Revision History
-   Revision $Revision$ $Date$
+   Copyright © 2005 Voice Sistem SRL
      __________________________________________________________________
 
    Table of Contents

modules_k/auth_db/doc/auth_db.xml

@@ -26,7 +26,7 @@
 		<author>
 		<firstname>Bogdan-Andrei</firstname>
 		<surname>Iancu</surname>
-		<affiliation><orgname>&voicesystem;</orgname></affiliation>
+		<affiliation><orgname>Voice Sistem SRL</orgname></affiliation>
 		<email>[email protected]</email>
 		</author>
 		<author>
@@ -47,14 +47,8 @@
 	</copyright>
 	<copyright>
 		<year>2005</year>
-		<holder>&voicesystem;</holder>
+		<holder>Voice Sistem SRL</holder>
 	</copyright>
-	<revhistory>
-		<revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-		</revision>
-	</revhistory>
 	</bookinfo>
 	<toc></toc>
 

modules_k/auth_diameter/README

@@ -8,35 +8,32 @@ Edited by
 
 Elena-Ramona Modroiu
 
-   Copyright © 2003, 2004 FhG FOKUS
-   Revision History
-   Revision $Revision$ $Date: 2008-08-06 12:08:33 +0200
-                              (Mi, 06 Aug 2008) $
-     __________________________________________________________
+   Copyright © 2003, 2004 FhG FOKUS
+     __________________________________________________________________
 
    Table of Contents
 
    1. Admin Guide
 
-        1.1. Overview
-        1.2. Dependencies
+        1. Overview
+        2. Dependencies
 
-              1.2.1. Kamailio Modules
-              1.2.2. External Libraries or Applications
+              2.1. Kamailio Modules
+              2.2. External Libraries or Applications
 
-        1.3. Exported Parameters
+        3. Exported Parameters
 
-              1.3.1. diameter_client_host (string)
-              1.3.2. diameter_client_port (int)
-              1.3.3. use_domain (int)
+              3.1. diameter_client_host (string)
+              3.2. diameter_client_port (int)
+              3.3. use_domain (int)
 
-        1.4. Exported Functions
+        4. Exported Functions
 
-              1.4.1. diameter_www_authorize(realm)
-              1.4.2. diameter_proxy_authorize(realm)
-              1.4.3. diameter_is_user_in(who, group)
+              4.1. diameter_www_authorize(realm)
+              4.2. diameter_proxy_authorize(realm)
+              4.3. diameter_is_user_in(who, group)
 
-        1.5. Installation and Running
+        5. Installation and Running
 
    List of Examples
 
@@ -50,20 +47,40 @@ Elena-Ramona Modroiu
 
 Chapter 1. Admin Guide
 
-1.1. Overview
+   Table of Contents
+
+   1. Overview
+   2. Dependencies
+
+        2.1. Kamailio Modules
+        2.2. External Libraries or Applications
+
+   3. Exported Parameters
+
+        3.1. diameter_client_host (string)
+        3.2. diameter_client_port (int)
+        3.3. use_domain (int)
+
+   4. Exported Functions
 
-   This module implements SIP authentication and authorization
-   with DIAMETER server, namely DIameter Server Client (DISC).
+        4.1. diameter_www_authorize(realm)
+        4.2. diameter_proxy_authorize(realm)
+        4.3. diameter_is_user_in(who, group)
 
-   NOTE: diameter support was developed for DISC (DIameter Server
-   Client project at http://developer.berlios.de/projects/disc/).
-   This project seems to be no longer maintained and DIAMETER
-   specifications were updated in the meantime. Thus, the module
-   is obsolete and needs rework to be usable with opendiameter or
-   other DIAMETER servers.
+   5. Installation and Running
 
-   The digest authentication mechanism is presented in next
-   figure.
+1. Overview
+
+   This module implements SIP authentication and authorization with
+   DIAMETER server, namely DIameter Server Client (DISC).
+
+   NOTE: diameter support was developed for DISC (DIameter Server Client
+   project at http://developer.berlios.de/projects/disc/). This project
+   seems to be no longer maintained and DIAMETER specifications were
+   updated in the meantime. Thus, the module is obsolete and needs rework
+   to be usable with opendiameter or other DIAMETER servers.
+
+   The digest authentication mechanism is presented in next figure.
 
    Example 1.1. Digest Authentication
 ...
@@ -94,73 +111,83 @@ Chapter 1. Admin Guide
 
 ...
 
-1.2. Dependencies
+2. Dependencies
 
-1.2.1. Kamailio Modules
+   2.1. Kamailio Modules
+   2.2. External Libraries or Applications
+
+2.1. Kamailio Modules
 
    The following modules must be loaded before this module:
      * sl - used to send stateless replies.
 
-1.2.2. External Libraries or Applications
+2.2. External Libraries or Applications
 
-   The following libraries or applications must be installed
-   before running Kamailio with this module loaded:
+   The following libraries or applications must be installed before
+   running Kamailio with this module loaded:
      * None.
 
-1.3. Exported Parameters
+3. Exported Parameters
+
+   3.1. diameter_client_host (string)
+   3.2. diameter_client_port (int)
+   3.3. use_domain (int)
 
-1.3.1. diameter_client_host (string)
+3.1. diameter_client_host (string)
 
    Hostname of the machine where the DIAMETER Client is running.
 
-   Default value is "localhost".
+   Default value is “localhost�.
 
    Example 1.2. Set diameter_client_host parameter
 ...
 modparam("auth_diameter", "diameter_client_host", "10.10.10.10")
 ...
 
-1.3.2. diameter_client_port (int)
+3.2. diameter_client_port (int)
 
    Port number where the DIAMETER Client is listening.
 
-   Default value is "3000".
+   Default value is “3000�.
 
    Example 1.3. Set diameter_client_port parameter
 ...
 modparam("auth_diameter", "diameter_client_port", 3000)
 ...
 
-1.3.3. use_domain (int)
+3.3. use_domain (int)
 
-   Specifies whether the domain name part of URI is used when
-   checking the user's privileges.
+   Specifies whether the domain name part of URI is used when checking the
+   user's privileges.
 
-   Default value is "0 (0==false and 1==true )".
+   Default value is “0 (0==false and 1==true )�.
 
    Example 1.4. Set use_domain parameter
 ...
 modparam("auth_diameter", "use_domain", 1)
 ...
 
-1.4. Exported Functions
+4. Exported Functions
+
+   4.1. diameter_www_authorize(realm)
+   4.2. diameter_proxy_authorize(realm)
+   4.3. diameter_is_user_in(who, group)
 
-1.4.1.  diameter_www_authorize(realm)
+4.1.  diameter_www_authorize(realm)
 
    SIP Server checks for authorization having a DIAMETER server in
-   backend. If no credentials are provided inside the SIP request
-   then a challenge is sent back to UAC. If the credentials don't
-   match the ones computed by DISC then "403 Forbidden" is sent
-   back.
+   backend. If no credentials are provided inside the SIP request then a
+   challenge is sent back to UAC. If the credentials don't match the ones
+   computed by DISC then “403 Forbidden� is sent back.
 
    Negative codes may be interpreted as follows:
-     * -5 (generic error) - some generic error occurred and no
-       reply was sent out;
+     * -5 (generic error) - some generic error occurred and no reply was
+       sent out;
      * -3 (stale nonce) - stale nonce;
 
    Meaning of the parameters is as follows:
-     * realm - the realm to be use for authentication and
-       authorization. The string may contain pseudo variables.
+     * realm - the realm to be use for authentication and authorization.
+       The string may contain pseudo variables.
 
    This function can be used from REQUEST_ROUTE.
 
@@ -172,18 +199,17 @@ if(!diameter_www_authorize("siphub.net"))
 };
 ...
 
-1.4.2.  diameter_proxy_authorize(realm)
+4.2.  diameter_proxy_authorize(realm)
 
-   SIP Proxy checks for authorization having a DIAMETER server in
-   backend. If no credentials are provided inside the SIP request
-   then a challenge is sent back to UAC. If the credentials don't
-   match the ones computed by DISC then "403 Forbidden" is sent
-   back. For more about the negative return codes, see the above
-   function.
+   SIP Proxy checks for authorization having a DIAMETER server in backend.
+   If no credentials are provided inside the SIP request then a challenge
+   is sent back to UAC. If the credentials don't match the ones computed
+   by DISC then “403 Forbidden� is sent back. For more about the negative
+   return codes, see the above function.
 
    Meaning of the parameters is as follows:
-     * realm - the realm to be use for authentication and
-       authorization. The string may contain pseudo variables.
+     * realm - the realm to be use for authentication and authorization.
+       The string may contain pseudo variables.
 
    This function can be used from REQUEST_ROUTE.
 
@@ -195,16 +221,15 @@ if(!diameter_proxy_authorize("siphub.net"))
 };
 ...
 
-1.4.3.  diameter_is_user_in(who, group)
+4.3.  diameter_is_user_in(who, group)
 
    The method performs group membership checking with DISC.
 
    Meaning of the parameters is as follows:
-     * who - what header to be used to get the SIP URI that is
-       wanted to be checked being member in a certain group. It
-       can be: "Request-URI", "From", "To" or "Credentials".
-     * group - the group name where to check if the user is part
-       of.
+     * who - what header to be used to get the SIP URI that is wanted to
+       be checked being member in a certain group. It can be:
+       “Request-URI�, “From�, “To� or “Credentials�.
+     * group - the group name where to check if the user is part of.
 
    This function can be used from REQUEST_ROUTE.
 
@@ -216,6 +241,6 @@ if(!diameter_is_user_in("From", "voicemail"))
 };
 ...
 
-1.5. Installation and Running
+5. Installation and Running
 
    Notes about installation and running.

modules_k/auth_diameter/doc/auth_diameter.xml

@@ -34,12 +34,6 @@
 	    <year>2004</year>
 	    <holder>FhG FOKUS</holder>
 	</copyright>
-	<revhistory>
-	    <revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-	    </revision>
-	</revhistory>
     </bookinfo>
     <toc></toc>
     

modules_k/auth_radius/README

@@ -13,7 +13,7 @@ Stelios Sidiroglou-Douskos
 
 Bogdan-Andrei Iancu
 
-   voice-system.ro
+   Voice Sistem SRL
    <[email protected]>
 
 Edited by
@@ -24,11 +24,9 @@ Jan Janak
 
    Copyright © 2002, 2003 FhG FOKUS
 
-   Copyright © 2005 voice-system.ro
+   Copyright © 2005 Voice Sistem SRL
 
    Copyright © 2008-2010 Juha Heinanen
-   Revision History
-   Revision $Revision$ $Date$
      __________________________________________________________________
 
    Table of Contents

modules_k/auth_radius/doc/auth_radius.xml

@@ -30,7 +30,7 @@
 		<author>
 		<firstname>Bogdan-Andrei</firstname>
 		<surname>Iancu</surname>
-		<affiliation><orgname>&voicesystem;</orgname></affiliation>
+		<affiliation><orgname>Voice Sistem SRL</orgname></affiliation>
 		<email>[email protected]</email>
 		</author>
 		<editor>
@@ -46,19 +46,13 @@
 	</copyright>
 	<copyright>
 		<year>2005</year>
-		<holder>&voicesystem;</holder>
+		<holder>Voice Sistem SRL</holder>
 	</copyright>
 	<copyright>
 		<year>2008-2010</year>
 		<holder>Juha Heinanen</holder>
 	</copyright>
 	<para></para>
-	<revhistory>
-		<revision>
-		<revnumber>$Revision$</revnumber>
-		<date>$Date$</date>
-		</revision>
-	</revhistory>
 	</bookinfo>
 	<toc></toc>
 	

modules_k/benchmark/README

@@ -15,12 +15,9 @@ Bastian Friedrich
 
    <[email protected]>
 
-   Copyright © 2007 Collax GmbH
+   Copyright © 2007 Collax GmbH
 
-   Copyright © 2007 Voice System SRL
-   Revision History
-   Revision $Revision: 1.1.1.1 $ $Date: 2007-04-11 14:40:39 +0200 (Mi, 11
-   Apr 2007) $
+   Copyright © 2007 Voice System SRL
      __________________________________________________________________
 
    Table of Contents
@@ -154,7 +151,7 @@ Chapter 1. Admin Guide
        that feature is implemented.
      * 1 - Globally enable benchmarking
 
-   Default value is "0".
+   Default value is “0�.
 
    Example 1.1. Set enable parameter
 ...
@@ -167,7 +164,7 @@ modparam("benchmark", "enable", 1)
    function, but only every n'th call. n is defined through this variable.
    A sensible granularity seems to be 100.
 
-   Default value is "1".
+   Default value is “1�.
 
    Example 1.2. Set granularity parameter
 ...
@@ -185,7 +182,7 @@ modparam("benchmark", "granularity", 500)
      * 3 - L_INFO
      * 4 - L_DBG
 
-   Default value is "3" (L_INFO).
+   Default value is “3� (L_INFO).
 
    Example 1.3. Set loglevel parameter
 ...
@@ -199,16 +196,16 @@ modparam("benchmark", "loglevel", 4)
    4.1. bm_start_timer(name)
    4.2. bm_log_timer(name)
 
-4.1. bm_start_timer(name)
+4.1.  bm_start_timer(name)
 
-   Start timer "name". A later call to "bm_log_timer()" logs this timer..
+   Start timer “name�. A later call to “bm_log_timer()� logs this timer..
 
    Example 1.4. bm_start_timer usage
 ...
 bm_start_timer("test");
 ...
 
-4.2. bm_log_timer(name)
+4.2.  bm_log_timer(name)
 
    This function logs the timer with the given ID. The following data are
    logged:
@@ -216,7 +213,7 @@ bm_start_timer("test");
        equals the granularity variable.
 
      * Last sum is the accumulated duration in the current logging
-       interval (i.e. for the last "granularity" calls).
+       interval (i.e. for the last “granularity� calls).
 
      * Last min is the minimum duration between start/log_timer calls
        during the last interval.
@@ -319,18 +316,18 @@ Chapter 2. Developer Guide
    1.2. bm_start(id)
    1.3. bm_log(id)
 
-1.1. bm_register(name, mode, id)
+1.1.  bm_register(name, mode, id)
 
    This function register a new timer and/or returns the internal ID
    associated with the timer. mode controls the creation of new timer if
    not found. id is to be used by start and log timer functions.
 
-1.2. bm_start(id)
+1.2.  bm_start(id)
 
    This function equals the user-exported function bm_start_timer. The id
    is passed as an integer, though.
 
-1.3. bm_log(id)
+1.3.  bm_log(id)
 
    This function equals the user-exported function bm_log_timer. The id is
    passed as an integer, though.

modules_k/benchmark/doc/benchmark.xml

@@ -38,12 +38,6 @@
 	    <year>2007</year>
 	    <holder>Voice System SRL</holder>
 	</copyright>
-	<revhistory>
-	    <revision>
-		<revnumber>$Revision: 1.1.1.1 $</revnumber>
-		<date>$Date: 2007-04-11 14:40:39 +0200 (Mi, 11 Apr 2007) $</date>
-	    </revision>
-	</revhistory>
     </bookinfo>
     <toc></toc>