<!-- 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] 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 -->
test sdp c line and sip source ip address is matched.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2045
-- Commit Summary --
* nathelper: test sdp c line and sip source ip address is matched
* nathelper : flag 256 is added to nathelper documentation
-- File Changes --
M src/modules/nathelper/doc/nathelper_admin.xml (72)
M src/modules/nathelper/nathelper.c (47)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2045.patchhttps://github.com/kamailio/kamailio/pull/2045.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/2045
### Description
Not shure is this relevant issue.
according to rfc3261:
> When a tag is generated by a UA for insertion into a request or
> response, it MUST be globally unique and cryptographically random
> with at least 32 bits of randomness.
Kamailio has 16 instead and distribution is not good.
I look at tags for 419485 sip flows (different callid) and table below (top keys ordered by count):
tag suffix; count for different flows with this suffix
ed54 6258
d118 5988
56ce 5923
a7a5 5220
de51 2150
82d8 1143
cf52 890
af92 740
7b5f 534
85f7 307
e553 163
7f7e 138
1d55 130
1afe 62
5a69 43
7caa 18
8474 18
9db2 18
11d3 18
f9ff 18
5420 17
dae6 17
908d 17
ede4 17
09ee 17
96be 17
25dc 17
af6d 16
2506 16
3da0 16
f161 16
1c29 16
#### SIP Traffic
To: <sip:039*101@host:5071>;tag=555d2c3eafafcba8ac92b676e91bb6ed.58eb
--
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/issues/1164
Hi Daniel and Kamailio developers,
Could you consider adding record_route_preset to KEMI in 5.3? If you
like I can do the PR. Hope it is not too late.
Regards
Anthony Alba
Hello,
with the perspective that Python2 is going to be removed from the major
Linux distributes starting with the beginning of next year, the work to
upgrade kamcli to run with Python3 has been started.
>From now on, master branch of kamcli is expected to work only with Python3:
* https://github.com/kamailio/kamcli
There is still work to be done to upgrade all the code, but any use of
it should be done with Python3 and eventual issues to be filed on bug
tracker. Of course, pull requests are welcome as always!
Who wants to use the version for Python2 has to use the code from git
branch v1.2-python2. That branch is probably not going to receive any
new feature, it will be kept for use with older systems (as well as a
running option during the upgrade period to Python3).
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda