which responses are ??
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/commit/c1bc5f7095659182401e6dd2b25bfaf…
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/commit/c1bc5f7095659182401e6dd2b25bfaf7f963466a/130981246(a)github.com>
Module: kamailio
Branch: master
Commit: c1bc5f7095659182401e6dd2b25bfaf7f963466a
URL: https://github.com/kamailio/kamailio/commit/c1bc5f7095659182401e6dd2b25bfaf…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2023-10-26T13:41:12+02:00
usrloc: docs for ka_reply_codes parameter
---
Modified: src/modules/usrloc/doc/usrloc_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/c1bc5f7095659182401e6dd2b25bfaf…
Patch: https://github.com/kamailio/kamailio/commit/c1bc5f7095659182401e6dd2b25bfaf…
---
diff --git a/src/modules/usrloc/doc/usrloc_admin.xml b/src/modules/usrloc/doc/usrloc_admin.xml
index 61491648a0c..5f244bc80e5 100644
--- a/src/modules/usrloc/doc/usrloc_admin.xml
+++ b/src/modules/usrloc/doc/usrloc_admin.xml
@@ -1504,6 +1504,29 @@ modparam("usrloc", "ka_logmsg", " to-uri: [$tu] remote-addr: [$sas]")
</example>
</section>
+ <section id="usrloc.p.ka_reply_codes">
+ <title><varname>ka_reply_codes</varname> (str)</title>
+ <para>
+ Comma separated list of reply code values or reply code classes to be
+ considered valid for keepalive processing. If the reply code does not
+ match any of them, then the reply is ignored, not considered a valid
+ response to keepalive request. It could be useful to skip replies
+ from intermediary proxies that could not forward the request.
+ </para>
+ <para>
+ Default value is <quote>0</quote> (checking of reply code is not done,
+ are responses are considered valid).
+ </para>
+ <example>
+ <title><varname>ka_reply_codes</varname> parameter usage</title>
+ <programlisting format="linespecific">
+...
+modparam("usrloc", "ka_reply_codes", "2,405,486")
+...
+ </programlisting>
+ </example>
+ </section>
+
<section id="usrloc.p.load_rank">
<title><varname>load_rank</varname> (int)</title>
<para>
>From https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000134:
```
Source: kamailio
Severity: important
User: matthew-pcredep(a)debian.org
Usertags: obsolete-pcre3
Dear maintainer,
Your package still depends on the old, obsolete PCRE3[0] libraries
(i.e. libpcre3-dev). This has been end of life for a while now, and
upstream do not intend to fix any further bugs in it. Accordingly, I
would like to remove the pcre3 libraries from Debian, preferably in
time for the release of Bookworm.
The newer PCRE2 library was first released in 2015, and has been in
Debian since stretch. Upstream's documentation for PCRE2 is available
here: https://pcre.org/current/doc/html/
Many large projects that use PCRE have made the switch now (e.g. git,
php); it does involve some work, but we are now at the stage where
PCRE3 should not be used, particularly if it might ever be exposed to
untrusted input.
This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00176.html
Regards,
Matthew [0] Historical reasons mean that old PCRE is packaged as
pcre3 in Debian
```
--
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/2946