Module: kamailio Branch: master Commit: ae08b5955935466c401709903b38491aba7ec33e URL: https://github.com/kamailio/kamailio/commit/ae08b5955935466c401709903b38491aba7ec33e
Author: Kamailio Dev <kamailio....@kamailio.org> Committer: Kamailio Dev <kamailio....@kamailio.org> Date: 2019-12-12T08:46:16+01:00 modules: readme files regenerated - tm ... [skip ci] --- Modified: src/modules/tm/README --- Diff: https://github.com/kamailio/kamailio/commit/ae08b5955935466c401709903b38491aba7ec33e.diff Patch: https://github.com/kamailio/kamailio/commit/ae08b5955935466c401709903b38491aba7ec33e.patch --- diff --git a/src/modules/tm/README b/src/modules/tm/README index 3607b3969b..4b23eacb58 100644 --- a/src/modules/tm/README +++ b/src/modules/tm/README @@ -1937,17 +1937,20 @@ branch_route[1] { the only way a script can add a new transaction in an atomic way. Typically, it is used to deploy a UAS. - Note that any flag operations (e.g. for accounting) after this function - has been called will be ignored. You can use the the tmx module - function t_flush_flags() to flush the altered flags to the already - created transaction. + Note: once the t_newtran() is executed, the new message flag operations + (i.e., setflag() and resetflag()) are not syncronized to the + transaction, being stored only in the private memory SIP message + structure. Use the tmx module function t_flush_flags() to synchronize + the modified message flags to the already created transaction. Example 1.56. t_newtran usage ... if (t_newtran()) { - log("UAS logic"); + xlog("the transaction has been created\n"); t_reply("999","hello"); -} else sl_reply_error(); +} else { + sl_reply_error(); +} ... See misc/examples/mixed/uas.cfg for more examples. _______________________________________________ Kamailio (SER) - Development Mailing List sr-dev@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
