Transaction Management

Chandra Bhan via sr-dev <[email protected]>
Newsgroups gmane.comp.voip.openser.devel,gmane.comp.voip.ser
Message-ID <OL1P279MB0001D3F63882304FCDB0DA20AE7FA@OL1P279MB0001.NORP279.PROD.OUTLOOK.COM>
Hi Henning,



I need one clarification



The flow is as follows:

  1.  SIPP send the INVITE to kamalio
  2.  Kamalio send 100 trying
  3.  Kamalio open transaction and send HTTP for async to external system
  4.  External System send HTTP response
  5.  Kamalio send 480 to SIPP
  6.  SIPP send ACK



If we want to use async, transaction module is important. But if send 480 response before sending HTTP, then we get error. It look like call session ends if we send 480 and hence HTTP async fails.



I want to delink SIP call flow with HTTP hit. I want to complete the SIP flow and the may be intimate the partner about the call thru HTTP.



Can this be done? Should I use kafka here instead of HTTP and may be transaction module may be not required as well.


I want to understand how these transactions are cleared in Kamalio once they are created.



Below, thing we are seeing transaction count as around 48000 which should be cleared ideally. I assume this 4800 is the count of outstanding call in the system.



Below is the history of previous messages.


If I use HTTP/1.1, I am not able to use Connection: keep alive option as the connection is getting closed. What is the way to use Connection keep alive option in HTTP async request?

I want to use HTTP/2 for sending the request to network instead of HTTP/1.1 while using async worker.



Can someone suggest how to use HTTP/2?


modparam("http_async_client", "connection_timeout", 1000)
modparam("http_async_client", "timeout", 2000)



I understand connection_timeout is the timeout for making HTTP connection, but timeout is the read timeout, where you wait for response.



But timeout is not working. Can you confirm if there is something like this.



Regards
Chandra Bhan Kumar

_______________________________________________
Kamailio - Development Mailing List -- [email protected]
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the sender!
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.