Hello,
at couple of events I participated during the past few months, I was
asked about support of STIR/SHAKEN (caller identity
authentication/verification), which is a hot topic these days at least
in USA, aiming to combat "fraudulent" robo-calling. Therefore I thought
of share some details with everyone in the community about the state in
Kamailio, writing to both devs and users, the information being relevant
for everyone.
We already have the (related) module named auth_identity, available
since 2008 (iirc):
- https://www.kamailio.org/docs/modules/stable/modules/auth_identity.html
But it implements the previous iteration of the specs for caller
identity, respectively RFC 4474:
- https://tools.ietf.org/html/rfc4474
However, that RFC is obsoleted by 8224 (the latest core specs for
STIR/SHAKEN):
- https://tools.ietf.org/html/rfc8224
Then, there are also RFCs 8225 and 8226 to add to the core specs.
Should anyone be interested to implement STIR/SHAKEN specs in a modules,
I would suggest to start from auth_identity -- might not be much work to
update it to become conform with latest specs (a new module can be
created, of course, even when starting from auth_identity).
However, these specs are about signing the SIP request (the INVITE) with
special PKI certificate. It can be done easily with embedded scripts
such as Lua or Python (inline execution in native kamailio.cfg or using
kemi scripts). At Kamailio World 2019, one of the participants I
discussed with told me they already implemented using Lua.
That's it for a starting point, if anyone wants to discuss more, just
reply to sr-users and add your comments or ask the questions.
If someone wants to go ahead and work on a C module, announce yourself
to avoid duplicate work of others, and use sr-dev if you need assistance
on module development.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
… reload
<!-- 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 -->
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2038
-- Commit Summary --
* Module:rtpengine: memory leak is fixed, if no rtpengine in list while reload
-- File Changes --
M src/modules/rtpengine/rtpengine_db.c (1)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2038.patchhttps://github.com/kamailio/kamailio/pull/2038.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/2038
Hello,
We facing an issue on capturing sip message in Kamailio(Version: 5.2.3).
The scenario is very simple.
UAC Kamailio UAS
|--------INVITE--------->| |
| |-------INVITE------->|
| |<------100 Trying----|
|<-------100 Trying------| |
| |<------200 Ok--------|
|<-------200 Ok----------| |
In this simple scenario, we can't catch any reply messages in between the
Kamailio and UAC. We have tried reply_route, onreply_route,
and onsend_route. But no one work to grep that reply on that side.
onsend_route was bad try as its only for forwarded reply message. Is there
any other magic to capture those replies. A debug=3 log message attached
here.
Thanks,
Salah