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

    one SIP call but with 2 legs ( A to B and B to C). Accounting the legs

    of a call is required for proper billing of the calls (if C is a PSTN

    number and the call is billed, user B must pay for the call - as last

-   party modifing the call destination-, and not A - as initiator of the

+   party modifying 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.

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

    First how it works: The idea is to have a set of AVPs and for each call

    leg to store a set of values in the AVPs. The meaning of the AVP

-   content is stricly decided by the script writer - it can be the origin

+   content is strictly decided by the script writer - it can be the origin

    and source of the leg, its status or any other related information. If

    you have a set of 4 AVPS (AVP1, AVP2, AVP3, AVP4), then for the "A call

    B and B forwards to C" example, you need to set a different set of

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

        call-leg info.

 Note

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

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

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

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

      * Radius -- all sets will be added to the 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 that

@@ -593,10 +593,10 @@ Note

    with the corresponding caller and callee in a dialog based

    pseudo-variable (dlg_var) (e.g. chain=B;cfa;C|C;cfnr;D). Additionally

    it is necessary to store the caller and callee for each leg. All this

-   helps to identify the involved phone parners and forwarding chain. When

-   you route such calls multiple times to the same Proxy, you could store

-   the caller and callee within an transaction based avp and write it into

-   the dialog based dlg_var pv during a 200 INVITE.

+   helps to identify the involved phone partners and forwarding chain.

+   When you route such calls multiple times to the same Proxy, you could

+   store the caller and callee within an transaction based avp and write

+   it into the dialog based dlg_var pv during a 200 INVITE.

 4.3.2.1. Example for a spiraled Proxy

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

 6.6. detect_direction (integer)

-   Controlles the direction detection for sequential requests. If enabled

+   Controls 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).

@@ -871,7 +871,7 @@ modparam("acc", "log_level", 2)   # Set log_level to 2 (L_INFO)

 6.13. log_facility (string)

    Log facility to which accounting messages are issued to syslog. This

-   allows to easily seperate the accounting specific logging from the

+   allows to easily separate the accounting specific logging from the

    other log messages.

    Default value is LOG_DAEMON.

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

 6.17. db_table_acc (string)

-   Table name of accounting successfull calls -- database specific. It can

+   Table name of accounting successful calls -- database specific. It can

    contain config variables that will be evaluated at runtime.

    Default value is “acc”

@@ -944,8 +944,8 @@ modparam("acc", "db_table_missed_calls", "myMC_table")

 6.19. db_url (string)

-   SQL address -- database specific. If is set to NULL or emty string, the

-   SQL support is disabled.

+   SQL address -- database specific. If is set to NULL or empty string,

+   the SQL support is disabled.

    Default value is “NULL” (SQL disabled).

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

 6.24. acc_sip_code_column (string)

-   Column name in accounting table to store the final reply's numric code

+   Column name in accounting table to store the final reply's numeric code

    value in string format.

    Default value is “sip_code”.

@@ -1336,7 +1336,7 @@ modparam("acc", "reason_from_hf", 1)

    If set to 1, request structure from transaction is cloned temporarily

    in the callback to get acc attributes. It is required if you account

-   values from SIP headers to avoid concurent access to the shared memory

+   values from SIP headers to avoid concurrent access to the shared memory

    transaction structure, specially when accounting 1xx events. If set to

    0, it uses directly the shared memory structure, be sure you store all

    needed attributes in AVPs/XAVPs inside request route.

@@ -1468,15 +1468,15 @@ Chapter 2. Frequently Asked Questions

        The parameter became obsolete with the restructure of the data logged

        by ACC module (refer to the Overview chapter). For similar behaviour

-       you can use the extra accouting (see the coresponding chapter).

+       you can use the extra accounting (see the corresponding chapter).

    2.2.

        What happened with old multi_leg_enabled parameter

-       The parameter becaome obsolete by the addition of the new

-       multi_leg_info parameter. The multi-leg accouting is automatically

-       enabled when multi_leg_info is defined.

+       The parameter became obsolete by the addition of the new multi_leg_info

+       parameter. The multi-leg accounting is automatically enabled when

+       multi_leg_info is defined.

    2.3.

@@ -10,7 +10,7 @@ Ramona-Elena Modroiu

    rosdev.ro

    <ramona@rosdev.ro>

-   Copyright � 2002, 2003 FhG FOKUS

+   Copyright © 2002, 2003 FhG FOKUS

      __________________________________________________________________

    Table of Contents

@@ -73,7 +73,7 @@ Chapter 1. Admin Guide

    NOTE: This was developed based on some very early version of the

    Diameter protocol, and has not been really tested for many years. It is

-   verly likely to be deleted in upcoming releases. If you want to revive

+   very likely to be deleted in upcoming releases. If you want to revive

    this module, you are welcome, be sure you do proper testing before

    using in production -- it also may need to be updated first to match

    the exported API by 'acc' module.

@@ -143,7 +143,7 @@ modparam("acc_diameter", "diameter_missed_flag", 3)

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

    DIAMETER specific.

-   Default value is "localhost".

+   Default value is “localhost”.

    Example 1.3. diameter_client_host example

 ...

@@ -179,7 +179,7 @@ email)")

    4.1. acc_diam_request(comment)

-4.1. acc_diam_request(comment)

+4.1.  acc_diam_request(comment)

    Like acc_log_request, acc_diam_request reports on a request. It reports

    to the configured Diameter server.

@@ -16,7 +16,7 @@ Julien Chavanton

    flowroute.com

    <jchavanton@gmail.com>

-   Copyright � 2018 Flowroute.com

+   Copyright © 2018 Flowroute.com

      __________________________________________________________________

    Table of Contents

@@ -142,7 +142,7 @@ modparam("acc_json", "acc_missed_flag", 3)

 3.3. acc_extra (integer)

-   Extra values to be added to the json dictionnary.

+   Extra values to be added to the json dictionary.

    Default value is NULL.

@@ -225,7 +225,7 @@ route[RUN_CDR_PUBLISH] {

 3.7. output_syslog (integer)

    Control if the output of acc json should be sent to syslog. This is not

-   dependent on Kamailio global logging settigns, we can use syslog even

+   dependent on Kamailio global logging settings, we can use syslog even

    if Kamailio is not daemonized and/or logging is done to sdtout stderr.

    Default value is not-set (no flag).

@@ -240,7 +240,7 @@ modparam("acc_json", "log_facility", "LOG_DAEMON")

 3.8. log_facility (integer)

    Log facility to which accounting messages are issued to syslog. This

-   allows to easily seperate the accounting specific logging from the

+   allows to easily separate the accounting specific logging from the

    other log messages.

    Default value is LOG_DAEMON.

@@ -87,8 +87,8 @@ Chapter 1. Admin Guide

 1. Overview

    The 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 the database for search (no memory

+   usrloc. The main feature is that it does not store all adjacent data as

+   for user location and always uses the database for search (no memory

    caching). A common use case is to provide additional user aliases, i.e.

    to supplement the registration in the location database. Users are this

    way on a proxy reachable with several request URIs.

@@ -229,7 +229,7 @@ modparam("app_java", "java_options", "-Xdebug -verbose:gc,class,jni

 4.4. force_cmd_exec (int)

-   This parameter forces execution a kamailio comnmand with java native

+   This parameter forces execution a kamailio command with java native

    method “KamExec”. # Note: this is an untested yet feature, may cause

    (but may not) a memory leaks if used from embedded languages.

@@ -291,8 +291,8 @@ modparam("app_java", "force_cmd_exec", 1)

         Each parameter passed to function will be cast according to given signat

 ure.

-        Parameters are optional, ommitting a parameter meant the passed value is

- NULL.

+        Parameters are optional, omitting a parameter meant the passed value is

+NULL.

         Parameters count should be exactly the same as signature count.

         Note 1: Arrays representation (symbol '[') is not supported yet.

         Note 2: You shall use a correct signature, e.g. the following examples o

@@ -332,7 +332,7 @@ public int ExampleMethod(String param1, int param2);

 java_method_exec("ExampleMethod", "Ljava/lang/String;I", "$mb", "$ml");

 # Java

-public int ExampleMethod(String SipMessageBuffer, int SipMessageLenght)

+public int ExampleMethod(String SipMessageBuffer, int SipMessageLength)

 {

     ... do something with buffer;

     return 1;

@@ -392,7 +392,7 @@ public static int ExampleMethod(String param1, int param2);

 java_staticmethod_exec("ExampleMethod", "Ljava/lang/String;I", "$mb", "$ml");

 # Java

-public static int ExampleMethod(String SipMessageBuffer, int SipMessageLenght)

+public static int ExampleMethod(String SipMessageBuffer, int SipMessageLength)

 {

     ... do something with buffer;

     return 1;

@@ -453,7 +453,7 @@ java_s_method_exec("ExampleMethod", "Ljava/lang/String;I", "$mb", "$ml");

 # Java

 public synchronized int ExampleMethod(String SipMessageBuffer, int SipMessageLen

-ght)

+gth)

 {

     ... do something with buffer;

     return 1;

@@ -516,7 +516,7 @@ java_s_staticmethod_exec("ExampleMethod", "Ljava/lang/String;I", "$mb", "$ml");

 # Java

 public static synchronized int ExampleMethod(String SipMessageBuffer, int SipMes

-sageLenght)

+sageLength)

 {

     ... do something with buffer;

     return 1;

@@ -94,7 +94,7 @@ Chapter 1. Admin Guide

        Therefore jsdt_run() cannot execute functions from scripts loaded

        via jsdt_dofile() in config. This is kind of caching mode, avoiding

        reading file every time, but you must be sure you do not have

-       someting that is executed by default and requires access to SIP

+       something that is executed by default and requires access to SIP

        message. This environment is also used by KEMI framework for the

        config SIP routing functions.

@@ -113,7 +113,7 @@ Chapter 1. Admin Guide

    The following libraries or applications must be installed before

    running Kamailio with this module loaded:

      * libm - the math library (part of standard system libraries - it is

-       needed to complile embedded Duktape JS interpreter).

+       needed to compile embedded Duktape JS interpreter).

 3. Parameters

@@ -102,7 +102,7 @@ Chapter 1. Admin Guide

        Therefore lua_run() cannot execute functions from scripts loaded

        via lua_dofile() in config. This is kind of caching mode, avoiding

        reading file every time, but you must be sure you do not have

-       someting that is executed by default and requires access to SIP

+       something that is executed by default and requires access to SIP

        message.

 2. Dependencies

@@ -268,7 +268,7 @@ pemap"

    The Perl module has two interfaces: The perl side, and the Kamailio

    side. Once a Perl function is defined and loaded via the module

    parameters (see below), it may be called in Kamailio's configuration at

-   an arbitary point. E.g., you could write a function "ldap_alias" in

+   an arbitrary point. E.g., you could write a function "ldap_alias" in

    Perl, and then execute

 ...

 if (perl_exec("ldap_alias")) {

@@ -294,7 +294,7 @@ if (perl_exec("ldap_alias")) {

 4.1. Kamailio Modules

    The following modules must be loaded before this module:

-     * The "sl" module is needed for sending replies uppon fatal errors.

+     * The "sl" module is needed for sending replies upon fatal errors.

        All other modules can be accessed from the Perl module, though.

 4.2. External Libraries or Applications

@@ -343,7 +343,7 @@ if (perl_exec("ldap_alias")) {

 5.1. filename (string)

    This is the file name of your script. This may be set once only, but it

-   may include an arbitary number of functions and “use” as many Perl

+   may include an arbitrary number of functions and “use” as many Perl

    module as necessary.

    Must not be empty!

@@ -1065,9 +1065,9 @@ my $phonenumbers = new Kamailio::Utils::PhoneNumbers(

 $canonical = $phonenumbers->canonicalForm("07612034567");

 $number    = $phonenumbers->dialNumber("+497612034567");

-   A telphone number starting with a plus sign and containing all dial

-   prefixes is in canonical form. This is usally not the number to dial at

-   any location, so the dialing number depends on the context of the

+   A telephone number starting with a plus sign and containing all dial

+   prefixes is in canonical form. This is usually not the number to dial

+   at any location, so the dialing number depends on the context of the

    user/system.

    The idea to canonicalize numbers were taken from hylafax.

@@ -1083,7 +1083,7 @@ $number    = $phonenumbers->dialNumber("+497612034567");

    829. Then we add all the general dial prefixes - 49 (country) 761

    (area) 4514 (pbx) and 829, the number itself => +497614514829

-   To get the dialing number from a canonical phone number, we substract

+   To get the dialing number from a canonical phone number, we subtract

    all general prefixes until we have something

    As said before, the interpretation of a phone number depends on the

@@ -1140,8 +1140,8 @@ my $conf = new Kamailio::LDAPUtils::LDAPConf();

    used by other LDAP software, such as nsswitch.ldap and pam-ldap. The

    configuration is usualy stored in /etc/openldap/ldap.conf

-   When used from an account with sufficient privilegs (e.g. root), the

-   ldap manager passwort is also retrieved.

+   When used from an account with sufficient privileges (e.g. root), the

+   ldap manager password is also retrieved.

 6.1. Constructor new()

@@ -1162,14 +1162,14 @@ my $conf = new Kamailio::LDAPUtils::LDAPConf();

 6.5. Method uri()

    Returns an uri to contact the ldap server. When there is no ldap_uri in

-   the configuration file, an ldap: uri is constucted from host and port.

+   the configuration file, an ldap: uri is constructed from host and port.

 6.6. Method rootbindpw()

    Returns the ldap "root" password.

    Note that the rootbindpw is only available when the current account has

-   sufficient privilegs to access /etc/openldap/ldap.secret.

+   sufficient privileges to access /etc/openldap/ldap.secret.

 6.7. Method rootbinddn()

@@ -1233,8 +1233,8 @@ ou=de");

 7.2. Function/Method search( conf, filter, base, [requested_attributes ...])

    perform an ldap search, return the dn of the first matching directory

-   entry, unless a specific attribute has been requested, in wich case the

-   values(s) fot this attribute are returned.

+   entry, unless a specific attribute has been requested, in which case

+   the values(s) for this attribute are returned.

    When the first argument (conf) is a

    Kamailio::LDAPUtils::LDAPConnection, it will be used to perform the

@@ -1270,7 +1270,7 @@ ou=de");

    matching entries in the LDAP directory.

    When some requested_attributes are given, return an array with those

-   attibutes. When multiple entries match the query, the attribute lists

+   attributes. When multiple entries match the query, the attribute lists

    are concatenated.

 8. Kamailio::VDB

@@ -1371,7 +1371,7 @@ ou=de");

    This package handles virtual tables and is used by the Kamailio::VDB

    class to store information about valid tables. The package is not

-   inteded for end user access.

+   intended for end user access.

 17.1. new()

@@ -1622,7 +1622,7 @@ Chapter 3. Perl samples

    When processing SIP messages, you may want to use persistent data

    across multiple calls to your Perl functions. Your first option is to

    use global variables in your script. Unfortunately, these globals are

-   not visible from the mulitple instances of Kamailio. You may want to

+   not visible from the multiple instances of Kamailio. You may want to

    use a mechanism such as the IPC::Shareable shared memory access package

    to correct this.

@@ -119,8 +119,8 @@ modparam("app_python", "load", "/usr/local/etc/kamailio/myscript.py")

 3.3. mod_init_function (string)

-   The Python function to be executed by this module when it is initialied

-   by Kamailio.

+   The Python function to be executed by this module when it is

+   initialized by Kamailio.

    Default value is “mod_init”.

@@ -132,7 +132,7 @@ modparam("app_python", "mod_init_function", "my_mod_init")

 3.4. child_init_method (string)

    The Python function to be executed by this module when a new worker

-   process (child) is initialied by Kamailio.

+   process (child) is initialized by Kamailio.

    Default value is “child_init”.

@@ -135,8 +135,8 @@ modparam("app_python3", "load", "/usr/local/etc/kamailio/myscript.py")

 3.3. mod_init_function (string)

-   The Python function to be executed by this module when it is initialied

-   by Kamailio.

+   The Python function to be executed by this module when it is

+   initialized by Kamailio.

    Default value is “mod_init”.

@@ -148,7 +148,7 @@ modparam("app_python3", "mod_init_function", "my_mod_init")

 3.4. child_init_method (string)

    The Python function to be executed by this module when a new worker

-   process (child) is initialied by Kamailio.

+   process (child) is initialized by Kamailio.

    Default value is “child_init”.

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

-

 app_sqlang Module

 Daniel-Constantin Mierla

@@ -95,7 +94,7 @@ Chapter 1. Admin Guide

        Therefore sqlang_run() cannot execute functions from scripts loaded

        via sqlang_dofile() in config. This is kind of caching mode,

        avoiding reading file every time, but you must be sure you do not

-       have someting that is executed by default and requires access to

+       have something that is executed by default and requires access to

        SIP message. This environment is also used by KEMI framework for

        the config SIP routing functions.

@@ -317,7 +317,7 @@ modparam("auth", "qop", "auth")   # set qop=auth

    Note: nonce_count should be enabled only in stateful mode (a

    transaction should be created prior to the authentication check to

    absorb possible retransmissions and all the replies should be sent

-   statefuly, using t_reply()). If nonce_count and the authentication

+   statefully, using t_reply()). If nonce_count and the authentication

    checks are used in the stateless mode then all retransmissions will be

    challenged.

@@ -705,7 +705,7 @@ if (www_authenticate("realm", "subscriber")) {

 4.2. has_credentials(realm)

-   This function returns true of the request has Autorization or

+   This function returns true of the request has Authorization or

    Proxy-Authorization header with provided realm. The parameter can be

    string with pseudo-variables.

@@ -823,9 +823,9 @@ if (!auth_check("$fd", "subscriber", "1")) {

        to the user so he can decide what username and password to use.

        Usually this is domain of the host the server is running on.

        It must not be empty string “”. In case of REGISTER requests To

-       header field domain (e.g., varibale $td) can be used (because this

+       header field domain (e.g., variable $td) can be used (because this

        header field represents a user being registered), for all other

-       messages From header field domain can be used (e.g., varibale $fd).

+       messages From header field domain can be used (e.g., variable $fd).

        The string may contain pseudo variables.

      * passwd - the password to be used for authentication. Can contain

        config variables. The Username is taken from Auth header.

@@ -879,7 +879,7 @@ if (!pv_proxy_authenticate("$fd", "$avp(password)", "0")) {

 4.8.  pv_auth_check(realm, passwd, flags, checks)

    The function combines the functionalities of pv_www_authenticate and

-   pv_proxy_authenticate, first being exectuted if the SIP request is a

+   pv_proxy_authenticate, first being executed if the SIP request is a

    REGISTER, the second for the rest.

    Meaning of the first three parameters is the same as for

@@ -219,7 +219,7 @@ modparam("auth_db", "password_column_2", "ha1_2")

 3.6. calculate_ha1 (integer)

    This parameter tells the server whether it should use a pre-calculated

-   HA1 string or plaintext passwords for authentification.

+   HA1 string or plaintext passwords for authentication.

    If the parameter is set to 0 and the username parameter of credentials

    contains also “@domain” (some user agents append the domain to the

@@ -268,7 +268,7 @@ modparam("auth_db", "use_domain", 1)

    This parameter specifies of credentials to be fetch from database when

    the authentication is performed. The loaded credentials will be stored

-   in AVPs. If the AVP name is not specificaly given, it will be used a

+   in AVPs. If the AVP name is not specifically given, it will be used a

    NAME AVP with the same name as the column name.

    Parameter syntax:

@@ -276,7 +276,7 @@ modparam("auth_db", "use_domain", 1)

      * credential = (avp_specification '=' column_name) | (column_name)

      * avp_specification = '$avp(' + 'i:'ID | 's:'NAME | alias + ')'

-   Default value of this parameter is “NULL” (no credientials loaded).

+   Default value of this parameter is “NULL” (no credentials loaded).

    Example 1.8. load_credentials parameter usage

 ...

@@ -431,7 +431,7 @@ if (!proxy_authorize("$fd", "subscriber)) {

        user. All other requests: From header must match the authentication

        user. If bit 2 is set as well (flags==3), the ID check is skipped

        for INVITE, BYE, PRACK, UPDATE, MESSAGE - these requests can come

-       with anonymoys caller id.

+       with anonymous caller id.

        Additionally all domains in the checked URIs and the realm in the

        authentication header will be checked to match the provided realm

        parameter.

@@ -224,7 +224,7 @@ modparam("auth_ephemeral", "username_format", 0)

 3.3. sha_algorithm (integer)

-   The SHA algorhithm to be used for the Hash.

+   The SHA algorithm to be used for the Hash.

      * 0 - SHA1 (default, as per IETF/RFC)

      * 1 - SHA256

@@ -62,7 +62,7 @@ Phil Lavin

    List of Examples

-   1.1. “SIP-AVP” RADIUS AVP exmaples

+   1.1. “SIP-AVP” RADIUS AVP examples

    1.2. radius_config parameter usage

    1.3. service_type parameter usage

    1.4. auth_extra parameter usage

@@ -108,13 +108,13 @@ Chapter 1. Admin Guide

    to make sure that only well formed credentials will get to the server.

    We have implemented radius authentication according to

    draft-sterman-aaa-sip-00. This module requires the radiusclient-ng

-   library version 0.5.0 or higheer or freeradius-client which is

-   available from https://github.com/FreeRADIUS/freeradius-client/. You

-   can also install this library from distribution repositories.

+   library version 0.5.0 or higher or freeradius-client which is available

+   from https://github.com/FreeRADIUS/freeradius-client/. You can also

+   install this library from distribution repositories.

 2. Additional Credentials

-   When performing authentification, the RADIUS server may include

+   When performing authentication, the RADIUS server may include

    additional credentials in the response. This scheme is very useful in

    fetching additional user information from the RADIUS server without

    making extra queries.

@@ -130,7 +130,7 @@ Chapter 1. Admin Guide

    The RPID value may be fetch via this mechanism.

-   Example 1.1. “SIP-AVP” RADIUS AVP exmaples

+   Example 1.1. “SIP-AVP” RADIUS AVP examples

 ....

 "email:joe@yahoo.com"

     - STRING NAME AVP (email) with STRING VALUE (joe@yahoo.com)

@@ -156,7 +156,7 @@ Chapter 1. Admin Guide

 3.2. External Libraries or Applications

    The following libraries or applications must be installed before

-   compilling Kamailio with this module loaded:

+   compiling Kamailio with this module loaded:

    One of these libraries. Notice that development of radiusclient-ng has

    stopped, as the project merged with freeradius-client.

@@ -94,8 +94,8 @@ Chapter 1. Admin Guide

    of the new node. On large deployments, that can become rather complex.

    For example, as a replacement for IP trust relationships, the sender

    can hash the local IP with the secret shared key, add it in the header

-   and the receiver will check if the source ip hased with the key results

-   in the same value.

+   and the receiver will check if the source ip hashed with the key

+   results in the same value.

    Not being a challenge-reply mechanism, this can be used to authenticate

    SIP responses from trusted peers.

@@ -143,7 +143,7 @@ modparam("auth_xkeys", "xkey", "id=abc;name=xyz;value=secret;expires=72000")

 4.1.  auth_xkeys_add(hdr, kid, alg, data)

-   Add a header computed with the first key in the group kid, hasing with

+   Add a header computed with the first key in the group kid, hashing with

    algorithm alg over the content of parameter data. The parameters can

    include variables.

@@ -159,7 +159,7 @@ auth_xkeys_add("X-My-Key", "abc", "sha256", "$Ri:$fu:$ru:$hdr(CSeq)");

 4.2.  auth_xkeys_check(hdr, kid, alg, data)

    Check if the value of header hdr matches the value computed with the

-   first key in the group kid, hasing with algorithm alg over the content

+   first key in the group kid, hashing with algorithm alg over the content

    of parameter data. The parameters can include variables.

    The algorithm can be: sha256, sha384, sha512.

@@ -173,12 +173,12 @@ Chapter 1. Admin Guide

        all AVPs, regardless they have or not a script flag set (preserves

        the compatibility with the old naming schema).

      * avp_name = string | integer

-       string - might be any alphanumeric string, wich contain following

+       string - might be any alphanumeric string, which contain following

        characters: [a-z] [A-Z] [0-9] '_'

        integer - might be an unsigned integer, greater than zero, up to

        2^16-1

      * avp_alias = string

-       string - might be any alphanumeric string, wich contain following

+       string - might be any alphanumeric string, which contain following

        characters: [a-z] [A-Z] [0-9] '_'

    Example 1.1. AVP naming examples

@@ -374,7 +374,7 @@ modparam("avpops","db_scheme",

             'a' or 'A' means matching any of AVP name types ('i' and 's')

             (NOTE: matching_flags cannot be used with $db_scheme because

             the name of AVP to save in cannot be specified), the rest have

-            the meaning descriped in 'AVP naming format' chapter.

+            the meaning described in 'AVP naming format' chapter.

    This function can be used from REQUEST_ROUTE, FAILURE_ROUTE,

    BRANCH_ROUTE, LOCAL_ROUTE and ONREPLY_ROUTE.

@@ -534,7 +534,7 @@ avp_pushto("$br","$avp(i:680)");

           + le - less or equal

           + gt - greater than

           + ge - greater or equal

-          + re - regexp (regular exression match)

+          + re - regexp (regular expression match)

           + fm - fast match (see: man fnmatch)

           + and - bitwise 'and'

           + or - bitwise 'or'

@@ -280,7 +280,7 @@ bm_log_timer("test");

 6.1. benchmark.enable_global

    Enables/disables the module. Parameter may be -1, 0 or 1. See

-   discription of "enable" parameter.

+   description of "enable" parameter.

 6.2. benchmark.enable_timer

@@ -137,13 +137,13 @@ if (msg_status==503){ # blacklist 503 source for Retry-After seconds

      * 0x04 - connect failed (TCP, TLS or SCTP).

      * 0x08 - ICMP error (not currently used).

      * 0x10 - SIP transaction timeout.

-     * 0x20 - 503 reply (statefull mode only). For more details see

+     * 0x20 - 503 reply (stateful mode only). For more details see

        tmblst_503.

 Note

    TCP and TLS send and connect errors are handled per connection and not

-   per message. The connection blacklist ignore flags are inherithed from

+   per message. The connection blacklist ignore flags are inherited from

    the message that caused the connection establishment.

    Example 1.5. blst_set_ignore usage

@@ -137,7 +137,7 @@ Chapter 1. Admin Guide

        to be used and it has to be started by engage_media_proxy() to be

        able to keep track of the call's dialog and end it on timeout.

        Even when mediaproxy is unable to end the dialog because it was not

-       started with engage_media_proxy(), the callcantrol application is

+       started with engage_media_proxy(), the callcontrol application is

        still able to detect calls that did timeout sending media, by

        looking in the radius accounting records for entries recorded by

        mediaproxy for calls that did timeout. These calls will also be

@@ -226,7 +226,7 @@ modparam("call_control", "socket_timeout", 500)

    This is used by the rating engine which finds the rates to apply to a

    call based on caller's SIP URI, caller's SIP domain or caller's IP

-   address (whichever yields a rate forst, in this order).

+   address (whichever yields a rate first, in this order).

    Default value is “$avp(s:signaling_ip)”.

@@ -237,13 +237,13 @@ Chapter 1. Admin Guide

    at Kamailio startup. It can uses one routing tree (for one carrier), or

    if needed for every user a different routing tree (unique for each

    carrier) for number prefix based routing. It supports several route

-   tree domains, e.g. for failback routes or different routing rules for

+   tree domains, e.g. for fallback routes or different routing rules for

    VoIP and PSTN targets.

    Based on the tree, the module decides which number prefixes are

    forwarded to which gateway. It can also distribute the traffic by ratio

    parameters. Furthermore, the requests can be distributed by a hash

-   funcion to predictable destinations. The hash source is configurable,

+   function to predictable destinations. The hash source is configurable,

    two different hash functions are available.

    This modules scales up to more than a few million users, and is able to

@@ -286,7 +286,7 @@ Chapter 1. Admin Guide

    Starting with version 3.1 , if you want to use this module in failure

    routes, it is not needed to call“append_branch()” after rewriting the

    request URI in order to relay the message to the new target. Its also

-   supportes the usage of database derived failure routing descisions with

+   supports the usage of database derived failure routing decisions with

    the carrierfailureroute table.

 2. Dependencies

@@ -459,9 +459,9 @@ modparam("carrierroute", "db_load_description", 0)

 3.12. match_mode (integer)

    The number of individual characters that are used for matching. Valid

-   values are 10 or 128. When you specifiy 10, only digits will be used

-   for matching, this operation mode is equivalent to the old behaviour.

-   When configured with 128, all standard ascii chars are available for

+   values are 10 or 128. When you specify 10, only digits will be used for

+   matching, this operation mode is equivalent to the old behaviour. When

+   configured with 128, all standard ascii chars are available for

    matching. Please be aware that memory requirements for storing the

    routing tree in shared memory will also increase by a factor of 12.8.

@@ -540,9 +540,9 @@ descavp)

    Request URI is rewritten using rewrite_user and the given hash source

    and algorithm. Returns -1 if there is no data found or an empty rewrite

    host on the longest match is found. On success also the description is

-   stored in the given AVP (if obmitted, nothing is stored in an AVP).

-   This is useful if you need some additional informations that belongs to

-   each gw, like the destination or the number of channels.

+   stored in the given AVP (if omitted, nothing is stored in an AVP). This

+   is useful if you need some additional informations that belongs to each

+   gw, like the destination or the number of channels.

    Depending on the value of the avoid_failed_destinations module

    parameter, the function pays special attention to the failurerouting

@@ -589,16 +589,16 @@ hash_source, descavp)

    Request URI is rewritten using rewrite_user and the given hash source

    and algorithm. Returns -1 if there is no data found or an empty rewrite

    host on the longest match is found. On success also the description is

-   stored in the given AVP (if obmitted, nothing is stored in an AVP).

-   This is useful if you need some additional informations that belongs to

-   each gw, like the destination or the number of channels. This function

-   is only usable with rewrite_user and prefix_matching containing a valid

+   stored in the given AVP (if omitted, nothing is stored in an AVP). This

+   is useful if you need some additional informations that belongs to each

+   gw, like the destination or the number of channels. This function is

+   only usable with rewrite_user and prefix_matching containing a valid

    string. This string needs to be numerical if the match_mode parameter

    is set to 10.

    It uses the standard CRC32 algorithm to calculate the hash values. In

    contrast to the normal cr_route function the backup rules of (now

-   obselete) cr_prime_route is used. This means not the configured

+   obsolete) cr_prime_route is used. This means not the configured

    probabilities will be used, only a fixed hash distribution. This makes

    sense to distribute incoming register requests e.g. to a bunch of

    registrar servers. If one of the hash targets is not available and

@@ -883,13 +883,13 @@ failure_route[1] {

    All traffic will be equally distributed between the hosts, both are

    active. The hash algorithm will working over the [1,2] set, messages

    hashed to one will go to the first host, the other to the second one.

-   Don't use a hash index value of zero. If you ommit the hash completly,

+   Don't use a hash index value of zero. If you omit the hash completely,

    the module gives them a autogenerated value, starting from one.

    Use the “NULL” prefix to specify an empty prefix in the config file.

    Please note that the prefix is matched against the request URI (or to

    URI), if they did not contain a valid (numerical) URI, no match is

-   possible. So for loadbalancing purposes e.g. for your registrars, you

+   possible. So for load-balancing purposes e.g. for your registrars, you

    should use an empty prefix.

 ...

 domain proxy {

@@ -989,9 +989,9 @@ domain register {

    section.

    This table provides also a “carrier 1” routing rule for the “49”

-   prefix, that is only choosen if some message flags are set. If this

+   prefix, that is only chosen if some message flags are set. If this

    flags are not set, the other two rules are used. The “strip”, “mask”

-   and “comment” colums are omitted for brevity.

+   and “comment” columns are omitted for brevity.

    Example 1.23. Example database content - simple carrierfailureroute

    table

@@ -1006,8 +1006,8 @@ domain register {

    This table contains two failure routes for the “gw.carrier1-1” and “-2”

    gateways. For any (failure) reply code the respective next domain is

-   choosen. After that no more failure routes are available, an error will

-   be returned from the “cr_next_domain” function. Not all table colums

+   chosen. After that no more failure routes are available, an error will

+   be returned from the “cr_next_domain” function. Not all table columns

    are show here for brevity.

    For each failure route domain and carrier that is added to the

@@ -1033,13 +1033,13 @@ domain register {

    for example that indicates that ringing has happened. If this flag is

    set, there will be no further forwarding, because next_domain is empty.

    In the second and third routes are certain gateway errors matched, if

-   this errors have occurred, then the next domain will be choosen. Note

+   this errors have occurred, then the next domain will be chosen. Note

    that the reply_code must be 3 characters wide, and only the "."

    character is accepted as wildcard.The last route does forwarding

    according some flags, e.g. the customer came from a certain carrier,

    and has call-forwarding deactivated. In order to use the routing that

    is specified above, a matching carrierroute table must be provided,

-   that holds domain entries for this routing rules. Not all table colums

+   that holds domain entries for this routing rules. Not all table columns

    are show here for brevity.

    Example 1.25. Example database content - carrier_name table