Module: kamailio
Branch: master
Commit: 6e9335ff2245596b74bc1c749d1e7805bf186f02
URL: https://github.com/kamailio/kamailio/commit/6e9335ff2245596b74bc1c749d1e780…
Author: �������������������� �������������������������������� <git-dpa(a)aegee.org>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2023-08-07T15:32:56+02:00
etc/ typos
---
Modified: etc/kamailio.cfg
Modified: etc/sip-router.cfg
---
Diff: https://github.com/kamailio/kamailio/commit/…
[View More]6e9335ff2245596b74bc1c749d1e780…
Patch: https://github.com/kamailio/kamailio/commit/6e9335ff2245596b74bc1c749d1e780…
---
diff --git a/etc/kamailio.cfg b/etc/kamailio.cfg
index 68493736d41..715c289af1e 100644
--- a/etc/kamailio.cfg
+++ b/etc/kamailio.cfg
@@ -227,7 +227,7 @@ enable_sctp=no
####### Custom Parameters #########
-/* These parameters can be modified runtime via RPC interface
+/* These parameters can be modified at runtime via RPC interface
* - see the documentation of 'cfg_rpc' module.
*
* Format: group.id = value 'desc' description
@@ -389,7 +389,7 @@ modparam("registrar", "path_mode", 0)
modparam("acc", "early_media", 0)
modparam("acc", "report_ack", 0)
modparam("acc", "report_cancels", 0)
-/* by default ww do not adjust the direct of the sequential requests.
+/* by default we do not adjust the direct of the sequential requests.
* if you enable this parameter, be sure the enable "append_fromtag"
* in "rr" module */
modparam("acc", "detect_direction", 0)
diff --git a/etc/sip-router.cfg b/etc/sip-router.cfg
index 0390ef7ec57..8669ea63d79 100644
--- a/etc/sip-router.cfg
+++ b/etc/sip-router.cfg
@@ -1,7 +1,7 @@
#
# $Id$
#
-# Example configuration file (simpler then ser-oob.cfg, but more
+# Example configuration file (simpler than ser-oob.cfg, but more
# complex then ser-basic.cfg).
#
# First start SER sample config script with:
@@ -73,7 +73,7 @@ rev_dns=no # (cmd. line: -R)
#group=ser
#disable_core=yes #disables core dumping
#open_fd_limit=1024 # sets the open file descriptors limit
-#mhomed=yes # usefull for multihomed hosts, small performance penalty
+#mhomed=yes # useful for multihomed hosts, small performance penalty
#disable_tcp=yes
#tcp_accept_aliases=yes # accepts the tcp alias via option (see NEWS)
sip_warning=yes
@@ -172,7 +172,7 @@ modparam("ctl", "binrpc", "tcp:127.0.0.1:2046")
# failed transactions (=negative responses) should be logged to
modparam("acc_db", "failed_transactions", 1)
-# comment the next line if you dont want to have accounting to DB
+# comment the next line if you don't want to have accounting to DB
modparam("acc_db", "log_flag", "FLAG_ACC")
# -- tm params --
@@ -197,7 +197,7 @@ modparam("tls", "private_key", "ser-selfsigned.key")
# -- xmlrpc params --
-# using a sub-route from the module is a lot safer then relying on the
+# using a sub-route from the module is a lot safer than relying on the
# request method to distinguish HTTP from SIP
modparam("xmlrpc", "route", "RPC");
@@ -358,8 +358,8 @@ route[RR]
# particularly good if upstream and downstream entities
# use different transport protocol
- # if the inital INVITE got the ACC flag store this in
- # an RR AVP cookie. this is more for demonstration purpose
+ # if the initial INVITE got the ACC flag store this in
+ # an RR AVP cookie. This is more for demonstration purpose
if (isflagset(FLAG_ACC)) {
$account = "yes";
setavpflag($account, "dialog_cookie");
@@ -377,7 +377,7 @@ route[DOMAIN]
# check if the callee is at a local domain
lookup_domain("$td", "@ruri.host");
- # we dont know the domain of the caller and also not
+ # we don't know the domain of the caller and also not
# the domain of the callee -> somone uses our proxy as
# a relay
if (strempty($t.did) && strempty($f.did)) {
@@ -528,7 +528,7 @@ route[INBOUND]
if (lookup_contacts("location")) {
append_hf("P-hint: usrloc applied\r\n");
- # we set the TM module timers according to the prefences
+ # we set the TM module timers according to the preferences
# of the callee (avoid too long ringing of his phones)
# Note1: timer values have to be in ms now!
# Note2: this makes even more sense if you switch to a voicemail
[View Less]
Hello,
(Adding sr-dev to CC)
This looks indeed a bit strange. Do you get any error messages in the log? In which process you are freeing the memory, one of the worker processes or the RPC process?
You could also try to use another memory manager to see if you get better performance. There is a command line parameter to choose one during startup.
Cheers,
Henning
--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://gilawa.com<https://gilawa.com/>
From: …
[View More]Chaigneau, Nicolas <nicolas.chaigneau(a)capgemini.com>
Sent: Wednesday, January 18, 2023 6:49 PM
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
Subject: [SR-Users] Performances issue when freeing shared memory in custom module (Kamailio 5.5.2)
Hello,
I'm encountering performance issues with Kamailio (5.5.2).
I'm using a custom Kamailio module that loads routing data in memory, using Kamailio shared memory.
This routing data is very large. It can be fully reloaded through a Kamailio RPC command (which is done once each day).
When reloading, two sets of data are maintained, one "loading" and another "current" (the latter being used to handle SIP requests).
When loading of the new data is finished, it is swapped to "current". Then, memory of the old (now unused) data is freed.
I've noticed that when Kamailio is freeing the old data, there is a very significant performance impact on SIP requests.
This is surprising to me, because the SIP requests do not use this old data.
This is not a CPU issue, idle CPU% is at about 99% at that moment.
I'm using the following functions :
- shm_mallocxz
- shm_free
From what I understand, shm_free is actually "qm_shm_free" defined in "src\core\mem\q_malloc.c" (the default shared memory manager being "qm").
I've noticed that there is also a variant shm_free_unsafe ("qm_free"), which does not perform locking.
I'm wondering if the lock could be the cause of my performances issues ?
(But I'm not sure how this could be possible, because although the SIP requests need to access the shared memory allocated, they do not use directly the functions from the share memory manager.)
If the performances issues are causes by the lock, could I use the unsafe version "safely" ? (considering that it is guaranteed that the old data cannot be used by anyone else)
Thanks for your help.
Regards,
Nicolas.
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
[View Less]
**Description**
We are using ims_charging module and Freediameter as diameter server for billing process....recently we faced one issue...For Initial **INVITEs** kamailio sending **CCR request (INITIAL_REQUEST)** to **diameter server** but if we receive Immediate **CANCLE** for the **INVITE**, kamailio sending **CCR request ( TERMINATE_REQUEST )** without waiting for the **CCR request (INITIAL_REQUEST) response** from the **Diameter server.**..
**Expected behavior**
Kamailio has to send **…
[View More]CCR request ( TERMINATE_REQUEST )** after getting the **response** from the **INITIAL_REQUEST.**
**Additional Info**
kamailio server : 4.2
platform : linux
--
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/2143
[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 …
[View More]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
- [x] Related to issue #3502
#### Description
From https://www.openssl.org/docs/man3.0/man7/migration_guide.html
> Use of low-level digest functions such as SHA1_Init(3) have been informally
> discouraged from use for a long time. Applications should instead use the
> high level EVP APIs EVP_DigestInit_ex(3), EVP_DigestUpdate(3) and
> EVP_DigestFinal_ex(3), or the quick one-shot EVP_Q_digest(3).
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3518
-- Commit Summary --
* crypto: SHA1_Init deprecated at openssl 3.0
-- File Changes --
M src/modules/crypto/crypto_uuid.c (19)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3518.patchhttps://github.com/kamailio/kamailio/pull/3518.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3518
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3518(a)github.com>
[View Less]
Hello everyone,
I'm trying to authenticate kamailio users using freeradius but I get the following error message when I try to start kamailio:
ERROR: <core> [core/cfg.y:3762]: yyparse(): cfg. parser: failed to find command radius_www_authorize (params 1).
Thanks for your help.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3525
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3525(a)github.com>
<!-- 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
- [x] Small bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds new functionality)
- [ ] Breaking change (fix or feature that would change existing functionality)
#### Checklist:
<!-- Go over all points below, and after creating the PR, tick the checkboxes that apply -->
- [ ] PR should be backported to stable branches
- [x] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
The module has been broken in d00ceda2c04. The code to replace strcpy() did not terminate the target sting with \0.
Discovered by our voiptests rig:
https://github.com/sippy/voiptests/actions/workflows/kamailio.yml
Results in a broken SDP (note garbage around o= attribute:
```
1681 00:00:08.271/GLOBAL/alice_ua: RECEIVED message from [::1]:5060:
1682 SIP/2.0 183 Session Progress
1683 Via: SIP/2.0/UDP [::1]:5061;received=::1;rport=5061;branch=z9hG4bK20a1169c6781e4bfe26554e84d3b4925
1684 Record-Route: <sip:[::1];ftag=l5v4RNY4iYqP.*!0LQUA.MLVq8RX'm!q;lr>
1685 From: "Alice Smith" <sip:alice_2_ipv6@[::1]>;tag=l5v4RNY4iYqP.*!0LQUA.MLVq8RX'm!q
1686 To: <sip:bob_2@[::1]>;tag=c77c4b2c8430cf6c18566bc3d9212ed3
1687 Call-ID: O%CciL!Yf0-SQn]G46v4J(SPddRr<MtH(a))<0.ev}(]q.\%X[>
1688 CSeq: 200 INVITE
1689 Content-Type: application/sdp
1690 Content-Length: 296
1691
1692 v=0
1693 o=- 577651195072 577651195072 IN IP6 ::1\x86zU
1694 s=BOBSDP Session
1695 c=IN IP6 ::1\x86zU
1696 t=0 0
1697 m=image 13424 udptl t38
1698 a=T38FaxVersion:0
1699 a=T38MaxBitRate:14400
1700 a=T38FaxRateManagement:transferredTCF
1701 a=T38FaxMaxBuffer:262
1702 a=T38FaxMaxDatagram:176
1703 a=T38FaxUdpEC:t38UDPRedundancy
1704 a=nortpproxy:yes
1740 00:00:08.322/GLOBAL/alice_ua: RECEIVED message from 127.0.0.1:5060:
1741 SIP/2.0 183 Session Progress
1742 v: SIP/2.0/UDP 127.0.0.1:5061;received=127.0.0.1;rport=5061;branch=z9hG4bK8e357573055f35a768af0c9be78c836d
1743 Record-Route: <sip:127.0.0.1;ftag=q3~s'YH'`.Krs%LQKdFWrWnWgwPHJHnf;lr>
1744 f: "Alice Smith" <sip:alice_7_ipv4@127.0.0.1>;tag=q3~s'YH'`.Krs%LQKdFWrWnWgwPHJHnf
1745 t: <sip:bob_7@127.0.0.1>;tag=8ee80e5205ef358c3cb868fb5e5614f8
1746 i: m6!(QAFQlv}vTlycDH[rpMjW}mVV1phG@z/c{KI:L*n'[`%15
1747 CSeq: 200 INVITE
1748 c: application/sdp
1749 l: 328
1750
1751 v=0
1752 o=- 577651195078 577651195078 IN IP4 127.0.0.1z\xcfpzG\xd1\xcb`\xef=\x86zU
1753 s=BOBSDP Session
1754 c=IN IP4 127.0.0.1z\xcfpzG\xd1\xcb`\xef=\x86zU
1755 t=0 0
1756 m=image 13696 udptl t38
1757 a=T38FaxVersion:0
1758 a=T38MaxBitRate:14400
1759 a=T38FaxRateManagement:transferredTCF
1760 a=T38FaxMaxBuffer:262
1761 a=T38FaxMaxDatagram:176
1762 a=T38FaxUdpEC:t38UDPRedundancy
1763 a=nortpproxy:yes
```
Looks like there were multiple changes of the same nature. All of them probably needs to be re-evaluated to make sure this pattern is not propagated.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3524
-- Commit Summary --
* rtpproxy: make sure we null terminate the copy of the string.
-- File Changes --
M src/modules/rtpproxy/rtpproxy.c (3)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3524.patchhttps://github.com/kamailio/kamailio/pull/3524.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3524
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3524(a)github.com>
[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 -->
CDR avp() mos values gets trimmed at the first larger mos value received.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3517
-- Commit Summary --
* rtpengine: increase buf size to print mos llint range
-- File Changes --
M src/modules/rtpengine/rtpengine.c (32)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3517.patchhttps://github.com/kamailio/kamailio/pull/3517.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3517
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3517(a)github.com>
[View Less]
Module: kamailio
Branch: master
Commit: 8b1139851d9f88add1fd7da0dbc0b2b56933cdd3
URL: https://github.com/kamailio/kamailio/commit/8b1139851d9f88add1fd7da0dbc0b2b…
Author: Stefan Mititelu <stefan-cristian.mititelu(a)1and1.ro>
Committer: Stefan Mititelu <stefan.mititelu(a)govoip.ro>
Date: 2023-07-20T15:25:37+03:00
rtpengine: increase buf size to print mos llint range
---
Modified: src/modules/rtpengine/rtpengine.c
---
Diff: https://github.com/kamailio/kamailio/commit/…
[View More]8b1139851d9f88add1fd7da0dbc0b2b…
Patch: https://github.com/kamailio/kamailio/commit/8b1139851d9f88add1fd7da0dbc0b2b…
---
diff --git a/src/modules/rtpengine/rtpengine.c b/src/modules/rtpengine/rtpengine.c
index 59bcfb47795..68003908268 100644
--- a/src/modules/rtpengine/rtpengine.c
+++ b/src/modules/rtpengine/rtpengine.c
@@ -180,14 +180,15 @@ struct minmax_mos_label_stats
};
struct minmax_stats_vals
{
- long long mos;
- long long at;
- long long packetloss;
- long long jitter;
- long long roundtrip;
- long long roundtrip_leg;
- long long samples;
- long long avg_samples; /* our own running count to average the averages */
+ long long int mos;
+ long long int at;
+ long long int packetloss;
+ long long int jitter;
+ long long int roundtrip;
+ long long int roundtrip_leg;
+ long long int samples;
+ long long int
+ avg_samples; /* our own running count to average the averages */
};
#define RTPE_LIST_VERSION_DELAY 10
@@ -3879,12 +3880,13 @@ static void avp_print_decimal(pv_elem_t *pv, int num, struct sip_msg *msg)
len = snprintf(buf, sizeof(buf), "%i.%i", num / 10, abs(num % 10));
avp_print_s(pv, buf, len, msg);
}
-static void avp_print_int(pv_elem_t *pv, int num, struct sip_msg *msg)
+static void avp_print_llint(
+ pv_elem_t *pv, long long int num, struct sip_msg *msg)
{
int len;
- char buf[8];
+ char buf[20];
- len = snprintf(buf, sizeof(buf), "%i", num);
+ len = snprintf(buf, sizeof(buf), "%lld", num);
avp_print_s(pv, buf, len, msg);
}
static void avp_print_time(pv_elem_t *pv, int num, struct sip_msg *msg)
@@ -3904,12 +3906,13 @@ static void avp_print_mos(struct minmax_mos_stats *s,
avp_print_decimal(s->mos_pv, vals->mos / vals->avg_samples, msg);
avp_print_time(s->at_pv, vals->at - created, msg);
- avp_print_int(s->packetloss_pv, vals->packetloss / vals->avg_samples, msg);
- avp_print_int(s->jitter_pv, vals->jitter / vals->avg_samples, msg);
- avp_print_int(s->roundtrip_pv, vals->roundtrip / vals->avg_samples, msg);
- avp_print_int(
+ avp_print_llint(
+ s->packetloss_pv, vals->packetloss / vals->avg_samples, msg);
+ avp_print_llint(s->jitter_pv, vals->jitter / vals->avg_samples, msg);
+ avp_print_llint(s->roundtrip_pv, vals->roundtrip / vals->avg_samples, msg);
+ avp_print_llint(
s->roundtrip_leg_pv, vals->roundtrip_leg / vals->avg_samples, msg);
- avp_print_int(s->samples_pv, vals->samples / vals->avg_samples, msg);
+ avp_print_llint(s->samples_pv, vals->samples / vals->avg_samples, msg);
}
static int decode_mos_vals_dict(
[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
- [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 -->
Make sure dialog cbs list is NULL after is destroyed.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3514
-- Commit Summary --
* dialog: set cbs list to NULL after destroying
-- File Changes --
M src/modules/dialog/dlg_hash.c (5)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3514.patchhttps://github.com/kamailio/kamailio/pull/3514.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3514
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3514(a)github.com>
[View Less]
Hello,
Kamailio SIP Server v5.5.7 stable release is out.
This is a maintenance release of the stable branch 5.5 that includes
fixes since the release of v5.5.6. There is no change to
database schema or configuration language structure that you have to do
on previous installations of v5.5.x. Deployments running previous v5.5.x
versions are strongly recommended to be upgraded to v5.5.7.
Note that 5.5 is now the third last stable branch, v5.5.7 being the last
planned released in 5.5.x series. …
[View More]The latest two stable branch are 5.6
and 5.7, with v5.7.1 being released a while ago.
For more details about version 5.5.7 (including links and guidelines to
download the tarball or from GIT repository), visit:
* https://www.kamailio.org/w/2023/07/kamailio-v5-5-7-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
Kamailio World Conference - www.kamailioworld.com
[View Less]
Hello,
I am planning to release v5.5.7 our of branch 5.5 this week, most likely
on Wednesday, July 19, 2023. It will mark the end of official packaging
for release series 5.5.x, currently the latest two stable branches are
5.6 and 5.7.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - www.kamailioworld.com
Module: kamailio
Branch: master
Commit: c35088bf31b3e3e828433bf03b6ce647a75ef8e2
URL: https://github.com/kamailio/kamailio/commit/c35088bf31b3e3e828433bf03b6ce64…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2023-07-18T16:38:20+02:00
geoip2: docs - section ids and formatting
---
Modified: src/modules/geoip2/doc/geoip2_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/…
[View More]c35088bf31b3e3e828433bf03b6ce64…
Patch: https://github.com/kamailio/kamailio/commit/c35088bf31b3e3e828433bf03b6ce64…
---
diff --git a/src/modules/geoip2/doc/geoip2_admin.xml b/src/modules/geoip2/doc/geoip2_admin.xml
index 50a7d855fa8..cbc6ccb1493 100644
--- a/src/modules/geoip2/doc/geoip2_admin.xml
+++ b/src/modules/geoip2/doc/geoip2_admin.xml
@@ -11,26 +11,25 @@
<!-- Module User's Guide -->
<chapter>
-
+
<title>&adminguide;</title>
-
+
<section>
<title>Overview</title>
<para>
- This module allows real-time queries against the Max Mind GeoIP2
- database to be performed from the config script.
+ This module allows real-time queries against the Max Mind GeoIP2
+ database to be performed from the config script.
</para>
<para>
- The Max Mind GeoIP2 database is a map of IP network address assignments
+ The Max Mind GeoIP2 database is a map of IP network address assignments
to geographical locales that can be useful -- though approximate --
in identifying the physical location with which an IP host address
is associated on a relatively granular level.
</para>
<para>
- This database itself can be obtained on a free or commercial basis
+ This database itself can be obtained on a free or commercial basis
from <ulink url="http://dev.maxmind.com/geoip/">
- http://dev.maxmind.com/geoip/</ulink>. The
- library libmaxminddb
+ http://dev.maxmind.com/geoip/</ulink>. The library libmaxminddb
that interfaces with the Max Mind API, as well as scripts to
automate downloading of the on-disk version are available at
<ulink url="http://dev.maxmind.com/geoip/geoip2/downloadable/">
@@ -126,10 +125,10 @@ if(geoip2_match("$si", "src")) {
</example>
</section>
</section>
-
+
<section>
<title>Functions</title>
- <section>
+ <section id="geoip.f.geoip2_match">
<title>
<function moreinfo="none">geoip2_match(ipaddr, pvc)</function>
</title>
@@ -149,7 +148,7 @@ if(geoip2_match("$si", "src"))
</programlisting>
</example>
</section>
- <section>
+ <section id="geoip.f.geoip2_distance">
<title>
<function moreinfo="none">geoip2_distance(ip_addr, latitude, longitude)</function>
</title>
@@ -172,7 +171,7 @@ if(geoip2_match("$si", "src"))
</programlisting>
</example>
</section>
-
+
</section>
<section>
@@ -195,13 +194,13 @@ if(geoip2_match("$si", "src"))
</example>
</section>
</section>
-
- <section>
+
+ <section id="geoip.pvs">
<title>Exported pseudo-variables</title>
<itemizedlist>
<listitem><para>
- <emphasis>$gip2(pvc=>key)</emphasis> - <emphasis>pvc</emphasis> is an
- identifier for this query result; it is designated by the second
+ <emphasis>$gip2(pvc=>key)</emphasis> - <emphasis>pvc</emphasis> is an
+ identifier for this query result; it is designated by the second
parameter of geoip2_match(). The <emphasis>key</emphasis> can be one of
the following:
</para>
[View Less]
kamctl: added new options to dispatcher interface
- added a new `rmip` option to delete a specific gateway `ip` in a predefined `setid`
- added a new `rmset` option to delete a specific `setid` completely
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3512
-- Commit Summary --
* Add support for deleting a gateway or full setid in dispatcher.
* Small style fix to help screen
-- File Changes --
M utils/kamctl/kamctl (34)
…
[View More] M utils/kamctl/kamctl.base (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3512.patchhttps://github.com/kamailio/kamailio/pull/3512.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3512
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3512(a)github.com>
[View Less]
Adding support for secure AMQP connections over TLS (amqps).
<!-- 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 …
[View More]contributed under BSD for core and main components (tm, sl, auth, tls)
- code is contributed GPLv2 or a compatible license for the other components
- GPL code is contributed with OpenSSL licensing exception
-->
#### Pre-Submission Checklist
<!-- Go over all points below, and after creating the PR, tick all the checkboxes that apply -->
<!-- All points should be verified, otherwise, read the CONTRIBUTING guidelines from above-->
<!-- If you're unsure about any of these, don't hesitate to ask on sr-dev mailing list -->
- [x] Commit message has the format required by CONTRIBUTING guide
- [x] Commits are split per component (core, individual modules, libs, utils, ...)
- [x] Each component has a single commit (if not, squash them into one commit)
- [ ] 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/3511
-- Commit Summary --
* rabbitmq: Adding amqps support
-- File Changes --
M src/modules/rabbitmq/rabbitmq.c (33)
M src/modules/rabbitmq/rabbitmq.h (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3511.patchhttps://github.com/kamailio/kamailio/pull/3511.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3511
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3511(a)github.com>
[View Less]
Module: kamailio
Branch: 5.5
Commit: edfbecd0ed515dab637a03a793c6c2d565dfdaee
URL: https://github.com/kamailio/kamailio/commit/edfbecd0ed515dab637a03a793c6c2d…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2023-07-17T11:17:12+02:00
sst: fix condition on sst_min_se for sst_check_min()
(cherry picked from commit a059af04ac47fd31238ca4f22ad868529e035c43)
(cherry picked from commit …
[View More]febfc9722f83d992a3c1643fa373468b73cb3fa0)
(cherry picked from commit 5fc4cca395e057714376b681bbad4935a9570d0d)
---
Modified: src/modules/sst/sst_handlers.c
---
Diff: https://github.com/kamailio/kamailio/commit/edfbecd0ed515dab637a03a793c6c2d…
Patch: https://github.com/kamailio/kamailio/commit/edfbecd0ed515dab637a03a793c6c2d…
---
diff --git a/src/modules/sst/sst_handlers.c b/src/modules/sst/sst_handlers.c
index 55010baaee2..690c03ddfac 100644
--- a/src/modules/sst/sst_handlers.c
+++ b/src/modules/sst/sst_handlers.c
@@ -672,7 +672,7 @@ int ki_sst_check_min(struct sip_msg *msg, int flag)
* too small. We will take the smaller of the messages
* Session-expires and min-se if stated.
*/
- if (sst_min_se < MIN(minse, se.interval)) {
+ if(sst_min_se > MIN(minse, se.interval)) {
/*
* Too small. See if we need to send the 422 and are able
* to send it.
[View Less]
Module: kamailio
Branch: 5.5
Commit: 2555e1b1a02af8d96504c43953ab395097c86adb
URL: https://github.com/kamailio/kamailio/commit/2555e1b1a02af8d96504c43953ab395…
Author: Ovidiu Sas <osas(a)voipembedded.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2023-07-17T11:16:44+02:00
tm: enhance documentation for on_sl_reply param
(cherry picked from commit a4970749b2be40cd598d4ce5cf2eaa6b38fc2307)
(cherry picked from commit 2f86215a704ff10a58cb3f5e57497918c381a048)
---…
[View More]
Modified: src/modules/tm/doc/params.xml
---
Diff: https://github.com/kamailio/kamailio/commit/2555e1b1a02af8d96504c43953ab395…
Patch: https://github.com/kamailio/kamailio/commit/2555e1b1a02af8d96504c43953ab395…
---
diff --git a/src/modules/tm/doc/params.xml b/src/modules/tm/doc/params.xml
index 247d6ad5e6d..d8f8251818d 100644
--- a/src/modules/tm/doc/params.xml
+++ b/src/modules/tm/doc/params.xml
@@ -715,7 +715,7 @@ modparam("tm", "reparse_on_dns_failover", 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.
+ receives a string parameter with the event name, respectively "on_sl_reply".
</para>
<example>
<title>Set <varname>on_sl_reply</varname> parameter</title>
@@ -727,6 +727,20 @@ modparam("tm", "on_sl_reply", "stateless_replies")
onreply_route["stateless_replies"] {
# do not allow stateless replies to be forwarded
return 0;
+}
+ </programlisting>
+ </example>
+ <example>
+ <title>Set <varname>on_sl_reply</varname> parameter (KEMI javascript)</title>
+ <programlisting>
+...
+modparam("tm", "on_sl_reply", "ksr_slreply")
+...
+-- event callback function implemented in javascript
+function ksr_slreply(evname) {
+ # the evname is set to "on_sl_reply"
+ # do not allow stateless replies to be forwarded
+ KSR.x.drop();
}
</programlisting>
</example>
[View Less]
Module: kamailio
Branch: 5.6
Commit: 5fc4cca395e057714376b681bbad4935a9570d0d
URL: https://github.com/kamailio/kamailio/commit/5fc4cca395e057714376b681bbad493…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2023-07-17T10:44:58+02:00
sst: fix condition on sst_min_se for sst_check_min()
(cherry picked from commit a059af04ac47fd31238ca4f22ad868529e035c43)
(cherry picked from commit …
[View More]febfc9722f83d992a3c1643fa373468b73cb3fa0)
---
Modified: src/modules/sst/sst_handlers.c
---
Diff: https://github.com/kamailio/kamailio/commit/5fc4cca395e057714376b681bbad493…
Patch: https://github.com/kamailio/kamailio/commit/5fc4cca395e057714376b681bbad493…
---
diff --git a/src/modules/sst/sst_handlers.c b/src/modules/sst/sst_handlers.c
index 55010baaee2..690c03ddfac 100644
--- a/src/modules/sst/sst_handlers.c
+++ b/src/modules/sst/sst_handlers.c
@@ -672,7 +672,7 @@ int ki_sst_check_min(struct sip_msg *msg, int flag)
* too small. We will take the smaller of the messages
* Session-expires and min-se if stated.
*/
- if (sst_min_se < MIN(minse, se.interval)) {
+ if(sst_min_se > MIN(minse, se.interval)) {
/*
* Too small. See if we need to send the 422 and are able
* to send it.
[View Less]
Module: kamailio
Branch: 5.6
Commit: 2f86215a704ff10a58cb3f5e57497918c381a048
URL: https://github.com/kamailio/kamailio/commit/2f86215a704ff10a58cb3f5e5749791…
Author: Ovidiu Sas <osas(a)voipembedded.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2023-07-17T10:38:18+02:00
tm: enhance documentation for on_sl_reply param
(cherry picked from commit a4970749b2be40cd598d4ce5cf2eaa6b38fc2307)
---
Modified: src/modules/tm/doc/params.xml
---
Diff: https://…
[View More]github.com/kamailio/kamailio/commit/2f86215a704ff10a58cb3f5e5749791…
Patch: https://github.com/kamailio/kamailio/commit/2f86215a704ff10a58cb3f5e5749791…
---
diff --git a/src/modules/tm/doc/params.xml b/src/modules/tm/doc/params.xml
index 3f67ae3f4d9..8c01ab78d0c 100644
--- a/src/modules/tm/doc/params.xml
+++ b/src/modules/tm/doc/params.xml
@@ -715,7 +715,7 @@ modparam("tm", "reparse_on_dns_failover", 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.
+ receives a string parameter with the event name, respectively "on_sl_reply".
</para>
<example>
<title>Set <varname>on_sl_reply</varname> parameter</title>
@@ -727,6 +727,20 @@ modparam("tm", "on_sl_reply", "stateless_replies")
onreply_route["stateless_replies"] {
# do not allow stateless replies to be forwarded
return 0;
+}
+ </programlisting>
+ </example>
+ <example>
+ <title>Set <varname>on_sl_reply</varname> parameter (KEMI javascript)</title>
+ <programlisting>
+...
+modparam("tm", "on_sl_reply", "ksr_slreply")
+...
+-- event callback function implemented in javascript
+function ksr_slreply(evname) {
+ # the evname is set to "on_sl_reply"
+ # do not allow stateless replies to be forwarded
+ KSR.x.drop();
}
</programlisting>
</example>
[View Less]