Closed #645.
---
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/645#event-675894765___
sr-dev mailing list
sr-dev@lists.sip-router.org
OK, thanks for testing! I am going to close it here, if you find any new issue,
report it in a new one.
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
I think 827ec4f may have just cracked it, log output with that patch:
```
10(19456) INFO:
Pushed a patch (referred above) that relocates the resetting of
T_ASYNC_SUSPENDED. Can you test and see the results? If all ok, it can be
considered for backporting.
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
The issue #644 is related to this one.
---
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/645#issuecomment-222453210___
sr-dev mailing list
As usual, thanks for the feedback Daniel!
I can work on it and report back.
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Looking at the code I see the T_ASYNC_SUSPENDED flag is cleared at the end of
t_continue(). Possible solutions:
* clear the flag earlier
* use a static var to know that t_suspend() was executed inside the route
block triggered by t_contine()
* use a counter to track the level of
Hi,
sorry for the late answer, I have been travelling last week.
You're right, the problem you are facing does not strictly depend on
http_async_client module. Kamailio's async framework doesn't look to me to
allow suspending again a transaction after having been resumed, even if it does
not
Hi All,
I've been doing some work this week with the new http_async_client module, it
seems that with it's default behaviour it's not possible to execute another
async query in the block immediately following the response, for example the
following config:
```
request_route {
if
