Hello,
I am considering to release Kamailio v5.3.3 next week, either on Monday
(March 16) or Tuesday (March 17). As usual, if any of you are aware of
issues not reported on the tracker yet or knows fixes not backported to
branch 5.3, reported them as soon as possible to take care of them.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com
<!-- 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 -->
- [ ] Commit message has the format required by CONTRIBUTING guide
- [ ] Commits are split per component (core, individual modules, libs, utils, ...)
- [ ] 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)
- [ ] 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
- [ ] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2251
-- Commit Summary --
* pv_headers: state header, which could not be split
-- File Changes --
M src/modules/pv_headers/pvh_func.c (4)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2251.patchhttps://github.com/kamailio/kamailio/pull/2251.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/2251
Module: kamailio
Branch: 5.3
Commit: 06b81521c9b0c8f9d510e15dfb55e1f61d9b0c0f
URL: https://github.com/kamailio/kamailio/commit/06b81521c9b0c8f9d510e15dfb55e1f…
Author: Bastian Triller <bastian.triller(a)gmail.com>
Committer: Henning Westerholt <hw(a)skalatan.de>
Date: 2020-03-14T21:22:54+01:00
sms: docs fix parameter name
(cherry picked from commit e9d4ab30419460175fe76b82c58b26768ea4ef57)
---
Modified: src/modules/sms/doc/params.xml
---
Diff: https://github.com/kamailio/kamailio/commit/06b81521c9b0c8f9d510e15dfb55e1f…
Patch: https://github.com/kamailio/kamailio/commit/06b81521c9b0c8f9d510e15dfb55e1f…
---
diff --git a/src/modules/sms/doc/params.xml b/src/modules/sms/doc/params.xml
index 242d4513f0..509238a4af 100644
--- a/src/modules/sms/doc/params.xml
+++ b/src/modules/sms/doc/params.xml
@@ -218,8 +218,8 @@ modparam("sms", "max_sms_parts", 10)
</example>
</section>
- <section id="domain_str">
- <title><varname>domain_str</varname> (string)</title>
+ <section id="domain">
+ <title><varname>domain</varname> (string)</title>
<para>
Specify a fake domain name to be used by the gateway. The Contact
headers and the From header from request will be construct based on
@@ -231,10 +231,10 @@ modparam("sms", "max_sms_parts", 10)
Default is the name of the machine the gateway is running on.
</para>
<example>
- <title>Set <varname>domain_str</varname> parameter</title>
+ <title>Set <varname>domain</varname> parameter</title>
<programlisting>
...
-modparam("sms", "domain_str", "foo.bar")
+modparam("sms", "domain", "foo.bar")
...
</programlisting>
</example>