sr-dev January 2022

sr-dev@lists.kamailio.org

13 participants
263 discussions

[kamailio/kamailio] db_redis: cluster support (Issue #2977)
by Riccardo-78 23 Feb '22

23 Feb '22

### Description At the moment db_redis driver does not support interfacing with a redis cluster. This is a proposal to add support to it. The db_redis module will get a new module parameter to enable cluster support (with default 0 - disabled): ``` modparam("db_redis", "cluster", 1) ``` The redis url used by other modules needs to specify all nodes in the cluster, and must NOT include redis database number (since it's not supported in cluster mode): ``` #!define DBURL_USRLOC "redis://10.0.1.… [View More]

3 5

[kamailio/kamailio] Kamailio crash with in-memory publ_cache = 2 (Issue #3008)
by Joe Mordica 14 Feb '22

14 Feb '22

### Description Usage of `modparam("presence", "publ_cache", 2)` causes kamailio to crash shortly after starting up. This only happens when subscribe traffic is high (400 requests per second avg). ### Troubleshooting #### Reproduction The issue can be reproduced by starting up kamailio with the option above enabled and ~400 subscribe requests per second. The crash happens ~20 seconds after startup. #### Debugging Data  ``` (paste your debugging data here) ``` #### Log Messages  ``` kernel: kamailio[25401]: segfault at 0 ip 00007f4a0a22d4d7 sp 00007fff6064a370 error 4 in presence.so[7f4a0a21e000+fe000] ``` #### SIP Traffic  ``` (paste your sip traffic here) ``` ### Possible Solutions Running with the default ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` (paste your output here) ``` * **Operating System**:  ``` Linux hostName 2.6.32-754.11.1.el6.x86_64 #1 SMP Tue Feb 26 15:38:56 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux version: kamailio 5.4.3 (x86_64/linux) e19ae3 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_BLACKLIST, HAVE_RESOLV_RES 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: e19ae3 compiled on 18:24:43 Dec 14 2020 with gcc 4.4.7 ``` I realize this is an older version so if it's resolved in a newer one let me know. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3008 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3008(a)github.com> [View Less]

2 9

[kamailio/kamailio] xHTTP_PROM does not include metric_type (Issue #3001)
by mneirynck 08 Feb '22

08 Feb '22

### Description We have a couple of Kamailio containers running on AWS ECS Fargate. Using a Cloudwatch Agent sidecar container I should be able to collect metrics from the Kamailio containers and push them to Cloudwatch for monitoring. ``` xHTTP_PROM exposes the metrics like this: # Kamailio whole internal statistics kamailio_app_python3_traced_replies 0 1640265350616 kamailio_app_python3_traced_requests 0 1640265350616 kamailio_core_bad_URIs_rcvd 0 1640265350616 kamailio_core_bad_msg_hdr 0 … [View More]

3 7

[kamailio/kamailio] Enable CentOS 7 to build with OpenSSL 1.1.1 package from EPEL (#2779)
by space88man 08 Feb '22

08 Feb '22

#### 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 - [ ] Small bug fix (non-breaking change which fixes an issue) - [X] New feature … [View More]

3 13

[kamailio/kamailio] fedora 36: build warnings (Issue #3014)
by sergey-safarov 08 Feb '22

08 Feb '22

**1** ``` CC (gcc) [kamailio] core/crypto/rijndael.o CC (gcc) [kamailio] core/crypto/sha256.o core/crypto/sha256.c:573:32: warning: argument 1 of type 'sha2_byte[]' {aka 'unsigned char[]'} with mismatched bound [-Warray-parameter=] 573 | void sr_SHA256_Final(sha2_byte digest[], SHA256_CTX* context) { | ~~~~~~~~~~^~~~~~~~ In file included from core/crypto/sha256.c:36: core/crypto/sha256.h:157:22: note: previously declared as 'u_int8_t[32]' {aka 'unsigned char[32]'} … [View More] 157 | void sr_SHA256_Final(u_int8_t[SHA256_DIGEST_LENGTH], SHA256_CTX*); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ core/crypto/sha256.c:636:47: warning: argument 2 of type 'char[]' with mismatched bound [-Warray-parameter=] 636 | char *sr_SHA256_End(SHA256_CTX* context, char buffer[]) { | ~~~~~^~~~~~~~ In file included from core/crypto/sha256.c:36: core/crypto/sha256.h:158:34: note: previously declared as 'char[65]' 158 | char* sr_SHA256_End(SHA256_CTX*, char[SHA256_DIGEST_STRING_LENGTH]); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ core/crypto/sha256.c:936:32: warning: argument 1 of type 'sha2_byte[]' {aka 'unsigned char[]'} with mismatched bound [-Warray-parameter=] 936 | void sr_SHA512_Final(sha2_byte digest[], SHA512_CTX* context) { | ~~~~~~~~~~^~~~~~~~ In file included from core/crypto/sha256.c:36: core/crypto/sha256.h:169:22: note: previously declared as 'u_int8_t[64]' {aka 'unsigned char[64]'} 169 | void sr_SHA512_Final(u_int8_t[SHA512_DIGEST_LENGTH], SHA512_CTX*); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ core/crypto/sha256.c:965:47: warning: argument 2 of type 'char[]' with mismatched bound [-Warray-parameter=] 965 | char *sr_SHA512_End(SHA512_CTX* context, char buffer[]) { | ~~~~~^~~~~~~~ In file included from core/crypto/sha256.c:36: core/crypto/sha256.h:170:34: note: previously declared as 'char[129]' 170 | char* sr_SHA512_End(SHA512_CTX*, char[SHA512_DIGEST_STRING_LENGTH]); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ core/crypto/sha256.c:1011:32: warning: argument 1 of type 'sha2_byte[]' {aka 'unsigned char[]'} with mismatched bound [-Warray-parameter=] 1011 | void sr_SHA384_Final(sha2_byte digest[], SHA384_CTX* context) { | ~~~~~~~~~~^~~~~~~~ In file included from core/crypto/sha256.c:36: core/crypto/sha256.h:163:22: note: previously declared as 'u_int8_t[48]' {aka 'unsigned char[48]'} 163 | void sr_SHA384_Final(u_int8_t[SHA384_DIGEST_LENGTH], SHA384_CTX*); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ core/crypto/sha256.c:1040:47: warning: argument 2 of type 'char[]' with mismatched bound [-Warray-parameter=] 1040 | char *sr_SHA384_End(SHA384_CTX* context, char buffer[]) { | ~~~~~^~~~~~~~ In file included from core/crypto/sha256.c:36: core/crypto/sha256.h:164:34: note: previously declared as 'char[97]' 164 | char* sr_SHA384_End(SHA384_CTX*, char[SHA384_DIGEST_STRING_LENGTH]); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ CC (gcc) [kamailio] core/crypto/shautils.o CC (gcc) [kamailio] core/cfg/cfg.o CC (gcc) [kamailio] core/cfg/cfg_ctx.o core/cfg/cfg_ctx.c: In function 'cfg_update_defaults': core/cfg/cfg_ctx.c:287:28: warning: the comparison will always evaluate as 'true' for the pointer operand in '(unsigned char *)&ginst->vars + (sizetype)var->offset' must not be NULL [-Waddress] 287 | if(ginst->vars + var->offset) { | ^~~~~ CC (gcc) [kamailio] core/cfg/cfg_script.o CC (gcc) [kamailio] core/cfg/cfg_select.o CC (gcc) [kamailio] core/cfg/cfg_struct.o CC (gcc) [kamailio] core/utils/srjson.o CC (gcc) [kamailio] core/utils/sruid.o CC (gcc) [kamailio] core/utils/tmrec.o ``` **2** ``` LD (gcc) [M nat_traversal.so] nat_traversal.so CC (gcc) [M nathelper.so] nathelper.o nathelper.c: In function 'nh_alias_to_uri': nathelper.c:2840:12: warning: the comparison will always evaluate as 'true' for the pointer operand in 'memchr_pointer + 1' must not be NULL [-Waddress] 2840 | if(&memchr_pointer[1]){ | ^ CC (gcc) [M nathelper.so] nhelpr_funcs.o LD (gcc) [M nathelper.so] nathelper.so CC (gcc) [M path.so] path.o ``` **3** ``` CC (gcc) [M ims_dialog.so] dlg_handlers.o CC (gcc) [M ims_dialog.so] dlg_hash.o dlg_hash.c: In function 'destroy_dlg': dlg_hash.c:256:9: warning: the comparison will always evaluate as 'true' for the address of 'dlg_entry_out' will never be NULL [-Waddress] 256 | if (&(dlg->dlg_entry_out)) { | ^ In file included from dlg_var.h:26, from dlg_hash.c:15: dlg_hash.h:124:26: note: 'dlg_entry_out' declared here 124 | struct dlg_entry_out dlg_entry_out; /*!< list of dialog_out entries */ | ^~~~~~~~~~~~~ CC (gcc) [M ims_dialog.so] dlg_ng_stats.o CC (gcc) [M ims_dialog.so] dlg_profile.o ``` **4** ``` CC (gcc) [M app_lua_sr.so] app_lua_sr_api.o CC (gcc) [M app_lua_sr.so] app_lua_sr_exp.o app_lua_sr_exp.c: In function 'lua_sr_exp_openlibs': app_lua_sr_exp.c:3686:17: warning: implicit declaration of function 'luaL_openlib'; did you mean 'luaL_openlibs'? [-Wimplicit-function-declaration] 3686 | luaL_openlib(L, "sr.sl", _sr_sl_Map, 0); | ^~~~~~~~~~~~ | luaL_openlibs CC (gcc) [M app_lua_sr.so] app_lua_sr_mod.o LD (gcc) [M app_lua_sr.so] app_lua_sr.so CC (gcc) [M lwsc.so] lwsc_mod.o LD (gcc) [M lwsc.so] lwsc.so ``` **5** ``` CC (gcc) [M nats.so] nats_pub.o In file included from nats_pub.c:25: defs.h:49:24: warning: '_nats_rts' defined but not used [-Wunused-variable] 49 | static nats_evroutes_t _nats_rts; | ^~~~~~~~~ LD (gcc) [M nats.so] nats.so CC (gcc) [M app_perl.so] app_perl_mod.o CC (gcc) [M app_perl.so] perlfunc.o xsubpp -typemap `perl -MConfig -e 'print $Config{installprivlib}'`/ExtUtils/typemap -typemap typemap kamailioxs.xs > kamailioxs.c CC (gcc) [M app_perl.so] kamailioxs.o LD (gcc) [M app_perl.so] app_perl.so CC (gcc) [M db_perlvdb.so] db_perlvdb.o CC (gcc) [M db_perlvdb.so] perlvdb_conv.o perlvdb_conv.c: In function 'conds2perlarray': perlvdb_conv.c:60:29: warning: the comparison will always evaluate as 'true' for the pointer operand in 'ops + (sizetype)((long unsigned int)i * 8)' must not be NULL [-Waddress] 60 | if (ops + i) | ^~~ CC (gcc) [M db_perlvdb.so] perlvdb_oohelpers.o CC (gcc) [M db_perlvdb.so] perlvdbfunc.o make[3]: 'libsrdb1.so.1.0' is up to date. LD (gcc) [M db_perlvdb.so] db_perlvdb.so CC (gcc) [M phonenum.so] phonenum_mod.o CC (gcc) [M phonenum.so] phonenum_pv.o Compiling cphonenumber.cpp ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3014 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3014(a)github.com> [View Less]

2 2

[kamailio/kamailio] misleading-indentation warning (Issue #3012)
by sergey-safarov 08 Feb '22

08 Feb '22

**1** ``` CC (gcc) [M sms.so] libsms_putsms.o CC (gcc) [M sms.so] sms.o CC (gcc) [M sms.so] sms_funcs.o sms_funcs.c: In function 'modem_process': sms_funcs.c:884:17: warning: this 'if' clause does not guard... [-Wmisleading-indentation] 884 | if (used_mem) | ^~ sms_funcs.c:886:25: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'if' 886 | for(i=1,k=1;k<=used_mem && i<=… [View More]max_mem;i++) { | ^~~ CC (gcc) [M sms.so] sms_report.o LD (gcc) [M sms.so] sms.so CC (gcc) [M sst.so] parse_sst.o ``` **2** ``` CC (gcc) [M ims_charging.so] ims_charging_stats.o CC (gcc) [M ims_charging.so] ims_ro.o ims_ro.c: In function 'create_cca_fui_avps': ims_ro.c:1622:5: warning: this 'else' clause does not guard... [-Wmisleading-indentation] 1622 | else | ^~~~ ims_ro.c:1625:9: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'else' 1625 | if (redirecturi && redirecturi->len >0 && redirecturi->s) { | ^~ CC (gcc) [M ims_charging.so] ro_avp.o CC (gcc) [M ims_charging.so] ro_db_handler.o CC (gcc) [M ims_charging.so] ro_fixup.o ``` **3** ``` CC (gcc) [M kazoo.so] kazoo.o CC (gcc) [M kazoo.so] kz_amqp.o kz_amqp.c: In function 'kz_amqp_channel_close': kz_amqp.c:802:5: warning: this 'if' clause does not guard... [-Wmisleading-indentation] 802 | if (!rmq) | ^~ In file included from ../../core/mem/pkg.h:32, from ../../core/mem/mem.h:41, from kz_amqp.c:38: ../../core/mem/../dprint.h:298:25: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'if' 298 | do { \ | ^~ ../../core/mem/../dprint.h:345:25: note: in expansion of macro 'LOG_FX' 345 | LOG_FX(facility, level, lname, prefix, _FUNC_NAME_, fmt, ## args) | ^~~~~~ ../../core/mem/../dprint.h:351:25: note: in expansion of macro 'LOG_FL' 351 | LOG_FL(facility, level, NULL, prefix, fmt, ## args) | ^~~~~~ ../../core/mem/../dprint.h:354:25: note: in expansion of macro 'LOG_FP' 354 | LOG_FP(DEFAULT_FACILITY, (level), LOC_INFO, fmt, ## args) | ^~~~~~ ../../core/mem/../dprint.h:401:45: note: in expansion of macro 'LOG' 401 | # define DBG(fmt, args...) LOG(L_DBG, fmt , ## args) | ^~~ ../../core/mem/../dprint.h:405:36: note: in expansion of macro 'DBG' 405 | # define DEBUG(fmt, args...) DBG(fmt , ## args) | ^~~ ../../core/mem/../dprint.h:422:16: note: in expansion of macro 'DEBUG' 422 | #define LM_DBG DEBUG | ^~~~~ kz_amqp.c:805:9: note: in expansion of macro 'LM_DBG' 805 | LM_DBG("close channel: %d rmq(%p)->channel(%d)\n", getpid(), (void *)rmq, channel); | ^~~~~~ kz_amqp.c: In function 'kz_amqp_pipe_send': kz_amqp.c:1132:5: warning: this 'if' clause does not guard... [-Wmisleading-indentation] 1132 | if(s_local_routing_key) | ^~ kz_amqp.c:1135:9: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'if' 1135 | return ret; | ^~~~~~ kz_amqp.c: In function 'kz_amqp_subscribe_simple': kz_amqp.c:2051:5: warning: this 'if' clause does not guard... [-Wmisleading-indentation] 2051 | if(binding != NULL) | ^~ kz_amqp.c:2054:9: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'if' 2054 | return -1; | ^~~~~~ CC (gcc) [M kazoo.so] kz_fixup.o CC (gcc) [M kazoo.so] kz_hash.o CC (gcc) [M kazoo.so] kz_json.o CC (gcc) [M kazoo.so] kz_pua.o CC (gcc) [M kazoo.so] kz_trans.o ``` **4** ``` CC (gcc) [M ndb_redis.so] ndb_redis_mod.o CC (gcc) [M ndb_redis.so] redis_client.o redis_client.c: In function 'redisc_init': redis_client.c:43:17: warning: this 'if' clause does not guard... [-Wmisleading-indentation] 43 | if (__tmp) freeReplyObject(__tmp); __tmp ? 0 : -1;}) | ^~ redis_client.c:235:21: note: in expansion of macro 'redisCommandNR' 235 | if (redisCommandNR(rsrv->ctxRedis, "PING")) { | ^~~~~~~~~~~~~~ redis_client.c:43:52: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'if' 43 | if (__tmp) freeReplyObject(__tmp); __tmp ? 0 : -1;}) | ^~~~~ redis_client.c:235:21: note: in expansion of macro 'redisCommandNR' 235 | if (redisCommandNR(rsrv->ctxRedis, "PING")) { | ^~~~~~~~~~~~~~ redis_client.c:43:17: warning: this 'if' clause does not guard... [-Wmisleading-indentation] 43 | if (__tmp) freeReplyObject(__tmp); __tmp ? 0 : -1;}) | ^~ redis_client.c:240:51: note: in expansion of macro 'redisCommandNR' 240 | if ((redis_cluster_param == 0) && redisCommandNR(rsrv->ctxRedis, | ^~~~~~~~~~~~~~ redis_client.c:43:52: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'if' 43 | if (__tmp) freeReplyObject(__tmp); __tmp ? 0 : -1;}) | ^~~~~ redis_client.c:240:51: note: in expansion of macro 'redisCommandNR' 240 | if ((redis_cluster_param == 0) && redisCommandNR(rsrv->ctxRedis, | ^~~~~~~~~~~~~~ redis_client.c: In function 'redisc_reconnect_server': redis_client.c:43:17: warning: this 'if' clause does not guard... [-Wmisleading-indentation] 43 | if (__tmp) freeReplyObject(__tmp); __tmp ? 0 : -1;}) | ^~ redis_client.c:549:13: note: in expansion of macro 'redisCommandNR' 549 | if (redisCommandNR(rsrv->ctxRedis, "PING")) | ^~~~~~~~~~~~~~ redis_client.c:43:52: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'if' 43 | if (__tmp) freeReplyObject(__tmp); __tmp ? 0 : -1;}) | ^~~~~ redis_client.c:549:13: note: in expansion of macro 'redisCommandNR' 549 | if (redisCommandNR(rsrv->ctxRedis, "PING")) | ^~~~~~~~~~~~~~ redis_client.c:43:52: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'if' 43 | if (__tmp) freeReplyObject(__tmp); __tmp ? 0 : -1;}) | ^~~~~ redis_client.c:549:13: note: in expansion of macro 'redisCommandNR' 549 | if (redisCommandNR(rsrv->ctxRedis, "PING")) | ^~~~~~~~~~~~~~ redis_client.c:43:17: warning: this 'if' clause does not guard... [-Wmisleading-indentation] 43 | if (__tmp) freeReplyObject(__tmp); __tmp ? 0 : -1;}) | ^~ redis_client.c:551:43: note: in expansion of macro 'redisCommandNR' 551 | if ((redis_cluster_param == 0) && redisCommandNR(rsrv->ctxRedis, | ^~~~~~~~~~~~~~ redis_client.c:43:52: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'if' 43 | if (__tmp) freeReplyObject(__tmp); __tmp ? 0 : -1;}) | ^~~~~ redis_client.c:551:43: note: in expansion of macro 'redisCommandNR' 551 | if ((redis_cluster_param == 0) && redisCommandNR(rsrv->ctxRedis, | ^~~~~~~~~~~~~~ redis_client.c:43:17: warning: this 'if' clause does not guard... [-Wmisleading-indentation] 43 | if (__tmp) freeReplyObject(__tmp); __tmp ? 0 : -1;}) | ^~ redis_client.c:555:21: note: in expansion of macro 'redisCommandNR' 555 | if (redisCommandNR(rsrv->ctxRedis, "FLUSHALL")) | ^~~~~~~~~~~~~~ redis_client.c:43:52: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'if' 43 | if (__tmp) freeReplyObject(__tmp); __tmp ? 0 : -1;}) | ^~~~~ redis_client.c:555:21: note: in expansion of macro 'redisCommandNR' 555 | if (redisCommandNR(rsrv->ctxRedis, "FLUSHALL")) | ^~~~~~~~~~~~~~ LD (gcc) [M ndb_redis.so] ndb_redis.so CC (gcc) [M topos_redis.so] topos_redis_mod.o CC (gcc) [M topos_redis.so] topos_redis_storage.o ``` **5** ``` CC (gcc) [M xhttp_pi.so] xhttp_pi.o CC (gcc) [M xhttp_pi.so] xhttp_pi_fnc.o xhttp_pi_fnc.c: In function 'ph_run_pi_cmd': xhttp_pi_fnc.c:2904:25: warning: this 'if' clause does not guard... [-Wmisleading-indentation] 2904 | if(c_vals) pkg_free(c_vals); c_vals = NULL; | ^~ xhttp_pi_fnc.c:2904:54: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'if' 2904 | if(c_vals) pkg_free(c_vals); c_vals = NULL; | ^~~~~~ make[3]: 'libsrdb1.so.1.0' is up to date. LD (gcc) [M xhttp_pi.so] xhttp_pi.so CC (gcc) [M xmlrpc.so] http.o CC (gcc) [M xmlrpc.so] xmlrpc.o LD (gcc) [M xmlrpc.so] xmlrpc.so ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3012 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3012(a)github.com> [View Less]

2 2

[kamailio/kamailio] format-truncation warning (Issue #3013)
by sergey-safarov 08 Feb '22

08 Feb '22

**1** ``` CC (gcc) [M presence.so] notify.o CC (gcc) [M presence.so] presence.o presence.c: In function 'child_init': presence.c:570:62: warning: '%d' directive output may be truncated writing between 1 and 11 bytes into a region of size 3 [-Wformat-truncation=] 570 | snprintf(tmp, 21, "PRESENCE NOTIFIER %d", i); | ^~ presence.c:570:43: note: directive argument in the range [-2147483647, 2147483646] … [View More]

2 2

[kamailio/kamailio] smsops: extend rpdata params manipulation (PR #3007)
by alexyosifov 07 Feb '22

07 Feb '22

- Add capability to set RPData originator and destination addresses flags. Default values 0x91.   #### 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 - [ ] 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:  - [ ] PR should be backported to stable branches - [x] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description  You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/3007 -- Commit Summary -- * smsops: extend rpdata params manipulation -- File Changes -- M src/modules/smsops/smsops_impl.c (52) -- Patch Links -- https://github.com/kamailio/kamailio/pull/3007.patch https://github.com/kamailio/kamailio/pull/3007.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/3007 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/3007(a)github.com> [View Less]

3 4

[kamailio/kamailio] db_postgres: added support for async queries (PR #3010)
by Federico Cabiddu 07 Feb '22

07 Feb '22

#### 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 - [ ] 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:  - [ ] PR should be backported to stable branches - [X] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description  This PR add support for async queries to db_postgres module. Implementation is the same as the mysql and unixodbx modules. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/3010 -- Commit Summary -- * db_postgres: added support for async queries -- File Changes -- M src/modules/db_postgres/db_postgres.c (2) M src/modules/db_postgres/km_dbase.c (96) M src/modules/db_postgres/km_dbase.h (9) -- Patch Links -- https://github.com/kamailio/kamailio/pull/3010.patch https://github.com/kamailio/kamailio/pull/3010.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/3010 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/3010(a)github.com> [View Less]

2 2

Kamailio Glob style include / wildcard.
by Brandon Armstead 04 Feb '22

04 Feb '22

Would it be possible to get glob style includes in place, i.e. include_file "/some/path/*.cfg". Reviewing the source, it looks like sr_push_yy_state in src/core/cfg.lex needs an update. Daniel - can you confirm if this is the correct place to modify such behavior and if there are any gotchas in implementation of this? It would be nice if it had full support for glob inclusion / imports, similar to nginx i.e. include_file "/home/*/foo/bar/*.cfg" would include files in /home/brandon/foo/bar/… [View More]

2 1

← Newer
1
...
7
8
9
10
11
12
13
...
27
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev January 2022