Hello,
with many countries having public holidays around Catholic Easter, I am
considering to release Kamailio v5.8.1 (out of branch 5.8) on Wednesday,
April 3, 2024. If anyone is aware of issues not yet on the bug tracker,
report them there asap in order to have a better chance to be fixed.
Cheers,
Daniel
--
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- 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
- [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:
<!-- 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 -->
When we use DNS failover in case of timeout kamailio executes the branch_failure route. In the case of the 503 - on_reply route. This commit is to equate behavior in both cases. So if there are more candidates we will always execute branch_failure route and on_reply route only if this is the last candidate.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3138
-- Commit Summary --
* branch_failure route in case 503 and dns failover
-- File Changes --
M src/modules/tm/t_reply.c (52)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3138.patchhttps://github.com/kamailio/kamailio/pull/3138.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3138
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3138(a)github.com>
<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for feature requests.
If you have questions about using Kamailio or related to its configuration file, ask on sr-users mailing list:
* https://lists.kamailio.org/mailman3/postorius/lists/sr-users.lists.kamailio…
If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:
* https://lists.kamailio.org/mailman3/postorius/lists/sr-dev.lists.kamailio.o…
Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot the issue.
If you submit a feature request (or enhancement) add the description of what you would like to be added.
If there is no content to be filled in a section, the entire section can be removed.
Note that a feature request may be closed automatically after about 2 months
if there is no interest from developers or community users to implement it, being
considered expired. In such case can be reopened by writing a comment that includes
the token `/notexpired`. About two weeks before considered expired, the item is
marked with the label `stale`, trying to notify the submitter and everyone else
that might be interested in it. To remove the label `stale`, write a comment that
includes the token `/notstale`. Also, any comment postpone the `expire` timeline,
being considered that there is interest in the proposed feature request.
You can delete the comments from the template sections when filling.
You can delete next line and everything above before submitting (it is a comment).
-->
### Description
Consider adding socket options SO_BINDTODEVICE when the interface name is given for listening in the config file. This will be useful in listening to linux VRF interfaces, especially when there are two different VRFs and it is required to proxy SIP messages between the VRFs
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3716
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3716(a)github.com>
Module: kamailio
Branch: master
Commit: 2063993c1ae54c07b39ea9deb8f735a47785c0ee
URL: https://github.com/kamailio/kamailio/commit/2063993c1ae54c07b39ea9deb8f735a…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2024-03-29T11:13:48+01:00
core: added fixup_spve1_pvar() helper
- comments to spveX pvar fixup helpers
---
Modified: src/core/mod_fix.c
Modified: src/core/mod_fix.h
---
Diff: https://github.com/kamailio/kamailio/commit/2063993c1ae54c07b39ea9deb8f735a…
Patch: https://github.com/kamailio/kamailio/commit/2063993c1ae54c07b39ea9deb8f735a…
---
diff --git a/src/core/mod_fix.c b/src/core/mod_fix.c
index 0947f788461..bba3a469028 100644
--- a/src/core/mod_fix.c
+++ b/src/core/mod_fix.c
@@ -728,7 +728,9 @@ int fixup_free_spve_spve_igp(void **param, int param_no)
}
/**
- *
+ * - first params are dynamic strings (spve)
+ * - n - how many params are spve; n+1 is name of pv
+ * - if pvmode==1, the last param pv has to be r/w
*/
int fixup_spve_n_pvar(void **param, int n, int param_no, int pvmode)
{
@@ -768,6 +770,15 @@ int fixup_spve_pvar(void **param, int param_no)
return fixup_spve_n_pvar(param, 1, param_no, 0);
}
+/**
+ * - first params are dynamic strings
+ * - last param pv has to be r/w
+ */
+int fixup_spve1_pvar(void **param, int param_no)
+{
+ return fixup_spve_n_pvar(param, 1, param_no, 1);
+}
+
/**
*
*/
@@ -777,7 +788,8 @@ int fixup_free_spve_pvar(void **param, int param_no)
}
/**
- *
+ * - first params are dynamic strings
+ * - last param pv has to be r/w
*/
int fixup_spve2_pvar(void **param, int param_no)
{
@@ -793,7 +805,8 @@ int fixup_free_spve2_pvar(void **param, int param_no)
}
/**
- *
+ * - first params are dynamic strings
+ * - last param pv has to be r/w
*/
int fixup_spve3_pvar(void **param, int param_no)
{
@@ -809,7 +822,8 @@ int fixup_free_spve3_pvar(void **param, int param_no)
}
/**
- *
+ * - first params are dynamic strings
+ * - last param pv has to be r/w
*/
int fixup_spve4_pvar(void **param, int param_no)
{
diff --git a/src/core/mod_fix.h b/src/core/mod_fix.h
index a202c4ade2b..d3f954fb1c2 100644
--- a/src/core/mod_fix.h
+++ b/src/core/mod_fix.h
@@ -147,6 +147,7 @@ int fixup_free_igp_all(void **param, int param_no);
int fixup_spve_igp(void **param, int param_no);
int fixup_free_spve_igp(void **param, int param_no);
int fixup_spve_pvar(void **param, int param_no);
+int fixup_spve1_pvar(void **param, int param_no);
int fixup_free_spve_pvar(void **param, int param_no);
int fixup_spve2_pvar(void **param, int param_no);
int fixup_free_spve2_pvar(void **param, int param_no);
While testing I noticed a strange behavior.
Usually when activated, `sipdump.enable 1` for the specific interface will dump needed logs and captures to `/tmp/`.
After stopping the dump with `sipdump.enable 0` deleting all captures starting with `kamailio.*` under `/tmp/` and reactivating the dump with `sipdump.enable 1` without restarting kamailio, the service will not create new captures under `/tmp/`.
This behavior was reproducible.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3798
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3798(a)github.com>