[SR-Users] is t_flush_flags() really needed?

Juha Heinanen jh at tutpro.com
Sun Mar 25 10:29:33 CEST 2018


While testing xflags, i noticed that a regular flag that I set AFTER
calling t_newtrans() stays set in onreply_route even when I do not
call t_flush_flags().

In a route block:

        if (!t_newtran()) {
            ERROR(Failed to create new transaction for $rm <$ru>);
            exit;
        };
        if (!isflagset(19))
            INFO(******** flag 19 is NOT set after t_newtran());
        setflag(19);

and in onreply_route:

    if (isflagset(19))
        INFO(********* flag 19 is set);
    else
        INFO(********* flag 19 is NOT set);

Syslog gets:

Mar 25 11:24:41 trout /usr/bin/sip-proxy[21362]: INFO: ******** flag 19 is NOT set after t_newtran()
Mar 25 11:24:41 trout /usr/bin/sip-proxy[21433]: INFO: ********* flag 19 is set

So what is the point of t_flush_flags()?

-- Juha



More information about the sr-users mailing list