sr-users January 2018

sr-users@lists.kamailio.org

83 participants
122 discussions

Re: [SR-Users] app_lua sr.sqlops.query exit status

by Daniel-Constantin Mierla

I have master (which should be more or less like latest 5.1) running with app_lua, but on debian 9.0. From backtrace, no obvious issue. Wondering if you can get a stripped down version of you config with as less loaded modules as possible and minimal routing blocks that expose the issue, so I can try it here. Try to load only the app_lua and the modules it binds to and see if crashes ... if not, it could be a side effect from other place. Cheers, Daniel On 10.01.18 12:44, jenus(a)cyberchaos.nl wrote: > Daniel, > > (gdb) frame 5 > #5 0x00007fd3b2684870 in lua_sr_kemi_register_libs (L=0xeffdb0) at > app_lua_sr.c:1973 > 1973 app_lua_sr.c: No such file or directory. > (gdb) list > 1968 in app_lua_sr.c > (gdb) info locals > _sr_crt_KSRMethods = 0xf0cf80 > emods = 0xa59a00 <_sr_kemi_modules> > emods_size = 37 > i = 3 > k = 35 > n = 346 > mname = > "KSR.uac_redirect\000\000\000\000\000\000\000\000\256\240B\262\323\177\000\000й\360\000\000\000\000\000\004\000\000\000\323\177\000\000 > ˏ\262\323\177\000\000\000\362\066\000\234\324\302Ͱ\375\357", '\000' > <repeats 21 times>, > "\065\246C\262\323\177\000\000@\265\225\356\376\177\000\000\000\000\000\000\377\377\377\377\000\000\000\000\000\000\000\000\177\241m\262\323\177\000" > __FUNCTION__ = "lua_sr_kemi_register_libs" > > (gdb) frame 6 > #6 0x00007fd3b26cf107 in lua_sr_openlibs (L=0xeffdb0) at > app_lua_api.c:185 > 185 app_lua_api.c: No such file or directory. > (gdb) list > 180 in app_lua_api.c > (gdb) info locals > No locals. > > > Jan > > > Daniel-Constantin Mierla schreef op 2018-01-10 12:40: >> Now the backtrace is different, gram the output for info locals in frame >> 5 and 6. >> >> Cheers, >> Daniel >> >> >> On 10.01.18 11:26, jenus(a)cyberchaos.nl wrote: >>> I have overwritten the core file b y accident. I did a new backtrace: >>> >>> (gdb) backtrace >>> #0 0x00007fd3b24365a0 in ?? () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #1 0x00007fd3b2437b62 in ?? () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #2 0x00007fd3b242a040 in lua_settable () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #3 0x00007fd3b243a412 in luaL_findtable () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #4 0x00007fd3b243a581 in luaL_openlib () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #5 0x00007fd3b2684870 in lua_sr_kemi_register_libs (L=0xeffdb0) at >>> app_lua_sr.c:1973 >>> #6 0x00007fd3b26cf107 in lua_sr_openlibs (L=0xeffdb0) at >>> app_lua_api.c:185 >>> #7 0x00007fd3b26cf7c1 in lua_sr_init_probe () at app_lua_api.c:225 >>> #8 0x00007fd3b265b97d in child_init (rank=-127) at app_lua_mod.c:197 >>> #9 0x0000000000549944 in init_mod_child (m=0x7fd3bc82cc70, rank=-127) >>> at core/sr_module.c:938 >>> #10 0x0000000000549c72 in init_child (rank=-127) at >>> core/sr_module.c:964 >>> #11 0x0000000000422c1c in main_loop () at main.c:1576 >>> #12 0x000000000042aab9 in main (argc=3, argv=0x7ffeee95b548) at >>> main.c:2646 >>> >>> (gdb) frame 7 >>> #7 0x00007fd3b26cf7c1 in lua_sr_init_probe () at app_lua_api.c:225 >>> 225 app_lua_api.c: No such file or directory. >>> (gdb) list >>> 220 in app_lua_api.c >>> (gdb) info locals >>> L = 0xeffdb0 >>> txt = 0x7fd3bd00dce7 <__fprintf+135> "H\201\304", <incomplete sequence >>> \330> >>> li = 0x0 >>> sbuf = {st_dev = 0, st_ino = 206158430256, st_nlink = 140732901208248, >>> st_mode = 4002787296, st_uid = 32766, st_gid = 4002787464, __pad0 = >>> 14, st_rdev = 140728898420739, st_size = 0, >>> st_blksize = 30795, st_blocks = 7970120, st_atim = {tv_sec = >>> 7929944, tv_nsec = 0}, st_mtim = {tv_sec = 0, tv_nsec = >>> 140732901208128}, st_ctim = {tv_sec = 140547210663782, >>> tv_nsec = 7938688}, __glibc_reserved = {-541165879423, >>> 140732901208240, 5544260}} >>> __FUNCTION__ = "lua_sr_init_probe" >>> >>> I assume that in this case i need to do a "frame 7". >>> >>> >>> Jan >>> >>> Daniel-Constantin Mierla schreef op 2018-01-10 11:18: >>>> Few more things to grab from core file with gdb -- take the output for >>>> the next commands: >>>> >>>> frame 16 >>>> >>>> list >>>> >>>> info locals >>>> >>>> Cheers, >>>> Daniel >>>> >>>> >>>> On 10.01.18 11:08, jenus(a)cyberchaos.nl wrote: >>>>> Daniel, >>>>> >>>>> Here are the app_lua settings: >>>>> >>>>> # ----- app_lua params ----- >>>>> modparam("app_lua", "load", "/etc/kamailio/kamailio_functions.lua") >>>>> modparam("app_lua", "register", "sqlops") >>>>> modparam("app_lua", "register", "siputils") >>>>> modparam("app_lua", "register", "xhttp") >>>>> >>>>> >>>>> Jan >>>>> >>>>> >>>>> Daniel-Constantin Mierla schreef op 2018-01-10 11:03: >>>>>> Can you give here the parameters you set for app_lua module? >>>>>> >>>>>> Cheers, >>>>>> Daniel >>>>>> >>>>>> >>>>>> On 09.01.18 22:27, jenus(a)cyberchaos.nl wrote: >>>>>>> Daniel, >>>>>>> >>>>>>> Here is the backtrace. >>>>>>> >>>>>>> (gdb) backtrace >>>>>>> #0 0x00007fe41140e067 in __GI_raise (sig=sig@entry=6) at >>>>>>> ../nptl/sysdeps/unix/sysv/linux/raise.c:56 >>>>>>> #1 0x00007fe41140f448 in __GI_abort () at abort.c:89 >>>>>>> #2 0x00007fe41144c1b4 in __libc_message >>>>>>> (do_abort=do_abort@entry=1, >>>>>>> fmt=fmt@entry=0x7fe411541210 "*** Error in `%s': %s: 0x%s >>>>>>> ***\n") at >>>>>>> ../sysdeps/posix/libc_fatal.c:175 >>>>>>> #3 0x00007fe41145198e in malloc_printerr (action=1, >>>>>>> str=0x7fe41153d42a "realloc(): invalid next size", ptr=<optimized >>>>>>> out>) at malloc.c:4996 >>>>>>> #4 0x00007fe41145476b in _int_realloc (av=av@entry=0x7fe41177e620 >>>>>>> <main_arena>, oldp=oldp@entry=0x21789c0, oldsize=oldsize@entry=736, >>>>>>> nb=nb@entry=1552) at malloc.c:4234 >>>>>>> #5 0x00007fe411455769 in __GI___libc_realloc (oldmem=0x21789d0, >>>>>>> bytes=1536) at malloc.c:3029 >>>>>>> #6 0x00007fe40c460cae in ?? () from >>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>> #7 0x00007fe40c45c9aa in ?? () from >>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>> #8 0x00007fe40c46166d in ?? () from >>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>> #9 0x00007fe40c4640b3 in ?? () from >>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>> #10 0x00007fe40c45ccd1 in ?? () from >>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>> #11 0x00007fe40c45c92e in ?? () from >>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>> #12 0x00007fe40c45d7bb in ?? () from >>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>> #13 0x00007fe40c45d8c2 in ?? () from >>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>> #14 0x00007fe40c459528 in lua_load () from >>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>> #15 0x00007fe40c469d8c in luaL_loadbuffer () from >>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>> #16 0x00007fe40c6fe7d7 in lua_sr_init_probe () at app_lua_api.c:228 >>>>>>> #17 0x00007fe40c68a97d in child_init (rank=-127) at >>>>>>> app_lua_mod.c:197 >>>>>>> #18 0x0000000000549944 in init_mod_child (m=0x7fe410c3b998, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:938 >>>>>>> #19 0x0000000000549662 in init_mod_child (m=0x7fe410c3bec0, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #20 0x0000000000549662 in init_mod_child (m=0x7fe410c3c708, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #21 0x0000000000549662 in init_mod_child (m=0x7fe410c3cd78, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #22 0x0000000000549662 in init_mod_child (m=0x7fe410c3d360, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #23 0x0000000000549662 in init_mod_child (m=0x7fe410c3e1e8, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #24 0x0000000000549662 in init_mod_child (m=0x7fe410c3e938, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #25 0x0000000000549662 in init_mod_child (m=0x7fe410c3f4c8, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #26 0x0000000000549662 in init_mod_child (m=0x7fe410c3fca0, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #27 0x0000000000549662 in init_mod_child (m=0x7fe410c40118, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #28 0x0000000000549662 in init_mod_child (m=0x7fe410c40780, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #29 0x0000000000549662 in init_mod_child (m=0x7fe410c422f8, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #30 0x0000000000549662 in init_mod_child (m=0x7fe410c42968, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #31 0x0000000000549662 in init_mod_child (m=0x7fe410c42e50, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #32 0x0000000000549662 in init_mod_child (m=0x7fe410c43b48, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #33 0x0000000000549662 in init_mod_child (m=0x7fe410c43f20, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #34 0x0000000000549662 in init_mod_child (m=0x7fe410c446e0, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #35 0x0000000000549662 in init_mod_child (m=0x7fe410c44bd0, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #36 0x0000000000549662 in init_mod_child (m=0x7fe410c44ec8, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #37 0x0000000000549662 in init_mod_child (m=0x7fe410c45378, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #38 0x0000000000549662 in init_mod_child (m=0x7fe410c458f0, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #39 0x0000000000549662 in init_mod_child (m=0x7fe410c45e48, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #40 0x0000000000549662 in init_mod_child (m=0x7fe410c464e8, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #41 0x0000000000549662 in init_mod_child (m=0x7fe410c47278, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #42 0x0000000000549662 in init_mod_child (m=0x7fe410c476f0, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #43 0x0000000000549662 in init_mod_child (m=0x7fe410c47b68, >>>>>>> rank=-127) >>>>>>> at core/sr_module.c:935 >>>>>>> #44 0x0000000000549c72 in init_child (rank=-127) at >>>>>>> core/sr_module.c:964 >>>>>>> #45 0x0000000000422c1c in main_loop () at main.c:1576 >>>>>>> #46 0x000000000042aab9 in main (argc=3, argv=0x7ffe17f0e788) at >>>>>>> main.c:2646 >>>>>>> >>>>>>> >>>>>>> Jan >>>>>>> >>>>>>> Daniel-Constantin Mierla schreef op 2018-01-09 22:21: >>>>>>>> Can you install the debug symbols for kamailio as well? There >>>>>>>> should be >>>>>>>> a kamailio-dbg package or so ... >>>>>>>> >>>>>>>> Then take again the backtrace, it should provide more >>>>>>>> information -- >>>>>>>> file and line for each frame, ... >>>>>>>> >>>>>>>> Cheers, >>>>>>>> Daniel >>>>>>>> >>>>>>>> >>>>>>>> On 09.01.18 21:21, jenus(a)cyberchaos.nl wrote: >>>>>>>>> Daniel, >>>>>>>>> >>>>>>>>> Just upgraded to 5.1 but kamailio now generates a core file. I'm >>>>>>>>> running debian 8.10. It seems to crash on liblua5.1.so.0 : >>>>>>>>> >>>>>>>>> Using host libthread_db library >>>>>>>>> "/lib/x86_64-linux-gnu/libthread_db.so.1". >>>>>>>>> Core was generated by `kamailio -m 1500'. >>>>>>>>> Program terminated with signal SIGSEGV, Segmentation fault. >>>>>>>>> #0 0x00007f30c17f25a0 in ?? () from >>>>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>>>> (gdb) backtrace >>>>>>>>> #0 0x00007f30c17f25a0 in ?? () from >>>>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>>>> #1 0x00007f30c17f3b62 in ?? () from >>>>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>>>> #2 0x00007f30c17e6040 in lua_settable () from >>>>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>>>> #3 0x00007f30c17f6412 in luaL_findtable () from >>>>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>>>> #4 0x00007f30c17f6581 in luaL_openlib () from >>>>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>>>> #5 0x00007f30c1a40870 in lua_sr_kemi_register_libs () from >>>>>>>>> /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so >>>>>>>>> #6 0x00007f30c1a8b107 in lua_sr_openlibs () from >>>>>>>>> /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so >>>>>>>>> #7 0x00007f30c1a8b7c1 in lua_sr_init_probe () from >>>>>>>>> /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so >>>>>>>>> #8 0x00007f30c1a1797d in ?? () from >>>>>>>>> /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so >>>>>>>>> #9 0x0000000000549944 in ?? () >>>>>>>>> #10 0x0000000000549c72 in init_child () >>>>>>>>> #11 0x0000000000421498 in main_loop () >>>>>>>>> #12 0x000000000042aab9 in main () >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> >>>>>>>>> Jan >>>>>>>>> >>>>>>>>> jenus(a)cyberchaos.nl schreef op 2018-01-09 20:53: >>>>>>>>>> Daniel, >>>>>>>>>> >>>>>>>>>> Currently running kamailio 5.0.5. >>>>>>>>>> >>>>>>>>>> Jan >>>>>>>>>> >>>>>>>>>> Daniel-Constantin Mierla schreef op 2018-01-09 13:27: >>>>>>>>>>> Hello, >>>>>>>>>>> >>>>>>>>>>> what version of kamailio are you using? >>>>>>>>>>> >>>>>>>>>>> Cheers, >>>>>>>>>>> Daniel >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On 07.01.18 22:14, jenus(a)cyberchaos.nl wrote: >>>>>>>>>>>> Hello, >>>>>>>>>>>> >>>>>>>>>>>> I'm doing some tests with a lua script and app_lua. I'm using >>>>>>>>>>>> sr.sqlops.query to insert records into the database but would >>>>>>>>>>>> like to >>>>>>>>>>>> test the exit status of the sql query. In kamailio i can do: >>>>>>>>>>>> >>>>>>>>>>>> if(!sql_query("kamailio", "INSERT INTO subscriber ...")) >>>>>>>>>>>> >>>>>>>>>>>> Is there some kind of exit status for the lua function >>>>>>>>>>>> sr.sqlops.query >>>>>>>>>>>> in order to do the same check in lua? In other words, is it >>>>>>>>>>>> possible >>>>>>>>>>>> to check if a sql query was successful in lua? The result >>>>>>>>>>>> seems >>>>>>>>>>>> to be >>>>>>>>>>>> nill in all cases for a INSERT in lua using sr.sqlops.query. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Thanks, >>>>>>>>>>>> >>>>>>>>>>>> Jan Hazenberg >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Kamailio (SER) - Users Mailing List >>>>>>>>>>>> sr-users(a)lists.kamailio.org >>>>>>>>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Kamailio (SER) - Users Mailing List >>>>>>>>>> sr-users(a)lists.kamailio.org >>>>>>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>>>>>>>> >>>>>>> >>>>> >>> > -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

6 years, 10 months

Siremis Subscriber List

by Alexandre Cardoso

Hi Guys, I’m a new guy working with Kamailio and sirens, could you help on a issue that I’ve found? I just installed Kamailio and Siremis and went to the Siremis GUI. I want to add subscriber to subscriber list and I’m facing the following error: [2018-01-11 11:22:18 (GMT)] An exception occurred while executing this script: Error message: #0, Error in query:: SELECT T0.id, T0.username, T0.domain, T0.contact, T0.received, T0.path, T0.expires, T0.q, T0.callid, T0.cseq, T0.last_modified, T0.flags, T0.cflags, T0.user_agent, T0.socket, T0.methods, T0.ruid, T0.instance, T0.reg_id, T0.server_id, T0.connection_id, T0.keepalive, T0.partition FROM `location` T0 LIMIT 10. SQLSTATE[42S22]: Column not found: 1054 Unknown column 'T0.server_id' in 'field list' Script name and line number of error: : function: _run_search ( Array(2) ) @ /var/www/html/openbiz/bin/data/BizDataObj_Lite.php 243 function: fetch ( ) @ /var/www/html/openbiz/bin/easy/EasyForm.php 690 function: fetchDataSet ( ) @ /var/www/html/openbiz/bin/easy/FormRenderer.php 69 function: renderSmarty ( Object(EasyForm), "/var/www/html/siremis/modules/ser/template/grid.tpl" ) @ /var/www/html/openbiz/bin/easy/FormRenderer.php 45 function: render ( Object(EasyForm) ) @ /var/www/html/openbiz/bin/easy/EasyForm.php 1648 function: renderHTML ( ) @ /var/www/html/openbiz/bin/easy/EasyForm.php 1538 function: render ( ) @ /var/www/html/openbiz/bin/easy/ViewRenderer.php 83 function: renderSmarty ( Object(EasyView), "/var/www/html/siremis/modules/ser/template/view_tabs.tpl" ) @ /var/www/html/openbiz/bin/easy/ViewRenderer.php 40 function: render ( Object(EasyView) ) @ /var/www/html/openbiz/bin/easy/EasyView.php 274 function: _render ( ) @ /var/www/html/openbiz/bin/easy/EasyView.php 237 function: render ( ) @ /var/www/html/openbiz/bin/BizController.php 221 function: renderView ( "ser.view.SubscriberListView", "", "", Null, "" ) @ /var/www/html/openbiz/bin/BizController.php 107 function: dispatchRequest ( ) @ /var/www/html/openbiz/bin/BizController.php 32 function: include_once ( "/var/www/html/openbiz/bin/BizController.php" ) @ /var/www/html/siremis/bin/controller.php 6 function: include ( "/var/www/html/siremis/bin/controller.php" ) @ /var/www/html/siremis/bin/_forward.php 102 function: include ( "/var/www/html/siremis/bin/_forward.php" ) @ /var/www/html/siremis/index.php 3 Please ask system administrator for help… Have you faced already a similar issue? Or do you know how I can add those subscribers via command line? Thanks in advance for your help Alex

6 years, 10 months

kamailio-5.0.5 active/passive pcs/cluster with rtpengine - how to fix calls after failover

by Karsten Horsmann

Hello List, and also an happy new year to everyone. I use CentOS 7.4.x with kamailio 5.0.5 and rtpengine on a pacemaker/corosync cluster in front of an internal kamailio siprouter and media-services. If i did an "pcs node standby" to failover my frontend-kamailio (udp/tcp 5060, udp/tcp 5061-tls and tcp websocket-secure) i noticed the following scenarios: 1) Plain RTP: just stocks a few seconds and flows. Everything fine. 2) SDES/RTP: silence - but REINVITE manually in my client brings audio back. Need improvement. 3) DTLS/RTP WebRTC: silence - all clients shows an active call. I know that there is NO way to recover this call - because of the temporay DTLS certificate due the rtpengine start-up. So i thought - for scenario1) i dont need anything to do. Works nice. For scenario2) i need something to "remember its SDES/RTP calls and send them an REINVITE" And for scenario3) i should just hangup all WebRTC calls - IMHO the best for that. How can i fire-up these tasks to get an "clean-up" or "reinvite" after an failover? scenario legend: 1) unencrypted call 2) TLS/SDES encrypted call 3) DTÖS WebRTC encrypted call -- Kind Regards *Karsten Horsmann*

6 years, 10 months

XML-RPC htable.reload

by Martin Nyström

Hi, I am trying to use XML-RPC for issuing a htable.reload but fails to get it working properly. In this scenario I am trying to reload the htable “foobar”. My XML doc looks as follows: <?xml version="1.0"?> <methodCall> <methodName>htable.reload foobar</methodName> <params></params> </methodCall> The returned response is: <?xml version="1.0"?> <methodResponse> <fault> <value> <struct> <member> <name>faultCode</name> <value><int>500</int></value> </member> <member> <name>faultString</name> <value><string>Method Not Found</string></value> </member> </struct> </value> </fault> </methodResponse> So my question is really how I can use XML-RPC to reload a htable. I am probaly missing a field here or anything like that. kamailio 4.4.5 (x86_64/linux) Regards

6 years, 10 months

Error linking contact to IMPU on SCSCF

by Rafi A.

Hi there, I need some help here to understand why the query in [usrloc_db.c:1084] is empty. This causes the linking of contact to IMPU to fail. I'm using Kamailio 5.0.4. 10(13882) DEBUG: ims_usrloc_scscf [impurecord.c:1284]: unref_subscription_unsafe(): un-reffing subscription [rafi(a)mnc001.mcc001.3gppnetwork.org] - was [3] 10(13882) DEBUG: ims_registrar_scscf [save.c:519]: update_contacts_helper(): updating the contacts for IMPU <sip:rafi@mnc001.mcc001.3gppnetwork.org> 10(13882) DEBUG: ims_registrar_scscf [save.c:137]: calc_contact_expires(): Calculated expires for contact is 600000 10(13882) DEBUG: ims_registrar_scscf [save.c:548]: update_contacts_helper(): Need to update contact: <sip:rafi@192.168.10.48:57230;transport=udp>: q_value [-1],sos: [0],expires [600000] 10(13882) DEBUG: ims_registrar_scscf [save.c:550]: update_contacts_helper(): packing contact information 10(13882) DEBUG: ims_registrar_scscf [save.c:556]: update_contacts_helper(): adding/updating contact based on prior existence 10(13882) DEBUG: ims_usrloc_scscf [impurecord.c:748]: get_scontact(): looking for contact [sip:rafi@192.168.10.48:57230;transport=udp] in slot 300 10(13882) DEBUG: ims_registrar_scscf [save.c:562]: update_contacts_helper(): inserting new contact 10(13882) DEBUG: ims_usrloc_scscf [impurecord.c:562]: insert_scontact(): INSERTing ucontact in usrloc module 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:118]: new_ucontact(): Checking param [+g.3gpp.cs-voice] 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:118]: new_ucontact(): Checking param [+g.3gpp.icsi-ref] 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:118]: new_ucontact(): Checking param [audio] 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:118]: new_ucontact(): Checking param [+g.oma.sip-im.large-message] 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:118]: new_ucontact(): Checking param [+g.3gpp.smsip] 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:118]: new_ucontact(): Checking param [language] 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:118]: new_ucontact(): Checking param [+g.oma.sip-im] 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:118]: new_ucontact(): Checking param [expires] 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:173]: new_ucontact(): generating hash based on [sip:rafi@192.168.10.48:57230;transport=udp] 10(13882) DEBUG: ims_usrloc_scscf [impurecord.c:280]: mem_insert_scontact(): Created new contact in memory with AOR: [sip:rafi@192.168.10.48:57230;transport=udp] and hash [300] 10(13882) DEBUG: ims_usrloc_scscf [usrloc_db.c:289]: db_insert_ucontact(): DB: inserting ucontact [sip:rafi@192.168.10.48:57230;transport=udp] 10(13882) DEBUG: ims_usrloc_scscf [usrloc_db.c:311]: db_insert_ucontact(): Converted params to string to insert into db: [+g.3gpp.cs-voice;+g.3gpp.icsi-ref=urn%3Aurn-7%3A3gpp-application.ims.iari.g sma-vs;audio;+g.oma.sip-im.large-message;+g.3gpp.smsip;language=en,fr;+g.oma .sip-im;expires=600000] 10(13882) DEBUG: ims_usrloc_scscf [udomain.c:843]: ref_contact_unsafe(): incrementing ref count on contact [sip:rafi@192.168.10.48:57230;transport=udp], was 1 10(13882) DEBUG: ims_usrloc_scscf [impurecord.c:1225]: link_contact_to_impu(): number of contacts for IMPU [sip:rafi@mnc001.mcc001.3gppnetwork.org] is 1 10(13882) DEBUG: ims_usrloc_scscf [usrloc_db.c:1065]: db_link_contact_to_impu(): DB: linking contact to IMPU 10(13882) DEBUG: ims_usrloc_scscf [usrloc_db.c:1084]: db_link_contact_to_impu(): QUERY IS [] and len is 0 10(13882) ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Query was empty (1065) 10(13882) ERROR: <core> [db_query.c:181]: db_do_raw_query(): error while submitting query 10(13882) ERROR: ims_usrloc_scscf [usrloc_db.c:1086]: db_link_contact_to_impu(): Unable to link impu-contact in DB - impu [ <sip:rafi@mnc001.mcc001.3gppnetwork.org> sip:rafi@mnc001.mcc001.3gppnetwork.org], contact [ <sip:rafi@192.168.10.48:57230;transport=udp> sip:rafi@192.168.10.48:57230;transport=udp] 10(13882) ERROR: ims_usrloc_scscf [impurecord.c:1227]: link_contact_to_impu(): Failed to update DB linking contact [ <sip:rafi@192.168.10.48:57230;transport=udp> sip:rafi@192.168.10.48:57230;transport=udp] to IMPU [ <sip:rafi@mnc001.mcc001.3gppnetwork.org> sip:rafi@mnc001.mcc001.3gppnetwork.org]...continuing but db will be out of sync! 10(13882) DEBUG: ims_usrloc_scscf [udomain.c:852]: unref_contact_unsafe(): decrementing ref count on contact [sip:rafi@192.168.10.48:57230;transport=udp], was 2 Best Regards, Rafael A.

6 years, 10 months

Re: [SR-Users] TLS cipher suites

by Steve

Hello, Thank you both for your responses to my query about TLS cipher suites supported by Kamailio 4.3.4. When I used a self-signed certificate generated from an RSA key, the server selected the RSA-AES256-GCM-SHA384 cipher suite for the connection. When I used a self-signed certificate generated from an EC key, the server selected the ECDH-ECDSA-AES256-GCM-SHA384 cipher suite for the connection. This was confirmed using the OpenSSL /s_client/ command and with Wireshark. In short, I am still unable to establish an ECDHE ephemeral key exchange even though the OpenSSL version 1.0.2g on Lubuntu 16.4.3 supports it. So I must not have the correct configuration of the TLS module for Kamailio 4.3.4 or else need to generate some other kind of key/certificate. I'm using the Kamailio and TLS config files that came with the package downloads, minimally modified to enable TLS and specify the file location of the key and certificate. I googled "ephemeral key exchange" and came across a posting on Stack Exchange talking about commands such as /SSL_CTX_set_temp_ecdh_callback/ that enable ephemeral key exchange. This command is not listed as a configuration setting in the TLS module man-page so I assume it is a coding command used within the module. In any case, I'd appreciate any further suggestions. Thanks, Steve --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

6 years, 10 months

Anyone successfully run Fortify on Kamailio?

by Malcolm O'Hare

I've been trying to run Fortify Static Code Analyzer on the Kamailio build but all the ways its suggested to hook the build aren't working. I'm curious if anyone has tried to run it and been successful, and if they saved / remember what they did.

6 years, 10 months

usrloc rpc command ul add

by Евгений Голей

Hello! Tell me how, when using the "kamcmd ul.add location username@domain sip:contact_username@contact_ip:contact_port 0 1.0 ??? 0 0 0" command, specify parameters that are not used, for example path ? -- С уважением, Евгений Голей

6 years, 10 months

Re: [SR-Users] app_lua sr.sqlops.query exit status

by Daniel-Constantin Mierla

Now the backtrace is different, gram the output for info locals in frame 5 and 6. Cheers, Daniel On 10.01.18 11:26, jenus(a)cyberchaos.nl wrote: > I have overwritten the core file b y accident. I did a new backtrace: > > (gdb) backtrace > #0 0x00007fd3b24365a0 in ?? () from > /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 > #1 0x00007fd3b2437b62 in ?? () from > /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 > #2 0x00007fd3b242a040 in lua_settable () from > /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 > #3 0x00007fd3b243a412 in luaL_findtable () from > /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 > #4 0x00007fd3b243a581 in luaL_openlib () from > /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 > #5 0x00007fd3b2684870 in lua_sr_kemi_register_libs (L=0xeffdb0) at > app_lua_sr.c:1973 > #6 0x00007fd3b26cf107 in lua_sr_openlibs (L=0xeffdb0) at > app_lua_api.c:185 > #7 0x00007fd3b26cf7c1 in lua_sr_init_probe () at app_lua_api.c:225 > #8 0x00007fd3b265b97d in child_init (rank=-127) at app_lua_mod.c:197 > #9 0x0000000000549944 in init_mod_child (m=0x7fd3bc82cc70, rank=-127) > at core/sr_module.c:938 > #10 0x0000000000549c72 in init_child (rank=-127) at core/sr_module.c:964 > #11 0x0000000000422c1c in main_loop () at main.c:1576 > #12 0x000000000042aab9 in main (argc=3, argv=0x7ffeee95b548) at > main.c:2646 > > (gdb) frame 7 > #7 0x00007fd3b26cf7c1 in lua_sr_init_probe () at app_lua_api.c:225 > 225 app_lua_api.c: No such file or directory. > (gdb) list > 220 in app_lua_api.c > (gdb) info locals > L = 0xeffdb0 > txt = 0x7fd3bd00dce7 <__fprintf+135> "H\201\304", <incomplete sequence > \330> > li = 0x0 > sbuf = {st_dev = 0, st_ino = 206158430256, st_nlink = 140732901208248, > st_mode = 4002787296, st_uid = 32766, st_gid = 4002787464, __pad0 = > 14, st_rdev = 140728898420739, st_size = 0, > st_blksize = 30795, st_blocks = 7970120, st_atim = {tv_sec = > 7929944, tv_nsec = 0}, st_mtim = {tv_sec = 0, tv_nsec = > 140732901208128}, st_ctim = {tv_sec = 140547210663782, > tv_nsec = 7938688}, __glibc_reserved = {-541165879423, > 140732901208240, 5544260}} > __FUNCTION__ = "lua_sr_init_probe" > > I assume that in this case i need to do a "frame 7". > > > Jan > > Daniel-Constantin Mierla schreef op 2018-01-10 11:18: >> Few more things to grab from core file with gdb -- take the output for >> the next commands: >> >> frame 16 >> >> list >> >> info locals >> >> Cheers, >> Daniel >> >> >> On 10.01.18 11:08, jenus(a)cyberchaos.nl wrote: >>> Daniel, >>> >>> Here are the app_lua settings: >>> >>> # ----- app_lua params ----- >>> modparam("app_lua", "load", "/etc/kamailio/kamailio_functions.lua") >>> modparam("app_lua", "register", "sqlops") >>> modparam("app_lua", "register", "siputils") >>> modparam("app_lua", "register", "xhttp") >>> >>> >>> Jan >>> >>> >>> Daniel-Constantin Mierla schreef op 2018-01-10 11:03: >>>> Can you give here the parameters you set for app_lua module? >>>> >>>> Cheers, >>>> Daniel >>>> >>>> >>>> On 09.01.18 22:27, jenus(a)cyberchaos.nl wrote: >>>>> Daniel, >>>>> >>>>> Here is the backtrace. >>>>> >>>>> (gdb) backtrace >>>>> #0 0x00007fe41140e067 in __GI_raise (sig=sig@entry=6) at >>>>> ../nptl/sysdeps/unix/sysv/linux/raise.c:56 >>>>> #1 0x00007fe41140f448 in __GI_abort () at abort.c:89 >>>>> #2 0x00007fe41144c1b4 in __libc_message (do_abort=do_abort@entry=1, >>>>> fmt=fmt@entry=0x7fe411541210 "*** Error in `%s': %s: 0x%s ***\n") at >>>>> ../sysdeps/posix/libc_fatal.c:175 >>>>> #3 0x00007fe41145198e in malloc_printerr (action=1, >>>>> str=0x7fe41153d42a "realloc(): invalid next size", ptr=<optimized >>>>> out>) at malloc.c:4996 >>>>> #4 0x00007fe41145476b in _int_realloc (av=av@entry=0x7fe41177e620 >>>>> <main_arena>, oldp=oldp@entry=0x21789c0, oldsize=oldsize@entry=736, >>>>> nb=nb@entry=1552) at malloc.c:4234 >>>>> #5 0x00007fe411455769 in __GI___libc_realloc (oldmem=0x21789d0, >>>>> bytes=1536) at malloc.c:3029 >>>>> #6 0x00007fe40c460cae in ?? () from >>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>> #7 0x00007fe40c45c9aa in ?? () from >>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>> #8 0x00007fe40c46166d in ?? () from >>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>> #9 0x00007fe40c4640b3 in ?? () from >>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>> #10 0x00007fe40c45ccd1 in ?? () from >>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>> #11 0x00007fe40c45c92e in ?? () from >>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>> #12 0x00007fe40c45d7bb in ?? () from >>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>> #13 0x00007fe40c45d8c2 in ?? () from >>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>> #14 0x00007fe40c459528 in lua_load () from >>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>> #15 0x00007fe40c469d8c in luaL_loadbuffer () from >>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>> #16 0x00007fe40c6fe7d7 in lua_sr_init_probe () at app_lua_api.c:228 >>>>> #17 0x00007fe40c68a97d in child_init (rank=-127) at app_lua_mod.c:197 >>>>> #18 0x0000000000549944 in init_mod_child (m=0x7fe410c3b998, >>>>> rank=-127) >>>>> at core/sr_module.c:938 >>>>> #19 0x0000000000549662 in init_mod_child (m=0x7fe410c3bec0, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #20 0x0000000000549662 in init_mod_child (m=0x7fe410c3c708, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #21 0x0000000000549662 in init_mod_child (m=0x7fe410c3cd78, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #22 0x0000000000549662 in init_mod_child (m=0x7fe410c3d360, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #23 0x0000000000549662 in init_mod_child (m=0x7fe410c3e1e8, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #24 0x0000000000549662 in init_mod_child (m=0x7fe410c3e938, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #25 0x0000000000549662 in init_mod_child (m=0x7fe410c3f4c8, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #26 0x0000000000549662 in init_mod_child (m=0x7fe410c3fca0, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #27 0x0000000000549662 in init_mod_child (m=0x7fe410c40118, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #28 0x0000000000549662 in init_mod_child (m=0x7fe410c40780, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #29 0x0000000000549662 in init_mod_child (m=0x7fe410c422f8, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #30 0x0000000000549662 in init_mod_child (m=0x7fe410c42968, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #31 0x0000000000549662 in init_mod_child (m=0x7fe410c42e50, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #32 0x0000000000549662 in init_mod_child (m=0x7fe410c43b48, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #33 0x0000000000549662 in init_mod_child (m=0x7fe410c43f20, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #34 0x0000000000549662 in init_mod_child (m=0x7fe410c446e0, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #35 0x0000000000549662 in init_mod_child (m=0x7fe410c44bd0, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #36 0x0000000000549662 in init_mod_child (m=0x7fe410c44ec8, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #37 0x0000000000549662 in init_mod_child (m=0x7fe410c45378, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #38 0x0000000000549662 in init_mod_child (m=0x7fe410c458f0, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #39 0x0000000000549662 in init_mod_child (m=0x7fe410c45e48, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #40 0x0000000000549662 in init_mod_child (m=0x7fe410c464e8, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #41 0x0000000000549662 in init_mod_child (m=0x7fe410c47278, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #42 0x0000000000549662 in init_mod_child (m=0x7fe410c476f0, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #43 0x0000000000549662 in init_mod_child (m=0x7fe410c47b68, >>>>> rank=-127) >>>>> at core/sr_module.c:935 >>>>> #44 0x0000000000549c72 in init_child (rank=-127) at >>>>> core/sr_module.c:964 >>>>> #45 0x0000000000422c1c in main_loop () at main.c:1576 >>>>> #46 0x000000000042aab9 in main (argc=3, argv=0x7ffe17f0e788) at >>>>> main.c:2646 >>>>> >>>>> >>>>> Jan >>>>> >>>>> Daniel-Constantin Mierla schreef op 2018-01-09 22:21: >>>>>> Can you install the debug symbols for kamailio as well? There >>>>>> should be >>>>>> a kamailio-dbg package or so ... >>>>>> >>>>>> Then take again the backtrace, it should provide more information -- >>>>>> file and line for each frame, ... >>>>>> >>>>>> Cheers, >>>>>> Daniel >>>>>> >>>>>> >>>>>> On 09.01.18 21:21, jenus(a)cyberchaos.nl wrote: >>>>>>> Daniel, >>>>>>> >>>>>>> Just upgraded to 5.1 but kamailio now generates a core file. I'm >>>>>>> running debian 8.10. It seems to crash on liblua5.1.so.0 : >>>>>>> >>>>>>> Using host libthread_db library >>>>>>> "/lib/x86_64-linux-gnu/libthread_db.so.1". >>>>>>> Core was generated by `kamailio -m 1500'. >>>>>>> Program terminated with signal SIGSEGV, Segmentation fault. >>>>>>> #0 0x00007f30c17f25a0 in ?? () from >>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>> (gdb) backtrace >>>>>>> #0 0x00007f30c17f25a0 in ?? () from >>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>> #1 0x00007f30c17f3b62 in ?? () from >>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>> #2 0x00007f30c17e6040 in lua_settable () from >>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>> #3 0x00007f30c17f6412 in luaL_findtable () from >>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>> #4 0x00007f30c17f6581 in luaL_openlib () from >>>>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>>>> #5 0x00007f30c1a40870 in lua_sr_kemi_register_libs () from >>>>>>> /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so >>>>>>> #6 0x00007f30c1a8b107 in lua_sr_openlibs () from >>>>>>> /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so >>>>>>> #7 0x00007f30c1a8b7c1 in lua_sr_init_probe () from >>>>>>> /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so >>>>>>> #8 0x00007f30c1a1797d in ?? () from >>>>>>> /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so >>>>>>> #9 0x0000000000549944 in ?? () >>>>>>> #10 0x0000000000549c72 in init_child () >>>>>>> #11 0x0000000000421498 in main_loop () >>>>>>> #12 0x000000000042aab9 in main () >>>>>>> >>>>>>> >>>>>>> >>>>>>> Thanks, >>>>>>> >>>>>>> Jan >>>>>>> >>>>>>> jenus(a)cyberchaos.nl schreef op 2018-01-09 20:53: >>>>>>>> Daniel, >>>>>>>> >>>>>>>> Currently running kamailio 5.0.5. >>>>>>>> >>>>>>>> Jan >>>>>>>> >>>>>>>> Daniel-Constantin Mierla schreef op 2018-01-09 13:27: >>>>>>>>> Hello, >>>>>>>>> >>>>>>>>> what version of kamailio are you using? >>>>>>>>> >>>>>>>>> Cheers, >>>>>>>>> Daniel >>>>>>>>> >>>>>>>>> >>>>>>>>> On 07.01.18 22:14, jenus(a)cyberchaos.nl wrote: >>>>>>>>>> Hello, >>>>>>>>>> >>>>>>>>>> I'm doing some tests with a lua script and app_lua. I'm using >>>>>>>>>> sr.sqlops.query to insert records into the database but would >>>>>>>>>> like to >>>>>>>>>> test the exit status of the sql query. In kamailio i can do: >>>>>>>>>> >>>>>>>>>> if(!sql_query("kamailio", "INSERT INTO subscriber ...")) >>>>>>>>>> >>>>>>>>>> Is there some kind of exit status for the lua function >>>>>>>>>> sr.sqlops.query >>>>>>>>>> in order to do the same check in lua? In other words, is it >>>>>>>>>> possible >>>>>>>>>> to check if a sql query was successful in lua? The result seems >>>>>>>>>> to be >>>>>>>>>> nill in all cases for a INSERT in lua using sr.sqlops.query. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Thanks, >>>>>>>>>> >>>>>>>>>> Jan Hazenberg >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Kamailio (SER) - Users Mailing List >>>>>>>>>> sr-users(a)lists.kamailio.org >>>>>>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Kamailio (SER) - Users Mailing List >>>>>>>> sr-users(a)lists.kamailio.org >>>>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>>>>>> >>>>> >>> > -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

6 years, 10 months

Re: [SR-Users] app_lua sr.sqlops.query exit status

by Daniel-Constantin Mierla

Few more things to grab from core file with gdb -- take the output for the next commands: frame 16 list info locals Cheers, Daniel On 10.01.18 11:08, jenus(a)cyberchaos.nl wrote: > Daniel, > > Here are the app_lua settings: > > # ----- app_lua params ----- > modparam("app_lua", "load", "/etc/kamailio/kamailio_functions.lua") > modparam("app_lua", "register", "sqlops") > modparam("app_lua", "register", "siputils") > modparam("app_lua", "register", "xhttp") > > > Jan > > > Daniel-Constantin Mierla schreef op 2018-01-10 11:03: >> Can you give here the parameters you set for app_lua module? >> >> Cheers, >> Daniel >> >> >> On 09.01.18 22:27, jenus(a)cyberchaos.nl wrote: >>> Daniel, >>> >>> Here is the backtrace. >>> >>> (gdb) backtrace >>> #0 0x00007fe41140e067 in __GI_raise (sig=sig@entry=6) at >>> ../nptl/sysdeps/unix/sysv/linux/raise.c:56 >>> #1 0x00007fe41140f448 in __GI_abort () at abort.c:89 >>> #2 0x00007fe41144c1b4 in __libc_message (do_abort=do_abort@entry=1, >>> fmt=fmt@entry=0x7fe411541210 "*** Error in `%s': %s: 0x%s ***\n") at >>> ../sysdeps/posix/libc_fatal.c:175 >>> #3 0x00007fe41145198e in malloc_printerr (action=1, >>> str=0x7fe41153d42a "realloc(): invalid next size", ptr=<optimized >>> out>) at malloc.c:4996 >>> #4 0x00007fe41145476b in _int_realloc (av=av@entry=0x7fe41177e620 >>> <main_arena>, oldp=oldp@entry=0x21789c0, oldsize=oldsize@entry=736, >>> nb=nb@entry=1552) at malloc.c:4234 >>> #5 0x00007fe411455769 in __GI___libc_realloc (oldmem=0x21789d0, >>> bytes=1536) at malloc.c:3029 >>> #6 0x00007fe40c460cae in ?? () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #7 0x00007fe40c45c9aa in ?? () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #8 0x00007fe40c46166d in ?? () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #9 0x00007fe40c4640b3 in ?? () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #10 0x00007fe40c45ccd1 in ?? () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #11 0x00007fe40c45c92e in ?? () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #12 0x00007fe40c45d7bb in ?? () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #13 0x00007fe40c45d8c2 in ?? () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #14 0x00007fe40c459528 in lua_load () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #15 0x00007fe40c469d8c in luaL_loadbuffer () from >>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>> #16 0x00007fe40c6fe7d7 in lua_sr_init_probe () at app_lua_api.c:228 >>> #17 0x00007fe40c68a97d in child_init (rank=-127) at app_lua_mod.c:197 >>> #18 0x0000000000549944 in init_mod_child (m=0x7fe410c3b998, rank=-127) >>> at core/sr_module.c:938 >>> #19 0x0000000000549662 in init_mod_child (m=0x7fe410c3bec0, rank=-127) >>> at core/sr_module.c:935 >>> #20 0x0000000000549662 in init_mod_child (m=0x7fe410c3c708, rank=-127) >>> at core/sr_module.c:935 >>> #21 0x0000000000549662 in init_mod_child (m=0x7fe410c3cd78, rank=-127) >>> at core/sr_module.c:935 >>> #22 0x0000000000549662 in init_mod_child (m=0x7fe410c3d360, rank=-127) >>> at core/sr_module.c:935 >>> #23 0x0000000000549662 in init_mod_child (m=0x7fe410c3e1e8, rank=-127) >>> at core/sr_module.c:935 >>> #24 0x0000000000549662 in init_mod_child (m=0x7fe410c3e938, rank=-127) >>> at core/sr_module.c:935 >>> #25 0x0000000000549662 in init_mod_child (m=0x7fe410c3f4c8, rank=-127) >>> at core/sr_module.c:935 >>> #26 0x0000000000549662 in init_mod_child (m=0x7fe410c3fca0, rank=-127) >>> at core/sr_module.c:935 >>> #27 0x0000000000549662 in init_mod_child (m=0x7fe410c40118, rank=-127) >>> at core/sr_module.c:935 >>> #28 0x0000000000549662 in init_mod_child (m=0x7fe410c40780, rank=-127) >>> at core/sr_module.c:935 >>> #29 0x0000000000549662 in init_mod_child (m=0x7fe410c422f8, rank=-127) >>> at core/sr_module.c:935 >>> #30 0x0000000000549662 in init_mod_child (m=0x7fe410c42968, rank=-127) >>> at core/sr_module.c:935 >>> #31 0x0000000000549662 in init_mod_child (m=0x7fe410c42e50, rank=-127) >>> at core/sr_module.c:935 >>> #32 0x0000000000549662 in init_mod_child (m=0x7fe410c43b48, rank=-127) >>> at core/sr_module.c:935 >>> #33 0x0000000000549662 in init_mod_child (m=0x7fe410c43f20, rank=-127) >>> at core/sr_module.c:935 >>> #34 0x0000000000549662 in init_mod_child (m=0x7fe410c446e0, rank=-127) >>> at core/sr_module.c:935 >>> #35 0x0000000000549662 in init_mod_child (m=0x7fe410c44bd0, rank=-127) >>> at core/sr_module.c:935 >>> #36 0x0000000000549662 in init_mod_child (m=0x7fe410c44ec8, rank=-127) >>> at core/sr_module.c:935 >>> #37 0x0000000000549662 in init_mod_child (m=0x7fe410c45378, rank=-127) >>> at core/sr_module.c:935 >>> #38 0x0000000000549662 in init_mod_child (m=0x7fe410c458f0, rank=-127) >>> at core/sr_module.c:935 >>> #39 0x0000000000549662 in init_mod_child (m=0x7fe410c45e48, rank=-127) >>> at core/sr_module.c:935 >>> #40 0x0000000000549662 in init_mod_child (m=0x7fe410c464e8, rank=-127) >>> at core/sr_module.c:935 >>> #41 0x0000000000549662 in init_mod_child (m=0x7fe410c47278, rank=-127) >>> at core/sr_module.c:935 >>> #42 0x0000000000549662 in init_mod_child (m=0x7fe410c476f0, rank=-127) >>> at core/sr_module.c:935 >>> #43 0x0000000000549662 in init_mod_child (m=0x7fe410c47b68, rank=-127) >>> at core/sr_module.c:935 >>> #44 0x0000000000549c72 in init_child (rank=-127) at >>> core/sr_module.c:964 >>> #45 0x0000000000422c1c in main_loop () at main.c:1576 >>> #46 0x000000000042aab9 in main (argc=3, argv=0x7ffe17f0e788) at >>> main.c:2646 >>> >>> >>> Jan >>> >>> Daniel-Constantin Mierla schreef op 2018-01-09 22:21: >>>> Can you install the debug symbols for kamailio as well? There >>>> should be >>>> a kamailio-dbg package or so ... >>>> >>>> Then take again the backtrace, it should provide more information -- >>>> file and line for each frame, ... >>>> >>>> Cheers, >>>> Daniel >>>> >>>> >>>> On 09.01.18 21:21, jenus(a)cyberchaos.nl wrote: >>>>> Daniel, >>>>> >>>>> Just upgraded to 5.1 but kamailio now generates a core file. I'm >>>>> running debian 8.10. It seems to crash on liblua5.1.so.0 : >>>>> >>>>> Using host libthread_db library >>>>> "/lib/x86_64-linux-gnu/libthread_db.so.1". >>>>> Core was generated by `kamailio -m 1500'. >>>>> Program terminated with signal SIGSEGV, Segmentation fault. >>>>> #0 0x00007f30c17f25a0 in ?? () from >>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>> (gdb) backtrace >>>>> #0 0x00007f30c17f25a0 in ?? () from >>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>> #1 0x00007f30c17f3b62 in ?? () from >>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>> #2 0x00007f30c17e6040 in lua_settable () from >>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>> #3 0x00007f30c17f6412 in luaL_findtable () from >>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>> #4 0x00007f30c17f6581 in luaL_openlib () from >>>>> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 >>>>> #5 0x00007f30c1a40870 in lua_sr_kemi_register_libs () from >>>>> /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so >>>>> #6 0x00007f30c1a8b107 in lua_sr_openlibs () from >>>>> /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so >>>>> #7 0x00007f30c1a8b7c1 in lua_sr_init_probe () from >>>>> /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so >>>>> #8 0x00007f30c1a1797d in ?? () from >>>>> /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so >>>>> #9 0x0000000000549944 in ?? () >>>>> #10 0x0000000000549c72 in init_child () >>>>> #11 0x0000000000421498 in main_loop () >>>>> #12 0x000000000042aab9 in main () >>>>> >>>>> >>>>> >>>>> Thanks, >>>>> >>>>> Jan >>>>> >>>>> jenus(a)cyberchaos.nl schreef op 2018-01-09 20:53: >>>>>> Daniel, >>>>>> >>>>>> Currently running kamailio 5.0.5. >>>>>> >>>>>> Jan >>>>>> >>>>>> Daniel-Constantin Mierla schreef op 2018-01-09 13:27: >>>>>>> Hello, >>>>>>> >>>>>>> what version of kamailio are you using? >>>>>>> >>>>>>> Cheers, >>>>>>> Daniel >>>>>>> >>>>>>> >>>>>>> On 07.01.18 22:14, jenus(a)cyberchaos.nl wrote: >>>>>>>> Hello, >>>>>>>> >>>>>>>> I'm doing some tests with a lua script and app_lua. I'm using >>>>>>>> sr.sqlops.query to insert records into the database but would >>>>>>>> like to >>>>>>>> test the exit status of the sql query. In kamailio i can do: >>>>>>>> >>>>>>>> if(!sql_query("kamailio", "INSERT INTO subscriber ...")) >>>>>>>> >>>>>>>> Is there some kind of exit status for the lua function >>>>>>>> sr.sqlops.query >>>>>>>> in order to do the same check in lua? In other words, is it >>>>>>>> possible >>>>>>>> to check if a sql query was successful in lua? The result seems >>>>>>>> to be >>>>>>>> nill in all cases for a INSERT in lua using sr.sqlops.query. >>>>>>>> >>>>>>>> >>>>>>>> Thanks, >>>>>>>> >>>>>>>> Jan Hazenberg >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Kamailio (SER) - Users Mailing List >>>>>>>> sr-users(a)lists.kamailio.org >>>>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Kamailio (SER) - Users Mailing List >>>>>> sr-users(a)lists.kamailio.org >>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>>>> >>> > -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

6 years, 10 months

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users January 2018