Hey Brett,
I agree that the terminology around the ’suspend’ might be confusing. The
concept that this configuration vernacular is trying to invoke — and, in fact,
uses under the hood — is that of the TM module’s t_suspend() / t_continue()
functionality:
Hey Alex,
Thanks that was really helpful.The $avps were available. Just needs a
little refactoring to work as expected.
Doesn't feel like a "suspend". I think calling it that and not being more
clear in the docs is confusing. But I can see how it kinda makes sense.
Appreciate the help,
Brett
On
A little more helpfully, perhaps:
- By default, a transaction is not created until t_relay(); if you want
`http_async_client` to preserve any transaction-affiliated information, you’ll
need to create it explicitly with t_newtran() beforehand;
- Only transaction-persistent information is
> On Aug 18, 2022, at 5:50 PM, Brett Nemeroff
> wrote:
>
> When I get to the end of the HTTP_REPLY block, I'm EXPECTING it to RESUME
> FROM the suspended location from the original route block, which it does NOT
> seem to do. Is that expected?
No, alas, that’s not going to happen.
— Alex
Hello Kamailio Team!
I've tried following the documentation for http_async_query() with
suspend=1 and not getting results I'm expecting. Perhaps I'm
misunderstanding the documentation.
Basically I'm performing a http_async_query() with suspend set to 1 and a
"route_name" set to HTTP_REPLY.
When
