Thanks for your reply Henning!
I also removed it from my script.
The only thing is that when using it there is this nasty side effect, so I
think if the function is meaningless it can be removed.
I will create a ticket for it, so it can be evaluated what is the best
approach.
Thank you,
Kind regards,
Patrick Wakano
On Thu, 28 Nov 2019 at 06:12, Henning Westerholt <hw(a)skalatan.de> wrote:
Hello,
usually it is not needed anymore to do this t_newtran early in the cfg.
Check this discussion from 2015 out:
http://sip-router.1086192.n5.nabble.com/Transaction-good-practices-with-t-r…
There is also another function in tmx, t_precheck_trans which can be used
to detect re-transmissions without actually creating a new one.
Cheers,
Henning
--
Henning Westerholt –
https://skalatan.de/blog/
Kamailio services –
https://gilawa.com
*From:* sr-users <sr-users-bounces(a)lists.kamailio.org> *On Behalf Of *Patrick
Wakano
*Sent:* Wednesday, November 27, 2019 3:26 AM
*To:* Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
*Subject:* [SR-Users] Possible conflict between t_newtran and setflag for
ACC
Hello list,
Hope you all doing well!
I am using the ACC module and using the setflag() function as done in
several examples. It works fine. However, I've added the t_newtran()
function almost in the begging of the INVITE handler to help the
retransmission detection and after that I noticed the ACC was not saving
anything in DB.
So after debugging I discovered that if I call the t_newtran() before
setting the ACC flags, the module will not save the calls in DB, but if I
call it after setting the ACC flags, it works....
So my question is, is this a bug or it is a expected side effect so when
one is using t_newtran you must be careful and set all your transaction
flags before? (ACC are the only transaction flags I am using so can't tell
if other modules have the same problem)
This is happening in Kamailio 5.2.2.
Thank you!
Kind regards,
Patrick Wakano