Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

siptrace: duplicate via HEP with any protocol #2244

Merged
merged 1 commit into from Mar 12, 2020

Conversation

btriller
Copy link
Contributor

Pre-Submission Checklist

  • 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:

  • PR should be backported to stable branches
  • Tested changes locally
  • Related to issue #XXXX (replace XXXX with an open issue number)

Description

Allow duplicating messages via HEP over any configured protocol.

@btriller btriller force-pushed the siptrace-duplicate-transport branch from 7356e16 to 645cb59 Compare March 11, 2020 06:43
@henningw
Copy link
Contributor

Thanks for the pull request. I already backported the (also included) example table fix to stable branches. About the new HEP functionality, this is probably something to include into the master branch, as it is new functionality.

@henningw henningw merged commit 711eeeb into kamailio:master Mar 12, 2020
@henningw
Copy link
Contributor

Thanks, merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants