Module: kamailio
Branch: master
Commit: ade001c89bda5f9f7a6b2802110c8a1ce4a96968
URL: https://github.com/kamailio/kamailio/commit/ade001c89bda5f9f7a6b2802110c8a1…
Author: Xenofon Karamanos <xk(a)gilawa.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2025-07-31T08:24:38+02:00
topos: Add new contact_mode docs.
---
Modified: src/modules/topos/doc/topos_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/ade001c89bda5f9f7a6b2802110c8a1…
Patch: https://github.com/kamailio/kamailio/commit/ade001c89bda5f9f7a6b2802110c8a1…
---
diff --git a/src/modules/topos/doc/topos_admin.xml b/src/modules/topos/doc/topos_admin.xml
index 574fff3d380..6698b0103c2 100644
--- a/src/modules/topos/doc/topos_admin.xml
+++ b/src/modules/topos/doc/topos_admin.xml
@@ -336,7 +336,12 @@ modparam("topos", "contact_host", "proxy.domain.com")
the database or redis server is stored. The default is to use
the Contact user (0), alternatively a Contact URI parameter
can be used (1) with values from the SIP message, or from AVP
- variables (2). This can be useful for interoperating which
+ variables (2).
+
+ Contact mode (3) is similar to mode 2, but for the case when we want
+ to alter the domain part.
+
+ This can be useful for interoperating which
gateways that need a certain user part in the Contact URI.
</para>
<para>In mode (1) the a-side contact user is taken from the
@@ -348,6 +353,13 @@ modparam("topos", "contact_host", "proxy.domain.com")
parameter. Furthermore you need to assign values to them during
the processing of the initial SIP request.
</para>
+ <para>
+ If you use the mode (3), you need to configure the
+ <emphasis>xavu_field_a_contact_host</emphasis> and <emphasis>xavu_field_b_contact_host</emphasis>
+ parameter. Furthermore you need to assign values to them during
+ the processing of the initial SIP request.
+ </para>
+
<para>
The name of the Contact URI parameter can be customized with
the <emphasis>cparam_name</emphasis> parameter.
<!-- 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)
- [ ] 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 -->
Added subscriptions replication and presentity sync via dmq for presence module.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/4239
-- Commit Summary --
* Subscriptions replication and presence sync
-- File Changes --
M src/modules/presence/hash.c (92)
M src/modules/presence/hash.h (6)
M src/modules/presence/notify.c (9)
M src/modules/presence/presence.c (18)
M src/modules/presence/presence.h (6)
M src/modules/presence/presence_dmq.c (334)
M src/modules/presence/presence_dmq.h (6)
M src/modules/presence/presentity.c (93)
M src/modules/presence/presentity.h (2)
M src/modules/presence/publish.c (4)
M src/modules/presence/subscribe.c (55)
M src/modules/presence/subscribe.h (1)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/4239.patchhttps://github.com/kamailio/kamailio/pull/4239.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/4239
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/4239(a)github.com>
anfedoro created an issue (kamailio/kamailio#4344)
Hello please advice what is wrong
The scenario is following
Client get registred with p-cscf using udp as transport and ipsec enabled
Registration completed successfully.
Client send reg event SUBSCRIBE, and get 200 back
But it do not get any notification then.
In p-cscf container I am observing NOTIFY coming from s-cscf and then something strange happen
```
52(95) NOTICE: {1 350779919 NOTIFY 0ed4dd8c-89a5-42ac-80cb-690891a400f1} <script>: PCSCF: NOTIFY sip:172.22.0.1:55822;transport=udp (sip:9076543210@ims.mnc001.mcc001.3gppnetwork.org (172.22.0.20:6060) to sip:9076543210@ims.mnc001.mcc001.3gppnetwork.org, 0ed4dd8c-89a5-42ac-80cb-690891a400f1)
52(95) NOTICE: {1 350779919 NOTIFY 0ed4dd8c-89a5-42ac-80cb-690891a400f1} <script>: Within DLG
52(95) NOTICE: {1 350779919 NOTIFY 0ed4dd8c-89a5-42ac-80cb-690891a400f1} <script>: Within loose route
52(95) NOTICE: {1 350779919 NOTIFY 0ed4dd8c-89a5-42ac-80cb-690891a400f1} <script>: PCSCF MO_indialog:
Destination URI: <null>
Request URI: sip:172.22.0.1:55822;transport=udp
52(95) NOTICE: {1 350779919 NOTIFY 0ed4dd8c-89a5-42ac-80cb-690891a400f1} <script>: Source IP and Port: (172.22.0.20:6060)
Route-URI: sip:mo@172.22.0.21:6101;lr=on;ftag=b7f568fe
52(95) NOTICE: {1 350779919 NOTIFY 0ed4dd8c-89a5-42ac-80cb-690891a400f1} <script>: Received IP and Port: (172.22.0.21:6101)
52(95) NOTICE: {1 350779919 NOTIFY 0ed4dd8c-89a5-42ac-80cb-690891a400f1} <script>: Next hop domain: (172.22.0.1)
52(95) NOTICE: {1 350779919 NOTIFY 0ed4dd8c-89a5-42ac-80cb-690891a400f1} <script>: Contact header: <sip:scscf.ims.mnc001.mcc001.3gppnetwork.org:6060>
52(95) INFO: {1 350779919 NOTIFY 0ed4dd8c-89a5-42ac-80cb-690891a400f1} ims_ipsec_pcscf [cmd.c:1187]: ipsec_forward(): new destination URI: sip:172.22.0.1:55822
99(142) ERROR: <core> [core/tcp_main.c:4645]: handle_tcpconn_ev(): connect 172.22.0.1:55822 failed
```
as you may see, request states transport=udp,
**Request URI: sip:172.22.0.1:55822;transport=udp**
while p-cscf then trying to use tcp??
**99(142) ERROR: <core> [core/tcp_main.c:4645]: handle_tcpconn_ev(): connect 172.22.0.1:55822 failed**
what is wrong?
Using tcp as a transport initially works well and NOTIFY is coming to the client.
thanks in advance
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4344
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4344(a)github.com>