[SR-Users] kamailio & redis

2016-06-27 Thread Fabian Pignataro
Hello Community, I'm trying to read data (hash) stored in redis database, from kamailio script. I read the module documentation ndb_redis: http://www.kamailio.org/docs/modules/4.4.x/modules/ndb_redis.html#idp26300788 But I'but I don't understand what I'm doing wrong :/ With someone has had exper

Re: [SR-Users] (no subject)

2016-06-27 Thread Joel Serrano | VOZELIA
Hi Jay, Can you paste your listen= lines from kamailio.cfg? Best regards, Joel. - Original Message - > From: "jay binks" > To: "Kamailio (SER) - Users Mailing List" > Sent: Sunday, June 26, 2016 8:40:47 PM > Subject: Re: [SR-Users] (no subject) > I cant believe I sent this without a

Re: [SR-Users] cgrates - cdrs_tables.sql error

2016-06-27 Thread Alex Balashov
Sounds like a great question for the CGRateS mailing list. :-) On 06/27/2016 01:26 PM, Infinicalls Infinicalls wrote: Hi, I am trying to install cgrates , but face this issue with database. " ERROR 1067 (42000) at line 7: Invalid default value for 'deleted_at' " is encountered in create_cdrs

[SR-Users] cgrates - cdrs_tables.sql error

2016-06-27 Thread Infinicalls Infinicalls
Hi, I am trying to install cgrates , but face this issue with database. " ERROR 1067 (42000) at line 7: Invalid default value for 'deleted_at' " is encountered in create_cdrs_tables.sql . Can somebody let me know how to overcome this? regards Ganesh Kumar __

Re: [SR-Users] Kamailio - PSTN (kamailio) - rtpproxy issue

2016-06-27 Thread Filippo Graziola
Sorry my thoughts weren't correct. When disabling rtpproxy in the local kamailio installation, I have one way audio. The caller, local SIP user, can hear audio from the user registered on the PSTN address, which also can't hang up the call. It seems to me that the kamailio PSTN gateway can't engage

Re: [SR-Users] userblacklist use avp for check_blacklist

2016-06-27 Thread Daniel-Constantin Mierla
You have a negation of the function int the if expression, respectively: !check_user_blacklist(...) If the function returns true on record match and you want to reject in that case, then just remove the ! in the expression. Cheers, Daniel On 27/06/16 14:11, Jan Hazenberg wrote: > Daniel, > > Se

Re: [SR-Users] S-CSCF (kamailio) crashes after deregistration of client

2016-06-27 Thread Jason Penton
Hi Christoff, yes, it will - I back-ported to the 4.4 branch. Cheers Jason On Mon, Jun 27, 2016 at 2:30 PM, Christoph Valentin < christoph.valen...@gmx.at> wrote: > Hi, > > Will this bugfix be part of the release 4.4.2? > > Thanks, > Christoph > > *Gesendet:* Dienstag, 07. Juni 2016 um 16:48 Uh

Re: [SR-Users] S-CSCF (kamailio) crashes after deregistration of client

2016-06-27 Thread Christoph Valentin
Hi,   Will this bugfix be part of the release 4.4.2?   Thanks, Christoph   Gesendet: Dienstag, 07. Juni 2016 um 16:48 Uhr Von: "Christoph Valentin" An: "Jason Penton" Cc: "SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users Mailing List" Betreff: Re: [SR-Users] S-CSCF (k

Re: [SR-Users] userblacklist use avp for check_blacklist

2016-06-27 Thread Jan Hazenberg
Daniel, Seems like it is not working anymore, i now have configured: if (!check_user_blacklist("blacklist", "oranjelaan.net", "318001234")) { xlog("L_ALERT", "ALERT: $rU is blacklisted, rejecting call - IP=$si PORT=$sp R=$ru ID=$ci FU=$fu M=$rm UA=$ua\n");

Re: [SR-Users] Kamailio Iterate All Headers

2016-06-27 Thread Colin Morelli
I suppose there's a lot of subjectivity here - and it greatly depends on your configuration - but at least for my use case I don't quite agree with that statement. My API is already the component performing authentication and making routing decisions anyway, which means Kamailio is going to send th

Re: [SR-Users] Kamailio Iterate All Headers

2016-06-27 Thread Alex Balashov
FWIW, I think that from a security and software quality perspective, explicitly defining which headers you want to feed to the API is the much better approach anyway. -- Alex -- Principal, Evariste Systems LLC (www.evaristesys.com) Sent from my Google Nexus.

Re: [SR-Users] Kamailio Iterate All Headers

2016-06-27 Thread Colin Morelli
Yeah, I saw $mb as I was browsing through things. I was hoping to not have to re-parse the SIP message in the API since Kamailio has already done that work, and it would require some form of a SIP parser in my API. As a future feature request, I'll say that I think this would be a helpful addition

Re: [SR-Users] userblacklist use avp for check_blacklist

2016-06-27 Thread Daniel-Constantin Mierla
Have you done any tests to see if runtime works fine as well? Just to be sure nothing was broken. Cheers, Daniel On 27/06/16 13:46, Jan Hazenberg wrote: > Daniel, > > Yes that seems to fix the problem. Kamailio now starts without crashing. > > Thanks, > > Jan > > > Daniel-Constantin Mierla schre

Re: [SR-Users] Kamailio Iterate All Headers

2016-06-27 Thread Olle E. Johansson
> On 26 Jun 2016, at 22:29, Colin Morelli wrote: > > Hey all, > > Back with more questions. > > I'm using Kamailio to make an HTTP call to my API to perform authentication > and message routing. Currently, I'm trying to build up the post body that I > send to my API to make those decisions.

Re: [SR-Users] userblacklist use avp for check_blacklist

2016-06-27 Thread Jan Hazenberg
Daniel, Yes that seems to fix the problem. Kamailio now starts without crashing. Thanks, Jan Daniel-Constantin Mierla schreef op 2016-06-27 13:08: Can you try with the master branch or backport the next commit? - https://github.com/kamailio/kamailio/commit/5fd2c91f512b7311f11c76023da45758

Re: [SR-Users] userblacklist use avp for check_blacklist

2016-06-27 Thread Daniel-Constantin Mierla
Can you try with the master branch or backport the next commit? - https://github.com/kamailio/kamailio/commit/5fd2c91f512b7311f11c76023da45758fb8c4365 If all ok, then I push the backported patch to stable branches. Cheers, Daniel On 27/06/16 11:57, Daniel-Constantin Mierla wrote: > The spec i

Re: [SR-Users] userblacklist use avp for check_blacklist

2016-06-27 Thread Daniel-Constantin Mierla
The spec is null, so the crash is obvious. I have to look at the code to see why it expect to be a spec there, while it can be a static string. Cheers, Daniel On 27/06/16 10:57, Jan Hazenberg wrote: > Daniel, > > Here the requested gdb output: > > (gdb) frame 1 > #1 0x7f22fd252ece in check_

[SR-Users] Kamailio - PSTN (kamailio) - rtpproxy issue

2016-06-27 Thread Filippo Graziola
Hello everybody, I have a local kamailio+rtpproxy under NAT listening on multiple local interfaces (vlans) which works fluenty for all local user indipendently and engages rtpproxy correctly. I have another working kamailio+rtpproxy which is accessible from everywhere at a public address and I wou

Re: [SR-Users] behaviour of uac_redirect module

2016-06-27 Thread Dirk Teurlings - Signet B.V.
On 06/27/2016 11:01 AM, Daniel-Constantin Mierla wrote: > as far as I can remember, sending a redirect 3xx response takes in > consideration any new request URI, which is added as contact. Now, not > sure why the second parameter of get_contacts() would influence that, no > much time to look at the

Re: [SR-Users] behaviour of uac_redirect module

2016-06-27 Thread Daniel-Constantin Mierla
Hello, as far as I can remember, sending a redirect 3xx response takes in consideration any new request URI, which is added as contact. Now, not sure why the second parameter of get_contacts() would influence that, no much time to look at the code. But, meanwhile, can you try with revert_uri() in

Re: [SR-Users] userblacklist use avp for check_blacklist

2016-06-27 Thread Jan Hazenberg
Daniel, Here the requested gdb output: (gdb) frame 1 #1 0x7f22fd252ece in check_user_blacklist_fixup (param=0x7f23061cdd88, param_no=1) at userblacklist.c:213 213 if(str2int(&s, (unsigned int*)&model->spec->pvp.pvn.u.isname.name.n) != 0) { (gdb) info l

Re: [SR-Users] behaviour of uac_redirect module

2016-06-27 Thread Dirk Teurlings - Signet B.V.
On 06/22/2016 07:45 AM, Daniel-Constantin Mierla wrote: > Looking quickly at the code, both versions of the functions are > executing the same inner function, but there can still be some > conditions on the reason parameter, so I need to dig in further. > > However, I need to understand first what