[bug]: Failed assertion user_data is NULL (0) at line 1090 in stasis_subscription_set_filter of stasis.c about asterisk HOT 8 CLOSED

I also have the pcap of the blind transfer if that helps as well. I don't see anything wrong with the SIP headers at first glance.

from asterisk.

Is there debug level information? Does Asterisk crash? Was Asterisk built with DONT_OPTIMIZE? What is the specific usage? Are you using external_replaces? If Asterisk is locked as you say please provide a deadlock backtrace[1] as well.

[1] https://docs.asterisk.org/Development/Debugging/Getting-a-Backtrace/?h=backtrace#reporting-crashes-and-deadlocks

from asterisk.

Asterisk itself is not locked. Dialplan operations can continue when this happens so there’s no deadlock backtrace. The PJSIP stack gets locked and can no longer take INVITE requests.

Yes using external_replaces, however, in this case the logs for external_replaces never show because this error happens before any actual dialplan logs are produced.

This is a routine blind transfer from an endpoint using REFER after receiving an inbound call.

the issue only occurs after 4+ days of asterisk running. No other errors in the logs and memory usage is ~2GB (which seems fine).

from asterisk.

That's still a deadlock, so a backtrace would show where exactly the PJSIP stack is stuck which may provide better insight into the particular scenario or case that is causing the issue. Debug level information can also show the full progression of events, such as other threads that may be involved or have done something to cause a problem.

from asterisk.

Is a backtrace required in order for this issue to move forward or would debug logging be good enough? If so, any specific module debug or just core debug?

from asterisk.

Ideally, both. The more information provided the easier it can be to diagnose and resolve issues. Can I just accept the issue without a backtrace? I can, but if someone else comes along and sees that PJSIP is locked and there's no backtrace then they'll probably just ignore the issue since it's too much effort for them and not even take a look or give any thought to working on it. No particular module comes to mind for debug, a core debug would be best.

Less friction for someone to work on an issue, the higher chance someone may.

from asterisk.

This issue is stale because it has been open 7 days with no activity. Remove stale label or comment or this will be closed in 14 days.

from asterisk.

This issue was closed because it has been stalled for 14 days with no activity.

from asterisk.