22 May
2006
22 May
'06
7:23 p.m.
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".
based on that, i understand that it is not possible to report missed call only in case all forks fail. if so, then i guess during post processing of accounting records, one needs to reject failure reports if there also exists a positive report for the same call.
-- juha