New module: add wolfSSL as alternate TLS stack.
<!-- 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
This a new module: an alternate TLS implementation based on wolfSSL. The current tls module based on OpenSSL has many multi-process workarounds and can be quite fragile.
This is the initial code dump which is a copy of `tls/` and edited to compile with wolfSSL by using the OpenSSL compatibility layer. The `doc/` directory has not been changed.
The proposal is to get it into the code base as soon as possible so as to sync up with any ongoing changes in the `tls/` module. Any shared features can be extracted out into a common module: like certificate and configuration.
In the short-term the steps are:
* testing
* use native wolfSSL APIs (remove OpenSSL compatibility layer)
* remove OpenSSL multi-process hacks in this module
This module is inspired by the `tls_wolfssl` module in the sister SIP project.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3144
-- Commit Summary --
* tls_wolfssl: new module TLS stack based on wolfSSL
-- File Changes --
A src/modules/tls_wolfssl/Makefile (81)
A src/modules/tls_wolfssl/README (1713)
A src/modules/tls_wolfssl/TODO.md (7)
A src/modules/tls_wolfssl/doc/Makefile (4)
A src/modules/tls_wolfssl/doc/certs_howto.xml (154)
A src/modules/tls_wolfssl/doc/functions.xml (63)
A src/modules/tls_wolfssl/doc/history.xml (38)
A src/modules/tls_wolfssl/doc/hsm_howto.xml (64)
A src/modules/tls_wolfssl/doc/params.xml (1410)
A src/modules/tls_wolfssl/doc/rpc.xml (69)
A src/modules/tls_wolfssl/doc/tls.xml (367)
A src/modules/tls_wolfssl/fixed_c_zlib.h (258)
A src/modules/tls_wolfssl/sbufq.h (283)
A src/modules/tls_wolfssl/tls.cfg (106)
A src/modules/tls_wolfssl/tls_bio.c (314)
A src/modules/tls_wolfssl/tls_bio.h (69)
A src/modules/tls_wolfssl/tls_cert.sh (201)
A src/modules/tls_wolfssl/tls_cfg.c (289)
A src/modules/tls_wolfssl/tls_cfg.h (111)
A src/modules/tls_wolfssl/tls_config.c (536)
A src/modules/tls_wolfssl/tls_config.h (53)
A src/modules/tls_wolfssl/tls_ct_q.h (133)
A src/modules/tls_wolfssl/tls_ct_wrq.c (205)
A src/modules/tls_wolfssl/tls_ct_wrq.h (98)
A src/modules/tls_wolfssl/tls_domain.c (1585)
A src/modules/tls_wolfssl/tls_domain.h (238)
A src/modules/tls_wolfssl/tls_dump_vf.c (150)
A src/modules/tls_wolfssl/tls_dump_vf.h (41)
A src/modules/tls_wolfssl/tls_init.c (589)
A src/modules/tls_wolfssl/tls_init.h (85)
A src/modules/tls_wolfssl/tls_locking.c (59)
A src/modules/tls_wolfssl/tls_locking.h (34)
A src/modules/tls_wolfssl/tls_map.c (195)
A src/modules/tls_wolfssl/tls_map.h (77)
A src/modules/tls_wolfssl/tls_mod.c (733)
A src/modules/tls_wolfssl/tls_mod.h (45)
A src/modules/tls_wolfssl/tls_rand.c (375)
A src/modules/tls_wolfssl/tls_rand.h (32)
A src/modules/tls_wolfssl/tls_rpc.c (263)
A src/modules/tls_wolfssl/tls_rpc.h (33)
A src/modules/tls_wolfssl/tls_select.c (1707)
A src/modules/tls_wolfssl/tls_select.h (52)
A src/modules/tls_wolfssl/tls_server.c (1557)
A src/modules/tls_wolfssl/tls_server.h (101)
A src/modules/tls_wolfssl/tls_util.c (99)
A src/modules/tls_wolfssl/tls_util.h (87)
A src/modules/tls_wolfssl/tls_verify.c (135)
A src/modules/tls_wolfssl/tls_verify.h (42)
A src/modules/tls_wolfssl/todo.txt (4)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3144.patchhttps://github.com/kamailio/kamailio/pull/3144.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3144
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3144(a)github.com>
#### 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
#### Description
Changes from Sipwise flavor:
- refresh_pubruri_avps_flag: if enabled, this message flag indicates whether to refresh R-Uri from avps before sending the PUBLISH requests.
- improvement for use_pubruri_avps: use locking to avoid crashes since we are using shared memory
- local_identity_dlg_var: reporting dialog-information will use the value of the dialog variable if exists
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3143
-- Commit Summary --
* pua_dialoginfo: refresh_pubruri_avps_flag
* pua_dialoginfo: use lock when use_puburi_avps is set
* pua_dialoginfo: local_identity_dlg_var
-- File Changes --
M src/modules/pua_dialoginfo/doc/pua_dialoginfo_admin.xml (39)
M src/modules/pua_dialoginfo/pua_dialoginfo.c (113)
M src/modules/pua_dialoginfo/pua_dialoginfo.h (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3143.patchhttps://github.com/kamailio/kamailio/pull/3143.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3143
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3143(a)github.com>
Module: kamailio
Branch: 5.6
Commit: b7778364742726357071dbad7c0549cca2d40c91
URL: https://github.com/kamailio/kamailio/commit/b7778364742726357071dbad7c0549c…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2022-06-16T09:29:38+02:00
auth_identity: docs - type for accept_pem_certs param
(cherry picked from commit 6e7b6cfabba6774627f942d7f02e1adf62bf7797)
---
Modified: src/modules/auth_identity/doc/auth_identity_params.xml
---
Diff: https://github.com/kamailio/kamailio/commit/b7778364742726357071dbad7c0549c…
Patch: https://github.com/kamailio/kamailio/commit/b7778364742726357071dbad7c0549c…
---
diff --git a/src/modules/auth_identity/doc/auth_identity_params.xml b/src/modules/auth_identity/doc/auth_identity_params.xml
index a252bbed6b6..aefb49cdd00 100644
--- a/src/modules/auth_identity/doc/auth_identity_params.xml
+++ b/src/modules/auth_identity/doc/auth_identity_params.xml
@@ -190,11 +190,11 @@ modparam("auth_identity","cainfo_path","/etc/ssl/certs/ca-certificates.crt")
</section>
<section id="accept_pem_certs">
- <title><varname>accept_pem_certs</varname> ([0|1])</title>
+ <title><varname>accept_pem_certs</varname> (int)</title>
<para>Note: this parameter is for verifier service.</para>
<para>
Enables the acquired certificate processing if it is in PEM
- format.
+ format. Value can be 0 or 1.
</para>
<para>
This parameter is optional. The default value is "0".
<!--
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:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot 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
Using kamailio 5.5.4 from the official Docker image (created like `create_dockerfile.sh bullseye 5.5.4`, but with no ENTRYPOINT).
Doing TLS listening like:
```
socket_workers=2
tls_max_connections=20000
listen=tls:192.168.0.11:5061
enable_tls=yes
dns_tls_pref=50
tls_port_no=5061
loadmodule "tls.so"
```
It is the second loaded module after tcpops.
Have to connect to the database through cnf files for the SSL support:
`modparam("sqlops","sqlcon","euler=>mysql://[euler]/euclid")`
Relevant section in the cnf file:
```
[euler]
port = 3306
host = 127.0.0.1
protocol = tcp
user = gauss
password = fermat
default-character-set = utf8
ssl-ca = /SSL/riemann/ca-cert.pem
ssl-cert = /SSL/riemann/client-cert.pem
ssl-key = /SSL/riemann/client-key.pem
#ssl-verify-server-cert
```
When starting kamailio:
```
8(18) ERROR: db_mysql [km_my_con.c:163]: db_mysql_new_connection(): driver error: SSL connection error: PEM lib
8(18) ERROR: <core> [db.c:319]: db_do_init2(): could not add connection to the pool
8(18) ERROR: sqlops [sql_api.c:165]: sql_connect(): failed to connect to the database [euclid]
8(18) ERROR: <core> [core/sr_module.c:874]: init_mod_child(): error while initializing module sqlops (/home/euler/lib64/euler/modules/sqlops.so) (idx: 8 rank: -2 desc: [Async Task Worker - default])
8(18) ERROR: <core> [core/pt.c:338]: fork_process(): init_child failed for process 8, pid 18, "Async Task Worker - default"
8(18) ERROR: <core> [main.c:1850]: main_loop(): error in init_child
12(22) CRITICAL: <core> [core/mem/q_malloc.c:501]: qm_free(): BUG: bad pointer 0x7fafa23e6270 (out of memory block!) called from tls: tls_init.c: ser_free(323) - ignoring
```
Then kamailio just hangs on in an incomplete state:
```
/ # ps auxww --forest
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 29 0.6 0.0 4092 3244 pts/1 Ss 08:59 0:00 bash
root 36 0.0 0.0 6692 2964 pts/1 R+ 08:59 0:00 \_ ps auxww --forest
root 1 0.0 0.0 4092 3252 pts/0 Ss 08:58 0:00 bash
root 8 0.4 0.0 110868 23764 pts/0 S+ 08:58 0:00 kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 9 0.0 0.0 0 0 ? Zs 08:58 0:00 \_ [kamailio] <defunct>
root 10 0.5 0.0 111080 31148 ? S 08:58 0:00 kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 11 0.0 0.0 111080 13412 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 12 99.9 0.0 111080 13240 ? R 08:58 0:43 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 13 0.0 0.0 111080 14252 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 14 0.0 0.0 111080 13432 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 15 0.0 0.0 111080 13296 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 16 0.0 0.0 111080 13348 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 17 0.0 0.0 111080 13220 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 18 0.0 0.0 111072 14196 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 19 99.7 0.0 111080 10748 ? R 08:58 0:43 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 20 0.2 0.0 0 0 ? Z 08:58 0:00 \_ [kamailio] <defunct>
root 21 0.0 0.0 111080 13068 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 22 0.0 0.0 111080 13156 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 23 0.0 0.0 111080 10684 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 24 0.0 0.0 111080 10684 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 25 0.0 0.0 111080 10748 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 26 0.0 0.0 111080 10748 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 27 0.0 0.0 111080 13344 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 28 0.0 0.0 111080 10748 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
```
<!--
Explain what you did, what you expected to happen, and what actually happened.
-->
### Troubleshooting
#### Reproduction
<!--
If the issue can be reproduced, describe how it can be done.
-->
It is always happening, but not when either `listen=tls` or the SSL options in the cnf file are dropped.
#### 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.
-->
```
/ # ps auxww --forest
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 29 0.6 0.0 4092 3244 pts/1 Ss 08:59 0:00 bash
root 36 0.0 0.0 6692 2964 pts/1 R+ 08:59 0:00 \_ ps auxww --forest
root 1 0.0 0.0 4092 3252 pts/0 Ss 08:58 0:00 bash
root 8 0.4 0.0 110868 23764 pts/0 S+ 08:58 0:00 kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 9 0.0 0.0 0 0 ? Zs 08:58 0:00 \_ [kamailio] <defunct>
root 10 0.5 0.0 111080 31148 ? S 08:58 0:00 kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 11 0.0 0.0 111080 13412 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 12 99.9 0.0 111080 13240 ? R 08:58 0:43 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 13 0.0 0.0 111080 14252 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 14 0.0 0.0 111080 13432 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 15 0.0 0.0 111080 13296 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 16 0.0 0.0 111080 13348 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 17 0.0 0.0 111080 13220 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 18 0.0 0.0 111072 14196 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 19 99.7 0.0 111080 10748 ? R 08:58 0:43 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 20 0.2 0.0 0 0 ? Z 08:58 0:00 \_ [kamailio] <defunct>
root 21 0.0 0.0 111080 13068 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 22 0.0 0.0 111080 13156 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 23 0.0 0.0 111080 10684 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 24 0.0 0.0 111080 10684 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 25 0.0 0.0 111080 10748 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 26 0.0 0.0 111080 10748 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 27 0.0 0.0 111080 13344 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
root 28 0.0 0.0 111080 10748 ? S 08:58 0:00 \_ kamailio -A NO_JSON_LOG -f /home/euler/etc/euler.cfg
```
#### 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).
-->
```
8(18) ERROR: db_mysql [km_my_con.c:163]: db_mysql_new_connection(): driver error: SSL connection error: PEM lib
8(18) ERROR: <core> [db.c:319]: db_do_init2(): could not add connection to the pool
8(18) ERROR: sqlops [sql_api.c:165]: sql_connect(): failed to connect to the database [euclid]
8(18) ERROR: <core> [core/sr_module.c:874]: init_mod_child(): error while initializing module sqlops (/home/euler/lib64/euler/modules/sqlops.so) (idx: 8 rank: -2 desc: [Async Task Worker - default])
8(18) ERROR: <core> [core/pt.c:338]: fork_process(): init_child failed for process 8, pid 18, "Async Task Worker - default"
8(18) ERROR: <core> [main.c:1850]: main_loop(): error in init_child
12(22) CRITICAL: <core> [core/mem/q_malloc.c:501]: qm_free(): BUG: bad pointer 0x7fafa23e6270 (out of memory block!) called from tls: tls_init.c: ser_free(323) - ignoring
```
#### 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`
```
version: kamailio 5.5.4 (x86_64/linux)
flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, 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: unknown
compiled with gcc 10.2.1
```
* **Operating System**:
<!--
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`)
-->
```
Linux euler01 5.4.44-2-pve #1 SMP PVE 5.4.44-2 (Wed, 01 Jul 2020 16:37:57 +0200) x86_64 GNU/Linux
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3115
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3115(a)github.com>
### Description
When using the [is_e164 function](https://kamailio.org/docs/modules/5.5.x/modules/siputils.html#sip… on a long Austrian number it doesn't seem to return true even if it's in e164 format.
#### Reproduction
The number in question, with some digits obfuscated for privacy, is +4322367108xxxxxx.
I can confirm that the number exists and is a valid one.
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
version: kamailio 5.5.4 (x86_64/linux)
flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, 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: unknown
compiled with gcc 10.2.1
```
* **Operating System**:
```
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye
Linux kamailio-primary 5.10.0-14-amd64 #1 SMP Debian 5.10.113-1 (2022-04-29) x86_64 GNU/Linux
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3117
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3117(a)github.com>
Module: kamailio
Branch: master
Commit: f0cea1a7c03e400b4398795c2d8b0f7e45d1dfb5
URL: https://github.com/kamailio/kamailio/commit/f0cea1a7c03e400b4398795c2d8b0f7…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2022-06-14T11:46:39+02:00
core: stop at the first config error on startup
- continuing to look for more errors to print them on one check can end
up in crashing because some internal interpreter structure may not be
filled properly
- new cli option --all-errors that can be used to enable printing
details for more detected config errors
---
Modified: src/core/cfg.y
Modified: src/core/globals.h
Modified: src/main.c
---
Diff: https://github.com/kamailio/kamailio/commit/f0cea1a7c03e400b4398795c2d8b0f7…
Patch: https://github.com/kamailio/kamailio/commit/f0cea1a7c03e400b4398795c2d8b0f7…
---
diff --git a/src/core/cfg.y b/src/core/cfg.y
index 713b6789b0..acf5e8c490 100644
--- a/src/core/cfg.y
+++ b/src/core/cfg.y
@@ -3854,6 +3854,9 @@ static void yyerror_at(struct cfg_pos* p, char* format, ...)
LM_CRIT("parse error in config file %s, line %d, column %d: %s\n",
p->fname, p->s_line, p->s_col, s);
cfg_errors++;
+ if(ksr_all_errors==0) {
+ ksr_exit(-1);
+ }
}
diff --git a/src/core/globals.h b/src/core/globals.h
index a4857cbf0c..03eb1ef897 100644
--- a/src/core/globals.h
+++ b/src/core/globals.h
@@ -213,6 +213,7 @@ extern int rt_timer2_policy; /* "slow" timer, SCHED_OTHER */
extern int http_reply_parse;
extern int _sr_ip_free_bind;
extern int ksr_verbose_startup;
+extern int ksr_all_errors;
extern int ksr_route_locks_size;
extern str _ksr_xavp_via_params;
extern str _ksr_xavp_via_fields;
diff --git a/src/main.c b/src/main.c
index cb0c92e357..e919a23274 100644
--- a/src/main.c
+++ b/src/main.c
@@ -206,6 +206,7 @@ Options:\n\
--modparam=modname:paramname:type:value set the module parameter\n\
type has to be 's' for string value and 'i' for int value, \n\
example: --modparam=corex:alias_subdomains:s:" NAME ".org\n\
+ --all-errors Print details about all config errors that can be detected\n\
-M nr Size of private memory allocated, in Megabytes\n\
-n processes Number of child processes to fork per interface\n\
(default: 8)\n"
@@ -482,6 +483,7 @@ int child_rank = 0;
int ser_kill_timeout=DEFAULT_SER_KILL_TIMEOUT;
int ksr_verbose_startup = 0;
+int ksr_all_errors = 0;
/* cfg parsing */
int cfg_errors=0;
@@ -2018,6 +2020,7 @@ int main(int argc, char** argv)
{"debug", required_argument, 0, KARGOPTVAL + 8},
{"cfg-print", no_argument, 0, KARGOPTVAL + 9},
{"atexit", required_argument, 0, KARGOPTVAL + 10},
+ {"all-errors", no_argument, 0, KARGOPTVAL + 11},
{0, 0, 0, 0 }
};
@@ -2128,6 +2131,9 @@ int main(int argc, char** argv)
goto error;
}
break;
+ case KARGOPTVAL+11:
+ ksr_all_errors = 1;
+ break;
default:
if (c == 'h' || (optarg && strcmp(optarg, "-h") == 0)) {
@@ -2317,6 +2323,7 @@ int main(int argc, char** argv)
case KARGOPTVAL+8:
case KARGOPTVAL+9:
case KARGOPTVAL+10:
+ case KARGOPTVAL+11:
break;
/* long options */
Module: kamailio
Branch: master
Commit: 93dccff9391e1336e1a37add1d07b4058b7593e8
URL: https://github.com/kamailio/kamailio/commit/93dccff9391e1336e1a37add1d07b40…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2022-06-14T10:01:27+02:00
modules: readme files regenerated - auth ... [skip ci]
---
Modified: src/modules/auth/README
---
Diff: https://github.com/kamailio/kamailio/commit/93dccff9391e1336e1a37add1d07b40…
Patch: https://github.com/kamailio/kamailio/commit/93dccff9391e1336e1a37add1d07b40…
---
diff --git a/src/modules/auth/README b/src/modules/auth/README
index 25c448901d..f846d752d9 100644
--- a/src/modules/auth/README
+++ b/src/modules/auth/README
@@ -836,6 +836,7 @@ if (!auth_check("$fd", "subscriber", "1")) {
+ 4 - build challenge header with qop=auth and add it to avp
+ 8 - build challenge header with qop=auth-int and add it to avp
+ 16 - build challenge header with stale=true
+ + 32 - don't invalidate nc on authentication failure
* method - the method to be used for authentication. This parameter
is optional and if not set is the first "word" on the request-line.
<!-- 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
This change modifies `pv_www_authenticate` and related functions to add flag 32. If the flag is set and `nonce_count` is enabled then we skip updating nc in `pre_auth`. On success we call `check_nonce` once more to do the nc update. This can be used to chain calls to authenticate against multiple passwords.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3133
-- Commit Summary --
* auth: Add flag for not invalidating nc on auth failure
-- File Changes --
M src/modules/auth/api.c (16)
M src/modules/auth/api.h (3)
M src/modules/auth/auth_mod.c (31)
M src/modules/auth/doc/auth_functions.xml (4)
M src/modules/auth/nc.c (4)
M src/modules/auth/nc.h (2)
M src/modules/auth/nonce.c (4)
M src/modules/auth/nonce.h (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3133.patchhttps://github.com/kamailio/kamailio/pull/3133.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3133
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3133(a)github.com>
Module: kamailio
Branch: master
Commit: a82e5657b66272c0833c1d1d6a55ee29acc315a5
URL: https://github.com/kamailio/kamailio/commit/a82e5657b66272c0833c1d1d6a55ee2…
Author: Jon Bergli Heier <jon.bergli.heier(a)zisson.com>
Committer: Jon Bergli Heier <jon.bergli.heier(a)zisson.com>
Date: 2022-06-03T16:30:53+02:00
auth: Add flag for not invalidating nc on auth failure
If flag 32 is set then we skip updating nc in pre_auth. On success we
call check_nonce once more to do the update. This can be used to chain
calls to eg. pv_auth_check to authenticate against multiple passwords.
---
Modified: src/modules/auth/api.c
Modified: src/modules/auth/api.h
Modified: src/modules/auth/auth_mod.c
Modified: src/modules/auth/doc/auth_functions.xml
Modified: src/modules/auth/nc.c
Modified: src/modules/auth/nc.h
Modified: src/modules/auth/nonce.c
Modified: src/modules/auth/nonce.h
---
Diff: https://github.com/kamailio/kamailio/commit/a82e5657b66272c0833c1d1d6a55ee2…
Patch: https://github.com/kamailio/kamailio/commit/a82e5657b66272c0833c1d1d6a55ee2…
<!--
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:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot 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
I want to get the CDR of the whole call. For this I use the following configuration.
I don't use any sql database. I want to get CDR in syslog
...
loadmodule "db_text.so"
loadmodule "dialog.so"
loadmodule "acc.so"
...
#----Dialog--------------------------
modparam("dialog", "db_mode", 0)
#-----ACCounting module -----
modparam("acc", "early_media", 0)
modparam("acc", "report_cancels", 1)
modparam("acc", "log_facility", "LOG_LOCAL1")
modparam("acc", "detect_direction", 0)
modparam("acc", "log_level", ACC_LOG_LEVEL)
modparam("acc", "log_flag", FLAG_ACC_LOG)
modparam("acc", "log_missed_flag", FLAG_ACC_LOG_MISSED)
modparam("acc", "failed_transaction_flag", FLAG_ACC_LOG_FAILED)
modparam("acc", "log_extra", "ip_src=$si;ip_dst=$avp(ip_dst);sip_from=$fU;sip_to=$tU;ruri_user=$rU;spx_rs=$avp(spx_http_rs)") ## TODO
modparam("acc", "cdr_enable", 1)
modparam("acc", "cdr_facility", "LOG_LOCAL1")
modparam("acc", "cdr_log_enable", 1)
...
request_route {
setflag(FLAG_ACC_LOG);
setflag(FLAG_ACC_LOG_MISSED);
setflag(FLAG_ACC_LOG_FAILED);
...
...
...
}
...
#___handle requests within SIP dialogs
route[HANDLE_IN_DIALOG_REQUESTS] {
if (has_totag()) {
if (loose_route()) {
xlog("L_INFO", "route[WITHINDLG]|$rm with to-tag and loose route|\n");
if (is_method("BYE")) {
setflag(FLAG_ACC_LOG);
}
}
}
As a result, I get two separate records for INVITE and BYE transactions. But I'm expecting one CDR for the entire call.
<!--
Explain what you did, what you expected to happen, and what actually happened.
-->
### Troubleshooting
#### Reproduction
<!--
If the issue can be reproduced, describe how it can be done.
-->
#### 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
I tried to find a solution on the internet, and found this message
https://www.mail-archive.com/sr-users@lists.kamailio.org/msg13617.html
The author talks about an additional flag in the dialog module. And also asks to add this to the documentation of the ACC module
I tried adding a flag but didn't get the desired result. Probably something else needs to be done. There is nothing in the documentation about this. Maybe it makes sense to write a similar article for kamailio?
https://www.opensips.org/Documentation/Tutorials-Advanced-Accounting
<!--
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`
```
[opodguyko@vms-vms-spx-1 ~]$ kamailio -v
version: kamailio 5.5.3 (x86_64/linux) b02728-dirty
flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, 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: b02728 -dirty
compiled on 15:35:46 Dec 15 2021 with gcc 8.3.1
```
* **Operating System**:
<!--
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`)
-->
```
[opodguyko@vms-vms-spx-1 ~]$ cat /etc/redhat-release
AlmaLinux release 8.5 (Arctic Sphynx)
[opodguyko@vms-vms-spx-1 ~]$
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3142
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3142(a)github.com>
<!-- 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)
- [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 -->
On EL8 package with Python 3.9; that is EoL in 2025; Python 3.6 was EoL end 2021.
Python 3.9 lifecycle matches the remaining Full Support cycle of EL8.
Although 5.6 packages were released with Python 3.6; this PR could be backported to 5.6 as 5.6 still has a lot of runway.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3140
-- Commit Summary --
* packaging: on EL8 package with Python 3.9
-- File Changes --
M pkg/kamailio/obs/kamailio.spec (10)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3140.patchhttps://github.com/kamailio/kamailio/pull/3140.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3140
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3140(a)github.com>
app_python3 needs to call `PyOS_AfterFork_Child()`/`PyOS_AfterFork()`
in real child processes.
We need a test for this: rank > 0 may not be sufficient due to
non-forking mode. This POC uses getpid().
- [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
- [ ] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
@miconda @henningw : this PR is for discussion only: in KEMI Python there is an interpreter function that needs to be called after `fork()` in real child processes. I realise that `rank > 0` may not be a completely correct test as kamailio has a non-forking mode. Your comments would be appreciated.
This POC uses `getpid()` to detect a &ldquo;real&rdquo; child process.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3139
-- Commit Summary --
* WIP app_python3: need a test for a real child process
-- File Changes --
M src/modules/app_python3/app_python3_mod.c (10)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3139.patchhttps://github.com/kamailio/kamailio/pull/3139.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3139
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3139(a)github.com>
Module: kamailio
Branch: 5.6
Commit: 824867fd1f81c78cc0fd8c688aa4032c24e49781
URL: https://github.com/kamailio/kamailio/commit/824867fd1f81c78cc0fd8c688aa4032…
Author: Anthony Alba <ascanio.alba7(a)gmail.com>
Committer: Anthony Alba <ascanio.alba7(a)gmail.com>
Date: 2022-06-10T22:20:06+08:00
app_python3: use _ksr_is_main to detect child process
(cherry picked from commit 8683deb20a)
---
Modified: src/modules/app_python3/app_python3_mod.c
---
Diff: https://github.com/kamailio/kamailio/commit/824867fd1f81c78cc0fd8c688aa4032…
Patch: https://github.com/kamailio/kamailio/commit/824867fd1f81c78cc0fd8c688aa4032…
---
diff --git a/src/modules/app_python3/app_python3_mod.c b/src/modules/app_python3/app_python3_mod.c
index d250640e0c..376d1c1312 100644
--- a/src/modules/app_python3/app_python3_mod.c
+++ b/src/modules/app_python3/app_python3_mod.c
@@ -185,9 +185,6 @@ static int child_init(int rank)
* this is called before any process is forked
* so the Python internal state handler
* should be called now.
- *
- * TODO: is PyOS_AfterFork_Parent() necesary
- * in the main process?
*/
#if PY_VERSION_HEX >= 0x03070000
PyOS_BeforeFork() ;
@@ -206,7 +203,7 @@ static int child_init(int rank)
}
_apy_process_rank = rank;
- if (rank > 0) {
+ if (!_ksr_is_main) {
#if PY_VERSION_HEX >= 0x03070000
PyOS_AfterFork_Child();
#else
Module: kamailio
Branch: master
Commit: 8683deb20a3f69c3b6d2c8370d23d1451f823a6b
URL: https://github.com/kamailio/kamailio/commit/8683deb20a3f69c3b6d2c8370d23d14…
Author: Anthony Alba <ascanio.alba7(a)gmail.com>
Committer: Anthony Alba <ascanio.alba7(a)gmail.com>
Date: 2022-06-10T22:13:39+08:00
app_python3: use _ksr_is_main to detect child process
---
Modified: src/modules/app_python3/app_python3_mod.c
---
Diff: https://github.com/kamailio/kamailio/commit/8683deb20a3f69c3b6d2c8370d23d14…
Patch: https://github.com/kamailio/kamailio/commit/8683deb20a3f69c3b6d2c8370d23d14…
---
diff --git a/src/modules/app_python3/app_python3_mod.c b/src/modules/app_python3/app_python3_mod.c
index d250640e0c..376d1c1312 100644
--- a/src/modules/app_python3/app_python3_mod.c
+++ b/src/modules/app_python3/app_python3_mod.c
@@ -185,9 +185,6 @@ static int child_init(int rank)
* this is called before any process is forked
* so the Python internal state handler
* should be called now.
- *
- * TODO: is PyOS_AfterFork_Parent() necesary
- * in the main process?
*/
#if PY_VERSION_HEX >= 0x03070000
PyOS_BeforeFork() ;
@@ -206,7 +203,7 @@ static int child_init(int rank)
}
_apy_process_rank = rank;
- if (rank > 0) {
+ if (!_ksr_is_main) {
#if PY_VERSION_HEX >= 0x03070000
PyOS_AfterFork_Child();
#else
Module: kamailio
Branch: master
Commit: da4f786b0c0275a6e4c8324f9b4c347351b5a48a
URL: https://github.com/kamailio/kamailio/commit/da4f786b0c0275a6e4c8324f9b4c347…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2022-06-10T09:16:30+02:00
modules: readme files regenerated - dispatcher ... [skip ci]
---
Modified: src/modules/dispatcher/README
---
Diff: https://github.com/kamailio/kamailio/commit/da4f786b0c0275a6e4c8324f9b4c347…
Patch: https://github.com/kamailio/kamailio/commit/da4f786b0c0275a6e4c8324f9b4c347…
---
diff --git a/src/modules/dispatcher/README b/src/modules/dispatcher/README
index 6f0978dc6d..9d4287804f 100644
--- a/src/modules/dispatcher/README
+++ b/src/modules/dispatcher/README
@@ -1458,12 +1458,13 @@ if(ds_list_exists("10")) {
specific group id. The parameter can be an integer or a variable
holding an integer value.
* mode - (optional) - a bitmask to specify how the matching should be
- done. If parameter is 0, all ip, port and proto are matched and
- active status is ignored. If bit one is set, then port is ignored.
- If bit two is set, then protocol is ignored. If bit three is set,
- then state must be active. The parameter can be an integer or a
- variable holding an integer value. It must be provided if the uri
- parameter is provided.
+ done. If the parameter is missing, the matching is done with
+ ignoring the protocol (value 2). If parameter is 0, all ip, port
+ and proto are matched and active status is ignored. If bit one is
+ set, then port is ignored. If bit two is set, then protocol is
+ ignored. If bit three is set, then state must be active. The
+ parameter can be an integer or a variable holding an integer value.
+ It must be provided if the uri parameter is provided.
* uri (optional) - if parameter is empty or missing, the matching is
done against source IP, port and protocol. Otherwise the value has
to be a valid SIP URI, used to match against addresses in the