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?
Cheers
[1]: https://wazo-platform.org/blog/kamailio-routing-with-rtjson-and-http-async-c...
--
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
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
-- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.comhttps://gilawa.com/
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?
Cheers
[1]: https://wazo-platform.org/blog/kamailio-routing-with-rtjson-and-http-async-c...
--
Julius Flohr - Voice Engineer - flohr@sipgate.demailto: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.dehttp://www.sipgate.de - www.sipgate.co.ukhttp://www.sipgate.co.uk
Hi Julius, it should be possible to use http_async in a stateless scenario setting $http_req(suspend) to 0 https://www.kamailio.org/docs/modules/5.6.x/modules/http_async_client.html#i... . Have you tried this?
Cheers,
Federico
On Tue, Jan 10, 2023 at 7:25 PM Julius Flohr flohr@sipgate.de wrote:
Hi Henning,
Thanks for your reply. The issue is that we have several load balancers behind an anycast setup and it’s not guaranteed that every packet belonging to a transaction is indeed processed by the same server.
Cheers
Julius
On 10. Jan 2023, at 17:29, Henning Westerholt hw@gilawa.com wrote:
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
--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com
*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?
Cheers
--
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
Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
-
Federico Cabiddu -
Henning Westerholt -
Julius Flohr