Module: kamailio
Branch: master
Commit: ca886ffa64db8cc209dcc7098ffb69902464da72
URL: https://github.com/kamailio/kamailio/commit/ca886ffa64db8cc209dcc7098ffb699…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2021-05-11T17:31:12+02:00
modules: readme files regenerated - siputils ... [skip ci]
---
Modified: src/modules/siputils/README
---
Diff: https://github.com/kamailio/kamailio/commit/ca886ffa64db8cc209dcc7098ffb699…
Patch: https://github.com/kamailio/kamailio/commit/ca886ffa64db8cc209dcc7098ffb699…
---
diff --git a/src/modules/siputils/README b/src/modules/siputils/README
index a1aeae393c..453179d5a1 100644
--- a/src/modules/siputils/README
+++ b/src/modules/siputils/README
@@ -449,8 +449,9 @@ modparam("auth", "rpid_avp", "$avp(myrpid)")
Inserting the call-id in the internal list, which is checked when
further replies arrive. Any 183 reply that is received during the
- timeout value will be converted to a 180 message. Please note that you
- need to set a positive timeout value in order to use this function.
+ timeout value will be converted to a 180 message with removed SDP body.
+ Please note that you need to set a positive ring_timeout value in order
+ to use this function.
The function returns TRUE on success, and FALSE during processing
failures.
Module: kamailio
Branch: master
Commit: 212840c367e4b2945bb105e1fd087543f7fdf316
URL: https://github.com/kamailio/kamailio/commit/212840c367e4b2945bb105e1fd08754…
Author: Henning Westerholt <hw(a)skalatan.de>
Committer: Henning Westerholt <hw(a)skalatan.de>
Date: 2021-05-11T15:24:01Z
siptuils: small doc extension for ring filter functionality
---
Modified: src/modules/siputils/doc/siputils_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/212840c367e4b2945bb105e1fd08754…
Patch: https://github.com/kamailio/kamailio/commit/212840c367e4b2945bb105e1fd08754…
---
diff --git a/src/modules/siputils/doc/siputils_admin.xml b/src/modules/siputils/doc/siputils_admin.xml
index 5764c152d4..8e7140385d 100644
--- a/src/modules/siputils/doc/siputils_admin.xml
+++ b/src/modules/siputils/doc/siputils_admin.xml
@@ -281,8 +281,9 @@ modparam("auth", "rpid_avp", "$avp(myrpid)")
<para>
Inserting the call-id in the internal list, which is checked when
further replies arrive. Any 183 reply that is received during the
- timeout value will be converted to a 180 message. Please note that you
- need to set a positive timeout value in order to use this function.
+ timeout value will be converted to a 180 message with removed SDP body.
+ Please note that you need to set a positive ring_timeout value in order
+ to use this function.
</para>
<para>
The function returns TRUE on success, and FALSE during processing failures.
Module: kamailio
Branch: master
Commit: 9c2fea2df70e3fe609324a9d868efe9998bcda10
URL: https://github.com/kamailio/kamailio/commit/9c2fea2df70e3fe609324a9d868efe9…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2021-05-11T15:46:16+02:00
modules: readme files regenerated - siputils ... [skip ci]
---
Modified: src/modules/siputils/README
---
Diff: https://github.com/kamailio/kamailio/commit/9c2fea2df70e3fe609324a9d868efe9…
Patch: https://github.com/kamailio/kamailio/commit/9c2fea2df70e3fe609324a9d868efe9…
---
diff --git a/src/modules/siputils/README b/src/modules/siputils/README
index 87d3ecf9e4..a1aeae393c 100644
--- a/src/modules/siputils/README
+++ b/src/modules/siputils/README
@@ -96,7 +96,7 @@ Gabriel Vasile
4.30. is_reply()
4.31. is_gruu([uri])
4.32. is_supported(option)
- 4.33. is_first_hop()
+ 4.33. is_first_hop([mode])
4.34. sip_p_charging_vector(flags)
4.35. contact_param_encode(pname, saddr)
4.36. contact_param_decode(pname)
@@ -217,7 +217,7 @@ Chapter 1. Admin Guide
4.30. is_reply()
4.31. is_gruu([uri])
4.32. is_supported(option)
- 4.33. is_first_hop()
+ 4.33. is_first_hop([mode])
4.34. sip_p_charging_vector(flags)
4.35. contact_param_encode(pname, saddr)
4.36. contact_param_decode(pname)
@@ -438,7 +438,7 @@ modparam("auth", "rpid_avp", "$avp(myrpid)")
4.30. is_reply()
4.31. is_gruu([uri])
4.32. is_supported(option)
- 4.33. is_first_hop()
+ 4.33. is_first_hop([mode])
4.34. sip_p_charging_vector(flags)
4.35. contact_param_encode(pname, saddr)
4.36. contact_param_decode(pname)
@@ -994,24 +994,37 @@ if(is_gruu()) { ... }
if (is_supported("outbound")) { ... }
...
-4.33. is_first_hop()
+4.33. is_first_hop([mode])
The function returns true if the proxy is first hop after the original
- sender. For incoming SIP requests, it means there is only one Via
- header. For incoming SIP replies, it means that top Record-Route URI is
- 'myself' and source address is not matching it (to avoid detecting in
- case of local loops). The detection is done only when Record-Route has
- an IP address in its URI (for a domain, it returns -1/false).
+ sender based on a best effort estimation by checking Via and
+ Record-Route headers.
+
+ For incoming SIP requests, it means there is only one Via header.
+
+ For incoming SIP replies, if mode==0, it means that top Record-Route
+ URI is 'myself' and source address is not matching local IP (to avoid
+ detecting in case of local loops). Therefore for mode==0 the detection
+ is done only when Record-Route has an IP address in its URI (for a
+ domain, it returns -1/false). If mode==1, then the check of local IP is
+ no longer done, only if top Record-Route is myself, returning true also
+ if there is a domain, assuming that is expected no looping can happen
+ based on config rules.
Note that it does not detect spirals, which can have the condition for
replies true also in the case of additional SIP reply reception.
+ Parameter mode is optional and can be an integer or a varaible holding
+ an integer. If not provided, the behaviour is like mode==0.
+
This function can be used from ANY_ROUTE.
Example 1.42. is_first_hop() usage
...
if(is_first_hop()) { ... }
...
+if(is_first_hop_mode("1")) { ... }
+...
4.34. sip_p_charging_vector(flags)
Module: kamailio
Branch: master
Commit: 425ba921288c8d5a6ae3076287d0cf39c735a8fd
URL: https://github.com/kamailio/kamailio/commit/425ba921288c8d5a6ae3076287d0cf3…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2021-05-11T15:38:14+02:00
siputils: docs - updates to is_first_hop() for mode parameter
---
Modified: src/modules/siputils/doc/siputils_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/425ba921288c8d5a6ae3076287d0cf3…
Patch: https://github.com/kamailio/kamailio/commit/425ba921288c8d5a6ae3076287d0cf3…
---
diff --git a/src/modules/siputils/doc/siputils_admin.xml b/src/modules/siputils/doc/siputils_admin.xml
index 4667e42f63..5764c152d4 100644
--- a/src/modules/siputils/doc/siputils_admin.xml
+++ b/src/modules/siputils/doc/siputils_admin.xml
@@ -1169,22 +1169,35 @@ if (is_supported("outbound")) { ... }
</section>
<section id="siputils.f.is_first_hop">
<title>
- <function moreinfo="none">is_first_hop()</function>
+ <function moreinfo="none">is_first_hop([mode])</function>
</title>
<para>
The function returns true if the proxy is first hop after the
- original sender. For incoming SIP requests, it means there is only
- one Via header. For incoming SIP replies, it means that top
- Record-Route URI is 'myself' and source address is not matching it
- (to avoid detecting in case of local loops). The detection is done
- only when Record-Route has an IP address in its URI (for a domain,
- it returns -1/false).
+ original sender based on a best effort estimation by checking Via
+ and Record-Route headers.
+ </para>
+ <para>
+ For incoming SIP requests, it means there is only one Via header.
+ </para>
+ <para>
+ For incoming SIP replies, if mode==0, it means that top Record-Route
+ URI is 'myself' and source address is not matching local IP (to avoid
+ detecting in case of local loops). Therefore for mode==0 the detection
+ is done only when Record-Route has an IP address in its URI (for a domain,
+ it returns -1/false). If mode==1, then the check of local IP is no
+ longer done, only if top Record-Route is myself, returning true also if
+ there is a domain, assuming that is expected no looping can happen
+ based on config rules.
</para>
<para>
Note that it does not detect spirals, which can have the condition
for replies true also in the case of additional SIP reply reception.
</para>
<para>
+ Parameter mode is optional and can be an integer or a varaible holding
+ an integer. If not provided, the behaviour is like mode==0.
+ </para>
+ <para>
This function can be used from ANY_ROUTE.
</para>
<example>
@@ -1193,6 +1206,8 @@ if (is_supported("outbound")) { ... }
...
if(is_first_hop()) { ... }
...
+if(is_first_hop_mode("1")) { ... }
+...
</programlisting>
</example>
</section>
### Description
According to design logic HELD request need to send a carrier LIS server. Now lost module sends this request to the preconfigured server via `http_client/httpcon` param.
I prefer to use dynamic LIS server discovery according to [rfc7216#section-4](https://tools.ietf.org/html/rfc7216#section-4) and [rfc5986#section-4](https://tools.ietf.org/html/rfc5986#section-4).
So dynamic LIS discovery works as:
1. Kamailio send reverse `.in-addr.arpa.` or `.ip6.arpa.` DNS request and caller host DNS name;
2. Kamailio send `LIS:HELD` NAPTR request for a resolved caller hostname and LIS server.
3. Kamailio send HELD request for resolved LIS address.
So do get working dynamic LIS discovery required to implement two DNS requests.
If any DNS request will fail, then `lost_held_query` function returns an error code.
To define required dynamic LIS discovery I suggest use an empty string ("") or NULL value ($null) as the first ("con") function param.
This feature request for discussion with lost module author (Wolfgang Kampichler @wkampich) and other interest devs.
The ticket may be closed at any time.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2574
<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for feature requests.
If you have questions about using Kamailio or related to its configuration file, ask on sr-users mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot the issue.
If you submit a feature request (or enhancement) add the description of what you would like to be added.
If there is no content to be filled in a section, the entire section can be removed.
You can delete the comments from the template sections when filling.
You can delete next line and everything above before submitting (it is a comment).
-->
### Description
Currently uac_reg_lookup don't have provision to pass the mode parameter but its implement in core fuction:
https://github.com/kamailio/kamailio/blob/951c9ac9adaccc1c35e152593cb3c2e7f…
This should be imported to kemi as well as cfg function.
<!--
Explain what you did, what you expected to happen, and what actually happened.
-->
### Expected behavior
lookup in uacreg should be supported using username based also, currently uuid based support is only there.
#### Actual observed behavior
#### Debugging Data
```
(paste your debugging data here)
```
#### Log Messages
<!--
Check the syslog file and if there are relevant log messages printed by Kamailio, add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
```
(paste your log messages here)
```
#### SIP Traffic
<!--
If the issue is exposed by processing specific SIP messages, grab them with ngrep or save in a pcap file, then add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
```
(paste your sip traffic here)
```
### Possible Solutions
<!--
If you found a solution or workaround for the issue, describe it. Ideally, provide a pull request with a improvement.
-->
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
5.4.5
```
(paste your output here)
```
* **Operating System**:
<!--
Details about the operating system, the type: Linux (e.g.,: Debian 8.4, Ubuntu 16.04, CentOS 7.1, ...), MacOS, xBSD, Solaris, ...;
Kernel details (output of `uname -a`)
-->
```
(paste your output here)
```
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2714
Module: kamailio
Branch: master
Commit: 624da2b7deb2539064be70a7566783fd36a15886
URL: https://github.com/kamailio/kamailio/commit/624da2b7deb2539064be70a7566783f…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2021-05-07T08:09:11+02:00
uac: docs for uac_reg_lookup_uri()
---
Modified: src/modules/uac/doc/uac_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/624da2b7deb2539064be70a7566783f…
Patch: https://github.com/kamailio/kamailio/commit/624da2b7deb2539064be70a7566783f…
---
diff --git a/src/modules/uac/doc/uac_admin.xml b/src/modules/uac/doc/uac_admin.xml
index 352d038ea2..52362af1e3 100644
--- a/src/modules/uac/doc/uac_admin.xml
+++ b/src/modules/uac/doc/uac_admin.xml
@@ -1005,6 +1005,31 @@ if(uac_reg_lookup("$rU", "$ru"))
{
lookup("location");
}
+...
+ </programlisting>
+ </example>
+ </section>
+ <section id="uac.f.uac_reg_lookup_uri">
+ <title>
+ <function moreinfo="none">uac_reg_lookup_uri(uri, dst)</function>
+ </title>
+ <para>
+ This function sets the PV dst to SIP URI that correspond to the URI user
+ in uac registrations table. The uri can contain pseudo-variables and
+ dst must be the name of a pseudo-variable.
+ </para>
+ <para>
+ This function can be used from ANY_ROUTE.
+ </para>
+ <example>
+ <title><function>uac_reg_lookup_uri</function> usage</title>
+ <programlisting format="linespecific">
+...
+
+if(uac_reg_lookup("$var(uri)", "$ru"))
+{
+ lookup("location");
+}
...
</programlisting>
</example>
```
LD (gcc) [M app_lua_sr.so] app_lua_sr.so
CC (gcc) [M lwsc.so] lwsc_mod.o
lwsc_mod.c: In function 'lwsc_get_endpoint':
lwsc_mod.c:533:13: error: 'struct lws_context_creation_info' has no member named 'ws_ping_pong_interval'
533 | ep->crtinfo.ws_ping_pong_interval = 5; /*secs*/
| ^
make[2]: *** [../../Makefile.rules:100: lwsc_mod.o] Error 1
make[1]: *** [Makefile:511: modules] Error 1
make[1]: Leaving directory '/root/rpmbuild/BUILD/kamailio-5.5.0/src'
make: *** [Makefile:34: every-module] Error 2
```
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2727
With several days before releasing v5.5.0, let's see if there is any tuning that should be done to default kamailio.cfg.
Note that the proposals and discussions must focus around current config, if any loaded module should have different values for parameters, if the routing blocks should be adjusted to cope better with common use cases.
This is not for asking refactoring or adding major changes/features. In such cases, the option is to make PR to add to `misc/examples/` (new files or to existing files).
>From the discussions done for 5.4.0, the next were considered for the future, however I haven't seen much activity on the community forums related to them during past months, so I am not sure they worth at this moment, but let list them for a starting point:
* keepalive to be done with usrloc module to get round trip timer, etc
* dlgs module loaded to see the basic stats about active calls
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2719
<!-- Kamailio Pull Request Template -->
<!--
IMPORTANT:
- for detailed contributing guidelines, read:
https://github.com/kamailio/kamailio/blob/master/.github/CONTRIBUTING.md
- pull requests must be done to master branch, unless they are backports
of fixes from master branch to a stable branch
- backports to stable branches must be done with 'git cherry-pick -x ...'
- code is contributed under BSD for core and main components (tm, sl, auth, tls)
- code is contributed GPLv2 or a compatible license for the other components
- GPL code is contributed with OpenSSL licensing exception
-->
#### Pre-Submission Checklist
<!-- Go over all points below, and after creating the PR, tick all the checkboxes that apply -->
<!-- All points should be verified, otherwise, read the CONTRIBUTING guidelines from above-->
<!-- If you're unsure about any of these, don't hesitate to ask on sr-dev mailing list -->
- [x] Commit message has the format required by CONTRIBUTING guide
- [x] Commits are split per component (core, individual modules, libs, utils, ...)
- [x] Each component has a single commit (if not, squash them into one commit)
- [x] No commits to README files for modules (changes must be done to docbook files
in `doc/` subfolder, the README file is autogenerated)
#### Type Of Change
- [x] Small bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds new functionality)
- [ ] Breaking change (fix or feature that would change existing functionality)
#### Checklist:
<!-- Go over all points below, and after creating the PR, tick the checkboxes that apply -->
- [ ] PR should be backported to stable branches
- [x] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
It looks like the db query is made before checking the configuration parameters for the following features:
- internal keep-alive mechanism
- contact-expired callback execution
For example, although keepalive mode is turned off, the location table is periodically queried.
This is also true when there is no usrloc:contact-expired route.
In this commit, checks are added before these two db queries.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2726
-- Commit Summary --
* Merge pull request #1 from kamailio/master
* Merge pull request #2 from kamailio/master
* Merge pull request #3 from kamailio/master
* usrloc: unnecessary periodic db queries cancelled
-- File Changes --
M src/modules/usrloc/dlist.c (4)
M src/modules/usrloc/udomain.c (6)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2726.patchhttps://github.com/kamailio/kamailio/pull/2726.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/2726