[OpenSIPS-Devel] [ opensips-Bugs-3514120 ] B2B - core on reply when 408

SourceForge.net noreply at sourceforge.net
Tue Apr 3 11:41:00 CEST 2012


Bugs item #3514120, was opened at 2012-04-02 04:56
Message generated for change (Settings changed) made by bogdan_iancu
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=3514120&group_id=232389

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: modules
Group: 1.8.x
Status: Open
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Nick Altmann (nikbyte)
Assigned to: Bogdan-Andrei Iancu (bogdan_iancu)
Summary: B2B - core on reply when 408

Initial Comment:
If b2b generates 408 Timeout, in b2b_reply route $mb is null and if I do
route[B2B_REPLY] {
    xlog("b2b_reply $si:$sp\n");
}
opensips crashes:
Apr  2 15:53:30 opensips /usr/sbin/opensips[15011]: CRITICAL:core:ip_addr2a: unknown address family 0
Apr  2 15:53:31 opensips /usr/sbin/opensips[15022]: CRITICAL:core:receive_fd: EOF on 23
Apr  2 15:53:31 opensips /usr/sbin/opensips[15000]: INFO:core:handle_sigs: child process 15011 exited by a signal 11
Apr  2 15:53:31 opensips /usr/sbin/opensips[15000]: INFO:core:handle_sigs: core was generated
Apr  2 15:53:31 opensips /usr/sbin/opensips[15000]: INFO:core:handle_sigs: terminating due to SIGCHLD
Apr  2 15:53:31 opensips /usr/sbin/opensips[15022]: INFO:core:sig_usr: signal 15 received


----------------------------------------------------------------------

>Comment By: Bogdan-Andrei Iancu (bogdan_iancu)
Date: 2012-04-03 02:40

Message:
OK, update from SVN please, this should be fixed.

Thanks and regards,
Bogdan

----------------------------------------------------------------------

Comment By: Nick Altmann (nikbyte)
Date: 2012-04-02 22:03

Message:
In case of timeout, there are $rr="Timeout", but $rs is NULL. It would be
helpful, if $rs="408".
I understand that it's fake call, but $rs and $rr needed for identify
reply.

So, problems:
1. Empty $rs when 408.
2. CRLF in $ci


----------------------------------------------------------------------

Comment By: Bogdan-Andrei Iancu (bogdan_iancu)
Date: 2012-04-02 13:58

Message:
OK, one step forward :)

The $mb is NULL as the "408" you have there is an internally generated
reply, not a real received one. So, it is a FAKED reply (just a reply code
and status) - it is actually build only when to be sent out.
As this route gives access to received replies, it is impossible to provide
a body to an internally reply.

Regarding the $ci (the ending CRLF), I will look into.


----------------------------------------------------------------------

Comment By: Nick Altmann (nikbyte)
Date: 2012-04-02 11:25

Message:
Now it not crashes, but $mb is still NULL. I think $mb should contain 408
reply.
Also why $ci ended by "\r\n" in b2b_reply?
$si, $sp point to self (ok).


----------------------------------------------------------------------

Comment By: Bogdan-Andrei Iancu (bogdan_iancu)
Date: 2012-04-02 08:22

Message:
Please apply and test the attached patch.

Thanks and regards,
Bogdan

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=3514120&group_id=232389



More information about the Devel mailing list