sr-dev March 2017

sr-dev@lists.kamailio.org

31 participants
269 discussions

[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

6 years, 2 months

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; } }

6 years, 2 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

6 years, 7 months

[kamailio/kamailio] kamailio 4.4.x: Abort and coredump (#604)

by Rick

Kamailio had an abort happend and does a coredump. Sorry I doesn't have debug symbols on this machine. Kamailio: ``` root@voip-integration-cust1:~ # kamailio -V version: kamailio 4.4.0 (amd64/freebsd) d4f23c 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_PTHREAD_MUTEX, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, select, kqueue. id: d4f23c compiled on 16:52:24 Apr 30 2016 with clang 3.4 ``` Log: ``` May 4 17:55:27 <local0.crit> voip-integration-cust1 kamailio[1177]: CRITICAL: <core> [pass_fd.c:275]: receive_fd(): EOF on 12 May 4 17:55:27 <kern.info> voip-integration-cust1 kernel: pid 1147 (kamailio), uid 986: exited on signal 6 (core dumped) May 4 17:55:27 <kern.info> voip-integration-cust1 kernel: pid 1146 (kamailio), uid 986: exited on signal 6 (core dumped) May 4 17:55:27 <local0.alert> voip-integration-cust1 kamailio[1145]: ALERT: <core> [main.c:739]: handle_sigs(): child process 1147 exited by a signal 6 May 4 17:55:27 <local0.alert> voip-integration-cust1 kamailio[1145]: ALERT: <core> [main.c:742]: handle_sigs(): core was generated May 4 17:55:27 <kern.info> voip-integration-cust1 kernel: pid 1148 (kamailio), uid 986: exited on signal 6 (core dumped) ``` Backtrace: ``` #0 0x000000080110235a in thr_kill () from /lib/libc.so.7 #1 0x0000000801102346 in raise () from /lib/libc.so.7 #2 0x00000008011022c9 in abort () from /lib/libc.so.7 #3 0x0000000800e3195a in pthread_attr_getaffinity_np () from /lib/libthr.so.3 #4 0x0000000800e2d046 in pthread_mutex_destroy () from /lib/libthr.so.3 #5 0x0000000805b436b5 in rpc_reply () from /usr/local/lib/kamailio/modules/tm.so #6 0x0000000805b23f18 in tm_reply_mutex_lock () from /usr/local/lib/kamailio/modules/tm.so #7 0x0000000805b34ba2 in reply_received () from /usr/local/lib/kamailio/modules/tm.so #8 0x000000000057146b in forward_reply () #9 0x0000000000570cca in forward_reply () #10 0x00000000004682a4 in receive_msg () #11 0x0000000000645023 in udp_rcv_loop () #12 0x0000000000543cad in main_loop () #13 0x00000000005519a5 in main () ``` --- 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/604

6 years, 8 months

[kamailio/kamailio] Wishlist #234: URI transformation to pick up URI scheme (#592)

by Olle E. Johansson

I would like the URI transformations to be more generic so one can pick up the URI scheme, like HTTP: or TEL: Just an idea --- 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/592

6 years, 8 months

[kamailio] PID file permissions (#231)

by Arsen

ENV: Debian 8 So on most Linux systems the /var/run folder is a tmpfs and after which clears after each reboot As I try to start up kamailio after a reboot through kamctl I get the following error. "ERROR: PID file /var/run/kamailio.pid does not exist -- Kamailio start failed" Because kamailio does not have the permission to write to the /var/run folder as the kamailio user. Would it be possible to add in the "kamctl" code a section where the SPECIFIED PID LOCATION (/var/run/kamailio) is checked and if it does not exist create it as the root user and chown it to the SPECIFIED USER (kamailio)? The way I have patched it for now is to create a init script that creates a /var/run/kamailio folder and chmods it to kamailio:kamailio Thanks everyone! --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/231

6 years, 9 months

[kamailio/kamailio] Kamailio Crashes 11 times: Malloc (#1026)

by igorPot

### Description Hi, I got a problem with Kamailio, it crashed 11 times in a row, with no visible reason, only thing I notice is MALLOC always on all the core-dumps.  ### Troubleshooting #### Reproduction It was aleatory 11 crashes in a row  #### Debugging Data  ``` Program terminated with signal 11, Segmentation fault. #0 0x0000000000622796 in qm_status (qm=0x7fcbe89b4000) at mem/q_malloc.c:788 788 f!=&(qm->free_hash[h].head); f=f->u.nxt_free, i++, j++){ Missing separate debuginfos, use: debuginfo-install bzip2-libs-1.0.5-7.el6_0.x86_64 db4-4.7.25-18.el6_4.x86_64 elfutils-libelf-0.152-1.el6.x86_64 glibc-2.12-1.132.el6.x86_64 keyutils-libs-1.4-4.el6.x86_64 krb5-libs-1.10.3-10.el6_4.6.x86_64 libacl-2.2.49-6.el6.x86_64 libattr-2.4.44-7.el6.x86_64 libcap-2.16-5.5.el6.x86_64 libcom_err-1.41.12-18.el6.x86_64 libgcc-4.4.7-11.el6.x86_64 libselinux-2.0.94-5.3.el6_4.1.x86_64 lm_sensors-libs-3.1.1-17.el6.x86_64 lua-5.1.4-4.1.el6.x86_64 mysql-libs-5.1.73-3.el6_5.x86_64 net-snmp-libs-5.5-50.el6_6.1.x86_64 nspr-4.10.0-1.el6.x86_64 nss-3.15.1-15.el6.x86_64 nss-softokn-freebl-3.14.3-9.el6.x86_64 nss-util-3.15.1-3.el6.x86_64 openssl-1.0.1e-30.el6_6.4.x86_64 pcre-7.8-6.el6.x86_64 perl-libs-5.10.1-136.el6.x86_64 popt-1.13-7.el6.x86_64 rpm-libs-4.8.0-37.el6.x86_64 tcp_wrappers-libs-7.6-57.el6.x86_64 xz-libs-4.999.9-0.3.beta.20091007git.el6.x86_64 zlib-1.2.3-29.el6.x86_64 (gdb) bt full #0 0x0000000000622796 in qm_status (qm=0x7fcbe89b4000) at mem/q_malloc.c:788 f = 0x69746163696c7070 i = 304 j = 3 h = 10 unused = 0 memlog = 5 mem_summary = 3 __FUNCTION__ = "qm_status" #1 0x000000000061a758 in qm_debug_frag (qm=0x7fcbe89b4000, f=0x7fcbf83fa268) at mem/q_malloc.c:150 __FUNCTION__ = "qm_debug_frag" #2 0x000000000061cd90 in qm_free (qm=0x7fcbe89b4000, p=0x7fcbf83fa298, file=0x7fcc0f8d336d "tm: h_table.c", func=0x7fcc0f8d3648 "free_cell", line=186) at mem/q_malloc.c:468 f = 0x7fcbf83fa268 size = 40 next = 0x400 prev = 0x7ffffdc3b7a0 __FUNCTION__ = "qm_free" #3 0x00007fcc0f814c9d in free_cell (dead_cell=0x7fcbf83ea0e8) at h_table.c:186 b = 0x7fcbf83fa298 "INVITE sip:0034126498563@proxy SIP/2.0\r\nRecord-Route: <sip:192.168.1.5;lr;did=d4d.7fa>\r\nCSeq: 1 INVITE\r\nCall-ID: SD7jt2a01-b81723f229af11e61f26a15065\r\nFrom: <sip:012854697@192.168.1."... i = 0 rpl = 0x0 tt = 0x7fcbe8ad0f18 foo = 0x7ffffdc3b870 cbs = 0x0 cbs_tmp = 0x7fcbf83f2308 __FUNCTION__ = "free_cell" #4 0x00007fcc0f859a1c in wait_handler (ti=269273136, wait_tl=0x7fcbf83ea168, data=0x7fcbf83ea0e8) at timer.c:675 p_cell = 0x7fcbf83ea0e8 ret = 1 #5 0x00000000005fd647 in timer_list_expire (t=269273136, h=0x7fcbe8a2d908, slow_l=0x7fcbe8a2fb38, slow_mark=15874) at timer.c:888 tl = 0x7fcbf83ea168 ret = 269273136 #6 0x00000000005fda8f in timer_handler () at timer.c:953 saved_ticks = 269273136 run_slow_timer = 0 i = 514 __FUNCTION__ = "timer_handler" #7 0x00000000005fdefd in timer_main () at timer.c:992 No locals. #8 0x00000000004a77e1 in main_loop () at main.c:1700 i = 8 pid = 0 si = 0x0 si_desc = "udp receiver child=7 sock=192.168.1.5:5060\000\177\000\000\200\272\303\375\377\177\000\000\023{N\000\000\000\000\000к\303\375\377\177\000\000\004\000\000\000\000\000\000\000`TA\000\000\000\000\000(\225\236\350\313\177", '\000' <repeats 14 times>, "\001\000\000\000к\303\375\377\177\000\000\266{N\000\000\000\000" nrprocs = 8 __FUNCTION__ = "main_loop" #9 0x00000000004acfa6 in main (argc=7, argv=0x7ffffdc3bd48) at main.c:2581 cfg_stream = 0x13b8010 c = -1 r = 0 tmp = 0x7ffffdc3cf70 "" tmp_len = 32767 port = -37503970 proto = 0 options = 0x703718 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:" ret = -1 seed = 2884067974 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0x40d134 p = 0xc2 <Address 0xc2 out of bounds> __FUNCTION__ = "main" (gdb) info locals f = 0x69746163696c7070 i = 304 j = 3 h = 10 unused = 0 memlog = 5 mem_summary = 3 __FUNCTION__ = "qm_status" (gdb) list 783 LOG_(DEFAULT_FACILITY, memlog, "qm_status: ", 784 "dumping free list stats :\n"); 785 for(h=0,i=0;h<QM_HASH_SIZE;h++){ 786 unused=0; 787 for (f=qm->free_hash[h].head.u.nxt_free,j=0; 788 f!=&(qm->free_hash[h].head); f=f->u.nxt_free, i++, j++){ 789 if (!FRAG_WAS_USED(f)){ 790 unused++; 791 #ifdef DBG_QM_MALLOC 792 LOG_(DEFAULT_FACILITY, memlog, "qm_status: ", (gdb) quit ``` #### Log Messages  ``` Mar 9 10:33:49 kamserv /usr/local/sbin/kamailio[2945]: : <core> [mem/q_malloc.c:140]: qm_debug_frag(): BUG: qm_*: fragm. 0x7f064ea52480 (address 0x7f064ea524b0) beginning overwritten(646e756f622d6575)! Mar 9 10:33:52 kamserv abrtd: Directory 'ccpp-2017-03-09-10:33:49-2945' creation detected Mar 9 10:33:52 kamserv abrt[3793]: Saved core dump of pid 2945 (/usr/local/sbin/kamailio) to /var/spool/abrt/ccpp-2017-03-09-10:33:49-2945 (608370688 bytes) Mar 9 10:33:52 kamserv abrtd: Executable '/usr/local/sbin/kamailio' doesn't belong to any package and ProcessUnpackaged is set to 'no' Mar 9 10:33:52 kamserv /usr/local/sbin/kamailio[2908]: ALERT: <core> [main.c:784]: handle_sigs(): child process 2945 exited by a signal 6 Mar 9 10:33:52 kamserv /usr/local/sbin/kamailio[2908]: ALERT: <core> [main.c:787]: handle_sigs(): core was generated Mar 9 10:33:52 kamserv /usr/local/sbin/kamailio[2908]: INFO: <core> [main.c:799]: handle_sigs(): terminating due to SIGCHLD Mar 9 10:33:52 kamserv /usr/local/sbin/kamailio[2953]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Mar 9 10:33:52 kamserv /usr/local/sbin/kamailio[2955]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Mar 9 10:33:52 kamserv /usr/local/sbin/kamailio[2947]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Mar 9 10:33:52 kamserv /usr/local/sbin/kamailio[2941]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Mar 9 10:33:52 kamserv /usr/local/sbin/kamailio[2939]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Mar 9 10:33:52 kamserv /usr/local/sbin/kamailio[2935]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Mar 9 10:33:52 kamserv /usr/local/sbin/kamailio[2927]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Mar 9 10:33:52 kamserv /usr/local/sbin/kamailio[2943]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Mar 9 10:33:52 kamserv /usr/local/sbin/kamailio[2929]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Mar 9 10:33:52 kamserv /usr/local/sbin/kamailio[2937]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Mar 9 10:33:52 kamserv /usr/local/sbin/kamailio[2949]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Mar 9 10:33:52 kamserv /usr/local/sbin/kamailio[2931]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Mar 9 10:33:52 kamserv /usr/local/sbin/kamailio[2933]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Mar 9 10:33:52 kamserv abrtd: 'post-create' on '/var/spool/abrt/ccpp-2017-03-09-10:33:49-2945' exited with 1 Mar 9 10:33:52 kamserv abrtd: Deleting problem directory '/var/spool/abrt/ccpp-2017-03-09-10:33:49-2945' ``` #### SIP Traffic  ``` (paste your sip traffic here) ``` ### Possible Solutions  ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 4.2.8 (x86_64/linux) 4507b8 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, DBG_QM_MALLOC, 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 64MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 4507b8 compiled on 16:19:58 Oct 26 2016 with gcc 4.4.7 ``` * **Operating System**:  ``` Linux kamserv 2.6.32-431.el6.x86_64 #1 SMP Sun Nov 10 22:19:54 EST 2013 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/1026

7 years

[kamailio/kamailio] "shm_mem_size" does not work if it was set in config file (#950)

by Maxim Malygin

### Description Config file has parameter "shm_mem_size" (or "shm" or "shm_mem") which allows to set shared memory size (in Mb) via configuration file. This parameter worked well in 3.1.5. Now it does not work (4.4.2). Shared memory size is always 64Mb (default value). The only way to set another size is to use "-m" command line option. #### Reproduction - Set shm_mem_size=512 in configuration file - Start kamailio and check size of shared memory using "kamcmd core.shmmem" - Expected result: total size of shared memory should be 512 Mb (in bytes) - Actual result: 64Mb ### Possible Solutions A workaround is to use "-m" command line option to send shared memeory size. ### Additional Information version: kamailio 4.4.3 (x86_64/linux) 5a2195 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: 5a2195 compiled on 13:41:22 Sep 27 2016 with gcc 4.4.7 OS: CentOS 6.8 (kernel 2.6.32-642.4.2.el6.x86_64) -- 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/950

7 years

Planning Kamailio v5.0.1

by Daniel-Constantin Mierla

Hello, I am considering to release Kamailio v5.0.1 sometime next week, likely on Wednesday, April 5, 2017. Should anyone be aware of issues not listed yet on bug tracker, report them there as soon as possible to try to fix. Soon after, we should release a new version from branch 4.4 and the last one from branch 4.3. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - May 22-24 (USA) - www.asipto.com Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com

7 years

[kamailio/kamailio] Keepalive module - prototype (#1045)

by Guillaume Bour

Hi all, Here is a prototype of Keepalive module I discussed on the mailing-list. It can work standalone: - destinations are set statically as module parameters - *is_alive()* function allows to check destination state It can also be used alongside with drouting module (currently only with sort_order 0) - all destinations defined in drouting module are automatically monitored when drouting *enable_keepalive* option is set to 1 - unavailable destinations are ignored when calling do_routing() function All comments are welcome Thanks, Guillaume You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/1045 -- Commit Summary -- * keepalive: module skeleton * keepalive: modularization, allow to specify more than one destination * keepalive: event routes * keepalive: module modularization * keepalive: adapt to trunk/5.0 branch * keepalive: attached informations related to destinations * keepalive: basic rpc interface * keepalive: remove ka_destination_list from api (not exported) * drouting: register destinations in keepalive module * keepalive: triggers events routes on state change only * drouting: refactoring * keepalive: support callback function on destination registration * drouting: register destination with callback * drouting: on do_routing() function, discard unavailable destinations * keepalive: checking uri format when adding destination * keepalive: *ping_interval* parameter to setup delay between destinations keepalives (default 30secs) * keepalive: ping considered successful if received 2XX response * keepalive: added is_alive(dest) function to check monitored destination status -- File Changes -- M src/modules/drouting/dr_load.c (3) M src/modules/drouting/drouting.c (58) M src/modules/drouting/prefix_tree.h (4) M src/modules/drouting/routing.c (2) A src/modules/keepalive/Makefile (18) A src/modules/keepalive/api.h (74) A src/modules/keepalive/keepalive.h (86) A src/modules/keepalive/keepalive_api.c (138) A src/modules/keepalive/keepalive_core.c (203) A src/modules/keepalive/keepalive_mod.c (193) A src/modules/keepalive/keepalive_rpc.c (101) -- Patch Links -- https://github.com/kamailio/kamailio/pull/1045.patch https://github.com/kamailio/kamailio/pull/1045.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/1045

7 years

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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev March 2017