#### 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.patch https://github.com/kamailio/kamailio/pull/3460.diff