Re: [SR-Users] PostgreSQL - How To

2016-03-18 Thread Daniel-Constantin Mierla
Hello, On 16/03/16 13:56, Barış Şekerciler wrote: > Hello everyone, > I have Kamailio server which runs at 192.168.2.170 address and have > PostgreSQL server which runs at 192.168.2.174. > > So I tried to arrange Kamailio for working with PostgreSQL but I think > I give something miss. I couldnt h

[SR-Users] htable - banning users

2016-03-18 Thread meres gr
I am using the following script to ban users failing to authenticate with fail2ban: My problem is that it logs attempts of users only existing to the database I would like to modify it in order to log all FAILED authentication attempts Is this possible? # Authentication route route[AUTH] { #!ifdef

[SR-Users] srv_query question

2016-03-18 Thread Vasiliy Ganchev
Hi folk! I am trying to implement srv_query usage in my script (server is based on Kamailio+Asterisk). The task: when outgoing REGISTER comes from Asterisk (outgoing trunk to operator), and R-URI consists domain name, need to store all ip-addresses of remote side (for following use) Currently, th

Re: [SR-Users] htable - banning users

2016-03-18 Thread Vasiliy Ganchev
Hi! you need to add one more case in switch ($retcode) condition: -3 (invalid user) - authentication user does not exist look in complete list of negative codes here: http://www.kamailio.org/docs/modules/4.3.x/modules/auth_db.html#auth_db.f.www_authenticate Hope this helps Cheers! -- View t

Re: [SR-Users] Missing pipelimit values in data returned by JSONRPC-S

2016-03-18 Thread Alex Balashov
Indeed, I can confirm that this happens even with two entries, running 4.3:9506574: [root@allegro-4 ~]# kamcmd -s /tmp/kamailio_ctl pl.stats PIPE: id=bg350_ingress load=0 counter=0 PIPE: id=bg208_ingress load=0 counter=0 [root@allegro-4 kamailio]# curl --digest --user:pass http://10.150.20.6:5

Re: [SR-Users] htable - banning users

2016-03-18 Thread Daniel-Constantin Mierla
Hello, I think auth_check() returns a particular code if the user doesn't exits -- see the readme and add the return code to the switch along with the -2 value. Alternative, you can use the function is_subscriber() from auth_db module to detect if the user exists or not, and if not, ban it direct

Re: [SR-Users] Missing pipelimit values in data returned by JSONRPC-S

2016-03-18 Thread Daniel-Constantin Mierla
I pushed a patch in master branch for now -- commit id 1c22f395df81dab09288ff945e97b0040894daaf Can anyone test and see if solves it? Then, if all ok, I will backport. Cheers, Daniel On 17/03/16 22:14, Alex Balashov wrote: > Indeed, I can confirm that this happens even with two entries, running

Re: [SR-Users] for kamailio registration

2016-03-18 Thread Daniel-Constantin Mierla
Search the net for ngrep, sngrep, sipgrep, tcpdump or wireshark -- all of them are open source tools that can be used for capturing the sip traffic. For ngrep, a good command to run on sip server is: ngrep -d any -qt -W byline "sip" port 5060 Cheers, Daniel On 15/03/16 16:44, Shiv Patidar wrote