<!-- Kamailio Pull Request Template -->
<!--
IMPORTANT:
- for detailed contributing guidelines, read:
https://github.com/kamailio/kamailio/blob/master/.github/CONTRIBUTING.md
- pull requests must be done to master branch, unless they are backports
of fixes from master branch to a stable branch
- backports to stable branches must be done with 'git cherry-pick -x ...'
- code is contributed under BSD for core and main components (tm, sl, auth, tls)
- code is contributed GPLv2 or a compatible license for the other components
- GPL code is contributed with OpenSSL licensing exception
-->
#### Pre-Submission Checklist
<!-- Go over all points below, and after creating the PR, tick all the checkboxes that apply -->
<!-- All points should be verified, otherwise, read the CONTRIBUTING guidelines from above-->
<!-- If you're unsure about any of these, don't hesitate to ask on sr-dev mailing list -->
- [x] Commit message has the format required by CONTRIBUTING guide
- [x] Commits are split per component (core, individual modules, libs, utils, ...)
- [x] Each component has a single commit (if not, squash them into one commit)
- [x] No commits to README files for modules (changes must be done to docbook files
in `doc/` subfolder, the README file is autogenerated)
#### Type Of Change
- [ ] 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 -->
- [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 -->
Ported all carrierroute module functions to KEMI API.
Here is an example,
```python3
...
# User location service
def ksr_route_location(self, msg):
if KSR.pv.get("$rm") == "INVITE" and KSR.carrierroute.cr_user_carrier("$fU", "$fd", "$avp(carrier)") > 0:
if KSR.pv.get("$rm") == "INVITE" and KSR.carrierroute.cr_route("$avp(carrier)","$avp(domain)","$rU","$rU","call_id") > 0:
KSR.info('Routing call via user carrier route\n')
self.ksr_route_relay(msg)
rc = KSR.registrar.lookup("location")
if rc < 0:
KSR.tm.t_newtran()
if rc == -1 or rc == -3:
KSR.sl.send_reply(404, "Not Found")
return -255
elif rc == -2:
KSR.sl.send_reply(405, "Method Not Allowed")
return -255
# when routing via usrloc, log the missed calls also
if KSR.is_INVITE() :
KSR.setflag(FLT_ACCMISSED)
self.ksr_route_relay(msg)
return -255
...
```
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3247
-- Commit Summary --
* KEMI API implementation for carrierroute module
-- File Changes --
M src/modules/carrierroute/carrierroute.c (50)
M src/modules/carrierroute/carrierroute.h (1)
M src/modules/carrierroute/cr_func.c (260)
M src/modules/carrierroute/cr_func.h (63)
A src/modules/carrierroute/cr_kemi.c (199)
A src/modules/carrierroute/cr_kemi.h (119)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3247.patchhttps://github.com/kamailio/kamailio/pull/3247.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3247
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3247(a)github.com>
Hello,
Kamailio SIP Server project is organizing another meeting of its
developers during November 16-17, 2022, hosted again by sipgate.de in
Dusseldorf, Germany.
The event is intended to facilitate the interaction between Kamailio
developers and to offer a convenient environment for working together on
several topics of high interest for the project, including writing code
for Kamailio and its tools, improving documentation, or discuss about
future development.
Everyone from the community is welcome to join. Please note we have a
limited capacity of seats in the meeting room, the main policy for
accepting participants being first come first server. Also, very
important to be aware that this is not an event to learn how to use
Kamailio.
More details about the event, the venue, how to register, are available at:
* https://www.kamailio.org/w/developers-meeting/
Looking forward to those two intensive hacking Kamailio days in Dusseldorf!
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - Online
Oct 10-13, 2022 (Europe Timezone)
* https://www.asipto.com/sw/kamailio-advanced-training-online/
<!--
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
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
We have a cluster of two Kamailio nodes on Debian 10 + v5.5.2.
We have added a node and updated to v5.6.1. So now it's a cluster of:
2x debian10 + v5.6.1
1x debian11 + v5.6.1
### Troubleshooting
I'm not sure what is the issue but per `dmesg` logs it seems related to `dmq_usrloc` module. We have a lot of cores, so it's happening constantly since the upgrade and the extra node addition.
#### Debugging Data
[core.kamailio.53605.1663462643.txt](https://github.com/kamailio/kamailio/fi…
#### 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).
-->
```
[155017.987497] kamailio[53605]: segfault at f8 ip 00007fd49cf02f72 sp 00007ffea6e37e70 error 4 in dmq_usrloc.so[7fd49cef0000+17000]
[155017.987527] Code: 40 38 01 d0 89 05 12 95 00 00 48 8b 05 cf 8f 00 00 8b 00 83 f8 01 0f 85 80 00 00 00 48 8b 85 48 ff ff ff 48 8b 80 a0 00 00 00 <8b> 90 f8 00 00 00 48 8b 85 48 ff ff ff 48 8b 80 a0 00 00 00 48 8b
```
#### 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`
```
version: kamailio 5.6.1 (x86_64/linux)
flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, 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_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED
ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, 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 10.2.1
```
* **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 `lsb_release -a` and `uname -a`)
-->
```
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye
Linux sip03.example.com 5.18.0-0.deb11.4-amd64 #1 SMP PREEMPT_DYNAMIC Debian 5.18.16-1~bpo11+1 (2022-08-12) x86_64 GNU/Linux
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3242
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3242(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, 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 -->
This new feature provides a way to have multiple users sharing the same speed dial number, if they belong to the same group.
A new function is add: "sd_lookup_group". It finds the URI for a specific sd_username and group_id (and sd_domain if is_domain value is defined) in the database, returning its URI.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3255
-- Commit Summary --
* speeddial: allow search uri of speed dial by group
-- File Changes --
M src/modules/speeddial/doc/speeddial_admin.xml (35)
M src/modules/speeddial/sdlookup.h (2)
M src/modules/speeddial/speeddial.c (8)
M src/modules/speeddial/speeddial.h (15)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3255.patchhttps://github.com/kamailio/kamailio/pull/3255.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3255
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3255(a)github.com>
Module: kamailio
Branch: master
Commit: 6f400a8074fe60916867596431ca26dff00435d1
URL: https://github.com/kamailio/kamailio/commit/6f400a8074fe60916867596431ca26d…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2022-09-30T11:46:18+02:00
modules: readme files regenerated - carrierroute ... [skip ci]
---
Modified: src/modules/carrierroute/README
---
Diff: https://github.com/kamailio/kamailio/commit/6f400a8074fe60916867596431ca26d…
Patch: https://github.com/kamailio/kamailio/commit/6f400a8074fe60916867596431ca26d…
---
diff --git a/src/modules/carrierroute/README b/src/modules/carrierroute/README
index ad924c1ca2..ba1d19d230 100644
--- a/src/modules/carrierroute/README
+++ b/src/modules/carrierroute/README
@@ -41,7 +41,7 @@ Lucian Balaceanu
4. Functions
- 4.1. cr_user_carrier(user, domain, dstavp)
+ 4.1. cr_user_carrier(user, domain, dstvar)
4.2. cr_route(carrier, domain, prefix_matching,
rewrite_user, hash_source, descavp)
@@ -185,7 +185,7 @@ Chapter 1. Admin Guide
4. Functions
- 4.1. cr_user_carrier(user, domain, dstavp)
+ 4.1. cr_user_carrier(user, domain, dstvar)
4.2. cr_route(carrier, domain, prefix_matching, rewrite_user,
hash_source, descavp)
@@ -473,7 +473,7 @@ modparam("carrierroute", "avoid_failed_destinations", 0)
4. Functions
- 4.1. cr_user_carrier(user, domain, dstavp)
+ 4.1. cr_user_carrier(user, domain, dstvar)
4.2. cr_route(carrier, domain, prefix_matching, rewrite_user,
hash_source, descavp)
@@ -501,22 +501,23 @@ cr_user_rewrite_uri(uri, domain)
cr_tree_rewrite_uri(tree, domain)
-> cr_route(tree, domain, "$rU", "$rU", "call_id")
-4.1. cr_user_carrier(user, domain, dstavp)
+4.1. cr_user_carrier(user, domain, dstvar)
- This function loads the carrier and stores it in an AVP. It cannot be
- used in the config file mode, as it needs a mapping of the given user
- to a certain carrier. The is derived from a database entry belonging to
- the user parameter. This mapping must be available in the table that is
- specified in the “subscriber_table” variable. This data is not cached
- in memory, that means for every execution of this function a database
- query will be done.
+ This function loads the carrier and stores it in a config variable. It
+ cannot be used in the config file mode, as it needs a mapping of the
+ given user to a certain carrier. The is derived from a database entry
+ belonging to the user parameter. This mapping must be available in the
+ table that is specified in the “subscriber_table” variable. This data
+ is not cached in memory, that means for every execution of this
+ function a database query will be done.
Meaning of the parameters is as follows:
* user - Name of the user for the carrier tree lookup. Additional to
a string any pseudo-variable could be used as input.
* domain - Name of the routing domain to be used. Additional to a
string any pseudo-variable could be used as input.
- * dstavp - Name of the AVP where to store the carrier id.
+ * dstvar - Name of the writaable variable (e.g., an AVP) where to
+ store the carrier id.
4.2. cr_route(carrier, domain, prefix_matching, rewrite_user, hash_source,
descavp)
Module: kamailio
Branch: master
Commit: c32ce4d776d40fe2eccea9007fb842cd8c9c3af9
URL: https://github.com/kamailio/kamailio/commit/c32ce4d776d40fe2eccea9007fb842c…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2022-09-30T11:21:29+02:00
carrierroute: docs updated for cr_user_carrier()
---
Modified: src/modules/carrierroute/doc/carrierroute_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/c32ce4d776d40fe2eccea9007fb842c…
Patch: https://github.com/kamailio/kamailio/commit/c32ce4d776d40fe2eccea9007fb842c…
---
diff --git a/src/modules/carrierroute/doc/carrierroute_admin.xml b/src/modules/carrierroute/doc/carrierroute_admin.xml
index 3b883d75155..341349495ec 100644
--- a/src/modules/carrierroute/doc/carrierroute_admin.xml
+++ b/src/modules/carrierroute/doc/carrierroute_admin.xml
@@ -412,10 +412,10 @@ cr_tree_rewrite_uri(tree, domain)
<section>
<title>
- <function moreinfo="none">cr_user_carrier(user, domain, dstavp)</function>
+ <function moreinfo="none">cr_user_carrier(user, domain, dstvar)</function>
</title>
<para>
- This function loads the carrier and stores it in an AVP.
+ This function loads the carrier and stores it in a config variable.
It cannot be used in the config file mode, as it needs a mapping of the
given user to a certain carrier. The is derived from a database entry
belonging to the user parameter. This mapping must be available in the
@@ -438,7 +438,8 @@ cr_tree_rewrite_uri(tree, domain)
</para>
</listitem>
<listitem>
- <para><emphasis>dstavp</emphasis> - Name of the AVP where to store the carrier id.
+ <para><emphasis>dstvar</emphasis> - Name of the writaable variable (e.g., an AVP)
+ where to store the carrier id.
</para>
</listitem>
</itemizedlist>