Module: kamailio
Branch: master
Commit: 1f1297b407be0525e314b9d734d39a1a20ed886d
URL: https://github.com/kamailio/kamailio/commit/1f1297b407be0525e314b9d734d39a1…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2022-08-08T16:01:20+02:00
modules: readme files regenerated - uac ... [skip ci]
---
Modified: src/modules/uac/README
---
Diff: https://github.com/kamailio/kamailio/commit/1f1297b407be0525e314b9d734d39a1…
Patch: https://github.com/kamailio/kamailio/commit/1f1297b407be0525e314b9d734d39a1…
---
diff --git a/src/modules/uac/README b/src/modules/uac/README
index f1a6e6f5e83..172fa4886de 100644
--- a/src/modules/uac/README
+++ b/src/modules/uac/README
@@ -1246,8 +1246,8 @@ event_route[uac:reply] {
* socket
* contact_addr
- Use a dot (.) if no value should be set for auth_password, auth_ha1, or
- contact_addr.
+ Use a dot (.) if no value should be set for realm, auth_password,
+ auth_ha1, socket or contact_addr.
Example 1.50. uac.reg_add usage
...
<!-- 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
<!-- Describe your changes in detail -->
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 --
* siptrace: Trace in-dialog ACK
-- File Changes --
M src/modules/siptrace/siptrace.c (7)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3206.patchhttps://github.com/kamailio/kamailio/pull/3206.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3206
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3206(a)github.com>