22 May
2006
22 May
'06
5:47 p.m.
Bogdan-Andrei Iancu writes:
behaviour fix:
- 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.
assuming the above holds true for radius_missed_flag, then how about radius_flag? does it remain set for all serial branches? if so, why would its behavior be different from radius_missed_flag?
-- juha