Module: kamailio
Branch: master
Commit: e49d77af246c52591e76cfdcf0d59970d7349e7e
URL: https://github.com/kamailio/kamailio/commit/e49d77af246c52591e76cfdcf0d5997…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2025-07-23T19:46:09+02:00
modules: readme files regenerated - topos ... [skip ci]
---
Modified: src/modules/topos/README
---
Diff: https://github.com/kamailio/kamailio/commit/e49d77af246c52591e76cfdcf0d5997…
Patch: https://github.com/kamailio/kamailio/commit/e49d77af246c52591e76cfdcf0d5997…
---
diff --git a/src/modules/topos/README b/src/modules/topos/README
index 60a06f6b705..3f4d931cf26 100644
--- a/src/modules/topos/README
+++ b/src/modules/topos/README
@@ -573,11 +573,14 @@ request_route {
It is executed before doing topology stripping processing for an
outgoing SIP message. If 'drop' is executed inside the event route,
- then the module skips doing the out part of topology hiding.
+ then the module skips doing the outbound part of topology stripping.
- Only fake msg is available in this event route. Inside the event route
- the variables $sndto(ip), $sndto(port) and $sndto(proto) point to the
- destination.
+ The event route is executed with an internal fake SIP message for the
+ purpose of performace (i.e., no parsing of the outgoing message is
+ done), therefore the R-URI, headers and body do not reflect the content
+ of the outgoing message. However, inside the event route the variables
+ $sndto(ip), $sndto(port) and $sndto(proto) point to the real
+ destination of the SIP message.
Example 1.24. Usage of event_route[topos:msg-outgoing]
...
@@ -593,11 +596,14 @@ event_route[topos:msg-outgoing] {
It is executed before doing topology stripping processing for a SIP
message to be sent out, being executed after
event_route[topos:msg-outgoing]. If 'drop' is executed inside the event
- route, then the module skips doing the out part of topology hiding.
+ route, then the module skips doing the outbound part of topology
+ stripping.
- A copy of the SIP msg to be sent out is available in this event route.
- Inside the event route the variables $sndto(ip), $sndto(port) and
- $sndto(proto) point to the destination.
+ A copy of the SIP message to be sent out is made available in this
+ event route, thefore the R-URI, headers and body reflect the content of
+ the outgoing SIP message. Inside the event route the variables
+ $sndto(ip), $sndto(port) and $sndto(proto) point to the real
+ destination of the SIP message.
Example 1.25. Usage of event_route[topos:msg-sending]
...
@@ -612,10 +618,14 @@ event_route[topos:msg-sending] {
It is executed before doing topology stripping processing for an
incoming SIP message. If 'drop' is executed inside this event route,
- then the module skips doing the in part of topology hiding.
+ then the module skips doing the inbound part of topology stripping.
- Only fake msg is available in this event route. $si, $sp and $proto
- will have default fake values.
+ The event route is executed with an internal fake SIP message for the
+ purpose of performace (i.e., no parsing of the incoming message is
+ done), therefore the R-URI, headers and body do not reflect the content
+ of the incoming message. However, inside the event route the variables
+ $si, $sp and $proto point to the real source address of the SIP
+ message, as well as the keywords src_port and dst_port.
Example 1.26. Usage of event_route[topos:msg-incoming]
...
@@ -631,11 +641,13 @@ event_route[topos:msg-incoming] {
It is executed before doing topology stripping processing for a SIP
message that was received, being executed after
event_route[topos:msg-incoing]. If 'drop' is executed inside this event
- route, then the module skips doing the in part of topology hiding.
+ route, then the module skips doing the inbound part of topology hiding.
- A copy of the received SIP msg is available in this event route. $si,
- $sp and $proto will have correct, expected values. Also src_port and
- dst_port can be used here.
+ A copy of the incoming SIP message is made available in this event
+ route, thefore the R-URI, headers and body reflect the content of the
+ incoming SIP message. Inside the event route the variables $si, $sp and
+ $proto point to the real source address of the SIP message, as well as
+ the keywords src_port and dst_port.
Example 1.27. Usage of event_route[topos:msg-receiving]
...
Module: kamailio
Branch: master
Commit: a9d6658862a5d266853456e5201e6e08b7c81de5
URL: https://github.com/kamailio/kamailio/commit/a9d6658862a5d266853456e5201e6e0…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2025-07-23T19:01:10+02:00
modules: readme files regenerated - topos ... [skip ci]
---
Modified: src/modules/topos/README
---
Diff: https://github.com/kamailio/kamailio/commit/a9d6658862a5d266853456e5201e6e0…
Patch: https://github.com/kamailio/kamailio/commit/a9d6658862a5d266853456e5201e6e0…
---
diff --git a/src/modules/topos/README b/src/modules/topos/README
index 9c82ff026e1..60a06f6b705 100644
--- a/src/modules/topos/README
+++ b/src/modules/topos/README
@@ -573,13 +573,11 @@ request_route {
It is executed before doing topology stripping processing for an
outgoing SIP message. If 'drop' is executed inside the event route,
- then the module skips doing the topology hiding.
+ then the module skips doing the out part of topology hiding.
- Inside the event route the variables $sndto(ip), $sndto(port) and
- $sndto(proto) point to the destination. The SIP message is not the one
- to be sent out, but an internally generated one at startup, to avoid
- reparsing the outgoing SIP message for the cases when topology hiding
- is not wanted.
+ Only fake msg is available in this event route. Inside the event route
+ the variables $sndto(ip), $sndto(port) and $sndto(proto) point to the
+ destination.
Example 1.24. Usage of event_route[topos:msg-outgoing]
...
@@ -594,11 +592,12 @@ event_route[topos:msg-outgoing] {
It is executed before doing topology stripping processing for a SIP
message to be sent out, being executed after
- event_route[topos:msg-outgoing].
+ event_route[topos:msg-outgoing]. If 'drop' is executed inside the event
+ route, then the module skips doing the out part of topology hiding.
+ A copy of the SIP msg to be sent out is available in this event route.
Inside the event route the variables $sndto(ip), $sndto(port) and
- $sndto(proto) point to the destination. The SIP message is the one to
- be sent out.
+ $sndto(proto) point to the destination.
Example 1.25. Usage of event_route[topos:msg-sending]
...
@@ -612,13 +611,11 @@ event_route[topos:msg-sending] {
5.3. event_route[topos:msg-incoming]
It is executed before doing topology stripping processing for an
- incoming SIP message. If 'drop' is executed inside the event route,
- then the module skips doing the topology hiding.
+ incoming SIP message. If 'drop' is executed inside this event route,
+ then the module skips doing the in part of topology hiding.
- Inside the event route the variables $si, $sp and $proto point to the
- source address. The SIP message is not the one to be sent out, but an
- internally generated one at startup, to avoid reparsing the outgoing
- SIP message for the cases when topology hiding is not wanted.
+ Only fake msg is available in this event route. $si, $sp and $proto
+ will have default fake values.
Example 1.26. Usage of event_route[topos:msg-incoming]
...
@@ -633,10 +630,12 @@ event_route[topos:msg-incoming] {
It is executed before doing topology stripping processing for a SIP
message that was received, being executed after
- event_route[topos:msg-incoing].
+ event_route[topos:msg-incoing]. If 'drop' is executed inside this event
+ route, then the module skips doing the in part of topology hiding.
- Inside the event route the variables $si, $sp and $proto point to the
- source address. The SIP message is the one to be sent out.
+ A copy of the received SIP msg is available in this event route. $si,
+ $sp and $proto will have correct, expected values. Also src_port and
+ dst_port can be used here.
Example 1.27. Usage of event_route[topos:msg-receiving]
...
@@ -644,5 +643,13 @@ event_route[topos:msg-receiving] {
if(is_request() and $fU=="alice") {
drop;
}
+
+ if($sp==5555 || $si=="1.2.3.4") {
+ drop;
+ }
+
+ if(src_port==1234 || dst_port==5678) {
+ drop;
+ }
}
...
Updated documentation.
<!-- 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 -->
Right now if I try to log $sp in event_route[topos:msg-receiving], will have value 0.
Updated documentation too, related to those event routes.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/4329
-- Commit Summary --
* topos: expose rcv data in event routes
-- File Changes --
M src/modules/topos/doc/topos_admin.xml (41)
M src/modules/topos/topos_mod.c (6)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/4329.patchhttps://github.com/kamailio/kamailio/pull/4329.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/4329
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/4329(a)github.com>
<!-- 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
- [x] Related to issue https://kamailio.org/mailman3/hyperkitty/list/sr-users@lists.kamailio.org/t…
#### Description
<!-- Describe your changes in detail -->
This PR fixes the bug when failing to parse a URN scheme with a '@' character in the host name.
- Format of file
- Add some comments on magic numbers
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/4336
-- Commit Summary --
* core: Fix urn parsing failing if @ is present
* core: add some comment on the hardcoded numbers
-- File Changes --
M src/core/parser/parse_uri.c (24)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/4336.patchhttps://github.com/kamailio/kamailio/pull/4336.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/4336
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/4336(a)github.com>