Module: kamailio
Branch: master
Commit: 335150695507456224c986720682090b2cb757cc
URL: https://github.com/kamailio/kamailio/commit/335150695507456224c986720682090…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2021-03-19T13:16:17+01:00
modules: readme files regenerated - stirshaken ... [skip ci]
---
Modified: src/modules/stirshaken/README
---
Diff: https://github.com/kamailio/kamailio/commit/335150695507456224c986720682090…
Patch: https://github.com/kamailio/kamailio/commit/335150695507456224c986720682090…
---
diff --git a/src/modules/stirshaken/README b/src/modules/stirshaken/README
index c956bdb663..caa3a2e5ec 100644
--- a/src/modules/stirshaken/README
+++ b/src/modules/stirshaken/README
@@ -248,9 +248,10 @@ modparam("stirshaken", "vs_connect_timeout_s", 10)
3.7. vs_cache_certificates (int)
If set, then certificates caching is turned on. This means that
- certificates downloaded during call verification are cached inside
- vs_cache_dir, and will be loaded from that cache as long as they are
- not there for more than vs_cache_expire_s seconds. If
+ certificates downloaded during call verification with
+ stirshaken_check_identity() are cached inside vs_cache_dir, and will be
+ loaded from that cache as long as they are not there for more than
+ vs_cache_expire_s seconds (see vs_cache_expire_s). If
vs_cache_certificates is set then vs_cache_dir must be set too and
pointing to existing directory. This param has no meaning for calls to
stirshaken_check_identity_with_key(key) and
@@ -285,8 +286,12 @@ modparam("stirshaken", "vs_cache_dir", "/tmp/cert_cache")
If vs_cache_certificates is set then cached certificates are saved in
vs_cache_dir directory and loaded from there when needed during a call
verification executed with stirshaken_check_identity(), as long as they
- are not there for more than vs_cache_expire_s seconds. This param has
- no meaning for calls to stirshaken_check_identity_with_key(key) and
+ are not there for more than vs_cache_expire_s seconds. If they are in
+ cache for more than vs_cache_expire_s seconds, then a blocking HTTP(s)
+ call is executed to download a new version of (expired) certificate. If
+ this is successful then old version is removed and new version is saved
+ in cache. This param has no meaning for calls to
+ stirshaken_check_identity_with_key(key) and
stirshaken_check_identity_with_cert(cert).
Default value is 120 seconds.
Module: kamailio
Branch: master
Commit: b5a6e7d7900ab9255ba10bd7aded9e60a9fc3d9e
URL: https://github.com/kamailio/kamailio/commit/b5a6e7d7900ab9255ba10bd7aded9e6…
Author: Piotr Gregor <piotr(a)signalwire.com>
Committer: Piotr Gregor <piotr(a)signalwire.com>
Date: 2021-03-19T12:02:17Z
stirshaken: enhance documentation
---
Modified: src/modules/stirshaken/doc/stirshaken_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/b5a6e7d7900ab9255ba10bd7aded9e6…
Patch: https://github.com/kamailio/kamailio/commit/b5a6e7d7900ab9255ba10bd7aded9e6…
---
diff --git a/src/modules/stirshaken/doc/stirshaken_admin.xml b/src/modules/stirshaken/doc/stirshaken_admin.xml
index b4b5ce1e14..a78eed9050 100644
--- a/src/modules/stirshaken/doc/stirshaken_admin.xml
+++ b/src/modules/stirshaken/doc/stirshaken_admin.xml
@@ -193,8 +193,8 @@ modparam("stirshaken", "vs_connect_timeout_s", 10)
<section>
<title><varname>vs_cache_certificates</varname> (int)</title>
<para>
- If set, then certificates caching is turned on. This means that certificates downloaded during call verification
- are cached inside vs_cache_dir, and will be loaded from that cache as long as they are not there for more than vs_cache_expire_s seconds.
+ If set, then certificates caching is turned on. This means that certificates downloaded during call verification with stirshaken_check_identity()
+ are cached inside vs_cache_dir, and will be loaded from that cache as long as they are not there for more than vs_cache_expire_s seconds (see vs_cache_expire_s).
If vs_cache_certificates is set then vs_cache_dir must be set too and pointing to existing directory.
This param has no meaning for calls to stirshaken_check_identity_with_key(key) and stirshaken_check_identity_with_cert(cert).
</para>
@@ -239,6 +239,8 @@ modparam("stirshaken", "vs_cache_dir", "/tmp/cert_cache")
<para>
If vs_cache_certificates is set then cached certificates are saved in vs_cache_dir directory and loaded from there
when needed during a call verification executed with stirshaken_check_identity(), as long as they are not there for more than vs_cache_expire_s seconds.
+ If they are in cache for more than vs_cache_expire_s seconds, then a blocking HTTP(s) call is executed to download a new version of (expired) certificate.
+ If this is successful then old version is removed and new version is saved in cache.
This param has no meaning for calls to stirshaken_check_identity_with_key(key) and stirshaken_check_identity_with_cert(cert).
</para>
<para>
<!-- 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)
- [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 -->
- [X ] PR should be backported to stable branches
- [X ] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
Now random uuid is generated for empty origid, as stated in documentaion.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2683
-- Commit Summary --
* modules: Add stirshaken module
* stirshaken: add doc
* stirshaken: enhance documentation
* stirshaken: handle NULL or empty origid by generating random uuid
-- File Changes --
A src/modules/stirshaken/Makefile (28)
A src/modules/stirshaken/doc/Makefile (4)
A src/modules/stirshaken/doc/stirshaken.xml (42)
A src/modules/stirshaken/doc/stirshaken_admin.xml (470)
A src/modules/stirshaken/stirshaken_mod.c (981)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2683.patchhttps://github.com/kamailio/kamailio/pull/2683.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/2683
<!-- 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
- [ ] 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 -->
- [X] PR should be backported to stable branches
- [X] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
This module uses libstirshaken to implement STIR-Shaken authentication and verification functions (STI-AS/VS).
It allows for easy verification of a SIP call containing PASSporT wrapped into SIP Identity Header using a specific certificate,
or a specific key, or by performing complete check on PASSporT including downloading certificate referenced in it's x5u header,
and optionally checking it against trusted root certificates (X509 cert path check). Certificates may be cached and loaded from disk.
Example usage:
loadmodule "stirshaken"
modparam("stirshaken", "as_default_key", "/path/to/key")
modparam("stirshaken", "vs_verify_x509_cert_path", 1)
modparam("stirshaken", "vs_ca_dir", "/path/to/ca")
modparam("stirshaken", "vs_cache_certificates", 1)
modparam("stirshaken", "vs_cache_dir", "/tmp/cert_cache")
modparam("stirshaken", "vs_cache_expire_s", 90)
request_route {
(...)
stirshaken_add_identity("https://sp.com/sp.pem".pem", "B", "+44100", "+44200", "ref");
(...)
request_route {
(...)
stirshaken_check_identity();
(...)
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2679
-- Commit Summary --
* modules: Add stirshaken module
-- File Changes --
A src/modules/stirshaken/Makefile (28)
A src/modules/stirshaken/stirshaken_mod.c (972)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2679.patchhttps://github.com/kamailio/kamailio/pull/2679.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/2679
Dear Team,
I am using SBC as proxy server and I am using Freeswitch for providing
RBT/MOH. Please guide how can I play RBT from Freeswitch while using SBC as
proxy server.
Thanks & Regards,
Amit Sharma
(Sr. Team Leader)
(An ISO 9001:2008 company)
Mobile: <tel:9891612004> tel:9891612004
PH: +91 120 2595870
Ext.: <tel:870> tel:870
Email : <mailto:amitsharma@coraltele.com> amitsharma(a)coraltele.com
Web : <blocked::http://www.coraltele.com> www.coraltele.com
Module: kamailio
Branch: master
Commit: 2e8ead7ec434e27a344916ddbf092337e6a0bdb4
URL: https://github.com/kamailio/kamailio/commit/2e8ead7ec434e27a344916ddbf09233…
Author: Piotr Gregor <piotr(a)signalwire.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2021-03-18T08:43:26+01:00
modules: Add stirshaken module
This module uses libstirshaken to implement STIR-Shaken authentication and verification functions (STI-AS/VS).
It allows for easy verification of a SIP call containing PASSporT wrapped into SIP Identity Header using a specific certificate,
or a specific key, or by performing complete check on PASSporT including downloading certificate referenced in it's x5u header,
and optionally checking it against trusted root certificates (X509 cert path check). Certificates may be cached and loaded from disk.
Example usage:
loadmodule "stirshaken"
modparam("stirshaken", "as_default_key", "/path/to/key")
modparam("stirshaken", "vs_verify_x509_cert_path", 1)
modparam("stirshaken", "vs_ca_dir", "/path/to/ca")
modparam("stirshaken", "vs_cache_certificates", 1)
modparam("stirshaken", "vs_cache_dir", "/tmp/cert_cache")
modparam("stirshaken", "vs_cache_expire_s", 90)
request_route {
(...)
stirshaken_add_identity("https://sp.com/sp.pem", "B", "+44100", "+44200", "ref");
(...)
request_route {
(...)
stirshaken_check_identity();
(...)
---
Added: src/modules/stirshaken/Makefile
Added: src/modules/stirshaken/stirshaken_mod.c
---
Diff: https://github.com/kamailio/kamailio/commit/2e8ead7ec434e27a344916ddbf09233…
Patch: https://github.com/kamailio/kamailio/commit/2e8ead7ec434e27a344916ddbf09233…
Hi, I'm using Kamailio version 5.4.0 on centos and I'm using rtjson to redirect SIP Invites. I'm using the JSON example bellow to try to set up the destination. It works fine to redirect the SIP Invite but From/To Headers are not working as expected, they are not changed and remain the same from original INVITE. I also attached my kamailio.cfg file in order for someone to help me here.
JSON Example String: {"version":"1.0","routing":"serial","routes":[{"uri":"sip:3005011999999999@10.20.10.55:5060","dst_uri":"sip:3005011999999999@10.20.10.55:5060","headers":{"from":{"display":"original","uri":"sip:6000@10.20.131.28:5060"},"to":{"display":"","uri":"sip:3005011999999999@10.20.10.55:5060"}}}]}
[kamailio.txt](https://github.com/kamailio/kamailio/files/6151929/kamailio.t…
Has anyone experienced this error?
--
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/2677
<!-- 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 -->
- [ ] PR should be backported to stable branches
- [X] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2681
-- Commit Summary --
* siputils: fix undefined symbol ruri_mark_new
-- File Changes --
M src/modules/siputils/contact_ops.c (1)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2681.patchhttps://github.com/kamailio/kamailio/pull/2681.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/2681
- Validity period is present only for SUBMIT
msg type and it is an optional parameter.
For now supports only Relative VP format.
<!-- 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 -->
- [ ] PR should be backported to stable branches
- [x] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2680
-- Commit Summary --
* smsops: fix parsing of validity period
-- File Changes --
M src/modules/smsops/smsops_impl.c (26)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2680.patchhttps://github.com/kamailio/kamailio/pull/2680.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/2680
Module: kamailio
Branch: master
Commit: 8cab8c2daa0c3f906406741db14df3861bb32cb4
URL: https://github.com/kamailio/kamailio/commit/8cab8c2daa0c3f906406741db14df38…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2021-03-17T11:01:17+01:00
modules: readme files regenerated - lrkproxy ... [skip ci]
---
Modified: src/modules/lrkproxy/README
---
Diff: https://github.com/kamailio/kamailio/commit/8cab8c2daa0c3f906406741db14df38…
Patch: https://github.com/kamailio/kamailio/commit/8cab8c2daa0c3f906406741db14df38…
---
diff --git a/src/modules/lrkproxy/README b/src/modules/lrkproxy/README
index d6b03a6642..b43dd8b16a 100644
--- a/src/modules/lrkproxy/README
+++ b/src/modules/lrkproxy/README
@@ -97,7 +97,7 @@ Chapter 1. Admin Guide
2.1. LRKP_Controlling Layer (LRKP_CL)
- The first layer develope as User-Space application that allows
+ The first layer is developed as User-Space application that allows
User-Space to directly access and manipulate cache data buffer and
packet buffer in Kernel-Space. This layer gets all information about
creating new sessions, active sessions and teardown sessions which is
@@ -106,8 +106,8 @@ Chapter 1. Admin Guide
2.2. LRKP_Transport Stateful Layer (LRKP_TSL)
- The second layer develope in Kernel-Space as a main decision point for
- RTP admission controller and Quickpath selector to where a received
+ The second layer is developed in Kernel-Space as a main decision point
+ for RTP admission controller and Quickpath selector to where a received
packet should be forwarded with power of packet mangling framework in
the network stack.
Module: kamailio
Branch: master
Commit: 81f8833ccbb80e1a4975c2ffaf56dd55fc0d3b54
URL: https://github.com/kamailio/kamailio/commit/81f8833ccbb80e1a4975c2ffaf56dd5…
Author: mojtaba <mespio(a)gmail.com>
Committer: mojtaba <mespio(a)gmail.com>
Date: 2021-03-17T13:30:28+03:30
lrkproxy: update doc/ folder
---
Modified: src/modules/lrkproxy/doc/lrkproxy_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/81f8833ccbb80e1a4975c2ffaf56dd5…
Patch: https://github.com/kamailio/kamailio/commit/81f8833ccbb80e1a4975c2ffaf56dd5…
---
diff --git a/src/modules/lrkproxy/doc/lrkproxy_admin.xml b/src/modules/lrkproxy/doc/lrkproxy_admin.xml
index 1f9eacc534..c826047040 100644
--- a/src/modules/lrkproxy/doc/lrkproxy_admin.xml
+++ b/src/modules/lrkproxy/doc/lrkproxy_admin.xml
@@ -35,7 +35,7 @@
<section>
<title>LRKP_Controlling Layer (LRKP_CL)</title>
<para>
- The first layer develope as User-Space
+ The first layer is developed as User-Space
application that allows User-Space to directly
access and manipulate cache data
buffer and packet buffer in Kernel-Space. This layer
@@ -49,7 +49,7 @@
<section>
<title>LRKP_Transport Stateful Layer (LRKP_TSL)</title>
<para>
- The second layer develope in Kernel-Space as
+ The second layer is developed in Kernel-Space as
a main decision point for RTP admission controller
and Quickpath selector to where a received packet
should be forwarded with power of packet mangling
Module: kamailio
Branch: master
Commit: 91c5626d7119cd9c78028d9b3bf968ecd7db5952
URL: https://github.com/kamailio/kamailio/commit/91c5626d7119cd9c78028d9b3bf968e…
Author: mojtaba <mespio(a)gmail.com>
Committer: mojtaba <mespio(a)gmail.com>
Date: 2021-03-17T12:49:04+03:30
lrkproxy: update doc/ folder for README
---
Modified: src/modules/lrkproxy/doc/lrkproxy_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/91c5626d7119cd9c78028d9b3bf968e…
Patch: https://github.com/kamailio/kamailio/commit/91c5626d7119cd9c78028d9b3bf968e…
---
diff --git a/src/modules/lrkproxy/doc/lrkproxy_admin.xml b/src/modules/lrkproxy/doc/lrkproxy_admin.xml
index 57cc2faab3..1f9eacc534 100644
--- a/src/modules/lrkproxy/doc/lrkproxy_admin.xml
+++ b/src/modules/lrkproxy/doc/lrkproxy_admin.xml
@@ -17,14 +17,16 @@
<section>
<title>Overview</title>
<para>
- This is a module that enables media streams to be relayed via an
- lrkproxy. This module works with py_lrkproxy engine in:
+ This is a module that enables media streams to be relayed via
+ pylrkproxy engine that exist in:
https://github.com/mojtabaesfandiari/pylrkproxy
- This module does relaying audio streams between peers in
+ It does relaying audio streams between peers in
PREROUTING netfilter-hooking section in kernel-space linux.
The LRKProxy architecture is composed of two
different layers. These layers are independent of each
other.
+ For more information about LRKProxy architecture, please visit our paper in ieeexplore:
+ https://ieeexplore.ieee.org/document/9303608
</para>
</section>
@@ -33,12 +35,12 @@
<section>
<title>LRKP_Controlling Layer (LRKP_CL)</title>
<para>
- The first layer is developed as User-Space
+ The first layer develope as User-Space
application that allows User-Space to directly
access and manipulate cache data
buffer and packet buffer in Kernel-Space. This layer
gets all information about creating new sessions,
- active sessions and tear-down sessions which is
+ active sessions and teardown sessions which is
gotten from SDP body during signaling plan and relay
them to the LRKP-Transport Stateful Layer (LRKP-
TSL).
@@ -47,7 +49,7 @@
<section>
<title>LRKP_Transport Stateful Layer (LRKP_TSL)</title>
<para>
- The second layer is developed in Kernel-Space as
+ The second layer develope in Kernel-Space as
a main decision point for RTP admission controller
and Quickpath selector to where a received packet
should be forwarded with power of packet mangling
**Description**
We use below config to test the topology hiding function,when kamailio receive “update” message,doesn't send out,it will send to itself with destination port 5060;
Sorry for raising this question again,I really don’t know what parameters need to be configured。And after I modified some codes, it could succeed probabilistically...
Sorry again, excuse me
**Troubleshooting**
```
loadmodule "ndb_redis.so"
loadmodule "topos_redis.so"
loadmodule "topos.so"
modparam("ndb_redis", "server", "name=srv8;addr=127.0.0.1;port=6381;db=2")
modparam("topos", "storage", "redis")
modparam("topos", "db_url", "redis://127.0.0.1:6381/2")
modparam("topos_redis", "serverid", "srv8")
...Omit the configuration in the middle...
route[WITHINDLG] {
if (has_totag()) {
# sequential request withing a dialog should
# take the path determined by record-routing
xlog("L_INFO","yang yangyang testin to not here");
if (loose_route()){
if(is_method("INFO")){
route("INFO_SELF");
}
route(BYE);
route(REINVITE);
route(ACK);
route(RELAY);
} else {
if ( is_method("ACK")) {
if ( t_check_trans() ) {
# no loose-route, but stateful ACK;
# must be an ACK after a 487
# or e.g. 404 $var(obj) = $sht(call_objects=>$ci);
xlog("L_INFO","Call $ci: ACK received in A-Leg, $fU@$si:$sp -----> $rU@$Ri:$Rp relaying downstreamrouteWITHINDLG\n");
t_relay();
exit;
} else {
exit;
}
}
xlog("L_INFO","yang in to not here");
sl_send_reply("404","Not here");
}
exit;
}
}
```
--------
Call flow
```
UE-----------------PROXY-------------B2bua
invite-------------->|------------------>invite
183<----------------|<------------------183
Prack------------ ->|------------------>Prack
200ok<-------------|<-----------------200ok
update1---------->|
|update2<-----------|
| 404 not here-------> |
````
**Additional Information**
```
version: kamailio master (x86_64/linux)
```
### Possible Solutions
I set the log level to debug, and the comparison found that the logic of prack and update is different。After checking the code of topos, it is found that kamailio/src/modules/topos/tps_msg.c has a separate processing for prack.according to
commit [37830f5](https://github.com/kamailio/kamailio/commit/37830f53b1f21fba5beef5…
So I added update to the prack processing method,Later I found that when the B-side update message comes, it should follow the original logic。
So I distinguish whether to follow the modified logic according to ONREPLY_ROUTE。
But after probabilistic success,The problem is that the value returned by get_route_type() is sometimes 1 and sometimes 4
Call flow after modification:
```
UE-----------------PROXY-------------B2bua
invite-------------->|------------------>invite
183<----------------|<------------------183
Prack------------ ->|------------------>Prack
200ok<-------------|<-----------------200ok
update1---------->|----------------->|update
200ok<-------------|<-----------------200ok
|<-----------------|update2
| 404 not here---------> |
````
Here is the code I modified:
/src/modules/topos/tps_msg.c

--
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/2659
<!-- 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
- [ ] 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 -->
- [ x] PR should be backported to stable branches
- [ x] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
This module uses libstirshaken to implement STIR-Shaken authentication and verification functions (STI-AS/VS).
It allows for easy verification of a SIP call containing PASSporT wrapped into SIP Identity Header using a specific certificate,
or a specific key, or by performing complete check on PASSporT including downloading certificate referenced in it's x5u header,
and optionally checking it against trusted root certificates (X509 cert path check). Certificates may be cached and loaded from disk.
Example usage:
loadmodule "stirshaken"
modparam("stirshaken", "as_default_key", "/path/to/key")
modparam("stirshaken", "vs_verify_x509_cert_path", 1)
modparam("stirshaken", "vs_ca_dir", "/path/to/ca")
modparam("stirshaken", "vs_cache_certificates", 1)
modparam("stirshaken", "vs_cache_dir", "/tmp/cert_cache")
modparam("stirshaken", "vs_cache_expire_s", 90)
request_route {
(...)
stirshaken_add_identity("https://sp.com/sp.pem".pem", "B", "+44100", "+44200", "ref");
(...)
request_route {
(...)
stirshaken_check_identity();
(...)
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2678
-- Commit Summary --
* modules: Add stirshaken module
-- File Changes --
A src/modules/stirshaken/Makefile (28)
A src/modules/stirshaken/stirshaken_mod.c (972)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2678.patchhttps://github.com/kamailio/kamailio/pull/2678.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/2678
Module: kamailio
Branch: master
Commit: 4cf65a7ee1f1803c7c1471f35dcddc8f55c958b1
URL: https://github.com/kamailio/kamailio/commit/4cf65a7ee1f1803c7c1471f35dcddc8…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2021-03-16T13:11:09+01:00
dmq: init internal tcp socket and global cfg structure for worker
---
Modified: src/modules/dmq/dmq.c
Modified: src/modules/dmq/worker.c
---
Diff: https://github.com/kamailio/kamailio/commit/4cf65a7ee1f1803c7c1471f35dcddc8…
Patch: https://github.com/kamailio/kamailio/commit/4cf65a7ee1f1803c7c1471f35dcddc8…
---
diff --git a/src/modules/dmq/dmq.c b/src/modules/dmq/dmq.c
index 4230e48a7f..0a807a983f 100644
--- a/src/modules/dmq/dmq.c
+++ b/src/modules/dmq/dmq.c
@@ -37,6 +37,7 @@
#include "../../core/pt.h"
#include "../../core/hashes.h"
#include "../../core/mod_fix.h"
+#include "../../core/cfg/cfg_struct.h"
#include "../../core/rpc_lookup.h"
#include "../../core/kemi.h"
@@ -299,11 +300,12 @@ static int child_init(int rank)
/* fork worker processes */
for(i = 0; i < dmq_num_workers; i++) {
LM_DBG("starting worker process %d\n", i);
- newpid = fork_process(PROC_RPC, "DMQ WORKER", 0);
+ newpid = fork_process(PROC_RPC, "DMQ WORKER", 1);
if(newpid < 0) {
LM_ERR("failed to fork worker process %d\n", i);
return -1;
} else if(newpid == 0) {
+ if (cfg_child_init()) return -1;
/* child - this will loop forever */
worker_loop(i);
} else {
@@ -327,7 +329,7 @@ static int child_init(int rank)
return 0;
}
if(rank == PROC_TCP_MAIN) {
- /* do nothing for the main process */
+ /* do nothing for the tcp main process */
return 0;
}
diff --git a/src/modules/dmq/worker.c b/src/modules/dmq/worker.c
index 43d76da309..fa4025fff2 100644
--- a/src/modules/dmq/worker.c
+++ b/src/modules/dmq/worker.c
@@ -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
*
*/
@@ -29,6 +29,7 @@
#include "../../core/sip_msg_clone.h"
#include "../../core/parser/parse_from.h"
#include "../../core/parser/parse_to.h"
+#include "../../core/cfg/cfg_struct.h"
/**
* @brief set the body of a response
@@ -88,6 +89,7 @@ void worker_loop(int id)
} else {
sleep_us(dmq_worker_usleep);
}
+ cfg_update();
/* remove from queue until empty */
while(job_queue_size(worker->queue) > 0) {
Hello,
it is the time to plan a bit the road to the next major release, to be
versioned 5.5.0.
The 5.4.0 was release by end of July 2020, therefore we are approaching
the end of our usual development cycle, also during the last online
devel meeting we considered the 2nd part of spring 2021 as a target time
frame for 5.5.
To narrow it down, I would propose to freeze the development at the end
of March 2021, test during April and maybe beginning of May, then
release v5.5.0.
So far we have a lot of development to existing components, by the
freeze date I expect 3-5 new modules to be in the repo as well.
If anyone wants a different time line towards 5.5.0, let's discuss and
choose the one that suits most of the developers.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Funding: https://www.paypal.me/dcmierla
Module: kamailio
Branch: master
Commit: 699d208adcae14565c1af289a9668aede5adaa72
URL: https://github.com/kamailio/kamailio/commit/699d208adcae14565c1af289a9668ae…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2021-03-15T12:29:08+01:00
core: global parameters to enable waiting for child one worker initialization
- new paramters:
- wait_child1_mode=[0|1] - set to wait or not
- wait_child1_time=1000000 (micro-seconds) - how long to wait over all
- wait_child1_usleep=100000 (micro-seconds) - step to wait before
checking if initialization completed
---
Modified: src/core/cfg.lex
Modified: src/core/cfg.y
Modified: src/core/globals.h
Modified: src/core/tcp_main.c
Modified: src/main.c
---
Diff: https://github.com/kamailio/kamailio/commit/699d208adcae14565c1af289a9668ae…
Patch: https://github.com/kamailio/kamailio/commit/699d208adcae14565c1af289a9668ae…
Module: kamailio
Branch: master
Commit: dc6d44b603b126c43757a53560d692e5f5f147a7
URL: https://github.com/kamailio/kamailio/commit/dc6d44b603b126c43757a53560d692e…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2021-03-12T18:15:34+01:00
core: execute event_route[core:worker-one-init] for sctp or tcp
- if no udp worker is started, the event route is executed by next
available transport, in the order: sctp, tcp (or tls)
---
Modified: src/core/tcp_init.h
Modified: src/core/tcp_main.c
Modified: src/main.c
---
Diff: https://github.com/kamailio/kamailio/commit/dc6d44b603b126c43757a53560d692e…
Patch: https://github.com/kamailio/kamailio/commit/dc6d44b603b126c43757a53560d692e…
---
diff --git a/src/core/tcp_init.h b/src/core/tcp_init.h
index ddabbc5fce..70a193a0e2 100644
--- a/src/core/tcp_init.h
+++ b/src/core/tcp_init.h
@@ -13,8 +13,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
*/
@@ -54,7 +54,7 @@ struct tcp_child{
int init_tcp(void);
void destroy_tcp(void);
int tcp_init(struct socket_info* sock_info);
-int tcp_init_children(void);
+int tcp_init_children(int *woneinit);
void tcp_main_loop(void);
void tcp_receive_loop(int unix_sock);
int tcp_fix_child_sockets(int* fd);
diff --git a/src/core/tcp_main.c b/src/core/tcp_main.c
index aecf3a88c1..1fda94ec27 100644
--- a/src/core/tcp_main.c
+++ b/src/core/tcp_main.c
@@ -5034,16 +5034,16 @@ int tcp_fix_child_sockets(int* fd)
/* starts the tcp processes */
-int tcp_init_children()
+int tcp_init_children(int *woneinit)
{
int r, i;
int reader_fd_1; /* for comm. with the tcp children read */
pid_t pid;
char si_desc[MAX_PT_DESC];
struct socket_info *si;
-
+
/* estimate max fd. no:
- * 1 tcp send unix socket/all_proc,
+ * 1 tcp send unix socket/all_proc,
* + 1 udp sock/udp proc + 1 tcp_child sock/tcp child*
* + no_listen_tcp */
for(r=0, si=tcp_listen; si; si=si->next, r++);
@@ -5051,12 +5051,12 @@ int tcp_init_children()
if (! tls_disable)
for (si=tls_listen; si; si=si->next, r++);
#endif
-
+
register_fds(r+tcp_max_connections+get_max_procs()-1 /* tcp main */);
#if 0
tcp_max_fd_no=get_max_procs()*2 +r-1 /* timer */ +3; /* stdin/out/err*/
/* max connections can be temporarily exceeded with estimated_process_count
- * - tcp_main (tcpconn_connect called simultaneously in all all the
+ * - tcp_main (tcpconn_connect called simultaneously in all all the
* processes) */
tcp_max_fd_no+=tcp_max_connections+get_max_procs()-1 /* tcp main */;
#endif
@@ -5095,7 +5095,7 @@ int tcp_init_children()
/* create the tcp sock_info structures */
/* copy the sockets --moved to main_loop*/
-
+
/* fork children & create the socket pairs*/
for(r=0; r<tcp_children_no; r++){
child_rank++;
@@ -5108,10 +5108,16 @@ int tcp_init_children()
goto error;
}else if (pid>0){
/* parent */
+ *woneinit = 1;
}else{
/* child */
bind_address=0; /* force a SEGFAULT if someone uses a non-init.
bind address on tcp */
+ if(*woneinit==0) {
+ if(run_child_one_init_route()<0)
+ goto error;
+ }
+
tcp_receive_loop(reader_fd_1);
}
}
diff --git a/src/main.c b/src/main.c
index 6f8b354d22..e9d66ed449 100644
--- a/src/main.c
+++ b/src/main.c
@@ -1720,8 +1720,14 @@ int main_loop(void)
/* child */
bind_address=si; /* shortcut */
+ if(woneinit==0) {
+ if(run_child_one_init_route()<0)
+ goto error;
+ }
+
return sctp_core_rcv_loop();
}
+ woneinit = 1;
}
/*parent*/
/*close(sctp_sock)*/; /*if closed=>sendto invalid fd errors?*/
@@ -1777,7 +1783,7 @@ int main_loop(void)
#ifdef USE_TCP
if (!tcp_disable){
/* start tcp & tls receivers */
- if (tcp_init_children()<0) goto error;
+ if (tcp_init_children(&woneinit)<0) goto error;
/* start tcp+tls main attendant proc */
pid = fork_process(PROC_TCP_MAIN, "tcp main process", 0);
if (pid<0){
<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for bug reports.
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 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
I've been trying the new in-memory only presence feature in 5.4.x but have run into an issue:
```
ERROR: presence [presence_dmq.c:109]: pres_dmq_init_proc(): dmq_worker_init: database not bound
kamailio[8404]: segfault at 0 ip 00007f4f8419c4d7 sp 00007ffd68ef0130 error 4 in presence.so[7f4f8418d000+fe000]
CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 31
ALERT: <core> [main.c:777]: handle_sigs(): child process 8411 exited by a signal 11
```
I have this set `modparam("presence", "publ_cache", 2)` but had to comment it out in order to prevent kamailio from crashing. I have reverted back to using mysql for storing presentity records for now.
### Troubleshooting
#### Reproduction
Starting kamailio with these mod params can re-produce the issue.
```
#!ifdef WITH_PRESENCE
# ----- presence params -----
modparam("presence", "db_url", DBURL)
modparam("presence", "server_address", "sip:EXTERNAL_LISTEN_IP:EXTERNAL_UDP_PORT")
modparam("presence", "subs_db_mode", 0)
modparam("presence", "publ_cache", 2)
modparam("presence", "clean_period", 40)
modparam("presence", "max_expires", 3600010)
modparam("presence", "enable_dmq", 1)
# ----- presence_xml params -----
modparam("presence_xml", "db_url", DBURL)
modparam("presence_xml", "force_active", 1)
# ----- presence_dialoginfo params -----
modparam("presence_dialoginfo", "force_dummy_dialog", 1)
#!endif
```
#### Debugging Data
<!--
If you got a core dump, use gdb to extract troubleshooting data - full backtrace,
local variables and the list of the code at the issue location.
gdb /path/to/kamailio /path/to/corefile
bt full
info locals
list
If you are familiar with gdb, feel free to attach more of what you consider to
be relevant.
-->
```
(paste your debugging data here)
```
#### Log Messages
<!--
Check the syslog file and if there are relevant log messages printed by Kamailio, add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
```
(paste your log messages here)
```
#### SIP Traffic
<!--
If the issue is exposed by processing specific SIP messages, grab them with ngrep or save in a pcap file, then add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
```
(paste your sip traffic here)
```
### Possible Solutions
<!--
If you found a solution or workaround for the issue, describe it. Ideally, provide a pull request with a fix.
-->
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
version: kamailio 5.4.3 (x86_64/linux) e19ae3
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_BLACKLIST, HAVE_RESOLV_RES
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: e19ae3
compiled on 18:17:25 Dec 14 2020 with gcc 4.8.5
```
* **Operating System**:
<!--
Details about the operating system, the type: Linux (e.g.,: Debian 8.4, Ubuntu 16.04, CentOS 7.1, ...), MacOS, xBSD, Solaris, ...;
Kernel details (output of `uname -a`)
-->
```
CentOS 7 - Linux hostname 3.10.0-1160.2.2.el7.x86_64 #1 SMP Tue Oct 20 16:53:08 UTC 2020 x86_64 x86_64 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/2642
The function lookup_to_dset() is a config command implemented inside the registrar module.
https://github.com/kamailio/kamailio/blob/351efd29d332703e79104a106ade08c9d…
As you can see from the link above, It triggers w_lookup_to_dset() and it ends up calling lookup_helper() with the mode flag set to zero that causes lookup_helper() to not overwrite the request uri (and destination uri if it's the case).
For me it's worth documenting lookup_to_dset() inside modules/registrar/README file, this function it was very useful to me and I found out about it only digging into the code.
Thanks
--
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/2623
Hi all,
I have one question.
What softphones can I use when trying VoLTE (not VoIP) with Kamailio? I would like to verify VoLTE of private LTE with Open5GS and Kamailio.
I'm sorry to ask you a question without much understanding of Kamailio, VoIP and VoLTE.
Thank you very much in advance.
--Shigeru
--
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/2673
### Description
According to the documentation for the UAC module, the `uac_reg` command can accept an optional argument to use the pre-calculated HA1 format:
```
4.7. uac_auth([mode])
This function can be called only from failure route and will build the authentication response header and insert it into the request without sending anything.
If mode is set to 1, then the password has to be provided in HA1 format. The parameter can be a static integer or a variable holding an integer value
```
However, when I attempt to use this in my configuration file, Kamailio fails to start.
### Troubleshooting
#### Reproduction
The problem is reproducible in the 5.4, 5.4-nightly, and dev-nightly debian packages with the following config file:
```
#!KAMAILIO
loadmodule "tm"
loadmodule "sl"
loadmodule "pv"
loadmodule "uac"
loadmodule "rr"
modparam("uac","auth_username_avp","$avp(auser)")
modparam("uac","auth_password_avp","$avp(apass)")
modparam("uac","auth_realm_avp","$avp(arealm)")
request_route {
if( $rm == "INVITE" ) {
t_on_failure("TRUNKAUTH");
}
t_relay();
}
failure_route[TRUNKAUTH] {
$avp(auser) = "user";
$avp(arealm) = "realm";
$avp(apass) = "password";
if (uac_auth(1)) {
t_relay();
}
exit;
}
```
A check on syntax file syntax gives an error of:
```
$ sudo kamailio -eEc
0(18427) ERROR: <core> [core/cfg.y:3451]: yyparse(): cfg. parser: failed to find command uac_auth (params 1)
0(18427) CRITICAL: <core> [core/cfg.y:3592]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 30, column 19: unknown command, missing loadmodule?
ERROR: bad config file (1 errors)
```
No failures are observed if the parameter is removed from line 30. Changed from `if (uac_auth(1)) {` to `if (uac_auth()) {`.
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
version: kamailio 5.4.4 (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_BLACKLIST, 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**:
<!--
Details about the operating system, the type: Linux (e.g.,: Debian 8.4, Ubuntu 16.04, CentOS 7.1, ...), MacOS, xBSD, Solaris, ...;
Kernel details (output of `uname -a`)
-->
```
Linux aarenet-sipdir2 4.19.0-14-cloud-amd64 #1 SMP Debian 4.19.171-2 (2021-01-30) 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/2672
Module: kamailio
Branch: 5.4
Commit: 0ddb019f3d80e4bef2d00a504dbe1baa6b982bba
URL: https://github.com/kamailio/kamailio/commit/0ddb019f3d80e4bef2d00a504dbe1ba…
Author: Victor Seva <vseva(a)sipwise.com>
Committer: Victor Seva <linuxmaniac(a)torreviejawireless.org>
Date: 2021-03-11T13:44:07+01:00
pv_headers: fix detection of split marker
If we set Diversion in split_headers and we get a header like
> "RULTEST, normalaa" <sip:0046341355354340@whatever.net;user=phone>;reason=unconditional
There was false detection of two Diversion headers.
Skip split marker between double quotes to avoid this
(cherry picked from commit c05c7133a5657a547a5b0ced0b0a05707b44bc06)
---
Modified: src/modules/pv_headers/pvh_func.c
Modified: src/modules/pv_headers/pvh_hash.c
Modified: src/modules/pv_headers/pvh_str.c
Modified: src/modules/pv_headers/pvh_str.h
---
Diff: https://github.com/kamailio/kamailio/commit/0ddb019f3d80e4bef2d00a504dbe1ba…
Patch: https://github.com/kamailio/kamailio/commit/0ddb019f3d80e4bef2d00a504dbe1ba…
Module: kamailio
Branch: master
Commit: c05c7133a5657a547a5b0ced0b0a05707b44bc06
URL: https://github.com/kamailio/kamailio/commit/c05c7133a5657a547a5b0ced0b0a057…
Author: Victor Seva <vseva(a)sipwise.com>
Committer: Victor Seva <linuxmaniac(a)torreviejawireless.org>
Date: 2021-03-11T13:41:41+01:00
pv_headers: fix detection of split marker
If we set Diversion in split_headers and we get a header like
> "RULTEST, normalaa" <sip:0046341355354340@whatever.net;user=phone>;reason=unconditional
There was false detection of two Diversion headers.
Skip split marker between double quotes to avoid this
---
Modified: src/modules/pv_headers/pvh_func.c
Modified: src/modules/pv_headers/pvh_hash.c
Modified: src/modules/pv_headers/pvh_str.c
Modified: src/modules/pv_headers/pvh_str.h
---
Diff: https://github.com/kamailio/kamailio/commit/c05c7133a5657a547a5b0ced0b0a057…
Patch: https://github.com/kamailio/kamailio/commit/c05c7133a5657a547a5b0ced0b0a057…
* default behavior of rtpengine is trust-address
* use SIP-source-address for nat_uac_test("8")
<!-- 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 -->
- [ ] Commit message has the format required by CONTRIBUTING guide
- [ ] Commits are split per component (core, individual modules, libs, utils, ...)
- [ ] Each component has a single commit (if not, squash them into one commit)
- [ ] 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)
- [ ] 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
- [ ] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2656
-- Commit Summary --
* kamailio.cfg: use SIP-source-address
-- File Changes --
M etc/kamailio.cfg (4)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2656.patchhttps://github.com/kamailio/kamailio/pull/2656.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/2656
Module: kamailio
Branch: master
Commit: e19cb103fd16b186fed673aae2d04f1abe982110
URL: https://github.com/kamailio/kamailio/commit/e19cb103fd16b186fed673aae2d04f1…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2021-03-11T09:49:45+01:00
jwt: docs - updates for key_mode parameter
---
Modified: src/modules/jwt/doc/jwt_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/e19cb103fd16b186fed673aae2d04f1…
Patch: https://github.com/kamailio/kamailio/commit/e19cb103fd16b186fed673aae2d04f1…
---
diff --git a/src/modules/jwt/doc/jwt_admin.xml b/src/modules/jwt/doc/jwt_admin.xml
index e222e81dc7..dba928b523 100644
--- a/src/modules/jwt/doc/jwt_admin.xml
+++ b/src/modules/jwt/doc/jwt_admin.xml
@@ -60,10 +60,9 @@
<section id="jwt.p.key_mode">
<title><varname>key_mode</varname> (int)</title>
<para>
- Mode to store the private and public keys.
- </para>
- <para>
- Work in progress.
+ Mode to use the private and public keys. If set to 0, they are read
+ always from the disk. If set to 1, they are cached in memory with
+ the first use (no reload support yet).
</para>
<para>
<emphasis>
@@ -74,7 +73,7 @@
<title>Set <varname>key_mode</varname> parameter</title>
<programlisting format="linespecific">
...
-modparam("jwt", "key_mode", 0)
+modparam("jwt", "key_mode", 1)
...
</programlisting>
</example>
- a permanently registered contact has an "expires" value of 0 in usrloc
when processing lookup, cplc module checks that contacts are not expired by
checking that the "expires" value of the contact is not lower than current
time
as a consequence, permanently registered contact are alsways skipped and
never targeted
<!-- 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 -->
- [ ] PR should be backported to stable branches
- [x] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2665
-- Commit Summary --
* cplc: permanent contact not skipped by lookup anymore
-- File Changes --
M src/modules/cplc/cpl_run.c (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2665.patchhttps://github.com/kamailio/kamailio/pull/2665.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/2665
Module: kamailio
Branch: master
Commit: 525ee139abcb45f71bda42b417b5f8e75c12a622
URL: https://github.com/kamailio/kamailio/commit/525ee139abcb45f71bda42b417b5f8e…
Author: easyrider14 <stephane.houssin(a)hotmail.fr>
Committer: easyrider14 <stephane.houssin(a)hotmail.fr>
Date: 2021-03-10T10:54:25+01:00
cplc: permanent contact not skipped by lookup anymore
- a permanently registered contact has an "expires" value of 0 in usrloc
when processing lookup, cplc module checks that contacts are not expired by
checking that the "expires" value of the contact is not lower than current
time
as a consequence, permanently registered contact are alsways skipped and
never targeted
---
Modified: src/modules/cplc/cpl_run.c
---
Diff: https://github.com/kamailio/kamailio/commit/525ee139abcb45f71bda42b417b5f8e…
Patch: https://github.com/kamailio/kamailio/commit/525ee139abcb45f71bda42b417b5f8e…
---
diff --git a/src/modules/cplc/cpl_run.c b/src/modules/cplc/cpl_run.c
index 768f6b3d4a..437e512667 100644
--- a/src/modules/cplc/cpl_run.c
+++ b/src/modules/cplc/cpl_run.c
@@ -283,7 +283,7 @@ static inline char *run_lookup( struct cpl_interpreter *intr )
} else {
contact = r->contacts;
/* skip expired contacts */
- while ((contact) && (contact->expires <= tc))
+ while ((contact) && (contact->expires > 0) && (contact->expires <= tc))
contact = contact->next;
/* any contacts left? */
if (contact) {
I was trying to install kamailio for the first time but I could not activate it.
I follow the steps of this installation https://powerpbx.org/content/kazoo-v4-single-server-install-guide-v1#detail…
The error given was

"Active: failed (Result: exit-code= since Mon 2021-03-08 15:44:55 (code=exited, status=255)"
The work around I found to solve this was to modify this archive vi /etc/kazoo/kamailio/local.cfg
More precisely you need to uncomment some lines and verify the information is right and similar to the one I post here.
In my case the hostname is ServerTest, the IP Address is 192.168.0.123.
################################################################################
## SERVER INFORMATION
################################################################################
## UNCOMMENT & CHANGE "somedomain.local" TO YOUR SERVERS HOSTNAME
**#!substdef "!MY_HOSTNAME!ServerTest.local!g"**
## UNCOMMENT & CHANGE "192.168.88.51" TO YOUR SERVERS IP ADDRESS
## Usually your public IP. If you need
## to listen on addtional ports or IPs
## add them in "BINDINGS" at the bottom.
**#!substdef "!MY_IP_ADDRESS!192.168.0.123!g"**
## CHANGE "kazoo://guest:guest@192.168.88.51:5672" TO THE AMQP URL
## This should be the primary RabbitMQ server
## in the zone that this server will service.
**#!substdef "!MY_AMQP_URL!amqp://guest:guest@192.168.88.51:5672!g"**
--
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/2670
Compiling the new `lrkproxy` module with clang throws the following warning:
```
CC (gcc) [M lrkproxy.so] lrkproxy.o
lrkproxy.c:1228:28: warning: address of array 'e->node->lrkp_n_c->internal_ip' will always evaluate to 'true' [-Wpointer-bool-conversion]
if (e->node->lrkp_n_c->internal_ip && flags) {
~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~ ~~
1 warning generated.
```
Looks like something that needs to be sorted out, comparison with an array address.
--
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/2663
<!-- 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 -->
- [ ] Commit message has the format required by CONTRIBUTING guide
- [ ] Commits are split per component (core, individual modules, libs, utils, ...)
- [ ] Each component has a single commit (if not, squash them into one commit)
- [ ] 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)
- [ ] 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
- [ ] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2666
-- Commit Summary --
* Merge pull request #1 from kamailio/master
* Merge pull request #2 from kamailio/master
* Merge pull request #3 from kamailio/master
* lrkproxy:fix flag parameter in change_media_sdp
* Merge branch 'lrkproxy_warning2663'
-- File Changes --
M src/modules/lrkproxy/lrkproxy.c (15)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2666.patchhttps://github.com/kamailio/kamailio/pull/2666.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/2666
### Description
`dns_int_match_ip` is broken on 5.3.0 and above
### Troubleshooting
#### Reproduction
Try this dialplan:
```
if (dns_int_match_ip('dns.google', '8.8.8.8')) {
xlog("L_INFO", "OK dns-ip match with dns_int_match_ip");
} else {
xlog("L_ERR", "FAIL dns-ip match with dns_int_match_ip");
}
if (dns_int_match_ip('100.100.100.100', '8.8.8.8')) {
xlog("L_ERR", "FAIL dns_int_match_ip on 2 ip's");
} else {
xlog("L_INFO", "OK dns_int_match_ip on 2 ip's");
}
```
On 5.2 releases, both checks succeed. On 5.3 and up, both fail.
#### Debugging Data
I've traced down the problem to `str2ip`.
In 5.2, this is a `static inline` function defined in the header file `resolve.h`. Therefore, the returned `ip` structure is allocated *once per compilation unit* - ie. `ipops_mod.c` and `dns_cache.c` both have their own versions of the variable.
Since fb75e90549a (5.3 and up) this function is defined in it's own compilation unit (`resolve.c`) and therefore shared by all callers.
See: https://stackoverflow.com/questions/185624/static-variables-in-an-inlined-f…
#### Log Messages
n/a
#### SIP Traffic
n/a
### Possible Solutions
- Have `ki_dns_sys_match_ip` make a local copy of the return value of `str2ip`
- Move `str2ip` back to a header file
- Refactor `str2ip` to take a pointer to an output struct
### Additional Information
In 5.3, this is what happens:
```
# - ki_dns_int_match_ip will call str2ip on 8.8.8.8, filling the static variable
# - resolvehost will call dns_a_get_he, which calls str2ip on dns.google.com, zeroing out the static variable
# - (dns_cache_do_request will call str2ip on dns.google.com, zeroing out the static variable again)
# - resolvehost queries DNS
# - the resolved IP's will be compared to the zero'd out struct
dns_int_match_ip('dns.google', '8.8.8.8') == false
# - ki_dns_int_match_ip will call str2ip on 8.8.8.8, filling the static variable
# - resolvehost will call dns_a_get_he, which calls str2ip on 100.100.100.100, overwriting the static variable
# - the static variable will be compared to itself
dns_int_match_ip('100.100.100.100', '8.8.8.8') == true
```
--
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/2645
<!-- 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 -->
- [ ] Commit message has the format required by CONTRIBUTING guide
- [ ] Commits are split per component (core, individual modules, libs, utils, ...)
- [ ] Each component has a single commit (if not, squash them into one commit)
- [ ] 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)
- [ ] 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
- [ ] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2664
-- Commit Summary --
* Merge pull request #1 from kamailio/master
* Merge pull request #2 from kamailio/master
* lrkproxy: lreproxy name is changed
* lrkproxy: add doc/ xml folder
* lrkproxy:some issue related to lrkproxy_manage
-- File Changes --
A src/modules/lrkproxy/Makefile (17)
A src/modules/lrkproxy/doc/Makefile (4)
A src/modules/lrkproxy/doc/lrkproxy.xml (33)
A src/modules/lrkproxy/doc/lrkproxy_admin.xml (364)
A src/modules/lrkproxy/lrkproxy.c (1732)
A src/modules/lrkproxy/lrkproxy.h (107)
A src/modules/lrkproxy/lrkproxy_funcs.c (479)
A src/modules/lrkproxy/lrkproxy_funcs.h (41)
A src/modules/lrkproxy/lrkproxy_hash.c (522)
A src/modules/lrkproxy/lrkproxy_hash.h (75)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2664.patchhttps://github.com/kamailio/kamailio/pull/2664.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/2664
### Description
Hi,
I am migrating from Kamailio 4.4.7 (debian 8.1) to 5.4.3 (debian 10.7).
I changed the neccessary changes in configuration (replaced MI with RPC) and I tried to start the kamailio. The issue is that it takes about 3minutes to start. On the older version 4.4.7 it started aproximetly in 20s.
The modules I am using are:
```
"cfgutils.so","db_mysql.so","kex.so","tm.so","tmx.so","sl.so","rr.so","pv.so","maxfwd.so","textops.so","siputils.so","xlog.so","sanity.so","ctl.so","jsonrpcs.so","exec.so","carrierroute.so","avpops.so","sqlops.so","dmq.so","htable.so","dialog.so","acc.so","acc_radius.so","dispatcher.so","dialplan.so","textopsx.so","statsd.so","app_perl.so","http_async_client.so".
```
I assume the issue is caused by carrierroute module. It takes also about 3 minutes to reload routes (when the kamailio service is running) using rpc command cr.reload_routes.
I did not change anything in configuration related to carrierroute module.
```
modparam("carrierroute", "config_source", "db")
modparam("carrierroute", "db_url", DBURL)
modparam("carrierroute", "match_mode", 128)
modparam("carrierroute", "avoid_failed_destinations", 0)
modparam("carrierroute", "carrierroute_table", "carrierroute_view")
```
Carrierroute module loading on version 4.4.7 needed:
- INFO: carrierroute [cr_db.c:317]: load_route_data_db(): **took 1s**
- INFO: carrierroute [cr_carrier.c:100]: add_domain_data(): and INFO: carrierroute [cr_data.c:414]: get_domain_data_or_add(): **took 8s**
- INFO: carrierroute [cr_data.c:655]: rule_fixup(): **took 3s**
Carrierroute module loading on version 5.4.3 needed:
- INFO: carrierroute [cr_db.c:317]: load_route_data_db(): **took 1s**
- INFO: carrierroute [cr_carrier.c:100]: add_domain_data(): and INFO: carrierroute [cr_data.c:414]: get_domain_data_or_add(): **took 2min 23s**
- INFO: carrierroute [cr_data.c:655]: rule_fixup(): **took 17s**
I have also compiled kamailio version 5.0 on both (debian 8.1 and debian 10.7), but it also took so long to start on both machines.
### Additional Information
```
version: kamailio 5.4.3 (x86_64/linux) 06bd17
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_BLACKLIST, 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: 06bd17
compiled on 16:10:30 Jan 25 2021 with gcc 8.3.0
```
* **Operating System**:
```
Linux 4.19.0-13-amd64 #1 SMP Debian 4.19.160-2 (2020-11-28) x86_64 GNU/Linux
Debian 10.7
```
Thank you for your help.
--
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/2613
Module: kamailio
Branch: master
Commit: b81f7bcf4427b050a52ba20f563e993c9e87c3e0
URL: https://github.com/kamailio/kamailio/commit/b81f7bcf4427b050a52ba20f563e993…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2021-03-09T13:43:28+01:00
uac_redirect: docs - updates for q_value param [skip ci]
---
Modified: src/modules/uac_redirect/doc/uac_redirect_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/b81f7bcf4427b050a52ba20f563e993…
Patch: https://github.com/kamailio/kamailio/commit/b81f7bcf4427b050a52ba20f563e993…
---
diff --git a/src/modules/uac_redirect/doc/uac_redirect_admin.xml b/src/modules/uac_redirect/doc/uac_redirect_admin.xml
index 97cb6414ad..eb66416d05 100644
--- a/src/modules/uac_redirect/doc/uac_redirect_admin.xml
+++ b/src/modules/uac_redirect/doc/uac_redirect_admin.xml
@@ -342,12 +342,12 @@ modparam("uac_redirect","flags_hdr_mode",2)
</example>
</section>
<section>
- <title><varname>default_q_value</varname> (int)</title>
+ <title><varname>q_value</varname> (int)</title>
<para>
Specifies the q-value to asign to contacts without one. Because
Kamailio doesn't support float parameter types, the value in the
parameter is divided by 1000 and stored as float. For example, if
- you want default_q_value to be 0.38, use value 380 here.
+ you want q value to be 0.38, use value 380 here.
</para>
<para>
<emphasis>
@@ -355,10 +355,10 @@ modparam("uac_redirect","flags_hdr_mode",2)
</emphasis>
</para>
<example>
- <title>Set <varname>default_q_value</varname> parameter</title>
+ <title>Set <varname>q_value</varname> parameter</title>
<programlisting format="linespecific">
...
-modparam("uac_redirect","default_q_value",0)
+modparam("uac_redirect","q_value",0)
...
</programlisting>
</example>
The old, quite arbitrary, default of 0.01 is preserved.
<!-- 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
- [ ] 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
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2647
-- Commit Summary --
* uac_redirect: Make default q-value configurable
-- File Changes --
M src/modules/uac_redirect/doc/uac_redirect_admin.xml (19)
M src/modules/uac_redirect/rd_funcs.c (4)
M src/modules/uac_redirect/uac_redirect.c (4)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2647.patchhttps://github.com/kamailio/kamailio/pull/2647.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/2647
<!-- 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 -->
- [ ] Commit message has the format required by CONTRIBUTING guide
- [ ] Commits are split per component (core, individual modules, libs, utils, ...)
- [ ] Each component has a single commit (if not, squash them into one commit)
- [ ] 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)
- [ ] 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
- [ ] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2657
-- Commit Summary --
* Merge pull request #1 from kamailio/master
* Merge pull request #2 from kamailio/master
* lrkproxy: lreproxy name is changed
-- File Changes --
A src/modules/lrkproxy/Makefile (17)
A src/modules/lrkproxy/README (341)
A src/modules/lrkproxy/lrkproxy.c (1738)
A src/modules/lrkproxy/lrkproxy.h (107)
A src/modules/lrkproxy/lrkproxy_funcs.c (479)
A src/modules/lrkproxy/lrkproxy_funcs.h (41)
A src/modules/lrkproxy/lrkproxy_hash.c (522)
A src/modules/lrkproxy/lrkproxy_hash.h (75)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2657.patchhttps://github.com/kamailio/kamailio/pull/2657.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/2657
Module: kamailio
Branch: master
Commit: a31c3c10872780991da9cabbb4ce62fd7fa599da
URL: https://github.com/kamailio/kamailio/commit/a31c3c10872780991da9cabbb4ce62f…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2021-03-09T12:40:16+01:00
lrkproxy: Makefile - removed unnecessary DEFS+=-DKAMAILIO_MOD_INTERFACE
---
Modified: src/modules/lrkproxy/Makefile
---
Diff: https://github.com/kamailio/kamailio/commit/a31c3c10872780991da9cabbb4ce62f…
Patch: https://github.com/kamailio/kamailio/commit/a31c3c10872780991da9cabbb4ce62f…
---
diff --git a/src/modules/lrkproxy/Makefile b/src/modules/lrkproxy/Makefile
index 54159bcebf..9b890a4262 100644
--- a/src/modules/lrkproxy/Makefile
+++ b/src/modules/lrkproxy/Makefile
@@ -2,15 +2,13 @@
# lrkproxy module makefile
#
#
-# WARNING: do not run this directly, it should be run by the master Makefile
+# WARNING: do not run this directly, it should be run by the main Makefile
include ../../Makefile.defs
auto_gen=
NAME=lrkproxy.so
LIBS=
-DEFS+=-DKAMAILIO_MOD_INTERFACE
-
SERLIBPATH=../../lib
#SER_LIBS+=$(SERLIBPATH)/srdb1/srdb1
include ../../Makefile.modules
<!-- 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)
- [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
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
topos_redis: support SUBSCRIBE dialog
topos: SUBSCRIBE dialog
topos: documentation for SUBSCRIBE dialog
topos: add description for dialog_expire key
Add support for dialog subscribe when using topos.
When a Subscribe is received, a Subscribe dialog is created. Dialog TTL is set according to expire received in SIP request.
At each resubscribe the TTL is refresh according to expires set in SIP request.
Notify (in-dialog) with header event set are supposed to be inside a Subscribe dialog.
bugfix:
topos: when contact mode is set to 1, contact uri created is malformed if received contact has no user part
In this case we have a sip uri like : sip:@host
htable: ht_dmq_replicate_action was always called on ht_rm_items even if dmq was not activated
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2662
-- Commit Summary --
* topos: when contact mode is set to 1, contact uri created is malformed if received contact has no user part
* topos_redis: support SUBSCRIBE dialog
* htable: ht_dmq_replicate_action was always called on ht_rm_items even if dmq was not activated
-- File Changes --
M src/modules/htable/htable.c (4)
M src/modules/topos/doc/topos.xml (9)
M src/modules/topos/doc/topos_admin.xml (7)
M src/modules/topos/tps_msg.c (5)
M src/modules/topos/tps_storage.c (41)
M src/modules/topos/tps_storage.h (2)
M src/modules/topos_redis/doc/topos_redis.xml (9)
M src/modules/topos_redis/topos_redis_storage.c (75)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2662.patchhttps://github.com/kamailio/kamailio/pull/2662.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/2662
<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for bug reports.
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 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
<!--
Explain what you did, what you expected to happen, and what actually happened.
-->
Extreme logging introduced in 5.4.4 here:
https://github.com/kamailio/kamailio/blob/2015cfdfd777085dad98a606fc41946af…
and here:
https://github.com/kamailio/kamailio/blob/2015cfdfd777085dad98a606fc41946af…
### Troubleshooting
Logging level for these should be DEBUG?
#### Reproduction
<!--
If the issue can be reproduced, describe how it can be done.
-->
Install Kamailio 5.4.4.
#### Debugging Data
<!--
If you got a core dump, use gdb to extract troubleshooting data - full backtrace,
local variables and the list of the code at the issue location.
gdb /path/to/kamailio /path/to/corefile
bt full
info locals
list
If you are familiar with gdb, feel free to attach more of what you consider to
be relevant.
-->
```
```
#### Log Messages
<!--
Check the syslog file and if there are relevant log messages printed by Kamailio, add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
```
20(70) INFO: ctl [io_listener.c:518]: handle_stream_read(): bytes processed: 29
20(70) INFO: ctl [io_listener.c:498]: handle_stream_read(): bytes read: 35
20(70) INFO: ctl [io_listener.c:518]: handle_stream_read(): bytes processed: 35
20(70) INFO: ctl [io_listener.c:498]: handle_stream_read(): bytes read: 18
20(70) INFO: ctl [io_listener.c:518]: handle_stream_read(): bytes processed: 18
20(70) INFO: ctl [io_listener.c:498]: handle_stream_read(): bytes read: 29
20(70) INFO: ctl [io_listener.c:518]: handle_stream_read(): bytes processed: 29
20(70) INFO: ctl [io_listener.c:498]: handle_stream_read(): bytes read: 29
20(70) INFO: ctl [io_listener.c:518]: handle_stream_read(): bytes processed: 29
```
#### SIP Traffic
<!--
If the issue is exposed by processing specific SIP messages, grab them with ngrep or save in a pcap file, then add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
```
(paste your sip traffic here)
```
### Possible Solutions
<!--
If you found a solution or workaround for the issue, describe it. Ideally, provide a pull request with a fix.
-->
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
version: kamailio 5.4.4 (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_BLACKLIST, 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**:
<!--
Details about the operating system, the type: Linux (e.g.,: Debian 8.4, Ubuntu 16.04, CentOS 7.1, ...), MacOS, xBSD, Solaris, ...;
Kernel details (output of `uname -a`)
-->
```
(paste your output here)
```
--
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/2661
lreproxy: add new lreproxy module
<!-- 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 -->
- [ ] Commit message has the format required by CONTRIBUTING guide
- [ ] Commits are split per component (core, individual modules, libs, utils, ...)
- [ ] Each component has a single commit (if not, squash them into one commit)
- [ ] 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)
- [ ] 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
- [ ] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2208
-- Commit Summary --
* lreproxy module
-- File Changes --
A src/modules/lreproxy/README.md (1)
A src/modules/lreproxy/lreproxy.c (1976)
A src/modules/lreproxy/lreproxy.h (120)
A src/modules/lreproxy/lreproxy_funcs.c (460)
A src/modules/lreproxy/lreproxy_funcs.h (41)
A src/modules/lreproxy/lreproxy_hash.c (521)
A src/modules/lreproxy/lreproxy_hash.h (70)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2208.patchhttps://github.com/kamailio/kamailio/pull/2208.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/2208
<!-- 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, ...)
- [ ] 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
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2649
-- Commit Summary --
* ims_diameter_server: check response is not null before json conversion
* ims_diameter_server: fix initialization of s_message
* ims_diameter_server: drop cdp session to avoid deadlock
* ims_diameter_server: fix check for addAVPsfromJSON return code
-- File Changes --
M src/modules/ims_diameter_server/ims_diameter_server.c (15)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2649.patchhttps://github.com/kamailio/kamailio/pull/2649.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/2649
### Description
ndb_redis is treating MOVED reply from redis cluster as error and breaking out even before the cluster handling code gets a chance to process this.
```
if(rpl->rplRedis->type == REDIS_REPLY_ERROR) {
LM_ERR("Redis error:%.*s\n",
(int)rpl->rplRedis->len, rpl->rplRedis->str);
goto error_exec;
}
if (check_cluster_reply(rpl->rplRedis, &rsrv)) {
...
}
```
### Troubleshooting
#### Reproduction
Setup a redis cluster with at least 2 nodes.
Set modparam cluster=1 and allow_dynamic_nodes=1
fire redis get commands
#### Log Messages
```
ERROR: ndb_redis [redis_client.c:1037]: redisc_exec(): Redis error:MOVED 1090 10.4.20.69:6379
```
### Possible Solutions
revert https://github.com/kamailio/kamailio/commit/d00b14704805d728f5a845a6af900ef…
or
Add another check to ignore the above logic if cluster support is enabled.
or
Do not treat MOVED replies as of type REDIS_REPLY_ERROR
### Additional Information
```
kamailio built from branch 5.4.1
```
--
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/2461
### Description
When using a combination of TopoS+UACreg+Dialog, Kamailio fails to match received replies to a transaction in a dialog.
### Troubleshooting
modparam("topos", "storage", "redis")
modparam("topos", "sanity_checks", 0)
modparam("topos", "contact_mode", 0)
modparam("dialog", "track_cseq_updates", 1)
#### Reproduction
Load Topos + UAC + Dialog modules. Enable dialog cseq tracking.
Add some uacrec record. Register with remote peer.
Make a call towards the remote peer.
INVITE
- Cseq: 1, Branch number: 0. Kamailio will receive a 401 challenge.
- Cseq: 2, Branch number: 1, it will include the Digest auth and try again. . The mangled topos Contact username will be slightly different (supposed to be?)
- Next, the UAS will reply with 100 Trying. In response to that, Kamailio keeps retransmitting the same INVITE with Cseq 2 over and over again, presumably because it fails to match that reply to an existing transaction.
#### Debugging Data
```
DEBUG: {2 2 INVITE a19dfac7c4a65} tm [t_lookup.c:1009]: t_reply_matching(): failure to match a transaction
```
#### Log Messages
<!--
Check the syslog file and if there are relevant log messages printed by Kamailio, add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
```
(paste your log messages here)
```
#### SIP Traffic
<!--
If the issue is exposed by processing specific SIP messages, grab them with ngrep or save in a pcap file, then add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
```
2021/02/26 12:10:16.213947 10.10.10.2:5060 -> 10.10.10.1:5060
INVITE sip:8882223333@mypbx.mydomain.net SIP/2.0
Via: SIP/2.0/UDP mysbc.mydomain.com:5060;branch=z9hG4bK4f81.97f17905fe7afced720300fea57ef462.0;i=6a
FROM: Demo Five<sip:2385@mypbx.mydomain.net>;tag=29e99c29147f425f914b73512fc13cf3
TO: <sip:8882223333@mypbx.mydomain.net>
CSEQ: 1 INVITE
CALL-ID: 33c9034c136e57de9c1278daef7d02fb
MAX-FORWARDS: 69
CONTENT-LENGTH: 575
MIN-SE: 300
SUPPORTED: timer
USER-AGENT: UA
CONTENT-TYPE: application/sdp
ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY
SESSION-EXPIRES: 3600
Contact: <sip:btpsh-603922bd-3db9-1@mysbc.mydomain.com:5060>
2021/02/26 12:10:16.215650 10.10.10.1:5060 -> 10.10.10.2:5060
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP mysbc.mydomain.com:5060;branch=z9hG4bK4f81.97f17905fe7afced720300fea57ef462.0;i=6a;received=10.10.10.2;rport=5060
From: Demo Five<sip:2385@mypbx.mydomain.net>;tag=29e99c29147f425f914b73512fc13cf3
To: <sip:8882223333@mypbx.mydomain.net>;tag=as7c952f5b
Call-ID: 33c9034c136e57de9c1278daef7d02fb
CSeq: 1 INVITE
Server: B2B
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer, path
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="4f8fcced"
Content-Length: 0
2021/02/26 12:10:16.238191 10.10.10.2:5060 -> 10.10.10.1:5060
ACK sip:8882223333@mypbx.mydomain.net SIP/2.0
FROM: Demo Five<sip:2385@mypbx.mydomain.net>;tag=29e99c29147f425f914b73512fc13cf3
To: <sip:8882223333@mypbx.mydomain.net>;tag=as7c952f5b
CSEQ: 1 ACK
CALL-ID: 33c9034c136e57de9c1278daef7d02fb
MAX-FORWARDS: 69
Via: SIP/2.0/UDP mysbc.mydomain.com:5060;branch=z9hG4bK4f81.97f17905fe7afced720300fea57ef462.0;i=6a
CONTENT-LENGTH: 0
2021/02/26 12:10:16.280455 10.10.10.2:5060 -> 10.10.10.1:5060
INVITE sip:8882223333@mypbx.mydomain.net SIP/2.0
Via: SIP/2.0/UDP mysbc.mydomain.com:5060;branch=z9hG4bK4f81.97f17905fe7afced720300fea57ef462.1.cs1;i=6a
FROM: Demo Five<sip:2385@mypbx.mydomain.net>;tag=29e99c29147f425f914b73512fc13cf3
TO: <sip:8882223333@mypbx.mydomain.net>
CSEQ: 2 INVITE
CALL-ID: 33c9034c136e57de9c1278daef7d02fb
MAX-FORWARDS: 69
CONTENT-LENGTH: 575
MIN-SE: 300
SUPPORTED: timer
USER-AGENT: UA
CONTENT-TYPE: application/sdp
ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY
SESSION-EXPIRES: 3600
Authorization: Digest username="2385", realm="asterisk", nonce="4f8fcced", uri="sip:8882223333@mypbx.mydomain.net", response="ec1986d94b9a508c4e9761c3c1cb80eb", algorithm=MD5
Contact: <sip:btpsh-603922bd-3db0-4@mysbc.mydomain.com:5060>
2021/02/26 12:10:16.284672 10.10.10.1:5060 -> 10.10.10.2:5060
SIP/2.0 100 Trying
Via: SIP/2.0/UDP mysbc.mydomain.com:5060;branch=z9hG4bK4f81.97f17905fe7afced720300fea57ef462.1.cs1;i=6a;received=10.10.10.2;rport=5060
From: Demo Five<sip:2385@mypbx.mydomain.net>;tag=29e99c29147f425f914b73512fc13cf3
To: <sip:8882223333@mypbx.mydomain.net>
Call-ID: 33c9034c136e57de9c1278daef7d02fb
CSeq: 2 INVITE
Server: B2B
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer, path
Session-Expires: 900;refresher=uas
Contact: <sip:8882223333@10.10.10.1:5060>
Content-Length: 0
2021/02/26 12:10:16.745320 10.10.10.2:5060 -> 10.10.10.1:5060
INVITE sip:8882223333@mypbx.mydomain.net SIP/2.0
Via: SIP/2.0/UDP mysbc.mydomain.com:5060;branch=z9hG4bK4f81.97f17905fe7afced720300fea57ef462.1.cs1;i=6a
FROM: Demo Five<sip:2385@mypbx.mydomain.net>;tag=29e99c29147f425f914b73512fc13cf3
TO: <sip:8882223333@mypbx.mydomain.net>
CSEQ: 2 INVITE
CALL-ID: 33c9034c136e57de9c1278daef7d02fb
MAX-FORWARDS: 69
CONTENT-LENGTH: 575
MIN-SE: 300
SUPPORTED: timer
USER-AGENT: UA
CONTENT-TYPE: application/sdp
ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY
SESSION-EXPIRES: 3600
Authorization: Digest username="2385", realm="asterisk", nonce="4f8fcced", uri="sip:8882223333@mypbx.mydomain.net", response="ec1986d94b9a508c4e9761c3c1cb80eb", algorithm=MD5
Contact: <sip:btpsh-603922bd-3db0-4@mysbc.mydomain.com:5060>
```
### Possible Solutions
<!--
If you found a solution or workaround for the issue, describe it. Ideally, provide a pull request with a fix.
-->
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
version: kamailio 5.5.0-dev4 (x86_64/linux) 5ad3bd
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
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: 5ad3bd
compiled on 15:35:01 Feb 11 2021 with gcc 4.9.2
```
* **Operating System**:
<!--
Details about the operating system, the type: Linux (e.g.,: Debian 8.4, Ubuntu 16.04, CentOS 7.1, ...), MacOS, xBSD, Solaris, ...;
Kernel details (output of `uname -a`)
-->
```
Debian GNU/Linux 8 (jessie)
```
--
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/2654
### Description
I have created a broken config with construction
```
if (is_request()) {
}
```
When I try to check config I get the core
```
0(66437) CRITICAL: <core> [core/cfg.y:3665]: yyerror_at(): parse error in config file proxy-media.cfg, line 18, column 5: syntax error
0(66437) CRITICAL: <core> [core/cfg.y:3665]: yyerror_at(): parse error in config file proxy-media.cfg, line 18, column 5: bad command
0(66437) CRITICAL: <core> [core/cfg.y:3662]: yyerror_at(): parse error in config file proxy-media.cfg, line 20, column 5-6:
ERROR: bad config file (3 errors) (parsing code: 1)
0(66437) ERROR: <core> [core/ppcfg.c:243]: pp_ifdef_level_error(): different number of preprocessor directives: 1 more #!if[n]def as #!endif
0(66437) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
Program received signal SIGSEGV, Segmentation fault.
0x00007fffee8589ca in BN_clear_free () from /lib64/libcrypto.so.1.1
Missing separate debuginfos, use: yum debuginfo-install brotli-1.0.6-2.el8.x86_64 cyrus-sasl-lib-2.1.27-5.el8.x86_64 hiredis-0.13.3-13.el8.x86_64 jansson-2.11-3.el8.x86_64 keyutils-libs-1.5.10-6.el8.x86_64 krb5-libs-1.18.2-5.el8.x86_64 libcom_err-1.45.6-1.el8.x86_64 libcurl-7.61.1-14.el8.x86_64 libidn2-2.2.0-1.el8.x86_64 libnghttp2-1.33.0-3.el8_2.1.x86_64 libpsl-0.20.2-6.el8.x86_64 libselinux-2.9-4.el8_3.x86_64 libssh-0.9.4-2.el8.x86_64 libunistring-0.9.9-3.el8.x86_64 libxcrypt-4.1.1-4.el8.x86_64 libxml2-2.9.7-8.el8.x86_64 openldap-2.4.46-15.el8.x86_64 openssl-libs-1.1.1g-11.el8.x86_64 pcre2-10.32-2.el8.x86_64 xz-libs-5.2.4-3.el8.x86_64 zlib-1.2.11-16.el8_2.x86_64
(gdb) bt full
#0 0x00007fffee8589ca in BN_clear_free () from /lib64/libcrypto.so.1.1
No symbol table info available.
#1 0x00007fffecec5825 in ssh_dh_finalize.part () from /lib64/libssh.so.4
No symbol table info available.
#2 0x00007fffeceb6e4d in libssh_destructor () from /lib64/libssh.so.4
No symbol table info available.
#3 0x00007ffff7de4386 in _dl_fini () from /lib64/ld-linux-x86-64.so.2
No symbol table info available.
#4 0x00007ffff708df8c in __run_exit_handlers () from /lib64/libc.so.6
No symbol table info available.
#5 0x00007ffff708e0c0 in exit () from /lib64/libc.so.6
No symbol table info available.
#6 0x00007ffff70777ba in __libc_start_main () from /lib64/libc.so.6
No symbol table info available.
#7 0x000000000041c39e in _start ()
No symbol table info available.
(gdb)
```
On host installed
```
[root@bcf-a0 config]# rpm -qf /lib64/libcrypto.so.1.1
openssl-libs-1.1.1g-11.el8.x86_64
```
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
[root@bcf-a0 config]# kamailio -v
version: kamailio 5.5.0-dev3 (x86_64/linux) aff06f
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: aff06f
compiled on 04:01:30 Jan 7 2021 with gcc 8.3.1
```
* **Operating System**:
```
[root@host ~]# cat /etc/os-release
NAME="CentOS Linux"
VERSION="8"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="8"
PLATFORM_ID="platform:el8"
PRETTY_NAME="CentOS Linux 8"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:8"
HOME_URL="https://centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"
CENTOS_MANTISBT_PROJECT="CentOS-8"
CENTOS_MANTISBT_PROJECT_VERSION="8"
```
--
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/2599
Module: kamailio
Branch: 5.4
Commit: c9a46eb88365add327b5d6f11f121c26a6230e58
URL: https://github.com/kamailio/kamailio/commit/c9a46eb88365add327b5d6f11f121c2…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2021-03-01T18:31:49+01:00
ims_qos: typos in comments
(cherry picked from commit f9c336aa9a78169cf9c7f3fd9bfcfd22218078fb)
---
Modified: src/modules/ims_qos/ims_qos_mod.c
Modified: src/modules/ims_qos/rx_aar.c
---
Diff: https://github.com/kamailio/kamailio/commit/c9a46eb88365add327b5d6f11f121c2…
Patch: https://github.com/kamailio/kamailio/commit/c9a46eb88365add327b5d6f11f121c2…
---
diff --git a/src/modules/ims_qos/ims_qos_mod.c b/src/modules/ims_qos/ims_qos_mod.c
index e58dd2c140..a49ee1bd90 100644
--- a/src/modules/ims_qos/ims_qos_mod.c
+++ b/src/modules/ims_qos/ims_qos_mod.c
@@ -597,7 +597,7 @@ void callback_pcscf_contact_cb(struct pcontact *c, int type, void *param)
if (type == PCSCF_CONTACT_EXPIRE || type == PCSCF_CONTACT_DELETE) {
- //we dont need to send STR if no QoS was ever succesfully registered!
+ // we dont need to send STR if no QoS was ever successfully registered!
if (must_send_str && (c->reg_state != PCONTACT_REG_PENDING) && (c->reg_state != PCONTACT_REG_PENDING_AAR)) {
LM_DBG("Received notification of contact (in state [%d] deleted for signalling bearer with with Rx session ID: [%.*s]\n",
c->reg_state, c->rx_session_id.len, c->rx_session_id.s);
diff --git a/src/modules/ims_qos/rx_aar.c b/src/modules/ims_qos/rx_aar.c
index d9f242f43b..756ed2a663 100644
--- a/src/modules/ims_qos/rx_aar.c
+++ b/src/modules/ims_qos/rx_aar.c
@@ -328,7 +328,8 @@ void async_aar_reg_callback(int is_timeout, void *param, AAAMessage *aaa, long e
}
//at this point we have the contact
- /*set the contact state to say we have succesfully done ARR for register and that we dont need to do it again
+ /*set the contact state to say we have successfully done ARR for register
+ * and that we dont need to do it again
* for the duration of the registration.
* */
if (ul.update_rx_regsession(domain_t, &local_data->auth_session_id, pcontact) != 0) {
### Description
I want to be sure my customization does not produce memory leack.
To get this work I want to use the ASAN project.
Could you add `mode=asan` build option that adds gcc ` -fsanitize=address -static-libasan` options `-lasan` linker flags.
More info
https://www.osc.edu/resources/getting_started/howto/howto_use_address_sanit…
Maybe important.
ASAN expects linked first
```
[root@b276215a3a22 kamailio]# kamailio -DD -E
==13760==ASan runtime does not come first in initial library list; you should either link runtime to your application or manually preload it with LD_PRELOAD.
```
--
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/2650
Dear all
we have been testing this module with the following setup
kamailio 5.3.2
evapi params
modparam("evapi", "workers", 4)
modparam("evapi", "netstring_format", 0)
modparam("evapi", "bind_addr", "127.0.0.1:8448")
modparam("evapi", "max_clients", 32)
then in the configuration we do evapi_relay of avp including a json data
(which can be quite long), like this
{"key" : "aarp2q0tcpqhs0cpucuhukjs2ah2j00q(a)10.18.5.64" , "msg" :
{"rg_in":"701","ani_init":{"ani_source":"pai", ....... }}}
We have an application listening on the tcp socket and writing those
messages to a kafka cluster, and this works ok, and in the previous manual
tests we have done no issue was found.
But when making some load tests, and passing some live traffic we see some
issues
seems like some times, when there are messages to be sent to the tcp socket
at the same time, they are sent in the same message, when normally each
data sent using evapi_relay is sent in 1 message
We do sometimes see something like this on the application consuming from
the tcp socket
2020-11-25 15:20:01.744 UTC [error]
<0.706.0>@evapi_kafka_listener:handle_info:167 body "{\"key\" : \"
6142651aa63616c6c04a783cd(a)72.21.24.130\" , \"msg\" :
{\"rg_in\":\"677\",\"ani_init\":{\"ani_source\":\"fro\",.......}}}{\"key\"
: \"isbc7caT4001915251VabcGhEfHdNiF0i(a)172.16.120.1\" , \"msg\" :
{\"rg_in\":\"22\",\"ani_init\":{\"ani_source\":\"pai\", .......
,\"translate" not valid json; error = {691,invalid_trailing_data}
2020-11-25 15:20:01.745 UTC [error]
<0.706.0>@evapi_kafka_listener:handle_info:167 body
"dPartition\":\"-1\",......}}}" not valid json; error = {1,invalid_json}
and we do see that the application cannot parse the json message fine,
because we have like 2 json objects together
......{\"ani_source\":\"fro\",.......}}}{\"key\" :
\"isbc7caT4001915251Vabc............
This happens with 2 different UDP receivers processing messages and calling
evapi_relay at the same time. But i don't think this happens all the time.
Seems like some issue when several processes try to use evapi workers at
the same time.
We tried to increase evapi workers and it's the same
We also saw another issue I think. Seems when the avp sent to evapi socket
is bigger than ~1680 char, the json is also truncated, and also happens
when we use the socket in Lo interface which has an MTU of 65535.
Could you please take a look to see if there is any problem or limitation,
or if we are using something wrong?
thanks and best regards
david
--
[image: Logo]
David Escartín Almudévar
VoIP/Switch Engineer
descartin(a)sonoc.io
*SONOC*
C/ Josefa Amar y Borbón, 10, 4ª · 50001 Zaragoza, España
Tlf: +34 917019888 · www.sonoc.io