Module: sip-router
Branch: 4.1
Commit: 66161fa4e9d949063ffb5f0f3d6fd086b0ceece8
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=66161fa…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: Tue Sep 16 19:05:57 2014 +0200
dialog: check if the transaction is created for BYE closing the dialog
- if not, release the dialog, because there will be no tm callbacks
called later to release it. In this way avoid zombie dialog.
- reported by Ovidiu Sas, FS#424
(cherry picked from commit 02e43f87b2fa3be61bc4c63a9f8359457e3e0484)
---
Module: sip-router
Branch: master
Commit: c4c25a07c77ca5e2ceccd11cdab29ed93d86d29a
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=c4c25a0…
Author: Olle E. Johansson <oej(a)edvina.net>
Committer: Olle E. Johansson <oej(a)edvina.net>
Date: Thu Sep 25 22:09:15 2014 +0200
enum: Minor updates to docs. Added section ID's
---
modules/enum/README | 6 +++---
modules/enum/doc/enum_admin.xml | 23 ++++++++++++-----------
2 files changed, 15 insertions(+), 14 deletions(-)
diff --git a/modules/enum/README b/modules/enum/README
index 5714184..2f10a2c 100644
--- a/modules/enum/README
+++ b/modules/enum/README
@@ -185,9 +185,9 @@ modparam("enum", "branchlabel", "i")
3.5. bl_algorithm (string)
- This parameter determines which algorithm i_enum_query() will use to
- select the position in the DNS tree where the infrastructure tree
- branches off the user ENUM tree.
+ This parameter determines which algorithm the i_enum_query() function
+ will use to select the position in the DNS tree where the
+ infrastructure tree branches off the user ENUM tree.
If set to "cc", i_enum_query() will always insert the label at the
country-code level. Examples: i.1.e164.arpa, i.3.4.e164.arpa,
diff --git a/modules/enum/doc/enum_admin.xml b/modules/enum/doc/enum_admin.xml
index 4b80896..939c5fc 100644
--- a/modules/enum/doc/enum_admin.xml
+++ b/modules/enum/doc/enum_admin.xml
@@ -84,7 +84,7 @@
and -1 if not.
</para>
<para>
- Enum module also implements is_from_user_enum function.
+ Enum module also implements <function>is_from_user_enum</function> function.
This function does an enum lookup on the from user and
returns true if found, false otherwise.
</para>
@@ -105,7 +105,7 @@
<section>
<title>Parameters</title>
- <section>
+ <section id="enum.p.domain_suffix">
<title><varname>domain_suffix</varname> (string)</title>
<para>
The domain suffix to be added to the domain name obtained from
@@ -123,7 +123,7 @@ modparam("enum", "domain_suffix", "e1234.arpa.")
</example>
</section>
- <section>
+ <section id="enum.p.tel_uri_params">
<title><varname>tel_uri_params</varname> (string)</title>
<para>
A string whose contents is appended to each new tel URI in the
@@ -145,7 +145,7 @@ modparam("enum", "tel_uri_params", ";npdi")
</programlisting>
</example>
</section>
- <section>
+ <section id="enum.p.i_enum_suffix">
<title><varname>i_enum_suffix</varname> (string)</title>
<para>
The domain suffix to be used for i_enum_query() lookups.
@@ -161,7 +161,7 @@ modparam("enum", "i_enum_suffix", "e1234.arpa.")
</programlisting>
</example>
</section>
- <section>
+ <section id="enum.p.branchlabel">
<title><varname>branchlabel</varname> (string)</title>
<para>
This parameter determines which label i_enum_query() will use
@@ -177,10 +177,11 @@ modparam("enum", "branchlabel", "i")
</programlisting>
</example>
</section>
- <section>
+ <section id="enum.p.bl_algorithm">
<title><varname>bl_algorithm</varname> (string)</title>
<para>
- This parameter determines which algorithm i_enum_query() will use
+ This parameter determines which algorithm the
+ <function>i_enum_query()</function> function will use
to select the position in the DNS tree where the infrastructure tree
branches off the user ENUM tree.
</para>
@@ -234,7 +235,7 @@ modparam("enum", "bl_algorithm", "txt")
<section>
<title>Functions</title>
- <section>
+ <section id="enum.f.enum_query">
<title>
<function moreinfo="none">enum_query(["suffix"[,"service"]])</function>
</title>
@@ -288,7 +289,7 @@ enum_query("e164.arpa.","+sip+voice:sip");
</example>
</section>
- <section>
+ <section id="enum.f.enum_pv_query">
<title>
<function moreinfo="none">enum_pv_query("pvar"[,"suffix"[,"service"]])</function>
</title>
@@ -347,7 +348,7 @@ enum_pv_query("$avp(i:100)","e164.arpa.","+sip+voice:sip");
</example>
</section>
- <section>
+ <section id="enum.f.i_enum_query">
<title>
<function moreinfo="none">i_enum_query(["suffix"[,"service"]])</function>
</title>
@@ -363,7 +364,7 @@ enum_pv_query("$avp(i:100)","e164.arpa.","+sip+voice:sip");
</para>
</section>
- <section>
+ <section id="enum.f.is_from_user_enum">
<title><function moreinfo="none">is_from_user_enum()</function></title>
<para>
Checks if the user part of from <abbrev>URI</abbrev>
Module: sip-router
Branch: master
Commit: 77462923e9c6f34c96f1d50440334964f0277efc
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=7746292…
Author: Olle E. Johansson <oej(a)edvina.net>
Committer: Olle E. Johansson <oej(a)edvina.net>
Date: Thu Sep 25 21:31:55 2014 +0200
Pike: Documentation updates
---
modules/pike/README | 42 +++++++++++++++++++-------------------
modules/pike/doc/pike_admin.xml | 28 +++++++++++++-------------
2 files changed, 35 insertions(+), 35 deletions(-)
diff --git a/modules/pike/README b/modules/pike/README
index 732db73..bb7466b 100644
--- a/modules/pike/README
+++ b/modules/pike/README
@@ -78,12 +78,12 @@ Chapter 1. Admin Guide
1. Overview
- The module keeps trace of all (or selected ones) incoming request's IP
- source and blocks the ones that exceeded some limit. Works simultaneous
- for IPv4 and IPv6 addresses.
+ The pike module keeps trace of all (or selected ones) incoming
+ request's IP source and blocks the ones that exceed the limit. It works
+ simultaneously for IPv4 and IPv6 addresses.
The module does not implement any actions on blocking - it just simply
- reports that there is a high traffic from an IP; what to do, is the
+ reports that there is high traffic from an IP; what to do, is the
administator decision (via scripting).
2. Dependencies
@@ -114,13 +114,13 @@ Chapter 1. Admin Guide
Time period in seconds used for sampling (or the sampling accuracy).
The smaller the better, but slower. If you want to detect peeks, use a
small one. To limit the access (like total number of requests on a long
- period of time) to a proxy resource (a gateway for ex), use a bigger
- value of this parameter.
+ period of time) to a proxy resource (a gateway for example), use a
+ bigger value of this parameter.
- IMPORTANT: a too small value may lead to performance penalties due
+ IMPORTANT: a too small value may lead to performance penalties due to
timer process overloading.
- Default value is 2.
+ Default value is "2".
Example 1.1. Set sampling_time_unit parameter
...
@@ -132,7 +132,7 @@ modparam("pike", "sampling_time_unit", 10)
How many requests should be allowed per sampling_time_unit before
blocking all the incoming request from that IP. Practically, the
blocking limit is between ( let's have x=reqs_density_per_unit) x and
- 3*x for IPv4 addresses and between x and 8*x for ipv6 addresses.
+ 3*x for IPv4 addresses and between x and 8*x for IPv6 addresses.
Default value is 30.
@@ -143,13 +143,13 @@ modparam("pike", "reqs_density_per_unit", 30)
3.3. remove_latency (integer)
- For how long the IP address will be kept in memory after the last
- request from that IP address. It's a sort of timeout value, in seconds.
- Note that it is not the duration to keep the IP in state 'blocked'. An
- IP is unblocked next occurence of 'sampling_time_unit' that does not
- exceed 'reqs_density_per_unit'. Keeping an IP in memory results in
- faster reaching of blocked state -- see the notes about the limits of
- getting to state 'blocked'.
+ Speciies for how long the IP address will be kept in memory after the
+ last request from that IP address. It's a sort of timeout value, in
+ seconds. Note that it is not the duration to keep the IP in state
+ 'blocked'. An IP is unblocked next occurence of 'sampling_time_unit'
+ that does not exceed 'reqs_density_per_unit'. Keeping an IP in memory
+ results in faster reaching of blocked state -- see the notes about the
+ limits of getting to state 'blocked'.
Default value is 120.
@@ -160,8 +160,8 @@ modparam("pike", "remove_latency", 130)
3.4. pike_log_level (integer)
- Log level to be used by module to auto report the blocking (only first
- time) and unblocking of IPs detected as source of floods.
+ Syslog log level to be used by module to auto report the blocking (only
+ first time) and unblocking of IPs detected as source of floods.
Default value is 1 (L_WARN).
@@ -176,8 +176,8 @@ modparam("pike", "pike_log_level", -1)
4.1. pike_check_req()
- Process the source IP of the current request and returns false if the
- IP was exceeding the blocking limit.
+ Process the source IP of the current request and return false if the IP
+ was exceeding the blocking limit.
Return codes:
* 1 (true) - IP is not to be blocked or internal error occured.
@@ -185,7 +185,7 @@ modparam("pike", "pike_log_level", -1)
Warning
IMPORTANT: in case of internal error, the function returns true to
avoid reporting the current processed IP as blocked.
- * -1 (false) - IP is source of flooding, being previously detected
+ * -1 (false) - IP is source of flooding, previously detected
* -2 (false) - IP is detected as a new source of flooding - first
time detection
diff --git a/modules/pike/doc/pike_admin.xml b/modules/pike/doc/pike_admin.xml
index 9ccc91c..bd4b846 100644
--- a/modules/pike/doc/pike_admin.xml
+++ b/modules/pike/doc/pike_admin.xml
@@ -16,13 +16,13 @@
<section>
<title>Overview</title>
<para>
- The module keeps trace of all (or selected ones) incoming request's IP
- source and blocks the ones that exceeded some limit.
- Works simultaneous for IPv4 and IPv6 addresses.
+ The pike module keeps trace of all (or selected ones) incoming request's IP
+ source and blocks the ones that exceed the limit.
+ It works simultaneously for IPv4 and IPv6 addresses.
</para>
<para>
The module does not implement any actions on blocking - it just simply
- reports that there is a high traffic from an IP; what to do, is
+ reports that there is high traffic from an IP; what to do, is
the administator decision (via scripting).
</para>
</section>
@@ -64,16 +64,16 @@
Time period in seconds used for sampling (or the sampling accuracy).
The smaller the better, but slower. If you want to detect peeks, use
a small one. To limit the access (like total number of requests on a
- long period of time) to a proxy resource (a gateway for ex), use
+ long period of time) to a proxy resource (a gateway for example), use
a bigger value of this parameter.
</para>
<para>
IMPORTANT: a too small value may lead to performance penalties due
- timer process overloading.
+ to timer process overloading.
</para>
<para>
<emphasis>
- Default value is 2.
+ Default value is <quote>2</quote>.
</emphasis>
</para>
<example>
@@ -88,10 +88,10 @@ modparam("pike", "sampling_time_unit", 10)
<section id="pike.p.reqs_density_per_unit">
<title><varname>reqs_density_per_unit</varname> (integer)</title>
<para>
- How many requests should be allowed per sampling_time_unit before
- blocking all the incoming request from that IP. Practically, the
+ How many requests should be allowed per <varname>sampling_time_unit</varname>
+ before blocking all the incoming request from that IP. Practically, the
blocking limit is between ( let's have x=reqs_density_per_unit) x
- and 3*x for IPv4 addresses and between x and 8*x for ipv6 addresses.
+ and 3*x for IPv4 addresses and between x and 8*x for IPv6 addresses.
</para>
<para>
<emphasis>
@@ -110,7 +110,7 @@ modparam("pike", "reqs_density_per_unit", 30)
<section id="pike.p.remove_latency">
<title><varname>remove_latency</varname> (integer)</title>
<para>
- For how long the IP address will be kept in memory after the last
+ Speciies for how long the IP address will be kept in memory after the last
request from that IP address. It's a sort of timeout value, in seconds.
Note that it is not the duration to keep the IP in state 'blocked'. An
IP is unblocked next occurence of 'sampling_time_unit' that does not
@@ -135,7 +135,7 @@ modparam("pike", "remove_latency", 130)
<section id="pike.p.pike_log_level">
<title><varname>pike_log_level</varname> (integer)</title>
<para>
- Log level to be used by module to auto report the blocking (only first
+ Syslog log level to be used by module to auto report the blocking (only first
time) and unblocking of IPs detected as source of floods.
</para>
<para>
@@ -162,7 +162,7 @@ modparam("pike", "pike_log_level", -1)
<function moreinfo="none">pike_check_req()</function>
</title>
<para>
- Process the source IP of the current request and returns false if
+ Process the source IP of the current request and return false if
the IP was exceeding the blocking limit.
</para>
<para>
@@ -181,7 +181,7 @@ modparam("pike", "pike_log_level", -1)
<listitem>
<para>
<emphasis>-1 (false)</emphasis> - IP is source of
- flooding, being previously detected
+ flooding, previously detected
</para>
</listitem>
<listitem>
Module: sip-router
Branch: master
Commit: 6b96fa92093ec41ae343da1537afd82666c9be5c
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=6b96fa9…
Author: Olle E. Johansson <oej(a)edvina.net>
Committer: Olle E. Johansson <oej(a)edvina.net>
Date: Thu Sep 25 21:45:23 2014 +0200
xlog: Minor documentation updates
Added section ID's
---
modules/xlog/README | 8 ++++----
modules/xlog/doc/xlog_admin.xml | 28 ++++++++++++++--------------
2 files changed, 18 insertions(+), 18 deletions(-)
diff --git a/modules/xlog/README b/modules/xlog/README
index 416473d..c770cf6 100644
--- a/modules/xlog/README
+++ b/modules/xlog/README
@@ -269,10 +269,10 @@ xdbg("time $Cbx[$Tf]$Cxx method ($rm) r-uri ($ru)\n");
5.3. xlogl([ [facility,] level,] format)
- Similar to xlog(), in addition is printing cfg line number at the
- beginning of message.
+ Similar to xlog(), in addition prints configuration file line number at
+ the beginning of message.
5.4. xdbgl(format)
- Similar to xdbg(), in addition is printing cfg line number at the
- beginning of message.
+ Similar to xdbg(), in addition prints configuration file line number at
+ the beginning of message.
diff --git a/modules/xlog/doc/xlog_admin.xml b/modules/xlog/doc/xlog_admin.xml
index 24d26a9..dad27a6 100644
--- a/modules/xlog/doc/xlog_admin.xml
+++ b/modules/xlog/doc/xlog_admin.xml
@@ -28,8 +28,8 @@
<title>Implemented Specifiers</title>
<para>
In the xlog function, you use pseudo-variables, that are a part
- of &kamailio; core and are used by other modules as well (e.g., avpops
- in the function avp_printf())
+ of &kamailio; core and are used by other modules as well (e.g., <emphasis>avpops</emphasis>
+ in the function <function>avp_printf()</function>)
</para>
<para>
The most important changes from earlier versions of &kamailio; are:
@@ -93,7 +93,7 @@
</section>
<section>
<title>Parameters</title>
- <section>
+ <section id="xlog.p.buf_size">
<title><varname>buf_size</varname> (integer)</title>
<para>
Maximum size of the log message.
@@ -112,7 +112,7 @@ modparam("xlog", "buf_size", 8192)
</programlisting>
</example>
</section>
- <section>
+ <section id="xlog.p.force_color">
<title><varname>force_color</varname> (integer)</title>
<para>
When set to 1, forces color printing even if log_stderror=0.
@@ -131,7 +131,7 @@ modparam("xlog", "force_color", 0)
</programlisting>
</example>
</section>
- <section>
+ <section id="xlog.p.long_format">
<title><varname>long_format</varname> (integer)</title>
<para>
When set to 1, prints config file name in xlogl() and xdbgl()
@@ -151,7 +151,7 @@ modparam("xlog", "long_format", 1)
</programlisting>
</example>
</section>
- <section>
+ <section id="xlog.p.varname">
<title><varname>prefix</varname> (str)</title>
<para>
Prefix to be printed before the log message.
@@ -170,7 +170,7 @@ modparam("xlog", "prefix", "-xlog: ")
</programlisting>
</example>
</section>
- <section>
+ <section id="xlog.p.log_facility">
<title><varname>log_facility</varname> (string)</title>
<para>
Syslog facility to be used when printing xlog messages.
@@ -188,7 +188,7 @@ modparam("xlog", "log_facility", "LOG_DAEMON")
</programlisting>
</example>
</section>
- <section>
+ <section id="xlog.p.log_colors">
<title><varname>log_colors</varname> (string)</title>
<para>
Update terminal colors used by core for log levels (when log_stderr=1
@@ -215,7 +215,7 @@ modparam("xlog", "log_colors", "L_ERR=cr;L_WARN=px")
</section>
<section>
<title>Functions</title>
- <section>
+ <section id="xlog.f.xlog">
<title>
<function moreinfo="none">xlog([ [facility,] level,] format)</function>
</title>
@@ -318,7 +318,7 @@ xlog("LOG_LOCAL3", "L_ERR", "this message will be sent to syslog facility LOG_LO
</example>
</section>
- <section>
+ <section id="xlog.f.xdbg">
<title>
<function moreinfo="none">xdbg(format)</function>
</title>
@@ -345,21 +345,21 @@ xdbg("time $Cbx[$Tf]$Cxx method ($rm) r-uri ($ru)\n");
</programlisting>
</example>
</section>
- <section>
+ <section id="xlog.f.xlogl">
<title>
<function moreinfo="none">xlogl([ [facility,] level,] format)</function>
</title>
<para>
- Similar to xlog(), in addition is printing cfg line number
+ Similar to xlog(), in addition prints configuration file line number
at the beginning of message.
</para>
</section>
- <section>
+ <section id="xlog.f.xdbgl">
<title>
<function moreinfo="none">xdbgl(format)</function>
</title>
<para>
- Similar to xdbg(), in addition is printing cfg line number
+ Similar to xdbg(), in addition prints configuration file line number
at the beginning of message.
</para>
</section>
Module: sip-router
Branch: master
Commit: fa6154cc346b77934ad57d0c96b8e8c7c1913dbc
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=fa6154c…
Author: Olle E. Johansson <oej(a)edvina.net>
Committer: Olle E. Johansson <oej(a)edvina.net>
Date: Thu Sep 25 20:46:03 2014 +0200
statistics: minor update of docs
---
modules/statistics/README | 5 +++--
modules/statistics/doc/statistics_admin.xml | 16 ++++++++--------
2 files changed, 11 insertions(+), 10 deletions(-)
diff --git a/modules/statistics/README b/modules/statistics/README
index 04b1bbd..03798f0 100644
--- a/modules/statistics/README
+++ b/modules/statistics/README
@@ -107,7 +107,8 @@ modparam("statistics", "variable", "active_calls/no_reset")
Meaning of the parameters is as follows:
* variable - variable to be updated (it can be a string or a
pseudovariable);
- * value - value to update with; it may be also negative.
+ * value - value to update with; it may be also negative (it can be a
+ string or pseudovariable).
This function can be used from ANY_ROUTE.
@@ -124,7 +125,7 @@ update_stat("$var(a_calls)", "-1");
Resets to zero the value of the statistic variable.
Meaning of the parameters is as follows:
- * variable - variable to be reset-ed (it can be a string or a
+ * variable - variable to be reset (it can be a string or a
pseudovariable).
This function can be used from REQUEST_ROUTE, BRANCH_ROUTE,
diff --git a/modules/statistics/doc/statistics_admin.xml b/modules/statistics/doc/statistics_admin.xml
index 1e4dab5..4997d7b 100644
--- a/modules/statistics/doc/statistics_admin.xml
+++ b/modules/statistics/doc/statistics_admin.xml
@@ -9,7 +9,7 @@
<chapter>
<title>&adminguide;</title>
- <section>
+ <section id="statistics.overview">
<title>Overview</title>
<para>The <acronym>Statistics</acronym> module is a wrapper over the
@@ -21,7 +21,7 @@
implementation of any kind of statistic scenario.</para>
</section>
- <section>
+ <section id="statistics.dependencies">
<title>Dependencies</title>
<section>
@@ -48,10 +48,10 @@
</section>
</section>
- <section>
+ <section id="statistics.parameters">
<title>Parameters</title>
- <section>
+ <section id="statistics.p.variable">
<title><varname>variable</varname> (string)</title>
<para>Name of a new statistic variable. The name may be followed by
@@ -75,10 +75,10 @@ modparam("statistics", "variable", "active_calls/no_reset")
</section>
</section>
- <section>
+ <section id="statistics.functions">
<title>Functions</title>
- <section>
+ <section id="statistics.f.update_stat">
<title><function
moreinfo="none">update_stat(variable,value)</function></title>
@@ -115,7 +115,7 @@ update_stat("$var(a_calls)", "-1");
</example>
</section>
- <section>
+ <section id="statistics.f.reset_stat">
<title><function moreinfo="none">reset_stat(variable)</function></title>
<para>Resets to zero the value of the statistic variable.</para>
@@ -124,7 +124,7 @@ update_stat("$var(a_calls)", "-1");
<itemizedlist>
<listitem>
- <para><emphasis>variable</emphasis> - variable to be reset-ed (it
+ <para><emphasis>variable</emphasis> - variable to be reset (it
can be a string or a pseudovariable).</para>
</listitem>
</itemizedlist>
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has been changed. The changes are listed below. For full information about what has changed, visit the URL and click the History tab.
FS#470 - mtree README is missing parameters
User who did this: Juha Heinanen (jh)
Category: Core -> Module
Task Type: Bug Report -> Improvement
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=470
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Juha Heinanen (jh)
Attached to Project - sip-router
Summary - mtree README is missing parameters
Task Type - Bug Report
Category - Core
Status - New
Assigned To -
Operating System - All
Severity - Low
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - mtree README is missing description of parameters pv_dstid, pv_weight, and pv_count. the last does not appear to have any code associated with it.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=470
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.