[OpenSIPS-Users] error_route not triggered for parsing error

[Mark Allen]

This seems to link to a past thread where error_route is not triggering if
the first line is malformed. Unfortunately, there is no resolution to this
past thread - link here:
https://opensips.org/pipermail/users/2019-February/040605.html

On Thu, 27 May 2021 at 11:56, Mark Allen <mark at allenclan.co.uk> wrote:

>
> In my script, I have an error_route...
>
> error_route {
>    xlog("--- error route class=$(err.class) level=$(err.level)
>         info=$(err.info) rcode=$(err.rcode) rreason=$(err.rreason)
> ---\n");
>    xlog("--- error from [$si:$sp]\n+++++\n$mb\n++++\n");
>    sl_send_reply($err.rcode, "$err.rreason");
>    exit;
> }
>
> ...but when I get a message parsing error, the error_route seems to ignore
> it. What am I doing wrong?
>
> ERROR:core:parse_method: invalid character :
> INFO:core:parse_first_line: failed to parse the method
> INFO:core:parse_first_line: bad message
> ERROR:core:parse_msg: message=<Contact: <sip:1234 at abc.def.com:5060>#015#012User-Agent:
> MWWRTC 3.4.21042#015#012Accept:
> application/sdp,application/dtmf-relay,text/plain#015#012SIP/2.0 200
> OK#015#012Via: SIP/2.0/TCP 192.168.1.23:5060;rport=57559;received=192.168.1.23;branch=z9hG4bK72a5d21#015#012From:
> <sip:pinger at 192.168.1.23>;tag=33e693c3#015#012To:
> <sip:xxx.xxx.xxx.xxx:5060>;tag=1550918023#015#012Call-ID:
> fc585e54-72a5d21-ab2 at 192.168.1.23#015#012CSeq
> <http://fc585e54-72a5d21-ab2@192.168.1.23#015%23012CSeq>: 1
> OPTIONS#015#012User-Agent: Yealink SIP-T54W#015#012Content-Length:
> 0#015#012#015#012>
> ERROR:core:receive_msg: Unable to parse msg received from [
> 192.168.1.23:5060]
> ERROR:core:tcp_handle_req: receive_msg failed
>
>
> We are running OpenSIPS 3.1
>
>
> (this is a follow-up to my other query
> http://lists.opensips.org/pipermail/users/2021-May/044776.html)
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210527/23e48f44/attachment.html>