I understand my mistake.
It's working when message is broken.
I wanted to use it for bad SDP.
We have a problem with SDP from some users.
In error of parsing SDP on log printed only wrong part of SDP
and correlation to call is very difficult.
Thank you,
Julia
On Wed, Oct 1, 2014 at 3:54 PM, Daniel-Constantin Mierla <miconda(a)gmail.com>
wrote:
Hello,
iirc, the event route is executed only when the sip request is so broken
not to make it till config file execution.
In your previous email on this topic that I had in mind to reply but got
forgotten, you refer to From. That is not part of the basic parsing (again,
iirc), you should catch that using sanity_check() function from sanity
module, using it somewhere at the top of config request route (see default
config, it is in the route[REQINIT)).
Cheers,
Daniel
On 01/10/14 14:38, Julia Boudniatsky wrote:
Hello,
I try to use event_route[core:receive-parse-error] in 4.1.6
event_route[core:receive-parse-error] {
xlog("L_WARN", "Event-parse-error: $rm from
$avp(inc_carrier)/n$mb/n");
}
When core parse error occurs , *log message is not printed*.
What is wrong?
Thank you,
Julia
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
listsr-users@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin
Mierlahttp://twitter.com/#!/miconda -
http://www.linkedin.com/in/miconda
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users