Looking at the backtrace, the execution continues with a `faked_msg` structure:
```
#14 0x000000000048e205 in run_top_route (a=0x7f3f732aa9c0, msg=0xb04f60
<_faked_msg>, c=0x0) at core/action.c:1661
#15 0x00007f3f705f7d0e in async_http_cb (reply=0x7f3f2b7ee620,
param=0x7f3f2b7eca18) at async_http.c:256
```
which, based on the code, is done when the query is done without suspending the
transaction:
*
https://github.com/kamailio/kamailio/blob/master/src/modules/http_async_client/async_http.c#L220-L268
Now I see that @abalashov's example is:
```
$http_req(suspend) = 1;
```
So I wonder if there is an issue propagating it or there are cases in
@abalashov's config not setting it.
On the other hand, the crash seems to be because in the worker process
continuing the execution with the faked_msg, the list of avps is not valid,
maybe they were not reset from a previous execution. The avps there are not for
sure those you set for the received SIP request, because, again, it is not
resuming any transaction in this case, so it doesn't get the avps from
transaction.
@abalashov - do you have event_route blocks in your config? Those are the usual
suspects running with a faked_msg structure.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2286#issuecomment-614556955
_______________________________________________
Kamailio (SER) - Development Mailing List
sr-dev@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
