Hello, guys,
I developed a feature, which I called "feature/rehash_of_hash" and
wanted to push to github, for the maintainers to review it and see if
it could be accepted into kamailio.
it is related to the following post, which no one responded :-(
https://lists.kamailio.org/pipermail/sr-users/2020-June/109516.html
I wrote to that list with my work email. It seems, confirmation emails
for subscription to this list are been blocked by my work's email
servers, so I subscribed now with my personal email.
Basically, this is the issue, related to the dispatcher module .
If distribution is based on a hash of a header (Call-ID, From, etc)
and destination is not available, just a "next" is selected. That
causes that all calls are sent to the same destination.
I opened an issue with this :
https://github.com/kamailio/kamailio/issues/2361
I also opened a pull request with the solution.
https://github.com/kamailio/kamailio/pull/2362
I don't understand why it shows so many changes on my two modified
files. I forked, cloned to my notebook and pushed back.
For instance, lines 82 to 97 in src/modules/dispatcher/dispatch.c ,
which I did not modify.
What did I do wrong?
Best regards,
Luis
<!-- 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 -->
- [x] PR should be backported to stable branches
- [x] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
in high volume systems with ephemeral user location data (e.g. very low expiration times on user location records), the user location delete action can cause a high amount of DMQ traffic when UAs unregister. This new parameter allows the user location `delete` action to be disabled from being shared across DMQ nodes which helps reduce DMQ traffic on systems with high register/unregister rates and low expiration times.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2358
-- Commit Summary --
* dmq_usrloc: add new parameter `usrloc_delete` to disable synchronizing delete actions
-- File Changes --
M src/modules/dmq_usrloc/dmq_usrloc.c (2)
M src/modules/dmq_usrloc/doc/dmq_usrloc.xml (16)
M src/modules/dmq_usrloc/doc/dmq_usrloc_admin.xml (20)
M src/modules/dmq_usrloc/usrloc_sync.c (5)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2358.patchhttps://github.com/kamailio/kamailio/pull/2358.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/2358
Kamailio close the TCP connection whenever the client sends a request .i am observing two different behavior.
when I configure "listen=tls:10.66.60.190:5061 advertise 54.214.14.120:5061" in kamailio.cfg
tcp connection closed immediately(RST,ACK) upon receiving of client TCP (SYN) message.
when I configured "listen=tcp:10.66.60.190:5061 advertise 54.214.14.120:5061" in kamailio.cfg
tcp connection closed after "Client Hello" in TLSv1.
####### Global Parameters #########
### LOG Levels: 3=DBG, 2=INFO, 1=NOTICE, 0=WARN, -1=ERR
#!ifdef WITH_DEBUG
debug=4
log_stderror=yes
#!else
debug=4
log_stderror=no
#!endif
memdbg=5
memlog=5
log_facility=LOG_LOCAL0
log_prefix="{$mt $hdr(CSeq) $ci} "
/* number of SIP routing processes for each UDP socket
* - value inherited by tcp_children and sctp_children when not set explicitely */
children=8
/* uncomment the next line to disable TCP (default on) */
# disable_tcp=yes
/* number of SIP routing processes for all TCP/TLS sockets */
tcp_children=8
/* uncomment the next line to disable the auto discovery of local aliases
* based on reverse DNS on IPs (default on) */
# auto_aliases=no
/* add local domain aliases */
#alias="sip.mydomain.com"
/* uncomment and configure the following line if you want Kamailio to
* bind on a specific interface/port/proto (default bind on all available) */
listen=tls:10.60.16.149:5061 advertise 54.204.184.189:5061
listen=udp:10.60.16.149:5070
/* life time of TCP connection when there is no traffic
* - a bit higher than registration expires to cope with UA behind NAT */
tcp_connection_lifetime=3605
/* upper limit for TCP connections (it includes the TLS connections) */
tcp_max_connections=2048
#!ifdef WITH_TLS
enable_tls=yes
/* upper limit for TLS connections */
tls_max_connections=2048
#!endif
#!ifdef WITH_TLS
loadmodule "tls.so"
#!endif
#!ifdef WITH_TLS
# ----- tls params -----
modparam("tls", "config", "/etc/kamailio/tls.cfg")
#!endif
tls.cfg:
[server:default]
method = TLSv1.0
verify_certificate = no
require_certificate = no
private_key = /etc/kamailio/privkey.pem
certificate = /etc/kamailio/kamailio1_cert.pem
#ca_list = /etc/kamailio/calist.pem
#crl = /etc/kamailio/tls/crl.pem
# ---
# This is the default client domain profile.
# Settings in this domain will be used for all outgoing
# TLS connections that do not match any other
# client domain in this configuration file.
# We require that servers present valid certificate.
#
[client:default]
#method = TLSv1.2+
verify_certificate = yes
require_certificate = yes
--
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/2357
#### 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
- [x] 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
- [x] Tested changes locally
#### Description
* avp_check
* avp_copy
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2356
-- Commit Summary --
* avpops: export functions to KEMI
-- File Changes --
M src/modules/avpops/avpops.c (162)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2356.patchhttps://github.com/kamailio/kamailio/pull/2356.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/2356