- sr-users - kamailio.org

XML-RPC htable.reload
by Martin Nyström 11 Jan '18

11 Jan '18

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

1 0

Error linking contact to IMPU on SCSCF
by Rafi A. 11 Jan '18

11 Jan '18

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.

1 0

Re: [SR-Users] TLS cipher suites
by Steve 10 Jan '18

10 Jan '18

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

2 2

Anyone successfully run Fortify on Kamailio?
by Malcolm O'Hare 10 Jan '18

10 Jan '18

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.

1 0

usrloc rpc command ul add
by Евгений Голей 10 Jan '18

10 Jan '18

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 ? -- С уважением, Евгений Голей

2 2

Re: [SR-Users] app_lua sr.sqlops.query exit status
by Daniel-Constantin Mierla 10 Jan '18

10 Jan '18

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

2 1

Re: [SR-Users] app_lua sr.sqlops.query exit status
by Daniel-Constantin Mierla 10 Jan '18

10 Jan '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

2 1

Re: [SR-Users] app_lua sr.sqlops.query exit status
by Daniel-Constantin Mierla 10 Jan '18

10 Jan '18

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

2 1

Re: [SR-Users] app_lua sr.sqlops.query exit status
by Daniel-Constantin Mierla 09 Jan '18

09 Jan '18

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

2 1

Re: [SR-Users] app_lua sr.sqlops.query exit status
by Daniel-Constantin Mierla 09 Jan '18

09 Jan '18

Hello, I needed to know in order to suggest use of "KSR" package or not, instead of "sr". The "sr" package likely to be obsoleted soon, as KSR has lot more exported functions and it is part of the kemi framework. See: http://kamailio.org/docs/tutorials/devel/kamailio-kemi-framework/ http://kamailio.org/docs/tutorials/devel/kamailio-kemi-framework/modules/#s… However, 5.0 doesn't have so many KSR exports as 5.1, and not sure if KSR has the sqlops exports in that version -- too late to check more in the code now... Looking at the code, sr.sqlops.query() should return -1 in case of error and 0 if ok. Cheers, Daniel On 09.01.18 20:53, jenus(a)cyberchaos.nl wrote: > 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 > -- 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

1 0

app_lua sr.sqlops.query exit status
by jenus＠cyberchaos.nl 09 Jan '18

09 Jan '18

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

2 4

t_relay dying ?
by Jean Cérien 09 Jan '18

09 Jan '18

Hello I am using kamailio 5.0.2, on a debian 9 system. Everything was running fine, until one of our voip provider changed his switch. Our kamailio is relaying between several voip providers and several asterisk (only the signalisation, no rtp). When we get an invite from this new switch, we select an asterisk and relay it correctly to this box. However, the OK is relayed back. But when the voip providers sends an ACK for this OK, the t_relay function does not return at all, it just dies with no action and no error. Here is the snippet from route(relay) xlog("L_INFO","route(relay) @@ $rm - Source: $si:$sp, fu:$fu, tu:$tu\n" ); $var(restrelay)=t_relay(); xlog("L_INFO","route(relay) @@ $rm - t_relay result: $var(restrelay)" ); if (!$var(restrelay)) { When processing the initial invite, I do get both INFO messages. When the ACK is processed, I only get one INFO message, and no ACK is relayed - so it seems execution dies in the t_relay What could be wrong ??? J. Details of the ACK: ACK sip:dialednumber@kamailioIP:5060 SIP/2.0 Via: SIP/2.0/UDP VOIPPROVIDERIP:5060;branch=z9hG4bKjq16fi00d85uee181ic0.1 To: <sip:kamailioIP:5060>;tag=as7f10ed48 From: <sip:sourcenumber@orange-multimedia.fr >;tag=SD8u3ob01-7dd8efde-0002-00d5-0000-0000 Call-ID: SD8u3ob01-688d41f5e2164ceeafe76f40b82b3f97-v300g00030 CSeq: 1 ACK Max-Forwards: 66 Content-Length: 0 Route: <sip:kamailioIP;lr=on;ftag=SD8u3ob01-7dd8efde-0002-00d5-0000-0000;did=a0b.49d> (should you have enough width; the diagram will look ok) VOIP PROVIDER KAMAILIO ASTERISK 21:38:54.685149 │ ──────────────────────────> │ │ ▒ +0.000451 │ 100 trying -- your call is │ │ ▒ 21:38:54.685600 │ <────────────────────────── │ │ ▒ +0.000084 │ │ INVITE (SDP) │ ▒ 21:38:54.685684 │ │ ──────────────────────────> │ ▒ +0.000831 │ │ 100 Trying │ ▒ 21:38:54.686515 │ │ <────────────────────────── │ ▒ +0.000471 │ │ 200 OK (SDP) │ ▒ 21:38:54.686986 │ │ <────────────────────────── │ ▒ +0.000394 │ 200 OK (SDP) │ │ ▒ 21:38:54.687380 │ <────────────────────────── │ │ ▒ +0.038694 │ ACK │ │ ▒ 21:38:54.726074 │ ──────────────────────────> │ │ ▒ +0.060155 │ │ 200 OK (SDP) │ ▒ 21:38:54.786229 │ │ <<<──────────────────────── │ ▒ +0.000138 │ 200 OK (SDP) │ │ ▒ 21:38:54.786367 │ <<<──────────────────────── │ │ ▒ +0.005721 │ ACK │ │

10 25

WebRTC proxy for legacy systems
by paul＠kristianpaul.org 09 Jan '18

09 Jan '18

Hi, I'm looking to use kamailio as a webrtc proxy for legacy sip system that doesnt have this capability, is there a example or blueprint i can follow to get started with this? I'm RTFMing the docs but still need a while to understand kamailio internals :-)

3 4

Kamailio fail to start with db_mongodb and ndb_mongodb modules
by Abdul Basit 09 Jan '18

09 Jan '18

Hi Daniel & K-Team, I setup kamailio 5.0.5 from git on vanilla Debian GNU/Linux 8.3 (jessie) # kamailio -v version: kamailio 5.0.5 (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 on 16:53:42 Jan 5 2018 with gcc 4.9.2 Installed mongodb from debian repo # dpkg -l | grep mongodb ii mongodb 1:3.2.17-1 amd64 object/document-oriented database (metapackage) ii mongodb-clients 1:3.2.17-1 amd64 object/document-oriented database (client apps) ii mongodb-dev 1:2.4.10-5+deb8u1 amd64 object/document-oriented database (development) ii mongodb-server 1:3.2.17-1 amd64 object/document-oriented database (server package) # mongo --version MongoDB shell version: 3.2.17 Will try sometime with mongodb latest version 3.6 as well as I will get time. Installed libmongoc driver through sid repo "deb http://ftp.de.debian.org/debian sid main" # dpkg -l | grep libmongoc ii libmongoc-1.0-0 1.9.0+dfsg-1 amd64 MongoDB C client library - runtime files ii libmongoc-dev 1.9.0+dfsg-1 amd64 MongoDB C client library - dev files Kamailio compiled with # make cfg include_modules="utils app_lua json evapi db_mongodb ndb_mongodb" Created version collection in mongodb # cat /usr/local/src/kamailio/utils/kamctl/mongodb/kamailio/version-create.mongo | mongo Setup kamailio.cfg as per https://telerain.com/kamailio This time kamailio started successfully without any crash :) --------- Now its time to use mongodb for kamailio backend database. Used default kamailio configuration and defined mongodb connection as #!define DBURL "mongodb://localhost/kamailio" I enabled WITH_USRLOCDB [#!define WITH_USRLOCDB], kamailio refuse to start with errors. Jan 5 19:16:05 kmaongo kamailio: CRITICAL: <core> [core/cfg.y:3411]: yyerror_at(): parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 365, column 30-34: syntax error Jan 5 19:16:05 kmaongo kamailio: CRITICAL: <core> [core/cfg.y:3411]: yyerror_at(): parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 365, column 30-34: Invalid arguments Jan 5 19:16:05 kmaongo kamailio: CRITICAL: <core> [core/cfg.y:3414]: yyerror_at(): parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 365, column 35: Jan 5 19:16:05 kmaongo kamailio[28067]: ERROR: bad config file (3 errors) Jan 5 19:16:05 kmaongo kamailio: WARNING: <core> [core/ppcfg.c:221]: pp_ifdef_level_check(): different number of preprocessor directives: N(#!IF[N]DEF) - N(#!ENDIF) = 1 Jan 5 19:16:05 kmaongo kamailio: INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized Jan 5 19:16:05 kmaongo systemd[1]: kamailio.service: control process exited, code=exited status=255 [FAILJan 5 19:16:05 kmaongo systemd[1]: Failed to start Kamailio (OpenSER) - the Open Source SIP Server. Jan 5 19:16:05 kmaongo systemd[1]: Unit kamailio.service entered failed state. failed! Default userloc params in kamailio.cfg states line 365 as # ----- usrloc params ----- /* enable DB persistency for location entries */ #!ifdef WITH_USRLOCDB modparam("usrloc", "db_url", DBURL) [ << line 365 ] modparam("usrloc", "db_mode", 2) modparam("usrloc", "use_domain", MULTIDOMAIN) modparam("usrloc", "db_insert_null", 1) #!endif I created location collection as well but it didn't help. I experienced same error when I enable WITH_ACCDB or any other section that use DBURL. 1. Whats the syntax error here? 2. Is there any special configuration required to work with mongodb? 3. How can we create collections using 'kamdbctl create' ? What else should I share for resolving the issue? -- regards, abdul basit On 4 January 2018 at 12:50, Abdul Basit <basit.engg(a)gmail.com> wrote: > Hi Daniel, > > Thank you for your reply. > > I tested libmongoc with debian package available with repo. Then I moved > to compile from source. result was same. > > But i will try it again with fresh installation and will post here. > > -- > regards, > > abdul basit > > On 2 January 2018 at 16:38, Daniel-Constantin Mierla <miconda(a)gmail.com> > wrote: > >> Hello, >> >> the issue happens inside mongoc library. Have you tried with the default >> one from Debian, without compiling it from sources? >> >> Cheers, >> Daniel >> >> On 01.01.18 16:51, Abdul Basit wrote: >> >> Hi, >> >> My last email was help for admin review. >> >> Sharing logs through pastebin https://pastebin.com/6HhdYLJK >> >> Interesting part will start from line 983 where it start initializing >> ndb_mongodb. >> >> >> >> On 1 January 2018 at 20:32, Abdul Basit <basit.engg(a)gmail.com> wrote: >> >>> Hi, >>> >>> I enabled but kamailio didn't generate any dump file >>> To enable code dump followed https://www.kamailio.org/dokuw >>> iki/doku.php/troubleshooting:corefiles >>> >>> I also un-commented lines in /etc/init.d/kamailio script >>> >>> if test "$DUMP_CORE" = "yes" ; then >>> # set proper ulimit >>> ulimit -c unlimited >>> >>> # directory for the core dump files >>> COREDIR=/tmp/corefiles >>> [ -d $COREDIR ] || mkdir -p $COREDIR >>> chmod 777 $COREDIR >>> echo "$COREDIR/core.%e.sig%s.%p" > /proc/sys/kernel/core_pattern >>> fi >>> >>> >>> I think reason is that kamailio process didn't exit after crash and keep >>> on restarting. each time with new PID. >>> >>> However, debug file is attached. I hope this will help. >>> -- >>> regards, >>> >>> abdul basit >>> >>> On 29 December 2017 at 20:11, M S <shaheryarkh(a)gmail.com> wrote: >>> >>>> Hi, >>>> >>>> Enable core dump and provide backtrace of sigfault. See this for more >>>> info, >>>> >>>> https://sourceware.org/gdb/onlinedocs/gdb/Backtrace.html >>>> >>>> Thank you. >>>> >>>> On Fri, Dec 29, 2017 at 12:25 PM, Abdul Basit <basit.engg(a)gmail.com> >>>> wrote: >>>> >>>>> Adding further from https://stackoverflow.com/ques >>>>> tions/2549214/interpreting-segfault-messages >>>>> >>>>> error 6 means, fault is >>>>> >>>>> * bit 2 == 1 means kernel, 1 means user-mode >>>>> * bit 4 == 1 means fault was an instruction fetch >>>>> >>>>> >>>>> That looks like kamailio is trying to invoke for db connection where >>>>> libmongo-c don't like to be. >>>>> -- >>>>> regards, >>>>> >>>>> abdul basit >>>>> >>>>> On 29 December 2017 at 15:39, Abdul Basit <basit.engg(a)gmail.com> >>>>> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I am trying to setup mongo db as database engine for kamailio as >>>>>> described at >>>>>> <http://www.kamailio.org/wiki/tutorials/kamailio-and-mongodb> >>>>>> http://www.kamailio.org/wiki/tutorials/kamailio-and-mongodb >>>>>> and >>>>>> https://telerain.com/kamailio >>>>>> >>>>>> OS: Debian GNU/Linux 8.10 (jessie) >>>>>> MongoDB server version: 3.4.10 >>>>>> mongo-c-driver-1.9.0.tar.gz compiled with >>>>>> ./configure --disable-static --disable-silent-rules >>>>>> --enable-debug-symbols --enable-ssl=no --enable-sasl=yes >>>>>> --with-libbson=bundled --enable-optimizations --disable-automatic-init-and-c >>>>>> leanup >>>>>> >>>>>> version: kamailio 5.0.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 on 20:45:44 Dec 27 2017 with gcc 4.9.2 >>>>>> >>>>>> include_modules= utils app_lua db_postgres json evapi db_mongodb >>>>>> ndb_mongodb >>>>>> >>>>>> Kamailio is crashing with segfault as soon as it try to load >>>>>> libmongo-c >>>>>> >>>>>> Dec 28 04:44:14 sipserver systemd[1]: Starting Kamailio (OpenSER) - >>>>>> the Open Source SIP Server... >>>>>> Dec 28 04:44:14 sipserver kamailio: INFO: <core> >>>>>> [core/sctp_core.c:75]: sctp_core_check_support(): SCTP API not enabled - if >>>>>> you want to use it, load sctp module >>>>>> Dec 28 04:44:14 sipserver kamailio: INFO: <core> >>>>>> [core/tcp_main.c:4671]: init_tcp(): using epoll_lt as the io watch method >>>>>> (auto detected) >>>>>> Dec 28 04:44:14 sipserver kamailio[11685]: Listening on >>>>>> Dec 28 04:44:14 sipserver kamailio[11685]: udp: 127.0.0.1:5060 >>>>>> Dec 28 04:44:14 sipserver kamailio[11685]: udp: 192.168.10.20:5060 >>>>>> Dec 28 04:44:14 sipserver kamailio[11685]: tcp: 127.0.0.1:5060 >>>>>> Dec 28 04:44:14 sipserver kamailio[11685]: tcp: 192.168.10.20:5060 >>>>>> Dec 28 04:44:14 sipserver kamailio[11685]: Aliases: >>>>>> Dec 28 04:44:14 sipserver kamailio[11685]: tcp: localhost:5060 >>>>>> Dec 28 04:44:14 sipserver kamailio[11685]: udp: localhost:5060 >>>>>> Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: INFO: rr >>>>>> [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe >>>>>> module is not loaded >>>>>> ..... >>>>>> Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: INFO: >>>>>> <core> [core/udp_server.c:203]: probe_max_receive_buffer(): SO_RCVBUF is >>>>>> finally 425984 >>>>>> Dec 28 04:44:14 sipserver systemd[1]: Started Kamailio (OpenSER) - >>>>>> the Open Source SIP Server. >>>>>> Dec 28 04:44:14 sipserver kernel: [53109.390171] show_signal_msg: 20 >>>>>> callbacks suppressed >>>>>> Dec 28 04:44:14 sipserver kernel: [53109.390176] kamailio[11696] >>>>>> segfault at 78 ip 00007f690c0e6e98 sp 00007ffcde1a4770 error 6 in >>>>>> libmongoc-1.0.so.0.0.0[7f690c0ca000+6e000] >>>>>> Dec 28 04:44:14 sipserver kernel: [53109.390753] kamailio[11694] >>>>>> segfault at 78 ip 00007f690c0e6e98 sp 00007ffcde1a4770 error 6 in >>>>>> libmongoc-1.0.so.0.0.0[7f690c0ca000+6e000] >>>>>> Dec 28 04:44:14 sipserver kernel: [53109.393147] kamailio[11699] >>>>>> segfault at 38 ip 00007f690c0e6e98 sp 00007ffcde1a4770 error 6 in >>>>>> libmongoc-1.0.so.0.0.0[7f690c0ca000+6e000] >>>>>> Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: >>>>>> <core> [main.c:743]: handle_sigs(): child process 11689 exited by a signal >>>>>> 11 >>>>>> Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: >>>>>> <core> [main.c:746]: handle_sigs(): core was not generated >>>>>> Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: >>>>>> <core> [main.c:743]: handle_sigs(): child process 11688 exited by a signal >>>>>> 11 >>>>>> ....... >>>>>> Dec 28 04:44:14 sipserver systemd[1]: kamailio.service: main process >>>>>> exited, code=exited, status=1/FAILURE >>>>>> Dec 28 04:44:14 sipserver systemd[1]: Unit kamailio.service entered >>>>>> failed state. >>>>>> >>>>>> >>>>>> As I tried googling the issue and found few issues with tls >>>>>> connection. >>>>>> I set in default kamailio.cfg but still facing the saem issue. >>>>>> >>>>>> enable_tls=no >>>>>> ... >>>>>> loadmodule "ndb_mongodb.so" >>>>>> modparam("ndb_mongodb", "server", "name=cgr91rc8;uri='mongodb:// >>>>>> localhost/kamailio'") >>>>>> >>>>>> Its mongodb default installation and its accessible without any auth >>>>>> yet. >>>>>> >>>>>> Please suggest the way farward. >>>>>> >>>>>> -- >>>>>> regards, >>>>>> >>>>>> abdul basit >>>>>> >>>>>

3 3

cdr processing questions
by voipspace voipspace 09 Jan '18

09 Jan '18

A few question; Firstly With mod acc and acc_cdr i see the default fields logged is only start_time, end_time, duration. This is an actual entry logged. start_time, end_time, duration 1515353126, 1515353135, 9.660000 Why is the duration 9.660000? It seems wrong because it is more then the difference in time 1515353135 - 1515353126 = 9 Secondly What is a reliable way to capture and log start time, answer time, and end time. How do I get the duration info. a) start time to end time. b) answer to end time. Is there an built in variable that store this info? Thirdly dialog events listed as: event_route[dialog:start] event_route[dialog:end] event_route[dialog:failed] There does not seems to be a event for answer so then how to be notified when a dialog is answered? Regards

2 1

parsing of SIP message failed
by Suresh Talasaniya 08 Jan '18

08 Jan '18

Hi, *I consistently receive the following 3 errors (see below) over and over when a call is being collected.* ERROR: <core> [core/parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 22) ERROR: <core> [core/parser/msg_parser.c:671]: parse_msg(): ERROR: parse_msg: message=<HTTP/1.1 101 Switching Protocols#015#012Sia: SIP/2.0/TLS x.x.x.x:42173#015#012Sec-WebSocket-Protocol: sip#015#012Upgrade: websocket#015#012Connection: upgrade#015#012Sec-WebSocket-Accept: qrLTSNMA7oAO8YXGaUhf3Ru26X0=#015#012Content-Length: 0#015#012#015#012> Any assistance would be appreciated. Thank you. -- Regards, Suresh Talasaniya. Contact : +91-9724264776 Skype : suresh.talsaniya

2 6

OT: question about codetriage
by Daniel-Constantin Mierla 08 Jan '18

08 Jan '18

Hello, anyone here familiar with codetriage service? We got a pull request to refer to it from Kamailio readme.md file: - https://github.com/kamailio/kamailio/pull/1389 The link is to: - https://www.codetriage.com/kamailio/kamailio Which I guess is created by the one who did the pull request. The pull request comments has few references to other projects, including Rails, but as I am not familiar with the service, I thought of asking here and see if others had to deal with and what's the experience. Cheers, Daniel -- 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

1 0

Error in parse json documents in kamailio with jansson module
by Mojtaba 08 Jan '18

08 Jan '18

Hello, I used ndbmongo module in kamailio, I used mongodb_find command to get some data from mongo, like this: if(mongodb_find("sermongo", "Asterisk", "user", "{ \"number\" : \"$fU\" }", "res")) { xlog("L_INFO", "Data from mongodb is \" $mongodb(res=>value) \" \n"); $var(data) = $mongodb(res=>value); } The result in syslog is like this: Jan 8 07:23:36 ubuntu14 /usr/local/sbin/kamailio[12127]: {1 2 INVITE MDRlMjRlNGVjZGY1Y2JkYjA5OGM2ZTg1ZTFjZTk0Nzg.} INFO: <script>: user Data from mongodb is " { "_id" : { "$oid" : "5916def36803fa48468b456b" }, "user_type" : "SIP", "context" : "main_routing", "deny" : "0.0.0.0/0.0.0.0", "call_record" : "no", "dtmfmode" : "rfc2833", "canreinvite" : "no", "directmedia" : "no", "host" : "dynamic", "type" : "friend", "nat" : "force_rport,comedia", "port" : "5060", "qualify" : "yes", "callgroup" : "1", "pickupgroup" : "1", "permit" : "0.0.0.0/0.0.0.0", "callcounter" : "yes", "faxdetect" : "no", "call_limit" : "", "name" : "1000", "number" : "1000", "cid_number" : "1000", "secret" : "123123", "date" : { "$date" : 1494671091612 }, "more_options" : "" } " Now i need to get just some keys like "context" from json and save them in PV, i used jansson2.10 for doing this job, like this: jansson_get("user.context", $var(jdata), "$var(context)"); but i have this error in syslog: Jan 8 07:23:36 ubuntu14 /usr/local/sbin/kamailio[12127]: {1 2 INVITE MDRlMjRlNGVjZGY1Y2JkYjA5OGM2ZTg1ZTFjZTk0Nzg.} ERROR: <core> [core/pvapi.c:903]: pv_parse_spec2(): error searching pvar "oid" Jan 8 07:23:36 ubuntu14 /usr/local/sbin/kamailio[12127]: {1 2 INVITE MDRlMjRlNGVjZGY1Y2JkYjA5OGM2ZTg1ZTFjZTk0Nzg.} ERROR: <core> [core/pvapi.c:1107]: pv_parse_spec2(): wrong char [d/100] in [$oid] at [3 (0)] Jan 8 07:23:36 ubuntu14 /usr/local/sbin/kamailio[12127]: {1 2 INVITE MDRlMjRlNGVjZGY1Y2JkYjA5OGM2ZTg1ZTFjZTk0Nzg.} ERROR: <core> [core/sr_module.c:1268]: fix_param(): bad PVE format: "{ "_id" : { "$oid" : "5916def36803fa48468b456b" }, "user_type" : "SIP", "context" : "main_routing", "deny" : "0.0.0.0/0.0.0.0", "call_record" : "no", "dtmfmode" : "rfc2833", "canreinvite" : "no", "directmedia" : "no", "host" : "dynamic", "type" : "friend", "nat" : "force_rport,comedia", "port" : "5060", "qualify" : "yes", "callgroup" : "1", "pickupgroup" : "1", "permit" : "0.0.0.0/0.0.0.0", "callcounter" : "yes", "faxdetect" : "no", "call_limit" : "", "name" : "1000", "number" : "1000", "cid_number" : "1000", "secret" : "123123", "date" : { "$date" : 1494671091612 }, "more_options" : "" }" Jan 8 07:23:36 ubuntu14 /usr/local/sbin/kamailio[12127]: {1 2 INVITE MDRlMjRlNGVjZGY1Y2JkYjA5OGM2ZTg1ZTFjZTk0Nzg.} ERROR: <core> [core/mod_fix.c:564]: fixup_spve_null(): Cannot convert function parameter 1 to spve Jan 8 07:23:36 ubuntu14 /usr/local/sbin/kamailio[12127]: {1 2 INVITE MDRlMjRlNGVjZGY1Y2JkYjA5OGM2ZTg1ZTFjZTk0Nzg.} ERROR: <core> [core/action.c:1139]: do_action(): runtime fixup failed for jansson_get param 2 Jan 8 07:23:36 ubuntu14 /usr/local/sbin/kamailio[12127]: {1 2 INVITE MDRlMjRlNGVjZGY1Y2JkYjA5OGM2ZTg1ZTFjZTk0Nzg.} ERROR: <core> [core/action.c:1518]: do_action(): run action error at: /usr/local/etc/kamailio/kamailio.cfg:990 Jan 8 07:23:36 ubuntu14 /usr/local/sbin/kamailio[12127]: {1 2 INVITE MDRlMjRlNGVjZGY1Y2JkYjA5OGM2ZTg1ZTFjZTk0Nzg.} ERROR: <script>: Send SIP message to Simotel <192.168.122.1:36854> Let me know how i could fixed this Error in regard of [$oid]? Thanks with regards. -- --Mojtaba Esfandiari.S

2 1

Kamailio World 2018 - Call for Presentations
by Daniel-Constantin Mierla 08 Jan '18

08 Jan '18

Hello, I would like to announce that Call for Presentations at Kamailio World 2018 is now open. You can submit your proposal or see more details at: - https://www.kamailioworld.com/k06/call-for-speakers/ The 6th edition of the event takes place again in Berlin, Germany, during May 14-16, 2018. Expect over 150 participants, developers and community members as well as representatives from other popular open source VoIP projects such as Asterisk or FreeSwitch. Looking forward to meeting many of you there! Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

1 1

Cnxcc doesn't update amount values in redis
by Donat Zenichev 05 Jan '18

05 Jan '18

Hi community. Have a problem with cnxcc call monitoring. __set_max_credit() allocates new call as expected: "DEBUG: cnxcc [cnxcc_mod.c:444]: __dialog_created_callback(): Flag is not set for this message. Ignoring DEBUG: cnxcc [cnxcc_mod.c:1569]: __set_max_credit(): Setting up new call for client [2], max-credit[0.100000], cost-per-sec[0.010000], initial-pulse [6], final-pulse [6], call-id[2f77fd103d0bfa28718d896876b373fe@b2b.user.agent:50600] DEBUG: cnxcc [cnxcc_mod.c:1470]: set_ctrl_flag(): Flag set! DEBUG: cnxcc [cnxcc_redis.c:313]: redis_get_int(): Got INT value: concurrent_calls=0i DEBUG: cnxcc [cnxcc_redis.c:68]: redis_get_or_create_credit_data(): credit_data with ID=[2] DOES NOT exist in the cluster, creating it... DEBUG: cnxcc [cnxcc_redis.c:92]: redis_insert_credit_data(): Inserting credit_data_t using ID [2] DEBUG: cnxcc [cnxcc_mod.c:1125]: __get_or_create_credit_data_entry(): Credit entry didn't exist. Allocated new entry [0x7f17668f6d70] DEBUG: cnxcc [cnxcc_mod.c:1255]: __alloc_new_call_by_money(): New call allocated for client [2]". So that I can see values inside redis: redis.callision.info:6389> HGETALL cnxcc:money:2 1) "concurrent_calls" 2) "0" 3) "consumed_amount" 4) "0.000000" 5) "ended_calls_consumed_amount" 6) "0.000000" 7) "max_amount" 8) "0.000000" 9) "number_of_calls" 10) "1" 11) "type" 12) "1" But cnxcc doesn't update credit amount during the call. modparam("debugger", "mod_level", "cnxcc=4") but there are no rows in kamailio log like: "DEBUG: cnxcc [cnxcc_check.c:94]: check_calls_by_money(): ec=0.000000, ca=0.600000, ca2=0.600000 DEBUG: cnxcc [cnxcc_check.c:107]: check_calls_by_money(): Client [some_client] | Ended-Calls-Credit-Spent: 0.000000 TotalCredit/MaxCredit: 0.600000/3.000000". cnxcc parameters: modparam("cnxcc", "dlg_flag", FLG_DLG) modparam("cnxcc", "redis", "addr=redis.youwillnever.find;port=6389;db=0") modparam("cnxcc", "credit_check_period", 1) function that performs credit setup: if (!cnxcc_set_max_credit("$var(setid)","$var(credit)","$var(cost_per_sec)","$var(i_pulse)","$var(f_pulse)")) { xlog("L_WARN", "----- cnxcc: $fU - Error setting up credit control - R=$ru ID=$ci\n"); sl_send_reply("402", "Payment Required"); } Why is it so? And as see, all values are set zero. Seems to be problem with redis inserts. Any ideas are highly appreciated. Thanks. -- -- BR, Donat Zenichev Wnet VoIP team Tel Ukraine: +380(44) 5-900-800 Tel USA: +164(67) 8-174-17 https://w-net.us/ <http://wnet.ua>

2 1

NOTIFY generation for REFER
by Konstantin Tumalevich 05 Jan '18

05 Jan '18

I try to build custom attended transfer logick with kamailio and asterisk. My backend can do all work (include interconnect between asterisk servers), so I need to fully handle REFER in kamailio. But I can't send back NOTIFY message with the result of a transfer. Is any way to do this logic inside kamailio or I need to write external SIP service? My route looks like: if(!route(FROM_NODE)) { if(is_method("REFER")) { xlog("L_NOTICE", "Got REFER in call ci:$ci for $(hdr(Refer-To){nameaddr.uri})"); sl_send_reply("202", "Accepted [1]"); # HERE I MAKE async request and want to send NOTIFY back exit; } } -- Skype: konstantin.tumalevich

2 1

BUG: tls [tls_server.c:1229]: tls_read_f(): SSL_ERROR_WANT_READ but data still in the rbio (0x7ffd354fcd30, 8 bytes at 461)
by Abdoul Osséni 05 Jan '18

05 Jan '18

Hello Dear, I use Kamailio 5.1.0 on Linux server: root@sip-africallshop-com:~# kamailio -V version: kamailio 5.1.0 (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 I have sometimes the following logs: Dec 14 19:22:16 sd-110402 /usr/local/sbin/kamailio[24197]: BUG: tls [tls_server.c:1229]: tls_read_f(): SSL_ERROR_WANT_READ but data still in the rbio (0x7ffd354fcd30, 8 bytes at 461) Dec 20 10:46:32 sd-110402 /usr/local/sbin/kamailio[24197]: BUG: tls [tls_server.c:1229]: tls_read_f(): SSL_ERROR_WANT_READ but data still in the rbio (0x7ffd354fcd30, 8 bytes at 8) Dec 22 11:02:49 sd-110402 /usr/local/sbin/kamailio[24212]: BUG: tls [tls_server.c:1229]: tls_read_f(): SSL_ERROR_WANT_READ but data still in the rbio (0x7ffd354fcd30, 8 bytes at 3357) Does anybody can explain me these logs? Thanks. Abdoul OSSENI

2 1

One way video using Kamailio, WebRTC, and Asterisk
by Wilkins, Steve 05 Jan '18

05 Jan '18

First I want to give Denys a huge shout-out for all of the help he has given me. It is wonderful that boards like this exists and people are so willing to help a newbie learn. I am on what I am hoping is my last major issue with WebRTC<=>WebRTC calls (using tryit-jssip Chrome or Firefox). I am using Kamailio 5, and Asterisk 15 (pjsip). I am making calls between two WebRTC clients - Client1, and Client2 (using tryit-jssip) Problem: If Client1 calls Client2, and Client2 'ANSWERS', I only have audio/video on Client1. Client2 gets no audio/video, but is connected. If I switch things up and call Client1 from Client2, the same thing happens (Client2 has audio/video and Client1 does not); I can only get audio/video on the calling laptop; the called laptop has no audio/video, but is connected. I see no errors in any of the logs. I am hoping that someone out there has seen this behavior before and has an idea as to the cause and possible solution. Thank you, -Steve

2 1

Is it possible to inject variables into transaction scope
by voipspace voipspace 05 Jan '18

05 Jan '18

2 1

Critical Error
by Nicolas Breuer 04 Jan '18

04 Jan '18

Hello, I got this error when passing a call. CRITICAL: dialog [dlg_hash.c:955]: log_next_state_dlg(): bogus event 5 in state 1 for dlg 0x7f7a17848bd8 [3582:11978] with clid 'ae27f53121fe6d84c6845dedcf2e2793' and tags 'f68d2151b8411946' '' Any ideas ? This is a bug ? Never seen that error before,

3 10

2025

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