This has implications on other parts, such as variables where they can be accessed and set via $mf (iirc).

On the other hand, I don't think having a variable with different lengths is a good approach, because it can break easily config behaviour when moving from one server to another. It should be same size on 32b or 64b, so if a change to increase the size is to be done, then should be long long to ensure it is 64 on all archs. An alternative would be to make the field inside sip_msg_t an array of flag_t values, so can be one or more, even beyond 64b. But this change will have also impact in other parts, therefore would need careful review.

As an alternative for now would be using an avp or xavps, and do bitwise operations (| and &) to set or test.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.