[OpenSIPS-Users] error_route not triggering
bogdan at opensips.org
Mon Feb 4 03:54:48 EST 2019
There is nothing extra for you to do. The error route should be triggered.
You get this error -
https://github.com/OpenSIPS/opensips/blob/master/receive.c#L147 and if a
request, the error route should be triggered (see line 151).
Try to log in debug level, maybe you will get more relevant data.
OpenSIPS Founder and Developer
OpenSIPS Summit 2019
On 01/25/2019 12:14 AM, Ben Newlin wrote:
> I recently noticed some parsing errors in our logs and after digging
> further I’ve realized that our error route is not triggering when this
> occurs. Is there some sort of subscribe or attach operation needed to
> get calls to the error route? The documentation states it will be
> called automatically. I’ve been able to reproduce the issue in our
> testbed. We are running OpenSIPS 2.4.4.
> My error route is defined like this:
> xlog("L_ALERT", "Error route called!\n");
> This is what I get from OpenSIPS logs:
> Jan 24 21:59:30  ERROR:core:receive_msg: Unable to parse msg
> received from [203.0.113.4:48096]
> Jan 24 21:59:30  ERROR:core:parse_first_line: bad request first line
> Jan 24 21:59:30  ERROR:core:parse_first_line: at line 0 char 17:
> Jan 24 21:59:30  ERROR:core:parse_first_line: parsed so far:
> INVITE sip:bad to
> Jan 24 21:59:30  INFO:core:parse_first_line: bad message
> Jan 24 21:59:30  ERROR:core:parse_msg: message=<INVITE sip:bad to
> syntax\r\n at 203.0.113.2:5060;transport=UDP;user=phone SIP/2.0
> My log from the error route is not called.
> Any help would be appreciated. I’m probably missing something simple.
> Ben Newlin
> Users mailing list
> Users at lists.opensips.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users