### Description
I haven't found a way to skip CDR generation per call once [cdr_enable modparam](http://kamailio.org/docs/modules/devel/modules/acc.html#acc.p.cdr… is enabled.
### Expected behavior
I have implemented via irontec/kamailio@38964a31d6c0158b7c9bb3abb4e9eb72aa8cd960 adding a new modparam with the dlg_var name that will prevent CDR generation for calls with that dlg_var set.
#### Actual observed behavior
Once CDR generation is enabled with [cdr_enable modparam](http://kamailio.org/docs/modules/devel/modules/acc.html#acc.p.cdr… all calls generate CDR.
### Additional Information
I can make a PR adapting that patch and documenting new modparam, as long as there is no way of achieving it that I have missed and if you find it useful.
Thank you and regards,
--
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/issues/2348
… or reloading the list
<!-- 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
- [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
When a destination is added/removed or the whole list is reloaded, the calls that are being routed to another destination will fail.
This because ds_load_replace is returning an error not finding in the table the entry for the call being rerouted.
Another side effect of this is that when adding/removing destinations the actual load of the endpoints will be wrong since the current calls will never be deleted.
I've removed the calls to ds_clean_slots and modified ds_load_replace to not exit when the old destination is not found (the endpoint could have been removed after the failover list had been created) and to return a new error code (-2) when the new destination is not found (for the same reason).
Finally I've modified ds_update_dst to skip the current selected destination and select the next if ds_load_replace returns -2.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2342
-- Commit Summary --
* dispatcher: don't reset load table when adding/removing a destination or reloading the list
-- File Changes --
M src/modules/dispatcher/dispatch.c (37)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2342.patchhttps://github.com/kamailio/kamailio/pull/2342.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/2342
Module: kamailio
Branch: 5.2
Commit: 50f60972abbde849c3e637cece7b08777ff3a515
URL: https://github.com/kamailio/kamailio/commit/50f60972abbde849c3e637cece7b087…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2020-06-05T19:46:32+02:00
modules: readme files regenerated - modules ... [skip ci]
---
Modified: src/modules/siptrace/README
---
Diff: https://github.com/kamailio/kamailio/commit/50f60972abbde849c3e637cece7b087…
Patch: https://github.com/kamailio/kamailio/commit/50f60972abbde849c3e637cece7b087…
---
diff --git a/src/modules/siptrace/README b/src/modules/siptrace/README
index 69b4fb247d..d7c1a25a5f 100644
--- a/src/modules/siptrace/README
+++ b/src/modules/siptrace/README
@@ -424,7 +424,8 @@ modparam("siptrace", "trace_delayed", 1)
The local interface in the form of SIP URI from where to send the
duplicated traffic. In the absence of this parameter Kamailio
- automatically picks an interface.
+ automatically picks an interface. This parameter is only used for HEP
+ forwarding, not for SIP forwarding mode.
Example 1.17. Set force_send_sock parameter
...