@@ -1,4 +1,3 @@

-

 Acc Module

 Jiri Kuthan

@@ -20,7 +19,7 @@ Bogdan-Andrei Iancu

    Copyright � 2002, 2003 FhG FOKUS

    Copyright � 2004, 2006 voice-system.ro

-     _________________________________________________________

+     __________________________________________________________

    Table of Contents

    1. User's Guide

@@ -130,7 +129,7 @@ Bogdan-Andrei Iancu

    1-35. acc_db_request usage

    1-36. acc_rad_request usage

    1-37. acc_diam_request usage

-     _________________________________________________________

+     __________________________________________________________

 Chapter 1. User's Guide

@@ -140,22 +139,22 @@ Chapter 1. User's Guide

    different backends like syslog, SQL, RADIUS and DIAMETER (beta

    version).

-   To account a transaction and to choose which set of backends

-   to be used, the script writer just has to set some flags (see

-   the module parameters section for flag definitions Section

-   1.5). If the accouting flag for a specific backend is set, the

-   acc module will then report on completed transaction. A

-   typical usage of the module takes no acc-specific script

-   command -- the functionality binds invisibly through

-   transaction processing. Script writers just need to mark the

-   transaction for accounting with proper setflag. Even so, the

-   module allows the script writter to force accouting in special

-   cases via some script functions.

+   To account a transaction and to choose which set of backends to

+   be used, the script writer just has to set some flags (see the

+   module parameters section for flag definitions Section 1.5). If

+   the accouting flag for a specific backend is set, the acc

+   module will then report on completed transaction. A typical

+   usage of the module takes no acc-specific script command -- the

+   functionality binds invisibly through transaction processing.

+   Script writers just need to mark the transaction for accounting

+   with proper setflag. Even so, the module allows the script

+   writter to force accouting in special cases via some script

+   functions.

    The accouting module will log by default a fixed set of

-   attributes for the transaction - if you customize you

-   accouting by adding more information to be logged, please see

-   the next chapter about extra accouting - Section 1.2.

+   attributes for the transaction - if you customize you accouting

+   by adding more information to be logged, please see the next

+   chapter about extra accouting - Section 1.2.

    The fixed minimal accouting information is:

@@ -182,11 +181,11 @@ Chapter 1. User's Guide

        with BYEs for generating proper CDRs for example for

        purpose of billing, then it is better done in the entity

        which collects accounting information.

-     * If a UA fails in middle of conversation, a proxy will

-       never learn it. In general, a better practice is to

-       account from an end-device (such as PSTN gateway), which

-       best knows about call status (including media status and

-       PSTN status in case of the gateway).

+     * If a UA fails in middle of conversation, a proxy will never

+       learn it. In general, a better practice is to account from

+       an end-device (such as PSTN gateway), which best knows

+       about call status (including media status and PSTN status

+       in case of the gateway).

    The SQL backend support is compiled in the moduls. For RADIUS

    and DIAMETER you need to enable it by recompiling the module

@@ -198,13 +197,13 @@ Chapter 1. User's Guide

    radius client needs to be configured properly. To do so, use

    the template at etc/radiusclient.conf and make sure that

    module's radius_config parameter points to its location. In

-   particular, accounting secret must match that one configured

-   in server and proper dictionary is used (one is available at

+   particular, accounting secret must match that one configured in

+   server and proper dictionary is used (one is available at

    etc/sip_dictionary). Uses along with FreeRadius (

    http://www.freeradius.org/) and Radiator (

-   http://www.open.com.au/radiator/) servers have been reported

-   to us.

-     _________________________________________________________

+   http://www.open.com.au/radiator/) servers have been reported to

+   us.

+     __________________________________________________________

 1.1.1. General Example

@@ -215,8 +214,8 @@ modparam("acc", "log_flag", 1)

 if (uri=~"sip:+40") /* calls to Romania */ {

     if (!proxy_authorize("sip_domain.net" /* realm */,

     "subscriber" /* table name */))  {

-        proxy_challenge("sip_domain.net" /* realm */, "0" /* no qop */

-);

+        proxy_challenge("sip_domain.net" /* realm */, "0" /* no qop */ )

+;

         exit;

     }

@@ -228,7 +227,7 @@ if (uri=~"sip:+40") /* calls to Romania */ {

     setflag(1); /* set for accounting (the same value as in log_flag!)

     t_relay();  /* enter stateful mode now */

 };

-     _________________________________________________________

+     __________________________________________________________

 1.2. Extra accounting

@@ -238,19 +237,18 @@ if (uri=~"sip:+40") /* calls to Romania */ {

    dynamical selection of extra information to be logged. This

    allows you to log any pseudo-variable (AVPs, parts of the

    request, etc).

-     _________________________________________________________

+     __________________________________________________________

 1.2.2. Definitions and syntax

-   Selection of extra information is done via xxx_extra

-   parameters by specifying the names of additional information

-   you want to log. This information is defined via

-   pseudo-variables and may include headers or AVPs values or

-   other message or system values. The syntax of the parameter

-   is: 

+   Selection of extra information is done via xxx_extra parameters

+   by specifying the names of additional information you want to

+   log. This information is defined via pseudo-variables and may

+   include headers or AVPs values or other message or system

+   values. The syntax of the parameter is:

-     * xxx_extra = extra_definition (';'extra_definition)* 

-     * extra_definition = log_name '=' pseudo_variable 

+     * xxx_extra = extra_definition (';'extra_definition)*

+     * extra_definition = log_name '=' pseudo_variable

    The full list of supported pseudo-variables in OpenSER is

    availabe at:

@@ -263,24 +261,23 @@ if (uri=~"sip:+40") /* calls to Romania */ {

        the data in log_name=data format;

      * DB accounting - log_name will be the name of the DB column

        where the data will be stored.IMPORTANT: add in db acc

-       table the columns corresponding to each extra data; 

+       table the columns corresponding to each extra data;

      * RADIUS accounting - log_name will be the AVP name used for

        packing the data into RADIUS message. The log_name will be

-       translated to AVP number via the dictionary. IMPORTANT:

-       add in RADIUS dictionary the log_name attribute. 

+       translated to AVP number via the dictionary. IMPORTANT: add

+       in RADIUS dictionary the log_name attribute.

      * DIAMETER accounting - log_name will be the AVP code used

-       for packing the data into DIAMETER message. The AVP code

-       is given directly as integer, since DIAMETER has no

-       dictionary support yet. IMPORTANT: log_name must be a

-       number.

-     _________________________________________________________

+       for packing the data into DIAMETER message. The AVP code is

+       given directly as integer, since DIAMETER has no dictionary

+       support yet. IMPORTANT: log_name must be a number.

+     __________________________________________________________

 1.2.3. How it works

    Some pseudo variables may return more than one value (like

    headers or AVPs). In this case, the returned values are

    embedded in a single string in a comma-separated format.

-     _________________________________________________________

+     __________________________________________________________

 1.3. Multi Call-Legs accounting

@@ -294,9 +291,9 @@ if (uri=~"sip:+40") /* calls to Romania */ {

    billed, user B must pay for the call -as last party modifing

    the call destination-, and not A -as initiator of the call.

    Call forwarding on server is only one example which shows the

-   necessity of the having an accounting engine with multiple

-   legs support.

-     _________________________________________________________

+   necessity of the having an accounting engine with multiple legs

+   support.

+     __________________________________________________________

 1.3.2. Configuration

@@ -304,8 +301,8 @@ if (uri=~"sip:+40") /* calls to Romania */ {

    each call leg to store another set of values of the AVPs. The

    meaning the AVP content is stricly decided by the script

    writter - it can be the origin and source of the leg, its

-   status or any other related imformation. If you have a set of

-   4 AVPS (AVP1, AVP2, AVP3, AVP4), then, for the A call B and B

+   status or any other related imformation. If you have a set of 4

+   AVPS (AVP1, AVP2, AVP3, AVP4), then, for the A call B and B

    forwards to C example, the for each leg ([A,B] and [B,C]) you

    need to set a different set of values for the AVPs. The script

    writer must take care and properly insert all these AVP from

@@ -318,7 +315,7 @@ if (uri=~"sip:+40") /* calls to Romania */ {

    By default, the multiple call-legs support is disable - it can

    be enabled just be setting the per-leg set of AVPs via the

    multi_leg_info module parameter.

-     _________________________________________________________

+     __________________________________________________________

 1.3.3. Logged data

@@ -328,38 +325,38 @@ if (uri=~"sip:+40") /* calls to Romania */ {

      * syslog -- all leg-sets will be added to one record string

        as AVP1=xxx, AVP2=xxxx ,... sets.

-     * database -- each pair will be separatly logged (due DB

-       data structure constraints); several records will be

-       written, the difference between them being only the fields

+     * database -- each pair will be separatly logged (due DB data

+       structure constraints); several records will be written,

+       the difference between them being only the fields

        corresponding to the call-leg info.

-       Note

+      Note

-   You will need to add in your DB (all acc related tables) the

-   colums for call-leg info (a column for each AVP for the set).

+           You will need to add in your DB (all acc related tables) the

+           colums for call-leg info (a column for each AVP for the set).

      * Radius -- all sets will be added to same Radius accounting

        message as RADIUS AVPs - for each call-leg a set of RADIUS

        AVPs will be added (corresponding to the per-leg AVP set)

-       Note

+    Note

-   You will need to add in your dictionaty the RADIUS AVPs used

-   in call-leg AVP set definition.

+         You will need to add in your dictionaty the RADIUS AVPs used in

+         call-leg AVP set definition.

      * Diameter same as for RADIUS.

-     _________________________________________________________

+     __________________________________________________________

 1.4. Dependencies

 1.4.1. OpenSER Modules

-   The module depends on the following modules (in the other

-   words the listed modules must be loaded before this module):

+   The module depends on the following modules (in the other words

+   the listed modules must be loaded before this module):

      * tm -- Transaction Manager

      * a database module -- If SQL support is used.

      * rr -- Record Route, if "detect_direction" module parameter

        is enabled.

-     _________________________________________________________

+     __________________________________________________________

 1.4.2. External Libraries or Applications

@@ -369,7 +366,7 @@ if (uri=~"sip:+40") /* calls to Romania */ {

      * radiusclient-ng 0.5.0 or higher -- if compiled with RADIUS

        support. See

        http://developer.berlios.de/projects/radiusclient-ng/.

-     _________________________________________________________

+     __________________________________________________________

 1.5. Exported Parameters

@@ -381,7 +378,7 @@ if (uri=~"sip:+40") /* calls to Romania */ {

    Example 1-1. early_media example

 modparam("acc", "early_media", 1)

-     _________________________________________________________

+     __________________________________________________________

 1.5.2. failed_transaction_flag (integer)

@@ -392,7 +389,7 @@ modparam("acc", "early_media", 1)

    Example 1-2. failed_transaction_flag example

 modparam("acc", "failed_transaction_flag", 4)

-     _________________________________________________________

+     __________________________________________________________

 1.5.3. report_ack (integer)

@@ -405,7 +402,7 @@ modparam("acc", "failed_transaction_flag", 4)

    Example 1-3. report_ack example

 modparam("acc", "report_ack", 1)

-     _________________________________________________________

+     __________________________________________________________

 1.5.4. report_cancels (integer)

@@ -417,15 +414,15 @@ modparam("acc", "report_ack", 1)

    Example 1-4. report_cancels example

 modparam("acc", "report_cancels", 1)

-     _________________________________________________________

+     __________________________________________________________

 1.5.5. detect_direction (integer)

    Controlles the direction detection for sequential requests. If

-   enabled (non zero value), for sequential requests with

-   upstream direction (from callee to caller), the FROM and TO

-   will be swapped (the direction will be preserved as in the

-   original request).

+   enabled (non zero value), for sequential requests with upstream

+   direction (from callee to caller), the FROM and TO will be

+   swapped (the direction will be preserved as in the original

+   request).

    It affects all values related to TO and FROM headers (body,

    URI, username, domain, TAG).

@@ -434,7 +431,7 @@ modparam("acc", "report_cancels", 1)

    Example 1-5. detect_direction example

 modparam("acc", "detect_direction", 1)

-     _________________________________________________________

+     __________________________________________________________

 1.5.6. multi_leg_info (string)

@@ -459,18 +456,18 @@ modparam("acc", "multi_leg_info",

 # for DIAMETER-based accouting, use the DIAMETER AVP ID (as integer)

 modparam("acc", "multi_leg_info",

     "2345=$avp(src);2346=$avp(dst)")

-     _________________________________________________________

+     __________________________________________________________

 1.5.7. log_flag (integer)

-   Request flag which needs to be set to account a transaction

-   via syslog.

+   Request flag which needs to be set to account a transaction via

+   syslog.

    Default value is not-set (no flag).

    Example 1-7. log_flag example

 modparam("acc", "log_flag", 2)

-     _________________________________________________________

+     __________________________________________________________

 1.5.8. log_missed_flag (integer)

@@ -481,7 +478,7 @@ modparam("acc", "log_flag", 2)

    Example 1-8. log_missed_flag example

 modparam("acc", "log_missed_flag", 3)

-     _________________________________________________________

+     __________________________________________________________

 1.5.9. log_level (integer)

@@ -491,7 +488,7 @@ modparam("acc", "log_missed_flag", 3)

    Example 1-9. log_level example

 modparam("acc", "log_level", 2)   # Set log_level to 2

-     _________________________________________________________

+     __________________________________________________________

 1.5.10. log_extra (string)

@@ -501,7 +498,7 @@ modparam("acc", "log_level", 2)   # Set log_level to 2

    Example 1-10. log_extra example

 modparam("acc", "log_extra", "ua=$hdr(User-Agent);uuid=$avp(i:123)")

-     _________________________________________________________

+     __________________________________________________________

 1.5.11. radius_config (string)

@@ -515,12 +512,12 @@ modparam("acc", "log_extra", "ua=$hdr(User-Agent);uuid=$avp(i:123)")

    If the parameter is set to empty string, the RADIUS accouting

    support will be disabled (even if compiled).

-   Default value is

-   "/usr/local/etc/radiusclient/radiusclient.conf ".

+   Default value is "/usr/local/etc/radiusclient/radiusclient.conf

+   ".

    Example 1-11. radius_config example

 modparam("acc", "radius_config", "/etc/radiusclient/radiusclient.conf")

-     _________________________________________________________

+     __________________________________________________________

 1.5.12. radius_flag (integer)

@@ -531,7 +528,7 @@ modparam("acc", "radius_config", "/etc/radiusclient/radiusclient.conf")

    Example 1-12. radius_flag example

 modparam("acc", "radius_flag", 2)

-     _________________________________________________________

+     __________________________________________________________

 1.5.13. radius_missed_flag (integer)

@@ -542,7 +539,7 @@ modparam("acc", "radius_flag", 2)

    Example 1-13. radius_missed_flag example

 modparam("acc", "radius_missed_flag", 3)

-     _________________________________________________________

+     __________________________________________________________

 1.5.14. service_type (integer)

@@ -552,7 +549,7 @@ modparam("acc", "radius_missed_flag", 3)

    Example 1-14. service_type example

 modparam("acc", "service_type", 16)

-     _________________________________________________________

+     __________________________________________________________

 1.5.15. radius_extra (string)

@@ -561,9 +558,8 @@ modparam("acc", "service_type", 16)

    Default value is NULL.

    Example 1-15. radius_extra example

-modparam("acc", "radius_extra", "via=$hdr(Via[*]); email=$avp(s:email)"

-)

-     _________________________________________________________

+modparam("acc", "radius_extra", "via=$hdr(Via[*]); email=$avp(s:email)")

+     __________________________________________________________

 1.5.16. db_flag (integer)

@@ -574,7 +570,7 @@ modparam("acc", "radius_extra", "via=$hdr(Via[*]); email=$avp(s:email)"

    Example 1-16. db_flag example

 modparam("acc", "db_flag", 2)

-     _________________________________________________________

+     __________________________________________________________

 1.5.17. db_missed_flag (integer)

@@ -585,7 +581,7 @@ modparam("acc", "db_flag", 2)

    Example 1-17. db_missed_flag example

 modparam("acc", "db_missed_flag", 3)

-     _________________________________________________________

+     __________________________________________________________

 1.5.18. db_table_acc (string)

@@ -596,7 +592,7 @@ modparam("acc", "db_missed_flag", 3)

    Example 1-18. db_table_acc example

 modparam("acc", "db_table_acc", "myacc_table")

-     _________________________________________________________

+     __________________________________________________________

 1.5.19. db_table_missed_calls (string)

@@ -606,7 +602,7 @@ modparam("acc", "db_table_acc", "myacc_table")

    Example 1-19. db_table_missed_calls example

 modparam("acc", "db_table_missed_calls", "myMC_table")

-     _________________________________________________________

+     __________________________________________________________

 1.5.20. db_url (string)

@@ -617,7 +613,7 @@ modparam("acc", "db_table_missed_calls", "myMC_table")

    Example 1-20. db_url example

 modparam("acc", "db_url", "mysql://user:password@localhost/openser")

-     _________________________________________________________

+     __________________________________________________________

 1.5.21. acc_method_column (string)

@@ -628,7 +624,7 @@ modparam("acc", "db_url", "mysql://user:password@localhost/openser")

    Example 1-21. acc_method_column example

 modparam("acc", "acc_method_column", "method")

-     _________________________________________________________

+     __________________________________________________________

 1.5.22. acc_from_tag_column (string)

@@ -639,7 +635,7 @@ modparam("acc", "acc_method_column", "method")

    Example 1-22. acc_from_tag_column example

 modparam("acc", "acc_from_tag_column", "from_tag")

-     _________________________________________________________

+     __________________________________________________________

 1.5.23. acc_to_tag_column (string)

@@ -650,7 +646,7 @@ modparam("acc", "acc_from_tag_column", "from_tag")

    Example 1-23. acc_to_tag_column example

 modparam("acc", "acc_to_tag_column", "to_tag")

-     _________________________________________________________

+     __________________________________________________________

 1.5.24. acc_callid_column (string)

@@ -661,7 +657,7 @@ modparam("acc", "acc_to_tag_column", "to_tag")

    Example 1-24. acc_callid_column example

 modparam("acc", "acc_callid_column", "callid")

-     _________________________________________________________

+     __________________________________________________________

 1.5.25. acc_sip_code_column (string)

@@ -672,7 +668,7 @@ modparam("acc", "acc_callid_column", "callid")

    Example 1-25. acc_sip_code_column example

 modparam("acc", "acc_sip_code_column", "sip_code")

-     _________________________________________________________

+     __________________________________________________________

 1.5.26. acc_sip_reason_column (string)

@@ -683,7 +679,7 @@ modparam("acc", "acc_sip_code_column", "sip_code")

    Example 1-26. acc_sip_reason_column example

 modparam("acc", "acc_sip_reason_column", "sip_reason")

-     _________________________________________________________

+     __________________________________________________________

 1.5.27. acc_time_column (string)

@@ -694,7 +690,7 @@ modparam("acc", "acc_sip_reason_column", "sip_reason")

    Example 1-27. acc_time_column example

 modparam("acc", "acc_time_column", "time")

-     _________________________________________________________

+     __________________________________________________________

 1.5.28. db_extra (string)

@@ -703,9 +699,9 @@ modparam("acc", "acc_time_column", "time")

    Default value is NULL.

    Example 1-28. db_extra example

-modparam("acc", "db_extra", "ct=$hdr(Content-type); email=$avp(s:email)

-")

-     _________________________________________________________

+modparam("acc", "db_extra", "ct=$hdr(Content-type); email=$avp(s:email)"

+)

+     __________________________________________________________

 1.5.29. diameter_flag (integer)

@@ -716,7 +712,7 @@ modparam("acc", "db_extra", "ct=$hdr(Content-type); email=$avp(s:email)

    Example 1-29. diameter_flag example

 modparam("acc", "diameter_flag", 2)

-     _________________________________________________________

+     __________________________________________________________

 1.5.30. diameter_missed_flag (integer)

@@ -727,18 +723,18 @@ modparam("acc", "diameter_flag", 2)

    Example 1-30. diameter_missed_flag example

 modparam("acc", "diameter_missed_flag", 3)

-     _________________________________________________________

+     __________________________________________________________

 1.5.31. diameter_client_host (string)

-   Hostname of the machine where the DIAMETER Client is running

-   -- DIAMETER specific.

+   Hostname of the machine where the DIAMETER Client is running --

+   DIAMETER specific.

    Default value is "localhost".

    Example 1-31. diameter_client_host example

 modparam("acc", "diameter_client_host", "3a_server.net")

-     _________________________________________________________

+     __________________________________________________________

 1.5.32. diameter_client_port (int)

@@ -749,7 +745,7 @@ modparam("acc", "diameter_client_host", "3a_server.net")

    Example 1-32. diameter_client_host example

 modparam("acc", "diameter_client_port", 3000)

-     _________________________________________________________

+     __________________________________________________________

 1.5.33. diameter_extra (string)

@@ -758,17 +754,17 @@ modparam("acc", "diameter_client_port", 3000)

    Default value is NULL.

    Example 1-33. diameter_extra example

-modparam("acc", "diameter_extra", "7846=$hdr(Content-type);7847=$avp(s:

-email)")

-     _________________________________________________________

+modparam("acc", "diameter_extra", "7846=$hdr(Content-type);7847=$avp(s:e

+mail)")

+     __________________________________________________________

 1.6. Exported Functions

 1.6.1. acc_log_request(comment)

    acc_request reports on a request, for example, it can be used

-   to report on missed calls to off-line users who are replied

-   404 - Not Found. To avoid multiple reports on UDP request

+   to report on missed calls to off-line users who are replied 404

+   - Not Found. To avoid multiple reports on UDP request

    retransmission, you would need to embed the action in stateful

    processing.

@@ -782,7 +778,7 @@ email)")

 ...

 acc_log_request("Some comment");

 ...

-     _________________________________________________________

+     __________________________________________________________

 1.6.2. acc_db_request(comment, table)

@@ -801,7 +797,7 @@ acc_log_request("Some comment");

 ...

 acc_log_request("Some comment", "Some table");

 ...

-     _________________________________________________________

+     __________________________________________________________

 1.6.3. acc_rad_request(comment)

@@ -818,12 +814,12 @@ acc_log_request("Some comment", "Some table");

 ...

 acc_rad_request("Some comment");

 ...

-     _________________________________________________________

+     __________________________________________________________

 1.6.4. acc_diam_request(comment)

-   Like acc_log_request, acc_diam_request reports on a request.

-   It reports to the configured Diameter server.

+   Like acc_log_request, acc_diam_request reports on a request. It

+   reports to the configured Diameter server.

    Meaning of the parameters is as follows:

@@ -835,13 +831,13 @@ acc_rad_request("Some comment");

 ...

 acc_diam_request("Some comment");

 ...

-     _________________________________________________________

+     __________________________________________________________

 Chapter 2. Developer's Guide

    The module does not provide any API to use in other OpenSER

    modules.

-     _________________________________________________________

+     __________________________________________________________

 Chapter 3. Frequently Asked Questions

@@ -880,8 +876,8 @@ Chapter 3. Frequently Asked Questions

    3.5. 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:

+   First at all check if your question was already answered on one

+   of our mailing lists:

      * User Mailing List -

        http://openser.org/cgi-bin/mailman/listinfo/users

@@ -1,4 +1,3 @@

-

 ALIAS_DB Module

 Daniel-Constantin Mierla

@@ -10,7 +9,7 @@ Edited by

 Daniel-Constantin Mierla

    Copyright � 2005 voice-system.ro

-     _________________________________________________________

+     __________________________________________________________

    Table of Contents

    1. User's Guide

@@ -47,7 +46,7 @@ Daniel-Constantin Mierla

    1-6. Set use_domain parameter

    1-7. Set domain_prefix parameter

    1-8. alias_db_lookup() usage

-     _________________________________________________________

+     __________________________________________________________

 Chapter 1. User's Guide

@@ -59,10 +58,10 @@ Chapter 1. User's Guide

    for search (no memory caching).

    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.

-     _________________________________________________________

+   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.2. Dependencies

@@ -71,7 +70,7 @@ Chapter 1. User's Guide

    The following modules must be loaded before this module:

      * database module (mysql, dbtext, ...).

-     _________________________________________________________

+     __________________________________________________________

 1.2.2. External Libraries or Applications

@@ -79,7 +78,7 @@ Chapter 1. User's Guide

    before running OpenSER with this module loaded:

      * None.

-     _________________________________________________________

+     __________________________________________________________

 1.3. Exported Parameters

@@ -87,61 +86,61 @@ Chapter 1. User's Guide

    Database URL.

-   Default value is "DEFAULT_RODB_URL". 

+   Default value is "DEFAULT_RODB_URL".

    Example 1-1. Set db_url parameter

 ...

 modparam("alias_db", "db_url", "mysql://user:passwd@localhost/openser")

 ...

-     _________________________________________________________

+     __________________________________________________________

 1.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)

    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)

    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)

    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)

@@ -149,37 +148,37 @@ modparam("alias_db", "alias_domain_column", "adomain")

    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 "o". 

+   Default value is "o".

    Example 1-6. Set use_domain parameter

 ...

 modparam("alias_db", "use_domain", 1)

 ...

-     _________________________________________________________

+     __________________________________________________________

 1.3.7. domain_prefix (str)

    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.4. Exported Functions

 1.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:

@@ -192,13 +191,13 @@ modparam("alias_db", "domain_prefix", "sip.")

 ...

 alias_db_lookup("dbaliases");

 ...

-     _________________________________________________________

+     __________________________________________________________

 Chapter 2. Developer's Guide

    The module does not provide any API to use in other OpenSER

    modules.

-     _________________________________________________________

+     __________________________________________________________

 Chapter 3. Frequently Asked Questions

@@ -212,8 +211,8 @@ Chapter 3. Frequently Asked Questions

    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:

+   First at all check if your question was already answered on one

+   of our mailing lists: