[SR-Users] Transaction good practices with t_relay t_newtran and t_release

Mickael Marrache mickaelmarrache at gmail.com
Thu Apr 30 10:31:24 CEST 2015


I think one would like to create transaction ASAP to absorb retransmissions.
In some scenarios, processing a message can take time and retransmissions
are likely to happen, and you don't want the retransmissions to be processed
again (which can lead to errors in some scenarios). t_relay is generally
called at the end for relaying the message.


-----Original Message-----
From: sr-users [mailto:sr-users-bounces at lists.sip-router.org] On Behalf Of
Alex Balashov
Sent: Thursday, April 30, 2015 11:26 AM
To: Dirk Teurlings - SIGNET B.V.
Subject: Re: [SR-Users] Transaction good practices with t_relay t_newtran
and t_release


Why do you need to create new transactions yourself with t_newtran()?
Nonexotic applications of Kamailio usually don't require this. A transaction
is automatically created after t_relay() is called, and its lifecycle is
automatically managed - including destruction - based on the replies
received to the transaction-forming request, and based on RFC 3261 rules in
cases of timeouts.

Alex Balashov | Principal | Evariste Systems LLC
303 Perimeter Center North, Suite 300
Atlanta, GA 30346
United States

Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

Sent from my BlackBerry.

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users at lists.sip-router.org

More information about the sr-users mailing list