Module: kamailio
Branch: 5.6
Commit: b230a4621c4fa4a19860c6e909bc06da3d4633c5
URL: https://github.com/kamailio/kamailio/commit/b230a4621c4fa4a19860c6e909bc06d…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2023-11-13T16:56:16+01:00
modules: readme files regenerated - modules ... [skip ci]
---
Modified: src/modules/db_text/README
Modified: src/modules/ldap/README
Modified: src/modules/snmpstats/README
Modified: src/modules/sst/README
---
Diff: https://github.com/kamailio/kamailio/commit/b230a4621c4fa4a19860c6e909bc06d…
Patch: https://github.com/kamailio/kamailio/commit/b230a4621c4fa4a19860c6e909bc06d…
---
diff --git a/src/modules/db_text/README b/src/modules/db_text/README
index a43bf8087ca..be34a3dc2dc 100644
--- a/src/modules/db_text/README
+++ b/src/modules/db_text/README
@@ -426,7 +426,7 @@ loadmodule "modules/auth_db/auth_db.so"
# use dbtext database for persistent storage
modparam("usrloc", "db_mode", 2)
-modparam("usrloc|auth_db", "db_url", "db_text:///tmp/kamailiodb")
+modparam("usrloc|auth_db", "db_url", "text:///tmp/kamailiodb")
# -- auth params --
#
diff --git a/src/modules/ldap/README b/src/modules/ldap/README
index c7555ca3c60..921f45822f1 100644
--- a/src/modules/ldap/README
+++ b/src/modules/ldap/README
@@ -533,7 +533,7 @@ ldap_result("telephoneNumber/$avp(s:tel_number)");
AVP. It can be either str for string, or int for integer. If avp_type
is specified as int then ldap_result tries to convert the LDAP
attribute values to integer. In this case, the values are only stored
- as AVP if the conversion to integer is succesfull.
+ as AVP if the conversion to integer is successful.
Function Parameters:
diff --git a/src/modules/snmpstats/README b/src/modules/snmpstats/README
index e22b2485130..047bb275189 100644
--- a/src/modules/snmpstats/README
+++ b/src/modules/snmpstats/README
@@ -340,7 +340,7 @@ modparam("snmpstats", "sipEntityType", "proxyServer")
The SNMPStats module monitors the number of bytes waiting to be
consumed by Kamailio. If the number of bytes waiting to be consumed
- exceeds a minor threshold, the SNMPStats module will send out an
+ exceeds a minor threshold, the SNMPStats module will send out a
kamailioMsgQueueDepthMinorEvent trap to signal that an alarm condition
has occurred. The minor threshold is set with the
MsgQueueMinorThreshold parameter.
@@ -357,7 +357,7 @@ modparam("snmpstats", "MsgQueueMinorThreshold", 2000)
The SNMPStats module monitors the number of bytes waiting to be
consumed by Kamailio. If the number of bytes waiting to be consumed
- exceeds a major threshold, the SNMPStats module will send out an
+ exceeds a major threshold, the SNMPStats module will send out a
kamailioMsgQueueDepthMajorEvent trap to signal that an alarm condition
has occurred. The major threshold is set with the
MsgQueueMajorThreshold parameter.
diff --git a/src/modules/sst/README b/src/modules/sst/README
index ed31b933133..3444863563d 100644
--- a/src/modules/sst/README
+++ b/src/modules/sst/README
@@ -90,7 +90,7 @@ Chapter 1. Admin Guide
The sst module provides a way to update the dialog expiry timer based
on the SIP INVITE/200 OK Session-Expires header value. You can use the
- sst module in a Kamailio proxy to allow freeing of local resources of
+ sst module in an Kamailio proxy to allow freeing of local resources of
dead calls.
You can also use the sst module to validate the MIN_SE header value and
Hello,
while couple of developers are at Kamailio project meeting in
Dusseldorf, it was somehow agreed here that it would be easier to
backport fixes from master to branch 5.7 if the code in that stable
branch is going to be formatted using clang like it was done for master.
Should anyone has any remarks against it, let's discuss. If not,
probably it is going to be done in couple of days, then plan to release
5.7.3.
Cheers,
Daniel
--
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy and Development Services
Use tcp_send_timeout config option also on listening socket to timeout outbound messages sent on passive inbound connections.
#### 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
- [x] Tested changes locally
- [x] Related to issue #3443
#### Description
Based on the description of core parameter "tcp_send_timeout" the timeout should also work for sending on forked incoming tcp connections. But sending on a broken connection causes the kernel to use the default values of `tcp_retries1` and `tcp_retries2` , leading to try to send a SIP message for 15 minutes. This makes absolutely no sense in a real time kamailio application.
Following man 7 tcp TCP_USER_TIMEOUT can be used on recent Linux kernels to utilize tcp_send_timeout:
TCP_USER_TIMEOUT (since Linux 2.6.37)
This option takes an unsigned int as an argument. When the value is greater than 0, it specifies the maximum
amount of time in milliseconds that transmitted data may remain unacknowledged before TCP will forcibly close the
corresponding connection and return ETIMEDOUT to the application. If the option value is specified as 0, TCP will
use the system default.
Increasing user timeouts allows a TCP connection to survive extended periods without end-to-end connectivity. De‐
creasing user timeouts allows applications to "fail fast", if so desired. Otherwise, failure may take up to 20
minutes with the current system defaults in a normal WAN environment.
This option can be set during any state of a TCP connection, but is effective only during the synchronized states
of a connection (ESTABLISHED, FIN-WAIT-1, FIN-WAIT-2, CLOSE-WAIT, CLOSING, and LAST-ACK). Moreover, when used
with the TCP keepalive (SO_KEEPALIVE) option, TCP_USER_TIMEOUT will override keepalive to determine when to close
a connection due to keepalive failure.
The option has no effect on when TCP retransmits a packet, nor when a keepalive probe is sent.
This option, like many others, will be inherited by the socket returned by accept(2), if it was set on the listen‐
ing socket.
Further details on the user timeout feature can be found in RFC 793 and RFC 5482 ("TCP User Timeout Option").
Having a tcp connection break by firewall or network breakdown the retransmits to this destination are now aborted after `tcp_send_timeout` seconds with a
NOTICE: <core> [core/tcp_read.c:267]: tcp_read_data(): error reading: Connection timed out (110) ([1.2.3.4]:51151 ->
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3528
-- Commit Summary --
* core: Add TCP_USER_TIMEOUT socket option on listening socket.
-- File Changes --
M src/core/tcp_main.c (13)
M src/core/tcp_options.h (7)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3528.patchhttps://github.com/kamailio/kamailio/pull/3528.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3528
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3528(a)github.com>
>From http://lists.kamailio.org/pipermail/sr-dev/2016-August/036231.html
On 24/08/16 10:17, Andreas Granig wrote:
> Hi,
>
> When translating strings with the dialplan module, you sometimes end up
> with very complex patterns for sanitizing the target string and
> performing some replacements, since for a given dialplan id, processing
> stops on the first match within the dialplan entries for a given dpid.
>
> The idea is to introduce a "continue" flag (default 0) in the dialplan
> table indicating to proceed with processing further dialplan entries
> within the given dpid after a match. The use case is to have a sanitize
> rule with highest priority which e.g. removes any spaces, dashes and
> parentheses from the target string, then with a lower priority do
> further processing with the cleaned up string, e.g. stripping leading
> double-zeroes or a plus when normalizing to E164 numbers, or replacing a
> single leading zero with the country code and so on.
>
> This is particularly useful when a user dials a number from an address
> book of some sort (e.g. on a mobile app) where number formats are stored
> with country-specific formating characters like "+1-(234)-567 890", and
> catching all of that in one rule results in really messy match/replace
> patterns.
--
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/764