Hi,
Take a look at the error route which serve this purpose - if a syntax
error is encountered, script execution jumps to that route.
http://www.opensips.org/Resources/DocsCoreRoutes16#toc5
Regards,
Bogdan
thrillerbee wrote:
What is the easiest way to identify traffic with invalid headers?
Hi,
I use a modified version of functions db_check_from() and db_check_to() from
the uri module. See *patch upload **3076779.* This adds a q option so
that parse errors don't end up in syslog and an e option to only check for
well-formed-ness, not actually check the db.
Regards,
Kennard
On Fri,
Thinking a bit about your case - do you know what all good traffic should
look like? If so - could you possibly create one REGEX statement that would
say if it doesn't look like this - discard ?
I don't think $fu can be NULL unless it's actually not in the packet. as
far as I can tell - OS
I'm really trying to find methods of combating memory leaks that I now
believe must be caused by some specific traffic pattern. As a result, I'm
trying to filter as much bad traffic as possible before it gets into the
core of my network.
I *have* seen parse errors on the from header as I use
I'm relatively new to OpenSIPs myself - but in my various experiments - the
idea that OS cannot parse a header is a bit foreign. As a SIP proxy - it's
job is more to use the routing logic in order to transmit packets from A
through to C via B (OS itself).
I have sent packets with bogus From and
What is the easiest way to identify traffic with invalid headers?
Specifically, the from and to URIs.
For example, if OpenSIPS is unable to parse a from URI, would $fu be NULL?
Thanks.
___
Users mailing list
Users@lists.opensips.org
