From e93717fe95f39c5832e4bc380fe4a1d24a4e977b Mon Sep 17 00:00:00 2001 From: Kamailio Dev Date: Fri, 23 Oct 2020 11:17:14 +0200 Subject: [PATCH] modules: readme files regenerated - modules ... [skip ci] --- src/modules/registrar/README | 8 +++++--- src/modules/secsipid/README | 2 +- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/src/modules/registrar/README b/src/modules/registrar/README index f4f5ccae0dd..7df142cb002 100644 --- a/src/modules/registrar/README +++ b/src/modules/registrar/README @@ -959,8 +959,9 @@ kamcmd cfg.set_now_int registrar use_expired_contacts 0 location records (in usrloc) depending on Contact and Expires header fields in the REGISTER message. On success and when called from the REQUEST_ROUTE, “200 OK” will be returned listing all contacts that are - currently in the location database. On an error, an error message will - be sent with a short description in reason phrase. + currently in the location database. As a side effect, also branch flags + are stored in usrloc. On an error, an error message will be sent with a + short description in reason phrase. Meaning of the parameters is as follows: * domain - Logical domain within the registrar. If a database is used @@ -1008,7 +1009,8 @@ save("location", "0x00", "sip:test@kamailio.org"); no such contacts, -1 will be returned. If there are such contacts, Request-URI will be overwritten with the contact that has the highest q value and optionally the rest will be appended to the message - (depending on append_branches parameter value). + (depending on append_branches parameter value). As a side effect, also + branch flags are restored from usrloc. If the method_filtering option is enabled and request is initial request without to-tag, the lookup function will return only the diff --git a/src/modules/secsipid/README b/src/modules/secsipid/README index f2a4bc98e93..a58d5110787 100644 --- a/src/modules/secsipid/README +++ b/src/modules/secsipid/README @@ -133,7 +133,7 @@ modparam("secsipid", "timeout", 2) downloading the key using the URL from "info" parameter of the Identity header, using the value od "timeout" parameter to limit the download time. The validity of the JWT body in the Identity header is also - checjed against the "expire" parameter. + checked against the "expire" parameter. The parameters can contain pseudo-variables.