#### 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
- [ ] Small bug fix (non-breaking change which fixes an issue)
- [x] 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
Needed a way to sync the publ_cache with changes made to the presentity table when using publ_cache modes 1 or 2. This seems pretty simple, and works for me.
Beneficial when adding numerous "message-summary" event entries from an external Voicemail application to the 'presentity' table.
Usage: `presence.htable_db_restore`
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3460
-- Commit Summary --
* presence: Add publ_cache sync RPC command.
-- File Changes --
M src/modules/presence/doc/presence_admin.xml (21)
M src/modules/presence/presence.c (14)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3460.patchhttps://github.com/kamailio/kamailio/pull/3460.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3460
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3460(a)github.com>
Hi,
I'm thinking we should start enforcing clang-format in order to have a coherent indentation and coding style in the project.
I've added a check in the pull-request Github Action to check the clang-format in the commits but for sure now it will almost always fail due to our code is not always formatted properly.
Is is OK if I start committing changes module by module of just changes related to clang-format formatting?
I'm aware this will our life harder to backport fixes to supported branches but I think it will help us in the long run.
Cheers
--
-----------------------------------------------------------------
| ,''`. Victor Seva |
| : :' : linuxmaniac(a)torreviejawireless.org |
| `. `' PGP Key ID: 0x51A09B18CF5A5068 |
| `- Debian Developer |
-----------------------------------------------------------------
Module: kamailio
Branch: master
Commit: 1f53b159c311715b993ee33d40fb35017626e89c
URL: https://github.com/kamailio/kamailio/commit/1f53b159c311715b993ee33d40fb350…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2023-05-18T13:01:45+02:00
modules: readme files regenerated - dispatcher ... [skip ci]
---
Modified: src/modules/dispatcher/README
---
Diff: https://github.com/kamailio/kamailio/commit/1f53b159c311715b993ee33d40fb350…
Patch: https://github.com/kamailio/kamailio/commit/1f53b159c311715b993ee33d40fb350…
---
diff --git a/src/modules/dispatcher/README b/src/modules/dispatcher/README
index 166dcfc886..dc21ebd604 100644
--- a/src/modules/dispatcher/README
+++ b/src/modules/dispatcher/README
@@ -572,7 +572,8 @@ modparam("dispatcher", "xavp_dst", "_dsdst_")
* attrs - the attributes - they are added if xavp_dst_mode does not
have the bit 1 set (value 1).
- Default value is ���0��� (add all fields).
+ Default value is ���0��� (add grp, uri, sock, attr and optionally dstid
+ fields).
Example 1.13. Set the ���xavp_dst_mode��� parameter
...