Open NormB opened 2 months ago
Possibly related to this: https://github.com/OpenSIPS/opensips/issues/3385
Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days.
Up
Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days.
Up
Hi, have you tried with latest version having that fix: https://github.com/OpenSIPS/opensips/commit/c4032f94f3993d1b62a0483eaae3ac0bd6c7c358 ? I haven't analyzed your crash but it looks like this commit may resolve corruption around some race conditions
Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days.
up
OpenSIPS version you are running
Crash Core Dump
Backtrace showing that bentity1 is NULL.
Describe the traffic that generated the bug
A REFER is being processed and during that process, a 603 is generated by the referred-to system.
A failure_route[] has been armed (and is being executed). Currently, no processing other than logging is performed in the failure_route[].
The REFER logic is similar to this example (https://www.opensips.org/Documentation/Tutorials-B2BUA-3-2):
The b2b_end_dlg_leg(); appears to be causing bentity1 to be correctly deleted. However, the process_bridge_200OK logic does not perform any validation of either bentity1 or bentity2 prior to using them.
See the code snippet (at the location of the segfault) below:
b2b_logic/bridging.c:895:
To Reproduce
Configure the REFER logic as defined in the above example. Configure a faulure_route[] --- This step might not be required Configure the refer-to system to return a failure (for example 603) Attempt to make a call that flows through the REFER logic.
Relevant System Logs
OS/environment information
Additional context