Module: kamailio
Branch: master
Commit: 2131af6464623a6bab1b23489cc1891faf7378b8
URL: https://github.com/kamailio/kamailio/commit/2131af6464623a6bab1b23489cc1891…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2025-07-10T10:51:05+02:00
tm: docs for rpc command tm.t_uac_attrs
---
Modified: src/modules/tm/doc/rpc.xml
---
Diff: https://github.com/kamailio/kamailio/commit/2131af6464623a6bab1b23489cc1891…
Patch: https://github.com/kamailio/kamailio/commit/2131af6464623a6bab1b23489cc1891…
---
diff --git a/src/modules/tm/doc/rpc.xml b/src/modules/tm/doc/rpc.xml
index 00164bc5793..21b77bab2ec 100644
--- a/src/modules/tm/doc/rpc.xml
+++ b/src/modules/tm/doc/rpc.xml
@@ -173,6 +173,46 @@
</para>
</section>
+ <section id="tm.rpc.t_uac_attrs">
+ <title>
+ <function moreinfo="none">tm.t_uac_attrs</function>
+ </title>
+ <para>
+ Combine the tm.t_uac_* variants, by providing the first parameter with
+ attributes, then the other parameters are like for tm.t_uac_start.
+ </para>
+ <para>
+ The attributes are in the format "name1=value1;...;nameX=valueX". The
+ name of the attribute can be:
+ </para>
+ <itemizedlist>
+ <listitem><para>
+ <emphasis>reply</emphasis> - control how the reply is waited. If
+ not provided, acts like tm.t_uac_start. The values can be:
+ "wait" - act like tm.t_uac_wait; "block" - act like
+ tm.t_uac_wait_block.
+ </para></listitem>
+ <listitem><para>
+ <emphasis>cbflags</emphasis> - the transaction callback flags. The
+ values can be: "noack" - to not automatically send ACK for local
+ INVITE requests
+ </para></listitem>
+ <listitem><para>
+ <emphasis>rpflags</emphasis> - RPC parameters flags. The values
+ can be: 1 - the body is hexa-encoded value.
+ </para></listitem>
+ </itemizedlist>
+ <example>
+ <title>Using <quote>tm.t_uac_attrs</quote></title>
+ <programlisting format="linespecific">
+...
+kamcli rpc tm.t_uac_attrs 'reply=wait;cbflags=noack;rpflags=1' 'INVITE' ...
+...
+</programlisting>
+ </example>
+ </section>
+
+
<section id="tm.rpc.cancel">
<title>
<function moreinfo="none">tm.cancel</function>
Module: kamailio
Branch: master
Commit: 558e6458c083d12087556808aced05589cd59669
URL: https://github.com/kamailio/kamailio/commit/558e6458c083d12087556808aced055…
Author: Henning Westerholt <hw(a)gilawa.com>
Committer: Henning Westerholt <hw(a)gilawa.com>
Date: 2025-07-10T08:36:17Z
carrierroute: spelling fix in comment
---
Modified: src/modules/carrierroute/cr_rule.h
---
Diff: https://github.com/kamailio/kamailio/commit/558e6458c083d12087556808aced055…
Patch: https://github.com/kamailio/kamailio/commit/558e6458c083d12087556808aced055…
---
diff --git a/src/modules/carrierroute/cr_rule.h b/src/modules/carrierroute/cr_rule.h
index f0517e2f165..96f69f58633 100644
--- a/src/modules/carrierroute/cr_rule.h
+++ b/src/modules/carrierroute/cr_rule.h
@@ -48,7 +48,7 @@ struct route_rule
double orig_prob; /*!< The original probability for that rule, only useful when using crc32 hashing */
str host; /*!< The new target host for the request */
int strip; /*!< the number of digits to be stripped off from uri before prepending prefix */
- str local_prefix; /*!< the pefix to be attached to the new destination */
+ str local_prefix; /*!< the prefix to be attached to the new destination */
str local_suffix; /*!< the suffix to be appended to the localpart of the new destination */
str comment; /*!< A comment for the route rule */
str prefix; /*!< The prefix for which the route is valid */
Pandi1981 created an issue (kamailio/kamailio#4208)
We are facing an issue while using TOPOS in Kamailio P-CSCF (running under Docker).
Kamailio version: 6.0.0
operating system: "10 (buster)"
**Call Flow & Issue Description:**
Note: Public IP and Private IP mapping using the below configuration.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
listen=udp:LOCAL_IP:5060 name "internal"
listen=udp:LOCAL_IP:6080 advertise PUBLIC_IP:6080 name "external"
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
**Call Flow (INVITE):**
A-Party --> Kamailio P-CSCF (Public IP) --> Kamailio P-CSCF (Private IP) --> Kamailio S-CSCF (Private IP)
B-Party <-- Kamailio P-CSCF (Public IP) <-- Kamailio P-CSCF (Private IP) <-- Kamailio S-CSCF (Private IP)
Everything works correctly up to the point where the 200 OK is received by the A-Party. However, when the A-Party sends the ACK, it is received by the Kamailio P-CSCF but is not forwarded to the B-Party.
Upon investigation, we found that when Kamailio receives the ACK from the A-Party, the rr (Record-Route) module fails to recognize its own Route header and thus falls back to strict routing instead of performing loose routing. This results in an incorrect rewrite of the Request-URI of the ACK, causing it to fail to reach the B-Party. Essentially, the Route header is not popped as expected and the ACK routing breaks.
TOPOS module is configured as follows:
loadmodule "topos_redis.so"
loadmodule "ndb_redis.so"
loadmodule "topos.so"
modparam("ndb_redis", "server", "name=tps;addr=127.0.0.1;port=6379;db=0")
modparam("topos", "storage", "redis")
modparam("topos_redis", "serverid", "tps")
modparam("topos", "rr_update", 1)
modparam("topos", "contact_mode", 1)
modparam("topos", "xavu_field_a_contact", "a_contact")
modparam("topos", "xavu_field_b_contact", "b_contact")
modparam("topos", "xavu_cfg", "tps")
Please guide us how to achieve and what we are doing wrong.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4208
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4208(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
- [ ] 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
- [x] Related to issue #3823
#### Description
<!-- Describe your changes in detail -->
This PR aims to implement what was discussed in [mailing list](https://lists.kamailio.org/mailman3/hyperkitty/list/sr-dev@lists.kama… regarding some `tls.reload` and increasing memory usage.
It adds a new parameter `enable_shared_ctx` in `tls` module that if set to 0, preserves the old behavior and if set to 1 (other than 0 tbh), it creates a single SSL context that is being shared. This have the effect of using way less memory when initialized as well, but also minimizes (can't say it fixes the problem) the `tls.reload` memory increase.
I have also added a small markdown (comparison.md) file, where some comparisons where made between enabled/disabled shared context and with/without CA file (where the initial problem was occurring by the reporter).
Feedback would be necessary to verify whether this patch, acts as expected and kamailio works as intented.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3972
-- Commit Summary --
* tls: Add parameter for shared contexts
* tls: Comparison for enable_shared_ctx
-- File Changes --
A comparison.md (15)
M src/modules/tls/tls_domain.c (172)
M src/modules/tls/tls_mod.c (11)
M src/modules/tls/tls_mod.h (1)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3972.patchhttps://github.com/kamailio/kamailio/pull/3972.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3972
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3972(a)github.com>
denyspozniak created an issue (kamailio/kamailio#4314)
### Description
The code below causes Kamailio to crash when sending a simple OPTIONS request.
I agree that this is not the most proper way to call the sl function,
but it's probably worth paying attention to this issue.
#### Reproduction
```import sys
import KSR as KSR
def mod_init():
return kamailio()
class kamailio:
def __init__(self):
KSR.info('== kamailio init ==\n')
def child_init(self, rank):
return 0
def ksr_request_route(self, msg):
KSR.x.modf("sl_send_reply", "200", "OK");
return 1
```
#### Debugging Data
[(gdb) bt full.txt](https://github.com/user-attachments/files/21149798/gdb.bt.full.tx…
[(gdb) info locals.txt](https://github.com/user-attachments/files/21149836/gdb.info.loc…
```
(gdb) list
154 in sl_funcs.c
```
#### Log Messages
```
Program received signal SIGSEGV, Segmentation fault.
sl_reply_helper (msg=msg@entry=0x7ffff6fada80, code=200, reason=reason@entry=0x7ffff75d2070 "OK", tag=tag@entry=0x0) at sl_funcs.c:159
159 sl_funcs.c: No such file or directory.
```
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
version: kamailio 6.1.0-dev1 (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, MEM_JOIN_FREE, 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_SEND_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 9.4.0
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4314
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4314(a)github.com>
tsearle created an issue (kamailio/kamailio#4308)
while rtpengine_subscribe_request is the correct method name in kemi, when using the kamailio scripting engine the correct name is rtpengine_subscribe_offer
the documentation for the module needs to be updated to reflect this
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4308
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4308(a)github.com>