Module: kamailio
Branch: master
Commit: 901d2c8c34c1585531808d3ebcbd6788fa40ae8c
URL: https://github.com/kamailio/kamailio/commit/901d2c8c34c1585531808d3ebcbd678…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2018-08-14T10:02:13+02:00
modules: readme files regenerated - topos ... [skip ci]
---
Modified: src/modules/topos/README
---
Diff: https://github.com/kamailio/kamailio/commit/901d2c8c34c1585531808d3ebcbd678…
Patch: https://github.com/kamailio/kamailio/commit/901d2c8c34c1585531808d3ebcbd678…
---
diff --git a/src/modules/topos/README b/src/modules/topos/README
index de5363ea56..e745e4b9cf 100644
--- a/src/modules/topos/README
+++ b/src/modules/topos/README
@@ -34,6 +34,7 @@ Daniel-Constantin Mierla
3.7. clean_interval (int)
3.8. event_callback (str)
3.9. event_mode (int)
+ 3.10. contact_host (str)
4. Event Routes
@@ -51,8 +52,9 @@ Daniel-Constantin Mierla
1.7. Set clean_interval parameter
1.8. Set event_callback parameter
1.9. Set event_mode parameter
- 1.10. Usage of event_route[topos:msg-outgoing]
- 1.11. Usage of event_route[topos:msg-sending]
+ 1.10. Set contact_host parameter
+ 1.11. Usage of event_route[topos:msg-outgoing]
+ 1.12. Usage of event_route[topos:msg-sending]
Chapter 1. Admin Guide
@@ -75,6 +77,7 @@ Chapter 1. Admin Guide
3.7. clean_interval (int)
3.8. event_callback (str)
3.9. event_mode (int)
+ 3.10. contact_host (str)
4. Event Routes
@@ -126,6 +129,7 @@ Chapter 1. Admin Guide
3.7. clean_interval (int)
3.8. event_callback (str)
3.9. event_mode (int)
+ 3.10. contact_host (str)
3.1. storage (str)
@@ -247,6 +251,21 @@ end
modparam("topos", "event_mode", 2)
...
+3.10. contact_host (str)
+
+ You may need to control the host part of the Contact header added by
+ topos. For example when using TLS with TOPOS the remote UAS must be
+ able to open a new TLS socket to the contact header. In this case, the
+ contact header must contain a domain name with a trusted CA signed
+ certitificate.
+
+ Default value is taken from the Record-Route URI.
+
+ Example 1.10. Set contact_host parameter
+...
+modparam("topos", "contact_host", "proxy.domain.com")
+...
+
4. Event Routes
4.1. event_route[topos:msg-outgoing]
@@ -264,7 +283,7 @@ modparam("topos", "event_mode", 2)
reparsing the outgoing SIP message for the cases when topology hiding
is not wanted.
- Example 1.10. Usage of event_route[topos:msg-outgoing]
+ Example 1.11. Usage of event_route[topos:msg-outgoing]
...
event_route[topos:msg-outgoing] {
if($sndto(ip)=="10.1.1.10") {
@@ -283,7 +302,7 @@ event_route[topos:msg-outgoing] {
$sndto(proto) point to the destination. The SIP message is the one to
be sent out.
- Example 1.11. Usage of event_route[topos:msg-sending]
+ Example 1.12. Usage of event_route[topos:msg-sending]
...
event_route[topos:msg-sending] {
if(is_request() and $fU=="alice") {
<!-- 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 -->
When using TLS with TOPOS the remote UAS could open a new TLS socket to the contact header.
The contact header must contain a domain name with a signed certitificate.
Adding the parameter to TOPOS module to control the host part of the contact headers
```
modparam("topos", "contact_hostname", "proxy.domain.com")
```
Default behavior is left unchanged
I will update documentation it his modification is confirmed to be valuable.
Else I would be curious to know how this should be handled differently.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/1596
-- Commit Summary --
* topos: adding param contact_hostname
-- File Changes --
M src/modules/topos/topos_mod.c (2)
M src/modules/topos/tps_storage.c (13)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/1596.patchhttps://github.com/kamailio/kamailio/pull/1596.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/1596
<!-- 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/1610
-- Commit Summary --
* core: print log_prefix after loglevel for more intuitive parsing
-- File Changes --
M src/core/dprint.h (16)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/1610.patchhttps://github.com/kamailio/kamailio/pull/1610.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/1610