sr-dev July 2017

sr-dev@lists.kamailio.org

23 participants
410 discussions

[kamailio] dmq_usrloc replication and max_contacts (Kamailio v4.3.1) (#265)

by 00Asgaroth00

This is a snip from the user's mailing list, I'm just adding it to the issue tracker, as it is yet to be confirmed as a bug, only here for tracking pruporses: ``` I have a situation where I have 2 devices registering with the same AOR, I have the registrar module's max_contacts parameter set to 1 and I use the 0x04 flag on the save function. When I use dmq_usrloc for replication, I can see 2 contacts registered for the AOR on the "client" nodes whereas the node where the actual registration took place only has 1 contact for the AOR. ``` ``` It seems to me like another bug, although again I'm not familiar with the module so can't be sure without looking that it is not intended behaviour. I plan to look later this week when I have some time but in the meantime, you can send me the examples directly if you like. ``` --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/265

7 years

[kamailio] having keep-alive response count before ending the dialog (#438)

by jayesh1017

Kamailio takes care of sending in-dialog keep-alives using OPTIONS when dlg_set_attribute ka-src and ka-dst is used. It also sends OPTIONS to correct address if a client sends Re-Invite indicating a network change, which is a common case with mobile clients (switching between mobile-data and Wifi) fixed in #273 The problem is that it ends the dialog on missing even one keep-alive response. Missing a response is possible when the client is handling the network change and keep-alive is sent around that time. Thus, having a configurable counter after which you expect to end the dialog might be helpful. For eg. you decide to end the dialog after we miss 3 responses for keep-alives in a row. Something like dlg_set_attribute(ka-src, 3) where 3 indicates the number of responses that can be missed before ending the dialog. --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/438

7 years

[kamailio/kamailio] redis support into usrloc (#1137)

by Surendra Tiwari

### Description  ### Troubleshooting #### Reproduction  #### Debugging Data  ``` (paste your debugging data here) ``` #### Log Messages  ``` (paste your log messages here) ``` #### SIP Traffic  ``` (paste your sip traffic here) ``` ### Possible Solutions  ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` (paste your output here) ``` * **Operating System**:  ``` (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/1137

7 years

git:master:b450a769: Updated P-CSCF example with additional Rx_AAR params

by Richard Good

Module: kamailio Branch: master Commit: b450a769cff3b5c8ea0962299f6b087da089cd59 URL: https://github.com/kamailio/kamailio/commit/b450a769cff3b5c8ea0962299f6b087… Author: Richard Good <richard.good(a)smilecoms.com> Committer: Richard Good <richard.good(a)smilecoms.com> Date: 2014-12-17T10:58:00+02:00 Updated P-CSCF example with additional Rx_AAR params --- Modified: examples/pcscf/kamailio.cfg --- Diff: https://github.com/kamailio/kamailio/commit/b450a769cff3b5c8ea0962299f6b087… Patch: https://github.com/kamailio/kamailio/commit/b450a769cff3b5c8ea0962299f6b087… --- diff --git a/examples/pcscf/kamailio.cfg b/examples/pcscf/kamailio.cfg index c09cdc9..c2d5f55 100644 --- a/examples/pcscf/kamailio.cfg +++ b/examples/pcscf/kamailio.cfg @@ -983,7 +983,7 @@ route[Orig_Initial] #!ifdef WITH_RX xlog("L_DBG","Diameter: Orig authorizing media via Rx\n"); - if(Rx_AAR("ORIG_SESSION_AAR","orig")==0){ + if(Rx_AAR("ORIG_SESSION_AAR","orig","",-1)==0){ exit; } } @@ -1035,7 +1035,7 @@ onreply_route[Orig_Initial_reply] #!ifdef WITH_RX if (t_check_status("180|183|200")){ xlog("L_DBG","Diameter: Orig authorizing media via Rx\n"); - if(Rx_AAR("ORIG_SESSION_AAR_REPLY","orig")==0){ + if(Rx_AAR("ORIG_SESSION_AAR_REPLY","orig","",-1)==0){ exit; } } @@ -1089,7 +1089,7 @@ route[Term_Initial] #!ifdef WITH_RX xlog("L_DBG","Diameter: Term authorizing media via Rx\n"); - if(Rx_AAR("TERM_SESSION_AAR","term")==0){ + if(Rx_AAR("TERM_SESSION_AAR","term","",-1)==0){ exit; } } @@ -1138,7 +1138,7 @@ onreply_route[Term_Initial_reply] #!ifdef WITH_RX if (t_check_status("180|183|200")){ xlog("L_DBG","Diameter: Orig authorizing media via Rx\n"); - if(Rx_AAR("TERM_SESSION_AAR_REPLY","term")==0){ + if(Rx_AAR("TERM_SESSION_AAR_REPLY","term","",-1)==0){ exit; } }

7 years

git:master:419275a5: evrexec: new module to execute an event route at startup in a dedicated process

by Daniel-Constantin Mierla

Module: kamailio Branch: master Commit: 419275a588d0f655d98ac80591cbd8756803b8ee URL: https://github.com/kamailio/kamailio/commit/419275a588d0f655d98ac80591cbd87… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2017-04-12T10:03:33+02:00 evrexec: new module to execute an event route at startup in a dedicated process --- Added: src/modules/evrexec/Makefile Added: src/modules/evrexec/README Added: src/modules/evrexec/doc/Makefile Added: src/modules/evrexec/doc/evrexec.xml Added: src/modules/evrexec/doc/evrexec_admin.xml Added: src/modules/evrexec/evrexec_mod.c --- Diff: https://github.com/kamailio/kamailio/commit/419275a588d0f655d98ac80591cbd87… Patch: https://github.com/kamailio/kamailio/commit/419275a588d0f655d98ac80591cbd87…

7 years, 2 months

[kamailio/kamailio] dmq & dmq_usrloc : let server_address & notification_address use the same IP and port (#1109)

by 张顺通

if server_address & notification_address use same ip and different port(see below)，in dmq.list_nodes will have two node for one kamailio(one node for notify_server 5360 and one for dmq local 5260), question is when send REGISTER to port 5160, REGISTER will copy from port 5260 to 5360 on the same kamailio,this is not what i want. dmq & dmq_usrloc cfg(**different port**): listen=eth0:5160 listen=eth0:5260 listen=eth0:5360 modparam("dmq", "server_address", "sip:10.6.1.200:5260") modparam("dmq", "notification_address", "sip:10.6.1.200:5360") modparam("dmq", "multi_notify", 1) modparam("dmq", "num_workers", 2) # ----- dmq_usrloc params ----- modparam("dmq_usrloc", "enable", 1) modparam("dmq_usrloc", "sync", 1) modparam("dmq_usrloc", "batch_msg_contacts", 50) modparam("dmq_usrloc", "batch_msg_size", 500000) And when I let server_address & notification_address use same IP & Port, check in function add_server_and_notify will report error("error adding notification node"),child_init will return failed. So I suggest that the following changes, let server_address & notification_address can use the same IP and port： @@ -315,11 +315,15 @@ dmq_node_t* add_server_and_notify(str *paddr) for (index = 0; index < host_cnt; index++) { pstr->s = puri_list [index]; pstr->len = strlen (puri_list [index]); - if (!find_dmq_node_uri(node_list, pstr)) { // check for duplicates + if (!(pnode = find_dmq_node_uri(node_list, pstr))) { // check for duplicates pnode = add_dmq_node (node_list, pstr); if (pnode && !pfirst) { pfirst = pnode; } - } + } else { + if (!pfirst) { + pfirst = pnode; + } + } } } After Such A change, dmq.list_nodes will only have on node for (notify_server & server_addr(local)). Is there any problem with this modification? Thanks $./sbin/kamailio -v version: kamailio 5.0.1 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, 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. -- 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/1109

7 years, 3 months

[kamailio/kamailio] Incorrect routing of RPACK packets with topos module (#1167)

by Sergey Lavrov

### Description  Kamailio incorrectly routed RPACK packets with topos module enabled. In the same time there is no problem with topoh module enabled. It's seems like related to #1097, ### Troubleshooting #### SIP Traffic  RPACK SIP packets with Kamailio topos module: http://imgur.com/SScErQp RPACK SIP packets with Kamailio topoh module: http://imgur.com/45ch3HB ### Possible Solutions  ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.1.0-dev4 (x86_64/linux) (git revision 7dbf3fe) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, 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 on 00:24:21 Jun 26 2017 with gcc 4.8.5 ``` * **Operating System**:  ``` Red Hat Enterprise Linux Server release 7.3 (Maipo) Linux 2.6.32-042stab113.21 #1 SMP Wed Mar 23 11:05:25 MSK 2016 x86_64 x86_64 x86_64 GNU/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/1167

7 years, 3 months

[kamailio/kamailio] pkg/kamailio/centos/7: Packages sipcapture module (#1106)

by sergey-safarov

You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/1106 -- Commit Summary -- * pkg/kamailio/centos/7: Packages sipcapture module -- File Changes -- A etc/kamailio-sipcapture.cfg (986) M pkg/kamailio/centos/7/kamailio.spec (40) A pkg/kamailio/centos/7/sipcapture.service (25) A pkg/kamailio/centos/7/sipcapture.sysconfig (12) A pkg/kamailio/centos/7/sipcapture.tmpfiles (1) M src/Makefile (14) -- Patch Links -- https://github.com/kamailio/kamailio/pull/1106.patch https://github.com/kamailio/kamailio/pull/1106.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/1106

7 years, 3 months

[kamailio/kamailio] app_python: fix compiler warning (#924)

by Victor Seva

> Add "-fno-strict-aliasing" to compilation flags > > Fixes a slew of: > "dereferencing type-punned pointer will break strict-aliasing rules" > warnings from GCC for lines of the form: > Py_INCREF(Py_True); > and > Py_INCREF(Py_False); > > due to the cast from PyIntObject* to PyObject* > > GCC is technically correct here; see: > http://www.python.org/dev/peps/pep-3123/ > though this is unlikely to lead to non-working machine code. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/924 -- Commit Summary -- * app_python: fix compiler warning -- File Changes -- M src/modules/app_python/Makefile (2) -- Patch Links -- https://github.com/kamailio/kamailio/pull/924.patch https://github.com/kamailio/kamailio/pull/924.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/924

7 years, 4 months

[kamailio/kamailio] Daemon not restated if process exited with not null code (#1085)

by sergey-safarov

Details in attached log file. [kamailio-fail.txt](https://github.com/kamailio/kamailio/files/949032/kamail… -- 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/1085

7 years, 5 months

← Newer
1
2
3
4
5
6
7
8
9
...
41
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev July 2017