You probably know this article, already, but Nick vs Networking has this
nice explanation:
Stateless, Stateful, Dialog Stateful and Transaction Stateful SIP Proxies |
Nick vs Networking
<https://nickvsnetworking.com/stateless-stateful-dialog-stateful-and-transaction-stateful-sip-proxies/>
Atenciosamente / Kind Regards / Cordialement / Un saludo,
*Sérgio Charrua*
On Sat, Dec 21, 2024 at 5:31 PM Alexis Fidalgo via sr-users <
sr-users(a)lists.kamailio.org> wrote:
Hello, after the discussion regarding http and
http_async, I started some
labs to make a comparison and see what’s the trade off and the associated
cost.
Main problem (to me) is im not clear on how transactions behave. Im
running some fast tests now before I start to deploy the final scenarios
and
1. A new transaction is created before the http_async call (as the module
example shows for http_async_query function
2. The http_async_query call is executed, receives a response and the
HTTP_REPLY route for http_async_query is executed.
3. As we need to redirect the call, im adding Contact information with
append_to_reply and then calling t_reply(302,”Redirect)
Up to here INVITE is received, a 100 is answered and then the 302 with the
expected Contact information (collected and built from the http_async_query
response), problem is that the 302 is retransmitted 3 more times.
So, im not even sure that im doing the correct actions to process the call
this way. Is there a document/book/reference I can read to understand
transactions better?
By now I can not handle the call to be processed correctly (without the
retransmissions) and finish the transaction the correct way.
Any help, link, guide, will be appreciated.
Regards.
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions --
sr-users(a)lists.kamailio.org
To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to
the sender!