Browse code

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

Kamailio Dev authored on 06/07/2022 07:31:48
Showing 2 changed files
... ...
@@ -146,7 +146,7 @@ Daniel-Constantin Mierla
146 146
               5.1. tm.list
147 147
               5.2. tm.t_uac_start
148 148
               5.3. tm.t_uac_wait
149
-              5.4. tm.t_uac_wait
149
+              5.4. tm.t_uac_wait_block
150 150
               5.5. tm.cancel
151 151
               5.6. tm.hash_stats
152 152
               5.7. tm.reply
... ...
@@ -410,7 +410,7 @@ Chapter 1. Admin Guide
410 410
         5.1. tm.list
411 411
         5.2. tm.t_uac_start
412 412
         5.3. tm.t_uac_wait
413
-        5.4. tm.t_uac_wait
413
+        5.4. tm.t_uac_wait_block
414 414
         5.5. tm.cancel
415 415
         5.6. tm.hash_stats
416 416
         5.7. tm.reply
... ...
@@ -3008,7 +3008,7 @@ t_clean();
3008 3008
    5.1. tm.list
3009 3009
    5.2. tm.t_uac_start
3010 3010
    5.3. tm.t_uac_wait
3011
-   5.4. tm.t_uac_wait
3011
+   5.4. tm.t_uac_wait_block
3012 3012
    5.5. tm.cancel
3013 3013
    5.6. tm.hash_stats
3014 3014
    5.7. tm.reply
... ...
@@ -3043,7 +3043,7 @@ t_clean();
3043 3043
    Similar to tm.t_uac_start, but waits asynchronously for the SIP
3044 3044
    response and tries to provide its details via RPC response.
3045 3045
 
3046
-5.4.  tm.t_uac_wait
3046
+5.4.  tm.t_uac_wait_block
3047 3047
 
3048 3048
    Similar to tm.t_uac_start, but blocks waiting for the SIP response and
3049 3049
    returns the SIP reply code and reason text via RPC response. It waits
... ...
@@ -140,11 +140,13 @@ Chapter 1. Admin Guide
140 140
    to be loaded (tune the module parameters if needed).
141 141
 
142 142
    It also works for SIP MESSAGE or other requests that do not create a
143
-   dialog -- record_route() must be used for them as well, the headers are
144
-   not going to be in the messages sent to the network, they are needed to
145
-   know local addresses used to communicate with each side. This module is
146
-   designed to work for presence (SUBSCRIBE-based) dialogs too. The
147
-   REGISTER and PUBLISH requests are skipped from processing by this
143
+   dialog (e.g., OPTIONS) -- record_route() must be used for them as well,
144
+   the headers are not going to be in the messages sent to the network,
145
+   they are needed to know local addresses used to communicate with each
146
+   side. This module is designed to work for presence (SUBSCRIBE-based)
147
+   dialogs too.
148
+
149
+   The REGISTER and PUBLISH requests are skipped from processing by this
148 150
    module, expected to be terminated on a local SIP server.
149 151
 
150 152
 2. Dependencies