### Description
I've recently spent some time debugging a case with JsSIP and usernames in form of a generated string which can be both upper and lower case letters plus digits.
On BYE from callee to JsSIP, it responded with a "404" and "Request-URI does not point to us" in the console while debugging.
JsSIP is using the Contact returned in the 200 OK to REGISTER (which is transformed to all lower case) for new outgoing INVITE.
It does not match this against the one used in BYE correctly, and …
[View More]return "404".
I see there is a setting in the registrar about this:
```
3.11. case_sensitive (integer)
If set to 1 then AOR comparison and also storing will be case sensitive, if set to 0 then AOR comparison and storing will be case insensitive.
This is recommended. This parameter can be modified via Kamailio config framework.
Default value is 0.
```
Since the RFC states that username should be handle case-sensitive, maybe it would be smart to change this default?
```
Comparison of the userinfo of SIP and SIPS URIs is case-
sensitive. This includes userinfo containing passwords or
formatted as telephone-subscribers.
...
The URIs within each of the following sets are not equivalent:
SIP:ALICE@AtLanTa.CoM;Transport=udp (different usernames)
sip:alice@AtLanTa.CoM;Transport=UDP
```
#### Reproduction
Make a registration with a username containing both upper and lower case characters. It will be stored in all lower case.
### Possible Solutions
Change default value.
Regardless of the outcome on this case - at least now there is a note about it here too.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3719
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3719(a)github.com>
[View Less]
Module: kamailio
Branch: 5.7
Commit: 2f0cca81bfc47783098e4c869b038229cd3e4ed0
URL: https://github.com/kamailio/kamailio/commit/2f0cca81bfc47783098e4c869b03822…
Author: S-P Chan <shihping.chan(a)gmail.com>
Committer: Victor Seva <linuxmaniac(a)torreviejawireless.org>
Date: 2024-02-12T07:52:26+01:00
Sample etc/kamailio.cfg: global var tls_threads_mode
- load tls first if used
- global var tls_threads_mode
---
Modified: etc/kamailio.cfg
---
Diff: https://github.com/kamailio/…
[View More]kamailio/commit/2f0cca81bfc47783098e4c869b03822…
Patch: https://github.com/kamailio/kamailio/commit/2f0cca81bfc47783098e4c869b03822…
---
diff --git a/etc/kamailio.cfg b/etc/kamailio.cfg
old mode 100644
new mode 100755
index fe7b111a012..a95a652b935
--- a/etc/kamailio.cfg
+++ b/etc/kamailio.cfg
@@ -220,6 +220,13 @@ enable_tls=yes
/* upper limit for TLS connections */
tls_max_connections=2048
+
+/* For OpenSSL 3 integration
+ * functions calling libssl3 can be invoked in a transient thread
+ * 0: disable threaded calls
+ * 1: use threads for process#0 only
+ * 2: use threads for all processes */
+tls_threads_mode=1
#!endif
/* set it to yes to enable sctp and load sctp.so module */
@@ -257,6 +264,12 @@ voicemail.srv_port = "5060" desc "VoiceMail Port"
/* set paths to location of modules */
# mpath="/usr/local/lib/kamailio/modules/"
+# when using TLS with OpenSSL it is recommended to load this module
+# first so that OpenSSL is initialized correctly
+#!ifdef WITH_TLS
+loadmodule "tls.so"
+#!endif
+
#!ifdef WITH_MYSQL
loadmodule "db_mysql.so"
#!endif
@@ -319,10 +332,6 @@ loadmodule "rtpproxy.so"
#!endif
#!endif
-#!ifdef WITH_TLS
-loadmodule "tls.so"
-#!endif
-
#!ifdef WITH_HTABLE
loadmodule "htable.so"
#!endif
[View Less]
<!-- 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, …
[View More]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
This PR restores the default behaviour of stable branch and makes libssl thread-guard work opt-in.
- user's config from 5.7.3 will run unchanged
- backport tls_threads_mode = 0|1|2 from dev; user must explicitly opt-in to libssl changes
Scenario 1: user does not change 5.7.3 configuration; then libssl thread-guards will be disabled and Kamailio will run as before
Scenario 2: user must opt-in to libssl thread-guards; `tls_threads_mode` has been backported from dev and user must use `tls_threads_mode = 1` in the configuration. The default value is `tls_threads_mode = 0`
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3754
-- Commit Summary --
* core: added tls_threads_mode global parameter
* core/rthreads.h: use global ksr_tls_threads_mode to constrain thread
* Sample etc/kamailio.cfg: global var tls_threads_mode
* tls: restore default to bypass thread guards
-- File Changes --
M etc/kamailio.cfg (17)
M src/core/cfg.lex (2)
M src/core/cfg.y (9)
M src/core/globals.h (1)
M src/core/rthreads.h (33)
M src/main.c (5)
M src/modules/tls/tls_mod.c (4)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3754.patchhttps://github.com/kamailio/kamailio/pull/3754.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3754
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3754(a)github.com>
[View Less]
<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for bug reports.
If you have questions about using Kamailio or related to its configuration file, ask on sr-users mailing list:
* https://lists.kamailio.org/mailman3/postorius/lists/sr-users.lists.kamailio…
If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:
* https://lists.kamailio.org/mailman3/postorius/…
[View More]lists/sr-dev.lists.kamailio.o…
Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot the issue.
Note that an issue report may be closed automatically after about 2 months
if there is no interest from developers or community users on pursuing it, being
considered expired. In such case, it can be reopened by writing a comment that includes
the token `/notexpired`. About two weeks before considered expired, the issue is
marked with the label `stale`, trying to notify the submitter and everyone else
that might be interested in it. To remove the label `stale`, write a comment that
includes the token `/notstale`. Also, any comment postpone the `expire` timeline,
being considered that there is interest in pursuing the issue.
If there is no content to be filled in a section, the entire section can be removed.
You can delete the comments from the template sections when filling.
You can delete next line and everything above before submitting (it is a comment).
-->
### Description
While doing a call, new dialogue is not created in PCSCF. RX feature is on. As per my understanding, ims_dialog has one call back function and it invokes dlg_onreq() function and a new dialgue can be created (function is dlg_new_dialog). And in the traces, that is not happening.
<!--
Explain what you did, what you expected to happen, and what actually happened.
-->
### Troubleshooting
I have added additional traces for troubleshooting, and I can see that in case of PCSCF, new dialog is not created. And later on Rx feature is not working as expected.
#### Reproduction
Everytime
<!--
If the issue can be reproduced, describe how it can be done.
-->
Need to do Two UEs VoLTE registration and then a call from UE1 to UE2
#### Debugging Data
<!--
If you got a core dump, use gdb to extract troubleshooting data - full backtrace,
local variables and the list of the code at the issue location.
gdb /path/to/kamailio /path/to/corefile
bt full
info locals
list
If you are familiar with gdb, feel free to attach more of what you consider to
be relevant.
-->
```
(paste your debugging data here)
```
#### Log Messages
<!--
Check the syslog file and if there are relevant log messages printed by Kamailio, add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
```
(paste your log messages here)
```
#### SIP Traffic
<!--
If the issue is exposed by processing specific SIP messages, grab them with ngrep or save in a pcap file, then add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
```
(paste your sip traffic here)
```
### Possible Solutions
<!--
If you found a solution or workaround for the issue, describe it. Ideally, provide a pull request with a fix.
-->

### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
(paste your output here)
```
root@openims-node-focal:/usr/local/etc/kamailio# kamailio -v
version: kamailio 5.7.2 (x86_64/linux) 02958e
flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, MEM_JOIN_FREE, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED
ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: 02958e
compiled on 18:07:29 Oct 17 2023 with gcc 9.4.0
* **Operating System**:
ubuntu
uname -a
Linux openims-node-focal 5.4.0-166-generic #183-Ubuntu SMP Mon Oct 2 11:28:33 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
<!--
Details about the operating system, the type: Linux (e.g.,: Debian 8.4, Ubuntu 16.04, CentOS 7.1, ...), MacOS, xBSD, Solaris, ...;
Kernel details (output of `lsb_release -a` and `uname -a`)
-->
```
(paste your output here)
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3676
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3676(a)github.com>
[View Less]