Module: kamailio
Branch: master
Commit: a34463c9f5fc5faade30d36f168b10105de98ac8
URL: https://github.com/kamailio/kamailio/commit/a34463c9f5fc5faade30d36f168b101…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2021-09-13T09:31:18+02:00
modules: readme files regenerated - registrar ... [skip ci]
---
Modified: src/modules/registrar/README
---
Diff: https://github.com/kamailio/kamailio/commit/a34463c9f5fc5faade30d36f168b101…
Patch: https://github.com/kamailio/kamailio/commit/a34463c9f5fc5faade30d36f168b101…
---
diff --git a/src/modules/registrar/README b/src/modules/registrar/README
index a33e556545..94ab08ab3c 100644
--- a/src/modules/registrar/README
+++ b/src/modules/registrar/README
@@ -1009,6 +1009,8 @@ kamcmd cfg.set_now_int registrar use_expired_contacts 0
AoR (user).
+ 0x08 - Do not apply expires_range or default_expires_range to
this registration.
+ + 0x10 - prepare the headers for reply, used only if flag 0x02
+ is set.
The flags may be given in decimal or hexadecimal format.
* uri (optional - flags param has to be set and can be 0 for default
behavior) - SIP URI to do be used instead of To header URI. It can
### Description
I have working Kamailio config for WebRTC clients.
I now want to use `tcp_reuse_port` feature and this feature breaks WebRTC clients.
#### Log Messages
```
106(106803) DEBUG: {1 41089865 ACK d50c83b4-124a-11ec-a038-835ce78b460e} <core> [core/forward.c:578]: forward_request(): orig. len=865, new_len=741, proto=5
106(106803) DEBUG: {1 41089865 ACK d50c83b4-124a-11ec-a038-835ce78b460e} <core> [core/forward.h:169]: msg_send_buffer(): sending to: 109.121.188.190:56424, force_socket=4, send_sock=0xffffa40ffa98
106(106803) WARNING: {1 41089865 ACK d50c83b4-124a-11ec-a038-835ce78b460e} <core> [core/forward.h:203]: msg_send_buffer(): TCP/TLS connection for WebSocket could not be found
106(106803) ERROR: {1 41089865 ACK d50c83b4-124a-11ec-a038-835ce78b460e} sl [sl_funcs.c:418]: sl_reply_error(): stateless error reply used: Unfortunately error on sending to next hop occurred (477/SL)
```
More logs at the attached `ack.log` file.
[ask.log](https://github.com/kamailio/kamailio/files/7144893/ask.log)
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
used master branch with small customization, base commit c503d2bd31a580138a67f1d4a265ccde5791d271
* **Operating System**:
aarch64
```
[root@tmp kamailio]# cat /etc/os-release
NAME="CentOS Linux"
VERSION="8"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="8"
PLATFORM_ID="platform:el8"
PRETTY_NAME="CentOS Linux 8"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:8"
HOME_URL="https://centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"
CENTOS_MANTISBT_PROJECT="CentOS-8"
CENTOS_MANTISBT_PROJECT_VERSION="8"
```
--
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/2849
Hello all,
Debian 11 "Bullseye" is to be released this Saturday. Do you expect to have
binaries available for it on deb.kamailio.org anytime soon following the
release? Thanks!
BR,
George
Module: kamailio
Branch: master
Commit: 7d41d02028d095bd7e52047665db4f53ae606cc3
URL: https://github.com/kamailio/kamailio/commit/7d41d02028d095bd7e52047665db4f5…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2021-09-10T13:31:16+02:00
modules: readme files regenerated - registrar ... [skip ci]
---
Modified: src/modules/registrar/README
---
Diff: https://github.com/kamailio/kamailio/commit/7d41d02028d095bd7e52047665db4f5…
Patch: https://github.com/kamailio/kamailio/commit/7d41d02028d095bd7e52047665db4f5…
---
diff --git a/src/modules/registrar/README b/src/modules/registrar/README
index e3876fa7c0..a33e556545 100644
--- a/src/modules/registrar/README
+++ b/src/modules/registrar/README
@@ -935,6 +935,9 @@ end
with branch flags matching at least one set inside xavp specified
by xavp_cfg parameter with inner name rlf_bflags - e.g.,
$xavp(reg=>rlf_bflags).
+ * 2 - apply the active tcp connection filter - return only contact
+ records that have the associated TCP/TLS/WSS connection active. UDP
+ and SCTP contacts are not filtered, all are returned.
Default value is NULL (disabled).