Module: kamailio
Branch: 5.1
Commit: 468403d98d8aec4a833e3f9a9be1913efe9897c8
URL: https://github.com/kamailio/kamailio/commit/468403d98d8aec4a833e3f9a9be1913…
Author: Henning Westerholt <hw(a)skalatan.de>
Committer: Henning Westerholt <hw(a)skalatan.de>
Date: 2019-09-12T23:40:58+02:00
acc: extend documentation related to flag usage
(cherry picked from commit 40905046baab49fb3baf0f2fdded1307b023d08a)
---
Modified: src/modules/acc/doc/acc_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/468403d98d8aec4a833e3f9a9be1913…
Patch: https://github.com/kamailio/kamailio/commit/468403d98d8aec4a833e3f9a9be1913…
---
diff --git a/src/modules/acc/doc/acc_admin.xml b/src/modules/acc/doc/acc_admin.xml
index 2588243f7c..36753ae10c 100644
--- a/src/modules/acc/doc/acc_admin.xml
+++ b/src/modules/acc/doc/acc_admin.xml
@@ -489,7 +489,9 @@ modparam("acc", "early_media", 1)
<title><varname>failed_transaction_flag</varname> (integer)</title>
<para>
Per transaction flag which says if the transaction should be
- accounted also in case of failure (status>=300).
+ accounted also in case of failure (SIP status code >= 300).
+ This flag triggers accouting when the whole transaction fails
+ (on the server side).
</para>
<para>
Default value is not-set (no flag).
@@ -679,12 +681,12 @@ modparam("acc", "log_flag", 2)
<para>
Request flag which needs to be set to account missed calls via syslog.
This can be used to e.g. account failures during the call setup phase
- from the callee side, for example if you do forking to several
+ from the callee (client) side, for example if you do forking to several
destinations.
</para>
<para>
- Keep in mind that this flag is reset after processing. Therefore it is
- necessary to set it again e.g. in a failure_route if you do serial
+ Keep in mind that this flag is reset after branch completion. Therefore
+ it is necessary to set it again e.g. in a failure_route if you do serial
forking and want to log all attempts.
</para>
<para>
@@ -775,8 +777,15 @@ modparam("acc", "db_flag", 2)
<section id="acc.p.db_missed_flag">
<title><varname>db_missed_flag</varname> (integer)</title>
<para>
- Request flag which needs to be set to account missed
- calls -- database specific.
+ Request flag which needs to be set to account missed calls via database.
+ This can be used to e.g. account failures during the call setup phase
+ from the callee (client) side, for example if you do forking to several
+ destinations.
+ </para>
+ <para>
+ Keep in mind that this flag is reset after branch completion. Therefore
+ it is necessary to set it again e.g. in a failure_route if you do serial
+ forking and want to log all attempts.
</para>
<para>
Default value is not-set (no flag).
Module: kamailio
Branch: master
Commit: 40905046baab49fb3baf0f2fdded1307b023d08a
URL: https://github.com/kamailio/kamailio/commit/40905046baab49fb3baf0f2fdded130…
Author: Henning Westerholt <hw(a)skalatan.de>
Committer: Henning Westerholt <hw(a)skalatan.de>
Date: 2019-09-12T21:53:21+02:00
acc: extend documentation related to flag usage
---
Modified: src/modules/acc/doc/acc_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/40905046baab49fb3baf0f2fdded130…
Patch: https://github.com/kamailio/kamailio/commit/40905046baab49fb3baf0f2fdded130…
---
diff --git a/src/modules/acc/doc/acc_admin.xml b/src/modules/acc/doc/acc_admin.xml
index 61e27a196e..a0794ca562 100644
--- a/src/modules/acc/doc/acc_admin.xml
+++ b/src/modules/acc/doc/acc_admin.xml
@@ -489,7 +489,9 @@ modparam("acc", "early_media", 1)
<title><varname>failed_transaction_flag</varname> (integer)</title>
<para>
Per transaction flag which says if the transaction should be
- accounted also in case of failure (status>=300).
+ accounted also in case of failure (SIP status code >= 300).
+ This flag triggers accouting when the whole transaction fails
+ (on the server side).
</para>
<para>
Default value is not-set (no flag).
@@ -679,12 +681,12 @@ modparam("acc", "log_flag", 2)
<para>
Request flag which needs to be set to account missed calls via syslog.
This can be used to e.g. account failures during the call setup phase
- from the callee side, for example if you do forking to several
+ from the callee (client) side, for example if you do forking to several
destinations.
</para>
<para>
- Keep in mind that this flag is reset after processing. Therefore it is
- necessary to set it again e.g. in a failure_route if you do serial
+ Keep in mind that this flag is reset after branch completion. Therefore
+ it is necessary to set it again e.g. in a failure_route if you do serial
forking and want to log all attempts.
</para>
<para>
@@ -775,8 +777,15 @@ modparam("acc", "db_flag", 2)
<section id="acc.p.db_missed_flag">
<title><varname>db_missed_flag</varname> (integer)</title>
<para>
- Request flag which needs to be set to account missed
- calls -- database specific.
+ Request flag which needs to be set to account missed calls via database.
+ This can be used to e.g. account failures during the call setup phase
+ from the callee (client) side, for example if you do forking to several
+ destinations.
+ </para>
+ <para>
+ Keep in mind that this flag is reset after branch completion. Therefore
+ it is necessary to set it again e.g. in a failure_route if you do serial
+ forking and want to log all attempts.
</para>
<para>
Default value is not-set (no flag).
The #!ifdef/#endif statement parsing of the kamailio.cfg does not work correctly on a mismatch of #!ifdef/#!define statements. In some cases will just ignore the #!defines and parses the cfg file without the statements.
version: kamailio 5.3.0-pre0 (x86_64/linux) ed10d7
> henning@linux:~/repositories/kamailio/src> ./kamailio -c -f ../etc/test-define.cfg
> 0(9501) CRITICAL: <core> [core/cfg.y:3539]: yyerror_at(): parse error in config file /home/henning/repositories/kamailio/src/../etc/test-define.cfg, line 12, column 8: syntax error
> 0(9501) CRITICAL: <core> [core/cfg.y:3539]: yyerror_at(): parse error in config file /home/henning/repositories/kamailio/src/../etc/test-define.cfg, line 12, column 8: unknown config variable
> 0(9501) CRITICAL: <core> [core/cfg.y:3536]: yyerror_at(): parse error in config file /home/henning/repositories/kamailio/src/../etc/test-define.cfg, line 12, column 9-11:
> ERROR: bad config file (3 errors)
Test cfg to show the problem:
```
henning@linux:~/repositories/kamailio/etc> cat test-define.cfg
#!KAMAILIO
#!define foo
#!ifdef foobar1
#!ifdef foobar2
#!endif
#!endif
#!endif
#!ifdef bar
invalid=123
#else
children=8
#!endif
request_route {
;
}
```
The "bar" condition is parsed, even if the #!define was not set. The WARN message is also not shown in this error case.
Probably the easist fix would be to stop kamailio startup on a mismatch of #!ifdef/#endif statements and output ERROR instead of the current WARN.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2057