Hi Bogdan, That makes sense to me. In fact, that seemed to be the central point of the argument against using a STOP record for a failed call: "You can't STOP what never STARTed in the first place." Perhaps the argument from the other side is that one must take a unique identifier into consideration? I cannot claim to understand the implications yet. I started playing with radius accounting only last week. :)
Thankfully, the patch buried within the contrib directory of CDRTool applied well against freeradius-server-2.1.3. Failed calls from OpenSIPS now cause SQL records to be inserted. Inspecting the inserted records, however, I don't see anything indicating whether it was a START, STOP, or FAILED at the radius level. Perhaps the only indicator is the session time? I'm still investigating. - Jeff On 12/15/08 6:36 AM, "Bogdan-Andrei Iancu" <[email protected]> wrote: > Hi Jeff, > > OpenSIPS is still sending the FAILED values for the missed calls. From > ACC point of view, you have two cases - A) established calls > (START+STOP) and B) failed calls (FAILED). > > If you use the STOP also for the failed calls, wouldn't be a confusion > in between the STOP of an ongoing call and the STOP of a failed call? > > Regards, > Bogdan > > Jeff Pyle wrote: >> Hello, >> >> It seems there was a long thread some time back about using the >> so-called non-standard ³Acct-Status-Type = Failed² in the radius >> packet. The two proposed solutions seemed to be 1) use a Stop type >> instead of Failed, or 2) patch Freeradius. >> >> Since I¹m still seeing the Failed type in the radius detail file, it >> appears OpenSIPS didn¹t change to Stop. >> >> So, anyone know of a patch for current Freeradius sources? >> >> >> Thanks, >> Jeff _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
