<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for feature requests.
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 you submit a feature request (or enhancement) add the description of what you would like to be added.
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
Could a module parameter be added to retry a request _n_ number of times in the event of a connection or server failure, without having to write a tedious bit of boiler plate config to catch failure response codes and retry.
### Expected behavior
A http(s) post or get is performed and the returned code is < 0 but > -20 (null url return code in libruxc) or is a 5xx or 6xx http error code. The module will reattempt the request up to the number of attempts defined in a module parameter.
By default this behaviour is disabled and would require explicitly defining the module parameter to enable it.
Requests could be exempted from automatic retries by either adding an additional argument to the function called in config, or a http header could be supplied `X-RUXC-NORETRY` for example using the existing function signature to exclude the request.
The header name could also be defined as a module parameter.
--
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/2820
### Description
Would it be possible to have the debug messages from libruxc entered into the kamailio logs, as thats much more useful than -1 for diagnosing connection failures, as well as the uri of the failing request?
### Expected behavior
Some diagnostic data passed up from libruxc detailing connection failure.
#### Actual observed behavior
`ERROR: ruxc [ruxc_mod.c:151]: ki_ruxc_http_get_helper(): failed to perform http get - retcode: -1 uri: https://someservice.somewhere.com`
--
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/2819
I've made some testing and found that filter_body() fails when body is something like "Content-Type:application\/sdp\r\n\r\n".
If i use this correction to add a space the filter works correctly :
replace_body_all("Content-Type:application\/sdp\r\n\r\n","Content-Type: application/sdp\r\n\r\n");
#Makes the changes to the message persistent, returns 1 if sucessful, 0 if it fails
if(msg_apply_changes())
{
xnotice("Kamailio_Log : reply_route : Changes to message applied");
}
I looked into the textops.c and found this line which i think might be the problem :
while (find_line_start("Content-Type: ", 14, &start, &len))
If more info is needed please let me know.
Cheers
--
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/2748
Module: kamailio
Branch: master
Commit: 1c9fa44521106968a0c68b2dba96a421ad523fda
URL: https://github.com/kamailio/kamailio/commit/1c9fa44521106968a0c68b2dba96a42…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2021-08-11T10:16:23+02:00
modules: readme files regenerated - tlsa ... [skip ci]
---
Modified: src/modules/tlsa/README
---
Diff: https://github.com/kamailio/kamailio/commit/1c9fa44521106968a0c68b2dba96a42…
Patch: https://github.com/kamailio/kamailio/commit/1c9fa44521106968a0c68b2dba96a42…
---
diff --git a/src/modules/tlsa/README b/src/modules/tlsa/README
index 100da0fed4..ed29072e58 100644
--- a/src/modules/tlsa/README
+++ b/src/modules/tlsa/README
@@ -53,3 +53,8 @@ Chapter 1. Admin Guide
not support same static linking options. Also, some operating systems
may provide only dynamic libssl and libcrypto libraries via their
packages.
+
+ NOTE: edit the Makefile in the module folder and update it accordingly
+ to set the path to libssl and libcrypto libraries specific to own
+ system when not wanting to use "pkg-config" (e.g., when having these
+ libraries compiled from sources).
Module: kamailio
Branch: master
Commit: 162c1d8f1d3522fa937bc1869fe65ad87d4e3680
URL: https://github.com/kamailio/kamailio/commit/162c1d8f1d3522fa937bc1869fe65ad…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2021-08-11T09:59:40+02:00
tlsa: Makefile - comment to set lib path to installation folder
- GH #2815
---
Modified: src/modules/tlsa/Makefile
---
Diff: https://github.com/kamailio/kamailio/commit/162c1d8f1d3522fa937bc1869fe65ad…
Patch: https://github.com/kamailio/kamailio/commit/162c1d8f1d3522fa937bc1869fe65ad…
---
diff --git a/src/modules/tlsa/Makefile b/src/modules/tlsa/Makefile
index eb01df99aa..9295898aad 100644
--- a/src/modules/tlsa/Makefile
+++ b/src/modules/tlsa/Makefile
@@ -12,6 +12,8 @@ NAME=tlsa.so
LIBSSL_STATIC_SRCLIB ?= no
# set to the path of the folder with static libraries compiled from source
LIBSSL_STATIC_SRCPATH ?= /usr/local/src/openssl
+# or set to the path where the static libraries are installed, for example:
+# LIBSSL_STATIC_SRCPATH ?= /usr/lib/x86_64-linux-gnu/
ifeq ($(CROSS_COMPILE),)
SSL_BUILDER=$(shell \
Module: kamailio
Branch: master
Commit: db77d45e03792f73982861dcf30bad8d94bd7453
URL: https://github.com/kamailio/kamailio/commit/db77d45e03792f73982861dcf30bad8…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2021-08-11T10:05:31+02:00
tls: docs - note about path to libraries in the Makefile
---
Modified: src/modules/tlsa/doc/tlsa.xml
---
Diff: https://github.com/kamailio/kamailio/commit/db77d45e03792f73982861dcf30bad8…
Patch: https://github.com/kamailio/kamailio/commit/db77d45e03792f73982861dcf30bad8…
---
diff --git a/src/modules/tlsa/doc/tlsa.xml b/src/modules/tlsa/doc/tlsa.xml
index eecc5f9ab1..d17c509813 100644
--- a/src/modules/tlsa/doc/tlsa.xml
+++ b/src/modules/tlsa/doc/tlsa.xml
@@ -72,6 +72,12 @@
systems may provide only dynamic libssl and libcrypto libraries
via their packages.
</para>
+ <para>
+ NOTE: edit the Makefile in the module folder and update it accordingly
+ to set the path to libssl and libcrypto libraries specific to own
+ system when not wanting to use "pkg-config" (e.g., when having
+ these libraries compiled from sources).
+ </para>
</section>
</chapter>
</book>
### Description
I've installed Kamailio 5.5 from the Debian 10 repository and added the WITH_TLS flag to default config file but Kamailio refuses to start.
Looking at the logs I found out that the tls.so file in the modules folder is missing. I checked the docs and it seems that the package has been compiled with the right flags but I'm no Kamailio expert so I decided to open this issue to have it checked.
#### Log Messages
```
kamailio kamailio: ERROR: <core> [core/sr_module.c:504]: ksr_locate_module(): could not find module <tls> in </usr/lib/x86_64-linux-gnu/kamailio/modules>
```
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
version: kamailio 5.5.1 (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 8.3.0
```
* **Operating System**:
```
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 10 (buster)
Release: 10
Codename: buster
Linux kamailio 4.19.0-17-amd64 #1 SMP Debian 4.19.194-3 (2021-07-18) x86_64 GNU/Linux
```
--
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/2816
- Mention when FR timeout is reached, and which of FR timers expired
- Log when starting FR/RETR timers
- log when changing default timeouts to user set values
- log when resetting fr/retr timers on provisional replies
<!-- 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
- [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 -->
- [X] 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 -->
The main reason for these changes is that we haven't found any possibility to distinguish which of `fr` timeouts expires. The rest of the logs are also helpful, but secondary.
As they all are under `ifdef TIMEOUT_DEBUG` I hope it is not a big deal.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2817
-- Commit Summary --
* tm: enhance fr/retr timers logging
-- File Changes --
M src/modules/tm/t_lookup.c (6)
M src/modules/tm/t_reply.c (3)
M src/modules/tm/t_suspend.c (3)
M src/modules/tm/timer.c (7)
M src/modules/tm/timer.h (4)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2817.patchhttps://github.com/kamailio/kamailio/pull/2817.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/2817