<!-- 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] Code is formatted with `clang-format` using the config file
`.clang-format`
from source code folder
- [ ] 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
<!-- Describe your changes in detail -->
We (Kontron Transportation) are issuing this pull request
with a new experimental module, which is called ims_rdn,
hopeful that this module might be useful for at least
some users of Kamailio IMS (I-CSCF and S-CSCF).
This module is most useful for terminating unregistered services
that are triggered by the I/S-CSCF and that are identified
by hierarchical address ranges of E.164 addresses and of
EIRENE addresses (in the Request-URI), not unlike wildcarded PSIs.
By configuring these address ranges at the I/S-CSCF,
one can save one SAR/SAA exchange with the HSS per call.
EIRENE addresses are railway specific telephone numbers,
which have been defined by the UIC.
This explains the name of the module RDN = Railway Dedicated Networks.
Additionally, this module defines kamailio transformations,
which are tailored for the use in RDNs,
e.g. for the transformation of functional numbers and
of MCData SDS into instant messages and vice versa.
This module is even more useful, when implementing
an IWF according to ETSI TS 103 792,
in which case some specific routing scripts will be needed.
We will be glad to help with those.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/4786
-- Commit Summary --
* ims_rdn: new experimental module for IMS RDNs
-- File Changes --
A src/modules/ims_rdn/Makefile (40)
A src/modules/ims_rdn/README (600)
A src/modules/ims_rdn/doc/Makefile (8)
A src/modules/ims_rdn/doc/ims_rdn.xml (86)
A src/modules/ims_rdn/doc/ims_rdn_admin.xml (709)
A src/modules/ims_rdn/ims_rdn.c (2327)
A src/modules/ims_rdn/ims_rdn.h (191)
A src/modules/ims_rdn/rdn_trans.c (847)
A src/modules/ims_rdn/rdn_trans.h (93)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/4786.patch
https://github.com/kamailio/kamailio/pull/4786.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/4786
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!
