I thought I replied to this, but actually I couldn't find it, maybe I
just had the intention to do it and then got distristracted by something
else -- thanks for the reminder.
The proposed changes are fine with me, they can be committed.
Daniel
On 8/29/13 2:53 PM, Juha Heinanen wrote:
Daniel
Daniel-Constantin Mierla writes:
> I will comment over the rest of proposed changes once I will check the
> sources.
i guess you have been too busy to check this:
> > in parser/parse_fline.c, i would like to make the first three L_DBG and
> > change the last to L_ERR:
> >
> > LOG(L_INFO, "E
Daniel-Constantin Mierla writes:
> Indeed, the efective execution of the actions was missing.
thanks, now it works.
-- juha
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-rout
On 8/22/13 5:24 PM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
Hope I caught it and fixed now in master.
i tried, but still no luck:
Indeed, the efective execution of the actions was missing.
I will comment over the rest of proposed changes once I will check the
sources.
Cheer
Daniel-Constantin Mierla writes:
> Hope I caught it and fixed now in master.
i tried, but still no luck:
Aug 22 18:15:18 siika /usr/sbin/sip-proxy[21745]: INFO:
[parser/parse_fline.c:229]: parse_first_line(): ERROR:parse_first_line: bad
request first line
Aug 22 18:15:18 siika /usr/sbin/sip-p
Hope I caught it and fixed now in master.
Regarding the verbosity, debug can be lowered, as one option that can be
done now.
The second is to update the code so these log messages are printed to
corelog level and change this value in config to be higher than debug:
http://www.kamailio.org/w
Daniel-Constantin Mierla writes:
> I backported the patch for the log message and now I pushed a patch that
> executes event_route[core:receive-parse-error] in such case as well,
> allowing for config interaction. Can you give it a test, I had no time
> to do it so far and have to go for a whil
On 8/22/13 7:11 AM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
We can add an event_route for it as well as print the src ip in the log
message for quick fix (this one can be backported easy).
thanks for the quick fix. please backport to 4.0. for the next
release, event_route woul
Daniel-Constantin Mierla writes:
> We can add an event_route for it as well as print the src ip in the log
> message for quick fix (this one can be backported easy).
thanks for the quick fix. please backport to 4.0. for the next
release, event_route would be nice to have so that the error mess
Sergey Okhapkin writes:
> Actually nothing needs to be done in kamailio core. I's a simple scripting
> logic.
>
> if(!sanity_check("whatever_you wan't_check")) {
> xlog("L_INFO","Malformed message from $proto:$si:$sp\n$mb\n");
> break;
> }
in this
The problem is that in some cases, it doesn't get to execute the config
file at all. The core does some basic parsing to detect the type of
message (request or reply) and looks for mandatory headers (CSeq is one
of them). When its a failure in this process, the config file is not
executed, beca
Actually nothing needs to be done in kamailio core. I's a simple scripting
logic.
if(!sanity_check("whatever_you wan't_check")) {
xlog("L_INFO","Malformed message from $proto:$si:$sp\n$mb\n");
break;
}
On Thursday 22 August 2013 00:07:56 Daniel-Con
On 8/21/13 12:53 PM, Juha Heinanen wrote:
i have noticed lots of these kind of attacks in my syslog:
/var/log/syslog.1:Aug 21 04:23:46 host /usr/sbin/sip-proxy[13490]: ERROR:
[parser/parse_cseq.c:95]: parse_cseq(): ERROR: CSeq EoL expected
/var/log/syslog.1:Aug 21 04:23:46 host /usr/sbin/sip-
i have noticed lots of these kind of attacks in my syslog:
/var/log/syslog.1:Aug 21 04:23:46 host /usr/sbin/sip-proxy[13490]: ERROR:
[parser/parse_cseq.c:95]: parse_cseq(): ERROR: CSeq EoL expected
/var/log/syslog.1:Aug 21 04:23:46 host /usr/sbin/sip-proxy[13490]: ERROR:
[parser/parse_cseq.c:9
14 matches
Mail list logo
