I've searched, but I cannot find anything recent about this.
My kamailio 5.0.8 proxy sends an INVITE downstream over UDP and gets
an ICMP port-unreachable response from the UAS.
Apparently ignoring this, it re-transmits the INVITEs and eventually
times out and sends to the next host (from the SRV lookup).
According to RFC 3261 (https://tools.ietf.org/html/rfc3261#section-8.1.3.1),
If a fatal transport error is reported by the transport layer
(generally, due to fatal ICMP errors in UDP or connection failures in
TCP), the condition MUST be treated as a 503 (Service Unavailable)
status code.
Does kamailio support handling ICMP responses to INVITEs (and
therefore either failing over immediately, or sending 503 upstream
immediately)?
I don't know for sure the "correct" behavior because the RFC3261 is so
old and because ICMP responses are limited in size and therefore can't
guarantee to uniquely identify the transactions that caused them.
Module: kamailio
Branch: master
Commit: 076649793bfdbdc4f03f96961f23997c87ce4268
URL: https://github.com/kamailio/kamailio/commit/076649793bfdbdc4f03f96961f23997…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2020-05-06T17:15:36+02:00
pua: use file name specific include guard
---
Modified: src/modules/pua/hash.h
Modified: src/modules/pua/pua.h
---
Diff: https://github.com/kamailio/kamailio/commit/076649793bfdbdc4f03f96961f23997…
Patch: https://github.com/kamailio/kamailio/commit/076649793bfdbdc4f03f96961f23997…
---
diff --git a/src/modules/pua/hash.h b/src/modules/pua/hash.h
index cc73d3e761..454e4bb853 100644
--- a/src/modules/pua/hash.h
+++ b/src/modules/pua/hash.h
@@ -15,8 +15,8 @@
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
- * You should have received a copy of the GNU General Public License
- * along with this program; if not, write to the Free Software
+ * You should have received a copy of the GNU General Public License
+ * along with this program; if not, write to the Free Software
* Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
*/
diff --git a/src/modules/pua/pua.h b/src/modules/pua/pua.h
index 57cc379ebe..908f5b0cb3 100644
--- a/src/modules/pua/pua.h
+++ b/src/modules/pua/pua.h
@@ -15,13 +15,13 @@
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
- * You should have received a copy of the GNU General Public License
- * along with this program; if not, write to the Free Software
+ * You should have received a copy of the GNU General Public License
+ * along with this program; if not, write to the Free Software
* Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
*/
-#ifndef PUBLISH_H
-#define PUBLISH_H
+#ifndef _PUA_H_
+#define _PUA_H_
#include "../../core/str.h"
#include "../../lib/srdb1/db.h"
Hello,
Kamailio SIP Server v5.3.4 stable release is out.
This is a maintenance release of the latest stable branch, 5.3, that
includes fixes since the release of v5.3.3. There is no change to
database schema or configuration language structure that you have to do
on previous installations of v5.3.x. Deployments running previous v5.3.x
versions are strongly recommended to be upgraded to v5.3.4.
For more details about version 5.3.4 (including links and guidelines to
download the tarball or from GIT repository), visit:
* https://www.kamailio.org/w/2020/05/kamailio-v5-3-4-released/
RPM, Debian/Ubuntu packages will be available soon as well.
Many thanks to all contributing and using Kamailio!
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Module: kamailio
Branch: 5.3
Commit: 4322479f914cc4a256000c1dae44129939d4dd10
URL: https://github.com/kamailio/kamailio/commit/4322479f914cc4a256000c1dae44129…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2020-05-06T12:31:52+02:00
modules: readme files regenerated - modules ... [skip ci]
---
Modified: src/modules/htable/README
---
Diff: https://github.com/kamailio/kamailio/commit/4322479f914cc4a256000c1dae44129…
Patch: https://github.com/kamailio/kamailio/commit/4322479f914cc4a256000c1dae44129…
---
diff --git a/src/modules/htable/README b/src/modules/htable/README
index 78b7547085..5acb910b23 100644
--- a/src/modules/htable/README
+++ b/src/modules/htable/README
@@ -442,11 +442,17 @@ $ kamcmd htable.dump htable
configuration file.
* htname - string specifying the name of the hash table. This string
is used by $sht(...) to refer to the hash table.
- * size - number specifying the size of hash table. Larger value means
- less collisions. The number of entries (aka slots or buckets) in
- the table is 2^size. The possible range for this value is from 2 to
- 31, smaller or larger values will be increased to 3 (8 slots) or
- decreased to 14 (16384 slots).
+ * size - number to control how many slots (buckets) to create for the
+ hash table. Larger value means more slots with higher probability
+ for less collisions. The actual number slots (or buckets) created
+ for the table is 2^size. The possible range for this value is from
+ 2 to 31, smaller or larger values will be increased to 3 (8 slots)
+ or decreased to 14 (16384 slots). Note that each slot can store
+ more than one item, when there are collisions of hash ids computed
+ for keys. The items in the same slot are stored in a linked list.
+ In other words, the size is not setting a limit of how many items
+ can be stored in a hash table, as long as there is enough free
+ shared memory, new items can be added.
* autoexpire -time in seconds to delete an item from a hash table if
no update was done to it. If is missing or set to 0, the items
won't expire.