Browse code

modules: readme files regenerated - tm ... [skip ci]

Kamailio Dev authored on 25/01/2021 11:46:23
Showing 1 changed files
... ...
@@ -77,6 +77,7 @@ Daniel-Constantin Mierla
77 77
               3.48. relay_100 (str)
78 78
               3.49. rich_redirect (int)
79 79
               3.50. exec_time_check (int)
80
+              3.51. reply_relay_mode (int)
80 81
 
81 82
         4. Functions
82 83
 
... ...
@@ -227,57 +228,58 @@ Daniel-Constantin Mierla
227 228
    1.48. Set relay_100 parameter
228 229
    1.49. rich_redirect example
229 230
    1.50. Set exec_time_check parameter
230
-   1.51. t_relay usage
231
-   1.52. t_relay_to_udp usage
232
-   1.53. t_on_failure usage
233
-   1.54. t_on_branch_failure usage
234
-   1.55. t_on_reply usage
235
-   1.56. t_on_branch usage
236
-   1.57. t_newtran usage
237
-   1.58. t_reply usage
238
-   1.59. t_send_reply usage
239
-   1.60. t_lookup_request usage
240
-   1.61. t_retransmit_reply usage
241
-   1.62. t_release usage
242
-   1.63. t_forward_nonack usage
243
-   1.64. t_set_fr usage
244
-   1.65. t_reset_fr usage
245
-   1.66. t_set_max_lifetime usage
246
-   1.67. t_reset_max_lifetime usage
247
-   1.68. t_set_retr usage
248
-   1.69. t_reset_retr usage
249
-   1.70. t_set_auto_inv_100 usage
250
-   1.71. t_branch_timeout usage
251
-   1.72. t_branch_replied usage
252
-   1.73. t_any_timeout usage
253
-   1.74. t_any_replied usage
254
-   1.75. t_grep_status usage
255
-   1.76. t_is_canceled usage
256
-   1.77. t_is_expired usage
257
-   1.78. t_relay_cancel usage
258
-   1.79. t_lookup_cancel usage
259
-   1.80. t_drop_replies() usage
260
-   1.81. t_save_lumps() usage
261
-   1.82. t_load_contacts usage
262
-   1.83. t_next_contacts usage
263
-   1.84. t_next_contact_flow usage
264
-   1.85. t_check_status usage
265
-   1.86. t_check_trans usage
266
-   1.87. t_set_disable_6xx usage
267
-   1.88. t_set_disable_failover usage
268
-   1.89. t_set_disable_internal_reply usage
269
-   1.90. t_replicate usage
270
-   1.91. t_relay_to usage
271
-   1.92. t_set_no_e2e_cancel_reason usage
272
-   1.93. t_replicate usage
273
-   1.94. t_use_uac_headers usage
274
-   1.95. t_is_retr_async_reply usage
275
-   1.96. t_uac_send usage
276
-   1.97. t_get_status_code usage
277
-   1.98. t_clean usage
278
-   1.99. event_route[tm:branch-failure:id] usage
279
-   1.100. event_route[tm:local-request] usage
280
-   1.101. event_route[tm:local-response] usage
231
+   1.51. Set reply_relay_mode parameter
232
+   1.52. t_relay usage
233
+   1.53. t_relay_to_udp usage
234
+   1.54. t_on_failure usage
235
+   1.55. t_on_branch_failure usage
236
+   1.56. t_on_reply usage
237
+   1.57. t_on_branch usage
238
+   1.58. t_newtran usage
239
+   1.59. t_reply usage
240
+   1.60. t_send_reply usage
241
+   1.61. t_lookup_request usage
242
+   1.62. t_retransmit_reply usage
243
+   1.63. t_release usage
244
+   1.64. t_forward_nonack usage
245
+   1.65. t_set_fr usage
246
+   1.66. t_reset_fr usage
247
+   1.67. t_set_max_lifetime usage
248
+   1.68. t_reset_max_lifetime usage
249
+   1.69. t_set_retr usage
250
+   1.70. t_reset_retr usage
251
+   1.71. t_set_auto_inv_100 usage
252
+   1.72. t_branch_timeout usage
253
+   1.73. t_branch_replied usage
254
+   1.74. t_any_timeout usage
255
+   1.75. t_any_replied usage
256
+   1.76. t_grep_status usage
257
+   1.77. t_is_canceled usage
258
+   1.78. t_is_expired usage
259
+   1.79. t_relay_cancel usage
260
+   1.80. t_lookup_cancel usage
261
+   1.81. t_drop_replies() usage
262
+   1.82. t_save_lumps() usage
263
+   1.83. t_load_contacts usage
264
+   1.84. t_next_contacts usage
265
+   1.85. t_next_contact_flow usage
266
+   1.86. t_check_status usage
267
+   1.87. t_check_trans usage
268
+   1.88. t_set_disable_6xx usage
269
+   1.89. t_set_disable_failover usage
270
+   1.90. t_set_disable_internal_reply usage
271
+   1.91. t_replicate usage
272
+   1.92. t_relay_to usage
273
+   1.93. t_set_no_e2e_cancel_reason usage
274
+   1.94. t_replicate usage
275
+   1.95. t_use_uac_headers usage
276
+   1.96. t_is_retr_async_reply usage
277
+   1.97. t_uac_send usage
278
+   1.98. t_get_status_code usage
279
+   1.99. t_clean usage
280
+   1.100. event_route[tm:branch-failure:id] usage
281
+   1.101. event_route[tm:local-request] usage
282
+   1.102. event_route[tm:local-response] usage
281 283
 
282 284
 Chapter 1. Admin Guide
283 285
 
... ...
@@ -337,6 +339,7 @@ Chapter 1. Admin Guide
337 339
         3.48. relay_100 (str)
338 340
         3.49. rich_redirect (int)
339 341
         3.50. exec_time_check (int)
342
+        3.51. reply_relay_mode (int)
340 343
 
341 344
    4. Functions
342 345
 
... ...
@@ -712,6 +715,7 @@ failure_route["serial"]
712 715
    3.48. relay_100 (str)
713 716
    3.49. rich_redirect (int)
714 717
    3.50. exec_time_check (int)
718
+   3.51. reply_relay_mode (int)
715 719
 
716 720
 3.1. fr_timer (integer)
717 721
 
... ...
@@ -1708,6 +1712,25 @@ modparam("tm", "rich_redirect", 3)
1708 1712
 modparam("tm", "exec_time_check", 0)
1709 1713
 ...
1710 1714
 
1715
+3.51. reply_relay_mode (int)
1716
+
1717
+   If set to 1, a received 200ok response that was suspeneded is no longer
1718
+   forwarded in the transactional context if another final response was
1719
+   forward while 200ok was suspended. Forwarding the 200ok, even it was
1720
+   received first, results in overwritting the transaction response buffer
1721
+   that can impact matching of incoming ACKs.
1722
+
1723
+   Set it to 0 in order to disable this behaviour and attempt to forward
1724
+   suspended 200ok in the transaction context. This was the behaviour
1725
+   before the commit 18410da0.
1726
+
1727
+   Default value is 1.
1728
+
1729
+   Example 1.51. Set reply_relay_mode parameter
1730
+...
1731
+modparam("tm", "reply_relay_mode", 0)
1732
+...
1733
+
1711 1734
 4. Functions
1712 1735
 
1713 1736
    4.1. t_relay([host, port])
... ...
@@ -1785,7 +1808,7 @@ modparam("tm", "exec_time_check", 0)
1785 1808
    Returns a negative value on failure -- you may still want to send a
1786 1809
    negative reply upstream statelessly not to leave upstream UAC in lurch.
1787 1810
 
1788
-   Example 1.51. t_relay usage
1811
+   Example 1.52. t_relay usage
1789 1812
 ...
1790 1813
 if (!t_relay())
1791 1814
 {
... ...
@@ -1812,7 +1835,7 @@ if (!t_relay())
1812 1835
    derived from the message uri (using sip specific DNS lookups), but with
1813 1836
    the protocol corresponding to the function name.
1814 1837
 
1815
-   Example 1.52. t_relay_to_udp usage
1838
+   Example 1.53. t_relay_to_udp usage
1816 1839
 ...
1817 1840
 if (src_ip==10.0.0.0/8)
1818 1841
         t_relay_to_udp("1.2.3.4", "5060"); # sent to 1.2.3.4:5060 over udp
... ...
@@ -1852,7 +1875,7 @@ else
1852 1875
    Meaning of the parameters is as follows:
1853 1876
      * failure_route - Failure route block to be called.
1854 1877
 
1855
-   Example 1.53. t_on_failure usage
1878
+   Example 1.54. t_on_failure usage
1856 1879
 ...
1857 1880
 route {
1858 1881
     t_on_failure("1");
... ...
@@ -1888,7 +1911,7 @@ failure_route[1] {
1888 1911
      * branch_failure_route - Name of the branch_failure route block to be
1889 1912
        called (it is prefixed internally with 'tm:branch-failure:').
1890 1913
 
1891
-   Example 1.54. t_on_branch_failure usage
1914
+   Example 1.55. t_on_branch_failure usage
1892 1915
 ...
1893 1916
 route {
1894 1917
     t_on_branch_failure("myroute");
... ...
@@ -1911,7 +1934,7 @@ event_route[tm:branch-failure:myroute] {
1911 1934
    Meaning of the parameters is as follows:
1912 1935
      * onreply_route - Onreply route block to be called.
1913 1936
 
1914
-   Example 1.55. t_on_reply usage
1937
+   Example 1.56. t_on_reply usage
1915 1938
 ...
1916 1939
 loadmodule "/usr/local/lib/ser/modules/nathelper.so"
1917 1940
 ...
... ...
@@ -1943,7 +1966,7 @@ es');
1943 1966
    Meaning of the parameters is as follows:
1944 1967
      * branch_route - branch route block to be called.
1945 1968
 
1946
-   Example 1.56. t_on_branch usage
1969
+   Example 1.57. t_on_branch usage
1947 1970
 ...
1948 1971
 route {
1949 1972
         t_on_branch("1");
... ...
@@ -1968,7 +1991,7 @@ branch_route[1] {
1968 1991
    structure. Use the tmx module function t_flush_flags() to synchronize
1969 1992
    the modified message flags to the already created transaction.
1970 1993
 
1971
-   Example 1.57. t_newtran usage
1994
+   Example 1.58. t_newtran usage
1972 1995
 ...
1973 1996
 if (t_newtran()) {
1974 1997
     xlog("the transaction has been created\n");
... ...
@@ -2000,7 +2023,7 @@ if (t_newtran()) {
2000 2023
      * code - Reply code number.
2001 2024
      * reason_phrase - Reason string.
2002 2025
 
2003
-   Example 1.58. t_reply usage
2026
+   Example 1.59. t_reply usage
2004 2027
 ...
2005 2028
 t_reply("404", "Not found");
2006 2029
 ...
... ...
@@ -2018,7 +2041,7 @@ t_reply("404", "Not found");
2018 2041
      * code - Reply code number.
2019 2042
      * reason - Reason string.
2020 2043
 
2021
-   Example 1.59. t_send_reply usage
2044
+   Example 1.60. t_send_reply usage
2022 2045
 ...
2023 2046
 t_send_reply("404", "Not found");
2024 2047
 ...
... ...
@@ -2031,7 +2054,7 @@ t_send_reply("404", "Not found");
2031 2054
    none was found. However this is safely (atomically) done using
2032 2055
    t_newtran.
2033 2056
 
2034
-   Example 1.60. t_lookup_request usage
2057
+   Example 1.61. t_lookup_request usage
2035 2058
 ...
2036 2059
 if (t_lookup_request()) {
2037 2060
     ...
... ...
@@ -2042,7 +2065,7 @@ if (t_lookup_request()) {
2042 2065
 
2043 2066
    Retransmits a reply sent previously by UAS transaction.
2044 2067
 
2045
-   Example 1.61. t_retransmit_reply usage
2068
+   Example 1.62. t_retransmit_reply usage
2046 2069
 ...
2047 2070
 t_retransmit_reply();
2048 2071
 ...
... ...
@@ -2052,7 +2075,7 @@ t_retransmit_reply();
2052 2075
    Remove transaction from memory (it will be first put on a wait timer to
2053 2076
    absorb delayed messages).
2054 2077
 
2055
-   Example 1.62. t_release usage
2078
+   Example 1.63. t_release usage
2056 2079
 ...
2057 2080
 t_release();
2058 2081
 ...
... ...
@@ -2066,7 +2089,7 @@ t_release();
2066 2089
      * ip - IP address where the message should be sent.
2067 2090
      * port - Port number.
2068 2091
 
2069
-   Example 1.63. t_forward_nonack usage
2092
+   Example 1.64. t_forward_nonack usage
2070 2093
 ...
2071 2094
 t_forward_nonack("1.2.3.4", "5060");
2072 2095
 ...
... ...
@@ -2105,7 +2128,7 @@ t_forward_nonack("1.2.3.4", "5060");
2105 2128
 
2106 2129
    See also: fr_timer, fr_inv_timer, t_reset_fr().
2107 2130
 
2108
-   Example 1.64. t_set_fr usage
2131
+   Example 1.65. t_set_fr usage
2109 2132
 ...
2110 2133
 route {
2111 2134
         t_set_fr(10000); # set only fr invite timeout to 10s
... ...
@@ -2132,7 +2155,7 @@ branch_route[1] {
2132 2155
 
2133 2156
    See also: fr_timer, fr_inv_timer, t_set_fr.
2134 2157
 
2135
-   Example 1.65. t_reset_fr usage
2158
+   Example 1.66. t_reset_fr usage
2136 2159
 ...
2137 2160
 route {
2138 2161
 ...
... ...
@@ -2158,7 +2181,7 @@ route {
2158 2181
 
2159 2182
    See also: max_inv_lifetime, max_noninv_lifetime, t_reset_max_lifetime.
2160 2183
 
2161
-   Example 1.66. t_set_max_lifetime usage
2184
+   Example 1.67. t_set_max_lifetime usage
2162 2185
 ...
2163 2186
 route {
2164 2187
     if (src_ip=1.2.3.4)
... ...
@@ -2180,7 +2203,7 @@ route {
2180 2203
 
2181 2204
    See also: max_inv_lifetime, max_noninv_lifetime, t_set_max_lifetime.
2182 2205
 
2183
-   Example 1.67. t_reset_max_lifetime usage
2206
+   Example 1.68. t_reset_max_lifetime usage
2184 2207
 ...
2185 2208
 route {
2186 2209
 ...
... ...
@@ -2215,7 +2238,7 @@ route {
2215 2238
 
2216 2239
    See also: retr_timer1, retr_timer2, t_reset_retr().
2217 2240
 
2218
-   Example 1.68. t_set_retr usage
2241
+   Example 1.69. t_set_retr usage
2219 2242
 ...
2220 2243
 route {
2221 2244
         t_set_retr(250, 0); # set only T1 to 250 ms
... ...
@@ -2242,7 +2265,7 @@ branch_route[1] {
2242 2265
 
2243 2266
    See also: retr_timer1, retr_timer2, t_set_retr.
2244 2267
 
2245
-   Example 1.69. t_reset_retr usage
2268
+   Example 1.70. t_reset_retr usage
2246 2269
 ...
2247 2270
 route {
2248 2271
 ...
... ...
@@ -2258,7 +2281,7 @@ route {
2258 2281
 
2259 2282
    See also: auto_inv_100.
2260 2283
 
2261
-   Example 1.70. t_set_auto_inv_100 usage
2284
+   Example 1.71. t_set_auto_inv_100 usage
2262 2285
 ...
2263 2286
 route {
2264 2287
 ...
... ...
@@ -2273,7 +2296,7 @@ route {
2273 2296
    timeout. It can be used from FAILURE_ROUTE and BRANCH_FAILURE_ROUTE
2274 2297
    event route.
2275 2298
 
2276
-   Example 1.71. t_branch_timeout usage
2299
+   Example 1.72. t_branch_timeout usage
2277 2300
 ...
2278 2301
 failure_route[0]{
2279 2302
         if (t_branch_timeout()){
... ...
@@ -2289,7 +2312,7 @@ failure_route[0]{
2289 2312
    taken into account). It can be used from failure_route and
2290 2313
    branch-failure event route.
2291 2314
 
2292
-   Example 1.72. t_branch_replied usage
2315
+   Example 1.73. t_branch_replied usage
2293 2316
 ...
2294 2317
 failure_route[0]{
2295 2318
         if (t_branch_timeout()){
... ...
@@ -2306,7 +2329,7 @@ failure_route[0]{
2306 2329
    Returns true if at least one of the current transactions branches did
2307 2330
    timeout.
2308 2331
 
2309
-   Example 1.73. t_any_timeout usage
2332
+   Example 1.74. t_any_timeout usage
2310 2333
 ...
2311 2334
 failure_route[0]{
2312 2335
         if (!t_branch_timeout()){
... ...
@@ -2323,7 +2346,7 @@ failure_route[0]{
2323 2346
    receive some reply in the past. If called from a failure or onreply
2324 2347
    route, the "current" reply is not taken into account.
2325 2348
 
2326
-   Example 1.74. t_any_replied usage
2349
+   Example 1.75. t_any_replied usage
2327 2350
 ...
2328 2351
 onreply_route[0]{
2329 2352
         if (!t_any_replied()){
... ...
@@ -2337,7 +2360,7 @@ onreply_route[0]{
2337 2360
    Returns true if "code" is the final reply received (or locally
2338 2361
    generated) in at least one of the current transactions branches.
2339 2362
 
2340
-   Example 1.75. t_grep_status usage
2363
+   Example 1.76. t_grep_status usage
2341 2364
 ...
2342 2365
 onreply_route[0]{
2343 2366
         if (t_grep_status("486")){
... ...
@@ -2350,7 +2373,7 @@ onreply_route[0]{
2350 2373
 
2351 2374
    Returns true if the current transaction was canceled.
2352 2375
 
2353
-   Example 1.76. t_is_canceled usage
2376
+   Example 1.77. t_is_canceled usage
2354 2377
 ...
2355 2378
 failure_route[0]{
2356 2379
         if (t_is_canceled()){
... ...
@@ -2364,7 +2387,7 @@ failure_route[0]{
2364 2387
    Returns true if the current transaction has already been expired, i.e.
2365 2388
    the max_inv_lifetime/max_noninv_lifetime interval has already elapsed.
2366 2389
 
2367
-   Example 1.77. t_is_expired usage
2390
+   Example 1.78. t_is_expired usage
2368 2391
 ...
2369 2392
 failure_route[0]{
2370 2393
         if (t_is_expired()){
... ...
@@ -2385,7 +2408,7 @@ failure_route[0]{
2385 2408
    CANCELs were successfully sent to the pending branches, true if the
2386 2409
    INVITE was not found, and false in case of any error.
2387 2410
 
2388
-   Example 1.78. t_relay_cancel usage
2411
+   Example 1.79. t_relay_cancel usage
2389 2412
 if (method == CANCEL) {
2390 2413
         if (!t_relay_cancel()) {  # implicit drop if relaying was successful,
2391 2414
                                   # nothing to do
... ...
@@ -2412,7 +2435,7 @@ if (method == CANCEL) {
2412 2435
    overwritten with the flags of the INVITE. isflagset() can be used to
2413 2436
    check the flags of the previously forwarded INVITE in this case.
2414 2437
 
2415
-   Example 1.79. t_lookup_cancel usage
2438
+   Example 1.80. t_lookup_cancel usage
2416 2439
 if (method == CANCEL) {
2417 2440
         if (t_lookup_cancel()) {
2418 2441
                 log("INVITE transaction exists");
... ...
@@ -2442,7 +2465,7 @@ if (method == CANCEL) {
2442 2465
    Dropping replies works only if a new branch is added to the
2443 2466
    transaction, or it is explicitly replied in the script!
2444 2467
 
2445
-   Example 1.80. t_drop_replies() usage
2468
+   Example 1.81. t_drop_replies() usage
2446 2469
 ...
2447 2470
 failure_route[0]{
2448 2471
         if (t_check_status("5[0-9][0-9]")){
... ...
@@ -2473,7 +2496,7 @@ failure_route[0]{
2473 2496
    The transaction must be created by t_newtran() before calling
2474 2497
    t_save_lumps().
2475 2498
 
2476
-   Example 1.81. t_save_lumps() usage
2499
+   Example 1.82. t_save_lumps() usage
2477 2500
 route {
2478 2501
         ...
2479 2502
         t_newtran();
... ...
@@ -2547,7 +2570,7 @@ failure_route[1] {
2547 2570
 
2548 2571
    This function can be used from REQUEST_ROUTE and FAILURE_ROUTE.
2549 2572
 
2550
-   Example 1.82. t_load_contacts usage
2573
+   Example 1.83. t_load_contacts usage
2551 2574
 ...
2552 2575
 if (!t_load_contacts()) {
2553 2576
         sl_send_reply("500", "Server Internal Error - Cannot load contacts");
... ...
@@ -2588,7 +2611,7 @@ if (!t_load_contacts()) {
2588 2611
    contact_flows_avp are not anymore set. Based on that test, you can then
2589 2612
    use t_set_fr() function to set timers according to your needs.
2590 2613
 
2591
-   Example 1.83. t_next_contacts usage
2614
+   Example 1.84. t_next_contacts usage
2592 2615
 ...
2593 2616
 # First call after t_load_contacts() when transaction does not exist yet
2594 2617
 # and contacts should be available
... ...
@@ -2626,7 +2649,7 @@ if (!t_next_contacts()) {
2626 2649
    syslog). This function can be used from a BRANCH_FAILURE_ROUTE event
2627 2650
    route.
2628 2651
 
2629
-   Example 1.84. t_next_contact_flow usage
2652
+   Example 1.85. t_next_contact_flow usage
2630 2653
 ...
2631 2654
 event_route[tm:branch-failure:outbound]
2632 2655
 {
... ...
@@ -2649,7 +2672,7 @@ event_route[tm:branch-failure:outbound]
2649 2672
 
2650 2673
    This function can be used from ANY_ROUTE .
2651 2674
 
2652
-   Example 1.85. t_check_status usage
2675
+   Example 1.86. t_check_status usage
2653 2676
 ...
2654 2677
 if (t_check_status("(487)|(408)")) {
2655 2678
     log("487 or 408 negative reply\n");
... ...
@@ -2703,7 +2726,7 @@ Note
2703 2726
 
2704 2727
    See also: t_lookup_request(), t_lookup_cancel().
2705 2728
 
2706
-   Example 1.86. t_check_trans usage
2729
+   Example 1.87. t_check_trans usage
2707 2730
 if ( method == "CANCEL" && !t_check_trans())
2708 2731
         sl_reply("403", "cancel out of the blue forbidden");
2709 2732
 # note: in this example t_check_trans() can be replaced by t_lookup_cancel()
... ...
@@ -2718,7 +2741,7 @@ if ( method == "CANCEL" && !t_check_trans())
2718 2741
 
2719 2742
    See also: disable_6xx_block.
2720 2743
 
2721
-   Example 1.87. t_set_disable_6xx usage
2744
+   Example 1.88. t_set_disable_6xx usage
2722 2745
 ...
2723 2746
 route {
2724 2747
 ...
... ...
@@ -2733,7 +2756,7 @@ route {
2733 2756
 
2734 2757
    See also: use_dns_failover.
2735 2758
 
2736
-   Example 1.88. t_set_disable_failover usage
2759
+   Example 1.89. t_set_disable_failover usage
2737 2760
 ...
2738 2761
 route {
2739 2762
 ...
... ...
@@ -2746,7 +2769,7 @@ route {
2746 2769
 
2747 2770
    Turn off/on sending internally a SIP reply in case of relay errors.
2748 2771
 
2749
-   Example 1.89. t_set_disable_internal_reply usage
2772
+   Example 1.90. t_set_disable_internal_reply usage
2750 2773
 ...
2751 2774
 t_set_disable_internal_reply(1); # turn off sending internal reply on error
2752 2775
 if(!t_relay()) {
... ...
@@ -2779,7 +2802,7 @@ if(!t_relay()) {
2779 2802
      * hostport - address in "host:port" format. It can be given via an
2780 2803
        AVP.
2781 2804
 
2782
-   Example 1.90. t_replicate usage
2805
+   Example 1.91. t_replicate usage
2783 2806
 ...
2784 2807
 # sent to 1.2.3.4:5060 over tcp
2785 2808
 t_replicate("sip:1.2.3.4:5060;transport=tcp");
... ...
@@ -2813,7 +2836,7 @@ t_replicate_to_udp("1.2.3.4", "5060");
2813 2836
           + 0x02 - do not generate reply on internal error.
2814 2837
           + 0x04 - disable dns failover.
2815 2838
 
2816
-   Example 1.91. t_relay_to usage
2839
+   Example 1.92. t_relay_to usage
2817 2840
 ...
2818 2841
 # sent to 1.2.3.4:5060 over tcp
2819 2842
 t_relay_to("tcp:1.2.3.4:5060");
... ...
@@ -2839,7 +2862,7 @@ t_relay_to("0x01");
2839 2862
 
2840 2863
    See also: e2e_cancel_reason.
2841 2864
 
2842
-   Example 1.92. t_set_no_e2e_cancel_reason usage
2865
+   Example 1.93. t_set_no_e2e_cancel_reason usage
2843 2866
 ...
2844 2867
 route {
2845 2868
 ...
... ...
@@ -2862,7 +2885,7 @@ opying
2862 2885
      * onreply_route - the function returns true if an onreply route is
2863 2886
        set to be executed.
2864 2887
 
2865
-   Example 1.93. t_replicate usage
2888
+   Example 1.94. t_replicate usage
2866 2889
 ...
2867 2890
 if(!t_is_set("failure_route"))
2868 2891
     LM_DBG("no failure route will be executed for current transaction\n");
... ...
@@ -2876,7 +2899,7 @@ if(!t_is_set("failure_route"))
2876 2899
 
2877 2900
    It returns true.
2878 2901
 
2879
-   Example 1.94. t_use_uac_headers usage
2902
+   Example 1.95. t_use_uac_headers usage
2880 2903
 ...
2881 2904
 t_use_uac_headers();
2882 2905
 ...
... ...
@@ -2895,7 +2918,7 @@ t_use_uac_headers();
2895 2918
    returns true if the transaction is currently reply suspended or false
2896 2919
    if not.
2897 2920
 
2898
-   Example 1.95. t_is_retr_async_reply usage
2921
+   Example 1.96. t_is_retr_async_reply usage
2899 2922
 ...
2900 2923
 if (t_is_retr_async_reply()) {
2901 2924
         xlog("L_DBG", "Dropping retransmitted reply which is still currently sus
... ...
@@ -2920,7 +2943,7 @@ pended\n");
2920 2943
        Content-Type header must exist.
2921 2944
      * body - SIP message body (can be empty).
2922 2945
 
2923
-   Example 1.96. t_uac_send usage
2946
+   Example 1.97. t_uac_send usage
2924 2947
 ...
2925 2948
 t_uac_send("OPTIONS", "sip:alice@kamailio.org", "", "",
2926 2949
     "From: bob@kamailio.org;tag=2w3e\r\nTo: bob@kamailio.org", "");
... ...
@@ -2931,7 +2954,7 @@ t_uac_send("OPTIONS", "sip:alice@kamailio.org", "", "",
2931 2954
    Return the status code for transaction - the most relevant SIP reply
2932 2955
    status code, or -1 in case of error or no status code was set.
2933 2956
 
2934
-   Example 1.97. t_get_status_code usage
2957
+   Example 1.98. t_get_status_code usage
2935 2958
 ...
2936 2959
 $var(ts) = t_get_status_code();
2937 2960
 if($var(ts) == 500) { ... }
... ...
@@ -2942,7 +2965,7 @@ if($var(ts) == 500) { ... }
2942 2965
    Cleans active but very old transactions. Returns true (1). Can be
2943 2966
    called from any route.
2944 2967
 
2945
-   Example 1.98. t_clean usage
2968
+   Example 1.99. t_clean usage
2946 2969
 ...
2947 2970
 t_clean();
2948 2971
 ...
... ...
@@ -3068,7 +3091,7 @@ t_clean();
3068 3091
    enabled with the t_on_branch_failure function. This event_route uses
3069 3092
    the BRANCH_FAILURE_ROUTE route type.
3070 3093
 
3071
-   Example 1.99. event_route[tm:branch-failure:id] usage
3094
+   Example 1.100. event_route[tm:branch-failure:id] usage
3072 3095
 ...
3073 3096
 request_route {
3074 3097
     ...
... ...
@@ -3094,7 +3117,7 @@ event_route[tm:branch-failure:myroute] {
3094 3117
    The request can still be updated, i.e., changes are possible to R-URI
3095 3118
    ($ru), destination URI ($du) or the send socket ($fs).
3096 3119
 
3097
-   Example 1.100. event_route[tm:local-request] usage
3120
+   Example 1.101. event_route[tm:local-request] usage
3098 3121
 ...
3099 3122
 event_route [tm:local-request] {
3100 3123
     xlog("L_INFO", "Routing locally generated $rm to $ru\n");
... ...
@@ -3107,7 +3130,7 @@ event_route [tm:local-request] {
3107 3130
    Executed after the tm module sent a local generated, transaction
3108 3131
    stateful response.
3109 3132
 
3110
-   Example 1.101. event_route[tm:local-response] usage
3133
+   Example 1.102. event_route[tm:local-response] usage
3111 3134
 ...
3112 3135
 event_route[tm:local-response] {
3113 3136
     xlog("tm:local-response replied locally\n");