#### Pre-Submission Checklist
- [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 …
[View More](non-breaking change which adds new functionality)
- [ ] Breaking change (fix or feature that would change existing functionality)
#### Checklist:
- [X] PR should be backported to stable branches
- [X] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
srjson_DeleteDoc(ctx->jreq) is already called in jsonrpc_clean_context(ctx). Calling it twice causes a crash due to a double free attempt.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/1839
-- Commit Summary --
* jsonrpcs: fix double free crash
-- File Changes --
M src/modules/jsonrpcs/jsonrpcs_mod.c (1)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/1839.patchhttps://github.com/kamailio/kamailio/pull/1839.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/1839
[View Less]
Hello,
it's about the time to set the milestones to the next major release -
v5.3.0. There are 6 new modules and many other enhancements to existing
components in git master branch, also during the last irc devel meeting
it was proposed to freeze after summer holidays.
At this moment I would propose Wednesday, September 4, 2019 to freeze
the development. Then the release should be about one month later, after
testing interval.
In case there are people willing a bit more time for development, …
[View More]we can
freeze one week later, September 11, or another date -- your
suggestions here.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
[View Less]
<!-- 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, …
[View More]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
- [ ] Small bug fix (non-breaking change which fixes an issue)
- [ X] 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 -->
rr module: expose record_route_preset to KEMI
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2051
-- Commit Summary --
* module rr: KEMI expose record_route_preset
-- File Changes --
M src/modules/rr/rr_mod.c (36)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2051.patchhttps://github.com/kamailio/kamailio/pull/2051.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/2051
[View Less]
Module: kamailio
Branch: master
Commit: 26d25b1c9e3654642f9f85c02492297ec1c03e75
URL: https://github.com/kamailio/kamailio/commit/26d25b1c9e3654642f9f85c02492297…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2019-09-04T00:19:38+02:00
nathelper: docs - added missing xml tags for the new nat test option
---
Modified: src/modules/nathelper/doc/nathelper_admin.xml
---
Diff: https://github.com/kamailio/…
[View More]kamailio/commit/26d25b1c9e3654642f9f85c02492297…
Patch: https://github.com/kamailio/kamailio/commit/26d25b1c9e3654642f9f85c02492297…
---
diff --git a/src/modules/nathelper/doc/nathelper_admin.xml b/src/modules/nathelper/doc/nathelper_admin.xml
index 71b8e92479..b5a5b08167 100644
--- a/src/modules/nathelper/doc/nathelper_admin.xml
+++ b/src/modules/nathelper/doc/nathelper_admin.xml
@@ -666,6 +666,7 @@ fix_nated_register();
URI port differs from the source port of the request (Warning: this is
might be legal or even intended combination in non NATted scenarios)
</para></listitem>
+ <listitem><para>
<emphasis>256</emphasis> - Test if the SDP connection address is different
from source IP address. It will work also with multiple connection address
lines.
[View Less]
<!-- 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 …
[View More]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
- [ ] Small bug fix (non-breaking change which fixes an issue)
- [x] 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 -->
test sdp c line and sip source ip address is matched.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2045
-- Commit Summary --
* nathelper: test sdp c line and sip source ip address is matched
* nathelper : flag 256 is added to nathelper documentation
-- File Changes --
M src/modules/nathelper/doc/nathelper_admin.xml (72)
M src/modules/nathelper/nathelper.c (47)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2045.patchhttps://github.com/kamailio/kamailio/pull/2045.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/2045
[View Less]
Module: kamailio
Branch: master
Commit: ce3bfaa843f0efabe49bd7087e89506f3f211669
URL: https://github.com/kamailio/kamailio/commit/ce3bfaa843f0efabe49bd7087e89506…
Author: Yasin Caner <caner_yaso(a)hotmail.com>
Committer: Henning Westerholt <hw(a)skalatan.de>
Date: 2019-09-03T23:14:16+02:00
nathelper: extend nat_uac_test() to test for mismatch between connection and source IP (GH #2045)
- extend nat_uac_test function to test for mismatch between connection and source IP
- add …
[View More]documentation for this new flag 256 to module docs as well
- based on pull request GH #2045 with smaller adaptions
---
Modified: src/modules/nathelper/doc/nathelper_admin.xml
Modified: src/modules/nathelper/nathelper.c
---
Diff: https://github.com/kamailio/kamailio/commit/ce3bfaa843f0efabe49bd7087e89506…
Patch: https://github.com/kamailio/kamailio/commit/ce3bfaa843f0efabe49bd7087e89506…
---
diff --git a/src/modules/nathelper/doc/nathelper_admin.xml b/src/modules/nathelper/doc/nathelper_admin.xml
index e3c47e2d70..71b8e92479 100644
--- a/src/modules/nathelper/doc/nathelper_admin.xml
+++ b/src/modules/nathelper/doc/nathelper_admin.xml
@@ -666,6 +666,10 @@ fix_nated_register();
URI port differs from the source port of the request (Warning: this is
might be legal or even intended combination in non NATted scenarios)
</para></listitem>
+ <emphasis>256</emphasis> - Test if the SDP connection address is different
+ from source IP address. It will work also with multiple connection address
+ lines.
+ </para></listitem>
</itemizedlist>
<para>
All flags can be bitwise combined, the test returns true if any of
diff --git a/src/modules/nathelper/nathelper.c b/src/modules/nathelper/nathelper.c
index 27015b7bd8..6baaa64528 100644
--- a/src/modules/nathelper/nathelper.c
+++ b/src/modules/nathelper/nathelper.c
@@ -100,7 +100,7 @@ MODULE_VERSION
#define NAT_UAC_TEST_O_1918 0x20
#define NAT_UAC_TEST_WS 0x40
#define NAT_UAC_TEST_C_PORT 0x80
-
+#define NAT_UAC_TEST_SDP_CLINE 0x100
#define DEFAULT_NATPING_STATE 1
@@ -123,6 +123,7 @@ static int fixup_fix_sdp(void **param, int param_no);
static int fixup_add_contact_alias(void **param, int param_no);
static int add_rcv_param_f(struct sip_msg *, char *, char *);
static int nh_sip_reply_received(sip_msg_t *msg);
+static int test_sdp_cline(struct sip_msg *msg);
static void nh_timer(unsigned int, void *);
static int mod_init(void);
@@ -1332,6 +1333,54 @@ static int contact_rport(struct sip_msg *msg)
}
}
+/**
+* test SDP C line ip address and source IP address match
+* if all ip address matches, return 0
+* returns unmatched ip address count
+* on parse error, returns -1
+*/
+static int test_sdp_cline(struct sip_msg *msg){
+ sdp_session_cell_t* session;
+ struct ip_addr cline_addr;
+ int sdp_session_num = 0;
+ int result = 0;
+
+ if(parse_sdp(msg) < 0) {
+ LM_ERR("Unable to parse sdp body\n");
+ return -1;
+ }
+
+ for(;;){
+ session = get_sdp_session(msg, sdp_session_num);
+ if(!session)
+ break;
+
+ if(!(session->ip_addr.len > 0 && session->ip_addr.s))
+ break;
+
+ if(session->pf==AF_INET){
+ if(str2ipbuf(&session->ip_addr,&cline_addr)<0){
+ LM_ERR("Couldn't get sdp c line IP address\n");
+ return -1;
+ }
+ }else if(session->pf==AF_INET6){
+ if(str2ip6buf(&session->ip_addr, &cline_addr)<0){
+ LM_ERR("Couldn't get sdp c line IP address\n");
+ return -1;
+ }
+ }else{
+ LM_ERR("Couldn't get sdp address type\n");
+ return -1;
+ }
+
+ if(ip_addr_cmp(&msg->rcv.src_ip,&cline_addr)){
+ result++;
+ }
+ sdp_session_num++;
+ }
+
+ return sdp_session_num - result;
+}
/*
* test for occurrence of RFC1918 IP address in SDP
*/
@@ -1441,6 +1490,12 @@ static int nat_uac_test(struct sip_msg *msg, int tests)
if((tests & NAT_UAC_TEST_C_PORT) && (contact_rport(msg) > 0))
return 1;
+ /**
+ * test if sdp c line ip address matches with sip source address
+ */
+ if((tests & NAT_UAC_TEST_SDP_CLINE) && (test_sdp_cline(msg) > 0))
+ return 1;
+
/* no test succeeded */
return -1;
}
[View Less]
<!-- 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, …
[View More]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 -->
- [ ] Commit message has the format required by CONTRIBUTING guide
- [ ] Commits are split per component (core, individual modules, libs, utils, ...)
- [ ] Each component has a single commit (if not, squash them into one commit)
- [ ] 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
- [ ] 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
- [ ] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
Issue in fetching resid param fixed for phonenum module
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2054
-- Commit Summary --
* phonenum_fix
-- File Changes --
M src/modules/phonenum/phonenum_mod.c (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2054.patchhttps://github.com/kamailio/kamailio/pull/2054.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/2054
[View Less]
Related to #2043.
When using the database for dialogs, the `caller_contact` and `callee_contact` columns are too short.
The following seems to help.
```
ALTER TABLE kamailio.dialog ALTER COLUMN caller_contact TYPE varchar(255);
ALTER TABLE kamailio.dialog ALTER COLUMN callee_contact TYPE varchar(255);
```
--
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/2053
Module: kamailio
Branch: master
Commit: b9cfe696db5f7bbcbe6fc8c3ae63b4f9d640e311
URL: https://github.com/kamailio/kamailio/commit/b9cfe696db5f7bbcbe6fc8c3ae63b4f…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2019-09-02T13:47:22+02:00
modules: readme files regenerated - phonenum ... [skip ci]
---
Modified: src/modules/phonenum/README
---
Diff: https://github.com/kamailio/kamailio/commit/…
[View More]b9cfe696db5f7bbcbe6fc8c3ae63b4f…
Patch: https://github.com/kamailio/kamailio/commit/b9cfe696db5f7bbcbe6fc8c3ae63b4f…
---
diff --git a/src/modules/phonenum/README b/src/modules/phonenum/README
index 842e2cfcc7..ebe872869b 100644
--- a/src/modules/phonenum/README
+++ b/src/modules/phonenum/README
@@ -26,6 +26,7 @@ Daniel-Constantin Mierla
3. Parameters
3.1. smode (int)
+ 3.2. resid (str)
4. Functions
@@ -37,8 +38,9 @@ Daniel-Constantin Mierla
List of Examples
1.1. Set smode parameter
- 1.2. phonenum_match usage
- 1.3. phonenum_match_cn usage
+ 1.2. Set resid parameter
+ 1.3. phonenum_match usage
+ 1.4. phonenum_match_cn usage
Chapter 1. Admin Guide
@@ -53,6 +55,7 @@ Chapter 1. Admin Guide
3. Parameters
3.1. smode (int)
+ 3.2. resid (str)
4. Functions
@@ -95,10 +98,11 @@ Chapter 1. Admin Guide
3. Parameters
3.1. smode (int)
+ 3.2. resid (str)
3.1. smode (int)
- Phone number search mode.
+ Phone number search mode (not in use yet).
Default value is “0”.
@@ -107,6 +111,23 @@ Chapter 1. Admin Guide
modparam("phonenum", "smode", 0)
...
+3.2. resid (str)
+
+ Preregister result container id during initialization, enabling the use
+ of the module in KEMI scripts. In native Kamailio.cfg file,
+ registration is done when parsing config and finding variables.
+
+ Default value is “” (empty).
+
+ Example 1.2. Set resid parameter
+...
+modparam("phonenum", "resid", "src")
+...
+if(phonenum_match("1-484-555-8888", "src")) {
+ ...
+}
+...
+
4. Functions
4.1. phonenum_match(num, pvc)
@@ -115,14 +136,14 @@ modparam("phonenum", "smode", 0)
4.1. phonenum_match(num, pvc)
Match num against the libphonenumber and set the attributes inside the
- pvc container. The function has to be called before accessing a key
- via: $phn(pvc=>key).
+ pvc result container. The function has to be called before accessing a
+ key via: $phn(pvc=>key).
The parameters can be static strings or strings with variables.
It can be used from ANY_ROUTE.
- Example 1.2. phonenum_match usage
+ Example 1.3. phonenum_match usage
...
if(phonenum_match("1-484-555-8888", "src")) {
if($phn(src=>valid)==1) {
@@ -144,7 +165,7 @@ if(phonenum_match("1-484-555-8888", "src")) {
It can be used from ANY_ROUTE.
- Example 1.3. phonenum_match_cn usage
+ Example 1.4. phonenum_match_cn usage
...
if(phonenum_match_cn("1-484-555-8888", "US", "src")) {
if($phn(src=>valid)==1) {
[View Less]
Module: kamailio
Branch: master
Commit: d2bac426192c074368bf78014e0d1d0ca97f3274
URL: https://github.com/kamailio/kamailio/commit/d2bac426192c074368bf78014e0d1d0…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2019-09-02T13:45:16+02:00
phonenum: docs for resid parameter
---
Modified: src/modules/phonenum/doc/phonenum_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/…
[View More]d2bac426192c074368bf78014e0d1d0…
Patch: https://github.com/kamailio/kamailio/commit/d2bac426192c074368bf78014e0d1d0…
---
diff --git a/src/modules/phonenum/doc/phonenum_admin.xml b/src/modules/phonenum/doc/phonenum_admin.xml
index 402edfdb60..d30c2026ee 100644
--- a/src/modules/phonenum/doc/phonenum_admin.xml
+++ b/src/modules/phonenum/doc/phonenum_admin.xml
@@ -71,7 +71,7 @@
<section id="phonenum.p.smode">
<title><varname>smode</varname> (int)</title>
<para>
- Phone number search mode.
+ Phone number search mode (not in use yet).
</para>
<para>
<emphasis>
@@ -87,7 +87,31 @@ modparam("phonenum", "smode", 0)
</programlisting>
</example>
</section>
-
+ <section id="phonenum.p.resid">
+ <title><varname>resid</varname> (str)</title>
+ <para>
+ Preregister result container id during initialization, enabling the use
+ of the module in KEMI scripts. In native &kamailio;.cfg file, registration
+ is done when parsing config and finding variables.
+ </para>
+ <para>
+ <emphasis>
+ Default value is <quote></quote> (empty).
+ </emphasis>
+ </para>
+ <example>
+ <title>Set <varname>resid</varname> parameter</title>
+ <programlisting format="linespecific">
+...
+modparam("phonenum", "resid", "src")
+...
+if(phonenum_match("1-484-555-8888", "src")) {
+ ...
+}
+...
+</programlisting>
+ </example>
+ </section>
</section>
<section>
@@ -98,7 +122,7 @@ modparam("phonenum", "smode", 0)
</title>
<para>
Match num against the libphonenumber and set the attributes inside
- the pvc container. The function has to be called before accessing
+ the pvc result container. The function has to be called before accessing
a key via: $phn(pvc=>key).
</para>
<para>
[View Less]
### Description
Not shure is this relevant issue.
according to rfc3261:
> When a tag is generated by a UA for insertion into a request or
> response, it MUST be globally unique and cryptographically random
> with at least 32 bits of randomness.
Kamailio has 16 instead and distribution is not good.
I look at tags for 419485 sip flows (different callid) and table below (top keys ordered by count):
tag suffix; count for different flows with this suffix
ed54 6258
d118 5988
56ce …
[View More]5923
a7a5 5220
de51 2150
82d8 1143
cf52 890
af92 740
7b5f 534
85f7 307
e553 163
7f7e 138
1d55 130
1afe 62
5a69 43
7caa 18
8474 18
9db2 18
11d3 18
f9ff 18
5420 17
dae6 17
908d 17
ede4 17
09ee 17
96be 17
25dc 17
af6d 16
2506 16
3da0 16
f161 16
1c29 16
#### SIP Traffic
To: <sip:039*101@host:5071>;tag=555d2c3eafafcba8ac92b676e91bb6ed.58eb
--
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/1164
[View Less]
Module: kamailio
Branch: master
Commit: e4ae7c7a7c7e8696870535e3399c8b9ddf585a06
URL: https://github.com/kamailio/kamailio/commit/e4ae7c7a7c7e8696870535e3399c8b9…
Author: Henning Westerholt <hw(a)skalatan.de>
Committer: Henning Westerholt <hw(a)skalatan.de>
Date: 2019-09-02T09:54:21+02:00
tm: improve from-tags to include more randomness and use the recommended size from RFC 3261 (GH #1164)
- improve from-tag generation for uac request to include more randomness (request uri)
- …
[View More]use the recommended size of 32 bit randomness from RFC 3261
- implementation could be further improved by using a cryptographic hash algorithm
- related to GH #1164
---
Modified: src/modules/tm/dlg.c
Modified: src/modules/tm/rpc_uac.c
Modified: src/modules/tm/t_msgbuilder.c
Modified: src/modules/tm/uac.c
Modified: src/modules/tm/uac.h
---
Diff: https://github.com/kamailio/kamailio/commit/e4ae7c7a7c7e8696870535e3399c8b9…
Patch: https://github.com/kamailio/kamailio/commit/e4ae7c7a7c7e8696870535e3399c8b9…
[View Less]
Module: kamailio
Branch: master
Commit: bc96f46f8a9f0beefffe281398671d216c839f20
URL: https://github.com/kamailio/kamailio/commit/bc96f46f8a9f0beefffe281398671d2…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2019-09-01T19:24:17+02:00
CONTRIBUTING.md: removed garbage bullet from commit mesage details
---
Modified: .github/CONTRIBUTING.md
---
Diff: https://github.com/kamailio/kamailio/commit/…
[View More]bc96f46f8a9f0beefffe281398671d2…
Patch: https://github.com/kamailio/kamailio/commit/bc96f46f8a9f0beefffe281398671d2…
---
diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md
index d22cbc0ce2..ea6ba9cdd8 100644
--- a/.github/CONTRIBUTING.md
+++ b/.github/CONTRIBUTING.md
@@ -94,7 +94,6 @@ Please start always with the prefix of the component (subsystem) that is modifie
* first line (subject line) has to contain meaningful text about what that commit
does, do not put just a reference to bug tracker or pull request items
- * t
* commit message must describe the changes done by the patch
* other details (e.g., how to reproduce, backtrace, sip packets, ...) belong
to content (comments) of the pull request. Example:
[View Less]
Hi Daniel and Kamailio developers,
Could you consider adding record_route_preset to KEMI in 5.3? If you
like I can do the PR. Hope it is not too late.
Regards
Anthony Alba
Hello,
with the perspective that Python2 is going to be removed from the major
Linux distributes starting with the beginning of next year, the work to
upgrade kamcli to run with Python3 has been started.
>From now on, master branch of kamcli is expected to work only with Python3:
* https://github.com/kamailio/kamcli
There is still work to be done to upgrade all the code, but any use of
it should be done with Python3 and eventual issues to be filed on bug
tracker. Of course, pull …
[View More]requests are welcome as always!
Who wants to use the version for Python2 has to use the code from git
branch v1.2-python2. That branch is probably not going to receive any
new feature, it will be kept for use with older systems (as well as a
running option during the upgrade period to Python3).
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
[View Less]
<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for bug reports.
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…
[View More]Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot the issue.
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
phonenum module is not working with KEMI framework, when debugged I found phonenum module functions "pv_parse_phonenum_name" "sr_phonenum_add_item" are not invoked with KEMI framework. With default config file these modules are invoked from config parser.
<!--
Explain what you did, what you expected to happen, and what actually happened.
-->
I am using lua KEMI framework and included phonenum module
### Troubleshooting
#### Reproduction
1. Any KEMI Framework
2. Include phonenum module
3. Test to validate phonenum
<!--
If the issue can be reproduced, describe how it can be done.
-->
#### Debugging Data
<!--
If you got a core dump, use gdb to extract troubleshooting data - full backtrace,
local variables and the list of the code at the issue location.
gdb /path/to/kamailio /path/to/corefile
bt full
info locals
list
If you are familiar with gdb, feel free to attach more of what you consider to
be relevant.
-->
```
(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 fix.
-->
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
(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/1883
[View Less]
With the default `*_contact ` address columns as `varchar(128)`, TOPOS is unable to handle inserting values into the database when using IPv6, which often has contact information hitting or exceeding 256 chars (tested with PostgreSQL). Perhaps these columns can be switched to the `text` type.
--
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/2043
Hello,
just discovered what I consider to be an inconsistency in naming and
behaviour for event_route blocks for local-request and local-response
and starting a discussion here to see how to move on.
The event_route[tm:local-request] is executed before sending there local
generated request out (allowing also to change its content, drop,
etc...). This event route is quite popular event route used when the
local generated requests need to be checked or updates.
The event_route[tm:local-…
[View More]response] is executed after the response is
sent out, obviously no possibility to change anymore the content. I
haven't checked the code for event_route[sl:local-response], but based
on commit message should be the same.
I haven't used the local-response so far at all, today after a
discussion on sr-users I wanted to enable kemi callback for
tm:local-response and I noticed that behaviour in the code, even I
expected to be like local-request (before sending out).
I am not sure how much used are the event routes for tm:local-response
and sl:local-response, I haven't seen any questions about them so far on
mailing lists, that's why I am asking here if would make sense to rename
them like tm:local-response-sent and sl:local-response-sent to properly
reflect when they are executed. I am expecting that they are very few
used so far, so no big head ache with upgrades and bringing some
consistency around (this change to be part of next major release).
It can stay like now with proper documentation, however in the future if
one want and event route for local responses before being sent out,
there will be more confusion, imo ...
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
[View Less]
Module: kamailio
Branch: master
Commit: d3211fdff1cfb9596a5339eff2184f1a91508bd2
URL: https://github.com/kamailio/kamailio/commit/d3211fdff1cfb9596a5339eff2184f1…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2019-08-27T12:49:20+02:00
tm: event_route[local-response] is actually executed after response is sent
- change back after previous commit
- somehow it is incoherent with event_route[local-request] that …
[View More]is
before sending out, allowing to change the content
---
Modified: src/modules/tm/doc/event_routes.xml
---
Diff: https://github.com/kamailio/kamailio/commit/d3211fdff1cfb9596a5339eff2184f1…
Patch: https://github.com/kamailio/kamailio/commit/d3211fdff1cfb9596a5339eff2184f1…
---
diff --git a/src/modules/tm/doc/event_routes.xml b/src/modules/tm/doc/event_routes.xml
index 22cce59abc..5c6111a075 100644
--- a/src/modules/tm/doc/event_routes.xml
+++ b/src/modules/tm/doc/event_routes.xml
@@ -79,7 +79,7 @@ event_route [tm:local-request] {
<function moreinfo="none">event_route[tm:local-response]</function>
</title>
<para>
- Executed when the tm module is about to send a local generated,
+ Executed after the tm module sent a local generated,
transaction stateful response.
</para>
<example>
[View Less]
Module: kamailio
Branch: master
Commit: 755e15fcfc4d36cdeff974a7ab701f3cdd445c78
URL: https://github.com/kamailio/kamailio/commit/755e15fcfc4d36cdeff974a7ab701f3…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2019-08-27T09:46:47+02:00
modules: readme files regenerated - tm ... [skip ci]
---
Modified: src/modules/tm/README
---
Diff: https://github.com/kamailio/kamailio/commit/755e15fcfc4d36cdeff974a7ab701f3……
[View More]Patch: https://github.com/kamailio/kamailio/commit/755e15fcfc4d36cdeff974a7ab701f3…
---
diff --git a/src/modules/tm/README b/src/modules/tm/README
index 7f0970a4e3..8cbefc75b8 100644
--- a/src/modules/tm/README
+++ b/src/modules/tm/README
@@ -269,8 +269,8 @@ Daniel-Constantin Mierla
1.94. t_uac_send usage
1.95. t_get_status_code usage
1.96. event_route[tm:branch-failure:id] usage
- 1.1. event_route[tm:local-request] usage
- 1.2. event_route[tm:local-response] usage
+ 1.97. event_route[tm:local-request] usage
+ 1.98. event_route[tm:local-response] usage
Chapter 1. Admin Guide
@@ -2994,11 +2994,12 @@ event_route[tm:branch-failure:myroute] {
6.2. event_route[tm:local-request]
Executed when the tm module generates a request, in other words, the
- request originates from and a transaction is created for it. The source
- of the requests can be tm itself or other modules that use tm
- internally (e.g., msilo, uac). The event route is executed if it is
- defined in the native config file. To execute the equivalent callback
- when using KEMI scripting, see the 'event_callback' module parameter.
+ request originates from Kamailio and a transaction is created for it.
+ The source of the requests can be tm itself or other modules that use
+ tm internally (e.g., msilo, uac). The event route is executed if it is
+ defined in the native Kamailio config file. To execute the equivalent
+ callback when using KEMI scripting, see the 'event_callback' module
+ parameter.
The request can still be updated, i.e., changes are possible to R-URI
($ru), destination URI ($du) or the send socket ($fs).
[View Less]
Module: kamailio
Branch: master
Commit: be8ba0dab1ee36ae517cef52c023cd83440f4af9
URL: https://github.com/kamailio/kamailio/commit/be8ba0dab1ee36ae517cef52c023cd8…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2019-08-27T09:31:51+02:00
modules: readme files regenerated - tm ... [skip ci]
---
Modified: src/modules/tm/README
---
Diff: https://github.com/kamailio/kamailio/commit/be8ba0dab1ee36ae517cef52c023cd8……
[View More]Patch: https://github.com/kamailio/kamailio/commit/be8ba0dab1ee36ae517cef52c023cd8…
---
diff --git a/src/modules/tm/README b/src/modules/tm/README
index 47598f379e..7f0970a4e3 100644
--- a/src/modules/tm/README
+++ b/src/modules/tm/README
@@ -149,7 +149,7 @@ Daniel-Constantin Mierla
6. Event Routes
- 6.1. event_route[tm:branch-failure]
+ 6.1. event_route[tm:branch-failure:id]
6.2. event_route[tm:local-request]
6.3. event_route[tm:local-response]
@@ -268,9 +268,9 @@ Daniel-Constantin Mierla
1.93. t_is_retr_async_reply usage
1.94. t_uac_send usage
1.95. t_get_status_code usage
- 1.96. event_route[tm:branch-failure] usage
- 1.97. event_route[tm:local-request] usage
- 1.98. event_route[tm:local-response] usage
+ 1.96. event_route[tm:branch-failure:id] usage
+ 1.1. event_route[tm:local-request] usage
+ 1.2. event_route[tm:local-response] usage
Chapter 1. Admin Guide
@@ -400,7 +400,7 @@ Chapter 1. Admin Guide
6. Event Routes
- 6.1. event_route[tm:branch-failure]
+ 6.1. event_route[tm:branch-failure:id]
6.2. event_route[tm:local-request]
6.3. event_route[tm:local-response]
@@ -2964,21 +2964,21 @@ if($var(ts) == 500) { ... }
6. Event Routes
- 6.1. event_route[tm:branch-failure]
+ 6.1. event_route[tm:branch-failure:id]
6.2. event_route[tm:local-request]
6.3. event_route[tm:local-response]
-6.1. event_route[tm:branch-failure]
+6.1. event_route[tm:branch-failure:id]
Named branch failure routes can be defined to run when when a failure
response is received. This allows handling failures on individual
branches, for example, retrying an alternative outbound flow.
- The format of the event_route name is "tm:branch-failure:<name>" and is
+ The format of the event_route name is "tm:branch-failure:<id>" and is
enabled with the t_on_branch_failure function. This event_route uses
the BRANCH_FAILURE_ROUTE route type.
- Example 1.96. event_route[tm:branch-failure] usage
+ Example 1.96. event_route[tm:branch-failure:id] usage
...
request_route {
...
@@ -2993,8 +2993,15 @@ event_route[tm:branch-failure:myroute] {
6.2. event_route[tm:local-request]
- Executed after the tm module has sent a local generated, transaction
- stateful request.
+ Executed when the tm module generates a request, in other words, the
+ request originates from and a transaction is created for it. The source
+ of the requests can be tm itself or other modules that use tm
+ internally (e.g., msilo, uac). The event route is executed if it is
+ defined in the native config file. To execute the equivalent callback
+ when using KEMI scripting, see the 'event_callback' module parameter.
+
+ The request can still be updated, i.e., changes are possible to R-URI
+ ($ru), destination URI ($du) or the send socket ($fs).
Example 1.97. event_route[tm:local-request] usage
...
@@ -3006,8 +3013,8 @@ event_route [tm:local-request] {
6.3. event_route[tm:local-response]
- Executed after the tm module has sent a local generated, transaction
- stateful response.
+ Executed when the tm module is about to send a local generated,
+ transaction stateful response.
Example 1.98. event_route[tm:local-response] usage
...
[View Less]
…nnection
<!-- 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, …
[View More]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 -->
- [ X] PR should be backported to stable branches
- [ X] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
Return the proper error code to not stop message processing in reply_route.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2047
-- Commit Summary --
* siptrace: check if trace_to_database is set before checking the db connection
-- File Changes --
M src/modules/siptrace/siptrace.c (6)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2047.patchhttps://github.com/kamailio/kamailio/pull/2047.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/2047
[View Less]
Module: kamailio
Branch: master
Commit: b241fc7e1d20098dd8b0666297303fe7255587e8
URL: https://github.com/kamailio/kamailio/commit/b241fc7e1d20098dd8b0666297303fe…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2019-08-27T09:17:18+02:00
tm: docs - clarifications about event routes
---
Modified: src/modules/tm/doc/event_routes.xml
---
Diff: https://github.com/kamailio/kamailio/commit/…
[View More]b241fc7e1d20098dd8b0666297303fe…
Patch: https://github.com/kamailio/kamailio/commit/b241fc7e1d20098dd8b0666297303fe…
---
diff --git a/src/modules/tm/doc/event_routes.xml b/src/modules/tm/doc/event_routes.xml
index adda5536ed..b969695c9a 100644
--- a/src/modules/tm/doc/event_routes.xml
+++ b/src/modules/tm/doc/event_routes.xml
@@ -10,20 +10,20 @@
<section id="tm.e.branch-failure">
<title>
- <function moreinfo="none">event_route[tm:branch-failure]</function>
+ <function moreinfo="none">event_route[tm:branch-failure:id]</function>
</title>
<para>
Named branch failure routes can be defined to run when when a failure
response is received. This allows handling failures on individual
branches, for example, retrying an alternative outbound flow.
</para>
- <para>
- The format of the event_route name is "tm:branch-failure:<name>"
- and is enabled with the t_on_branch_failure function.
- This event_route uses the BRANCH_FAILURE_ROUTE route type.
- </para>
+ <para>
+ The format of the event_route name is "tm:branch-failure:<id>"
+ and is enabled with the t_on_branch_failure function.
+ This event_route uses the BRANCH_FAILURE_ROUTE route type.
+ </para>
<example>
- <title><function>event_route[tm:branch-failure]</function> usage</title>
+ <title><function>event_route[tm:branch-failure:id]</function> usage</title>
<programlisting>
...
request_route {
@@ -44,7 +44,17 @@ event_route[tm:branch-failure:myroute] {
<function moreinfo="none">event_route[tm:local-request]</function>
</title>
<para>
- Executed after the tm module has sent a local generated, transaction stateful request.
+ Executed when the tm module generates a request, in other words,
+ the request originates from &kamailio; and a transaction is created
+ for it. The source of the requests can be tm itself or other modules
+ that use tm internally (e.g., msilo, uac). The event route is executed
+ if it is defined in the native &kamailio; config file. To execute
+ the equivalent callback when using KEMI scripting, see the
+ 'event_callback' module parameter.
+ </para>
+ <para>
+ The request can still be updated, i.e., changes are possible to
+ R-URI ($ru), destination URI ($du) or the send socket ($fs).
</para>
<example>
<title><function>event_route[tm:local-request]</function> usage</title>
@@ -63,7 +73,8 @@ event_route [tm:local-request] {
<function moreinfo="none">event_route[tm:local-response]</function>
</title>
<para>
- Executed after the tm module has sent a local generated, transaction stateful response.
+ Executed when the tm module is about to send a local generated,
+ transaction stateful response.
</para>
<example>
<title><function>event_route[tm:local-response]</function> usage</title>
[View Less]
My Kamailio master based test sip proxy has two rtpengine sets:
```
# sip-proxy_ctl rtpengine.show all
{
url: udp:192.26.134.1:6050
set: 0
index: 0
weight: 1
disabled: 0
recheck_ticks: 0
}
{
url: udp:192.26.134.40:6050
set: 1
index: 1
weight: 1
disabled: 0
recheck_ticks: 0
}
```
Config calls set_rtpengine_set() with two set argument followed by rtpengine_offer():
```
set_rtpengine_set("1", "0");
rtpengine_offer("...");
```
Debug shows that sip proxy sends TWO offer commands to the
…
[View More]rtpproxy in the first set 1 and NONE to the rtpproxy in the second set 0.
Debug at set 1 engine:
```
Aug 19 18:06:08 buster-10-0 rtpengine[1314]: NOTICE: [5e1407211cc50fd9]: Creating new call
Aug 19 18:06:08 buster-10-0 rtpengine[1314]: INFO: [5e1407211cc50fd9]: Replying to 'offer' from 192.26.134.1:33284 (elapsed time 0.000812 sec)
Aug 19 18:06:08 buster-10-0 rtpengine[1314]: INFO: [5e1407211cc50fd9]: Received command 'offer' from 192.26.134.1:33284
Aug 19 18:06:08 buster-10-0 rtpengine[1314]: INFO: [5e1407211cc50fd9]: Replying to 'offer' from 192.26.134.1:33284 (elapsed time 0.005247 sec)
```
This looks like a bug to me, since according to README, rtpengine should first send the offer to an engine in the first set and then to an engine in the second set.
--
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/2039
[View Less]
Module: kamailio
Branch: master
Commit: 78a62e19955ada9d67245031780bad29035b0ef2
URL: https://github.com/kamailio/kamailio/commit/78a62e19955ada9d67245031780bad2…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2019-08-26T16:02:22+02:00
modules: readme files regenerated - tm ... [skip ci]
---
Modified: src/modules/tm/README
---
Diff: https://github.com/kamailio/kamailio/commit/78a62e19955ada9d67245031780bad2……
[View More]Patch: https://github.com/kamailio/kamailio/commit/78a62e19955ada9d67245031780bad2…
---
diff --git a/src/modules/tm/README b/src/modules/tm/README
index d9643f2ce1..47598f379e 100644
--- a/src/modules/tm/README
+++ b/src/modules/tm/README
@@ -1161,8 +1161,11 @@ modparam("tm", "reparse_on_dns_failover", 0)
Sets reply route block, to which control is passed when a reply is
received that has no associated transaction. The reply is passed to the
- core for stateless forwarding after the route block execution unless it
- returns 0.
+ core for stateless forwarding after the route block execution unless
+ drop is executed (or it returns 0).
+
+ If KEMI is used, the parameter has to be the KEMI function name, which
+ receives a string parameter with the event name.
Example 1.24. Set on_sl_reply parameter
...
[View Less]
Module: kamailio
Branch: master
Commit: fa3c97a331b06ea675e830f418771e94375216cc
URL: https://github.com/kamailio/kamailio/commit/fa3c97a331b06ea675e830f418771e9…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2019-08-26T15:52:29+02:00
tm: docs - note about kemi for on_sl_reply parameter
---
Modified: src/modules/tm/doc/params.xml
---
Diff: https://github.com/kamailio/kamailio/commit/…
[View More]fa3c97a331b06ea675e830f418771e9…
Patch: https://github.com/kamailio/kamailio/commit/fa3c97a331b06ea675e830f418771e9…
---
diff --git a/src/modules/tm/doc/params.xml b/src/modules/tm/doc/params.xml
index c7923d8c25..e17137c0cd 100644
--- a/src/modules/tm/doc/params.xml
+++ b/src/modules/tm/doc/params.xml
@@ -711,7 +711,11 @@ modparam("tm", "reparse_on_dns_failover", 0)
Sets reply route block, to which control is passed when a
reply is received that has no associated transaction.
The reply is passed to the core for stateless forwarding after
- the route block execution unless it returns 0.
+ the route block execution unless drop is executed (or it returns 0).
+ </para>
+ <para>
+ If KEMI is used, the parameter has to be the KEMI function name, which
+ receives a string parameter with the event name.
</para>
<example>
<title>Set <varname>on_sl_reply</varname> parameter</title>
@@ -727,7 +731,7 @@ onreply_route["stateless_replies"] {
</programlisting>
</example>
</section>
-
+
<section id ="tm.p.contacts_avp">
<title><varname>contacts_avp</varname> (string)</title>
<para>
[View Less]
Module: kamailio
Branch: master
Commit: b38fe1b5b6061c07a050b329bacd55377bdd45ef
URL: https://github.com/kamailio/kamailio/commit/b38fe1b5b6061c07a050b329bacd553…
Author: Henning Westerholt <hw(a)skalatan.de>
Committer: Henning Westerholt <hw(a)skalatan.de>
Date: 2019-08-25T13:20:17+02:00
core: remove STATS #define, depends on non-existing module, does not compile
- remove STATS #define, depends on non-existing snmp module, does not compile
- could be used to print e.g. number of …
[View More]packets on SIGUSR1
- these numbers were reported through SNMP
- replaced by Kamailio statistics support
- remove stats.c and stats.h files
---
Modified: src/Makefile.defs
Modified: src/core/cfg.y
Modified: src/core/forward.c
Modified: src/core/forward.h
Modified: src/core/receive.c
Modified: src/core/ver_defs.h
Modified: src/main.c
Removed: src/core/stats.c
Removed: src/core/stats.h
---
Diff: https://github.com/kamailio/kamailio/commit/b38fe1b5b6061c07a050b329bacd553…
Patch: https://github.com/kamailio/kamailio/commit/b38fe1b5b6061c07a050b329bacd553…
[View Less]
Hello,
I used from kamailio with MMTel features as AS in my IMS scenario and I
wanted to send UDR diameter request from AS to my HSS. According to my
study I should use "diameter_request" or "diameter_request_async" in
ims_diameter_server module . but some problem exists in diameter_request
function which caused "json" string as input of "diameter_request" ignored
and fault happened.
I added parse and checking "json" string in diameter_request function in
ims_diameter_server.c file :
if …
[View More](message) {
if (get_str_fparam(&s_message, msg, (fparam_t*)message) <
0) {
LM_ERR("failed to get json string\n");
return -1;
}
LM_DBG("json %.*s\n", s_message.len, s_message.s);
}
also cdp_get_session function in cdp module has problem with "lock and
unlock session" and " AAASessionsLock(hash);
" doesn't work correctly. I comment " AAASessionsLock(hash);" and "
AAASessionsUnlock(hash);"
I recompiled ims_diameter_server and cdp modules again
called below part in request_route of my configuration :
if(is_method("REGISTER"))
{
diameter_request("hss domain address", "16777217", "306", "{
'avpCode':263 , ....}");
}
this worked correctly and UDR request sent to hss .
[View Less]
### Description
I have a Kamailio with several Gateways configured. It's Probing is done using Dispatcher module and setting the GW state with value "8". If more than 15 Gw's are set as "8" with a probing frequency of 1min, only 15 GW will be probed each minute.
I can't find a configuration for this and have already posted this issue in the sr-users mailing list
I'm using Kamailio 5.2.0.
Best Regards
--
You are receiving this because you are subscribed to this thread.
Reply to this email …
[View More]directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2041
[View Less]
Module: kamailio
Branch: master
Commit: c8132a25d412c4fb907b27dc4f4d24a479fc2770
URL: https://github.com/kamailio/kamailio/commit/c8132a25d412c4fb907b27dc4f4d24a…
Author: Henning Westerholt <hw(a)skalatan.de>
Committer: Henning Westerholt <hw(a)skalatan.de>
Date: 2019-08-24T12:29:57+02:00
uac: small whitespace change in docs
---
Modified: src/modules/uac/doc/uac_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/c8132a25d412c4fb907b27dc4f4d24a…
Patch: https://…
[View More]github.com/kamailio/kamailio/commit/c8132a25d412c4fb907b27dc4f4d24a…
---
diff --git a/src/modules/uac/doc/uac_admin.xml b/src/modules/uac/doc/uac_admin.xml
index e3a1abd35c..3ac4cc2a17 100644
--- a/src/modules/uac/doc/uac_admin.xml
+++ b/src/modules/uac/doc/uac_admin.xml
@@ -570,9 +570,9 @@ modparam("uac", "reg_gc_interval", 60)
interfaces are available.
</para>
<para>
- A send socket in the $uac_reg variable used together with the uac_req_send()
- function will override this parameter. A socket value in the uacreg table will
- also override the parameter for this particular entry.
+ A send socket in the $uac_reg variable used together with the uac_req_send()
+ function will override this parameter. A socket value in the uacreg table will
+ also override the parameter for this particular entry.
</para>
<para>
<emphasis>
[View Less]
Module: kamailio
Branch: master
Commit: 8c8aaa62db91c0b4ea25f09b4214947a6b80950b
URL: https://github.com/kamailio/kamailio/commit/8c8aaa62db91c0b4ea25f09b4214947…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2019-08-24T12:01:42+02:00
modules: readme files regenerated - uac ... [skip ci]
---
Modified: src/modules/uac/README
---
Diff: https://github.com/kamailio/kamailio/commit/8c8aaa62db91c0b4ea25f09b4214947……
[View More]Patch: https://github.com/kamailio/kamailio/commit/8c8aaa62db91c0b4ea25f09b4214947…
---
diff --git a/src/modules/uac/README b/src/modules/uac/README
index 72722e0cc4..d2f1a180d6 100644
--- a/src/modules/uac/README
+++ b/src/modules/uac/README
@@ -567,9 +567,12 @@ modparam("uac", "reg_gc_interval", 60)
Default socket to be used for generating registration requests and
sending requests with the function uac_req_send(). Useful e.g. when
- several public interfaces are available. A send socket in the $uac_reg
- variable used together with the uac_req_send() function will override
- this parameter.
+ several public interfaces are available.
+
+ A send socket in the $uac_reg variable used together with the
+ uac_req_send() function will override this parameter. A socket value in
+ the uacreg table will also override the parameter for this particular
+ entry.
By default no default socket is defined, the send socket is choosen
from the “tm” module when the requests is send out.
@@ -1079,6 +1082,9 @@ event_route[uac:reply] {
* reg_delay - delay initial registration with at least reg_delay
seconds, e.g.,: 3
+ * socket - Used socket for sending out registration requests, e.g.:,
+ udp:192.168.0.125:5060
+
The module takes care of sending REGISTER and refresh registrations
before they expire.
[View Less]
Module: kamailio
Branch: 5.1
Commit: d7730b1c271b7699267fb4ddd9afb2ab3548105c
URL: https://github.com/kamailio/kamailio/commit/d7730b1c271b7699267fb4ddd9afb2a…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2019-08-24T10:46:47+02:00
modules: readme files regenerated - modules ... [skip ci]
---
Modified: src/modules/ims_registrar_scscf/README
---
Diff: https://github.com/kamailio/kamailio/commit/…
[View More]d7730b1c271b7699267fb4ddd9afb2a…
Patch: https://github.com/kamailio/kamailio/commit/d7730b1c271b7699267fb4ddd9afb2a…
---
diff --git a/src/modules/ims_registrar_scscf/README b/src/modules/ims_registrar_scscf/README
index 3401e825ef..79dc6846a1 100644
--- a/src/modules/ims_registrar_scscf/README
+++ b/src/modules/ims_registrar_scscf/README
@@ -1,4 +1,4 @@
-IMS Usrloc PCSCF Module
+IMS Registrar SCSCF Module
Jason Penton
@@ -810,31 +810,31 @@ Chapter 2. Frequently Asked Questions
2.1.
- Where can I find more about Kamailio?
+ Where can I find more about Kamailio?
- Take a look at https://www.kamailio.org/.
+ Take a look at https://www.kamailio.org/.
2.2.
- Where can I post a question about this module?
+ Where can I post a question about this module?
- First at all check if your question was already answered on one of our
- mailing lists:
- * User Mailing List -
- https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
- * Developer Mailing List -
- https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
+ First at all check if your question was already answered on one of our
+ mailing lists:
+ * User Mailing List -
+ https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
+ * Developer Mailing List -
+ https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
- E-mails regarding any stable Kamailio release should be sent to
- <sr-users(a)lists.kamailio.org> and e-mails regarding development
- versions should be sent to <sr-dev(a)lists.kamailio.org>.
+ E-mails regarding any stable Kamailio release should be sent to
+ <sr-users(a)lists.kamailio.org> and e-mails regarding development
+ versions should be sent to <sr-dev(a)lists.kamailio.org>.
- If you want to keep the mail private, send it to
- <sr-users(a)lists.kamailio.org>.
+ If you want to keep the mail private, send it to
+ <sr-users(a)lists.kamailio.org>.
2.3.
- How can I report a bug?
+ How can I report a bug?
- Please follow the guidelines provided at:
- https://github.com/kamailio/kamailio/issues.
+ Please follow the guidelines provided at:
+ https://github.com/kamailio/kamailio/issues.
[View Less]
Document title is fixed
<!-- 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)…
[View More]
- 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
- [ ] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
Document title is fixed
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2042
-- Commit Summary --
* ims_registrar_scscf : document title is fixed
-- File Changes --
M src/modules/ims_registrar_scscf/doc/ims_registrar_scscf.xml (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2042.patchhttps://github.com/kamailio/kamailio/pull/2042.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/2042
[View Less]
Hello,
at couple of events I participated during the past few months, I was
asked about support of STIR/SHAKEN (caller identity
authentication/verification), which is a hot topic these days at least
in USA, aiming to combat "fraudulent" robo-calling. Therefore I thought
of share some details with everyone in the community about the state in
Kamailio, writing to both devs and users, the information being relevant
for everyone.
We already have the (related) module named auth_identity, available
…
[View More]since 2008 (iirc):
- https://www.kamailio.org/docs/modules/stable/modules/auth_identity.html
But it implements the previous iteration of the specs for caller
identity, respectively RFC 4474:
- https://tools.ietf.org/html/rfc4474
However, that RFC is obsoleted by 8224 (the latest core specs for
STIR/SHAKEN):
- https://tools.ietf.org/html/rfc8224
Then, there are also RFCs 8225 and 8226 to add to the core specs.
Should anyone be interested to implement STIR/SHAKEN specs in a modules,
I would suggest to start from auth_identity -- might not be much work to
update it to become conform with latest specs (a new module can be
created, of course, even when starting from auth_identity).
However, these specs are about signing the SIP request (the INVITE) with
special PKI certificate. It can be done easily with embedded scripts
such as Lua or Python (inline execution in native kamailio.cfg or using
kemi scripts). At Kamailio World 2019, one of the participants I
discussed with told me they already implemented using Lua.
That's it for a starting point, if anyone wants to discuss more, just
reply to sr-users and add your comments or ask the questions.
If someone wants to go ahead and work on a C module, announce yourself
to avoid duplicate work of others, and use sr-dev if you need assistance
on module development.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
[View Less]
… reload
<!-- 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 …
[View More]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 -->
- [ ] Commit message has the format required by CONTRIBUTING guide
- [ ] Commits are split per component (core, individual modules, libs, utils, ...)
- [ ] Each component has a single commit (if not, squash them into one commit)
- [ ] 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
- [ ] 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
- [ ] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2038
-- Commit Summary --
* Module:rtpengine: memory leak is fixed, if no rtpengine in list while reload
-- File Changes --
M src/modules/rtpengine/rtpengine_db.c (1)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2038.patchhttps://github.com/kamailio/kamailio/pull/2038.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/2038
[View Less]
Hello,
We facing an issue on capturing sip message in Kamailio(Version: 5.2.3).
The scenario is very simple.
UAC Kamailio UAS
|--------INVITE--------->| |
| |-------INVITE------->|
| |<------100 Trying----|
|<-------100 Trying------| |
| |<------200 Ok--------|
|<-------200 Ok----------| |
In this simple …
[View More]scenario, we can't catch any reply messages in between the
Kamailio and UAC. We have tried reply_route, onreply_route,
and onsend_route. But no one work to grep that reply on that side.
onsend_route was bad try as its only for forwarded reply message. Is there
any other magic to capture those replies. A debug=3 log message attached
here.
Thanks,
Salah
[View Less]
<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for bug reports.
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…
[View More]Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot the issue.
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
I've noticed PKG memory increasing since enabling the topoh module last week in a significant manner (~7MB per worker over 3000 calls split between 4 workers). Removing the topoh module removed the memory usage.
Here is a pkg dump of one of the process post 3000 calls:
https://paste.ubuntu.com/p/85KYg7gD2z/
### Additional Information
```kamailio 5.3.0-dev4 (x86_64/linux) 6d43ea-dirty. ```
I'm unsure why it's tagged dirty, as I simply cloned master and reset to 6d43eacd6d5b78fe857267e70b7fa85519a7d5b6.
I do plan to test this on dev7, however an unrelated issue is preventing me from testing this with my app_ruby based code.
--
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/2027
[View Less]
Hi,
I'm trying to register to a SIP provider (v5.2.4), so I added in kamailio.cfg:
...
loadmodule "uac.so"
...
modparam("rr", "append_fromtag", 1)
modparam("uac", "credential", "user:host_provider_ip:password")
modparam("uac", "reg_retry_interval", 300)
Seems that nothing happens after a service restart.
I also tried :
`kamcmd uac.reg_dump
error: 500 - command uac.reg_dump not found`
Is there something I misunderstood ?
Thanks in advanced !
--
You are receiving this because you …
[View More]are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2036
[View Less]
Module: kamailio
Branch: master
Commit: 4acc8aa71b50efc0f8ec073d711dda27b928e991
URL: https://github.com/kamailio/kamailio/commit/4acc8aa71b50efc0f8ec073d711dda2…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2019-08-19T11:47:13+02:00
modules: readme files regenerated - lost ... [skip ci]
---
Modified: src/modules/lost/README
---
Diff: https://github.com/kamailio/kamailio/commit/4acc8aa71b50efc0f8ec073d711dda2……
[View More]Patch: https://github.com/kamailio/kamailio/commit/4acc8aa71b50efc0f8ec073d711dda2…
---
diff --git a/src/modules/lost/README b/src/modules/lost/README
index cbb49366e7..357c41d388 100644
--- a/src/modules/lost/README
+++ b/src/modules/lost/README
@@ -230,9 +230,11 @@ var(uri)\n");
https://www.digitalocean.com/community/questions/how-to-upgrade-curl-in
-centos6
- Note: http_client_query exported by the http_client API returns the
- first line of the HTTP response (query_params.oneline = 1), but the
- lost module requires the complete response message, which requires
- query_params.oneline set to 0. In the case lost_query is used with the
- default http_client API, dereferencing location via HTTP provided with
- the Geolocation header causes an error.
+ Note: http_client_query exported by the http_client API returns by
+ default the first line of the HTTP response (query_params.oneline = 1),
+ but the lost module requires the complete response message, which
+ requires query_params.oneline set to 0. In the case lost_query is used
+ with the default http_client API, dereferencing location via HTTP
+ provided with the Geolocation header causes an error. Therefore, to
+ work properlu=y, it requires to set http_client module parameter
+ query_result to 0.
[View Less]
Module: kamailio
Branch: master
Commit: 878c41b7dbd1a716d5a2a9281ab99af585737022
URL: https://github.com/kamailio/kamailio/commit/878c41b7dbd1a716d5a2a9281ab99af…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2019-08-19T11:37:40+02:00
lost: docs - note that http_client param query_result has to be set to 0
---
Modified: src/modules/lost/doc/lost_admin.xml
---
Diff: https://github.com/kamailio/kamailio/…
[View More]commit/878c41b7dbd1a716d5a2a9281ab99af…
Patch: https://github.com/kamailio/kamailio/commit/878c41b7dbd1a716d5a2a9281ab99af…
---
diff --git a/src/modules/lost/doc/lost_admin.xml b/src/modules/lost/doc/lost_admin.xml
index d4228f3044..b5701d3fb8 100644
--- a/src/modules/lost/doc/lost_admin.xml
+++ b/src/modules/lost/doc/lost_admin.xml
@@ -255,11 +255,13 @@ xlog("L_INFO", "LOST findService: Result code $var(res)\nUri: $var(uri)\nName: $
https://www.digitalocean.com/community/questions/how-to-upgrade-curl-in-cen…</ulink>
</para>
<para>
- Note: http_client_query exported by the http_client API returns the first line of
+ Note: http_client_query exported by the http_client API returns by default the first line of
the HTTP response (query_params.oneline = 1), but the lost module requires the complete
response message, which requires query_params.oneline set to 0. In the case lost_query
is used with the default http_client API, dereferencing location via HTTP provided with
- the Geolocation header causes an error.
+ the Geolocation header causes an error. Therefore, to work properlu=y, it requires to set
+ <ulink url="https://www.kamailio.org/docs/modules/devel/modules/http_client.html#http_c…">
+ http_client module parameter query_result to 0</ulink>.
</para>
</section>
</chapter>
[View Less]
Module: kamailio
Branch: master
Commit: 9115bcdabaa3da04e3e563bb43a04358b33e2c17
URL: https://github.com/kamailio/kamailio/commit/9115bcdabaa3da04e3e563bb43a0435…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2019-08-16T11:05:35+02:00
core: dset - function to push a new branch and return its pointer
---
Modified: src/core/dset.c
Modified: src/core/dset.h
---
Diff: https://github.com/kamailio/kamailio/…
[View More]commit/9115bcdabaa3da04e3e563bb43a0435…
Patch: https://github.com/kamailio/kamailio/commit/9115bcdabaa3da04e3e563bb43a0435…
---
diff --git a/src/core/dset.c b/src/core/dset.c
index 1803155206..184ddc9e92 100644
--- a/src/core/dset.c
+++ b/src/core/dset.c
@@ -328,7 +328,7 @@ void clear_branches(void)
-/** Add a new branch to the current transaction.
+/** Add a new branch to the current destination set.
* @param msg sip message, used for getting the uri if not specified (0).
* @param uri uri, can be 0 (in which case the uri is taken from msg)
* @param dst_uri destination uri, can be 0.
@@ -352,7 +352,7 @@ int append_branch(struct sip_msg* msg, str* uri, str* dst_uri, str* path,
str luri;
/* if we have already set up the maximum number
- * of branches, don't try new ones
+ * of branches, don't try new ones
*/
if (unlikely(nr_branches == sr_dst_max_branches - 1)) {
LM_ERR("max nr of branches exceeded\n");
@@ -466,12 +466,40 @@ int append_branch(struct sip_msg* msg, str* uri, str* dst_uri, str* path,
branches[nr_branches].location_ua[0] = '\0';
branches[nr_branches].location_ua_len = 0;
}
-
+
nr_branches++;
return 1;
}
+/** Push a new branch to the current destination set.
+ * @param msg sip message, used for getting the uri if not specified (0).
+ * @param uri uri, can be 0 (in which case the uri is taken from msg)
+ * @param dst_uri destination uri, can be 0.
+ * @param path path vector (passed in a string), can be 0.
+ * @param q q value.
+ * @param flags per branch flags.
+ * @param force_socket socket that should be used when sending.
+ * @param instance sip instance contact header param value
+ * @param reg_id reg-id contact header param value
+ * @param ruid ruid value from usrloc
+ * @param location_ua location user agent
+ *
+ * @return NULL on failure, new branch pointer on success.
+ */
+branch_t* ksr_push_branch(struct sip_msg* msg, str* uri, str* dst_uri, str* path,
+ qvalue_t q, unsigned int flags,
+ struct socket_info* force_socket,
+ str* instance, unsigned int reg_id,
+ str* ruid, str* location_ua)
+{
+ if(append_branch(msg, uri, dst_uri, path, q, flags, force_socket,
+ instance, reg_id, ruid, location_ua)<0) {
+ return NULL;
+ }
+ return &branches[nr_branches-1];
+}
+
/*! \brief
* Combines the given elements into a Contact header field
* dest = target buffer, will be updated to new position after the printed contact
diff --git a/src/core/dset.h b/src/core/dset.h
index 96f31978a6..ebb4e765bb 100644
--- a/src/core/dset.h
+++ b/src/core/dset.h
@@ -94,7 +94,16 @@ branch_t *get_sip_branch(int idx);
int drop_sip_branch(int idx);
/*! \brief
- * Add a new branch to current transaction
+ * Push a new branch to current destination set
+ */
+branch_t *ksr_push_branch(sip_msg_t* msg, str* uri, str* dst_uri, str* path,
+ qvalue_t q, unsigned int flags,
+ struct socket_info* force_socket,
+ str* instance, unsigned int reg_id,
+ str* ruid, str* location_ua);
+
+/*! \brief
+ * Add a new branch to current destination set
*/
int append_branch(struct sip_msg* msg, str* uri, str* dst_uri, str* path,
qvalue_t q, unsigned int flags,
[View Less]
<!-- 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 …
[View More]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 -->
- [ ] Commit message has the format required by CONTRIBUTING guide
- [ ] Commits are split per component (core, individual modules, libs, utils, ...)
- [ ] Each component has a single commit (if not, squash them into one commit)
- [ ] 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
- [ ] 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
- [ ] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2034
-- Commit Summary --
* lost: adds HELD (RFC6155) and LOST (RFC5222) queries for location-based routing
* lost: adds HELD (RFC6155) and LOST (RFC5222) queries for location-based routing
* lost: adds HELD (RFC6155) and LOST (RFC5222) queries for location-based routing
* lost: adds HELD (RFC6155) and LOST (RFC5222) queries for location-based routing
-- File Changes --
A src/modules/lost/Makefile (23)
A src/modules/lost/doc/Makefile (4)
A src/modules/lost/doc/lost.xml (36)
A src/modules/lost/doc/lost_admin.xml (265)
A src/modules/lost/functions.c (590)
A src/modules/lost/functions.h (40)
A src/modules/lost/lost.c (339)
A src/modules/lost/pidf.c (137)
A src/modules/lost/pidf.h (50)
A src/modules/lost/utilities.c (653)
A src/modules/lost/utilities.h (76)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2034.patchhttps://github.com/kamailio/kamailio/pull/2034.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/2034
[View Less]
…ed routing
- lost_held_query() takes specific id (pvar, P-A-I, or From), assembles a
locationRequest (XML), and sends it to an http_client connection, responses
are parsed (pidf-lo and location reference are returned)
- lost_query() takes pidf-lo (pvar, msg body, or de-referenced), a service urn
(pvar, request line) assembles a findService request (XML), and sends it to
an http_client connection, responses are parsed (target uri and display name
are returned)
<!-- Kamailio Pull …
[View More]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 -->
- [ ] Commit message has the format required by CONTRIBUTING guide
- [ ] Commits are split per component (core, individual modules, libs, utils, ...)
- [ ] Each component has a single commit (if not, squash them into one commit)
- [ ] 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
- [ ] 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
- [ ] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2031
-- Commit Summary --
* lost: adds HELD (RFC6155) and LOST (RFC5222) queries for location-based routing
-- File Changes --
A src/modules/lost/Makefile (23)
A src/modules/lost/README (238)
A src/modules/lost/doc/Makefile (4)
A src/modules/lost/doc/lost.xml (36)
A src/modules/lost/doc/lost_admin.xml (265)
A src/modules/lost/functions.c (551)
A src/modules/lost/functions.h (40)
A src/modules/lost/lost.c (343)
A src/modules/lost/pidf.c (143)
A src/modules/lost/pidf.h (53)
A src/modules/lost/utilities.c (592)
A src/modules/lost/utilities.h (73)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2031.patchhttps://github.com/kamailio/kamailio/pull/2031.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/2031
[View Less]
Module: kamailio
Branch: master
Commit: e255aaa596d622103628903d08f07a226dacdbd9
URL: https://github.com/kamailio/kamailio/commit/e255aaa596d622103628903d08f07a2…
Author: wkampich <wolfgang.kampichler(a)gmail.com>
Committer: Henning Westerholt <hw(a)skalatan.de>
Date: 2019-08-16T08:04:03+02:00
lost: adds HELD (RFC6155) and LOST (RFC5222) queries for location-based routing
- lost_held_query() takes specific id (pvar, P-A-I, or From), assembles a
locationRequest (XML), and sends …
[View More]it to an http_client connection, responses
are parsed (pidf-lo and location reference are returned)
- lost_query() takes pidf-lo (pvar, msg body, or de-referenced), a service urn
(pvar, request line) assembles a findService request (XML), and sends it to
an http_client connection, responses are parsed (target uri and display name
are returned)
---
Added: src/modules/lost/Makefile
Added: src/modules/lost/README
Added: src/modules/lost/doc/Makefile
Added: src/modules/lost/doc/lost.xml
Added: src/modules/lost/doc/lost_admin.xml
Added: src/modules/lost/functions.c
Added: src/modules/lost/functions.h
Added: src/modules/lost/lost.c
Added: src/modules/lost/pidf.c
Added: src/modules/lost/pidf.h
Added: src/modules/lost/utilities.c
Added: src/modules/lost/utilities.h
---
Diff: https://github.com/kamailio/kamailio/commit/e255aaa596d622103628903d08f07a2…
Patch: https://github.com/kamailio/kamailio/commit/e255aaa596d622103628903d08f07a2…
[View Less]
Hi Daniel,
good tip about the crypto module.
It will indeed hide the IP address in the call-id, just tried it:
Call-ID: d810d369-aa60-4d79-aee5-9c03d2e66781
I think if we would feed the sruid unique ID (in libs/srutils) into the SHA256 hash (also available there) this it should be secure enough without the crypto dependencies.
The sruid is based on a LSFR implementation which is quite fast, and the SHA256 should provide the necessary unpredictability.
But as the crypto module approach …
[View More]works, it has probably not a really high priority. I can also look a bit into it when I got time.
Cheers,
Henning
Am 14.08.19 um 19:21 schrieb Daniel-Constantin Mierla:
Hello,
using the ip in call-id is not a good practice imo, I had it in mind to replace it properly everywhere for quite some time -- actually at this moment there is an option that can be activated in the crypto module making the call-id to be generated with libssl unique id generation functions, but I don't recall if the local ip is still appended. This would require libssl, so my goal was to add an alternative to generate a "good-enough" unique id, without external dependencies, to be used as local call-id.
Cheers,
Daniel
On 14.08.19 19:01, Joel Serrano wrote:
Hello Henning,
No concerns at all!! As you say, the Call-ID can really say whatever... The only concern could/would be in the security topic that you are disclosing potential sensible information about your infrastructure blablabla... but that can be solved just by changing the listen= order so even that wouldn't be a problem.. In reality I was just curious so I thought I'd ask :)
Thanks!!
Joel.
On Wed, Aug 14, 2019 at 9:32 AM Henning Westerholt <hw(a)skalatan.de<mailto:hw@skalatan.de>> wrote:
Hello Joel,
funny - I just had this discussion about the same topic some days ago.
In the end this is "only" the call-id, the IP should not be used to to routing descisions etc.. Do you have some more concerns about this?
I think as well it just uses the first IP. I think at the moment the call-id is generated internally from tm, but this could be of course changed for the module with some coding/extension.
Cheers,
Henning
Am 14.08.19 um 17:12 schrieb Joel Serrano:
Hello,
Simple doubt regarding dispatcher module when you have the ds_default_socket() modparam set:
Say you have 2 kamailio boxes, active + passive, one shared IP via keepalived.... On the actrive node, you have dispatcher.send_ping to 1, and the passive has it set to 0.
So far OK, only the active box is sending out probing OPTIONS requests, and it's using as outbound socket the virtual IP out of all the available ones (as defined with ds_default_socket() modparam)
I have seen in a capture that the outbound OPTIONS look like:
OPTIONS sip:190.14.203.219:5060<http://190.14.203.219:5060> SIP/2.0
Via: SIP/2.0/UDP A.B.C.180;branch=z9hG4bK7abb.6fbaccc1000000000000000000000000.0
To: <sip:190.14.203.219:5060<http://190.14.203.219:5060>>
From: <sip:dspinger@my.domain><mailto:sip:dspinger@my.domain>;tag=e2bdd495733c59fd91487a137fccad4e-8a73
CSeq: 10 OPTIONS
Call-ID: 2019f8491329c382-31419(a)A.B.C.181
Max-Forwards: 70
Content-Length: 0
A.B.C.180 -> VRRP
A.B.C.181 -> Physical IP of the box
My doubt is, shouldn't ds_default_socket also update the IP used to generate the Call-ID used in the OPTIONS request? Currently, I believe it's using the first defined listen= IP from config script as I switched the order the listen= are defined and I get the desired result:
OPTIONS sip:186.188.220.174:5060<http://186.188.220.174:5060> SIP/2.0
Via: SIP/2.0/UDP A.B.C.180;branch=z9hG4bKc97e.a8d9e1c2000000000000000000000000.0
To: <sip:186.188.220.174:5060<http://186.188.220.174:5060>>
From: <sip:dspinger@my.domain><mailto:sip:dspinger@my.domain>;tag=5e2e1773f812f6a7e4085c5d036e29d8-d323
CSeq: 10 OPTIONS
Call-ID: 7d9a92c218fc1ba0-32111(a)A.B.C.180
Max-Forwards: 70
Content-Length: 0
Is this expected?
Cheers,
Joel.
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://skalatan.de/services
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla -- www.asipto.com<http://www.asipto.com>
www.twitter.com/miconda<http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda<http://www.linkedin.com/in/miconda>
--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://skalatan.de/services
[View Less]
The ims_usrloc_scscf module lacks module documentation in git master:
~/repositories/kamailio/src/modules/ims_usrloc_scscf> ls -la README doc*
ls: cannot access 'README': No such file or directory
ls: cannot access 'doc*': No such file or directory
The purpose of this module and also its parameters that are exported should be documented in a doc/*.xml files like the other modules. This are the exported parameters from the source code:
{"timer_interval", INT_PARAM, &…
[View More]timer_interval },
{"desc_time_order", INT_PARAM, &desc_time_order },
{"matching_mode", INT_PARAM, &matching_mode },
{"cseq_delay", INT_PARAM, &cseq_delay },
{"fetch_rows", INT_PARAM, &ul_fetch_rows },
{"hash_size", INT_PARAM, &ul_hash_size },
{"subs_hash_size", INT_PARAM, &subs_hash_size },
{"contacts_hash_size", INT_PARAM, &contacts_hash_size },
{"nat_bflag", INT_PARAM, &nat_bflag },
{"contact_delete_delay", INT_PARAM, &contact_delete_delay },
{"usrloc_debug_file", PARAM_STR, &usrloc_debug_file},
{"enable_debug_file", INT_PARAM, &usrloc_debug},
{"user_data_dtd", PARAM_STRING, &scscf_user_data_dtd},
{"user_data_xsd", PARAM_STRING, &scscf_user_data_xsd},
{"support_wildcardPSI", INT_PARAM, &scscf_support_wildcardPSI},
{"unreg_validity", INT_PARAM, &unreg_validity},
{"maxcontact_behaviour",INT_PARAM, &maxcontact_behaviour},
{"maxcontact", INT_PARAM, &maxcontact},
{"maxcontact_3gpp", INT_PARAM, &maxcontact_3gpp},
{"max_subscribes", INT_PARAM, &max_subscribes},
{"sub_dialog_hash_size",INT_PARAM, &sub_dialog_hash_size},
{"db_mode", INT_PARAM, &db_mode},
{"db_url", PARAM_STR, &db_url},
{"timer_procs", INT_PARAM, &ul_timer_procs},
--
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/1644
[View Less]
<!-- 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 …
[View More]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 -->
- [x] 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 -->
ims_usrloc_scscf module documentation is added.
removed unnecessary files.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/1835
-- Commit Summary --
* ims_registrar_scscf : fixed wrong comment for emergency register
* ims_registrar_scscf: removed screensharing log file.
* ims_usrloc_scscf: removed NewFile.xml file
* ims_usrloc_scscf: doc is added
-- File Changes --
M src/modules/ims_registrar_scscf/config.c (4)
D src/modules/ims_registrar_scscf/screensharing.log (66)
D src/modules/ims_usrloc_scscf/NewFile.xml (9)
A src/modules/ims_usrloc_scscf/doc/Makefile (4)
A src/modules/ims_usrloc_scscf/doc/ims_usrloc_scscf.xml (62)
A src/modules/ims_usrloc_scscf/doc/ims_usrloc_scscf_admin.xml (340)
A src/modules/ims_usrloc_scscf/doc/ims_usrloc_scscf_faq.xml (58)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/1835.patchhttps://github.com/kamailio/kamailio/pull/1835.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/1835
[View Less]
Hello,
Kamailio SIP Server v5.2.4 stable release is out.
This is a maintenance release of the latest stable branch, 5.2, that
includes fixes since the release of v5.2.3. There is no change to
database schema or configuration language structure that you have to do
on previous installations of v5.2.x. Deployments running previous v5.2.x
versions are strongly recommended to be upgraded to v5.2.4.
For more details about version 5.2.4 (including links and guidelines to
download the tarball or …
[View More]from GIT repository), visit:
* https://www.kamailio.org/w/2019/08/kamailio-v5-2-4-released/
RPM, Debian/Ubuntu packages will be available soon as well.
Many thanks to all contributing and using Kamailio!
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
[View Less]
### Description
We are running Kamailio 5.1.x in a mixed native/Kemi environment. That means, most of the config is still native Kamailio language, but some newer functions were written in JS and included via `jsdt_run("...");`.
In one of those functions, we place an sqlops query. And since introducing this code, Kamailio leaks memory. Slowly, but eventually, the private memory will fill up.
### Troubleshooting
#### Reproduction
In Kamailio, the code looks like this:
```
if (!jsdt_run("…
[View More]ksrIsCallAccountingRequired", "$(var(accentries){s.select,10,|})", "$(var(accentries){s.select,12,|})")) {
xlog("L_ERR", "JS Call of ksrIsCallAccountingRequired route failed.\n");
}
```
And our JS code containing sqlops looks like this:
```
extension = '1234567e0';
mastersipid = '1234567';
KSR.sqlops.sql_query(
"dbconn",
`SELECT username, grp FROM grp WHERE username IN ('${mastersipid}', '${extension}') AND grp = 'ourGroupName'`,
user
);
```
For each call, this query is executed once. Depending on the traffic, you can see the private package memory starting to fill up quicker or slower.
#### Debugging Data
### Possible Solutions
We had a similar problem about two years ago with app_lua and getting entries from a hash table, which we solved by introducing a temporary variable for using in the hash table index instead of strings. We tried doing the same thing in our current setup:
```
KSR.pv.sets("$var(extensionForQuery)", extension);
KSR.pv.sets("$var(masterSipidForQuery)", masterSipid);
KSR.sqlops.sql_query(
"dbconn",
"SELECT username, grp FROM grp WHERE username IN ('$var(masterSipidForQuery)', '$var(extensionForQuery)') AND grp = 'ourGroupName'",
user
);
```
However, Kamailio doesn't replace the variables in the query string. Although the documentation of the sqlops module says, it supports pseudovars in the query string. We even tried putting the whole query into a variable, but ended up with a sqlops error.
### Additional Information
```
ersion: kamailio 5.1.4 (x86_64/linux)
flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: unknown
compiled with gcc 4.7.2
```
* **Operating System**:
```
Debian Wheezy (yeah, I know... )
```
--
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/2032
[View Less]
Hello,
I am considering to do soon a new release out of branch 5.2,
respectively v5.2.4. I am aiming for August 12 or August 14, a matter of
how backporting is finished, given that next week some devs travel to
ClueCon.
As usual, if you are aware of issues not reported yet on bug tracker or
fixes not yet backported to branch 5.2, act during the next days to have
enough time to approach them.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Module: kamailio
Branch: master
Commit: 6542a638bee90afdbfe63b59d9d7f1d23b0406aa
URL: https://github.com/kamailio/kamailio/commit/6542a638bee90afdbfe63b59d9d7f1d…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2019-08-13T16:07:05+02:00
rr: docs - note about use of record_route() for requests within dialog
- it has to be used after loose_route() for a proper detection of
request direction
---
Modified: src/…
[View More]modules/rr/doc/rr_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/6542a638bee90afdbfe63b59d9d7f1d…
Patch: https://github.com/kamailio/kamailio/commit/6542a638bee90afdbfe63b59d9d7f1d…
---
diff --git a/src/modules/rr/doc/rr_admin.xml b/src/modules/rr/doc/rr_admin.xml
index 74e59abe82..362edd4f1f 100644
--- a/src/modules/rr/doc/rr_admin.xml
+++ b/src/modules/rr/doc/rr_admin.xml
@@ -397,8 +397,7 @@ loose_route();
</section>
<section id="rr.f.record_route">
- <title><function moreinfo="none">record_route()</function> and <function
- moreinfo="none">record_route(string)</function></title>
+ <title><function moreinfo="none">record_route([sparams])</function></title>
<para>The function adds a new Record-Route header field. The header
field will be inserted in the message before any other Record-Route
@@ -414,6 +413,10 @@ loose_route();
request and generate and add a flow-token as the username part of the
Record-Route-URI.</para>
+ <para>Note: if append From-tag is enabled and the function is used for requests
+ within dialog, it must be executed after loose_route() in order to detect
+ properly the direction.</para>
+
<para>This function can be used from REQUEST_ROUTE, BRANCH_ROUTE and
FAILURE_ROUTE.</para>
[View Less]
Module: kamailio
Branch: master
Commit: 8546983de13bba7ed7a84a88ed91027e4291a1bc
URL: https://github.com/kamailio/kamailio/commit/8546983de13bba7ed7a84a88ed91027…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2019-08-13T10:16:43+02:00
modules: readme files regenerated - registrar ... [skip ci]
---
Modified: src/modules/registrar/README
---
Diff: https://github.com/kamailio/kamailio/commit/…
[View More]8546983de13bba7ed7a84a88ed91027…
Patch: https://github.com/kamailio/kamailio/commit/8546983de13bba7ed7a84a88ed91027…
---
diff --git a/src/modules/registrar/README b/src/modules/registrar/README
index d55fc5a7c9..e4516756e6 100644
--- a/src/modules/registrar/README
+++ b/src/modules/registrar/README
@@ -1070,7 +1070,7 @@ add_sock_hdr("Sock-Info");
* ruid - The record unique ID for a a specific contact to be removed.
It can contain pseudo-variables that are evaluated at runtime.
- This function can be used from REQUEST_ROUTE, FAILURE_ROUTE.
+ This function can be used from ANY_ROUTE.
Return values:
* 0 - Successfully deleted contact(s)
[View Less]
Module: kamailio
Branch: master
Commit: 23a5b8d9baf40a416401017324ceb01e7d769494
URL: https://github.com/kamailio/kamailio/commit/23a5b8d9baf40a416401017324ceb01…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2019-08-13T10:03:32+02:00
registrar: updated docs for unregister()
- function is allowed to be used in any route
---
Modified: src/modules/registrar/doc/registrar_admin.xml
---
Diff: https://github.…
[View More]com/kamailio/kamailio/commit/23a5b8d9baf40a416401017324ceb01…
Patch: https://github.com/kamailio/kamailio/commit/23a5b8d9baf40a416401017324ceb01…
---
diff --git a/src/modules/registrar/doc/registrar_admin.xml b/src/modules/registrar/doc/registrar_admin.xml
index 32752eac89..67e13e09e3 100644
--- a/src/modules/registrar/doc/registrar_admin.xml
+++ b/src/modules/registrar/doc/registrar_admin.xml
@@ -1400,7 +1400,7 @@ add_sock_hdr("Sock-Info");
</listitem>
</itemizedlist>
<para>
- This function can be used from REQUEST_ROUTE, FAILURE_ROUTE.
+ This function can be used from ANY_ROUTE.
</para>
<para>
Return values:
[View Less]
Module: kamailio
Branch: master
Commit: d93b1861c6e9be5991040d2da327d2f543d9f9ab
URL: https://github.com/kamailio/kamailio/commit/d93b1861c6e9be5991040d2da327d2f…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2019-08-13T09:15:43+02:00
http_client: docs for query_result parameter
---
Modified: src/modules/http_client/doc/http_client_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/…
[View More]d93b1861c6e9be5991040d2da327d2f…
Patch: https://github.com/kamailio/kamailio/commit/d93b1861c6e9be5991040d2da327d2f…
---
diff --git a/src/modules/http_client/doc/http_client_admin.xml b/src/modules/http_client/doc/http_client_admin.xml
index 70bcd2a433..55c65ccc97 100644
--- a/src/modules/http_client/doc/http_client_admin.xml
+++ b/src/modules/http_client/doc/http_client_admin.xml
@@ -36,10 +36,10 @@
<para>
Like in SIP, the HTTP URL may need encoding to be transported safely
over the network. Check the string encoding functions in the Transformation
- Cookbook (as used in the http_client_query example below).
+ Cookbook (as used in the http_client_query() example below).
</para>
<para>
- The function http_client_query allows &kamailio; to issue an HTTP GET
+ The function http_client_query() allows &kamailio; to issue an HTTP GET
request and get access to parts of the reply. This function has
been ported from the utils module and now use the same libcurl
functions. We recommend using the new functionality provided by
@@ -433,6 +433,31 @@ modparam("http_client", "authmethod", 3)
<programlisting format="linespecific">
...
modparam("http_client", "keep_connections", 1)
+...
+ </programlisting>
+ </example>
+ </section>
+ <section id="http_client.p.query_result">
+ <title><varname>query_result</varname> (int)</title>
+ <para>
+ Control what is returned by the http_client_query(...) in the result
+ variable.
+ </para>
+ <para>
+ Valid values are:
+ <itemizedlist>
+ <listitem><para>0 - Return the entire HTTP result body</para></listitem>
+ <listitem><para>1 - Return the first oine from HTTP result body</para></listitem>
+ </itemizedlist>
+ </para>
+ <para>
+ Default value: 1 (return first line).
+ </para>
+ <example>
+ <title>Set <varname>query_result</varname> parameter</title>
+ <programlisting format="linespecific">
+...
+modparam("http_client", "query_result", 0)
...
</programlisting>
</example>
@@ -796,17 +821,18 @@ http_get_redirect("apiserver", "$var(targeturl)");
</para>
<para>
If HTTP server returns a class 2xx, 3xx or 4xx reply,
- the first line of the reply's body (if any) is
+ the first line or the entire reply body (if any) is
stored in <quote>result</quote> parameter,
- which must be a writable pseudo variable.
+ which must be a writable pseudo variable. See the query_result
+ parameter for controling what value to be stored in the result
+ variable.
</para>
<para>
Function returns reply code of HTTP reply or -1
if something went wrong.
</para>
<para>
- This function can be used from REQUEST_ROUTE,
- ONREPLY_ROUTE, FAILURE_ROUTE, and BRANCH_ROUTE.
+ This function can be used from ANY_ROUTE.
</para>
<para>
Note that this function is based on the http_query function in the utils module.
[View Less]
Module: kamailio
Branch: master
Commit: b3d9da5c5e80e42e550c4cf56c29aee1ab068c92
URL: https://github.com/kamailio/kamailio/commit/b3d9da5c5e80e42e550c4cf56c29aee…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2019-08-12T21:01:45+02:00
modules: readme files regenerated - topos ... [skip ci]
---
Modified: src/modules/topos/README
---
Diff: https://github.com/kamailio/kamailio/commit/b3d9da5c5e80e42e550c4cf56c29aee……
[View More]
Patch: https://github.com/kamailio/kamailio/commit/b3d9da5c5e80e42e550c4cf56c29aee…
---
diff --git a/src/modules/topos/README b/src/modules/topos/README
index d75a9de697..d430714543 100644
--- a/src/modules/topos/README
+++ b/src/modules/topos/README
@@ -197,7 +197,11 @@ modparam("topos", "branch_expire", 300)
3.6. dialog_expire (int)
- Interval in seconds after which the dialog records are deleted.
+ Interval in seconds after which the dialog records are deleted. Keep in
+ mind that the module does not update the dialog timestamp after the
+ initial call setup on re-INVITEs or other in-dialog messages. So set a
+ large enough value (according your longest call duration) to prevent
+ problems in re-writing messages.
Default value is 10800 (3 hours).
[View Less]
Module: kamailio
Branch: 5.2
Commit: db0ae1e3dde3331810ba8b154d7e111bf3322583
URL: https://github.com/kamailio/kamailio/commit/db0ae1e3dde3331810ba8b154d7e111…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2019-08-12T21:01:32+02:00
modules: readme files regenerated - modules ... [skip ci]
---
Modified: src/modules/topos/README
---
Diff: https://github.com/kamailio/kamailio/commit/db0ae1e3dde3331810ba8b154d7e111……
[View More]
Patch: https://github.com/kamailio/kamailio/commit/db0ae1e3dde3331810ba8b154d7e111…
---
diff --git a/src/modules/topos/README b/src/modules/topos/README
index d75a9de697..d430714543 100644
--- a/src/modules/topos/README
+++ b/src/modules/topos/README
@@ -197,7 +197,11 @@ modparam("topos", "branch_expire", 300)
3.6. dialog_expire (int)
- Interval in seconds after which the dialog records are deleted.
+ Interval in seconds after which the dialog records are deleted. Keep in
+ mind that the module does not update the dialog timestamp after the
+ initial call setup on re-INVITEs or other in-dialog messages. So set a
+ large enough value (according your longest call duration) to prevent
+ problems in re-writing messages.
Default value is 10800 (3 hours).
[View Less]
Module: kamailio
Branch: 5.2
Commit: 6e5cb772817a8275c89869c868ce20a2ddb47df9
URL: https://github.com/kamailio/kamailio/commit/6e5cb772817a8275c89869c868ce20a…
Author: Henning Westerholt <hw(a)skalatan.de>
Committer: Henning Westerholt <hw(a)skalatan.de>
Date: 2019-08-12T20:55:26+02:00
topos: docs for dialog_expire param limitation for in-dialog requests (GH #2024)
(cherry picked from commit 3ccf5ee691440e806d441f0e58562ddc4137a488)
---
Modified: src/modules/topos/doc/…
[View More]topos_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/6e5cb772817a8275c89869c868ce20a…
Patch: https://github.com/kamailio/kamailio/commit/6e5cb772817a8275c89869c868ce20a…
---
diff --git a/src/modules/topos/doc/topos_admin.xml b/src/modules/topos/doc/topos_admin.xml
index b81672b006..681c5bb9a1 100644
--- a/src/modules/topos/doc/topos_admin.xml
+++ b/src/modules/topos/doc/topos_admin.xml
@@ -192,6 +192,10 @@ modparam("topos", "branch_expire", 300)
<title><varname>dialog_expire</varname> (int)</title>
<para>
Interval in seconds after which the dialog records are deleted.
+ Keep in mind that the module does not update the dialog timestamp
+ after the initial call setup on re-INVITEs or other in-dialog
+ messages. So set a large enough value (according your longest call
+ duration) to prevent problems in re-writing messages.
</para>
<para>
<emphasis>
[View Less]
Module: kamailio
Branch: master
Commit: 3ccf5ee691440e806d441f0e58562ddc4137a488
URL: https://github.com/kamailio/kamailio/commit/3ccf5ee691440e806d441f0e58562dd…
Author: Henning Westerholt <hw(a)skalatan.de>
Committer: Henning Westerholt <hw(a)skalatan.de>
Date: 2019-08-12T20:54:48+02:00
topos: docs for dialog_expire param limitation for in-dialog requests (GH #2024)
---
Modified: src/modules/topos/doc/topos_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/…
[View More]3ccf5ee691440e806d441f0e58562dd…
Patch: https://github.com/kamailio/kamailio/commit/3ccf5ee691440e806d441f0e58562dd…
---
diff --git a/src/modules/topos/doc/topos_admin.xml b/src/modules/topos/doc/topos_admin.xml
index b81672b006..681c5bb9a1 100644
--- a/src/modules/topos/doc/topos_admin.xml
+++ b/src/modules/topos/doc/topos_admin.xml
@@ -192,6 +192,10 @@ modparam("topos", "branch_expire", 300)
<title><varname>dialog_expire</varname> (int)</title>
<para>
Interval in seconds after which the dialog records are deleted.
+ Keep in mind that the module does not update the dialog timestamp
+ after the initial call setup on re-INVITEs or other in-dialog
+ messages. So set a large enough value (according your longest call
+ duration) to prevent problems in re-writing messages.
</para>
<para>
<emphasis>
[View Less]
The topos module fails to update the dialog data in the topos_d table after the processing of re-INVITEs.
I have setup a call at 11:55, and triggered a re-INVITE at 12:08. The respective topos_d table entry is not updated.
This causes the entry to expire after topos dialog_timeout value.
I would expect that the timestamp of the call in the topos_d table is updated. Is this assumption correct? If the current behavior is expected, it should documented in the module README.
No error messages …
[View More]from topos module in kamailio.log. Output from tables:
```
MariaDB [kamailio]> select id, rectime, s_method, a_callid from topos_t; select id, rectime, s_method, a_callid from topos_d;
+-----+---------------------+----------+----------------------------------+
| id | rectime | s_method | a_callid |
+-----+---------------------+----------+----------------------------------+
| 305 | 2019-08-04 12:08:12 | INVITE | q0Jeh9g49GeYdJXqcjCo-G0CW4dQ0iav |
| 306 | 2019-08-04 12:08:12 | ACK | q0Jeh9g49GeYdJXqcjCo-G0CW4dQ0iav |
| 307 | 2019-08-04 12:08:14 | INVITE | q0Jeh9g49GeYdJXqcjCo-G0CW4dQ0iav |
| 308 | 2019-08-04 12:08:14 | ACK | q0Jeh9g49GeYdJXqcjCo-G0CW4dQ0iav |
+-----+---------------------+----------+----------------------------------+
+-----+---------------------+----------+----------------------------------+
| id | rectime | s_method | a_callid |
+-----+---------------------+----------+----------------------------------+
| 156 | 2019-08-04 11:55:22 | INVITE | q0Jeh9g49GeYdJXqcjCo-G0CW4dQ0iav |
+-----+---------------------+----------+----------------------------------+
```
--
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/2024
[View Less]
Hi Alex,
there have been many changes to the modules between 5.1 and 5.2. I just
looked a bit to the code of dispatch.c and also the commits.
I noticed something in commit 3933a64c464acfb285e - there was a block
related to round-robin before which got removed in this refactoring (if
I analyzed it correctly):
- /* if alg is round-robin then update the shortcut to next to be
used */
- if(alg == DS_ALG_ROUNDROBIN)
…
[View More]- idx->last = (hash + 1) % idx->nr;
It could be simple added back, because of the changed logic, though.
Cheers,
Henning
Am 12.08.19 um 17:28 schrieb Alex Balashov:
> Hi Daniel,
>
> Haven’t checked that, no. But all the external system does is issue RPC commands (`dispatcher.set_state`) maybe a few times a day. It’s nothing volatile or overly Byzantine.
>
> —
> Sent from mobile, with due apologies for brevity and errors.
>
>> On Aug 12, 2019, at 11:24 AM, Daniel-Constantin Mierla <miconda(a)gmail.com> wrote:
>>
>> Hello,
>>
>> could you observe similar behavior on other dispatchers that don't use
>> an external system tomanage activation and deactivation of the gateways?
>> Or you haven't checked such one so far?
>>
>> Cheers,
>> Daniel
>>
>>> On 12.08.19 15:23, Alex Balashov wrote:
>>> Hi,
>>>
>>> I've got a proxy that does very basic round-robin distribution of calls
>>> to an elastic pool of servers, defined in a simple SQLite database with
>>> equal priorities. Nothing too complicated, just a vanilla
>>> `ds_select_domain("1", "4")`.
>>>
>>> The only complication is that seldom are most of the gateways enabled.
>>> Probing stuff was turned on, but didn't do quite what was desired, so it
>>> was replaced with a system that manages activation and deactivation of
>>> the gateways externally. Nevertheless, these are the left-over probing
>>> settings:
>>>
>>> modparam("dispatcher", "ds_ping_method", "OPTIONS")
>>> modparam("dispatcher", "ds_ping_from", "sip:pinger@domain")
>>> modparam("dispatcher", "ds_ping_interval", 15)
>>> modparam("dispatcher", "ds_probing_threshold", 256)
>>> modparam("dispatcher", "ds_inactive_threshold", 1)
>>> modparam("dispatcher", "ds_probing_mode", 0)
>>>
>>> After an upgrade from 5.1 to 5.2.3 (009f62), the round-robin has become
>>> extremely "sticky" and tendentious. That is to say, it directs _almost_
>>> all calls to a single gateway -- the first gateway in the table --
>>> though not 100%. There is also a marked tendency to send lots of
>>> consecutive calls to the same gateway, even if it's not the first one,
>>> though most of the time it is.
>>>
>>> Has anyone experienced similar upon upgrading to 5.2?
>>>
>>> Thanks much!
>>>
>>> -- Alex
>>>
>> --
>> Daniel-Constantin Mierla -- www.asipto.com
>> www.twitter.com/miconda -- www.linkedin.com/in/miconda
>>
> _______________________________________________
> Kamailio (SER) - Users Mailing List
> sr-users(a)lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://skalatan.de/services
[View Less]
#### 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 …
[View More]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
What the affected line of code really wants to achieve is: if an
accepted inputs type mask is not specified then default to accepting
only the actual variable type. So we must mask the var type first,
then shift it by `CFG_INPUT_SHIFT`, before or-ing it with the rest.
What happened before was that the entire type was shifted, and that
included var type, input type and flags. What we end up with is some
additional higher bits set (for flags). I actually discovered this while
adding an additional flag that was meant to mark variables as private,
only accessible through an internal API (not available to modules such
as cfg_rpc).
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2022
-- Commit Summary --
* core: Fix the cfg framework variable input type default
-- File Changes --
M src/core/cfg/cfg.c (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2022.patchhttps://github.com/kamailio/kamailio/pull/2022.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/2022
[View Less]
Module: kamailio
Branch: master
Commit: c3b2eacbba1097ed3d40cff18ea2d51ebcad1c67
URL: https://github.com/kamailio/kamailio/commit/c3b2eacbba1097ed3d40cff18ea2d51…
Author: MancaÈ George <mancas.f.george(a)gmail.com>
Committer: MancaÈ George <mancas.f.george(a)gmail.com>
Date: 2019-08-01T09:39:28Z
core: Fix the cfg framework variable input type default
What the affected line of code really wants to achieve is: if an
accepted inputs type mask is not specified then default to …
[View More]accepting
only the actual variable type. So we must mask the var type first,
then shift it by `CFG_INPUT_SHIFT`, before or-ing it with the rest.
What happened before was that the entire type was shifted, and that
included var type, input type and flags. What we end up with is some
additional higher bits set (for flags). I actually discovered this while
adding an additional flag that was meant to mark variables as private,
only accessible through an internal API (not available to modules such
as cfg_rpc).
---
Modified: src/core/cfg/cfg.c
---
Diff: https://github.com/kamailio/kamailio/commit/c3b2eacbba1097ed3d40cff18ea2d51…
Patch: https://github.com/kamailio/kamailio/commit/c3b2eacbba1097ed3d40cff18ea2d51…
---
diff --git a/src/core/cfg/cfg.c b/src/core/cfg/cfg.c
index 3822a9c94d..488d72f35a 100644
--- a/src/core/cfg/cfg.c
+++ b/src/core/cfg/cfg.c
@@ -94,7 +94,7 @@ int cfg_declare(char *group_name, cfg_def_t *def, void *values, int def_size,
/* verify the type of the input */
if (CFG_INPUT_MASK(def[i].type)==0) {
- def[i].type |= def[i].type << CFG_INPUT_SHIFT;
+ def[i].type |= CFG_VAR_MASK(def[i].type) << CFG_INPUT_SHIFT;
} else {
if ((CFG_INPUT_MASK(def[i].type) != CFG_VAR_MASK(def[i].type) << CFG_INPUT_SHIFT)
&& (def[i].on_change_cb == 0)) {
[View Less]