sr-dev January 2017

sr-dev@lists.kamailio.org

33 participants
538 discussions

[kamailio/kamailio] Kamailio crashes when it receives a 404 reply to an INVITE originated after a 302. (#875)

by Joel Serrano

Hi, Kamailio crashes when we handle a 302 redirect and the reply is a 404. > # kamailio -v > version: kamailio 4.4.4 (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. > id: unknown > compiled with gcc 4.9.2 root@14cn5:/home/joel/files# This works: > softphone1 > kamailio1 > server1 > 302 > kamailio1 > server2 > 200 OK This crashes: > softphone1 > kamailio1 > server1 > 302 > kamailio1 > server2 > 404 Not Found I'm attaching debug logs, sip traces and the bt full from backtrace. IPs: > A.B.C.D = Kamailio IP > E.F.G.H = Softphone IP > I.J.K.L1 = dispatcher node1 > I.J.K.L2 = dispatcher node2 In the config we send INVITE requests to a dispatcher group (very simple config). Then, in failure_route we have: ``` if (t_check_status("302")) { xlog("L_NOTICE", "Redirecting to TestName: $T_rpl($ct) - M=$rm R=$ru ID=$ci\n"); get_redirects("*"); route(RELAY); } ``` And call get redirected to the address of the contact in the 302. If the new INVITE to that address gets a 200, all works, if that request gets a 404, Kamailio crashes. Please let me know if you need more info, this is 100% reproducible on our platform. Thank you! Joel. [backtrace.txt](https://github.com/kamailio/kamailio/files/623307/backtrace.… [debug.txt](https://github.com/kamailio/kamailio/files/623308/debug.txt) [sip.txt](https://github.com/kamailio/kamailio/files/623309/sip.txt) -- 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/875

7 years, 7 months

[kamailio/kamailio] Enabling DMQ cause high CPU usage (#822)

by Soapnix

Hi all! We trying to use two instances of kamailio on FreeBSD, kamailio was build from master branch. If I enables DMQ, 2 threads (pids) start utilize CPU, less than minute it's up to 100% (on a both servers). At that time kamailio successful handle calls, dmq and usrloc replication wokrs fine. While trying to understand what happens I got this debug info - something happens and K. cycles on shed_yeld() func. All additional info I put into attachments: [gdb_output.txt](https://github.com/kamailio/kamailio/files/528881/gdb_outpu… [kamailio.log.gz](https://github.com/kamailio/kamailio/files/528879/kamailio… [kamailio.txt](https://github.com/kamailio/kamailio/files/528883/kamailio.tx… [kdump.txt.gz](https://github.com/kamailio/kamailio/files/528880/kdump.txt.g… [ktrace.out.gz](https://github.com/kamailio/kamailio/files/528878/ktrace.out… [top_output.txt](https://github.com/kamailio/kamailio/files/528882/top_outpu… -- 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/822

7 years, 8 months

[kamailio/kamailio] rabbitmq doc (#903)

by Olle E. Johansson

http://kamailio.org/docs/modules/devel/modules/rabbitmq.html Please do provide a URL to the rabbitmq library project in addition to the name of the package name of a Linux distro. - Is the package name "librabbitmq-dev" the same for all major Linux distributions? - Have you checked this on OpenBSD or FreeBSD? We are multi-linux-distro and multi-platform :-) -- 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/903

7 years, 8 months

[kamailio/kamailio] Kamailio failed to autostart on reboot with MySQL database (#925)

by Fyodor

MYIP = my server ip MYDOMAIN = my domain name syslog: ``` Jan 13 04:18:19 kaf kamailio[1153]: loading modules under config path: /usr/lib/x86_64-linux-gnu/kamailio/modules/ Jan 13 04:18:19 kaf kamailio[1153]: Listening on Jan 13 04:18:19 kaf kamailio[1153]: udp: MYIP:5776 Jan 13 04:18:19 kaf kamailio[1153]: tcp: MYIP:5776 Jan 13 04:18:19 kaf kamailio[1153]: tls: MYIP:5777 Jan 13 04:18:19 kaf kamailio[1153]: Aliases: Jan 13 04:18:19 kaf kamailio[1153]: tls: MYDOMAIN:5777 Jan 13 04:18:19 kaf kamailio[1153]: tcp: MYDOMAIN:5776 Jan 13 04:18:19 kaf kamailio[1153]: udp: MYDOMAIN:5776 Jan 13 04:18:20 kaf systemd[1]: kamailio.service: Control process exited, code=exited status=255 Jan 13 04:18:20 kaf systemd[1]: Failed to start Kamailio (OpenSER) - the Open Source SIP Server. Jan 13 04:18:20 kaf systemd[1]: kamailio.service: Unit entered failed state. Jan 13 04:18:20 kaf systemd[1]: kamailio.service: Failed with result 'exit-code'. ``` `/etc/init.d/mysql-kamailio start` works fine (kamailio starts) `service kamailio start` - works fine mysql start fine kamailio.log: ``` Jan 13 04:18:19 kaf kamailio: INFO: tls [tls_init.c:403]: init_tls_compression(): tls: init_tls: disabling compression... Jan 13 04:18:19 kaf kamailio: INFO: <core> [sctp_core.c:74]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Jan 13 04:18:19 kaf kamailio: INFO: <core> [tcp_main.c:4656]: init_tcp(): using epoll_lt as the io watch method (auto detected) Jan 13 04:18:20 kaf /usr/sbin/kamailio[1276]: INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob Jan 13 04:18:20 kaf /usr/sbin/kamailio[1276]: INFO: rr [rr_mod.c:174]: mod_init(): outbound module not available Jan 13 04:18:20 kaf /usr/sbin/kamailio[1276]: INFO: usrloc [hslot.c:51]: ul_init_locks(): locks array size 1024 Jan 13 04:18:20 kaf /usr/sbin/kamailio[1276]: INFO: auth [auth_mod.c:333]: mod_init(): auth: qop set, but nonce-count (nc_enabled) support disabled Jan 13 04:18:20 kaf /usr/sbin/kamailio[1276]: INFO: tls [tls_mod.c:362]: mod_init(): With ECDH-Support! Jan 13 04:18:20 kaf /usr/sbin/kamailio[1276]: INFO: tls [tls_mod.c:365]: mod_init(): With Diffie Hellman Jan 13 04:18:20 kaf /usr/sbin/kamailio[1276]: INFO: tls [tls_init.c:591]: init_tls_h(): tls: _init_tls_h: compiled with openssl version "OpenSSL 1.0.2g 1 Mar 2016" (0x1000207f), kerberos support: off, compression: on Jan 13 04:18:20 kaf /usr/sbin/kamailio[1276]: INFO: tls [tls_init.c:599]: init_tls_h(): tls: init_tls_h: installed openssl library version "OpenSSL 1.0.2g 1 Mar 2016" (0x1000207f), kerberos support: off, zlib compression: off#012 compiler: cc -I. -I.. -I../include -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -m64 -DL_ENDIAN -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-Bsymbolic-functions -Wl,-z,relro -Wa,--noexecstack -Wall -DMD32_REG_T=int -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM Jan 13 04:18:20 kaf /usr/sbin/kamailio[1276]: WARNING: tls [tls_init.c:653]: init_tls_h(): tls: openssl bug #1491 (crash/mem leaks on low memory) workaround enabled (on low memory tls operations will fail preemptively) with free memory thresholds 7864320 and 3932160 bytes Jan 13 04:18:20 kaf /usr/sbin/kamailio[1276]: INFO: <core> [cfg/cfg_ctx.c:608]: cfg_set_now(): INFO: cfg_set_now(): tls.low_mem_threshold1 has been changed to 7864320 Jan 13 04:18:20 kaf /usr/sbin/kamailio[1276]: INFO: <core> [cfg/cfg_ctx.c:608]: cfg_set_now(): INFO: cfg_set_now(): tls.low_mem_threshold2 has been changed to 3932160 Jan 13 04:18:20 kaf /usr/sbin/kamailio[1276]: ERROR: db_mysql [km_my_con.c:124]: db_mysql_new_connection(): driver error: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) Jan 13 04:18:20 kaf /usr/sbin/kamailio[1276]: ERROR: <core> [db.c:318]: db_do_init2(): could not add connection to the pool Jan 13 04:18:20 kaf /usr/sbin/kamailio[1276]: ERROR: usrloc [dlist.c:637]: register_udomain(): failed to open database connection Jan 13 04:18:20 kaf /usr/sbin/kamailio[1276]: ERROR: registrar [reg_mod.c:561]: domain_fixup(): failed to register domain Jan 13 04:18:20 kaf /usr/sbin/kamailio[1276]: ERROR: <core> [route.c:1153]: fix_actions(): fixing failed (code=-1) at cfg:/etc/kamailio/kamailio.cfg:676 Jan 13 04:18:20 kaf /usr/sbin/kamailio[1276]: ERROR: <core> [route.c:1153]: fix_actions(): fixing failed (code=-1) at cfg:/etc/kamailio/kamailio.cfg:678 Jan 13 04:18:20 kaf /usr/sbin/kamailio[1276]: INFO: <core> [sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized ``` -- 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/925

7 years, 8 months

[kamailio/kamailio] [uac] REGISTER source port alternates between 5060 and != 5060 (#936)

by Peter Colberg

When registering to an upstream provider using the uac module, the source port of REGISTER messages alternates seemingly randomly between either 5060 or the lowest available port, e.g., 1024, 1025, 1026. All SIP providers that I tested send subsequent INVITEs of incoming calls to the originating ip/port of the prior REGISTER, which is problematic when kamilio is running behind a firewall. I tested both the latest master (7c03340b4b486afaf00b14a6589c13b7165240a0) and 4.4 (df5ef6183350d99f77087dd83950ef35466e84a1) on Debian unstable/amd64. #### /etc/kamailio/kamailio.cfg ``` #!KAMAILIO debug=3 loadmodule "kex.so" loadmodule "corex.so" loadmodule "tm.so" loadmodule "tmx.so" loadmodule "sl.so" loadmodule "rr.so" loadmodule "pv.so" loadmodule "db_text.so" loadmodule "dialog.so" loadmodule "uac.so" #!define DBURL "text:///etc/kamailio/dbtext" modparam("rr", "append_fromtag", 1) modparam("dialog", "dlg_flag", 4) modparam("dialog", "track_cseq_updates", 1) modparam("uac", "restore_dlg", 1) modparam("uac", "reg_db_url", DBURL) modparam("uac", "reg_timer_interval", 60) modparam("uac", "reg_retry_interval", 60) modparam("uac", "reg_contact_addr", "1.2.3.4:5060") request_route { exit; } ``` #### /etc/kamailio/dbtext/uacreg ``` l_uuid(string) l_username(string) l_domain(string) r_username(string) r_domain(string) realm(string) auth_username(string) auth_password(string) auth_proxy(string) expires(int) flags(int) reg_delay(int) 12345678:user:domain.local:11111111:sip.example.org:sip.example.org:11111111:XXXXXXXXXXXXXXXX:sip\:sip.example.org:600:0:0 ``` -- 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/936

7 years, 9 months

[kamailio/kamailio] kamailio crashes on CANCEL due to empty reply_lumps (#872)

by apogrebennyk

We have a crash in kamailio 4.4.4 after t_next_contacts() has been called from failure route, if at this very moment when kamailio is preparing new INVITE the caller sends a cancel. #0 build_res_buf_from_sip_req (code=3186024432, code@entry=487, text=0x25, new_tag=0x7f8dcf5fb2b0 <tm_tag>, msg=0x7f8dbde6cf78, returned_len=0xb7, bmark=0x4) at msg_translator.c:2395 #1 0x00007f8dcf35f7b2 in _reply (trans=0x7f8dbde70960, p_msg=0x7f8dbde6cf78, code=487, text=<optimized out>, lock=1) at t_reply.c:712 #2 0x00007f8dcf3b5e8b in e2e_cancel (cancel_msg=0x7f8dbde6dff0, cancel_msg@entry=0x7f8dd26bb750, t_cancel=0x25, t_invite=0x7f8dbde70960) at t_fwd.c:1278 So the scheme is the following: proxy > INVITE < 486 > INVITE* < CANCEL Victor has investigated this and found that the issue seems to be related to the reply lumps added by append_to_reply when processing initial invite. In order to reproduce this you need children>=2. When first target replies 486 the proxy calls t_next_contacts() and starts preparing invite to the next target and at this time another process receives cancel and destroys the transaction, the process handling that invite message(*) gets crashed. While we are investigating the possibility to move the append_to_reply calls to the branch route, would it be possible to avoid crash by some kind of lock mechanism? The thing is that it's not always possible to move append_to_reply to the branch route, e.g. our proxy is deployed behind stateless lb with multiple interfaces and proxy needs to tell lb which interface to use already in the 100 Trying reply it sends to lb as a first thing when receiving a message. -- 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/872

7 years, 9 months

[kamailio/kamailio] dialog: crash when trying to print error info (#807)

by Victor Seva

``` Reading symbols from kamailio...Reading symbols from /usr/lib/debug/.build-id/10/824757bd1066806f2e19310929e17a9009a991.debug...done. done. [New LWP 5578] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/sbin/kamailio -f /etc/kamailio/proxy/kamailio.cfg -P /var/run/kamailio/kam'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f4871c9adcc in vfprintf () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0 0x00007f4871c9adcc in vfprintf () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007f4871d34466 in __vsyslog_chk () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x00007f4871d345bf in syslog () from /lib/x86_64-linux-gnu/libc.so.6 #3 0x00007f485b71d796 in dlg_onroute (req=0x7f4866d8e5f0, route_params=0x7fffff82, param=0x7ffceb21fd60) at dlg_handlers.c:1336 #4 0x00007f48632aa2cd in run_rr_callbacks (req=0x7f4866d8e5f0, rr_param=0x7f48634bd8d0 <routed_params>) at rr_cb.c:96 #5 0x00007f486329e051 in after_loose (_m=0x7f4866d8e5f0, preloaded=2) at loose.c:914 #6 0x0000000000446700 in do_action (h=0x7ffceb220830, a=0x7f4865d1f1a0, msg=0x7f4866d8e5f0) at action.c:1060 #7 0x00000000004451c5 in run_actions (h=0x6, h@entry=0x7ffceb220830, a=0x7fffff82, msg=0x7ffceb21fd60) at action.c:1549 #8 0x0000000000451b97 in run_actions_safe (h=0x7ffceb221b00, a=<optimized out>, msg=<optimized out>) at action.c:1614 #9 0x0000000000426d20 in rval_get_int (h=0x7ffceb221b00, msg=0x6, i=0x7ffceb220b60, rv=0xffffffffffffffff, cache=0x6) at rvalue.c:912 #10 0x000000000042caac in rval_expr_eval_int (h=0x7ffceb221b00, msg=0x7f4866d8e5f0, res=0x7ffceb220b60, rve=0x7f4865d1f2d0) at rvalue.c:1910 #11 0x0000000000446bd7 in do_action (h=0x7ffceb221b00, a=0x7f4865d6c508, msg=0x7f4866d8e5f0) at action.c:1030 #12 0x00000000004451c5 in run_actions (h=0x6, a=0x7fffff82, msg=0x7ffceb21fd60) at action.c:1549 #13 0x0000000000446df0 in do_action (h=0x7ffceb221b00, a=0x7f4866624370, msg=0x7f4866d8e5f0) at action.c:678 #14 0x00000000004451c5 in run_actions (h=0x6, a=0x7fffff82, msg=0x7ffceb21fd60) at action.c:1549 #15 0x0000000000446c28 in do_action (h=0x7ffceb221b00, a=0x7f4866cbbe10, msg=0x7f4866d8e5f0) at action.c:1049 #16 0x00000000004451c5 in run_actions (h=0x6, h@entry=0x7ffceb221b00, a=0x7fffff82, a@entry=0x7f4866c6a758, msg=0x7ffceb21fd60, msg@entry=0x7f4866d8e5f0) at action.c:1549 #17 0x0000000000451c35 in run_top_route (a=0x7f4866c6a758, msg=0x7f4866d8e5f0, c=<optimized out>) at action.c:1635 #18 0x000000000055b4ae in receive_msg (buf=0x0, len=1725490672, rcv_info=0x7ffceb221de0) at receive.c:240 #19 0x000000000047abe0 in udp_rcv_loop () at udp_server.c:495 #20 0x000000000050360e in main_loop () at main.c:1600 #21 0x000000000041cdbc in main (argc=0, argv=0x0) at main.c:2616 (gdb) f 3 #3 0x00007f485b71d796 in dlg_onroute (req=0x7f4866d8e5f0, route_params=0x7fffff82, param=0x7ffceb21fd60) at dlg_handlers.c:1336 1336 dlg_handlers.c: No such file or directory. ``` relevant code: https://github.com/kamailio/kamailio/blob/4.4/modules/dialog/dlg_handlers.c… ``` /* run actions for the transition */ if (event==DLG_EVENT_REQBYE && new_state==DLG_STATE_DELETED && old_state!=DLG_STATE_DELETED) { LM_DBG("BYE successfully processed\n"); /* remove from timer */ ret = remove_dialog_timer(&dlg->tl); if (ret < 0) { LM_CRIT("unable to unlink the timer on dlg %p [%u:%u] " "with clid '%.*s' and tags '%.*s' '%.*s'\n", dlg, dlg->h_entry, dlg->h_id, dlg->callid.len, dlg->callid.s, dlg->tag[DLG_CALLER_LEG].len, dlg->tag[DLG_CALLER_LEG].s, dlg->tag[DLG_CALLEE_LEG].len, dlg->tag[DLG_CALLEE_LEG].s); } else if (ret > 0) { ``` ``` (gdb) p dlg $1 = (dlg_cell_t *) 0x7f47c4c7d560 (gdb) p *dlg $2 = {ref = -419086585, next = 0x7f47c4c7d598, prev = 0xa, h_id = 2, h_entry = 0, state = 3301430691, lifetime = 32583, init_ts = 3, start_ts = 0, end_ts = 1475139409, dflags = 32583, iflags = 1601467251, sflags = 1650552421, toroute = 2030069100, toroute_name = {s = 0x58 <error: Cannot access memory at address 0x58>, len = 0}, from_rr_nb = 0, tl = {next = 0x0, prev = 0x6eaf61, timeout = 7257938}, callid = {s = 0x6acfa0 "core", len = 94}, from_uri = {s = 0x7f47f0f0f0f0 "", len = -1005795570}, to_uri = { s = 0x7f47c4c7d628 "sst_refresh_method", len = 18}, req_uri = {s = 0x2 <error: Cannot access memory at address 0x2>, len = -993536453}, tag = {{ s = 0x6 <error: Cannot access memory at address 0x6>, len = -993536672}, {s = 0x726665725f747373 <error: Cannot access memory at address 0x726665725f747373>, len = 1600680805}}, cseq = {{s = 0x5449564e4900646f <error: Cannot access memory at address 0x5449564e4900646f>, len = 69}, { s = 0xc0 <error: Cannot access memory at address 0xc0>, len = 0}}, route_set = {{s = 0x0, len = 0}, {s = 0x6eaf61 "core: xavp.c", len = 7257938}}, contact = {{ s = 0x6acfa0 "core", len = 94}, {s = 0x7f47f0f0f0f0 "", len = 2060094989}}, bind_addr = {0x7f47c4c7d6c8, 0x12}, cbs = {first = 0x2, types = -993536293}, profile_links = 0x3, vars = 0x7f47c4c7d5f0} (gdb) p dlg->callid $3 = {s = 0x6acfa0 "core", len = 94} (gdb) p dlg->tag[0] $4 = {s = 0x6 <error: Cannot access memory at address 0x6>, len = -993536672} (gdb) p dlg->tag[1] $5 = {s = 0x726665725f747373 <error: Cannot access memory at address 0x726665725f747373>, len = 1600680805} ``` -- 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/807

7 years, 9 months

[kamailio/kamailio] db_mysql: Let the database convert the timestamp (#957)

by Holger Freyther

Instead of using the time2str routines that go through timezone conversion in kamailio, let MySQL do it. This helps with the sipcapture module in case the system time is CET but the database is operated in UTC. In these cases the micro_ts and date columns would be offseted by the timezone difference and look-ups fail to work. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/957 -- Commit Summary -- * db_mysql: Let the database convert the timestamp -- File Changes -- M src/modules/db_mysql/km_val.c (18) -- Patch Links -- https://github.com/kamailio/kamailio/pull/957.patch https://github.com/kamailio/kamailio/pull/957.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/957

7 years, 9 months

[kamailio] consistency on name of main c file for a module (#82)

by Victor Seva

main file should be modulename.c or modulename_mod.c --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/82

7 years, 9 months

[kamailio/kamailio] kamailio-basic-kemi.cfg: add WITH_DB_TEXT (#930)

by Stefan Mititelu

This is for the people out there (me included) who don't want to install mysql to play with kamailio: - comment out ``#!define WITH_DB_MYSQL`` (still used by default) - set the right ``DB_TEXT_DIR``, to match ``kamailio_path/misc/examples/kemi/db_text`` (absolute path is needed; I tried with relative path and it did not work) - add users/passwords by editing ``kamailio_path/misc/examples/kemi/db_text/subscriber`` file Hope it's helpful. Enjoy! You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/930 -- Commit Summary -- * kamailio-basic-kemi.cfg: add WITH_DB_TEXT -- File Changes -- A misc/examples/kemi/db_text/acc (1) A misc/examples/kemi/db_text/address (1) A misc/examples/kemi/db_text/bkp (1) A misc/examples/kemi/db_text/missed_calls (1) A misc/examples/kemi/db_text/subscriber (4) A misc/examples/kemi/db_text/trusted (1) A misc/examples/kemi/db_text/version (7) M misc/examples/kemi/kamailio-basic-kemi.cfg (63) -- Patch Links -- https://github.com/kamailio/kamailio/pull/930.patch https://github.com/kamailio/kamailio/pull/930.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/930

7 years, 9 months

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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev January 2017