[Devel] Last changes before CVS freez

Bogdan-Andrei Iancu bogdan at voice-system.ro
Tue May 23 12:51:24 CEST 2006

Hi Juha,

normally only one missed call report should be generated per fork 
sequence. I'm still trying to reproduce what you are reporting, but not 
successful so fat - still getting only one report.
Are you using the latest CVS version?

Accounting is done on TMCB_RESPONSE_OUT. if you set the accounting flag, 
the call report will be triggered at that point - by default only 
successful transactions are reported; to get also the negative ones, you 
need to set the failed_transaction flag also.

Missing calls is a different story - there can be more than one report 
per transaction if serial fork was done.

To achieve your scenario, you need to set the accounting flag (to get 
the call report if successful) and the missed call flag (to get a missed 
call report(s) if the call fails).


Juha Heinanen wrote:

>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

More information about the Devel mailing list