Hello,
there is some planned work on the data center infrastructure hosting
kamailio.org server that is going to affect briefly the web server (web
site, wiki) and the mailing lists.
The downtime is expected to be 10-15 minutes around 1:00am Western
Europe time (CEST / GMT+2), but if it takes longer or repeats, be
patient for a while.
Cheers,
Daniel
--
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com
### Description
Hello. Probably I'm doing something wrong but I can't get rid of **received** parameter in the **Via** header in responses from kamailio by websocket transport.
According [RFC 7118](https://datatracker.ietf.org/doc/rfc7118/):
``
When a SIP WebSocket Server receives a request, it MAY decide not
to add a "received" parameter to the top Via header. Therefore,
SIP WebSocket Clients MUST accept responses without such a
parameter in the top Via header regardless of whether the **Via**
"sent-by" field contains a domain name.
``
### Expected behavior
For responses to websocket transport have a way to not add **received** parameter in **Via** header
#### Actual observed behavior
Responses to OPTION or REGISTER methods trough websocket got **received** containing IP we want to not show to the end users.
### Possible Solutions
maybe add a param in **tm** module or something
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
version: kamailio 5.2.1 (x86_64/linux)
```
and
```
kamailio 5.6.1 (x86_64/linux) b36a13
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3515
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3515(a)github.com>
Module: kamailio
Branch: master
Commit: 94b9cd5d5ffafde86fbcbede2d9a018fc616b6b1
URL: https://github.com/kamailio/kamailio/commit/94b9cd5d5ffafde86fbcbede2d9a018…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2024-04-15T11:01:29+02:00
modules: readme files regenerated - cfgutils ... [skip ci]
---
Modified: src/modules/cfgutils/README
---
Diff: https://github.com/kamailio/kamailio/commit/94b9cd5d5ffafde86fbcbede2d9a018…
Patch: https://github.com/kamailio/kamailio/commit/94b9cd5d5ffafde86fbcbede2d9a018…
---
diff --git a/src/modules/cfgutils/README b/src/modules/cfgutils/README
index b7c8075fad9..cb6251b6719 100644
--- a/src/modules/cfgutils/README
+++ b/src/modules/cfgutils/README
@@ -65,9 +65,9 @@ Daniel-Constantin Mierla
4.12. set_gflag(flag)
4.13. reset_gflag(flag)
4.14. is_gflag(flag)
- 4.15. lock(key)
- 4.16. trylock(key)
- 4.17. unlock(key)
+ 4.15. lock(key [, key2])
+ 4.16. trylock(key [, key2])
+ 4.17. unlock(key [, key2])
4.18. check_route_exists(route)
4.19. route_if_exists(route)
4.20. core_hash(string1, string2, size)
@@ -154,9 +154,9 @@ Chapter 1. Admin Guide
4.12. set_gflag(flag)
4.13. reset_gflag(flag)
4.14. is_gflag(flag)
- 4.15. lock(key)
- 4.16. trylock(key)
- 4.17. unlock(key)
+ 4.15. lock(key [, key2])
+ 4.16. trylock(key [, key2])
+ 4.17. unlock(key [, key2])
4.18. check_route_exists(route)
4.19. route_if_exists(route)
4.20. core_hash(string1, string2, size)
@@ -304,9 +304,9 @@ modparam("cfgutils", "lock_set_size", 4)
4.12. set_gflag(flag)
4.13. reset_gflag(flag)
4.14. is_gflag(flag)
- 4.15. lock(key)
- 4.16. trylock(key)
- 4.17. unlock(key)
+ 4.15. lock(key [, key2])
+ 4.16. trylock(key [, key2])
+ 4.17. unlock(key [, key2])
4.18. check_route_exists(route)
4.19. route_if_exists(route)
4.20. core_hash(string1, string2, size)
@@ -506,16 +506,18 @@ if(is_gflag("4"))
};
...
-4.15. lock(key)
+4.15. lock(key [, key2])
Lock the key. Can be used to synchronize operations in config file, a
- hash id is computed over the key and appropriate lock is set in the
+ hash id is computed over the keys and appropriate lock is set in the
lock array controlled by parameter "lock_set_size". Do not use lock()
after another lock() unless you are sure the keys hit different array
entries.
���key��� can be static string or string with PVs.
+ ���key2��� is optional and can be static string or string with PVs.
+
This function can be used from REQUEST_ROUTE, FAILURE_ROUTE,
ONREPLY_ROUTE, BRANCH_ROUTE and LOCAL_ROUTE.
@@ -524,13 +526,15 @@ if(is_gflag("4"))
lock("$rU");
...
-4.16. trylock(key)
+4.16. trylock(key [, key2])
Try to lock the key. If the lock can not be obtained (possibly already
locked), the function returns an error and script execution continues.
���key��� can be static string or string with PVs.
+ ���key2��� is optional and can be static string or string with PVs.
+
This function can be used from REQUEST_ROUTE, FAILURE_ROUTE,
ONREPLY_ROUTE, BRANCH_ROUTE and LOCAL_ROUTE.
@@ -542,12 +546,14 @@ if (trylock("$rU")) {
}
...
-4.17. unlock(key)
+4.17. unlock(key [, key2])
Unlock the key.
���key��� can be static string or string with PVs.
+ ���key2��� is optional and can be static string or string with PVs.
+
This function can be used from REQUEST_ROUTE, FAILURE_ROUTE,
ONREPLY_ROUTE, BRANCH_ROUTE and LOCAL_ROUTE.
#### 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
- [ ] Small bug fix (non-breaking change which fixes an issue)
- [x] 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 -->
- [ ] PR should be backported to stable branches
- [x] Tested changes locally
#### Description
expose in config via cfgutils ``core_case_hash`` optional second string key for hashing
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3808
-- Commit Summary --
* cfgutils: expose optional second string key for hashing at locks
* cfgutils: document second optional string for hashing on lock functions family [skip ci]
* app_lua_sr: support second str for cfgutils lock
-- File Changes --
M src/modules/app_lua_sr/app_lua_sr_exp.c (30)
M src/modules/cfgutils/api.h (4)
M src/modules/cfgutils/cfgutils.c (103)
M src/modules/cfgutils/doc/cfgutils_admin.xml (18)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3808.patchhttps://github.com/kamailio/kamailio/pull/3808.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3808
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3808(a)github.com>
Module: kamailio
Branch: master
Commit: 235591cd704529589bbde700b6232ac55281d071
URL: https://github.com/kamailio/kamailio/commit/235591cd704529589bbde700b6232ac…
Author: Victor Seva <linuxmaniac(a)torreviejawireless.org>
Committer: Victor Seva <linuxmaniac(a)torreviejawireless.org>
Date: 2024-04-15T10:50:26+02:00
cfgutils: document second optional string for hashing on lock functions family [skip ci]
---
Modified: src/modules/cfgutils/doc/cfgutils_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/235591cd704529589bbde700b6232ac…
Patch: https://github.com/kamailio/kamailio/commit/235591cd704529589bbde700b6232ac…
---
diff --git a/src/modules/cfgutils/doc/cfgutils_admin.xml b/src/modules/cfgutils/doc/cfgutils_admin.xml
index 1cab1284fd5..35721e31c6d 100644
--- a/src/modules/cfgutils/doc/cfgutils_admin.xml
+++ b/src/modules/cfgutils/doc/cfgutils_admin.xml
@@ -485,10 +485,10 @@ if(is_gflag("4"))
</example>
</section>
<section id="cfgutils.f.lock">
- <title><function moreinfo="none">lock(key)</function></title>
+ <title><function moreinfo="none">lock(key [, key2])</function></title>
<para>
Lock the key. Can be used to synchronize operations in config file,
- a hash id is computed over the key and appropriate lock is set in the
+ a hash id is computed over the keys and appropriate lock is set in the
lock array controlled by parameter "lock_set_size". Do not use lock()
after another lock() unless you are sure the keys hit different array
entries.
@@ -497,6 +497,9 @@ if(is_gflag("4"))
<quote>key</quote> can be static string or string with PVs.
</para>
<para>
+ <quote>key2</quote> is optional and can be static string or string with PVs.
+ </para>
+ <para>
This function can be used from REQUEST_ROUTE, FAILURE_ROUTE,
ONREPLY_ROUTE, BRANCH_ROUTE and LOCAL_ROUTE.
</para>
@@ -510,7 +513,7 @@ lock("$rU");
</example>
</section>
<section id="cfgutils.f.trylock">
- <title><function moreinfo="none">trylock(key)</function></title>
+ <title><function moreinfo="none">trylock(key [, key2])</function></title>
<para>
Try to lock the key. If the lock can not be obtained (possibly already locked),
the function returns an error and script execution continues.
@@ -519,6 +522,9 @@ lock("$rU");
<quote>key</quote> can be static string or string with PVs.
</para>
<para>
+ <quote>key2</quote> is optional and can be static string or string with PVs.
+ </para>
+ <para>
This function can be used from REQUEST_ROUTE, FAILURE_ROUTE,
ONREPLY_ROUTE, BRANCH_ROUTE and LOCAL_ROUTE.
</para>
@@ -535,7 +541,7 @@ if (trylock("$rU")) {
</example>
</section>
<section id="cfgutils.f.unlock">
- <title><function moreinfo="none">unlock(key)</function></title>
+ <title><function moreinfo="none">unlock(key [, key2])</function></title>
<para>
Unlock the key.
</para>
@@ -543,6 +549,9 @@ if (trylock("$rU")) {
<quote>key</quote> can be static string or string with PVs.
</para>
<para>
+ <quote>key2</quote> is optional and can be static string or string with PVs.
+ </para>
+ <para>
This function can be used from REQUEST_ROUTE, FAILURE_ROUTE,
ONREPLY_ROUTE, BRANCH_ROUTE and LOCAL_ROUTE.
</para>
@@ -854,4 +863,3 @@ if (rand_event()) {
</section>
</section>
</chapter>
-