(Feature request)
be able to recover data from htable variable when kamailio starts, from another kamailio instances through dmq module.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/260
<!-- Kamailio Pull Request Template -->
<!--
IMPORTANT:
- for detailed contributing guidelines, read:
https://github.com/kamailio/kamailio/blob/master/.github/CONTRIBUTING.md
- pull requests must be done to master branch, unless they are backports
of fixes from master branch to a stable branch
- backports to stable branches must be done with 'git cherry-pick -x ...'
- code is contributed under BSD for core and main components (tm, sl, auth, tls)
- code is contributed GPLv2 or a compatible license for the other components
- GPL code is contributed with OpenSSL licensing exception
-->
#### Pre-Submission Checklist
<!-- Go over all points below, and after creating the PR, tick all the checkboxes that apply -->
<!-- All points should be verified, otherwise, read the CONTRIBUTING guidelines from above-->
<!-- If you're unsure about any of these, don't hesitate to ask on sr-dev mailing list -->
- [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
- [ ] Small bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds new functionality)
- [ ] Breaking change (fix or feature that would change existing functionality)
#### Checklist:
<!-- Go over all points below, and after creating the PR, tick the checkboxes that apply -->
- [ ] PR should be backported to stable branches
- [x] Tested changes locally
- [x] Related to issue #260
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/1667
-- Commit Summary --
* htable: added startup synchronization over dmq
-- File Changes --
M src/modules/htable/doc/htable_admin.xml (22)
M src/modules/htable/ht_dmq.c (395)
M src/modules/htable/ht_dmq.h (6)
M src/modules/htable/htable.c (4)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/1667.patchhttps://github.com/kamailio/kamailio/pull/1667.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/1667
<!-- Kamailio Pull Request Template -->
<!--
IMPORTANT:
- for detailed contributing guidelines, read:
https://github.com/kamailio/kamailio/blob/master/.github/CONTRIBUTING.md
- pull requests must be done to master branch, unless they are backports
of fixes from master branch to a stable branch
- backports to stable branches must be done with 'git cherry-pick -x ...'
- code is contributed under BSD for core and main components (tm, sl, auth, tls)
- code is contributed GPLv2 or a compatible license for the other components
- GPL code is contributed with OpenSSL licensing exception
-->
#### Pre-Submission Checklist
<!-- Go over all points below, and after creating the PR, tick all the checkboxes that apply -->
<!-- All points should be verified, otherwise, read the CONTRIBUTING guidelines from above-->
<!-- If you're unsure about any of these, don't hesitate to ask on sr-dev mailing list -->
- [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)
- [ ] 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
- [ ] Small bug fix (non-breaking change which fixes an issue)
- [X] New feature (non-breaking change which adds new functionality)
- [ ] Breaking change (fix or feature that would change existing functionality)
#### Checklist:
<!-- Go over all points below, and after creating the PR, tick the checkboxes that apply -->
- [ ] PR should be backported to stable branches
- [X] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
maybe this already exists but i didn't find.
not required to backport but could be useful in 5.1
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/1666
-- Commit Summary --
* siputils: add is_uri function
-- File Changes --
M src/modules/siputils/checks.c (31)
M src/modules/siputils/checks.h (4)
M src/modules/siputils/doc/siputils_admin.xml (27)
M src/modules/siputils/siputils.c (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/1666.patchhttps://github.com/kamailio/kamailio/pull/1666.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/1666
Module: kamailio
Branch: master
Commit: 61405d0f0139622f78d81daa634caff86f5b3970
URL: https://github.com/kamailio/kamailio/commit/61405d0f0139622f78d81daa634caff…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2018-10-04T16:52:00+02:00
corex: docs for via_use_xavp_fields()
---
Modified: src/modules/corex/doc/corex_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/61405d0f0139622f78d81daa634caff…
Patch: https://github.com/kamailio/kamailio/commit/61405d0f0139622f78d81daa634caff…
---
diff --git a/src/modules/corex/doc/corex_admin.xml b/src/modules/corex/doc/corex_admin.xml
index 346ecf2019..6460d11913 100644
--- a/src/modules/corex/doc/corex_admin.xml
+++ b/src/modules/corex/doc/corex_admin.xml
@@ -664,6 +664,34 @@ via_add_srv("1");
...
via_add_xavp_params("1");
...
+</programlisting>
+ </example>
+ </section>
+ <section id="corex.f.via_use_xavp_fields">
+ <title><function moreinfo="none">via_use_xavp_fields(flags)</function></title>
+ <para>
+ Control if fields of the xavp with the name specified by
+ xavp_via_fields global parameter are used or not to build local Via.
+
+ </para>
+ <para>Meaning of the parameters is as follows:</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis>flags</emphasis>: 1 - use xavp fields; 0 - do not
+ use xavp fields.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ This function can be used from ANY_ROUTE.
+ </para>
+ <example>
+ <title><function>via_use_xavp_fields</function> usage</title>
+ <programlisting format="linespecific">
+...
+via_use_xavp_fields("1");
+...
</programlisting>
</example>
</section>