Module: kamailio
Branch: master
Commit: 66e3c96f49e25ef7d2441f95b20d34a138572231
URL: https://github.com/kamailio/kamailio/commit/66e3c96f49e25ef7d2441f95b20d34a…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2018-04-06T09:31:52+02:00
modules: readme files regenerated - dialog ... [skip ci]
---
Modified: src/modules/dialog/README
---
Diff: https://github.com/kamailio/kamailio/commit/66e3c96f49e25ef7d2441f95b20d34a…
Patch: https://github.com/kamailio/kamailio/commit/66e3c96f49e25ef7d2441f95b20d34a…
---
diff --git a/src/modules/dialog/README b/src/modules/dialog/README
index fbad4ab89f..962046c23d 100644
--- a/src/modules/dialog/README
+++ b/src/modules/dialog/README
@@ -130,6 +130,7 @@ Olle E. Johansson
7.17. dlg_remote_profile(cmd, profile, value, uid, expires)
7.18. dlg_set_ruri()
7.19. dlg_db_load_callid(cival)
+ 7.20. dlg_db_load_extra()
8. Statistics
@@ -257,6 +258,7 @@ Olle E. Johansson
1.77. dlg_remote_profile usage
1.78. dlg_set_ruri() usage
1.79. dlg_db_load_callid() usage
+ 1.80. dlg_db_load_extra() usage
Chapter 1. Admin Guide
@@ -355,6 +357,7 @@ Chapter 1. Admin Guide
7.17. dlg_remote_profile(cmd, profile, value, uid, expires)
7.18. dlg_set_ruri()
7.19. dlg_db_load_callid(cival)
+ 7.20. dlg_db_load_extra()
8. Statistics
@@ -1354,11 +1357,11 @@ modparam("dialog", "h_id_start", 5)
the rule: h_id_start + N * h_id_step. The first value of N is randomly
selected at startup, then incremented by 1 for each new dialog. Setting
h_id_start and h_id_step to non-default values should be done when
- using dlg_db_load_callid(...) to load dialog records generated by
- another Kamailio instance, making also sure that those Kamailio
- instances are not going to generate overalapping dialog hash id values
- by using different h_id_start and the same h_id_step (h_id_step has to
- be greater than the maximum value of h_id_start).
+ using dlg_db_load_callid(...) or dlg_db_load_extra() to load dialog
+ records generated by another Kamailio instance, making also sure that
+ those Kamailio nstances are not going to generate overalapping dialog
+ hash id values by using different h_id_start and the same h_id_step
+ (h_id_step has to be greater than the maximum value of h_id_start).
Default value is “1”.
@@ -1388,6 +1391,7 @@ modparam("dialog", "h_id_step", 10)
7.17. dlg_remote_profile(cmd, profile, value, uid, expires)
7.18. dlg_set_ruri()
7.19. dlg_db_load_callid(cival)
+ 7.20. dlg_db_load_extra()
7.1. set_dlg_profile(profile,[value])
@@ -1792,6 +1796,25 @@ if(has_totag()) {
}
...
+7.20. dlg_db_load_extra()
+
+ Load all dialog records from database that are not in memory of the
+ current Kamailio instance.
+
+ This function can be used from ANY_ROUTE.
+
+ Example 1.80. dlg_db_load_extra() usage
+...
+if(has_totag()) {
+ if(!is_known_dlg()) {
+ dlg_db_load_extra();
+ if(!is_known_dlg()) {
+ xlog("no dialog found with callid: $ci\n");
+ }
+ }
+}
+...
+
8. Statistics
8.1. active_dialogs
Module: kamailio
Branch: master
Commit: 7ff8f04079fc9c7e6710b43c3e893518f17ef48e
URL: https://github.com/kamailio/kamailio/commit/7ff8f04079fc9c7e6710b43c3e89351…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2018-04-06T09:21:56+02:00
dialog: documented dlg_db_load_extra() function
- related to #1274
---
Modified: src/modules/dialog/doc/dialog_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/7ff8f04079fc9c7e6710b43c3e89351…
Patch: https://github.com/kamailio/kamailio/commit/7ff8f04079fc9c7e6710b43c3e89351…
---
diff --git a/src/modules/dialog/doc/dialog_admin.xml b/src/modules/dialog/doc/dialog_admin.xml
index d231d9a2f6..5ed51d450d 100644
--- a/src/modules/dialog/doc/dialog_admin.xml
+++ b/src/modules/dialog/doc/dialog_admin.xml
@@ -1552,12 +1552,12 @@ modparam("dialog", "h_id_start", 5)
with the rule: h_id_start + N * h_id_step. The first value of N is
randomly selected at startup, then incremented by 1 for each new
dialog. Setting h_id_start and h_id_step to non-default values
- should be done when using dlg_db_load_callid(...) to load dialog
- records generated by another &kamailio; instance, making also sure
- that those &kamailio; instances are not going to generate
- overalapping dialog hash id values by using different h_id_start
- and the same h_id_step (h_id_step has to be greater than the
- maximum value of h_id_start).
+ should be done when using dlg_db_load_callid(...) or
+ dlg_db_load_extra() to load dialog records generated by another
+ &kamailio; instance, making also sure that those &kamailio;
+ nstances are not going to generate overalapping dialog hash id
+ values by using different h_id_start and the same h_id_step
+ (h_id_step has to be greater than the maximum value of h_id_start).
</para>
<para>
<emphasis>
@@ -2281,6 +2281,33 @@ if(has_totag()) {
}
}
...
+</programlisting>
+ </example>
+ </section>
+ <section id="dialog.f.dlg_db_load_extra">
+ <title>
+ <function moreinfo="none">dlg_db_load_extra()</function>
+ </title>
+ <para>
+ Load all dialog records from database that are not in memory of the
+ current &kamailio; instance.
+ </para>
+ <para>
+ This function can be used from ANY_ROUTE.
+ </para>
+ <example>
+ <title><function>dlg_db_load_extra()</function> usage</title>
+ <programlisting format="linespecific">
+...
+if(has_totag()) {
+ if(!is_known_dlg()) {
+ dlg_db_load_extra();
+ if(!is_known_dlg()) {
+ xlog("no dialog found with callid: $ci\n");
+ }
+ }
+}
+...
</programlisting>
</example>
</section>
Module: kamailio
Branch: master
Commit: d6cd5655df83d233562ab557a0e73cb5e65f0b1c
URL: https://github.com/kamailio/kamailio/commit/d6cd5655df83d233562ab557a0e73cb…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2018-04-05T20:03:44+02:00
textops: documentation for append_body_part_hex()
---
Modified: src/modules/textops/doc/textops_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/d6cd5655df83d233562ab557a0e73cb…
Patch: https://github.com/kamailio/kamailio/commit/d6cd5655df83d233562ab557a0e73cb…
---
diff --git a/src/modules/textops/doc/textops_admin.xml b/src/modules/textops/doc/textops_admin.xml
index 3ff09fb812..966169d2dd 100644
--- a/src/modules/textops/doc/textops_admin.xml
+++ b/src/modules/textops/doc/textops_admin.xml
@@ -1561,6 +1561,63 @@ Content-Disposition: signal;handling=required
7e Od 04 55 75 69 20 4d 61 6b 65 43 61 6c 6c
+--unique-boundary-1
+...
+</programlisting>
+ </example>
+ </section>
+
+ <section id="textops.f.append_body_part_hex">
+ <title>
+ <function moreinfo="none">append_body_part_hex(txt,content_type[, content_disposition])</function>
+ </title>
+ <para>
+ Append a part on multipart body SIP message, with the content provided
+ in hexa format. Will use "unique-boundary-1" as boundary.
+ </para>
+ <para>Meaning of the parameters is as follows:</para>
+ <itemizedlist>
+ <listitem>
+ <para><emphasis>txt</emphasis> - content for the multipart body in
+ hexa format. Spaces can be used between the pairs of hexa digits
+ to make it easier to read in the config, they are ignored and
+ not added in the body part. The parameter can include
+ pseudo-variables.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>content_type</emphasis> - value of Content-Type header,
+ can include pseudo-variables.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>content_disposition</emphasis> - value of Content-Disposition header,
+ can include pseudo-variables.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ This function can be used from REQUEST_ROUTE, FAILURE_ROUTE, BRANCH_ROUTE.
+ </para>
+ <para>
+ The core will take care of the last boundary ending "--". Detecting wich one is
+ the last and fixing the others if needed.
+ </para>
+ <example>
+ <title><function>append_body_part_hex</function> usage</title>
+ <programlisting format="linespecific">
+...
+$var(b) = "6b 61 6d 61 69 6c 69 6f";
+append_body_part_hex("$var(b)", "application/my-custom-ext");
+...
+
+# Will append this to the body:
+
+...
+Content-Type: application/my-custom-ext
+
+kamailio
+
--unique-boundary-1
...
</programlisting>
Module: kamailio
Branch: master
Commit: 8549789a595fa62dabe877781e6f8d89dbbff0b3
URL: https://github.com/kamailio/kamailio/commit/8549789a595fa62dabe877781e6f8d8…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2018-04-05T14:31:36+02:00
modules: readme files regenerated - rtpengine ... [skip ci]
---
Modified: src/modules/rtpengine/README
---
Diff: https://github.com/kamailio/kamailio/commit/8549789a595fa62dabe877781e6f8d8…
Patch: https://github.com/kamailio/kamailio/commit/8549789a595fa62dabe877781e6f8d8…
---
diff --git a/src/modules/rtpengine/README b/src/modules/rtpengine/README
index 297ff4d517..d6588fdffa 100644
--- a/src/modules/rtpengine/README
+++ b/src/modules/rtpengine/README
@@ -2008,6 +2008,10 @@ rtpengine_offer();
+ record-call=on - instructs RTPEngine to record the session.
Use it in rtpengine_offer() to start recording immediately and
save the call metadata, as alternative to start_recording().
+ + metadata - a generic metadata string. The metadata will be
+ used when recording calls to provide custom additional
+ information. More details about this are found in the
+ rtpengine README.
Check also the documentation of RTPEngine, these flags are
documented there as well: https://github.com/sipwise/rtpengine.
Module: kamailio
Branch: master
Commit: 1e712ed93aef8ab96ee7a9760f89ebc0fd02caff
URL: https://github.com/kamailio/kamailio/commit/1e712ed93aef8ab96ee7a9760f89ebc…
Author: Claudiu Boriga <paul.boriga(a)1and1.ro>
Committer: Claudiu Boriga <paul.boriga(a)1and1.ro>
Date: 2018-04-05T15:30:15+03:00
rtpengine: Add description for metadata flag
---
Modified: src/modules/rtpengine/doc/rtpengine_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/1e712ed93aef8ab96ee7a9760f89ebc…
Patch: https://github.com/kamailio/kamailio/commit/1e712ed93aef8ab96ee7a9760f89ebc…
---
diff --git a/src/modules/rtpengine/doc/rtpengine_admin.xml b/src/modules/rtpengine/doc/rtpengine_admin.xml
index 8ab9349b35..ae875cfc4a 100644
--- a/src/modules/rtpengine/doc/rtpengine_admin.xml
+++ b/src/modules/rtpengine/doc/rtpengine_admin.xml
@@ -2326,6 +2326,11 @@ rtpengine_offer();
it in rtpengine_offer() to start recording immediately and save the call metadata,
as alternative to start_recording().
</para></listitem>
+ <listitem><para>
+ <emphasis>metadata</emphasis> - a generic metadata string. The metadata will be used when
+ recording calls to provide custom additional information. More details about this are found
+ in the rtpengine README.
+ </para></listitem>
</itemizedlist>
<para>
Check also the documentation of RTPEngine, these flags are documented there as well: