Module: kamailio Branch: 5.6 Commit: d49c4b498a0c835d4f3a36d0494b7a131bdfd332 URL: https://github.com/kamailio/kamailio/commit/d49c4b498a0c835d4f3a36d0494b7a1… Author: Kamailio Dev <kamailio.dev(a)kamailio.org> Committer: Kamailio Dev <kamailio.dev(a)kamailio.org> Date: 2022-07-06T09:31:48+02:00 modules: readme files regenerated - modules ... [skip ci] --- Modified: src/modules/tm/README Modified: src/modules/topos/README --- Diff: https://github.com/kamailio/kamailio/commit/d49c4b498a0c835d4f3a36d0494b7a1… Patch: https://github.com/kamailio/kamailio/commit/d49c4b498a0c835d4f3a36d0494b7a1… --- diff --git a/src/modules/tm/README b/src/modules/tm/README index 445630cf34..f1827a9e77 100644 --- a/src/modules/tm/README +++ b/src/modules/tm/README @@ -146,7 +146,7 @@ Daniel-Constantin Mierla 5.1. tm.list 5.2. tm.t_uac_start 5.3. tm.t_uac_wait - 5.4. tm.t_uac_wait + 5.4. tm.t_uac_wait_block 5.5. tm.cancel 5.6. tm.hash_stats 5.7. tm.reply @@ -410,7 +410,7 @@ Chapter 1. Admin Guide 5.1. tm.list 5.2. tm.t_uac_start 5.3. tm.t_uac_wait - 5.4. tm.t_uac_wait + 5.4. tm.t_uac_wait_block 5.5. tm.cancel 5.6. tm.hash_stats 5.7. tm.reply @@ -3008,7 +3008,7 @@ t_clean(); 5.1. tm.list 5.2. tm.t_uac_start 5.3. tm.t_uac_wait - 5.4. tm.t_uac_wait + 5.4. tm.t_uac_wait_block 5.5. tm.cancel 5.6. tm.hash_stats 5.7. tm.reply @@ -3043,7 +3043,7 @@ t_clean(); Similar to tm.t_uac_start, but waits asynchronously for the SIP response and tries to provide its details via RPC response. -5.4. tm.t_uac_wait +5.4. tm.t_uac_wait_block Similar to tm.t_uac_start, but blocks waiting for the SIP response and returns the SIP reply code and reason text via RPC response. It waits diff --git a/src/modules/topos/README b/src/modules/topos/README index ef7c0e9634..6c7ef0e3d8 100644 --- a/src/modules/topos/README +++ b/src/modules/topos/README @@ -140,11 +140,13 @@ Chapter 1. Admin Guide to be loaded (tune the module parameters if needed). It also works for SIP MESSAGE or other requests that do not create a - dialog -- record_route() must be used for them as well, the headers are - not going to be in the messages sent to the network, they are needed to - know local addresses used to communicate with each side. This module is - designed to work for presence (SUBSCRIBE-based) dialogs too. The - REGISTER and PUBLISH requests are skipped from processing by this + dialog (e.g., OPTIONS) -- record_route() must be used for them as well, + the headers are not going to be in the messages sent to the network, + they are needed to know local addresses used to communicate with each + side. This module is designed to work for presence (SUBSCRIBE-based) + dialogs too. + + The REGISTER and PUBLISH requests are skipped from processing by this module, expected to be terminated on a local SIP server. 2. Dependencies