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

SourceForge.net noreply at sourceforge.net
Mon Apr 2 13:56:56 CEST 2012


Bugs item #3514120, was opened at 2012-04-02 04:56
Message generated for change (Tracker Item Submitted) made by nikbyte
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: None
Priority: 5
Private: No
Submitted By: Nick Altmann (nikbyte)
Assigned to: Nobody/Anonymous (nobody)
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


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

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