sr-dev

sr-dev@lists.kamailio.org

22 participants
45186 discussions

git:master:5898c5ac: kex: docs for rpc pkg.info command
by Daniel-Constantin Mierla 16 Sep '20

16 Sep '20

Module: kamailio Branch: master Commit: 5898c5ac89d7a53aa9aa877cc1c642e4365e66dd URL: https://github.com/kamailio/kamailio/commit/5898c5ac89d7a53aa9aa877cc1c642e… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2020-09-16T07:31:27+02:00 kex: docs for rpc pkg.info command --- Modified: src/modules/kex/doc/kex_admin.xml --- Diff: https://github.com/kamailio/kamailio/commit/5898c5ac89d7a53aa9aa877cc1c642e… Patch: https://github.com/kamailio/kamailio/commit/5898c5ac89d7a53aa9aa877cc1c642e… --- diff --git a/src/modules/kex/doc/kex_admin.xml b/src/modules/kex/doc/kex_admin.xml index 334f989342..3e4ee9e1f4 100644 --- a/src/modules/kex/doc/kex_admin.xml +++ b/src/modules/kex/doc/kex_admin.xml @@ -732,6 +732,20 @@ resetdebug(); &kamcmd; pkg.stats rank 1 &kamcmd; pkg.stats index 10 </programlisting> + </section> + <section id="kex.r.pkg.info"> + <title> + <function moreinfo="none">pkg.info</function> + </title> + <para> + Get pkg manager details. + </para> + <para> + Example: + </para> + <programlisting format="linespecific"> + &kamcli; rpc pkg.info + </programlisting> </section> <section id="kex.r.stats.get_statistics"> <title>

1 0

git:5.2:07e51b97: modules: readme files regenerated - modules ... [skip ci]
by Kamailio Dev 15 Sep '20

15 Sep '20

Module: kamailio Branch: 5.2 Commit: 07e51b97c9a409eeb4d735f8d20a67b6f6c7e097 URL: https://github.com/kamailio/kamailio/commit/07e51b97c9a409eeb4d735f8d20a67b… Author: Kamailio Dev <kamailio.dev(a)kamailio.org> Committer: Kamailio Dev <kamailio.dev(a)kamailio.org> Date: 2020-09-15T18:01:51+02:00 modules: readme files regenerated - modules ... [skip ci] --- Modified: src/modules/registrar/README --- Diff: https://github.com/kamailio/kamailio/commit/07e51b97c9a409eeb4d735f8d20a67b… Patch: https://github.com/kamailio/kamailio/commit/07e51b97c9a409eeb4d735f8d20a67b… --- diff --git a/src/modules/registrar/README b/src/modules/registrar/README index c5f35ed381..ab3a38a260 100644 --- a/src/modules/registrar/README +++ b/src/modules/registrar/README @@ -239,21 +239,22 @@ Chapter 1. Admin Guide If path support is enabled in the registrar module, a call to save(...) stores the values of the Path Header(s) along with the contact into usrloc. There are three modes regarding the reply to a REGISTER - including one or more Path HFs: + including one or more Path header fields: * off - stores the value of the Path headers into usrloc without passing it back to the UAC in the reply. * lazy - stores the Path header and passes it back to the UAC if - Path-support is indicated by the “path” param in the Supported HF. + Path-support is indicated by the “path” param in the Supported + header field. * strict - rejects the registration with “420 Bad Extension” if there's a Path header but no support for it is indicated by the UAC. Otherwise it's stored and passed back to the UAC. A call to lookup(...) always uses the path header if found, and inserts - it as Route HF either in front of the first Route HF, or after the last - Via HF if no Route is present. It also sets the destination uri to the - first Path uri, thus overwriting the received-uri, because NAT has to - be handled at the outbound-proxy of the UAC (the first hop after - client's NAT). + it as Route header field either in front of the first Route header + field, or after the last Via header field if no Route is present. It + also sets the destination uri to the first Path uri, thus overwriting + the received-uri, because NAT has to be handled at the outbound-proxy + of the UAC (the first hop after client's NAT). The whole process is transparent to the user, so no config changes are required beside setting the registrar-parameters “use_path” and @@ -322,10 +323,10 @@ Chapter 1. Admin Guide 3.1. default_expires (integer) - If the processed message contains neither Expires HFs nor expires - contact parameters, this value will be used for newly created usrloc - records. The parameter contains number of second to expire (for example - use 3600 for one hour). If it is set to a lower value than the + If the processed message contains neither Expires header fields nor + expires contact parameters, this value will be used for newly created + usrloc records. The parameter contains number of second to expire (for + example use 3600 for one hour). If it is set to a lower value than the “min_expires” parameter then it will be ignored. This parameter can be modified via ser config framework. A random value in a specific interval can be selected by using the default_expires_range parameter @@ -853,8 +854,8 @@ end 4.1. save(domain, [, flags [, uri]]) The function processes a REGISTER message. It can add, remove or modify - location records (in usrloc) depending on Contact and Expires HFs in - the REGISTER message. On success and when called from the + 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. @@ -864,7 +865,7 @@ end then this must be name of the table which stores the contacts. * flags (optional) - the value may be a bitwise OR of the following flags: - + 0x01 - save the contacts only in memory cache without no DB + + 0x01 - save the contacts only in memory cache with no DB operation; + 0x02 - do not generate a SIP reply to the current REGISTER request. When used in ONREPLY_ROUTE, this parameter is

1 0

git:5.3:458d96d9: modules: readme files regenerated - modules ... [skip ci]
by Kamailio Dev 15 Sep '20

15 Sep '20

Module: kamailio Branch: 5.3 Commit: 458d96d9cabf679efbcaaa81f69086c50940e495 URL: https://github.com/kamailio/kamailio/commit/458d96d9cabf679efbcaaa81f69086c… Author: Kamailio Dev <kamailio.dev(a)kamailio.org> Committer: Kamailio Dev <kamailio.dev(a)kamailio.org> Date: 2020-09-15T18:01:38+02:00 modules: readme files regenerated - modules ... [skip ci] --- Modified: src/modules/registrar/README --- Diff: https://github.com/kamailio/kamailio/commit/458d96d9cabf679efbcaaa81f69086c… Patch: https://github.com/kamailio/kamailio/commit/458d96d9cabf679efbcaaa81f69086c… --- diff --git a/src/modules/registrar/README b/src/modules/registrar/README index e4516756e6..2a611ef564 100644 --- a/src/modules/registrar/README +++ b/src/modules/registrar/README @@ -245,21 +245,22 @@ Chapter 1. Admin Guide If path support is enabled in the registrar module, a call to save(...) stores the values of the Path Header(s) along with the contact into usrloc. There are three modes regarding the reply to a REGISTER - including one or more Path HFs: + including one or more Path header fields: * off - stores the value of the Path headers into usrloc without passing it back to the UAC in the reply. * lazy - stores the Path header and passes it back to the UAC if - Path-support is indicated by the “path” param in the Supported HF. + Path-support is indicated by the “path” param in the Supported + header field. * strict - rejects the registration with “420 Bad Extension” if there's a Path header but no support for it is indicated by the UAC. Otherwise it's stored and passed back to the UAC. A call to lookup(...) always uses the path header if found, and inserts - it as Route HF either in front of the first Route HF, or after the last - Via HF if no Route is present. It also sets the destination uri to the - first Path uri, thus overwriting the received-uri, because NAT has to - be handled at the outbound-proxy of the UAC (the first hop after - client's NAT). + it as Route header field either in front of the first Route header + field, or after the last Via header field if no Route is present. It + also sets the destination uri to the first Path uri, thus overwriting + the received-uri, because NAT has to be handled at the outbound-proxy + of the UAC (the first hop after client's NAT). The whole process is transparent to the user, so no config changes are required beside setting the registrar-parameters “use_path” and @@ -329,10 +330,10 @@ Chapter 1. Admin Guide 3.1. default_expires (integer) - If the processed message contains neither Expires HFs nor expires - contact parameters, this value will be used for newly created usrloc - records. The parameter contains number of second to expire (for example - use 3600 for one hour). If it is set to a lower value than the + If the processed message contains neither Expires header fields nor + expires contact parameters, this value will be used for newly created + usrloc records. The parameter contains number of second to expire (for + example use 3600 for one hour). If it is set to a lower value than the “min_expires” parameter then it will be ignored. This parameter can be modified via ser config framework. A random value in a specific interval can be selected by using the default_expires_range parameter @@ -892,8 +893,8 @@ request_route { 4.1. save(domain, [, flags [, uri]]) The function processes a REGISTER message. It can add, remove or modify - location records (in usrloc) depending on Contact and Expires HFs in - the REGISTER message. On success and when called from the + 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. @@ -903,7 +904,7 @@ request_route { then this must be name of the table which stores the contacts. * flags (optional) - the value may be a bitwise OR of the following flags: - + 0x01 - save the contacts only in memory cache without no DB + + 0x01 - save the contacts only in memory cache with no DB operation; + 0x02 - do not generate a SIP reply to the current REGISTER request. When used in ONREPLY_ROUTE, this parameter is

1 0

git:5.4:5cbec397: modules: readme files regenerated - modules ... [skip ci]
by Kamailio Dev 15 Sep '20

15 Sep '20

Module: kamailio Branch: 5.4 Commit: 5cbec397d4dbe338400aefacddcce69dd0547f39 URL: https://github.com/kamailio/kamailio/commit/5cbec397d4dbe338400aefacddcce69… Author: Kamailio Dev <kamailio.dev(a)kamailio.org> Committer: Kamailio Dev <kamailio.dev(a)kamailio.org> Date: 2020-09-15T18:01:22+02:00 modules: readme files regenerated - modules ... [skip ci] --- Modified: src/modules/registrar/README --- Diff: https://github.com/kamailio/kamailio/commit/5cbec397d4dbe338400aefacddcce69… Patch: https://github.com/kamailio/kamailio/commit/5cbec397d4dbe338400aefacddcce69… --- diff --git a/src/modules/registrar/README b/src/modules/registrar/README index fe9c969ce9..f4f5ccae0d 100644 --- a/src/modules/registrar/README +++ b/src/modules/registrar/README @@ -254,21 +254,22 @@ Chapter 1. Admin Guide If path support is enabled in the registrar module, a call to save(...) stores the values of the Path Header(s) along with the contact into usrloc. There are three modes regarding the reply to a REGISTER - including one or more Path HFs: + including one or more Path header fields: * off - stores the value of the Path headers into usrloc without passing it back to the UAC in the reply. * lazy - stores the Path header and passes it back to the UAC if - Path-support is indicated by the “path” param in the Supported HF. + Path-support is indicated by the “path” param in the Supported + header field. * strict - rejects the registration with “420 Bad Extension” if there's a Path header but no support for it is indicated by the UAC. Otherwise it's stored and passed back to the UAC. A call to lookup(...) always uses the path header if found, and inserts - it as Route HF either in front of the first Route HF, or after the last - Via HF if no Route is present. It also sets the destination uri to the - first Path uri, thus overwriting the received-uri, because NAT has to - be handled at the outbound-proxy of the UAC (the first hop after - client's NAT). + it as Route header field either in front of the first Route header + field, or after the last Via header field if no Route is present. It + also sets the destination uri to the first Path uri, thus overwriting + the received-uri, because NAT has to be handled at the outbound-proxy + of the UAC (the first hop after client's NAT). The whole process is transparent to the user, so no config changes are required beside setting the registrar-parameters “use_path” and @@ -341,10 +342,10 @@ Chapter 1. Admin Guide 3.1. default_expires (integer) - If the processed message contains neither Expires HFs nor expires - contact parameters, this value will be used for newly created usrloc - records. The parameter contains number of second to expire (for example - use 3600 for one hour). If it is set to a lower value than the + If the processed message contains neither Expires header fields nor + expires contact parameters, this value will be used for newly created + usrloc records. The parameter contains number of second to expire (for + example use 3600 for one hour). If it is set to a lower value than the “min_expires” parameter then it will be ignored. This parameter can be modified via ser config framework. A random value in a specific interval can be selected by using the default_expires_range parameter @@ -955,8 +956,8 @@ kamcmd cfg.set_now_int registrar use_expired_contacts 0 4.1. save(domain, [, flags [, uri]]) The function processes a REGISTER message. It can add, remove or modify - location records (in usrloc) depending on Contact and Expires HFs in - the REGISTER message. On success and when called from the + 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. @@ -966,7 +967,7 @@ kamcmd cfg.set_now_int registrar use_expired_contacts 0 then this must be name of the table which stores the contacts. * flags (optional) - the value may be a bitwise OR of the following flags: - + 0x01 - save the contacts only in memory cache without no DB + + 0x01 - save the contacts only in memory cache with no DB operation; + 0x02 - do not generate a SIP reply to the current REGISTER request. When used in ONREPLY_ROUTE, this parameter is

1 0

git:5.2:8e62b35f: registrar: Update documentation
by Henning Westerholt 15 Sep '20

15 Sep '20

Module: kamailio Branch: 5.2 Commit: 8e62b35f97ba34268fbde35599ecd1645f0d7f76 URL: https://github.com/kamailio/kamailio/commit/8e62b35f97ba34268fbde35599ecd16… Author: whosgonna <ben.whosgonna.com(a)gmail.com> Committer: Henning Westerholt <hw(a)skalatan.de> Date: 2020-09-15T15:50:10Z registrar: Update documentation - Fix double negative "without no DB operation". Changed to "with no DB operation". (cherry picked from commit be0382fa11920de972ddbcdbe17c3ff583da87e4) --- Modified: src/modules/registrar/doc/registrar_admin.xml --- Diff: https://github.com/kamailio/kamailio/commit/8e62b35f97ba34268fbde35599ecd16… Patch: https://github.com/kamailio/kamailio/commit/8e62b35f97ba34268fbde35599ecd16… --- diff --git a/src/modules/registrar/doc/registrar_admin.xml b/src/modules/registrar/doc/registrar_admin.xml index 7c4226ad3c..3edede4096 100644 --- a/src/modules/registrar/doc/registrar_admin.xml +++ b/src/modules/registrar/doc/registrar_admin.xml @@ -1026,7 +1026,7 @@ end <itemizedlist> <listitem> <para><emphasis>0x01</emphasis> - save the contacts only - in memory cache without no DB operation; + in memory cache with no DB operation; </para> </listitem> <listitem>

1 0

git:5.2:59cede26: registrar: Update documentation
by Henning Westerholt 15 Sep '20

15 Sep '20

Module: kamailio Branch: 5.2 Commit: 59cede2607d8847cfff96aa6221f00e0abbb625d URL: https://github.com/kamailio/kamailio/commit/59cede2607d8847cfff96aa6221f00e… Author: whosgonna <ben.whosgonna.com(a)gmail.com> Committer: Henning Westerholt <hw(a)skalatan.de> Date: 2020-09-15T15:50:15Z registrar: Update documentation - Replace all occurences of "HF" with "header field" - Replace all occurences of "HFs" with "header fields" (cherry picked from commit d936c6276b6d8e45efd87a4fc25a55b9c3ab1fce) --- Modified: src/modules/registrar/doc/registrar_admin.xml --- Diff: https://github.com/kamailio/kamailio/commit/59cede2607d8847cfff96aa6221f00e… Patch: https://github.com/kamailio/kamailio/commit/59cede2607d8847cfff96aa6221f00e… --- diff --git a/src/modules/registrar/doc/registrar_admin.xml b/src/modules/registrar/doc/registrar_admin.xml index 3edede4096..54bfea5ff6 100644 --- a/src/modules/registrar/doc/registrar_admin.xml +++ b/src/modules/registrar/doc/registrar_admin.xml @@ -28,7 +28,7 @@ If path support is enabled in the registrar module, a call to save(...) stores the values of the Path Header(s) along with the contact into usrloc. There are three modes regarding the reply to a REGISTER including - one or more Path HFs: + one or more Path header fields: </para> <itemizedlist> <listitem> @@ -42,7 +42,7 @@ <para> <emphasis>lazy</emphasis> - stores the Path header and passes it back to the UAC if Path-support is indicated - by the <quote>path</quote> param in the Supported HF. + by the <quote>path</quote> param in the Supported header field. </para> </listitem> <listitem> @@ -56,8 +56,8 @@ </itemizedlist> <para> A call to lookup(...) always uses the path header if - found, and inserts it as Route HF either in front of - the first Route HF, or after the last Via HF if no + found, and inserts it as Route header field either in front of + the first Route header field, or after the last Via header field if no Route is present. It also sets the destination uri to the first Path uri, thus overwriting the received-uri, because NAT has to be handled at the outbound-proxy of @@ -131,7 +131,7 @@ <title><varname>default_expires</varname> (integer)</title> <para> If the processed message contains neither Expires - <acronym>HFs</acronym> nor expires contact parameters, this value + header fields nor expires contact parameters, this value will be used for newly created usrloc records. The parameter contains number of second to expire (for example use 3600 for one hour). If it is set to a lower value than the <quote>min_expires</quote> parameter @@ -1003,7 +1003,7 @@ end </title> <para> The function processes a <emphasis>REGISTER</emphasis> message. It can add, remove or - modify location records (in usrloc) depending on Contact and Expires HFs in the + modify location records (in usrloc) depending on Contact and Expires header fields in the REGISTER message. On success and when called from the REQUEST_ROUTE, <quote>200 OK</quote> 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

1 0

git:5.3:9be13ba9: registrar: Update documentation
by Henning Westerholt 15 Sep '20

15 Sep '20

Module: kamailio Branch: 5.3 Commit: 9be13ba9668b1c0aea9122ef4d8bfbb22e29eabb URL: https://github.com/kamailio/kamailio/commit/9be13ba9668b1c0aea9122ef4d8bfbb… Author: whosgonna <ben.whosgonna.com(a)gmail.com> Committer: Henning Westerholt <hw(a)skalatan.de> Date: 2020-09-15T15:49:47Z registrar: Update documentation - Replace all occurences of "HF" with "header field" - Replace all occurences of "HFs" with "header fields" (cherry picked from commit d936c6276b6d8e45efd87a4fc25a55b9c3ab1fce) --- Modified: src/modules/registrar/doc/registrar_admin.xml --- Diff: https://github.com/kamailio/kamailio/commit/9be13ba9668b1c0aea9122ef4d8bfbb… Patch: https://github.com/kamailio/kamailio/commit/9be13ba9668b1c0aea9122ef4d8bfbb… --- diff --git a/src/modules/registrar/doc/registrar_admin.xml b/src/modules/registrar/doc/registrar_admin.xml index 1a8942d3b4..8b83e3c00e 100644 --- a/src/modules/registrar/doc/registrar_admin.xml +++ b/src/modules/registrar/doc/registrar_admin.xml @@ -28,7 +28,7 @@ If path support is enabled in the registrar module, a call to save(...) stores the values of the Path Header(s) along with the contact into usrloc. There are three modes regarding the reply to a REGISTER including - one or more Path HFs: + one or more Path header fields: </para> <itemizedlist> <listitem> @@ -42,7 +42,7 @@ <para> <emphasis>lazy</emphasis> - stores the Path header and passes it back to the UAC if Path-support is indicated - by the <quote>path</quote> param in the Supported HF. + by the <quote>path</quote> param in the Supported header field. </para> </listitem> <listitem> @@ -56,8 +56,8 @@ </itemizedlist> <para> A call to lookup(...) always uses the path header if - found, and inserts it as Route HF either in front of - the first Route HF, or after the last Via HF if no + found, and inserts it as Route header field either in front of + the first Route header field, or after the last Via header field if no Route is present. It also sets the destination uri to the first Path uri, thus overwriting the received-uri, because NAT has to be handled at the outbound-proxy of @@ -131,7 +131,7 @@ <title><varname>default_expires</varname> (integer)</title> <para> If the processed message contains neither Expires - <acronym>HFs</acronym> nor expires contact parameters, this value + header fields nor expires contact parameters, this value will be used for newly created usrloc records. The parameter contains number of second to expire (for example use 3600 for one hour). If it is set to a lower value than the <quote>min_expires</quote> parameter @@ -1048,7 +1048,7 @@ request_route { </title> <para> The function processes a <emphasis>REGISTER</emphasis> message. It can add, remove or - modify location records (in usrloc) depending on Contact and Expires HFs in the + modify location records (in usrloc) depending on Contact and Expires header fields in the REGISTER message. On success and when called from the REQUEST_ROUTE, <quote>200 OK</quote> 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

1 0

git:5.3:edbafff7: registrar: Update documentation
by Henning Westerholt 15 Sep '20

15 Sep '20

Module: kamailio Branch: 5.3 Commit: edbafff7df51d2dc16f3a379cfb0d333c37439fd URL: https://github.com/kamailio/kamailio/commit/edbafff7df51d2dc16f3a379cfb0d33… Author: whosgonna <ben.whosgonna.com(a)gmail.com> Committer: Henning Westerholt <hw(a)skalatan.de> Date: 2020-09-15T15:49:43Z registrar: Update documentation - Fix double negative "without no DB operation". Changed to "with no DB operation". (cherry picked from commit be0382fa11920de972ddbcdbe17c3ff583da87e4) --- Modified: src/modules/registrar/doc/registrar_admin.xml --- Diff: https://github.com/kamailio/kamailio/commit/edbafff7df51d2dc16f3a379cfb0d33… Patch: https://github.com/kamailio/kamailio/commit/edbafff7df51d2dc16f3a379cfb0d33… --- diff --git a/src/modules/registrar/doc/registrar_admin.xml b/src/modules/registrar/doc/registrar_admin.xml index 67e13e09e3..1a8942d3b4 100644 --- a/src/modules/registrar/doc/registrar_admin.xml +++ b/src/modules/registrar/doc/registrar_admin.xml @@ -1071,7 +1071,7 @@ request_route { <itemizedlist> <listitem> <para><emphasis>0x01</emphasis> - save the contacts only - in memory cache without no DB operation; + in memory cache with no DB operation; </para> </listitem> <listitem>

1 0

git:5.4:76864d45: registrar: Update documentation
by Henning Westerholt 15 Sep '20

15 Sep '20

Module: kamailio Branch: 5.4 Commit: 76864d4508ff4e1d9d909480663819db272aae48 URL: https://github.com/kamailio/kamailio/commit/76864d4508ff4e1d9d909480663819d… Author: whosgonna <ben.whosgonna.com(a)gmail.com> Committer: Henning Westerholt <hw(a)skalatan.de> Date: 2020-09-15T15:48:45Z registrar: Update documentation - Fix double negative "without no DB operation". Changed to "with no DB operation". (cherry picked from commit be0382fa11920de972ddbcdbe17c3ff583da87e4) --- Modified: src/modules/registrar/doc/registrar_admin.xml --- Diff: https://github.com/kamailio/kamailio/commit/76864d4508ff4e1d9d909480663819d… Patch: https://github.com/kamailio/kamailio/commit/76864d4508ff4e1d9d909480663819d… --- diff --git a/src/modules/registrar/doc/registrar_admin.xml b/src/modules/registrar/doc/registrar_admin.xml index e3140965d4..75a4104fb2 100644 --- a/src/modules/registrar/doc/registrar_admin.xml +++ b/src/modules/registrar/doc/registrar_admin.xml @@ -1174,7 +1174,7 @@ kamcmd cfg.set_now_int registrar use_expired_contacts 0 <itemizedlist> <listitem> <para><emphasis>0x01</emphasis> - save the contacts only - in memory cache without no DB operation; + in memory cache with no DB operation; </para> </listitem> <listitem>

1 0

git:5.4:acce084f: registrar: Update documentation
by Henning Westerholt 15 Sep '20

15 Sep '20

Module: kamailio Branch: 5.4 Commit: acce084fcab7249d52862bef0f4c32ed488222bc URL: https://github.com/kamailio/kamailio/commit/acce084fcab7249d52862bef0f4c32e… Author: whosgonna <ben.whosgonna.com(a)gmail.com> Committer: Henning Westerholt <hw(a)skalatan.de> Date: 2020-09-15T15:49:00Z registrar: Update documentation - Replace all occurences of "HF" with "header field" - Replace all occurences of "HFs" with "header fields" (cherry picked from commit d936c6276b6d8e45efd87a4fc25a55b9c3ab1fce) --- Modified: src/modules/registrar/doc/registrar_admin.xml --- Diff: https://github.com/kamailio/kamailio/commit/acce084fcab7249d52862bef0f4c32e… Patch: https://github.com/kamailio/kamailio/commit/acce084fcab7249d52862bef0f4c32e… --- diff --git a/src/modules/registrar/doc/registrar_admin.xml b/src/modules/registrar/doc/registrar_admin.xml index 75a4104fb2..461605f3d0 100644 --- a/src/modules/registrar/doc/registrar_admin.xml +++ b/src/modules/registrar/doc/registrar_admin.xml @@ -28,7 +28,7 @@ If path support is enabled in the registrar module, a call to save(...) stores the values of the Path Header(s) along with the contact into usrloc. There are three modes regarding the reply to a REGISTER including - one or more Path HFs: + one or more Path header fields: </para> <itemizedlist> <listitem> @@ -42,7 +42,7 @@ <para> <emphasis>lazy</emphasis> - stores the Path header and passes it back to the UAC if Path-support is indicated - by the <quote>path</quote> param in the Supported HF. + by the <quote>path</quote> param in the Supported header field. </para> </listitem> <listitem> @@ -56,8 +56,8 @@ </itemizedlist> <para> A call to lookup(...) always uses the path header if - found, and inserts it as Route HF either in front of - the first Route HF, or after the last Via HF if no + found, and inserts it as Route header field either in front of + the first Route header field, or after the last Via header field if no Route is present. It also sets the destination uri to the first Path uri, thus overwriting the received-uri, because NAT has to be handled at the outbound-proxy of @@ -131,7 +131,7 @@ <title><varname>default_expires</varname> (integer)</title> <para> If the processed message contains neither Expires - <acronym>HFs</acronym> nor expires contact parameters, this value + header fields nor expires contact parameters, this value will be used for newly created usrloc records. The parameter contains number of second to expire (for example use 3600 for one hour). If it is set to a lower value than the <quote>min_expires</quote> parameter @@ -1151,7 +1151,7 @@ kamcmd cfg.set_now_int registrar use_expired_contacts 0 </title> <para> The function processes a <emphasis>REGISTER</emphasis> message. It can add, remove or - modify location records (in usrloc) depending on Contact and Expires HFs in the + modify location records (in usrloc) depending on Contact and Expires header fields in the REGISTER message. On success and when called from the REQUEST_ROUTE, <quote>200 OK</quote> 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

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev