Module: kamailio Branch: master Commit: 877d357a0f3489b90e088daf0cc970f63204cf7c URL: https://github.com/kamailio/kamailio/commit/877d357a0f3489b90e088daf0cc970f63204cf7c
Author: Daniel-Constantin Mierla <[email protected]> Committer: Daniel-Constantin Mierla <[email protected]> Date: 2026-01-20T15:30:45+01:00 tm: docs for t_msg_apply_changes() --- Modified: src/modules/tm/doc/functions.xml --- Diff: https://github.com/kamailio/kamailio/commit/877d357a0f3489b90e088daf0cc970f63204cf7c.diff Patch: https://github.com/kamailio/kamailio/commit/877d357a0f3489b90e088daf0cc970f63204cf7c.patch --- diff --git a/src/modules/tm/doc/functions.xml b/src/modules/tm/doc/functions.xml index 35c33cfffae..76d062fea04 100644 --- a/src/modules/tm/doc/functions.xml +++ b/src/modules/tm/doc/functions.xml @@ -2026,4 +2026,41 @@ reply_route { </example> </section> + <section id="tm.f.t_msg_apply_changes"> + <title> + <function>t_msg_apply_changes()</function> + </title> + <para> + Apply changes to the SIP request processed in a branch_route block. It + changes the request only for that particular branch, not the transaction + incoming request. It is similar to msg_apply_changes(), but designed + to be used in the context of the branch route, after the transaction + was created. + </para> + <para> + It is not needed to use this function explicitely, unless the changes + to the SIP request are needed for the next functions in the same + branch_route block, otherwise the operations for adding/removing headers + or changing the body of the request are applied before writing to + the outbound socket. + </para> + <para> + It requires to set core parameter + <emphasis>msg_apply_changes_mode = 1</emphasis>. + </para> + <example> + <title><function>t_msg_apply_changes</function> usage</title> + <programlisting> +... +msg_apply_changes_mode = 1; +... +branch_route[OUT] { + append_hf("X-Hdr: abc\n"); + t_msg_apply_changes(); +} +... + </programlisting> + </example> + </section> + </section> _______________________________________________ Kamailio - Development Mailing List -- [email protected] To unsubscribe send an email to [email protected] Important: keep the mailing list in the recipients, do not reply only to the sender!
