Hello,
If you are already using http_async_reply and therefore processing the request stateful, I personally would just stay stateful.
What is your motivation about trying to avoid it?
Cheers,
Henning
From: Julius Flohr <flohr@sipgate.de>
Sent: Tuesday, January 10, 2023 4:47 PM
To: sr-users@lists.kamailio.org
Cc: Alles wird besser <alleswirdbesser@sipgate.de>
Subject: [SR-Users] Performing async_http calls on stateless Loadbalancers
Hi List,
we are running several stateless SIP Loadbalancers using Kamaillio 5.1 and 5.6.
Now we would like to perform an async_http request if an INVITE matches certain criteria. The request itself is performed very similar to how it's described here [1]
This uses the transaction module in order to assure that the response can be mapped to the original request. However, this also means that the processing of the entire request becomes stateful which we would like
to avoid.
We tried to use t_release() in the callback route (in [1] this route is called "RELAY_API_RESPONSE"). However, documentation says that this is only allowed in the REQUEST_ROUTE.
Is there an easy way to circumnavigate this issue?
--
Julius Flohr - Voice Engineer - flohr@sipgate.de
Telefon: +49 (0)211-63 55 55-0
Mobil: +49 (0)1579-000-0205
Telefax: +49 (0)211-63 55 55-22
sipgate GmbH - Gladbacher Str. 74 - 40219 Düsseldorf
HRB Düsseldorf 39841 - Geschäftsführer: Thilo Salmon, Tim Mois
Steuernummer: 106/5724/7147, Umsatzsteuer-ID: DE219349391
www.sipgate.de - www.sipgate.co.uk