[sr-dev] [kamailio/kamailio] Adding CDR as JSON functionality (#2107)

Lucian Balaceanu notifications at github.com
Mon Oct 21 18:15:39 CEST 2019


<!-- 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 -->
These commits create a CDR addressed engine, similar to the one that acc module exports for acc message accounting. Such an engine made an extension module like acc_json possible. This CDR engine is then used in acc_json to write the functionality for logging CDRs in JSON format.

I have added functions to the API exported by acc module instead of creating another separate CDR API, as I thought this is cleaner.
I only implemented the acc_json logging to syslog (no message queue support yet).

You can view, comment on, or merge this pull request online at:

  https://github.com/kamailio/kamailio/pull/2107

-- Commit Summary --

  * acc: adding CDR engine functionality
  * acc_json: adding CDR as JSON functionality

-- File Changes --

    M src/modules/acc/acc_api.h (38)
    M src/modules/acc/acc_cdr.c (41)
    M src/modules/acc/acc_cdr.h (6)
    M src/modules/acc/acc_logic.c (10)
    M src/modules/acc/acc_logic.h (2)
    M src/modules/acc/acc_mod.c (93)
    M src/modules/acc_json/acc_json_mod.c (131)
    M src/modules/acc_json/acc_json_mod.h (4)
    M src/modules/acc_json/doc/acc_json_admin.xml (54)

-- Patch Links --

https://github.com/kamailio/kamailio/pull/2107.patch
https://github.com/kamailio/kamailio/pull/2107.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/2107
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-dev/attachments/20191021/6d2a29f8/attachment-0001.html>


More information about the sr-dev mailing list