Module: kamailio
Branch: 5.3
Commit: a41dcf3259d72dfecf4cd34638d885734dc7a5ea
URL: https://github.com/kamailio/kamailio/commit/a41dcf3259d72dfecf4cd34638d8857…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2020-06-05T12:31:49+02:00
modules: readme files regenerated - modules ... [skip ci]
---
Modified: src/modules/siptrace/README
---
Diff: https://github.com/kamailio/kamailio/commit/a41dcf3259d72dfecf4cd34638d8857…
Patch: https://github.com/kamailio/kamailio/commit/a41dcf3259d72dfecf4cd34638d8857…
---
diff --git a/src/modules/siptrace/README b/src/modules/siptrace/README
index 5eab39eb23..df5b99f7cc 100644
--- a/src/modules/siptrace/README
+++ b/src/modules/siptrace/README
@@ -472,8 +472,10 @@ modparam("siptrace", "auth_key", "spoihepuirthpeuia")
Store or forward the current processed SIP message/transaction/dialog
in database. It is stored in the form prior applying changes made to
- it. Based on mode, one can trace the current message('m' - default),
- the current transaction('t') or the current dialog('d').
+ it. Based on mode, one can trace the current message('m'), the current
+ transaction('t') or the current dialog('d'). If no mode is given, it
+ falls back to the default mode - transaction tracking when trace_flag
+ is set, otherwise only the current message.
Meaning of the parameters is as follows:
* address - The address in form of SIP URI where to send a duplicate
@@ -564,13 +566,13 @@ kamcmd siptrace.status check
6. Database setup
- Before running Kamailio with siptrace, you have to setup the database
- tables where the module will store the data. For that, if the table
- were not created by the installation script or you choose to install
- everything by yourself you can use the siptrace-create.sql SQL script
- in the database directories in the kamailio/scripts folder as template.
- You can also find the complete database documentation on the project
- webpage,
+ Before running Kamailio with siptrace and activated trace_to_database
+ parameter, you have to setup the database tables where the module will
+ store the data. For that, if the table were not created by the
+ installation script or you choose to install everything by yourself you
+ can use the siptrace-create.sql SQL script in the database directories
+ in the kamailio/scripts folder as template. You can also find the
+ complete database documentation on the project webpage,
https://www.kamailio.org/docs/db-tables/kamailio-db-devel.html.
7. Known issues
Module: kamailio
Branch: master
Commit: a118641af8fb6bdd288e97c17b12076db6442ef9
URL: https://github.com/kamailio/kamailio/commit/a118641af8fb6bdd288e97c17b12076…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2020-06-05T12:31:22+02:00
modules: readme files regenerated - siptrace ... [skip ci]
---
Modified: src/modules/siptrace/README
---
Diff: https://github.com/kamailio/kamailio/commit/a118641af8fb6bdd288e97c17b12076…
Patch: https://github.com/kamailio/kamailio/commit/a118641af8fb6bdd288e97c17b12076…
---
diff --git a/src/modules/siptrace/README b/src/modules/siptrace/README
index 9006415a23..d9130a312e 100644
--- a/src/modules/siptrace/README
+++ b/src/modules/siptrace/README
@@ -551,8 +551,10 @@ modparam("siptrace", "auth_key", "spoihepuirthpeuia")
Store or forward the current processed SIP message/transaction/dialog
in database. It is stored in the form prior applying changes made to
- it. Based on mode, one can trace the current message('m' - default),
- the current transaction('t') or the current dialog('d').
+ it. Based on mode, one can trace the current message('m'), the current
+ transaction('t') or the current dialog('d'). If no mode is given, it
+ falls back to the default mode - transaction tracking when trace_flag
+ is set, otherwise only the current message.
Meaning of the parameters is as follows:
* address - The address in form of SIP URI where to send a duplicate
@@ -643,13 +645,13 @@ kamcmd siptrace.status check
6. Database setup
- Before running Kamailio with siptrace, you have to setup the database
- tables where the module will store the data. For that, if the table
- were not created by the installation script or you choose to install
- everything by yourself you can use the siptrace-create.sql SQL script
- in the database directories in the kamailio/scripts folder as template.
- You can also find the complete database documentation on the project
- webpage,
+ Before running Kamailio with siptrace and activated trace_to_database
+ parameter, you have to setup the database tables where the module will
+ store the data. For that, if the table were not created by the
+ installation script or you choose to install everything by yourself you
+ can use the siptrace-create.sql SQL script in the database directories
+ in the kamailio/scripts folder as template. You can also find the
+ complete database documentation on the project webpage,
https://www.kamailio.org/docs/db-tables/kamailio-db-devel.html.
7. Known issues
Module: kamailio
Branch: 5.3
Commit: 05a6f13c40249e0d658016652ae46b8512149857
URL: https://github.com/kamailio/kamailio/commit/05a6f13c40249e0d658016652ae46b8…
Author: Henning Westerholt <hw(a)skalatan.de>
Committer: Henning Westerholt <hw(a)skalatan.de>
Date: 2020-06-05T10:29:10Z
siptrace: manual backport of 75e6e370ceb7, improve documentation for siptrace and DB setup
---
Modified: src/modules/siptrace/doc/siptrace_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/05a6f13c40249e0d658016652ae46b8…
Patch: https://github.com/kamailio/kamailio/commit/05a6f13c40249e0d658016652ae46b8…
---
diff --git a/src/modules/siptrace/doc/siptrace_admin.xml b/src/modules/siptrace/doc/siptrace_admin.xml
index 6b3a1f49f8..f5be1c663c 100644
--- a/src/modules/siptrace/doc/siptrace_admin.xml
+++ b/src/modules/siptrace/doc/siptrace_admin.xml
@@ -522,7 +522,9 @@ modparam("siptrace", "auth_key", "spoihepuirthpeuia")
<para>
Store or forward the current processed SIP message/transaction/dialog in database.
It is stored in the form prior applying changes made to it. Based on mode, one can trace
- the current message('m' - default), the current transaction('t') or the current dialog('d').
+ the current message('m'), the current transaction('t') or the current dialog('d').
+ If no mode is given, it falls back to the default mode - transaction tracking when
+ trace_flag is set, otherwise only the current message.
</para>
<para>Meaning of the parameters is as follows:</para>
<itemizedlist>
@@ -674,12 +676,12 @@ hlog("$hdr(P-MyID)", "Another one with a custom correlation ID");
<section>
<title>Database setup</title>
<para>
- Before running &kamailio; with siptrace, you have to setup the database
- tables where the module will store the data. For that, if the
- table were not created by the installation script or you choose
- to install everything by yourself you can use the siptrace-create.sql
- <acronym>SQL</acronym> script in the database directories in the
- kamailio/scripts folder as template.
+ Before running &kamailio; with siptrace and activated trace_to_database
+ parameter, you have to setup the database tables where the module will
+ store the data. For that, if the table were not created by the
+ installation script or you choose to install everything by yourself
+ you can use the siptrace-create.sql <acronym>SQL</acronym> script in
+ the database directories in the kamailio/scripts folder as template.
You can also find the complete database documentation on the
project webpage, &kamailiodbdocslink;.
</para>
Module: kamailio
Branch: master
Commit: 75e6e370ceb701eabbdb2a1b7f12311ba0ae5024
URL: https://github.com/kamailio/kamailio/commit/75e6e370ceb701eabbdb2a1b7f12311…
Author: Henning Westerholt <hw(a)skalatan.de>
Committer: Henning Westerholt <hw(a)skalatan.de>
Date: 2020-06-05T10:25:46Z
siptrace: improve documentation about sip_trace and DB setup
---
Modified: src/modules/siptrace/doc/siptrace_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/75e6e370ceb701eabbdb2a1b7f12311…
Patch: https://github.com/kamailio/kamailio/commit/75e6e370ceb701eabbdb2a1b7f12311…
---
diff --git a/src/modules/siptrace/doc/siptrace_admin.xml b/src/modules/siptrace/doc/siptrace_admin.xml
index 5bd274a2f0..7d5b0d34ef 100644
--- a/src/modules/siptrace/doc/siptrace_admin.xml
+++ b/src/modules/siptrace/doc/siptrace_admin.xml
@@ -643,7 +643,9 @@ modparam("siptrace", "auth_key", "spoihepuirthpeuia")
<para>
Store or forward the current processed SIP message/transaction/dialog in database.
It is stored in the form prior applying changes made to it. Based on mode, one can trace
- the current message('m' - default), the current transaction('t') or the current dialog('d').
+ the current message('m'), the current transaction('t') or the current dialog('d').
+ If no mode is given, it falls back to the default mode - transaction tracking when
+ trace_flag is set, otherwise only the current message.
</para>
<para>Meaning of the parameters is as follows:</para>
<itemizedlist>
@@ -795,12 +797,12 @@ hlog("$hdr(P-MyID)", "Another one with a custom correlation ID");
<section>
<title>Database setup</title>
<para>
- Before running &kamailio; with siptrace, you have to setup the database
- tables where the module will store the data. For that, if the
- table were not created by the installation script or you choose
- to install everything by yourself you can use the siptrace-create.sql
- <acronym>SQL</acronym> script in the database directories in the
- kamailio/scripts folder as template.
+ Before running &kamailio; with siptrace and activated trace_to_database
+ parameter, you have to setup the database tables where the module will
+ store the data. For that, if the table were not created by the
+ installation script or you choose to install everything by yourself
+ you can use the siptrace-create.sql <acronym>SQL</acronym> script in
+ the database directories in the kamailio/scripts folder as template.
You can also find the complete database documentation on the
project webpage, &kamailiodbdocslink;.
</para>
#### Pre-Submission Checklist
- [x] Commit message has the format required by CONTRIBUTING guide
- [x] Commits are split per component (core, individual modules, libs, utils, ...)
- [x] Each component has a single commit (if not, squash them into one commit)
- [x] No commits to README files for modules (changes must be done to docbook files
in `doc/` subfolder, the README file is autogenerated)
#### Type Of Change
- [x] Small bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds new functionality)
- [ ] Breaking change (fix or feature that would change existing functionality)
#### Checklist:
- [ ] PR should be backported to stable branches
- [x] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
If kamailio is behind a NAT only return connection if port matches. We observed this issue on an instance after ~10h of operation.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2307
-- Commit Summary --
* core: do not return connection if port does not match
-- File Changes --
M src/core/tcp_main.c (11)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2307.patchhttps://github.com/kamailio/kamailio/pull/2307.diff
--
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/pull/2307