Bogdan-Andrei Iancu writes:
- the "missed call" flag has effect only on the next serial fork - once triggered to report a missed call (a serial fork step ended), the flag is automatically reset by module. To catch the potential "missed call" reports due next serial forks, you need to re-arm the flag from failure route. This behaviour gives full control over what branches should be or not accounted as "missed calls".
coming back to this, what i would like to do is to have an accounting report to be send only upon:
* TMCB_RESPONSE_OUT -- a final reply was sent out (either local * or proxied) -- there is nothing more you can change from * the callback, it is good for accounting-like uses.
and if at that moment both radius_flag and radius_missed_flag (or log_flag and log_missed_flag) are set and final reply is negative (>= 400), then only one report should be sent out.
-- juha