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

Daniel, Here is the backtrace. (gdb) backtrace #0 0x7fe41140e067 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x7fe41140f448 in __GI_abort () at abort.c:89 #2 0x7fe41144c1b4 in __libc_message (do_abort=do_abort@entry=1,

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

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, je...@cyberchaos.nl wrote: > Daniel, > > Just

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

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/

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

If i use the default config and load app_lua.so there it starts fine. But with my own config only loading (no app_lua params) the app_lua.so module seems to crash kamailio. Jan je...@cyberchaos.nl schreef op 2018-01-09 21:21: Daniel, Just upgraded to 5.1 but kamailio now generates a core

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

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,

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

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, je...@cyberchaos.nl wrote: Hello, I'm doing some tests with a lua script and app_lua. I'm using

Re: [SR-Users] kamailio-5.0.5 active/passive pcs/cluster with rtpengine - how to fix calls after failover

Hello Daniel, yes the extra rtpengine server would also an solution but what is if that fails. Two of them are maybe or more. But that makes the public ip stuff more tricky. And I found the dialog modules (there are two of them) would be also a good idea. But brings more complexity to

Re: [SR-Users] t_relay dying ?

Many thanks, I've managed to handle a call properly. I really want to thank Daniel, and all that have helped on this subject. Regards J. On Mon, Jan 8, 2018 at 11:42 PM, Joel Serrano wrote: > Just a hint here, try setting $du and then t_relay... > > On Mon, Jan 8, 2018 at

Re: [SR-Users] topos redis -> failed to store

Hello, I am using kamailio 5.1.0 version root@sip-africallshop-com:/home/aosseni# 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,

Re: [SR-Users] WebRTC proxy for legacy systems

Hello, On 05.01.18 09:55, Karsten Horsmann wrote: > Hello, > > you also be aware of longer callsetups to webrtc clients (13 - 38 > seconds) if there are many ICE candidates on the client (like > different networking devices). > > There maybe also fixes in the js SIP libraries for that (I don't

Re: [SR-Users] kamailio-5.0.5 active/passive pcs/cluster with rtpengine - how to fix calls after failover

Hello, maybe not directly related to the issue, but could be better to separate rtpengine on its own system, likely it requires less failover scenarios, so active calls are not affected at all if you have to do a failover for the signaling server... Anyhow, as you trigger a failover and you know

Re: [SR-Users] TLS cipher suites

Hello, can you see what are the supported cypher advertised by kamailio with tls? Next link should provide some options to do it, searching on web should reveal more:   - https://superuser.com/questions/109213/how-do-i-list-the-ssl-tls-cipher-suites-a-particular-website-offers Cheers, Daniel

Re: [SR-Users] topos redis -> failed to store

Hello, what version of kamailio are you using? Cheers, DAniel On 06.01.18 07:37, Abdoul Osséni wrote: > Hello list, > > I activated topos and topos_redis backend. > > Now, I have the following errors: > > Jan  6 07:34:11 sd-110402 /usr/local/sbin/kamailio[30288]: {1 102 > NOTIFY

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

Hello, what version of kamailio are you using? Cheers, Daniel On 07.01.18 22:14, je...@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

Re: [SR-Users] Kami as NAT traversal + FS as media

Hello, On 05.01.18 12:33, Yu Boot wrote: > Thanks for an answer? but what I want to do (already done :)) is > totally opposite to your solution. > > The main thing I wanted, so I don't need to open 5060/UDP on > FreeSwitch for (entire world), BUT at the same time АЫ should work > with RTP

Re: [SR-Users] Kamailio fail to start with db_mongodb and ndb_mongodb modules

Hi, Please check the definition of DBURL in your code. Before i had the same problem, I solved this issue like this: # *** Value defines - IDs used later in config #!ifdef WITH_MYSQL # - database URL - used to connect to database server by modules such # #as: auth_db, acc, usrloc, a.s.o.

Re: [SR-Users] Kamailio fail to start with db_mongodb and ndb_mongodb modules

Hello, can you check that the #!ifdef ... #!endif are properly paired? There is a warning about it: Jan  5 19:16:05 kmaongo kamailio: WARNING: [core/ppcfg.c:221]: pp_ifdef_level_check(): different number of preprocessor directives: N(#!IF[N]DEF) - N(#!ENDIF) = 1 The error is now in the config

Re: [SR-Users] cdr processing questions

Hello! Regarding the second and third question. I once did like this: route {     route(checks);     route(reqinit); ..     route(class4); } route[reqinit] {          if (has_totag() && (uri == myself) && is_method("INVITE|ACK|BYE|UPDATE"))     {         if(match_dialog())         {