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

While testing this module, I've seen it doesn't trace in-dialog ACKs.
Found this old maillist discussion: https://lists.kamailio.org/pipermail/sr-users/2015-June/088731.html
Added a condition to trace also the in-dialog ACKs. Is it ok to keep it as default or should I guard it via a modparam?

Thanks,
Stefan

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

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

Commit Summary

8f3726c siptrace: Trace in-dialog ACK

File Changes

(1 file)

M src/modules/siptrace/siptrace.c (7)

Patch Links:

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.