<!-- 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