This was done not very long ago, to fix other issues. Practically, a suspend is creating a
'fake' branch that is never sent out, but can time out to close the transaction
nicely if the transaction is not resumed. If resumed, the branch is marked anyhow as
consumed, the transaction being already created and with a branch not being answered. So,
from tm states point of view, is like failure_route rather than pre-transaction request
route.
What are the issues you are facing? After resuming, which async module does in this case,
you should work in transaction context anyhow.
--
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/750#issuecomment-240813287