[OpenSIPS-Users] error_route not triggering

Ben Newlin Ben.Newlin at genesys.com
Fri Feb 8 08:53:14 EST 2019


I have increased the logging level to 6, but unfortunately there is only one new log line that is not helpful.

Feb  8 13:37:53 [333] ERROR:core:parse_first_line: bad request first line
Feb  8 13:37:53 [333] ERROR:core:parse_first_line: at line 0 char 17:
Feb  8 13:37:53 [333] ERROR:core:parse_first_line: parsed so far: INVITE sip:bad to
Feb  8 13:37:53 [333] INFO:core:parse_first_line: bad message
Feb  8 13:37:53 [333] DBG:core:parse_msg: invalid message
Feb  8 13:37:53 [333] ERROR:core:parse_msg: message=<INVITE sip:bad to syntax\r\n at;transport=UDP;user=phone SIP/2.0

Have you been able to successfully trigger an error route in this manner on 2.4.4? Are there any restrictions on where the error route must be defined in the script, e.g. before or after the modules section? I’m just trying to isolate whether it is specific to our implementation and if so, what possible causes exist.

Ben Newlin

From: Bogdan-Andrei Iancu <bogdan at opensips.org>
Date: Monday, February 4, 2019 at 3:55 AM
To: OpenSIPS users mailling list <users at lists.opensips.org>, Ben Newlin <Ben.Newlin at genesys.com>
Subject: Re: [OpenSIPS-Users] error_route not triggering

Hi Ben,

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<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.


Bogdan-Andrei Iancu

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 [329] ERROR:core:receive_msg: Unable to parse msg received from []
Jan 24 21:59:30 [336] ERROR:core:parse_first_line: bad request first line
Jan 24 21:59:30 [336] ERROR:core:parse_first_line: at line 0 char 17:
Jan 24 21:59:30 [336] ERROR:core:parse_first_line: parsed so far: INVITE sip:bad to
Jan 24 21:59:30 [336] INFO:core:parse_first_line: bad message
Jan 24 21:59:30 [336] ERROR:core:parse_msg: message=<INVITE sip:bad to syntax\r\n at;transport=UDP;user=phone<mailto:n at;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<mailto:Users at lists.opensips.org>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20190208/94d86cc8/attachment.html>

More information about the Users mailing list