<!-- 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 -->
- [ ] 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:
<!-- Go over all points below, and after creating the PR, tick the
checkboxes that apply -->
- [ ] PR should be backported to stable branches
- [ ] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
This PR introduces a new Kamailio module named `peerstate`.
The peerstate module provides real-time tracking of SIP peer state by
correlating dialog lifecycle events with registration status. It
maintains a shared-memory cache of peer states and supports multiple
simultaneous dialogs and contacts per peer.
The design and behavior of the module are inspired by existing presence
and PUA-related modules such as `pua_reginfo` and `pua_dialoginfo`.
Some concepts and mechanisms used in those modules (dialog and
registration event handling, some parameters) are reused and adapted for peer
state tracking without requiring
full SIP presence functionality.
Peer state changes are exposed through:
- Kamailio event routes (event_route[dialog:state_changed])
- A callback-based API for other modules
- RPC commands for runtime inspection and monitoring
The module integrates with the `dialog` and `usrloc` modules to receive
dialog and registration events. It supports both URI-derived and
AVP-based peer identification and handles multi-contact registration
scenarios conservatively.
Documentation is provided in DocBook XML format following the standard
Kamailio Admin Guide / Developer Guide structure.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/4537
-- Commit Summary --
* peerstate: Add real-time peer state tracking module
-- File Changes --
A src/modules/peerstate/CMakeLists.txt (3)
A src/modules/peerstate/Makefile (12)
A src/modules/peerstate/README (618)
A src/modules/peerstate/docs/Makefile (4)
A src/modules/peerstate/docs/peerstate.xml (32)
A src/modules/peerstate/docs/peerstate_admin.xml (595)
A src/modules/peerstate/docs/peerstate_devel.xml (165)
A src/modules/peerstate/peerstate.h (35)
A src/modules/peerstate/peerstate_cache.c (550)
A src/modules/peerstate/peerstate_cache.h (76)
A src/modules/peerstate/peerstate_cb.c (150)
A src/modules/peerstate/peerstate_cb.h (94)
A src/modules/peerstate/peerstate_mod.c (1157)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/4537.patch
https://github.com/kamailio/kamailio/pull/4537.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/4537
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/[email protected]>
_______________________________________________
Kamailio - Development Mailing List -- [email protected]
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the
sender!
