12 Dec
2019
12 Dec
'19
2:45 a.m.
Hello,
it was supposed to be about sip message flags (the setflag() and
resetflag() operations) - I updated that paragraph to clarify it. Feel
free to add more or remove content to make it better.
Cheers,
Daniel
On 12.12.19 08:01, Juha Heinanen wrote:
I noticed this in t_newtrans() README:
Note that any flag operations (e.g. for accounting) after this
function has been called will be ignored. You can use the the tmx
module function t_flush_flags() to flush the altered flags to the
already created transaction.
The text is wrong. I have for ages set bflags after calliing
t_newtrans() and the sets are NOT ignored.
Here is an example:
In route blocks:
Dec 12 08:41:53 /usr/bin/sip-proxy[231131]: INFO: ********* called t_newtrans()
Dec 12 08:41:53 /usr/bin/sip-proxy[231131]: INFO: ************ set bflag 9
In failure route block:
Dec 12 08:41:58 /usr/bin/sip-proxy[231195]: INFO: ************ bflag 9 is set
-- Juha
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com